search

music-assistant / hass-music-assistant

Turn your Home Assistant instance into a jukebox, hassle free streaming of your favorite media to Home Assistant media players.
Apache License 2.0
1.2k stars 44 forks source link

Chromecast with Google TV (4K) devices are disabled by default #2516

Closed madbrain76 closed 2 days ago

madbrain76 commented 1 week ago

What version of Music Assistant has the issue?

2.0.7

What version of the Home Assistant Integration have you got installed?

2024.6.2

Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

The problem

When adding the Chromecast player provider, Chromecast with Google TV (4K) devices are found, but in disabled state

How to reproduce

  1. add Chromecast player provider
  2. open settings/player
  3. observe that the CCwGTV4K devices are disabled

image

Music Providers

N/A

Player Providers

Chromecast

Full log output

log.txt

Additional information

No response

What version of Home Assistant Core are your running

2024.6.3

What type of installation are you running?

Home Assistant OS

On what type of hardware are you running?

Windows

marcelveldt commented 1 week ago

Yes, that is by design as those are TV devices, we disable those by default

madbrain76 commented 1 week ago

I see. I would suggest documenting it, then. I looked there before filing this issue.

madbrain76 commented 1 week ago

BTW, the Chromecast Ultra (A/V casting stick) is enabled by default.

marcelveldt commented 1 week ago

BTW, the Chromecast Ultra (A/V casting stick) is enabled by default.

I think we should add that to the default disabled items as well, as that is also purely targeted to video, right ?

OzGav commented 1 week ago

I am not sure what their target is but I use one with MA. You don’t need to interact with it for playback to work and it is always on unlike a TV

madbrain76 commented 1 week ago

From my point of view, all the sticks prior to the Google TV present only one interface - the cast interface, which you can control only through apps over the network.

The Google TV series are a superset of that - they offer an additional on-screen local interface, which you can control with a remote.

Somewhat orthogonal is the fact that some of the sticks are audio-only (Chromecast audio) and others audio-video (all Chromecast video, Ultra, Google TV). In most cases, with any of the video sticks, the TV (and AVR if there is one) will be turned on automatically when audio or video playback starts. If the goal is to prevent the TVs from being turned on by default, then all the video sticks should be treated equally.

There are a few cases when the TV will not be turned on with video sticks : a) the TV is very old and doesn't support HDMI-CEC b) an AVR is in use, without a display attached ;) c) the TV is a projector, and intentionally doesn't support HDMI-CEC

Case c) applies to one of my setups, in the home theater. The AVR has to be manually turned on, and the input has to manually be set. But the projector can be left off, and audio will play fine. I just verified this yesterday. There is a way to automate this too with HA, but I won't bore you with the details.

The video sticks would know if they are attached to an HDMI-CEC device (receiver, TV) even if they are turned off - or if HDMI-CEC is completely disabled. - which would apply to cases a), b) and c). But this is very likely not exposed through the cast API.

OzGav commented 2 days ago

This is expected behaviour. The docs have been updated.