-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Having trouble with device actions #80
Comments
Are the credentials on the device the same account as the device model you registered in the console? |
Yes, it uses the same credentials with the JSON file downloaded from my account. |
Have you enabled the OnOff trait for that device model id in the console? Can you register a device with that device model id, and update the |
Yes, it's selected under "Supported traits" on the Linked device models webpage. When I try to follow the instructions on this webpage to get DEVICE_INSTANCE_ID, I get stuck at where $ACCESS_TOKEN is written since my sample-googleassistant\app\src\main\res\raw\credentials.json doesn't contain the property with the key "token" in the string. |
If you re-authenticate the tool, then you shouldn't need to save it to the credentials.json |
I'm trying to test the capability of controlling hardware (e.g. LEDs) on the board using Google Voice Assistant. When I give the commands "Turn on" and "Turn off" to control the LED using the NXP i.MX7D Starter Kit, I get "Sorry, power control is not yet supported."
The device has been registered using the registration UI and DEVICE_MODEL_ID was modified to match the device model ID from the webpage. I didn't modify DEVICE_INSTANCE_ID so the value is initialized to "PLACEHOLDER".
The text was updated successfully, but these errors were encountered: