ZHA "update.*" firmware entity "Unknown" for multiple devices

[alpepi12]

The problem

I am using ZHA with my ZigBee devices, which all happen to be from IKEA. Up to and including core 2023.3.3, I was able to see if the firmware of my ZigBee devices were Up-to-date or not (Device > Configuration > 'update.*' entity). If the firmware was out of date, I was notified to perform the update. I have done this successfully in the last month when I bought some new IKEA devices.

Since core 2024.4, all update.* entitles now show as Unknown:

For this device above specifically, I expect to see "Up-to-date" as I updated this device less than a month ago in core 2023.3. The latest release was in December 2023 per: https://ww8.ikea.com/ikeahomesmart/releasenotes/releasenotes.html

My interpretation of this is that, because of the latest OTA changes, ZHA can no longer see what the latest IKEA firmware versions are. Therefore, it doesn't know if the installed firmware is up-to-date or not. I tried reading through the latest ZHA OTA changes but couldn't figure it out myself.

Any help is appreciated, thanks!

What version of Home Assistant Core has the issue?

2024.4

What was the last working version of Home Assistant Core?

2024.3.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zigbee Home Automation

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zha/

Diagnostics information

config_entry-zha-e5a22e8b92badca3dd4b93870bd033ba.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

My ZHA configuration.yaml that worked in 2023.3 and stopped working in 2024.4:

zha:
  zigpy_config:
    ota:
      ikea_provider: true # Auto update Trådfri devices

in 2024.4, I tried changing my configuration.yaml to:

zha:
  zigpy_config:
    ota:
      # Download the index over HTTPS
      z2m_remote_index: https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

but it didn't solve the issue. All update entities still say "Unknown".

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[HaraldGithub]

Same here with the same configuration for all my Aqara- and Silvercrest (LIDL)-devices. Last working version 2024.3.3 after Update to 2024.4.0 it stops working, also update "unknown" with 2024.4.1.

[xmow49]

Same, all my device are in unknown version since HA 2024.4

[Yoda-Soda]

Same here

[FedeL16]

same here not only for Ikea, but all aqara and others.

[erkr]

There has been a major makeover for OTA recently. Great job! From the related commits, it seems that the ZHA configuration options changed as well. Please update the ZHA documentation accordingly and explain how it works now. In the past, when enabled a provider, it would update automatically. How does it work now? Will we get update notifications? Do we have the option to skip updates for particular devices? Can updates still be applied automatically? ... The config as listed above is not documented AFIK:

zha:
  zigpy_config:
    ota:
      # Download the index over HTTPS
      z2m_remote_index: https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

[ggravlingen]

There has been a major makeover for OTA recently. Great job! From the related commits, it seems that the ZHA configuration options changed as well. Please update the ZHA documentation accordingly and explain how it works now. In the past, when enabled a provider, it would update automatically. How does it work now? Will we get update notifications? Do we have the option to skip updates for particular devices? Can updates still be applied automatically? ... The config as listed above is not documented AFIK:

zha:
  zigpy_config:
    ota:
      # Download the index over HTTPS
      z2m_remote_index: https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

I tried this and ended up getting a few devices with pending updates, in addition to the ones with unknown state:

[alpepi12]

@ggravlingen - Interesting that it works for one of your devices, and not the others.

I tried this and ended up getting a few devices with pending updates, in addition to the ones with unknown state:

Can you confirm if your "Portabel lampa" device is listed in the OTA master list referenced above? https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

Are your other devices listed in there as well? I think maybe only the devices listed in that repository will show up as available updates for ZHA OTA.

[ggravlingen]

@ggravlingen - Interesting that it works for one of your devices, and not the others.

I tried this and ended up getting a few devices with pending updates, in addition to the ones with unknown state:

Can you confirm if your "Portabel lampa" device is listed in the OTA master list referenced above? https://raw.githubusercontent.com/Koenkk/zigbee-OTA/master/index.json

Are your other devices listed in there as well? I think maybe only the devices listed in that repository will show up as available updates for ZHA OTA.

What you say make sense. The devices that were pending an update were all Hue and I haven't updated them in years as I haven't had them connected to a hue bridge. The rest of them are all IKEA and they should be updated.

I'm not sure how to match my device with the names in the list. The one in the screenshot is v1 of this:

[JackWent]

same issue here on SP 242 by innr - Firmware: 0x14033682 only started happening since upgrade to 2024.4

[vincenty79]

I'd like to add that it's the same for TRADFRI on/off switch

[bh56]

Same where. I have Aqara temperature, motion sensors and ThirdReality smartplugs. The firmware version was working before, but now not anymore for these.

[FedeL16]

same issue remains… with last version 2024.4.3

[3jam3]

If you delete a device and then add it, the correct display of the firmware version returns. Unfortunately, only until you reload the ZHA manually or because of a reboot (e.g., after an update).

[puddly]

This will be fixed in the upcoming beta. We don't keep track of the latest firmware version and changes need to be made to show when the latest version is installed.

[erkr]

@puddly Please update the OTA section of the official documentation as well: https://www.home-assistant.io/integrations/zha/

Both new settings and the new OTA behavior are not described. It can be only found scattered around in github issue / discussions

[FedeL16]

This will be fixed in the upcoming beta. We don't keep track of the latest firmware version and changes need to be made to show when the latest version is installed.

the problem Is not solved with 2024.4.4. I have always unknown state in firmware entities.

[HaraldGithub]

the problem Is not solved with 2024.4.4.

Of course it isn't, because they wrote: "...with the next beta...", that means with 2024.5*-beta/final release!!

[FedeL16]

the problem Is not solved with 2024.4.4.

Of course it isn't, because they wrote: "...with the next beta...", that means with 2024.5*-beta/final release!!

Of course… the issue Is not solved with 2024.5 I have always unknown state in firmware entities again. what beta will it be?

[bh56]

This appears to be working for me.

[HaraldGithub]

Most of them are working for me, but unfortunately not all:

[Yoda-Soda]

Nice things seem to be working again thank you