Working on a bug report (bogus overheat errors when internal temps approach the low end limit) that I filed on the Inovelli firmware github repo and EricM tells me it should be fixed in v3.04 and that he would like me to test it. Since I live in the frozen north, I want to try out this release for the Inovelli blue VZM31-SN, but it doesn't look like that's possible on Hubitat. My understanding is that zigbee firmware updates are stored on hubitat servers and that there is no functionality in the firmware updater app for zigbee. Is this correct? Possible workarounds?
That is correct. The only workaround would be to pair it to another controller that allows you to select this particular update (perhaps Z2M?) and then pair it back to Hubitat. For Zigbee devices, this isn't as bad as it might sound since -- as long as you don't delete the device from Hubitat first -- it will slide back into place.
Depending on Inovelli's confidence with the update, the other possibility would be for them to give it to Hubitat for upload to their servers, which would make it available for everyone (there are not separate beta vs. production firmware channels, for example).
3 Likes
It seems to me that we have a gap in Hubitat support for zigbee device firmware. To me this could potentially be solved by improving the existing device firmware updater to also encompass zigbee firmware upgrades. Those of us who use Hubitat and also interact with the developer/vendor communities could benefit greatly from an integrated solution here; ultimately to the ongoing benefit of the Hubitat platform itself.
I say this because at first glance, it looks like I'm going to have to bring up a competing platform (HA/Z2M) in order to continue to work with the Inovelli team towards improving their VZM31-SN firmware. Still need to take a look at the Hubitat Z2M bridge but not optimistic that it will help me solve this problem.
edit: still looking at this.... I may be able to bring up a native Z2M web interface that can provide OTA upgrade capabilities by adding "frontend: enabled:true" to the Z2M configuration.yaml file. So, thinking upgrade process is:
- Bring up Z2M on a different zigbee channel
- factory reset my switch but don't remove it from Hubitat
- pair to Z2M and upgrade firmware
- factory reset again then add back to Hubitat choosing "replace existing device"
2 Likes
Yes. This will work, and removes the overhead of managing z2m via HA. Also, the rest of your proposed workflow is on the mark.
2 Likes
