Hi,
I have a growing Zigbee network that works reasonably well (Unsing HubZ smart controller and ZHA). Almost all of my devices are Third Reality smart plugs so they are all mains powered routers. I expect that in most ways this probably helps my reliability.
One thing I’ve noticed is that - and this is mostly the case with the dual plug Third Reality devices, not the single - they take forever to acquire neighbors in the Zigbee mesh. While doing this all data is available in HA and they are fully controllable. Also, they will go long stretches where the Configuration–>Firmware setting says “Unknown”. This is the case even though the Device Info has the firmware version. It seems almost as if ZHA doesn’t know what the current correct version is. Then, randomly, it seems to figure out the version and offer to upgrade. This could be minutes or days after I add the device (always same device typpes, new out of box with same starting fw version).
In the device Activity (Log) I see that the devices will periodically go unavailable for several seconds. This seems to coincide with the network mesh updating. When that happens I often see messages like this:
Master Bedroom Northeast Outlet (dual) Firmware became unknown
I’m trying to understand how the firmware updater in ZHA works without spending too much time in the code. I’m not sure if there’s a way to improve this. As I said, in all cases the device info displays the correct firmware version and if I go into Reconfigure>Manage Zigbee Device I can read the currrent_file_version from the OTA cluster and that comes back correct. It seems like an issue on the ZHA side knowing what the most current fw version should be.
Any tips on how to troubleshoot further or make this consistent would be greatly appreciated!