Z-Wave Update Tool

News and Updates
#21

From the release notes, 7.18.3 and 7.18.2 are functionally identical:

I’m sticking with the 7.18.2 I’ve been using for many months, since it’s worked perfectly fine for me.

#22

ZwaveJS-UI now has a built-in updater in the latest version 8.8.0:

#23

hmmm, trying to update and OTW doesn’t show the advanced path and the OLL command gives me this:

oh-la@Collective-Core:~$ sudo oll-zwave-tool --region US
Basepath used: /etc/core/oll-zwave-tool
Verifying that all services which could cause interference are DISABLED…
zwave-js-ui active: False
zwavejs2mqtt active: False
homeassistant active: False
All potenially dangerous services have been DISABLED!
[Errno 2] could not open port /dev/serial/by-type/z-wave: [Errno 2] No such file or directory: ‘/dev/serial/by-type/z-wave’
Don’t forget to re-enable HomeAssistant and zwave-js-ui if you need them, they were disabled to enable the firmware update.
Exit cleanup! Reason: ‘ZWSerial’ object has no attribute ‘regionCurrent’

#24

I tried to set my region and got the same error.

#25

This means the z-wave stick wasn’t recognized as a Z-wave stick when plugged in to CORE. What stick are you using? Re-seating it should help as long as the stick is not stuck in the bootloader.

#26

Silabs zst-700

#27

Reseating fixed it! Thanks!

#28

I just attempted to upgrade this stick, but it failed with the following error, twice.

þ¨2!43¥ó¨2!43¥ó¨2!43¥ó¨2!43¥ó¨
2!2·§2
Auto Programming Frame 1: b'\x01\x03\x00\x08\xf4' [1, 3, 0, 8, 244]
Waiting 11 seconds before sending the next frame...
Auto Programming Frame 2: b"\x01\x03\x00'\xdb" [1, 3, 0, 39, 219]
Auto Programming Enabled, again!
¨
2!2᤬
2!2᤬
2!2᤬
2!2᤬
2!2᤬
2!2᤬
2!2·§
Gecko Bootloader v1.12.01
1. upload gbl
2. run
3. ebl info
BL >1

begin upload
C
DEBUG:xmodem.XMODEM:Begin start sequence, packet_size=128
DEBUG:xmodem.XMODEM:16-bit CRC requested (CRC).
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\x18' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\r' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'\n' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'S' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'e' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'r' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'i' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b' ' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'u' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'p' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'l' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'o' for block 1
DEBUG:xmodem.XMODEM:send: block 1
ERROR:xmodem.XMODEM:send error: expected ACK; got b'a' for block 1
ERROR:xmodem.XMODEM:send error: NAK received 17 times, aborting.
Opened firmware file. Sending it to the Z-Wave device: .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 .0 ..
Firmware upgrade failed!
d aborted
#29

Anyone? More text to post.

#30

Mike. Markus took a little vacation. He’ll be back in his tomorrow.

1 Like
#31

Judging from that output it does look like you’re getting the 0x18 error, which normally means you’re fully-up-to-date. Did you install the dev-version previously, the one which ends in 255? (if you haven’t then don’t do that). If you have more output to share, that’d be good to see as well.
Have you tried the Windows app update route as well?

#32

Hmm. I last updated via the windows tool. Dont think I’ve ever used the dev branch. I’ll try again later.

#33

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.