Failing to execute commands thet would normally launch apps on my Chromecast

[adumont]

Describe the bug

Hi,

I have installed assistant_relay docker image on my rpi using apipa169/armv7-hassio-assistant_relay:latest image (a build for the ARM7 Raspberry PI)

I already had a Google Actions project with API & credentials setup, so I downloaded the credentials json from it, and setup went very smooth.

Using Assistant Relay, I am able to run commands like "what will be the weather tomorrow in Madrid", "what time is it" and it works fine. I can also control some devices with "power on alfa" (alfa is a light I have). All that works fine, so I think the setup is correct, as well as permissions...

What is not working for me is when I try to use commands like: "Play music on the chromecast" , "Play Friends from Netflix on the Chromecast" . The answer is something like "I don't understand you" or "Sorry I can't help you with that".

When I say the same sentences to Okay Google on my phone, or to Okay Google to my Raspberry Pi (*) it works fine.

*: I am running Google Assistant on my Raspberry Pi, I can speak to it like a Google Home, and it will actually control the Chromecast with theses exact same sentences just fine. I emphasize here that the credentials I have used in Assistant Relay are exactly the same as the one I am using in the Raspberry Pi (I have downloaded the same json file in both). So I think it can't be a permission problem on the Google project side if it works from the Rpi Google Assistant, but not in Assistant Relay...

Any idea what I am missing here?

Expected behavior

Chromecast would start playing music of the netflix series... instead of saying it doesn't know how to help me (which is absurd as it know very well how to :) ).

Desktop (please complete the following information):

• Platform Linux Ubuntu 16
• Browser Chrome

Additional context

I have launched the docker like this:

docker run -d --name assistant_relay
-p 3000:3000
-v /vol/assistant_relay/config.json:/data/config.json:rw
-v /vol/assistant_relay/audio-responses:/data/audio-responses:rw
apipa169/armv7-hassio-assistant_relay:latest

• Version v3.2.0

[ryancasler]

Rpi Google Assistant doesn't use the same SDK as Google Assistant Relay. The RPi Google Assistant is another device, so it behaves like another Google Assistant device. Assistant Relay only queries the Assistant cloud service. Also, Google Assistant RPi uses voice commands. Assistant Relay only allows text commands. So, they are not the same.

[adumont]

Thanks, I guess I'll have to hack the RPi Google Assistant to see how to use that SDK and launch the text commands as if they were received by voice. I thought it was what the assistant relay was doing internally. El mié., 9 dic. 2020 16:37, ryancasler <[email protected]> escribió:

…

Rpi Google Assistant doesn't use the same SDK as Google Assistant Relay. The RPi Google Assistant is another device, so it behaves like another Google Assistant device. Assistant Relay only queries the Assistant cloud service. Also, Google Assistant RPi uses voice commands. Assistant Relay only allows text commands. So, they are not the same. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#217 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACRLWWPXMNJS4JIFJ5FV53ST6KUTANCNFSM4UR5HFUQ> .

[ryancasler]

Well, when a Google Device can interpret your voice, the voice message is sent to the Google Assistant cloud service. When you enter text, only the text is sent. Some things are only able to be done when it recognizes your voice, like putting your phone on Do Not Disturb. It doesn't matter if your oauth file matches, that function only works with voice commands.

[JakeHedman]

@adumont: If you're really desperate you can try using my abomination of a setup. It's ugly and won't run on a raspberry pi though.