-
Notifications
You must be signed in to change notification settings - Fork 44
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
How to get device_action from AssistResponse #72
Comments
You cannot send a device action from a conversational action. A device action is triggered directly, without having to go through the "talk to" invocation. |
@Fleker , does this implementation have some bult-in actions like the seven (brightness, colorSpectrum, colorTemperature, dock, OnOff, StartpStop, getTemperature) from Python implementation? I'm trying to use this cpp implementation as same the Python SDK on Raspberry Pi. |
@maimang9 any progress with this issue? |
@toymak3r currently have no progress. i think device & device instance's action maybe not configure correctly? |
I'm not sure if the problem are device/device action configuration. We have the same problem even using same device with same id/model_id that works with python sdk version. |
@maimang9 after few days working on different part of code i returned today and got actions on response with CPP SDK example, i do not known why the Built-in Device Actions do not works but with custom actions worked as we needed. use: do not forget to change this values: if you do not already registered your device follows instructions: Here the useful link: https://developers.google.com/assistant/sdk/device-actions-overview |
First i have create some action for my device model with dialogflow.
then I run run_assistant_text and config with my device model id & device instance id,
when enter my "training phrases" of the action , assistant response only "text response" of the action, no device_action response.
how can i get device_action response from assistant?
The text was updated successfully, but these errors were encountered: