2022.3: Select and play media

A 404 error typically indicates the disk is full

Later the say tried it again and now it updated :slight_smile:

Just updated to 2022.3.2 and I canā€™t edit lovelace cards anymore. Wanted to add some entities, but that doesnā€™t work. I can search, but not select.

Edit: just added a complete card via devices, that goes fine, and after that I can delete some items from that card and save. But seems to be be possible to edit an existing card.

Edit2: Seems to be an issue when you select an entity with the mouse, then the hits disappear. When I start selecting with the cursor, it goes fine. Tested with different browsers.

Did the update kill old browser support? Like Safari for ios 9.3.6?
Slow, but It was working before this update, and I was using only for simple switching my devices.
Specifically, I type user/pass on the login screen but whatever I do, it gives Invalid username or password. Was the way to accept passwords changed? I need to double type a character to have the black dot appear in the password field. Well this is a iPad3 device and ios is so old. so I canā€™t ask much though.

Since the last updates, ZHA does not work at all or totally unreliable for many. So you are not the only one who has massive problems with it.

2 Likes

I have zero problems with ZHA and the updates, but I have just about 5 zigbee devices.

Is it possible to play media/radio on the Amazon Media Player component i.e. on the echo dot? I cannot see an option to play it on my echo dot. Anyone has the same issue?

1 Like

For the record, this happens when you are ā€œin a choose optionā€.

Just upgrade from 2022.2 to 2022.3 and got the following errors in the log:

[homeassistant.components.websocket_api.http.connection] [140424280409088] Error handling message: extra keys not allowed @ data[ā€˜modeā€™]. Got ā€˜storageā€™

Any hints to troubleshoot it?

find a service call in your configuration where you provide the word storage, when you need mode.

l.e. look for

storage: ...

somewhere in your configuration. Find out what service it is that youā€™re using. Then look at the docs for that service and update it accordingly.

1 Like

Hey, any idea how to get the nifty release notes and direct link to the blog entry back with the new version integration?
This was a great little detail with the updater, which now seems to be gone.

Thanks

Removed as it seems not fixed.

I am using a ā€œweblinkā€ with the following URL:
https://rc.home-assistant.io/latest-release-notes/
This link automatically redirects you to the latest release notes page.

1 Like

I just got around to reviewing all the changes, additions that version 2022.3.x has to offer. Iā€™m thrilled, amazed, pleased and thankful about the hard work and dedication shown by those contributing to Home Assistant.

SUCH AMAZING WORK AND EFFORT - THANK YOU

4 Likes

The Version integration exposes 2 sensors.

  • The update binary_sensor which does not have additional attributes
  • The version sensor which does have some additional attributes among which a link to the release notes. Not sure if it is the exact same set as the old updater sensor, but it works for me.

Personally I put both sensors in 1 row with the multiple-entity-row so it looks a bit neater (click the number for the attributes)

image

      - entity: sensor.home_assistant_core_version
        type: custom:multiple-entity-row
        name: Home Assistant Core
        entities:
          - entity: binary_sensor.home_assistant_core_update_available
            name: false

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