I had HA perform the 1.1 firmware update for the zwa-2 right after I had installed it... unfortunately, it didn't come back up and the zwave add-on logs state that it's stuck in the bootloader... errors state "please flash new firmware" ... how do I fix this? I can't find any documentation about how to manually flash the device...
#zwa-2 stuck in bootloader after HA firmware update to 1.1
1 messages · Page 1 of 1 (latest)
Using the core Z-Wave JS add-on or Z-Wave JS UI?
core z-wave JS
I would try the command line tool which you can run from either of the SSH/Terminal add-ons. https://github.com/kpine/zwave-js-server-docker/wiki/700-series-Controller-Firmware-Updates-(Linux)#z-wave-js-flash-utility-update
The download link for the GBL file is https://github.com/NabuCasa/zwave-firmware/releases/download/1.1.0/zwa2_controller_1.1.0.gbl
Other option would be to contact Nabu Casa support directly. I presume they provide some kind of product support. Or submit a Github issue for HA core. Seems a way to get out of bootloader mode is going to be required if they are providing an update entity.
awesome! thanks for the guidance! I'm giving it a go now
If you happen to have any logs of the bad upgrade they might be useful for a bug report.
I did contact their support, but I have to assume it will be slow and was hoping there was a way to attempt a reflash in the meantime
Yep.
Let me know if the CLI works. The other option would be to install Z-Wave JS UI (even temporarily if you don't want it) and use the bootloader option.
the firmware seemed to take via command line this time... the add-on started and logs look good... now adding it as a zwave device just says "failed to connect"... I'm deleting the add-on and rebooting to start from scratch
and success! looks like I'm back in business!
I agree with you the logs would have been helpful, but I doubt anything would still be there since after the initial process failed, I deleted all the zwave integration stuff trying to get a fresh retry...
Thanks again! I appreciate the help!
Typically debug level logs are required, which aren't enabled by default anyways.