home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.72k stars 30.45k forks source link

Wrong state chromecast device #71596

Closed erkr closed 2 years ago

erkr commented 2 years ago

The problem

I have a chromecast playing music casted via Spotify on a mobile. The chromecast entity in HA reports that the device is idle. This is not always the case. Unclear why, one time the state and media information are correct. Other moments it looks idle while it is in use.

What version of Home Assistant Core has the issue?

Core-2022.2.5.3

What was the last working version of Home Assistant Core?

Core-2022.4.X

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Google Cast

Link to integration documentation on our website

https://www.home-assistant.io/integrations/cast/

Diagnostics information

7DA859F9-14F6-4E51-AEBB-7F1008989257

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

cast documentation cast source (message by IssueLinks)

probot-home-assistant[bot] commented 2 years ago

Hey there @emontnemery, mind taking a look at this issue as it has been labeled with an integration (cast) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)

emontnemery commented 2 years ago

Something similar has been reported before, but for Netflix.

Which type of chromecast device does this happen for? When this happens, are you by any chance casting to a group of several cast devices instead to a single cast device? Does it matter how you start the casting (from the official Spotify Android App, from the web player, from Home Assistant, etc.)?

erkr commented 2 years ago

Hi I was in the mean time experimenting and succeeded to reproduce. I think the issue could indeed be Group related as I created a group for the first time yesterday and I didn't observe this behavior earlier. I have 3 chrome-casts in my setup: one audio and two videos gen 2. All used for music only and configured together in a group. I observed it in two scenarios:

Best Eric

erkr commented 2 years ago

Just verified on core 2022.6.6. This issue is not solved!! @emontnemery: please re-open. Using the new Music Assistant integratie made this state error very visible. The reproduce flow is very easy: