2022.3: Select and play media

Blog
292

image

Both my HA OS as on Docker are showing this!

293

So read the release notes!

294

From the Breaking Changes section of the release notes:

Updater

The Updater integration has been deprecated; other integrations have replaced all its functionality. It is no longer a part of default_config, and if you have the updater integration defined directly in your YAML configuration, please remove it.

  • For the binary_sensor.updater entity, you can set up the Version integration with the “Home Assistant Website” source to get the same functionality back.
  • The configuration options reporting and include_used_components for the updater: configuration entry was deprecated in 2021.4. If you still want to share that, please use the new Analytics integration.
1 Like
295

Oops missed that one. Thanks and Sorry.

1 Like
296

Nabu Casa? Had it too, untill I changed my external link to also be my internal link. Everything works back as normal again.

297

I no longer have a media browser. It was here in 2022.2.9 but since 2022.3.0 (now 2022.3.2) it is gone.

I did the radio_browser integration installation and it doesn’t publish any device/entities.
image
Is it linked? Is it 2 different issues?

In my media card, like Sonos, I’ve the message “Text to speech has moved to the media browser.” but, as said before, I don’t have any media browser, nowhere, please help!

298

I had the same issue. The camera and sensor stop working for IP Cam Android integration. Is this a bug or a breaking change?

299

Since version 2022.3.1 ZHA/ZigBee (stick) no longer works:

Config entry ‘TI CC2531 USB CDC, s/n: __0X00124B001CD492BA - Texas Instruments’ for zha integration not ready yet; Retrying in background

12:58:26 AM – (WARNING) config_entries.py

Couldn’t start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator

12:58:26 AM – (ERROR) Zigbee Home Automation

And no, version 2022.3.2 has not changed anything. Still does not work.

As you can read here, several people have this problem: https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+zha%22

Almost every major new version is the same!
Something that has worked for months or years suddenly doesn’t work anymore.
It totally sucks!

300

This is a complex project integrating thousands of disconnected different things to all work together. And — it’s free!

If you want something that just works and requires nothing from you except money, you should consider getting a contractor to install a proprietary whole-home system. Of course, it may have problems too — but at least in that case you’ll be justified in complaining.

Your bug report barely has any useful information. Something like that is very unlikely to let people who want to help do anything — but worse, ranting that it “sucks” doesn’t help anyone want to help you.

1 Like
301

While the software (HA) is indeed free, many people have put together IoT-devices based on supposed compatibility with the software and have sometimes spend a significant amount of money for those devices. Thus their anger is understandable if some of the devices which used to work before seemingly break with HA-updates which is certainly happening since some time with HA’s monthly updates.

You don’t wait to shut the stable door after the horse has bolted…

Agreed.

I believe most of us consider those angry statements as a way of just venting their anger thus people wont pick it up anyway.

Me personally have stopped jumping onto each and every update as soon as one gets released but rather wait for their maturation and until the integrations, cards etc. used have been adapted. Avoids a lot of anger :innocent:

4 Likes
302

I am not sure what integrations you are specifically referring to, but there are many that stop working due to manufacturers ceasing support and/or developers of the underlying libraries ceasing support.

Often people make bad buying choices, (which may only be apparent in hindsight), and then it is suddenly HA’s fault.

303

I am not specifically referring to a definite integration.

1 Like
304

But you must have been thinking about some specific examples. If you think there is a reson why someone should be angry about something, be specific.

305

No need to try to put something into my mouth. And I never used the wording “should be angry” rather than trying to paint a picture why i.e. @andbpow might be that angry.

1 Like
306

OK so first, can stream has moved to mjpeg integration, install and bring cam stream in that way, sensors should still work with the latest update 2022.3. 2

1 Like
307

anyone else experiencing the Google Assistant feedback acknowledgment to be cut-off too? Never had that before, but in seemingly random situations the regular feedback is suddenly cut-off, sometimes even as short as: “ok…”.

or would this be a GA thing.

308

I tried the new “Play Media” of version 2022.3

I want to display the camera on my frontdoor on my Nest hub when presence is detected.

So I did this :

trigger:
  - platform: state
    entity_id: binary_sensor.motion_sensor_voordeur_occupancy
    to: 'on'
    from: 'off'
    for:
      hours: 0
      minutes: 0
      seconds: 1
condition:
  - condition: state
    entity_id: input_boolean.toggle_op_vakantie
    state: 'off'
action:
  - service: media_player.play_media
    target:
      entity_id: media_player.nest_hub_living
    data:
      media_content_id: media-source://camera/camera.fi9900ep_voordeur
      media_content_type: application/vnd.apple.mpegurl
    metadata:
      title: FI9900EP_Voordeur
      thumbnail: /api/camera_proxy/camera.fi9900ep_voordeur
      media_class: video
      children_media_class: null
      navigateIds:
        - {}
        - media_content_type: app
          media_content_id: media-source://camera
mode: single

I’ve noticed my camera is 25 seconds behind, so the person is already on my door but I cann’t see him on my Nest hub…

The picture in the HA app is only 3 seconds behind :

type: picture-glance
entities: []
camera_image: camera.fi9900ep_voordeur
tap_action:
  action: none
hold_action:
  action: none
camera_view: live

Is there a solution for this ?

309

Cant install 2022.3.2 on my RPi4

22-03-07 10:20:32 ERROR (SyncWorker_7) [supervisor.docker.interface] Can't install ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.2: 404 Client Error for http+docker://localhost/v1.41/images/ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.2/json: Not Found ("no such image: ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.2: No such image: ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2022.3.2")
22-03-07 10:20:32 WARNING (MainThread) [supervisor.homeassistant.core] Updating Home Assistant image failed

Can this happen when to many people try to install it on same time?

310

A typical reaction that makes it quite clear where the problem lies.If I were to react the same way as you, I would now say that if you don’t like people reporting that something doesn’t work, then just shut up. Your reaction is just embarrassing and arrogant. I have not asked for anything! It simply striking when such massive problems always occur and how people like you react to it. Is not my problem that you can not do much with the shared information. That is not the only bin where the problem occurs, shows the link.

1 Like
311

No I can’t see anyone else with this problem. Can you either point to the issue, of post your own?