2022.3: Select and play media

thought Id give the most basic of my media_player configs a new try, and uncommented the Mpd config I stopped using because of the log spam issues it suffered before.

its nothing more than:

media_player:

  platform: mpd
  host: 192.168.1.177
  name: Bryston Bdp-1

and does create a media_player, but it remains ā€˜unavailableā€™ in the states. Before, we could see what it played, though no cover art was displayed.

No errors in the log, only a warning:

022-03-05 15:20:22 WARNING (MainThread) [homeassistant.components.media_player] Setup of media_player platform mpd is taking over 10 seconds.

but no ā€˜Setup of Mpd took xx secondsā€™ either.

Anyone else around with a working Mpd integration?

would have hoped that https://github.com/home-assistant/core/pull/67565 would make the player appear in the Media section, but unfortunately that doesnt happen eitherā€¦

I have a 1080p Chromecast and a GTV chromecast and have never been able to cast Lovelace dashboards, with the exception of casting a browser tab.

Is the option to cast Lovelace dashs exclusive to a Nabu Casa subscription?

Since this update one of my yamaha musiccast devices is getting disconnected and canā€™t get back in HA. Restart does not help. Removing the device and adding it right after brings it back to HA. Device is available in MusicCast mobile app without any issues, also additional sensors and switches that I have configure via REST integrations work ok. Only the official integration fails after a while (couple hours).
Restarting the yamaha device or unplugging it from power does not resolve the issue either.
Error in the log:

2022-03-04 15:14:13 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry 10.144.1.165 for yamaha_musiccast
Traceback (most recent call last):
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/aiomusiccast/pyamaha.py", line 248, in request_json
    response = await self.get(args[0])
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/aiomusiccast/pyamaha.py", line 268, in get
    return await self.client.get(uri.format(host=self.ip), headers=self._headers, timeout=ClientTimeout(total=5))
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/aiohttp/client.py", line 559, in _request
    await resp.start(conn)
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 898, in start
    message, payload = await protocol.read()  # type: ignore[union-attr]
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/aiohttp/streams.py", line 616, in read
    await self._waiter
aiohttp.client_exceptions.ClientOSError: [Errno 54] Connection reset by peer

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/homeassistant/config_entries.py", line 335, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/homeassistant/components/yamaha_musiccast/__init__.py", line 81, in async_setup_entry
    await coordinator.musiccast.device.enable_polling()
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/aiomusiccast/pyamaha.py", line 194, in enable_polling
    await self.request_json(System.get_device_info())
  File "/usr/local/share/homeassistant/lib/python3.9/site-packages/aiomusiccast/pyamaha.py", line 256, in request_json
    raise MusicCastConnectionException() from ce
aiomusiccast.exceptions.MusicCastConnectionException

nevermind the post above on MPDā€¦ I changed the config to use the .local address and there it showed immediately. Turns out the IP address wasnt correct anymore.

However this success leads to another question: when selecting a media_player in the bottom right corner, shouldnā€™t it only show the available media services in the panel? Right now, it simply shows them all? (well no Plex and Lovelace)

and my Bryston can only play music filesā€¦
moreover, I can not browse it in this panel, which is what is was supposed to do?

Hi all, I made some nice automations to press a button and play the music on the selected chrome casts. This worked like a charm for about a day, after the new update it doesnā€™t work anymore. Donā€™t know if it has to do with the update or not, just mentioning it. It triggers the automation, selects the speakers (you hear the bleeps) starts playing the music and after a few secondsā€¦ it stops again. Doesnā€™t matter what station.

In the logs, step details:

Result:
params:
  domain: media_player
  service: play_media
  service_data:
    media_content_id: media-source://radio_browser/c19d0f8c-24a5-11e9-a80b-52543be04c81
    media_content_type: audio/mpeg
    entity_id:
      - media_player.beneden
  target:
    entity_id:
      - media_player.beneden
running_script: false
limit: 10

code in the Lovelace:

show_name: true
show_icon: true
type: button
tap_action:
  action: call-service
  service: automation.trigger
  service_data: {}
  target:
    entity_id: automation.radio_kink
hold_action:
  action: more-info
icon: mdi:head-alert-outline
icon_height: 50px

Anyone an idea why it stops playing? Iā€™m lostā€¦

After upgrading to 2022.3 all my input_selects have a grey input box. I was able to change it back to the way I like it when the screen first comes up but after selecting to a different item in the dropdown the gray box reappears. Iā€™ve tried a number of variables but canā€™t find the right one.Thanks for your help.

type: vertical-stack
in_card: true
cards:
  - type: markdown
    style: |
      ha-card { margin-top: -.8em;
                margin-bottom: .5em; }
    content: >
      ## {{ states('sensor.todays_date') }}

  - type: entities
    style: |
      ha-card { margin-top: -2em;
                margin-bottom: .8em;
                background-color: white;
                --mdc-select-fill-color: white;
                }    

    show_header_toggle: false
    entities:
       - input_select.calendar_selection

I have found radio to be a little ā€˜flakyā€™ sometimes.

Is there any way/setting to get rid of the tip showing at the bottom of the settings page?
Currently showing links for joining the ha community.

1 Like

Set the theme variables, which have been posted more than once in this thread. Just scroll a little bit up or read top down. You will find them.

I donā€™t use themes, maybe I should

reinstalled complete HA with use of configiuration backup, now everything works againā€¦

After some fiddling around, this happens when you start streaming to a group (few google devices). After a few seconds it stops. When playing to a single entity (1 google device) it works. So it has something to do with the groupingā€¦ but what?

Edit: found this also: Google decided to just delete features instead of paying royalties to SONOS

So I guess we all need to change to Sonosā€¦

I donā€™t know the answer to that. I do have a nabu casa sub. Iā€™ll try disabling it and see.

The same feature was implemented in Automations:


The issue:

Again, I totally disagree with this changes.

7 Likes

I appreciate reading in the notes that the team is still focus on improving accessibility for screen reader users. I am one of those users and this level of attention is greatly appreciated. The platform is becoming much more accessible with each subsequent release and thus extremely enjoyable to use. It is rewarding that almost everything is now very accessible.

Great home automations equal excellent home accessibility for anyone with a disability, not just the convenience and comfort.

Thanks to all the devs!

3 Likes

Same here. I have two cameras setup as ā€˜Generic cameraā€™. They use WebRTC. Both are missing with message ā€œ2 incompatible items hiddenā€

1 Like

This morning I noticed that the issue is no more present (device or entity are created in the Samsung TV integration).
May be because i used the TV yesterday evening and then was on line for the integration ?

1 Like

Currently there is not.

there wont be, (a way to get rid of the Tips) at least not for the foreseeable time. Balloob has stated that rather clearly in the Beta period after several testers made the same remarkā€¦

give people something to complain about and they will indeed complain about it, no matter how minimal it is.

4 Likes