Is my controller bricked? #7313
-
Checklist
Describe the issueI recently tried to updated my ZAC93 Zooz 800 GPIO hat to the ZAC93_SDK_7.22.1_US-LR_V01R50.gbl firmware. Before the firmware was even half way uploaded, it failed and the controller has been stuck in bootloader mode since, and Z Wave JS is unable to connect to it at all, even in bootloader only mode. I have a Serial to USB adapter that I quickly tried to attach to simplicity studio, but it was also unable to connect, though its very possible I did not set that up correctly. Regardless, here are the logs from Z Wave JS. Is there anything else I can try? Or do I just need a new controller. Software versionsZ-Wave JS UI: 9.24.0 Z-Wave Controller (Stick/Dongle/...)ZAC93 attempting to update to v1.5 Device informationNo response Checklist
Upload Logfile |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 23 replies
-
|
👋 Hey @MangoScango! It looks like you copied the contents of a logfile. Please attach it as a file instead, so it is easier to work with. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like the stick is indeed in bootloader mode. Can you make another log where you enable the "bootloader only" flag and try to start the firmware upgrade again? |
Beta Was this translation helpful? Give feedback.
-
|
Attached below. It just keeps trying to "recover" it, so it wont do anything else, despite me ostensibly turning on bootloader only mode. I'm not seeing anything showing the setting being changed though, maybe its not taking somehow? |
Beta Was this translation helpful? Give feedback.
-
|
Hmm seems that the bootloader detection after attempting to leave the bootloader does not work. As a workaround, you can try using the standalone flasher utility: You need a recent version of Node.js installed, then you can run (replace |
Beta Was this translation helpful? Give feedback.
-
|
Okay, so I have another Pi that I just spun up hass and zwave js on to try there, same behavior. I logged into the the zwave docker and ran that, here's what I got. Something I'm doing wrong? Do I need to do this in a fresh enviornment? |
Beta Was this translation helpful? Give feedback.
-
|
Ah damn. Looks like that is affected by the same bug. I'll try to reproduce this and fix ASAP - might be tonight or tomorrow though. |
Beta Was this translation helpful? Give feedback.
-
|
Tracking as an issue here: #7316 |
Beta Was this translation helpful? Give feedback.
-
|
Same for me I think: |
Beta Was this translation helpful? Give feedback.
-
|
Yep looks pretty similar. I think the issue is that the bootloader screen gets written in multiple chunks, when it's expected to come as one. |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha. Appreciate you!
…On Thu, Oct 24, 2024, 7:56 AM AlCalzone ***@***.***> wrote:
Ah damn. Looks like that is affected by the same bug. I'll try to
reproduce this and fix ASAP - might be tonight or tomorrow though.
—
Reply to this email directly, view it on GitHub
<#7313 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2FH7WDPWXVPA3OZO5TQSTZ5DN6HAVCNFSM6AAAAABQQEENKGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBUGAZDSMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Fixed in #7318 |
Beta Was this translation helpful? Give feedback.
-
|
Looks like new releases have already rolled out, but for reference I added a link to the "old" minicom instructions at https://github.com/kpine/zwave-js-server-docker/wiki/700-series-Controller-Firmware-Updates-(Linux)#minicom-and-z-modem. |
Beta Was this translation helpful? Give feedback.
-
|
Appreciated. I'll keep my controller borked for the time being for testing purposes, but I'll take that route if nothing else. |
Beta Was this translation helpful? Give feedback.
-
|
I'll gladly be a second test for the next patch. Borked is OK right now as I'm not in any rush to get this up. |
Beta Was this translation helpful? Give feedback.
-
|
Z-Wave JS UI v9.25.0 already includes the fix. So unless you are using the add-on, you can test it now. |
Beta Was this translation helpful? Give feedback.
-
|
I re-ran the manual upgrade and it worked perfectly. Device info All is well and my zwave test network is up and running. Thank you @AlCalzone !! |
Beta Was this translation helpful? Give feedback.
-
|
After seeing @jdranchman's success, I took another stab at it today, and was also successful using the flasher utility, did not have to resort to minicom. This time I spun up a new install of Pi OS (Preparing to use the minicom method). I installed NPM and ran the utility on the bare metal, and everything went smoothly. So it seems there maybe something about the HassOS/Docker environment that was causing the problem. Not a clue what it could be though. Regardless, I'm back up and running and the flasher logic seems to be working as expected, so I suppose that's all that can really be done here. |
Beta Was this translation helpful? Give feedback.
-
|
It's mainly the chunk size that seems to differ. Glad that it's at least working, I'm still going to try and make this more resilient. |
Beta Was this translation helpful? Give feedback.
-
|
Let me know if anyone needs the fix to be ported to the v13 release line. Right now it is only in the work in progress v14. |
Beta Was this translation helpful? Give feedback.
-
|
I could use it in v13 |
Beta Was this translation helpful? Give feedback.
-
|
Released as v13.10.2. |
Beta Was this translation helpful? Give feedback.
Fixed in #7318
Will release tomorrow morning