Can I make a simple quality of life suggestion? Name your firmware files with the target in the name.
Example: LZW31-SN_1.57 (target 0).otz and LZW31-SN_1.45 (target 1).bin
My simple brain has to triple check each time I go to update it.
3 Likes
@EricM_Inovelli if a new firmware version is released could more scene control be added to the config button? It would be nice to be able to use 2, 3, 4, and 5 config button presses as triggers to control scenes rather than only being able to use the current single config button press. From what I read in the Red 2 and 1 thread the config button will have the 1-5 button press triggers as well as hold and release. I plan on getting a couple of them to replace some other switches I have but would like to avoid paying to replace the Red Dimmers I have with the Red 2 in 1 just for the multiple config button triggers.
I’m not sure if this will be possible. For one, the manufacturer has cut ties with Inovelli and is no longer entertaining firmware updates or manufacturing new units. Also, I believe the Lee is no more room on the LZW31-SN MCU for any new features. They would have to remove some of the other features in order to fit new features in it.
I only foresee replacing the older gen 2 reds with the upcoming Red 2-1 dimmer.
Can we get this updated in Home Assistant? GitHub - zwave-js/firmware-updates: The firmware update service for Z-Wave JS at https://firmware.zwave-js.io doesn’t have this listed, and I have switches stuck on 1.35.
We’re waiting on this issue to be resolved: Restore Inovelli LZW31-SN (draft until multi-target updates are fixed) by AlCalzone · Pull Request #39 · zwave-js/firmware-updates · GitHub
Looks like they still aren’t in Z-Wave JS, which is annoying but not completely Inovelli’s fault. Looks like they Z-Wave JS folks won’t add it back until they get them a physical switch and UPS made that hard.
But I’m having issues getting the firmware from Github. When I download them from HERE they don’t pass my MD5 checksum.
certutil -hashfile .\LZW31-SN_1.57.otz MD5
MD5 hash of .\LZW31-SN_1.57.otz:
469099e640a2f4aee4bc8ff5a611d6b0
MD5 from the repo:
7ee1e4cd015f8669ff1c50a0da2caf92
@EricM_Inovelli @Eric_Inovelli can we get the GitRepo fixed or get the files somewhere with verified hashes? I’m still not having any luck downloading firmware from the Git.
Name: LZW31-SN_1.57.otz
Date: 9/19/2023
Size: 271 KB (277,850 bytes)
SHA-1: 6c0e6deeb0e6d080d841ec98089dd3141da1d2fa
MD5: d80cd2d07a675e0947b4e71c4a5206b7
CRC32: c15363e2
MD5 from verification file: 7ee1e4cd015f8669ff1c50a0da2caf92
2 Likes
https://files.inovelli.com/firmware/LZW31-SN/1.57/
I downloaded https://files.inovelli.com/firmware/LZW31-SN/1.57/LZW31-SN_1.57.otz and it matched the md5sum txt file
2 Likes
Yep, I think the Github version is hosed. I hashed the Github version and got the same MD-5 and SHA1 that @nfwolfpryde got, which do not match the published values. I hashed the files.inovelli.com version and got the proper hashes just as @stu1811 did.
So go get it from the location @stu1811 posted.
2 Likes
Thanks guys. I replaced the file and the md5 seems to be checking ok now. I’m not a fan of how files are treated in github when we are wanting them to just be downloadable. Is there a different way to do it? Like, when I click on the file name it displays the contents of the file and then I right click on “raw” to download the file. Is there a way to make it just download the file in the first place instead of having it display the contents?
@EricM_Inovelli I can’t get 3 of my LZW31-SN switches to update to the latest version. They are all stuck on 1.35. I’m running the latest HASS. I have attached my ZWaveJS log. Thanks for your time and assistance.
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 545
is last: false
2024-11-14T20:07:50.625Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:50.629Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:50.630Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:50.631Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:50.757Z SERIAL « 0x01050013680081 (7 bytes)
2024-11-14T20:07:50.758Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:50.759Z DRIVER « [REQ] [SendData]
callback id: 104
transmit status: OK
2024-11-14T20:07:50.762Z DRIVER all queues idle
2024-11-14T20:07:50.833Z SERIAL « 0x011700040006119f033a00586ac3c50af4fb7f1816bd88d3fb (25 bytes)
2024-11-14T20:07:50.839Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:50.843Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 58
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 546
2024-11-14T20:07:50.846Z CNTRLR » [Node 006] Sending firmware fragment 546 / 555
2024-11-14T20:07:50.853Z DRIVER one or more queues busy
2024-11-14T20:07:50.858Z SERIAL » 0x01350013062e9f032b009a00a0d9062c42912ee88cbfa4a2069592ee4c6f7f455 (55 bytes)
97053cba676c56fef1b1de902244ac88fc4440d256978
2024-11-14T20:07:50.860Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 105
└─[Security2CCMessageEncapsulation]
│ sequence number: 43
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 546
is last: false
2024-11-14T20:07:50.866Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:50.870Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:50.870Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:50.872Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:51.003Z SERIAL « 0x01050013690080 (7 bytes)
2024-11-14T20:07:51.004Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.006Z DRIVER « [REQ] [SendData]
callback id: 105
transmit status: OK
2024-11-14T20:07:51.012Z DRIVER all queues idle
2024-11-14T20:07:51.083Z SERIAL « 0x011700040006119f033b00dd9f98a0976e66f15d9936260e92 (25 bytes)
2024-11-14T20:07:51.088Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.093Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 59
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 547
2024-11-14T20:07:51.095Z CNTRLR » [Node 006] Sending firmware fragment 547 / 555
2024-11-14T20:07:51.102Z DRIVER one or more queues busy
2024-11-14T20:07:51.107Z SERIAL » 0x01350013062e9f032c00f17689d84645822ccf9b118818054bc1dae1af744fbca (55 bytes)
2d73c8e886f79a80762af5596cef8c81de089ee256aa0
2024-11-14T20:07:51.108Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 106
└─[Security2CCMessageEncapsulation]
│ sequence number: 44
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 547
is last: false
2024-11-14T20:07:51.114Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:51.126Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:51.128Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.130Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:51.240Z SERIAL « 0x010500136a0083 (7 bytes)
2024-11-14T20:07:51.242Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.244Z DRIVER « [REQ] [SendData]
callback id: 106
transmit status: OK
2024-11-14T20:07:51.252Z DRIVER all queues idle
2024-11-14T20:07:51.325Z SERIAL « 0x011700040006119f033c00fa6f2124f33ce65f53db4ee0019a (25 bytes)
2024-11-14T20:07:51.334Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.338Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 60
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 548
2024-11-14T20:07:51.341Z CNTRLR » [Node 006] Sending firmware fragment 548 / 555
2024-11-14T20:07:51.393Z DRIVER one or more queues busy
2024-11-14T20:07:51.401Z SERIAL » 0x01350013062e9f032d00712748800260eb95192249f64cbdc4a606b5e272f639e (55 bytes)
33efcfd655514b6243c2de1313b7af853bc1b15256b84
2024-11-14T20:07:51.406Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 107
└─[Security2CCMessageEncapsulation]
│ sequence number: 45
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 548
is last: false
2024-11-14T20:07:51.413Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:51.417Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:51.418Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.419Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:51.501Z SERIAL « 0x010500136b0082 (7 bytes)
2024-11-14T20:07:51.913Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.915Z DRIVER « [REQ] [SendData]
callback id: 107
transmit status: OK
2024-11-14T20:07:51.924Z DRIVER all queues idle
2024-11-14T20:07:51.926Z SERIAL « 0x011700040006119f033d00a5d77851175b270e0fd59e222321 (25 bytes)
2024-11-14T20:07:51.929Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.931Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 61
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 549
2024-11-14T20:07:51.933Z CNTRLR » [Node 006] Sending firmware fragment 549 / 555
2024-11-14T20:07:51.939Z DRIVER one or more queues busy
2024-11-14T20:07:51.946Z SERIAL » 0x01350013062e9f032e001eaaa69fa194acfe92e77c653234450cf89d4b66c1ed3 (55 bytes)
a0290c6a58894ffdde6c50d1d6dfe2cb25d8d19256ca5
2024-11-14T20:07:51.948Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 108
└─[Security2CCMessageEncapsulation]
│ sequence number: 46
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 549
is last: false
2024-11-14T20:07:51.954Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:51.958Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:51.959Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:51.960Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:52.057Z SERIAL « 0x010500136c0085 (7 bytes)
2024-11-14T20:07:52.059Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.061Z DRIVER « [REQ] [SendData]
callback id: 108
transmit status: OK
2024-11-14T20:07:52.067Z DRIVER all queues idle
2024-11-14T20:07:52.135Z SERIAL « 0x011700040006119f033e009505277a7a6817edbbf8db8f355e (25 bytes)
2024-11-14T20:07:52.141Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.144Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 62
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 550
2024-11-14T20:07:52.146Z CNTRLR » [Node 006] Sending firmware fragment 550 / 555
2024-11-14T20:07:52.158Z DRIVER one or more queues busy
2024-11-14T20:07:52.163Z SERIAL » 0x01350013062e9f032f0094af92adeaf2491f092c91d6d20c4a13d64041d341ea2 (55 bytes)
c150843d670e67c71f3cf03bb10b6e81f67ed60256d0a
2024-11-14T20:07:52.164Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 109
└─[Security2CCMessageEncapsulation]
│ sequence number: 47
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 550
is last: false
2024-11-14T20:07:52.171Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:52.178Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:52.179Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.182Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:52.293Z SERIAL « 0x010500136d0084 (7 bytes)
2024-11-14T20:07:52.295Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.297Z DRIVER « [REQ] [SendData]
callback id: 109
transmit status: OK
2024-11-14T20:07:52.301Z DRIVER all queues idle
2024-11-14T20:07:52.374Z SERIAL « 0x011700040006119f033f00215946631fae510ba0fbdb1bcabf (25 bytes)
2024-11-14T20:07:52.379Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.382Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 63
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 551
2024-11-14T20:07:52.384Z CNTRLR » [Node 006] Sending firmware fragment 551 / 555
2024-11-14T20:07:52.391Z DRIVER one or more queues busy
2024-11-14T20:07:52.421Z SERIAL » 0x01350013062e9f03300009b425a7a5e63cd6f13e063c1ec78f649b431ddf52634 (55 bytes)
fdeba20c8b3b987e3fcaebc554710564ede8390256ef8
2024-11-14T20:07:52.424Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 110
└─[Security2CCMessageEncapsulation]
│ sequence number: 48
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 551
is last: false
2024-11-14T20:07:52.429Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:52.434Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:52.435Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.437Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:52.524Z SERIAL « 0x010500136e0087 (7 bytes)
2024-11-14T20:07:52.525Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.528Z DRIVER « [REQ] [SendData]
callback id: 110
transmit status: OK
2024-11-14T20:07:52.533Z DRIVER all queues idle
2024-11-14T20:07:52.604Z SERIAL « 0x011700040006119f0340005ccb49c018e58f611a7c9c5c810d (25 bytes)
2024-11-14T20:07:52.609Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.612Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 64
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 552
2024-11-14T20:07:52.614Z CNTRLR » [Node 006] Sending firmware fragment 552 / 555
2024-11-14T20:07:52.621Z DRIVER one or more queues busy
2024-11-14T20:07:52.626Z SERIAL » 0x01350013062e9f0331002926bb56e88d855a51b449a8cbe872bcbef24eddd6a0f (55 bytes)
f4c70ec00ef7b554c0744f3234191c67be3c21a256f69
2024-11-14T20:07:52.627Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 111
└─[Security2CCMessageEncapsulation]
│ sequence number: 49
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 552
is last: false
2024-11-14T20:07:52.639Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:52.641Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:52.642Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.644Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:52.754Z SERIAL « 0x010500136f0086 (7 bytes)
2024-11-14T20:07:52.756Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.760Z DRIVER « [REQ] [SendData]
callback id: 111
transmit status: OK
2024-11-14T20:07:52.766Z DRIVER all queues idle
2024-11-14T20:07:52.833Z SERIAL « 0x011700040006119f03410020b0115ab85b197b3827b680a0f5 (25 bytes)
2024-11-14T20:07:52.838Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.841Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 65
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 553
2024-11-14T20:07:52.843Z CNTRLR » [Node 006] Sending firmware fragment 553 / 555
2024-11-14T20:07:52.851Z DRIVER one or more queues busy
2024-11-14T20:07:52.856Z SERIAL » 0x01350013062e9f033200b46c5ee83778fc2a9d73b3e53cfd9edfb8b7fb9a01265 (55 bytes)
a377bf8a36bfea4d96c76d09448eb3627bb5fa7257086
2024-11-14T20:07:52.857Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 112
└─[Security2CCMessageEncapsulation]
│ sequence number: 50
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 553
is last: false
2024-11-14T20:07:52.864Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:52.867Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:52.868Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:52.870Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:53.057Z SERIAL « 0x01050013700099 (7 bytes)
2024-11-14T20:07:53.058Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.061Z DRIVER « [REQ] [SendData]
callback id: 112
transmit status: OK
2024-11-14T20:07:53.071Z DRIVER all queues idle
2024-11-14T20:07:53.141Z SERIAL « 0x011700040006119f0342008377eace1e49696c1f755c3811b8 (25 bytes)
2024-11-14T20:07:53.146Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.148Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 66
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 554
2024-11-14T20:07:53.150Z CNTRLR » [Node 006] Sending firmware fragment 554 / 555
2024-11-14T20:07:53.159Z DRIVER one or more queues busy
2024-11-14T20:07:53.163Z SERIAL » 0x01350013062e9f033300f71091cbc7c62e9e82204fbf0426c6fcecb60ae1840c2 (55 bytes)
8cd5e45f09a2823bd97ceb1b57b2198179cca502571d9
2024-11-14T20:07:53.165Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 113
└─[Security2CCMessageEncapsulation]
│ sequence number: 51
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 554
is last: false
2024-11-14T20:07:53.170Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:53.176Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:53.177Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.179Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:53.300Z SERIAL « 0x01050013710098 (7 bytes)
2024-11-14T20:07:53.301Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.303Z DRIVER « [REQ] [SendData]
callback id: 113
transmit status: OK
2024-11-14T20:07:53.308Z DRIVER all queues idle
2024-11-14T20:07:53.383Z SERIAL « 0x011700040006119f0343000b709e5e96013cd106d115db3bc7 (25 bytes)
2024-11-14T20:07:53.389Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.392Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 67
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 555
2024-11-14T20:07:53.393Z CNTRLR » [Node 006] Sending firmware fragment 555 / 555
2024-11-14T20:07:53.401Z DRIVER one or more queues busy
2024-11-14T20:07:53.405Z SERIAL » 0x012d001306269f0334006a5fa0ff12c71d2fb64d629305d0cbce7ffed51dc72eb (47 bytes)
5e716980cea449840d8d85325721c
2024-11-14T20:07:53.407Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 114
└─[Security2CCMessageEncapsulation]
│ sequence number: 52
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCReport]
report #: 555
is last: true
2024-11-14T20:07:53.411Z SERIAL « [ACK] (0x06)
2024-11-14T20:07:53.416Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:07:53.417Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.419Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:07:53.530Z SERIAL « 0x0105001372009b (7 bytes)
2024-11-14T20:07:53.531Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.533Z DRIVER « [REQ] [SendData]
callback id: 114
transmit status: OK
2024-11-14T20:07:53.638Z DRIVER all queues idle
2024-11-14T20:07:53.924Z SERIAL « 0x011700040006119f034400fdf9344946733c9ebbce7bc55b5d (25 bytes)
2024-11-14T20:07:53.941Z SERIAL » [ACK] (0x06)
2024-11-14T20:07:53.961Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCMessageEncapsulation]
│ sequence number: 68
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCStatusReport]
status: OK_RestartPending
wait time: 0 seconds
2024-11-14T20:07:53.985Z CNTRLR « [Node 006] Firmware update (part 1 / 2) succeeded with status OK_RestartPendin
g
2024-11-14T20:07:53.986Z CNTRLR [Node 006] Continuing with next part in 5 seconds...
2024-11-14T20:07:59.112Z CNTRLR [Node 006] Updating firmware (part 2 / 2)...
2024-11-14T20:07:59.477Z CNTRLR » [Node 006] Starting firmware update...
2024-11-14T20:08:01.200Z DRIVER one or more queues busy
2024-11-14T20:08:02.101Z SERIAL » 0x011f001306189f0335007220e40f0607363c1a9ce078606f4320c5eb7ced25736 (33 bytes)
d
2024-11-14T20:08:02.560Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 115
└─[Security2CCMessageEncapsulation]
│ sequence number: 53
│ security class: S2_Authenticated
└─[FirmwareUpdateMetaDataCCRequestGet]
manufacturer id: 0x031e
firmware id: 0x0101
checksum: 0xbc1c
firmware target: 0
fragment size: 28
activation: false
resume: false
non-secure transfer: false
2024-11-14T20:08:02.794Z SERIAL « 0x010900040006039f018be2 (11 bytes)
2024-11-14T20:08:02.987Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:02.990Z SERIAL « 0x010900040006039f018be2 (11 bytes)
2024-11-14T20:08:03.217Z SERIAL « 0x010900040006039f018be2 (11 bytes)
2024-11-14T20:08:03.264Z SERIAL « [CAN] (0x18)
2024-11-14T20:08:03.382Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-11-14T20:08:03.386Z DRIVER Dropping message with invalid payload
2024-11-14T20:08:03.388Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCNonceGet] [INVALID]
error: Duplicate command (sequence number 139)
2024-11-14T20:08:03.388Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:03.389Z DRIVER Dropping message with invalid payload
2024-11-14T20:08:03.390Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCNonceGet] [INVALID]
error: Duplicate command (sequence number 139)
2024-11-14T20:08:03.390Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:04.385Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCNonceGet]
sequence number: 139
2024-11-14T20:08:06.482Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 115
└─[Security2CCMessageEncapsulation]
│ sequence number: 53
└─[FirmwareUpdateMetaDataCCRequestGet]
manufacturer id: 0x031e
firmware id: 0x0101
checksum: 0xbc1c
firmware target: 0
fragment size: 28
activation: false
resume: false
non-secure transfer: false
2024-11-14T20:08:06.499Z SERIAL » 0x011f001306189f0335007220e40f0607363c1a9ce078606f4320c5eb7ced25736 (33 bytes)
d
2024-11-14T20:08:06.632Z SERIAL « 0x010900040006039f018ce5 (11 bytes)
2024-11-14T20:08:06.634Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:06.635Z SERIAL « 0x010900040006039f018ce5 (11 bytes)
2024-11-14T20:08:06.744Z SERIAL « [ACK] (0x06)
2024-11-14T20:08:06.747Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:08:06.749Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:06.749Z DRIVER Dropping message with invalid payload
2024-11-14T20:08:06.750Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCNonceGet] [INVALID]
error: Duplicate command (sequence number 140)
2024-11-14T20:08:06.751Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:06.929Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCNonceGet]
sequence number: 140
2024-11-14T20:08:07.067Z CNTRLR [Node 006] in the process of replying to a NonceGet, won't send another NonceR
eport
2024-11-14T20:08:07.107Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:08:07.114Z SERIAL « 0x0105001373009a (7 bytes)
2024-11-14T20:08:07.116Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:07.117Z SERIAL « 0x011a00040006149f028d01dc3abfd77c8ae46dbaa103ac6ae891b004 (28 bytes)
2024-11-14T20:08:07.121Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:07.123Z DRIVER « [REQ] [SendData]
callback id: 115
transmit status: OK
2024-11-14T20:08:07.328Z SERIAL » 0x011b001306149f0236018c15a73cfa996ca6720c9df769db0d7f057441 (29 bytes)
2024-11-14T20:08:07.549Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 116
└─[Security2CCNonceReport]
sequence number: 54
SOS: true
MOS: false
receiver entropy: 0x8c15a73cfa996ca6720c9df769db0d7f
2024-11-14T20:08:07.707Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCNonceReport]
sequence number: 141
SOS: true
MOS: false
receiver entropy: 0xdc3abfd77c8ae46dbaa103ac6ae891b0
2024-11-14T20:08:07.796Z CNTRLR « [Node 006] received S2 nonce without an active transaction, not sure what to d
o with it
2024-11-14T20:08:07.802Z SERIAL « [ACK] (0x06)
2024-11-14T20:08:07.804Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:08:07.806Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:07.809Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:08:07.813Z SERIAL « 0x0105001374009d (7 bytes)
2024-11-14T20:08:07.814Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:07.816Z DRIVER « [REQ] [SendData]
callback id: 116
transmit status: OK
2024-11-14T20:08:07.820Z DRIVER all queues idle
2024-11-14T20:08:41.631Z SERIAL « 0x010900040006039f018ee7 (11 bytes)
2024-11-14T20:08:42.053Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:42.335Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[Security2CCNonceGet]
sequence number: 142
2024-11-14T20:08:42.542Z DRIVER one or more queues busy
2024-11-14T20:08:42.679Z SERIAL » 0x011b001306149f023701ad246ab53f29eb07a9a6bb2f1fbc7a7a0575aa (29 bytes)
2024-11-14T20:08:42.682Z DRIVER » [Node 006] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 117
└─[Security2CCNonceReport]
sequence number: 55
SOS: true
MOS: false
receiver entropy: 0xad246ab53f29eb07a9a6bb2f1fbc7a7a
2024-11-14T20:08:42.688Z SERIAL « [ACK] (0x06)
2024-11-14T20:08:42.692Z SERIAL « 0x0104011301e8 (6 bytes)
2024-11-14T20:08:42.693Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:42.695Z DRIVER « [RES] [SendData]
was sent: true
2024-11-14T20:08:42.755Z SERIAL « 0x0105001375009c (7 bytes)
2024-11-14T20:08:42.756Z SERIAL » [ACK] (0x06)
2024-11-14T20:08:42.758Z DRIVER « [REQ] [SendData]
callback id: 117
transmit status: OK
2024-11-14T20:08:42.765Z DRIVER all queues idle
Z-Wave error ZWaveError: Received no matching command within the provided timeout! (ZW0201)
at Timeout.<anonymous> (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6395:6)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7) {
code: 201,
context: undefined,
transactionSource: undefined
}
I believe I have seen this issue when the device is included using S2. The workaround is to include the device without security and then try the update again. Make sure you do a factory reset after updating both targets.
I believe that after the update you can simply choose “Replace node” in Zwave JS to add it back and not have to worry about re-doing automations etc.
Looks like the firmware issue has been resolved in this release of the zwavejs. @EricM_Inovelli do you have any idea when HomeAssistant will pull this release in?
Unfortunately, I do not. It is nice that they have fixed it though!
Hello,
I’m trying to update my LZW31-SN from 1.47 to 1.57 and having issues. I’m currently trying OTA updates with zwavejs docker:
zwave-js-ui: 10.9.0.26f2e69
zwave-js: 15.9.0
The 1.57 option is available, however the update is failing every time. I’ve tried pulling the air gap and restarting zwavejs, pushing air gap, waiting for status green, and trying again, but no luck.
2025-07-21 06:45:39.081 INFO Z-WAVE: Success zwave api call firmwareUpdateOTA { success: false, status: 1, reInterview: false }
I’m currently included without security. Thank you for your time,
~jerry
Full Debug:
Scan completed
Filter logs
Type to filter logs, case sensitive
2025-07-21 06:44:25.700 INFO APP: GET /api/settings 200 1039.354 ms - 40196
2025-07-21 06:44:25.707 INFO APP: GET /api/auth-enabled 304 1.733 ms - -
2025-07-21 06:44:25.911 INFO APP: GET /assets/index-Blr6EMNg.js 200 3.216 ms - 103120
2025-07-21 06:44:28.396 INFO APP: GET /assets/SmartStart-DQEq7IdO.js 200 4.840 ms - 13936
2025-07-21 06:44:28.416 INFO APP: GET /assets/MissingKeysAlert-CuyVgKq3.js 200 3.034 ms - 1168
2025-07-21 06:44:28.417 DEBUG SOCKET: Event ZWAVE_API emitted to IZrN9V6XkqPJuLLPAAAF
2025-07-21 06:44:28.418 INFO Z-WAVE: Calling api getProvisioningEntries with args: [ [length]: 0 ]
2025-07-21 06:44:28.419 INFO Z-WAVE: Success zwave api call getProvisioningEntries [ [length]: 0 ]
2025-07-21 06:44:34.334 INFO APP: GET /assets/Settings-CelSEgKp.css 200 3.563 ms - 149
2025-07-21 06:44:34.335 INFO APP: GET /assets/Settings-09wn9ovw.js 200 3.326 ms - 89468
2025-07-21 06:44:34.360 INFO APP: GET /assets/DialogGatewayValue-CBAbjUim.js 200 3.403 ms - 8864
2025-07-21 06:44:34.362 INFO APP: GET /assets/InvertedCheckbox-BxTNUbmf.js 200 5.882 ms - 417
2025-07-21 06:44:34.364 INFO APP: GET /assets/DialogGatewayValue-EYROGA4d.css 200 5.498 ms - 61
2025-07-21 06:44:34.868 SERIAL « 0x011c00a800000100030e3202216400000181ffff000001810094007f7fa6 (30 bytes)
2025-07-21 06:44:34.873 SERIAL » [ACK] (0x06)
2025-07-21 06:44:34.875 CNTRLR [Node 003] [Meter] value[65537]: metadata updated [Endpoint 0]
2025-07-21 06:44:34.875 INFO Z-WAVE: [Node 003] Metadata updated: 50-0-value-65537
2025-07-21 06:44:34.875 CNTRLR [Node 003] [~] [Meter] value[65537]: 0.385 => 0.385 [Endpoint 0]
2025-07-21 06:44:34.875 INFO Z-WAVE: [Node 003] Value updated: 50-0-value-65537 0.385 => 0.385
2025-07-21 06:44:34.876 DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -108 dBm
└─[MeterCCReport]
meter type: Electric
scale: kWh
rate type: Consumed
value: 0.385
prev. value: 0.385
2025-07-21 06:44:35.415 INFO APP: GET /api/settings 304 1033.759 ms - -
2025-07-21 06:44:35.422 INFO APP: GET /api/auth-enabled 304 1.453 ms - -
2025-07-21 06:44:37.567 INFO APP: GET /assets/Scenes-hUqq3hjY.js 200 27.779 ms - 5795
2025-07-21 06:44:37.579 DEBUG SOCKET: Event ZWAVE_API emitted to IZrN9V6XkqPJuLLPAAAF
2025-07-21 06:44:37.581 INFO Z-WAVE: Calling api _getScenes with args: [ [length]: 0 ]
2025-07-21 06:44:37.583 INFO Z-WAVE: Success zwave api call _getScenes [ [length]: 0 ]
2025-07-21 06:44:37.586 INFO APP: GET /assets/DialogSceneValue-Cc8ZADjM.js 200 1.315 ms - 3182
2025-07-21 06:44:42.563 INFO APP: GET /assets/Store-BLs9K8EO.css 304 1.061 ms - -
2025-07-21 06:44:42.566 INFO APP: GET /assets/Store-DvpEeDs7.js 304 0.915 ms - -
2025-07-21 06:44:42.706 INFO APP: GET /api/store 200 115.452 ms - 337007
2025-07-21 06:44:44.807 DEBUG SOCKET: Event ZWAVE_API emitted to IZrN9V6XkqPJuLLPAAAF
2025-07-21 06:44:44.808 INFO Z-WAVE: Calling api getProvisioningEntries with args: [ [length]: 0 ]
2025-07-21 06:44:44.809 INFO Z-WAVE: Success zwave api call getProvisioningEntries [ [length]: 0 ]
2025-07-21 06:44:51.241 DRIVER one or more queues busy
2025-07-21 06:44:51.243 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:44:51.243 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:44:51.247 SERIAL « [ACK] (0x06)
2025-07-21 06:44:51.249 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:44:51.250 SERIAL » [ACK] (0x06)
2025-07-21 06:44:51.250 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:44:51.251 DRIVER all queues idle
2025-07-21 06:45:21.240 DRIVER one or more queues busy
2025-07-21 06:45:21.241 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:45:21.241 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:45:21.245 SERIAL « [ACK] (0x06)
2025-07-21 06:45:21.246 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:45:21.247 SERIAL » [ACK] (0x06)
2025-07-21 06:45:21.248 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:45:21.248 DRIVER all queues idle
2025-07-21 06:45:33.693 DEBUG SOCKET: Event ZWAVE_API emitted to IZrN9V6XkqPJuLLPAAAF
2025-07-21 06:45:33.694 INFO Z-WAVE: Calling api getAvailableFirmwareUpdates with args: [ 3, { includePrereleases: false }, [length]: 2 ]
2025-07-21 06:45:33.820 INFO Z-WAVE: Success zwave api call getAvailableFirmwareUpdates [
{
device: {
manufacturerId: 798,
productType: 1,
productId: 1,
firmwareVersion: '1.47',
rfRegion: 9
},
version: '1.57',
changelog: '* Fixed - Optimization of Aux mode in neutral setting. \n' +
'* Fixed - The inoperative issue after changing parameter 8 from high value to low value.',
channel: 'stable',
files: [
{
target: 1,
url: 'https://files.inovelli.com/firmware/LZW31-SN/1.57/LZW31-SN_1.45.bin',
integrity: 'sha256:2a338a5f501746b69c91489efe1cb4b8b3d62a29501779943bf90625582693f1'
},
{
target: 0,
url: 'https://files.inovelli.com/firmware/LZW31-SN/1.57/LZW31-SN_1.57.otz',
integrity: 'sha256:c58d970e7148c000798e0bef3f214be4cbf93f62a784738e9b9c30b516b91e61'
},
[length]: 2
],
downgrade: false,
normalizedVersion: '1.57.0'
},
{
device: {
manufacturerId: 798,
productType: 1,
productId: 1,
firmwareVersion: '1.47',
rfRegion: 9
},
version: '1.61',
changelog: 'Fixed - Dimmer sending duplicate reports in certain scenarios while being controlled by certain hubs.',
channel: 'beta',
files: [
{
target: 1,
url: 'https://files.inovelli.com/firmware/LZW31-SN/Beta/1.61/LZW31-SN_1.45.bin',
integrity: 'sha256:2a338a5f501746b69c91489efe1cb4b8b3d62a29501779943bf90625582693f1'
},
{
target: 0,
url: 'https://files.inovelli.com/firmware/LZW31-SN/Beta/1.61/LZW31-SN_1.61.otz',
integrity: 'sha256:e07cb9972bfe88e143c72c9b6ed88a640b9d969fbf09d6c1a4625f711979b541'
},
[length]: 2
],
downgrade: false,
normalizedVersion: '1.61.0-beta'
},
[length]: 2
]
2025-07-21 06:45:38.387 DEBUG SOCKET: Event ZWAVE_API emitted to IZrN9V6XkqPJuLLPAAAF
2025-07-21 06:45:38.388 INFO Z-WAVE: Calling api firmwareUpdateOTA with args: [
3,
{
device: {
manufacturerId: 798,
productType: 1,
productId: 1,
firmwareVersion: '1.47',
rfRegion: 9
},
version: '1.57',
changelog: '<ul>\n' +
'<li>Fixed - Optimization of Aux mode in neutral setting.</li>\n' +
'<li>Fixed - The inoperative issue after changing parameter 8 from high value to low value.</li>\n' +
'</ul>\n',
channel: 'stable',
files: [
{
target: 1,
url: 'https://files.inovelli.com/firmware/LZW31-SN/1.57/LZW31-SN_1.45.bin',
integrity: 'sha256:2a338a5f501746b69c91489efe1cb4b8b3d62a29501779943bf90625582693f1'
},
{
target: 0,
url: 'https://files.inovelli.com/firmware/LZW31-SN/1.57/LZW31-SN_1.57.otz',
integrity: 'sha256:c58d970e7148c000798e0bef3f214be4cbf93f62a784738e9b9c30b516b91e61'
},
[length]: 2
],
downgrade: false,
normalizedVersion: '1.57.0'
},
[length]: 2
]
2025-07-21 06:45:38.389 CNTRLR [Node 003] OTA firmware update started, downloading 2 updates...
2025-07-21 06:45:38.389 CNTRLR [Node 003] Downloading firmware update 0 of 2...
2025-07-21 06:45:38.484 CNTRLR [Node 003] Downloading firmware update 1 of 2...
2025-07-21 06:45:38.751 CNTRLR [Node 003] All updates downloaded, validating device IDs...
2025-07-21 06:45:38.752 DRIVER one or more queues busy
2025-07-21 06:45:38.753 DRIVER » [Node 003] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 53
└─[ManufacturerSpecificCCGet]
2025-07-21 06:45:38.753 SERIAL » 0x011000a90001000302720425000000003520 (18 bytes)
2025-07-21 06:45:38.757 SERIAL « [ACK] (0x06)
2025-07-21 06:45:38.760 SERIAL « 0x010401a90152 (6 bytes)
2025-07-21 06:45:38.761 SERIAL » [ACK] (0x06)
2025-07-21 06:45:38.762 DRIVER « [RES] [SendDataBridge]
was sent: true
2025-07-21 06:45:38.776 SERIAL « 0x011d00a935000001008f7f7f7f7f00000300000000030100007f7f7f7f7f8e (31 bytes)
2025-07-21 06:45:38.777 SERIAL » [ACK] (0x06)
2025-07-21 06:45:38.777 DRIVER « [REQ] [SendDataBridge]
callback id: 53
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave, 100 kbit/s
routing scheme: LWR
ACK RSSI: -113 dBm
ACK channel no.: 0
TX channel no.: 0
2025-07-21 06:45:38.792 SERIAL « 0x011600a80000010003087205031e000100010096007f7fb7 (24 bytes)
2025-07-21 06:45:38.793 SERIAL » [ACK] (0x06)
2025-07-21 06:45:38.793 CNTRLR [Node 003] [~] [Manufacturer Specific] productId: 1 => 1 [Endpoint 0]
2025-07-21 06:45:38.793 INFO Z-WAVE: [Node 003] Value updated: 114-0-productId 1 => 1
2025-07-21 06:45:38.794 CNTRLR [Node 003] [~] [Manufacturer Specific] productType: 1 => 1 [Endpoint 0]
2025-07-21 06:45:38.794 INFO Z-WAVE: [Node 003] Value updated: 114-0-productType 1 => 1
2025-07-21 06:45:38.794 CNTRLR [Node 003] [~] [Manufacturer Specific] manufacturerId: 798 => 798 [Endpoint 0]
2025-07-21 06:45:38.795 INFO Z-WAVE: [Node 003] Value updated: 114-0-manufacturerId 798 => 798
2025-07-21 06:45:38.795 DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -106 dBm
└─[ManufacturerSpecificCCReport]
manufacturer id: 0x031e
product type: 0x01
product id: 0x01
2025-07-21 06:45:38.796 DRIVER » [Node 003] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 54
└─[VersionCCGet]
2025-07-21 06:45:38.796 SERIAL » 0x011000a900010003028611250000000036c2 (18 bytes)
2025-07-21 06:45:38.800 SERIAL « [ACK] (0x06)
2025-07-21 06:45:38.803 SERIAL « 0x010401a90152 (6 bytes)
2025-07-21 06:45:38.803 SERIAL » [ACK] (0x06)
2025-07-21 06:45:38.804 DRIVER « [RES] [SendDataBridge]
was sent: true
2025-07-21 06:45:38.873 SERIAL « 0x011d00a936000006008f7f7f7f7f00000300000000030200007f7f7f7f7f89 (31 bytes)
2025-07-21 06:45:38.875 SERIAL » [ACK] (0x06)
2025-07-21 06:45:38.876 DRIVER « [REQ] [SendDataBridge]
callback id: 54
transmit status: OK, took 60 ms
routing attempts: 2
protocol & route speed: Z-Wave, 100 kbit/s
routing scheme: LWR
ACK RSSI: -113 dBm
ACK channel no.: 0
TX channel no.: 0
2025-07-21 06:45:38.889 SERIAL « 0x011600a80000010003087205031e000100010095007f7fb4 (24 bytes)
2025-07-21 06:45:38.890 SERIAL » [ACK] (0x06)
2025-07-21 06:45:38.892 CNTRLR [Node 003] [~] [Manufacturer Specific] productId: 1 => 1 [Endpoint 0]
2025-07-21 06:45:38.892 INFO Z-WAVE: [Node 003] Value updated: 114-0-productId 1 => 1
2025-07-21 06:45:38.893 CNTRLR [Node 003] [~] [Manufacturer Specific] productType: 1 => 1 [Endpoint 0]
2025-07-21 06:45:38.894 INFO Z-WAVE: [Node 003] Value updated: 114-0-productType 1 => 1
2025-07-21 06:45:38.894 CNTRLR [Node 003] [~] [Manufacturer Specific] manufacturerId: 798 => 798 [Endpoint 0]
2025-07-21 06:45:38.895 INFO Z-WAVE: [Node 003] Value updated: 114-0-manufacturerId 798 => 798
2025-07-21 06:45:38.895 DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -107 dBm
└─[ManufacturerSpecificCCReport]
manufacturer id: 0x031e
product type: 0x01
product id: 0x01
2025-07-21 06:45:39.025 SERIAL « 0x011900a800000100030b8612030604012f010101290094007f7f40 (27 bytes)
2025-07-21 06:45:39.027 SERIAL » [ACK] (0x06)
2025-07-21 06:45:39.028 CNTRLR [Node 003] [~] [Version] hardwareVersion: 1 => 1 [Endpoint 0]
2025-07-21 06:45:39.030 INFO Z-WAVE: [Node 003] Value updated: 134-0-hardwareVersion 1 => 1
2025-07-21 06:45:39.030 CNTRLR [Node 003] [~] [Version] firmwareVersions: 1.47,1.41 => 1.47,1.41 [Endpoint 0]
2025-07-21 06:45:39.031 INFO Z-WAVE: [Node 003] Value updated: 134-0-firmwareVersions 1.47,1.41 => 1.47,1.41
2025-07-21 06:45:39.031 CNTRLR [Node 003] [~] [Version] protocolVersion: "6.4" => "6.4" [Endpoint 0]
2025-07-21 06:45:39.032 INFO Z-WAVE: [Node 003] Value updated: 134-0-protocolVersion 6.4 => 6.4
2025-07-21 06:45:39.032 CNTRLR [Node 003] [~] [Version] libraryType: 3 => 3 [Endpoint 0]
2025-07-21 06:45:39.032 INFO Z-WAVE: [Node 003] Value updated: 134-0-libraryType 3 => 3
2025-07-21 06:45:39.033 DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -108 dBm
└─[VersionCCReport]
library type: Enhanced Slave
protocol version: 6.4
firmware versions: 1.47, 1.41
hardware version: 1
2025-07-21 06:45:39.034 CNTRLR [Node 003] Device IDs match, installing firmware updates...
2025-07-21 06:45:39.035 DRIVER » [Node 003] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 55
└─[FirmwareUpdateMetaDataCCMetaDataGet]
2025-07-21 06:45:39.035 SERIAL » 0x011000a900010003027a012500000000372f (18 bytes)
2025-07-21 06:45:39.040 SERIAL « [ACK] (0x06)
2025-07-21 06:45:39.043 SERIAL « 0x010401a90152 (6 bytes)
2025-07-21 06:45:39.044 SERIAL » [ACK] (0x06)
2025-07-21 06:45:39.044 DRIVER « [RES] [SendDataBridge]
was sent: true
2025-07-21 06:45:39.060 SERIAL « 0x011d00a93700000100907f7f7f7f00000300000000030100007f7f7f7f7f93 (31 bytes)
2025-07-21 06:45:39.061 SERIAL » [ACK] (0x06)
2025-07-21 06:45:39.062 DRIVER « [REQ] [SendDataBridge]
callback id: 55
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave, 100 kbit/s
routing scheme: LWR
ACK RSSI: -112 dBm
ACK channel no.: 0
TX channel no.: 0
2025-07-21 06:45:39.077 SERIAL « 0x011c00a800000100030e7a02031e0101daf2ff01002812340090007f7f6a (30 bytes)
2025-07-21 06:45:39.078 SERIAL » [ACK] (0x06)
2025-07-21 06:45:39.079 CNTRLR [Node 003] [~] [Firmware Update Meta Data] additionalF [Endpoint 0] [internal]
irmwareIDs: 4660 => 4660
2025-07-21 06:45:39.079 CNTRLR [Node 003] [~] [Firmware Update Meta Data] firmwareUpg [Endpoint 0] [internal]
radable: true => true
2025-07-21 06:45:39.080 DRIVER « [Node 003] [REQ] [BridgeApplicationCommand]
│ RSSI: -112 dBm
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 798
firmware id: 257
checksum: 56050
firmware upgradable: true
max fragment size: 40
additional firmware IDs: [4660]
2025-07-21 06:45:39.081 INFO Z-WAVE: Success zwave api call firmwareUpdateOTA { success: false, status: 1, reInterview: false }
2025-07-21 06:45:39.082 DRIVER all queues idle
2025-07-21 06:45:51.241 DRIVER one or more queues busy
2025-07-21 06:45:51.242 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:45:51.242 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:45:51.245 SERIAL « [ACK] (0x06)
2025-07-21 06:45:51.247 SERIAL « 0x0107013b918f8f97c4 (9 bytes)
2025-07-21 06:45:51.248 SERIAL » [ACK] (0x06)
2025-07-21 06:45:51.248 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -105 dBm
2025-07-21 06:45:51.249 DRIVER all queues idle
2025-07-21 06:46:21.242 DRIVER one or more queues busy
2025-07-21 06:46:21.243 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:46:21.243 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:46:21.246 SERIAL « [ACK] (0x06)
2025-07-21 06:46:21.248 SERIAL « 0x0107013b91909095c6 (9 bytes)
2025-07-21 06:46:21.249 SERIAL » [ACK] (0x06)
2025-07-21 06:46:21.249 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -112 dBm
channel 2: -112 dBm
channel 3: -107 dBm
2025-07-21 06:46:21.250 DRIVER all queues idle
2025-07-21 06:46:51.243 DRIVER one or more queues busy
2025-07-21 06:46:51.245 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:46:51.245 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:46:51.248 SERIAL « [ACK] (0x06)
2025-07-21 06:46:51.250 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:46:51.251 SERIAL » [ACK] (0x06)
2025-07-21 06:46:51.251 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:46:51.252 DRIVER all queues idle
2025-07-21 06:47:21.244 DRIVER one or more queues busy
2025-07-21 06:47:21.245 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:47:21.245 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:47:21.248 SERIAL « [ACK] (0x06)
2025-07-21 06:47:21.251 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:47:21.252 SERIAL » [ACK] (0x06)
2025-07-21 06:47:21.252 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:47:21.253 DRIVER all queues idle
2025-07-21 06:47:51.245 DRIVER one or more queues busy
2025-07-21 06:47:51.247 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:47:51.248 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:47:51.251 SERIAL « [ACK] (0x06)
2025-07-21 06:47:51.253 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:47:51.253 SERIAL » [ACK] (0x06)
2025-07-21 06:47:51.254 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:47:51.254 DRIVER all queues idle
2025-07-21 06:48:21.245 DRIVER one or more queues busy
2025-07-21 06:48:21.246 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:48:21.247 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:48:21.250 SERIAL « [ACK] (0x06)
2025-07-21 06:48:21.251 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:48:21.252 SERIAL » [ACK] (0x06)
2025-07-21 06:48:21.253 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:48:21.254 DRIVER all queues idle
2025-07-21 06:48:51.247 DRIVER one or more queues busy
2025-07-21 06:48:51.248 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:48:51.248 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:48:51.253 SERIAL « [ACK] (0x06)
2025-07-21 06:48:51.255 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:48:51.255 SERIAL » [ACK] (0x06)
2025-07-21 06:48:51.256 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:48:51.257 DRIVER all queues idle
2025-07-21 06:49:21.248 DRIVER one or more queues busy
2025-07-21 06:49:21.249 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:49:21.250 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:49:21.253 SERIAL « [ACK] (0x06)
2025-07-21 06:49:21.254 SERIAL « 0x0107013b918f8f96c5 (9 bytes)
2025-07-21 06:49:21.255 SERIAL » [ACK] (0x06)
2025-07-21 06:49:21.256 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -106 dBm
2025-07-21 06:49:21.257 DRIVER all queues idle
2025-07-21 06:49:51.249 DRIVER one or more queues busy
2025-07-21 06:49:51.251 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:49:51.251 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:49:51.255 SERIAL « [ACK] (0x06)
2025-07-21 06:49:51.256 SERIAL « 0x0107013b91909096c5 (9 bytes)
2025-07-21 06:49:51.257 SERIAL » [ACK] (0x06)
2025-07-21 06:49:51.258 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -112 dBm
channel 2: -112 dBm
channel 3: -106 dBm
2025-07-21 06:49:51.259 DRIVER all queues idle
2025-07-21 06:50:21.250 DRIVER one or more queues busy
2025-07-21 06:50:21.251 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:50:21.252 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:50:21.255 SERIAL « [ACK] (0x06)
2025-07-21 06:50:21.257 SERIAL « 0x0107013b908f8f97c5 (9 bytes)
2025-07-21 06:50:21.258 SERIAL » [ACK] (0x06)
2025-07-21 06:50:21.259 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -112 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -105 dBm
2025-07-21 06:50:21.259 DRIVER all queues idle
2025-07-21 06:50:51.249 DRIVER one or more queues busy
2025-07-21 06:50:51.250 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:50:51.251 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:50:51.254 SERIAL « [ACK] (0x06)
2025-07-21 06:50:51.255 SERIAL « 0x0107013b91909096c5 (9 bytes)
2025-07-21 06:50:51.256 SERIAL » [ACK] (0x06)
2025-07-21 06:50:51.257 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -112 dBm
channel 2: -112 dBm
channel 3: -106 dBm
2025-07-21 06:50:51.257 DRIVER all queues idle
2025-07-21 06:51:21.250 DRIVER one or more queues busy
2025-07-21 06:51:21.251 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:51:21.253 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:51:21.256 SERIAL « [ACK] (0x06)
2025-07-21 06:51:21.257 SERIAL « 0x0107013b908f8f95c7 (9 bytes)
2025-07-21 06:51:21.258 SERIAL » [ACK] (0x06)
2025-07-21 06:51:21.259 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -112 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -107 dBm
2025-07-21 06:51:21.259 DRIVER all queues idle
2025-07-21 06:51:51.250 DRIVER one or more queues busy
2025-07-21 06:51:51.251 DRIVER » [REQ] [GetBackgroundRSSI]
2025-07-21 06:51:51.251 SERIAL » 0x0103003bc7 (5 bytes)
2025-07-21 06:51:51.254 SERIAL « [ACK] (0x06)
2025-07-21 06:51:51.256 SERIAL « 0x0107013b918f8f95c6 (9 bytes)
2025-07-21 06:51:51.257 SERIAL » [ACK] (0x06)
2025-07-21 06:51:51.258 DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -113 dBm
channel 2: -113 dBm
channel 3: -107 dBm
2025-07-21 06:51:51.259 DRIVER all queues idle
Made with ❤️ by
Daniel Lando
Very strange tbh, I haven’t tried to update this device through z-wave js for a long time. The only thing I can think of is to try downloading the file and manually updating through the device menu? Here is the update file:
https://files.inovelli.com/firmware/LZW31-SN/1.57/LZW31-SN_1.57.otz