Using my sensor.all_my_speakers, sensor.kitchen_speakers, and sensor.main_speakers template sensors, defined above, this is pretty easy (see group_volumes.yaml): - id: track_volume_group_offĮntity_id: sensor.all_my_speakers, sensor.kitchen_speakers, sensor.
I need an automation that will update my trackers (i.e., input_number.) for the group volumes when they are NOT playing by averaging the volumes of their members, excluding the Kitchen Home. Update the group volume trackers when a group is playing service: python_a_sync_chromecast_volumesĢc. What is possible - can stream audio from your mobile using cast screen/audio option - can steam audio files in your device using players that support. Note that for the groups, the value of the sensor is the average of its members, excluding the Google Home. I also defined sensors to display these volumes, with the icon indicating whether the device is currently playing. To do this, I defined an input_number for each Chromecast, including the groups: input_number: Make sure you save your settings by pressing the Enter key on the save button. Locate the Audio CD section and change this to VLC Media player and the one underneath it called enhanced audio CD as well.
In order to get around this, I’ll need to track the volume of both the individual speakers and the Chromecast Audio groups. If you set the DVD movie to VLC Media player, when you put in a DVD it will come up in VLC Media Player. The challenge in all of this is that Home Assistant only knows the (average) volume of the group, not the volumes of the group members. In Home Assistant, I created a group for each Chromecast Audio group, as follows: all_my_speakers: I also use that Python script to set the volume of my Google Home when group playback stops. The Python script is set_chromecast_volumes.py and the automation is set_chromecast_volumes_hourly.yaml. It’s worth mentioning that I have a Python script that I use to set the Chromecast volumes each hour, as well as an automation that calls it.
The three devices that are commented out – “All My Speakers,” “Kitchen Speakers,” and “Main Speakers” – are cast groups that don’t have an IP address, and so they must be automatically discovered by Home Assistant. Host: !secret living_room_speakers_ip_address Host: !secret computer_speakers_ip_address Host: !secret bedroom_speakers_ip_address Setupįor starters, here are the Chromecast Audio devices that I include in my setup: media_player: So I set out to use Home Assistant to ensure that when casting to a group, all speakers remain at the same volume.
Unfortunately, the volume levels can get out of sync due to How to Stream from VLC Media Player in Macbook to Chromecast Devices. Group playback is awesome… when all my speakers are playing at the same volume.
It seems stocks of the gadget are rapidly diminishing: Like the Google Store, Staples is also listing the dongle as out of stock, although Newegg is still offering it through a third-party seller for US$29 at the time of writing.I have 3 Chromecast Audio devices, plus a Google Home and a Google Home Mini. However, the time has come for the Chromecast Audio to take a final bow. The Google dongle attempted to attract music-lovers and audiophiles with its support for 96 KHz/24-bit lossless audio playback. The obvious difference between the Chromecast Audio and a regular Chromecast was that the former came with a 3.5 mm jack/mini-TOSLINK socket instead of an HDMI plug. Google introduced Chromecast Audio in 2015 as part of its Chromecast range of media players. Support for the gadget will be continued, though. audio equipment and media players have started to integrate Chromecast.
In a statement to Android Police, the company has confirmed that the device has been discontinued and no more of them will be manufactured. Expand the Advanced Tab ) Select Print and Scan ) Select Print Jobs Using a. If you have been debating over the decision to buy a Chromecast Audio dongle lately, you might want to hurry up and make a purchase.