Skip to content
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

Brodcast to specific areas or devices ARE SUPPORTED #224

Open
Mightyinks opened this issue Dec 31, 2020 · 13 comments
Open

Brodcast to specific areas or devices ARE SUPPORTED #224

Mightyinks opened this issue Dec 31, 2020 · 13 comments

Comments

@Mightyinks
Copy link

Hello,
I need to point out that broadcast to specific google home is actually supported. In the manual says no and I know it used to be the case but this can now be corrected:

Limitations#
By Google's design, a broadcast goes out to all Google Home devices. This cannot be changed.

Thanksfully it has been supported for a while now and in the assistant relay you can use a command instead of the Broadcast option to send your message to specific ones.
Like this
By room >> Command: broadcast to living room, are surprised yet?
This is choosing an specific room that the google homes are. but in my case some rooms have multiples so for this I use the following

By Device >> Command: Broadcast to living room speaker, this is a TEST.
or even hubs using their name for example >> Command: Broadcast to Studio HUB, this is a TEST.
Notice that I use my specific device name so you need to use yours.

@ryancasler
Copy link
Contributor

Yes....did you look at the date that GAR was released? That was before this change from Google. The new version that is being worked on will have native support for specific broadcasts. But if you want to speed things along, you're more than welcome to take a look at the help request that Greg has and do a pull request with updates. Otherwise, be patient.

@Mightyinks
Copy link
Author

Yes....did you look at the date that GAR was released? That was before this change from Google. The new version that is being worked on will have native support for specific broadcasts. But if you want to speed things along, you're more than welcome to take a look at the help request that Greg has and do a pull request with updates. Otherwise, be patient.

I was trying to help those new ones that might not know that they can achieve this now without the need of any updates or anything. I don't need to be patient because there's nothing I need, it currently does everything perfectly 👍

@rezzalex
Copy link

Hello @ryancasler ,
it don't work for me on 3.2
it broadcast the message to ALL my devices :
image

Did I missed something ?

@Mightyinks
Copy link
Author

Mightyinks commented Jan 22, 2021 via email

@rezzalex
Copy link

rezzalex commented Jan 24, 2021 via email

@Mightyinks
Copy link
Author

Mightyinks commented Jan 24, 2021 via email

@ryancasler
Copy link
Contributor

Has nothing to do with GAR. This is a function of Google Assistant. What region/language are you located in? Room/device specific broadcasts have not rolled out to all regions/languages as of yet.

@Mightyinks
Copy link
Author

Mightyinks commented Jan 24, 2021 via email

@ryancasler
Copy link
Contributor

ryancasler commented Jan 25, 2021

Don't work for me, neither with the room name. It indeed broadcast the message to ALL available speakers saying "here is the message from "$USER", to "$room" or "$SPEAKER", "$Rest of the message" ". Are we on the same version ?

I just reread your message. You are passing the correct values to AR correct? So, if I want to broadcast a message to the device named "Office display" I have to send the command, with broadcast turned OFF (because using broadcast will force it to all your speakers). So, in the sandbox, it looks like this:
image

And if you're looking at the body of the request to send, the json should only contain your username and the command with all of the details in the command field.

Also, for some reason, mine has problems when the first word after the device name is "This". So, if i try to say "This is a test, I have to put this twice. That's because it think you are saying broadcast this message and not that "this" is part of the message. Stupid, I know, but how often does your message start with the word "This".

@Mightyinks
Copy link
Author

Mightyinks commented Jan 25, 2021 via email

@rezzalex
Copy link

version

On my side, all Google devices registered in France.

a Lenovo Smart Display with those firmwares :

  • system : 33.27.44.346118233
  • cast : 1.52.239754

A Google Home mini :

  • system : 229149
  • cast : 1.50.229149

@rezzalex
Copy link

Don't work for me, neither with the room name. It indeed broadcast the message to ALL available speakers saying "here is the message from "$USER", to "$room" or "$SPEAKER", "$Rest of the message" ". Are we on the same version ?

I just reread your message. You are passing the correct values to AR correct? So, if I want to broadcast a message to the device named "Office display" I have to send the command, with broadcast turned OFF (because using broadcast will force it to all your speakers). So, in the sandbox, it looks like this:
image

And if you're looking at the body of the request to send, the json should only contain your username and the command with all of the details in the command field.

Also, for some reason, mine has problems when the first word after the device name is "This". So, if i try to say "This is a test, I have to put this twice. That's because it think you are saying broadcast this message and not that "this" is part of the message. Stupid, I know, but how often does your message start with the word "This".

Almost what I did initially...., except I wrote "Broadcast to" instead of " Broadcast on", but... same result...

@rezzalex
Copy link

rezzalex commented Apr 13, 2021

Finally using v3.3.2b, and by replacing "Broadcast to" by ma configured language (french), it worked.

can be closed concerning me.
thanks a lot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants