I like the chromecasts, including the audio version.
I don’t like the fact that out of the box they can only be managed via Google home, or a casting capable mobile app.
So as a starting point I needed to figure out a way of at least turning them off, ie stopping the stream to them.
So this is the setup im currently mucking about with.
I’ve got tasker, with the autocast plugin along with sharptools.
Tasker/autocast allows control of chromecast functions play pause stop (and more), at an individual device level.
Sharptools brings the st events into tasker.
So for now I’m testing mode changes sending stop to all my chromecasts.
Autocast also is capable of sending tts to the cast devices, which also works, through I don’t know how that effects an existing stream.
So if anyone else out there is messing with this setup, let’s share notes.
It took me an entire day of farting about to find and configure these bits to get this working, granted this was mostly learning curve with these three apps.
Chromecast is a media render, vs a media app server.
In any event, sure no reason the autocast commands and states couldn’t be wired to a virtual dth and then controlled via Alexa.
Forgot to mention that I have at one harmony chromecast activity wired via sharptools into tasker, but I’m looking for a lowest common denominator for chromecast control.
Yikes! That’s not saying much for other apps as I was just thinking I could do a much better job documenting some of the “pro” features! I’ve tried to self-document some features directly in the app and while I have some good examples on the SharpTools microsite, I’d like to find some time to better document the core app on there!
I gave away the TV in the bedroom, and replaced it with another. This one has two HDMI ports, as well as USB. So the Chromecast is plugged into it. Additionally, the TV has CEC capability.
So this coming weekend, I will start messing around with Chromecast and AutoCast. My first objective: have the bathtub-full detection be read by sharptools (this already is configured), and then have that fulfill a Tasker profile. When that profile is fulfilled, the associated Task will use Autocast to reach the bedroom TV. Hypothetically, whether the TV is on or off (standby) the Chromecast will a) fire it up, b) switch to the Chromecast input. Then, it could hypothetically utilize any number of options to alert the bedroom that the tub has filled. Don’t yet know whether I’ll use straight screen cast, TTS, play a short video (perhaps a waterfall? lol)…
But as I’m thinking this through, it also occurs to me that Alexa could tie into this. You can use Alexa with Hangouts to compose/send texts and emails. So I have added a contact called “Home Alerts”. Now when AutoNotifiction detects any incoming messages (such as a “bathtub full” flood alert from SmartThings), it should fulfill the above profile… but also, it could be used as an instant messaging system. Send a text to my own GV number from anywhere, be that from Alexa or out in the field, and it could say/display anything on any device, based on the contents of the notification.
EDIT: this was almost too easy. Didn’t even need sharptools. AutoNotification intercepts the “water leak sensor” notification sent by ST. From there, it AutoCasts to both the above-mentioned Chromecast and the Android Bravia. In both cases, the Cast will power up the tv if it’s not already on, switch the set to that input, and display the “tub is full” message.
I will eventually make the trigger a sharptools water leak event, just to make it even more reliable… but for the moment, it’s fine as-is.
I thought I read somewhere that autocast doesn’t work for chromecast audio groups. But I could be wrong. I tried this too and nothing plays to audio groups. I’m having issues playing on more than one chromecast audio with autocast. I use sharptools, tasker, and autocast to stop casting on a chromecast device, play TTS message to the device, stop casting again, move the next device to play the same message but nothing happens. The autocast app still stays stuck casting to the first device. It’s kind of clunky to do it this way. That’s why I wish audio groups were supported.
I haven’t had luck getting my chromecast DLNA renderers to show up in mediarenderer during the discovery. It only found 1 device and it was a regular chromecast that is on my TV. I have 2 audios and 1 home speaker (I don’t plan to use the regular CC’s in ST) but none of them show up.
Hopefully someone finds a workable solution to using google cast devices for TTS notifications, weather forecasts, and such, in ST.
I second that statement about integrating CC into the ST ecosystem for things like music and announcements. I ended up adding a Samsung R1 speaker for announcements and I don’t love it because of the delay time between a trigger event and the announcement.
I ended up using this for notifications to my Google Home devices. It involves setting up a node.js server in your network, installing a smartapp and a DTH. I got it to work by using my existing FreeBSD/FreeNAS 11 server (in standard jail), installed nodejs-legacy, npm, git, and followed the instructions to install the API.
When my mailbox sensor is tripped I get a notification on all my GH’s and also when my wife is arriving. Works surprisingly well. I use it with the Speaker Companion smartapp from the marketplace.