To expand on what @scottgu3 said, I believe Zooz devices are intentionally factory reset when the firmware is updated (@agnes.zooz - correct me if I'm incorrect on this).
Failure to exclude an updated z-wave device before re-pairing it to the controller can create a stranded z-wave device. The nightly hub clean-up is supposed to remove such devices, but did not do so for my HE, with the negative consequences that I have detailed earlier in this thread.
This is recommended best practice for all Z-Wave devices actually. Depending on what's contained in the update and how much it affects the initial association to the hub, a given device may not behave correctly after the update so that's why we recommend a reset after any update. That being said, we have many users who were able to update their devices without the need to reset or exclude them from the hub if the update contained just a few minor changes in the advanced settings for example.
Thanks for the clarification!
More specifically in the case of zooz.. I have noticed some firmwares add z-wave classes .. and as such the device has a different NIF
Has anyone been able to successfully to update the Inovelli LED MCU, the one that has target 1 with this driver?
Yep! You'll need the new "binary" driver shared above rather than the original, but I did two of my LZW31-SNs this way.
When I use the Z-Wave Firmware Updater on my Inovelli LZW31-SN, it seems to work properly. When I asked for the version, it returns 1.47.
But when I set it back to the Inovelli driver, it says 1.35. Any idea why ?
Try removing, factory reset, rejoin, configure? Pretty sure it pulls that info during pairing.
You might try just hitting the 'configure' button or 'refresh', perhaps it's cached info...before remove/reset/rejoin/configure. Worth a shot anyway.
S.
Clicking the configure worked. Thanks
Excellent news. I think as a matter of general policy, it's a good idea to hit "configure" after changing a driver. In this case, even though you went from the Inovelli Driver to the Firmware driver, and back to the Inovelli driver, it doesn't hurt run configure, just to make sure everything is synched up. Refresh might do it as well since you are still using the same device, but I couldn't say for sure.
S.
Will firmware updater handle GBL files now? I've a couple of bug fixes from Aeotec for the RE7s that I need to test out.
Anyone knows how to find firmware for fibaro???
Specifically I need firmware files for FGS-222 relay.....
Why yes .. yes it will ..
I should note.. The both variants of the firmware updater are not equipped yet to handle device that have been securely joined..
One more thing.. The binary updater has a bug with some hex files that include bootloaders and have to be 0 filled.. Until I have time to look at this use the original version for those specific files.. Binary version works for hex (without bootloader), otz, gbl, and bin
The original version works for hex, otz
Thanks Bryan. I'll enroll them insecurely for the update.
Ran into a problem updating firmware for the Aeotec Range Extender 7...
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:20.701 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)locked by:
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:20.689 [warn](http://hubitat-c5-dev.cococafe.com/device/edit/186)ERROR. The requested Fragment Size exceeds the Max Fragment Size
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:20.466 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)7A03037104BDD7F100002800
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:20.447 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)done calculating crc: d7f1
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.953 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)calculating crc
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.949 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)done loading list
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.642 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)loading 138865 bytes into list
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.633 [info](http://hubitat-c5-dev.cococafe.com/device/edit/186)byte buffer size: 138865
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.622 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)false
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.617 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)ë¦
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.597 [info](http://hubitat-c5-dev.cococafe.com/device/edit/186)138865 bytes read into memory
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.590 [info](http://hubitat-c5-dev.cococafe.com/device/edit/186)byte buffer size: 138865
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:19.576 [info](http://hubitat-c5-dev.cococafe.com/device/edit/186)138865 bytes
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:18.396 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)firmwareMdReport: checksum 0 firmwareId: 1213 manufacturerId: 881 maxFragmentSize: null firmwareTargets: 0
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:18.341 [debug](http://hubitat-c5-dev.cococafe.com/device/edit/186)FirmwareMDReport: FirmwareMdReport(manufacturerId:881, firmwareId:1213, checksum:0, firmwareUpgradable:false, numberOfTargets:0, maxFragmentSize:null, firmwareIds:[])
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:18.066 [info](http://hubitat-c5-dev.cococafe.com/device/edit/186)VersionReport- applicationVersion:1.1
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:18.060 [info](http://hubitat-c5-dev.cococafe.com/device/edit/186)VersionReport- zWaveProtocolVersion:7.11
[dev:186](http://hubitat-c5-dev.cococafe.com/logs#dev186)2020-07-30 11:03:17.790 [info](http://hubitat-c5-dev.cococafe.com/device/edit/186)FirmwareUpdateMd version:5Smooth updates on two Zen15 power switches today. 1.3 to 1.4. Zooz support was quick to send over the firmware like usual. 
I am getting "Please wake up your sleepy device" message for an Inovelli Black On/Off switch (LZW30). I am trying to flash the beta firmware found below
https://files.inovelli.com/firmware/LZW30/LZW30_1.19.otz
Please help
Download the Hubitat app
