-
-
Notifications
You must be signed in to change notification settings - Fork 28.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZHA "update.*" firmware entity "Unknown" for multiple devices #115116
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
Same here with the same configuration for all my Aqara- and Silvercrest (LIDL)-devices. |
Same, all my device are in unknown version since HA 2024.4 |
Same here |
same here not only for Ikea, but all aqara and others. |
There has been a major makeover for OTA recently. Great job!
|
@ggravlingen - Interesting that it works for one of your devices, and not the others.
Can you confirm if your "Portabel lampa" device is listed in the OTA master list referenced above? 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: ![]() |
same issue remains… with last version 2024.4.3 |
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). |
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. |
@puddly Both new settings and the new OTA behavior are not described. It can be only found scattered around in github issue / discussions |
the problem Is not solved with 2024.4.4. I have always unknown state in firmware entities. |
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? |
Nice things seem to be working again thank you |
The very problem is the limited firmware available to the devices managed by ZHA and not in the latest version. |
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:
![image](https://private-user-images.githubusercontent.com/91648886/320282747-c5c61be0-1420-4e92-9837-0dda3ec177d0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3MTc2NDEsIm5iZiI6MTcxOTcxNzM0MSwicGF0aCI6Ii85MTY0ODg4Ni8zMjAyODI3NDctYzVjNjFiZTAtMTQyMC00ZTkyLTk4MzctMGRkYTNlYzE3N2QwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjMwVDAzMTU0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRlYmNjNTE5MWZlM2M5YzI0M2JmNjlmYTVjMmVmYjZjNzcwZTU3MDljZjMyNDM0OTViMzk0ZDlmOGFmYmY3YTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.GgP4Yz6NtWVjb45D1duxmw_JURtt6y7lSY_avhsu7o8)
![image](https://private-user-images.githubusercontent.com/91648886/320283369-4485c74e-f72a-4cc0-961a-83ef0cf183b8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3MTc2NDEsIm5iZiI6MTcxOTcxNzM0MSwicGF0aCI6Ii85MTY0ODg4Ni8zMjAyODMzNjktNDQ4NWM3NGUtZjcyYS00Y2MwLTk2MWEtODNlZjBjZjE4M2I4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MzAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjMwVDAzMTU0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI1NGI2YjQzY2ZiMjY0NWYzZWYzMGQ2YzkzZmRiY2JlOGUzZmI5NGEyMzdjMmExNTA4NjQ3OTg0YTA0NTlhMzUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.qA_h0jLLj-Ry-B5pdjZ14fFF-fMnQXih7gERFVEyfg0)
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:
in 2024.4, I tried changing my configuration.yaml to:
but it didn't solve the issue. All update entities still say "Unknown".
The text was updated successfully, but these errors were encountered: