I have a number of devices where I KNOW there are firmware updates, but they never show up in the HA updates.
Settings → System → Updates → The “check for update” circle arrow button… Just says “No updates found”. Clicking the triple-dot menu and “Show skipped updates” does NOT show them either…
Here’s two examples:
I’ve got a bunch of 3rd Reality Zigbee devices. All exactly the same model number. Several showed up for update two days ago. Another two showed up last night. I still have 4 that haven’t gotten the update… This seems to happen very frequently with the various Zigbee devices I have. They seem to show up in waves… not all at once. I don’t know why.
“The AirGradient integration provides an update entity that checks for firmware updates for your AirGradient device. To install the update, the device needs to be rebooted.”
Except… that’s not true for me. I have one on 3.3.8 and another on 3.4.1 and it looks like 3.6.0 is the latest ( Releases · airgradienthq/arduino · GitHub) … Why isn’t there an update for these devices?
But I’ve had this issue with other devices. I just manually went through and manually updated my Shelly devices one-by-one because they never ever showed up. I’ve got a z-wave device in similar situation. I dunno :- seems weird and it’s weirder still that I can’t just get all the updates through the “check for updates” button.
Is there a more reliable way to check for updates or force a device to check for updates?
Thanks!
[Edit] I just rebooted my HA… three of the four remaining Zigbee devices now are showing updates … why not the fourth? Probably show up tomorrow though… I really don’t get it. They are ALL exactly the same model of the same device. Why isn’t it just a simple DB lookup? I really don’t understand how these updates are working…
That is because companies that sell the devices are now doing a very slow rollout of firmware. Most likely because the coding involved is now AI generated and hardly a human gets to review it before it goes out the door. So they slow walk it out either based on the models or a number to test at a time. All companies seem to be doing it now. It will not be days, but more like many weeks to months if at all before everyone get the update. Even worst that they stop the rollout and move on to another version to fix what broke in the last version.
Yes if they are in the wild using the mfgr’s app, but if Z2M or HAsees a new rev available, it should just flag anything older.
My warning is only update one zigbee device at a time, because they get confused sometimes. I have one that is up to data, but Z2M doesn’t think so, so every time it updates I get a firmware update warning that won’t do anything. Happened when I pushed update on 4 at once.
I don’t know how HA handles updates, but I highly doubt that the reason why all the zigbee devices are getting updates in waves is because of slow rollout from upstream. I would think that HA would check update source then see that I’ve got the exact same updates for a ton of the same devices and flag all of them at once.
Also, that doesn’t explain at all why AirGradient has yet to post an update.
I’ve done a little poking to see if I can figure out what’s going on under-the-hood of HA, but I’m no where close to having a grasp on it. If anyone can point me at a few debug features such as:
How does HA know there’s an update? (eg: is it checking a known public list somewhere?)
How to manually run the update process in debug mode?
How do I find out how it selects items once it knows there’s an update?
Check your system log for any failures to connect to ‘home base’ to check current versions. If your system is so tighly locked up to remain local, reaching out to vendor land to check should raise warnings and timeouts in the system and network logs. Often the only time it does this is during device startup, unless there is a timing loop in the vendor software to check more often - each vendor doing what they think is best. Be sure your network is stable and working and then you don’t have timing issues where the devices come up earlier than the network and repeatedly time out. Each vendor controls how they make updates available, and your integration should allow for this. If not, you may have to use vendor supplied apps or tools outside of HomeAssistant to achieve this.
Is IPv6 working? Increasingly this is being used for these update purposes.
I appreciate the suggestions. I haven’t found anything in the logs yet.
As for Ipv6 - My primary network is only ipv4, but the IoT network and the Matter/Thread network is IPv6.
Also, I updated to 2026.2.0 today and the updates had a nifty surprise for me! The updates page is now displaying a “not installable updates” section which is listing all of the Air Gradients! Nifty! Doesn’t tell me /why/ they aren’t installable, but at least I know now that it is actually seeing them and it tells me what the firmware should be!
I don’t know why.
… why not the fourth? 