SmartThings Community

[Release] [Closed] Google Assistant Relay V1 - Google Home Audio Notifications!

tts
requires_server
project_alerts
project_voice
googlehome
(Craig Bennett) #858

It sounds like they won’t

I found another method that uses the cast feature. https://www.youtube.com/watch?v=WYdvZVI7KFA

If you follow the instructions in the first link, it will tell you how to make your Google Home devices into speakers. There is a smartapps on the app which has a few sounds already in it, and it has a TTS function. I’m using the method in the video so I can take any MP3 I made and have it play through the speakers. When I get time, I will try to get the thing to work with WebCore instead of IFTTT to quicken things up.

BTW one thing I didn’t put in the video. I’m using the app I was referencing above to tell me the weather in the morning. Basically, when a given motion sensor finds me walking around first in the morning, it will play the weather in any Google Home device I want. I have it where it plays only1 time.

Basically I have a virtual switch which can be triggered on by giving motion sensors during x and y time. This has to happen from an off state (otherwise it will keep playing the weather).
Then when the time gets to y, the system automatically makes the switch off so it’s ready for tomorrow.
So what triggers the sound is the switch going into an on state.

1 Like
(Greg) #859

Fix is coming soon

Hi guys, we’re actively working on a fix to re-enable this. ETA is Friday next week (sorry, the rollout takes a bit of time).

Thanks for the suggestions, endoplasmic@. We definitely want to support them, and even more delightful features. (Wish I can reveal more details, but not sure if legal team would like it).

4 Likes
(Sean Donaghey) #860

It would be nice that when they re-enable the broadcast feature, they allow for directed broadcasts, so that this privacy issue doesn’t happen. I would like to be able to just send for example door open broadcasts to the mini in the living room and not to every GH device on my network. Especially since I have one in the bedroom and wouldn’t want it broadcasting to the bedroom in the middle of the night when I come home and the wife is asleep.

(Eddy) #861

On a different note, @ghesp, do you happen to know if /commands work?

(Brennan) #862

Thanks for keeping us update on this and too, not simply abandoning the project!!

1 Like
#863

Almost Friday! Hope this thing is still on track at Google!

1 Like
[RELEASE] cast-web 1.1.0 - Chromecast Device Handler & SmartApps
#864

I really hope so too :grinning:

(Eric) #865

Ready for Friday!:+1:

#866

Unfortunately, it’s been pushed back to next Friday :confused:

amdoh commented 7 hours ago
Hi guys, I just want to give a quick update. The fix was submitted, and unfortunately we had to roll it back later since it caused other issues. New ETA is next Friday. Sorry for the inconveniences!

1 Like
(Mark C) #867

greg, im trying to understand what is the differance between this thred and this one, could you help explain, thanks

(Alwas) #868

If you want full control of each of your Chromecast devices cast-web is way better, it doesn’t even compare, this one just seems to be a hack.

#869

This one is the best for broadcast notifications. It exactly mimics what google does when you use the “broadcast” command either verberally or via the app. It also allows you to send practically any command that follows ok google via text.

The other apps convert your Google home devices into smart “things”, allowing you to do whatever you want with speakers on the smart thing ecosystem. Including making them speak.

It really depends on your usecase, to decide one over the other. Biggest advantage with this method here - no interruptions to what ever is already playing on your device - music, news, podcast whatever. It is of course limited by what ever google allows you to do, since it really depends on Google’s own broadcast API at the core level. Therefore, no fine tuned control (yet), so cannot do things like broadcast to a single speaker.

And people who thing this is a “hack” just need to spend some time reading more about the underlying tech for each! Although, it can be argued that everything is a hack when it comes to smart things custom device handlers since it’s all coded by (smart) third party developers/enthusiasts.

1 Like
(Greg) #870

The cast handlers are essentially casting content to your Chromecast in the same way your phone will. It will interrupt whatever it is doing and has no state.

This uses the Google Assistant SDK so you can interact directly with the Assistant from SmartThings. The main functionality this has at the moment is to use the broadcast functionality for voice notifications (when Google fix it on Friday)

It’ll resume state, so if you have music playing on your Google Home, you can broadcast an TTS notification which will fade the volume of the music, play the audio notification and then continue playing the music (or whatever it was doing). Something the cast functionality cannot do

1 Like
(Alwas) #871

With the greatest respect Greg, I think you haven’t used cast-web. I’m listening to Radio 5 Live on 4 Chromecasts, I had a TTS notification come through, then Radio 5 Live resumed again.

(Mark C) #872

this is why i asked the question as im finding the cast api a bit buggy, im having to restat the node/js, device showing playing when there not or there even off

#873

That only works if Cast-Web was what you used to start the content in the first place. Today I was casting to my kitchen speaker from my phone because all my podcasts are synced across multiple devices. A voice notification came through and my podcast did not resume. Personally, I have both Cast-web and Assistant relay set up. Both work simultaneously without a problem. I use cast web to play audio (sound) notifications or control the volume and i use assistant relay for spoken voice notifications. Why can’t we use both for what each does better. :smiley:

3 Likes
(Dana ) #874

Greg:

Thanks for tracking the issue and the updates, really appreciated.

Do you know if the fix from Google will just re-enable TTS automagically, or if we’re going to need to update something to pick up the change?

Thanks.

#875

They’re supposed to rollout a fix in the backend so theoretically, if you never closed the script it should start working again this Friday.

Restarting the script might be needed at some point tho.

As for cast-web, while it’s different from AssRelay, I personally prefer the latter. It’s more robust and more useful for my needs.

1 Like
(DJAC) #876

hopefully there won’t be a delay between Ghs…

Has anyone else noticed that GH is less responsive. Sometimes not answering me all.

1 Like
(Greg) #877

As @kebel871 said, it should be a backend change at Google so it should magically start working again :slight_smile: