Been using the newer device firmware updater the past few days. It generally works well but a few observations/suggestions:
- Add a batch mode capability. I have several devices of the same model number type and with the current tool I can only do one at a time. It would be nice if you could select several target devices then the app goes off and does them one by one. It may take a long time to do several but at least you wouldn't have to wait at the screen to start the next one after the last one completes.
- I found a sensitivity to distance for OTA with one location but much less so with another. So not sure why but in my second location I have not needed to move Hubitat from its central location.
- Add a polling scheme at the end of the firmware update such that the device details page shows the new firmware revision. That might require a delay to ensure the firmware update trickles through but currently its a bit hit or miss when the revision gets properly updated in the device page and that will surely lead to unnecessary confusion.
- I didn't want to brick one of my devices but wondering if the App has the logic to deny updating if the firmware file is the wrong one. Zooz, for example, names a lot of the firmware files similarly so it is easy to select the wrong one. Hopefully the tool does this but if not that would be a good addition.
A nice improvement over the prior Copeland et al tool but still room for some improvement.
p.s. several hours later, 17 ZEN77s, 3 ZEN71s, 3 ZEN76s, 1 ZEN52, 5 ZEN32s and I am all updated. Batch mode or scheduler tool please....
I also eventually came across proximity issues with firmware updates like I saw at my other location.. I just put Hubitat on an extension cord and long LAN cable and moved it around close to the devices. Not sure why its an issue but it seems to correlate to multi-gang devices, where more than one Zooz product is in the same location/box. Wondering if there is some sort of IF stage corruption or sensitivity of the RF front end caused by co-channel interference. Maybe next update I'll power off the neighbor devices (would be nice if they had an air gap switch on front) and see via A/B test if that makes a difference to firmware update speed. If Zooz is reading this it would be an easy lab test to see if there is sensitivity degradation with colocation of devices. Test, don't guess.
