ok, I found it, Chromecast app added devices which I did not notice
“Message queuing“, jamming up broadcasts, is a known issue without a 100% full proof work around.
This device driver has been in beta almost as long as Star Citizen has been in alpha.
Sorry, I know this is kinda old but,
It's mostly working now but with some really weird problems. I have 5 devices and a 'Home group' device which is all of them together. I set the volume loud for each individual device, speak to home group, and then set the volume quiet for each. Here is a log:
dev:31272020-08-29 22:44:49.588 infoHome group volume is 45
dev:31282020-08-29 22:44:47.957 infoFront Bath Mini media source is None
dev:31262020-08-29 22:44:47.582 infoLiving Room display volume is 45
dev:31252020-08-29 22:44:47.438 infoKitchen Hub media source is None
dev:31282020-08-29 22:44:46.405 errorsu.litvak.chromecast.api.v2.ChromeCastException: Waiting for response timed out (parse)
dev:31252020-08-29 22:44:46.343 errorsu.litvak.chromecast.api.v2.ChromeCastException: Waiting for response timed out (parse)
dev:31232020-08-29 22:44:20.578 infoBedroom display media source is None
dev:31242020-08-29 22:44:20.573 infoMstr Bath display media source is None
dev:31272020-08-29 22:44:20.557 infoHome group media source is None
dev:31262020-08-29 22:44:20.552 infoLiving Room display media source is None
dev:31272020-08-29 22:44:20.153 infoHome group is idle
dev:31272020-08-29 22:44:18.807 infoHome group is playing
dev:31272020-08-29 22:44:18.285 infoHome group is buffering
dev:31272020-08-29 22:44:16.492 infoHome group media source is Hubitat
dev:31272020-08-29 22:44:16.487 infoHome group volume is 50
dev:31242020-08-29 22:44:16.454 infoMstr Bath display volume is 45
dev:31242020-08-29 22:44:16.395 infoMstr Bath display media source is Default Media Receiver
dev:31282020-08-29 22:44:16.365 infoFront Bath Mini media source is Default Media Receiver
dev:31232020-08-29 22:44:16.358 infoBedroom display media source is Default Media Receiver
dev:31262020-08-29 22:44:16.342 infoLiving Room display media source is Default Media Receiver
dev:31252020-08-29 22:44:16.244 infoKitchen Hub media source is Default Media Receiver
dev:31272020-08-29 22:44:16.082 infoHome group volume is 45
dev:31232020-08-29 22:44:16.078 infoBedroom display volume is 45
dev:31262020-08-29 22:44:15.368 infoLiving Room display volume is 70
dev:31242020-08-29 22:44:14.983 infoMstr Bath display volume is 70
dev:31232020-08-29 22:44:14.953 infoBedroom display volume is 70
dev:31272020-08-29 22:44:14.922 infoHome group volume is 70
The code's real simple:
setVolume(70) on Bedroom display, Mstr Bath display, Kitchen Hub, Living Room display, Home group, Front Bath Mini
setVolume(30) on Doorbell
speak(Text2Speak(The backdoor has been closed.)) on Home group, Doorbell
setVolume(45) on Bedroom display, Mstr Bath display, Kitchen Hub, Living Room display, Home group, Front Bath Mini, Doorbell
Whazzup??
Hi,
Notify pushover, sends the notification to (www.pushover.net) which is a 3rd party notification service which I use instead of the hubitat app. Speak sends the message to the chrome cast. I found that without the refresh, the chrome cast would occasionally not speak and then spit out loads of messages at once when it finally woke up.
I no longer use chrome cast as my speaker, I use a raspberry pi and have written a hubitat device driver to send the TTS url to the raspberry via MQTT.
It found my MVidia SHIELD but nothing else.
I did set statics for all of them though which might have helped.
Perhaps I'm missing something with the Chromecast Integration. Is is possible to get the status of a Chromecast when it is playing to get status to control lighting?
I believe so. My dashboard shows current status of my chromecast devices (I use Lenovo displays) and you can read the attributes from RM with the custom attribute option.
In case this helps anyone, I found that my display devices (Google Nest Hub and Lenovo Smart Display) along with my Google Home Max speaker, frequently get stuck queues. Clicking on the devices' device tab "Initialize" button empties the queue and they work again. My other google home speakers have this problem much more rarely.
I had issues with my groups disappearing. (Happened to look, and downdetector said google was having issues today and coincidentally a few days ago when they disappeared last time). Did not appear to affect the physical devices. Just the created groups of multiple devices.
Has anyone worked out how to send the off command to chromecast ? My tv can turn off with the off command ths connected chromecast via Google home. So I'm assuming I can do it through habitat as well?
Chromecast only finds my Nvidia Shield (connected to the 4K set) and none of my Samsung Smart TVs so I do not know how to handle TVs with it. Same for Logitech which only finds 1 of 3. The plasma HDTV still makes 4K look weak.
I have 2 4K and one plasma HDTV on my network but only the NVidia shield was found and it has 12 actuators. I would like to be able to access the TV it is connected to but can not yet. Anyhow, Initialize, Mute, Pause, Play, PlayTrack (with a parameter), Refresh, SetVolume (with a parameter), Speak (a text to audio function with a parameter for text input), Stop, Unmute, Volume Down and Volume Up are available if someone wants to start figuring out how to use one with Hubitat Elevation. Mine says the media source is "Plex".
Usually you use "Run Custom Action", "Run Custom Action", "Actuator" to get to any of those functions. I would say 95% of my rules are "Custom". You can then find the device and then the off command. I have done this a lot. I do not even know what most of the other useless options are.
yeah that's what i thought but i can't get it to work
there are no custom actions just the standard set
You can only stop the stream. You can't turn a TV off using the Chromecast device. You likely can do that using a driver for your TV, if one exists.
I have a Sharp TV and the driver on the forum here is pants (many errors). And using an RM3 IR device for TV on/off isn't reliable because the power toggles, so if you send a power command you need to be sure of the current state to make sure you are turning the TV off and not on! So my solution is quite weird....
First I stop the Chromecast stream using the custom action mentioned above. This stops whatever was playing (Netflix, YouTube etc). Then I issues a TTS to my tablet (which is running Fully Kiosk for my custom dashboard), which says "hey Google, TV off". My Google Nest Display which is next to the tablet hears this and turns the TV off. It's so funny to witness, but it works 100% every time ha ha ha.
I recently ran across this Chromecast and thought I would try it. I have a google clock. The driver found the clock. I tested it and was able to make it talk. Great. Created a test rule that was to run last night. It didn't work. So when I checked this morning my clock had changed IP address. Does the driver detect this? Or how do I tell the driver to find the clock again? I did go into my router and set a static IP, but still can't get Chromecast to refind.
Edit: Figured out how to rerun discovery, but I assume this won't happen automatically?
Now I'm really getting confused. Told my router to give the clock a permanent IP address. Reboot clock. Check IP of clock, not what I told it. Check router. Apparently clock has a different mac address. Redid. Everytime the clock reboots it comes up with a different mac address.
Does that make any sense? I can't quite figure out what is going on.
Download the Hubitat app
