I have Z-Wave Blinds (Graber ZWaves / Springs Window Fashion). The blinds I had had firmware 11.0 which is known to have bugs when sending commands to a group of blinds (commands overload device, and blinds might stop mid way on some occurrences)
Having learned about this - I got the firmware update files from Graber direct. Apparently it is a 2 step process. The first file is a .hex file which is an intermediate file which must be loaded first which allows you to install the new boot loader. Once you load that file you must load the actual firmware update which is a otz file.
The issue as it appears - that both Bryan Copelands original Hubitat firmware updater and the built in firmware updater on the C7 hubs, require the device to respond to a firmware request.
The issue: Once the intermediate file is loaded the device does not respond to a firmware request. So now the device is stuck with the intermediate file - I am looking for an app or driver that can allow a 'forced' firmware update file to be sent to overcome this dilemma so I can complete the update with the secondary firmware file.
Any suggestions?
Wow.. that's a pretty strange upgrade path.. I haven't seen a device require this before..
And if it doesn't respond to the firmware commands, I'm not sure of any method that will work ..
Would you mind sharing the instructions they provided?
They specifically did not want the update shared, I did privately send them to you at: support@hubitat.com if that works? It also has the engineers contact info in the readme
Ok.. I see.. It requires you to re-include after the intermediate update is done.. Then you can run the second update on the new node.. Then you will have to re-include again after the second update..
Interesting, so would you recommend I 'force' remove it from Hubitat too?
Yes.. It’s going to leave behind an old device and ghost node twice
Will let you know how it turns out, first thing I see is now 2 firmwares are identified in the firmware update module, one with a version 6.61 and one with a version 0.00; would you guess that 6.61 is where I should send the second update? Or maybe it doesn't matter?
Guessing.. I would say the 0.0 is the staged update, since I wrote the firmware updater to read the application firmware version and not the bootloader
Well as an FYI selecting 6.61 in the 2 options appeared to work. A bit annoying to update it from start to finish, but it did update the Graber Blinds (spring fashion/somfy) from 11.0 -> 12.1
Process:
- Update with intermediary file
- Exclude/Include
- Update with firmware file (selecting firmware 6.61 from the 2 options)
- Exclude/Include
- Remove both ghost devices
- Done
1 Like
Ok - would you guess it would work with either selection? I dare not try the other one (0.17 I think it was) since 6.61 worked at least for this one
