#Any help unbricking a Zooz ZAC93 gpio module in my HA Yellow after a failed FW update?!

1 messages · Page 1 of 1 (latest)

buoyant vale
#

Apparently I should have looked to see if others had this issue before trying to update to the latest fw since a few others have gotten stuck in the same scenario. The update got to about 8% and then the update failed bricking the ZAC93 in the process. I got some instructions from Zooz support about enabling bootloader mode from the zwave js ui addon, but it almost appears like the module cannot even be seen. This is what I am seeing in the zwave addon logs:

2024-12-03T00:00:08.527Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ █████╗ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ ██║ ███████╗
███╔╝ ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2024-12-03T00:00:08.534Z DRIVER version 13.10.3
2024-12-03T00:00:08.535Z DRIVER
2024-12-03T00:00:09.591Z DRIVER Controller is in bootloader, attempting to recover...
2024-12-03T00:00:10.595Z DRIVER Failed to recover from bootloader. Please flash a new firmware to continue...
Error in driver ZWaveError: Failed to recover from bootloader. Please flash a new firmware to continue... (ZW0100)
at Driver.destroyWithMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:3269:17)
at Immediate.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:1289:18) {
code: 100,
context: undefined,
transactionSource: undefined
}
Shutting down
[00:00:11] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

Not sure if anyone is able to help with this? Hopefully I am even posting in the right place!

Thanks!

signal moon
#

Based on the error message, it looks like the "Bootloader only" option was not actually enabled in ZUI at that time.

buoyant vale
#

i was a little confused about setting the module up in the zwave ui addon. it had no seret keys filled in so I wasnt able to get it into the correct mode to reflash the firmware. after just hitting the refresh icon next to each key section and hitting save, it allowed me into the bootloader mode to reflash the fw.

#

thank you for your time @signal moon

#

all is working now

signal moon
#

Were you using the core add-on?

buoyant vale
#

i was using the core zwave addon to initially update the fw when it failed, but used the zwave ui addon afterwards to reflash.

signal moon
#

Ok makes sense then.

#

Yeah ZUI will require you to fill in the security keys, even if you were to use it temporarily.

#

Did you use the CLI command?

buoyant vale
#

i did not, selecting the device /dev/ttyAMA0 and then hitting the little refresh icons next to each key let me save and then i was able to go into advanced mode and upload the fw file.

signal moon
#

Ok, works the same

#

There have been a number of fixes to address reliability problems with the controller firmware upgrade, but apparently not all the problems have been squashed.

buoyant vale
#

it sat at 0% for about 30 minutes and I read somewhere else that i could essentially back out after 10 minutes as the update would have been completed.

#

luckily it was finished. restarted HA and everything was back to normal. didnt have to readd any of my devices.

signal moon
#

Are you using SmartStart at all? Scanned QR codes.

buoyant vale
#

i was scanning qr codes...all newer zooz devices.

signal moon
#

Ok, there is an open issue that will cause this, maybe you hit that. Can't tell without logs though.

buoyant vale
#

my luck lol. i can provide logs if you are interested in looking.

signal moon
#

You have old logs?

#

They aren't enabled by default

buoyant vale
#

ah no sorry

signal moon
#

Are you switching to ZUI or sticking with core add-on?

buoyant vale
#

i am going to stick with core as i am still a noob and it feels more comfortable for me.

ebon umbra
#

I bricked a zooz zen switch using OTA once, and they were very understanding thru customer service, and even replaced the device for free. I suggest you email zooz support. Good luck! @buoyant vale

signal moon
#

this was resolved

jagged spoke
#

Thanks to everyone on this thread I was also able to recover my bricked zooz GPIO!