2022.3: Select and play media

Amazing update! I really like the media capabilities. However, my local mp3 won’t play on my cast devices any longer: the Call Service: Play Media of a doorbell.mp3 onto my Cast devices now renders this error. The Cast device wakes up, but the mp3 is inaccessible all of a sudden. Any ideas where to look?

Logger: homeassistant.components.cast.media_player
Source: components/cast/media_player.py:387
Integration: Google Cast ([documentation](https://www.home-assistant.io/integrations/cast), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+cast%22))
First occurred: March 7, 2022, 18:05:38 (29 occurrences)
Last logged: 22:18:41

* Failed to cast media http://192.168.1.30:8123/local/house-bell.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI5ODBlZThjYTQ1Y2U0M2UwYWY3NWNjMmUxODhmMmJkNiIsInBhdGgiOiIvbG9jYWwvaG91c2UtYmVsbC5tcDMiLCJpYXQiOjE2NDY3NzQwMzUsImV4cCI6MTY0Njg2MDQzNX0.g7KYspiikJLqoYrGmFWRugjnuDEYB3OvabGEb0iRq8Y from internal_url (http://192.168.1.30:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
* Failed to cast media http://192.168.1.30:8123/local/house-bell.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI5ODBlZThjYTQ1Y2U0M2UwYWY3NWNjMmUxODhmMmJkNiIsInBhdGgiOiIvbG9jYWwvaG91c2UtYmVsbC5tcDMiLCJpYXQiOjE2NDY3NzQwMzIsImV4cCI6MTY0Njg2MDQzMn0.8EErvj4CBsWR6LM20boZCBJ-BWK-XyMZzKu2FCWGWVQ from internal_url (http://192.168.1.30:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
* Failed to cast media http://192.168.1.30:8123/media/local/house-bell.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI5ODBlZThjYTQ1Y2U0M2UwYWY3NWNjMmUxODhmMmJkNiIsInBhdGgiOiIvbWVkaWEvbG9jYWwvaG91c2UtYmVsbC5tcDMiLCJpYXQiOjE2NDY3NzQxNTUsImV4cCI6MTY0Njg2MDU1NX0.KRKsnmA0JZNgM0zj-kTx5nzdTVhna7CkKFVOyrR-gyE from internal_url (http://192.168.1.30:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
* Failed to cast media http://192.168.1.30:8123/media/local/house-bell.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI5ODBlZThjYTQ1Y2U0M2UwYWY3NWNjMmUxODhmMmJkNiIsInBhdGgiOiIvbWVkaWEvbG9jYWwvaG91c2UtYmVsbC5tcDMiLCJpYXQiOjE2NDY3NzQxOTQsImV4cCI6MTY0Njg2MDU5NH0.XHu7TAcKP0FW6xX36j8DPlxLHoV-k4P91GsrZBsHWcw from internal_url (http://192.168.1.30:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address
* Failed to cast media http://192.168.1.30:8123/media/local/house-bell.mp3?authSig=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI5ODBlZThjYTQ1Y2U0M2UwYWY3NWNjMmUxODhmMmJkNiIsInBhdGgiOiIvbWVkaWEvbG9jYWwvaG91c2UtYmVsbC5tcDMiLCJpYXQiOjE2NDY3NzQzMjAsImV4cCI6MTY0Njg2MDcyMH0.4zNZd_udR-2A3dpBGUS7stOQimMAOnxg_Rig39iPtYM from internal_url (http://192.168.1.30:8123). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address

**Edit: I fixed it!
Apparently the Internal URL in General Settings changed, for some reason. I haven’t touched it in over a year, but it got jinxed somehow.

Yes it is, but mine shuts off when I move to another view. Would be nice to be able to make it persistent.

1 Like

I am running into the same issue, all my ZHA devices seems not triggering events so many automation stop functioning…

My setup is a Pi3, Home Assistant OS 5.13, using the nortek z-wave+ZHA USB adapter.


Tuya climate still not working since 2.9.
Last working core is 2.7

It’s nice to have the “select and play media”, that implements the open source https://www.radio-browser.info/
What I miss, are services. Not everybody uses an automation. I try not to use them at all.
I’m using pyscript.
So, I miss services like "get the url of “radio X” in “BE” . So, I can lookup the data myself, to use as parameters for the media_player.play_media

Also, if you select a country in “select and play media”, and there are a lot of “radios”, HA freezes.

1 Like

Nice pic and welcome aboard, but neither 2.7 nor 2.9 are versions. Please see here, and follow the advice there.

1 Like

I have it already enabled under configuration.yaml but no luck, any other idea?

Just upgraded to 2022.3.3 and my system does not reports the correct versions and wants to upgrade to 2022.3.2. Interesting…

The update is for supervisor :blush:

1 Like

Thanks for your help! didn’t notice it was only the supervisor :sweat_smile:

1 Like

just noticed the top corners of the input_selects (border-top-left-radius/border-top-right-radius) in eg logbook use a 4px border -radius, while the bottom ones (border-bottom-left-radius/border-bottom-right-radius …) use 0px.

the 4px looks odd in my 0px frontend, so just letting you know that setting:

mdc-shape-small: 0px

in the theme fixes that.

with

# set colors on quickbar
    mdc-text-field-fill-color: var(--card-background-color) # quickbar header
    mdc-text-field-ink-color: var(--primary-text-color) #var(--mdc-theme-primary)
# set colors on input_select
    mdc-select-ink-color: var(--primary-text-color)
    mdc-select-fill-color: var(--card-background-color)
# set top corners of input_selects in logbook
    mdc-shape-small: 0px

I have my themes corrected (…) though I admit not using all other theme options that might be off in the new frontend.

in my case stream component is enabled

I was able to get music to play on roku, but not a video from a camera stream. This is a great feature, let me know if I can help.

Getting a failure on the upgrade from core-2022.3.2 to core-2022.3.3:

22-03-09 20:25:22 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2022.3.3
22-03-09 20:25:22 INFO (SyncWorker_2) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.2 to ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.3
22-03-09 20:25:22 INFO (SyncWorker_2) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/raspberrypi4-64-homeassistant with tag 2022.3.3.
22-03-09 20:25:42 ERROR (MainThread) [supervisor.jobs] Unhandled exception: 
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 106, in wrapper
    return await self._method(*args, **kwargs)
  File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 229, in update
    await _update(version)
  File "/usr/src/supervisor/supervisor/homeassistant/core.py", line 207, in _update
    await self.instance.update(
  File "/usr/src/supervisor/supervisor/utils/__init__.py", line 33, in wrap_api
    return await method(api, *args, **kwargs)
asyncio.exceptions.TimeoutError
22-03-09 20:25:42 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.168.17.115:443: i/o timeout"
1 Like

That appears to be one of amazon’s hosts. Possibly a momentary glitch.

Same here. I was having some other issues simultaneously, so thought it was a “me” issue.

There are some additional errors in the supervisor:

22-03-09 19:46:59 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.168.17.115:443: i/o timeout"
22-03-09 19:47:19 ERROR (MainThread) [supervisor.resolution.check] Error during processing IssueType.TRUST: 
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-03-09 19:47:19 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-03-09 19:47:29 ERROR (MainThread) [supervisor.utils.codenotary] Timeout while processing CodeNotary
22-03-09 19:47:39 WARNING (MainThread) [supervisor.utils.codenotary] rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 35.168.17.115:443: i/o timeout"

The same here from 2022.02.09 to 2022.03.03.
It seems the supervisor-2022.03.2 has a problem. Before updated to supervisor-2022.03.2 it was possible for me to update to 2022.03.03 but I had to restore 2022.02.09 due to a issue with the Netatmo integration which doesn’t work for me with 2022.03.03.
Unfortunately I updated the supervisor meanwhile and since that I am not able to update :frowning:

Anyway, there is a issue opened: Cann't update from 2022.3.1 to 2022.3.3 · Issue #67930 · home-assistant/core · GitHub

Is it just me or has the UI link to config/energy/dashboard gone AWOL?

It’s here now: config/dashboards/energy

Ah, thanks. I was trying to find it under Configuration, not Dashboards.

I managed to get to it for my post via…
image