Trouble with Chromecast Audio different firmware versions

Hardware
1

I have one Chromecast Audio running firmware 1.27.96538 and one running 1.28.100555. According to the below link, 1.28 is a preview firmware, but neither Chromecast Audio is signed up for the preview program. See here: https://support.google.com/chromecast/answer/7124014?hl=en

The Chromecast Audio running 1.27.x is discovered just fine, but the one running 1.28 is not. Does anyone else have this issue?

Edit: I’m running HomeAssistant 0.56.2 in a Docker container, and both Chromecasts are on the same subnet.

2

I have the same issue with a Google Home running 1.28: https://github.com/home-assistant/home-assistant/issues/9965

3

Interesting. I also have a google home running the same firmware as you, and it also fails to load in HomeAssistant as a cast device. I didn’t mention it here for fear of confusing the thread into a google home thread. I’ve only had it about a month, and when I first tried to add it as a cast device it worked fine. Then it mysteriously stopped. Unfortunately, I can’t verify what the firmware was when it initially worked or if it had a subsequent firmware update.

4

I also got my Google Home recently, and had it working for a couple weeks only. But I have an nVidia Shield (I don’t know the firmware version for it, it’s not displayed the same was as a standard Chromecast/Home device), which is still working as a Cast device from hass.

5

It’s so strange that we seem to be the only two having trouble here. I’m really curious if anyone else on the preview Cast firmware 1.28.xx is having issues. I could try upgrading my working 1.27 Chromecast, but I don’t really want to lose my only working Chromecast Audio.

6

Wild guess, your nickname sounds french, is by any chance your Google Home set to french? Mine is. Maybe the combination of this specific firmware, in french, isn’t so common.

7

Nope. English in the USA.

8

Here goes my far-stretched theory.

9

Same issues here on HASS.IO version 0.57.2.

Chromecast Audio version : 1.27.96538
Chromecast Audio version : 1.28.100555
Chromecast TV version : 1.28.100555

All of them are somehow not visible anymore and i’ve got the idea since it from the latest Home Assistant update, but according to this topic it’s not Home Assistant but probably has to do with the update from Google.

Temporary I added the chromecasts on the following way, but in the past I had some issues with this

#  - platform: cast  

# Chromecast Slaapkamer 
  - platform: cast
    host: 192.168.1.31  
# Chromecast Audio Woonkamer  
  - platform: cast 
    host: 192.168.1.40
# Chromecast Audio Tuin  
  - platform: cast 
    host: 192.168.1.41
10

I just had an issue of a segfault which occurred while an automation was running for my chromecast audio. This happened once before while I was on 0.55. I am currently on 0.57.2 (just upgraded today). I was curious to see if there was a known issue when I came across this. I do not have any problems with 0.57.2 recognizing my chromecast audio however after digging deeper I noticed I am also on version 1.28.100555 and did not recall ever signing up for this preview but upon checking within the Home app I found that it was set to receive the preview software. I have now unchecked it but it makes me wonder if this is the reason for my sudden segfaults when sending tts or an audio file to the chromecast audio.

Nov 08 16:30:00 raspberrypi hass[12389]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: service_call_id=1971404368-128, domain=media_player, service=volume_set, service_data=volume_level=0.3, entity_id=media_player.chromecastaudio1>
Nov 08 16:30:00 raspberrypi hass[12389]: INFO:pychromecast.controllers:Receiver:Launching app CC1AD845
Nov 08 16:30:00 raspberrypi hass[12389]: INFO:pychromecast.controllers:Receiver:setting volume to 0.3
Nov 08 16:30:00 raspberrypi systemd[1]: home-assistant.service: Main process exited, code=killed, status=11/SEGV
Nov 08 16:30:00 raspberrypi systemd[1]: home-assistant.service: Unit entered failed state.
Nov 08 16:30:00 raspberrypi systemd[1]: home-assistant.service: Failed with result ‘signal’.

11

I’m pretty convinced it has to do with the 1.28 updated cast firmware considering both @kernald and I tried various older HA versions in Docker containers. Please comment on the github thread if you haven’t already. I’d love to get this fixed soon so I can use my cast devices.

12

Does it work for you when you configure them this way?

13

It’s working but all the groups what are configured in the Google Home app you can’t see them.
So use some groups from my mediaplayer for automation and they don’t work anymore offcourse

14

I’m not sure we’re facing the same issue, then. Not speaking of groups, I can’t even see my Google Home at all on Home Assistant anymore.

15

Damnit my last working Chromecast Audio just randomly updated itself to 1.28.xxx, and now it doesn’t show up in HomeAssistant. This is so frustrating because 1.28.xxx is supposed to be a preview firmware that you sign up for, and I never signed up. So annoying!

16

I think I have a Chromecast still in its box somewhere. I’ll make some tests with it - configure it in hass, check if it appears (I don’t know if I will be able to set it up without updating though, but I’ll try), and wait for it to disappear.

17

Looks like we should get a fix in the next release: https://github.com/home-assistant/home-assistant/pull/10728

Thanks everyone!

18

Everyone still having issues seeing as the merge was removed?

19

I still have the issue indeed.

20

Yes. With .59 my cast devices are discovered, but I can’t control them. With .59.2 they aren’t discovered.