jhein
July 25, 2021, 4:39pm
1
Hi,
I have successfully updated a handful of Red Dimmers using zwavejs2mqtt to 1.48/1.41 already, but now I have one that refuses to update Target 1, after Target 0 has already been updated.
The error message I am getting is something like “this device doesn’t support target 1” or “firmware update already in progress” when I try a 2nd time.
I tried restarting the driver and re-interviewing the device, but that did not help.
Any ideas what steps to try next?
Thanks,
Julian
Agreed. It has to be a ZJS2M bug because I am having the same problem.
jhein
July 26, 2021, 2:09pm
3
I updated 5 or 6 dimmer switches successfully before that one, though. It might have been an older version, though. Maybe I’ll try to roll back one version and try again.
Agreed, I’ve done 100+ firmware updates to both targets. I think its the software that is the issue, not the switch or firmware.
What Version ZWaveJSToMqtt? They just updated to ZWaveJS 8.0.5 so there could be a bug.
Not the same Vendor, but seem similar issue it seems. Also looks like the same version you are on.
opened 03:06PM - 26 Jul 21 UTC
closed 08:47AM - 25 Oct 21 UTC
### Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
YE… S, BUT a Home Assistant developer has told me to come here
### Is your problem within ZWaveJS2MQTT?
YES, BUT a ZWaveJS2MQTT developer has told me to come here
### Checklist
- [X] I have checked the [troubleshooting section](https://zwave-js.github.io/node-zwave-js/#/troubleshooting/index) and my problem is **not** described there.
- [X] I have read the [changelog](https://github.com/zwave-js/node-zwave-js/blob/master/CHANGELOG.md) and my problem was **not** mentioned there.
### Describe the bug
What causes the bug?
OTA Firmware Updates for Zooz ZEN77 Series 700 Dimmer Switches from a Nortek husbzb‑1 controller
What do you observe?
Firmware attempts to take, but times out usually less than 1/4 of the way through the file transfers of firmware fragments. I then try again (persistence is what worked on ZEN72s and ZEN71s, but it will not take on the ZEN77s), so it fails and I try again.
"Node 45 firmware update FINISHED: Status -1, Time: undefined"
After a few more attempts, the updates fail to take as ZwaveJS2MQTT believes that a firmware update is already happening.
What did you expect to happen?
Firmware to take.
Steps to reproduce the behavior:
1. Go to 'Z-WAveJS2MQTT Control Panel within Home Assistant'
2. Find ZEN77 Z-Wave Node
3. Click on down arrow
4. Click on Advanced
5. Under Firmware update, click Begin
6. Leave Target as "0" and click OK
7. Select Firmware and open
### Device information
Manufacturer: Zooz
Model name: ZEN77
Node ID in your network: 45
controller device: Nortek husbzb‑1
### How are you using `node-zwave-js`?
- [ ] `zwavejs2mqtt` Docker image (latest)
- [ ] `zwavejs2mqtt` Docker image (dev)
- [ ] `zwavejs2mqtt` Docker manually built _(please specify branches)_
- [ ] `ioBroker.zwave2` adapter _(please specify version)_
- [X] `HomeAssistant zwave_js` integration _(please specify version)_
- [ ] `pkg`
- [ ] `node-red-contrib-zwave-js` _(please specify version, double click node to find out)_
- [ ] Manually built from GitHub _(please specify branch)_
- [X] Other _(please describe)_
### Which branches or versions?
ZwaveJS2MQTT via Home Assistant
version: 0.23.2
`node-zwave-js` branch: 8.0.5
`zwavejs2mqtt` branch: 5.4.2
### Did you change anything?
no
### If yes, what did you change?
N/A
### Did this work before?
Don't know, this is a new device
### If yes, where did it work?
Don't know.
### Attach Driver Logfile
```
ZWaveJS2MQTT
Innovation System © 2021
Debug
Node 45 firmware update FINISHED: Status -1, Time: undefined
2021-07-26T15:00:11.442Z CNTRLR » [Node 045] Sending firmware fragment 266 / 4179
2021-07-26 11:00:11.620 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 266/4179
2021-07-26T15:00:11.703Z CNTRLR » [Node 045] Sending firmware fragment 267 / 4179
2021-07-26 11:00:11.881 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 267/4179
2021-07-26T15:00:11.963Z CNTRLR » [Node 045] Sending firmware fragment 268 / 4179
2021-07-26 11:00:12.139 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 268/4179
2021-07-26T15:00:12.222Z CNTRLR » [Node 045] Sending firmware fragment 269 / 4179
2021-07-26 11:00:12.401 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 269/4179
2021-07-26T15:00:12.482Z CNTRLR » [Node 045] Sending firmware fragment 270 / 4179
2021-07-26 11:00:12.619 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 270/4179
2021-07-26T15:00:12.701Z CNTRLR » [Node 045] Sending firmware fragment 271 / 4179
2021-07-26 11:00:12.881 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 271/4179
2021-07-26T15:00:12.966Z CNTRLR » [Node 045] Sending firmware fragment 272 / 4179
2021-07-26 11:00:13.220 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 272/4179
2021-07-26T15:00:13.301Z CNTRLR » [Node 045] Sending firmware fragment 273 / 4179
2021-07-26 11:00:13.481 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 273/4179
2021-07-26T15:00:13.563Z CNTRLR » [Node 045] Sending firmware fragment 274 / 4179
2021-07-26 11:00:13.740 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 274/4179
2021-07-26T15:00:13.823Z CNTRLR » [Node 045] Sending firmware fragment 275 / 4179
2021-07-26 11:00:14.000 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 275/4179
2021-07-26T15:00:14.083Z CNTRLR » [Node 045] Sending firmware fragment 276 / 4179
2021-07-26 11:00:14.259 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 276/4179
2021-07-26T15:00:14.341Z CNTRLR » [Node 045] Sending firmware fragment 277 / 4179
2021-07-26 11:00:14.520 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 277/4179
2021-07-26T15:00:14.600Z CNTRLR » [Node 045] Sending firmware fragment 278 / 4179
2021-07-26 11:00:14.780 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 278/4179
2021-07-26T15:00:14.862Z CNTRLR » [Node 045] Sending firmware fragment 279 / 4179
2021-07-26 11:00:15.041 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 279/4179
2021-07-26T15:00:15.124Z CNTRLR » [Node 045] Sending firmware fragment 280 / 4179
2021-07-26 11:00:15.300 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 280/4179
2021-07-26T15:00:15.381Z CNTRLR » [Node 045] Sending firmware fragment 281 / 4179
2021-07-26 11:00:15.561 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 281/4179
2021-07-26T15:00:15.643Z CNTRLR » [Node 045] Sending firmware fragment 282 / 4179
2021-07-26 11:00:15.821 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 282/4179
2021-07-26T15:00:15.905Z CNTRLR » [Node 045] Sending firmware fragment 283 / 4179
2021-07-26 11:00:16.079 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 283/4179
2021-07-26T15:00:16.162Z CNTRLR » [Node 045] Sending firmware fragment 284 / 4179
2021-07-26 11:00:16.346 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 284/4179
2021-07-26T15:00:16.428Z CNTRLR » [Node 045] Sending firmware fragment 285 / 4179
2021-07-26 11:00:16.610 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 285/4179
2021-07-26T15:00:16.692Z CNTRLR » [Node 045] Sending firmware fragment 286 / 4179
2021-07-26 11:00:16.871 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 286/4179
2021-07-26T15:00:16.954Z CNTRLR » [Node 045] Sending firmware fragment 287 / 4179
2021-07-26 11:00:17.129 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 287/4179
2021-07-26T15:00:17.211Z CNTRLR » [Node 045] Sending firmware fragment 288 / 4179
2021-07-26 11:00:17.390 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 288/4179
2021-07-26T15:00:17.473Z CNTRLR » [Node 045] Sending firmware fragment 289 / 4179
2021-07-26 11:00:17.651 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 289/4179
2021-07-26T15:00:17.734Z CNTRLR » [Node 045] Sending firmware fragment 290 / 4179
2021-07-26 11:00:17.910 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 290/4179
2021-07-26T15:00:17.992Z CNTRLR » [Node 045] Sending firmware fragment 291 / 4179
2021-07-26 11:00:18.172 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 291/4179
2021-07-26T15:00:18.254Z CNTRLR » [Node 045] Sending firmware fragment 292 / 4179
2021-07-26 11:00:18.431 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 292/4179
2021-07-26T15:00:18.513Z CNTRLR » [Node 045] Sending firmware fragment 293 / 4179
2021-07-26 11:00:18.690 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 293/4179
2021-07-26T15:00:18.775Z CNTRLR » [Node 045] Sending firmware fragment 294 / 4179
2021-07-26 11:00:18.951 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 294/4179
2021-07-26T15:00:19.032Z CNTRLR » [Node 045] Sending firmware fragment 295 / 4179
2021-07-26 11:00:19.208 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 295/4179
2021-07-26T15:00:19.290Z CNTRLR » [Node 045] Sending firmware fragment 296 / 4179
2021-07-26 11:00:19.470 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 296/4179
2021-07-26T15:00:19.553Z CNTRLR » [Node 045] Sending firmware fragment 297 / 4179
2021-07-26 11:00:19.731 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 297/4179
2021-07-26T15:00:19.811Z CNTRLR » [Node 045] Sending firmware fragment 298 / 4179
2021-07-26 11:00:19.989 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 298/4179
2021-07-26T15:00:20.072Z CNTRLR » [Node 045] Sending firmware fragment 299 / 4179
2021-07-26 11:00:20.256 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 299/4179
2021-07-26T15:00:20.338Z CNTRLR » [Node 045] Sending firmware fragment 300 / 4179
2021-07-26 11:00:20.510 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 300/4179
2021-07-26T15:00:20.593Z CNTRLR » [Node 045] Sending firmware fragment 301 / 4179
2021-07-26 11:00:20.770 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 301/4179
2021-07-26T15:00:20.852Z CNTRLR » [Node 045] Sending firmware fragment 302 / 4179
2021-07-26 11:00:21.033 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 302/4179
2021-07-26T15:00:21.113Z CNTRLR » [Node 045] Sending firmware fragment 303 / 4179
2021-07-26 11:00:21.289 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 303/4179
2021-07-26T15:00:21.371Z CNTRLR » [Node 045] Sending firmware fragment 304 / 4179
2021-07-26 11:00:21.550 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 304/4179
2021-07-26T15:00:21.631Z CNTRLR » [Node 045] Sending firmware fragment 305 / 4179
2021-07-26 11:00:21.813 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 305/4179
2021-07-26T15:00:21.894Z CNTRLR » [Node 045] Sending firmware fragment 306 / 4179
2021-07-26 11:00:22.071 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 306/4179
2021-07-26T15:00:22.153Z CNTRLR » [Node 045] Sending firmware fragment 307 / 4179
2021-07-26 11:00:22.330 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 307/4179
2021-07-26T15:00:22.412Z CNTRLR » [Node 045] Sending firmware fragment 308 / 4179
2021-07-26 11:00:22.589 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 308/4179
2021-07-26T15:00:22.678Z CNTRLR » [Node 045] Sending firmware fragment 309 / 4179
2021-07-26 11:00:22.860 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 309/4179
2021-07-26T15:00:22.941Z CNTRLR » [Node 045] Sending firmware fragment 310 / 4179
2021-07-26 11:00:23.121 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 310/4179
2021-07-26T15:00:23.203Z CNTRLR » [Node 045] Sending firmware fragment 311 / 4179
2021-07-26 11:00:23.380 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 311/4179
2021-07-26T15:00:23.462Z CNTRLR » [Node 045] Sending firmware fragment 312 / 4179
2021-07-26 11:00:23.640 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 312/4179
2021-07-26T15:00:23.723Z CNTRLR » [Node 045] Sending firmware fragment 313 / 4179
2021-07-26 11:00:23.900 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 313/4179
2021-07-26T15:00:23.983Z CNTRLR » [Node 045] Sending firmware fragment 314 / 4179
2021-07-26 11:00:24.159 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 314/4179
2021-07-26T15:00:24.241Z CNTRLR » [Node 045] Sending firmware fragment 315 / 4179
2021-07-26 11:00:24.420 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 315/4179
2021-07-26T15:00:24.503Z CNTRLR » [Node 045] Sending firmware fragment 316 / 4179
2021-07-26 11:00:24.679 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 316/4179
2021-07-26T15:00:24.762Z CNTRLR » [Node 045] Sending firmware fragment 317 / 4179
2021-07-26 11:00:24.940 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 317/4179
2021-07-26T15:00:25.023Z CNTRLR » [Node 045] Sending firmware fragment 318 / 4179
2021-07-26 11:00:25.199 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 318/4179
2021-07-26T15:00:25.281Z CNTRLR » [Node 045] Sending firmware fragment 319 / 4179
2021-07-26 11:00:25.420 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 319/4179
2021-07-26T15:00:25.503Z CNTRLR » [Node 045] Sending firmware fragment 320 / 4179
2021-07-26 11:00:25.680 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 320/4179
2021-07-26T15:00:25.762Z CNTRLR » [Node 045] Sending firmware fragment 321 / 4179
2021-07-26 11:00:25.940 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 321/4179
2021-07-26T15:00:26.022Z CNTRLR » [Node 045] Sending firmware fragment 322 / 4179
2021-07-26 11:00:26.201 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 322/4179
2021-07-26T15:00:26.284Z CNTRLR » [Node 045] Sending firmware fragment 323 / 4179
2021-07-26 11:00:26.461 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 323/4179
2021-07-26T15:00:26.541Z CNTRLR » [Node 045] Sending firmware fragment 324 / 4179
2021-07-26 11:00:26.720 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 324/4179
2021-07-26T15:00:26.803Z CNTRLR » [Node 045] Sending firmware fragment 325 / 4179
2021-07-26 11:00:26.982 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 325/4179
2021-07-26T15:00:27.064Z CNTRLR » [Node 045] Sending firmware fragment 326 / 4179
2021-07-26 11:00:27.241 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 326/4179
2021-07-26T15:00:27.324Z CNTRLR » [Node 045] Sending firmware fragment 327 / 4179
2021-07-26 11:00:27.499 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 327/4179
2021-07-26T15:00:27.580Z CNTRLR » [Node 045] Sending firmware fragment 328 / 4179
2021-07-26 11:00:27.761 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 328/4179
2021-07-26T15:00:27.842Z CNTRLR » [Node 045] Sending firmware fragment 329 / 4179
2021-07-26 11:00:27.979 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 329/4179
2021-07-26T15:00:28.060Z CNTRLR » [Node 045] Sending firmware fragment 330 / 4179
2021-07-26 11:00:28.242 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 330/4179
2021-07-26 11:00:28.361 INFO ZWAVE: Node 13: value updated: 50-0-value-65537 14.394 => 14.412
2021-07-26 11:00:28.695 INFO ZWAVE: Node 13: value updated: 50-0-value-65537 14.412 => 14.412
2021-07-26T15:00:28.739Z CNTRLR » [Node 045] Sending firmware fragment 331 / 4179
2021-07-26 11:00:28.950 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 331/4179
2021-07-26T15:00:29.472Z CNTRLR » [Node 045] Sending firmware fragment 332 / 4179
2021-07-26 11:00:29.647 INFO ZWAVE: Node 13: value updated: 50-0-value-65537 14.412 => 14.412
2021-07-26 11:00:30.325 INFO ZWAVE: Node 13: value updated: 50-0-value-65537 14.412 => 14.412
2021-07-26 11:00:32.497 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 332/4179
2021-07-26T15:00:42.061Z CNTRLR » [Node 045] Sending firmware fragment 333 / 4179
2021-07-26 11:00:42.682 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 333/4179
2021-07-26T15:00:42.759Z CNTRLR » [Node 045] Sending firmware fragment 334 / 4179
2021-07-26T15:00:43.634Z CNTRLR » [Node 045] Sending firmware fragment 335 / 4179
2021-07-26 11:00:44.631 INFO ZWAVE: Controller status: Node 45 firmware update IN PROGRESS: 334/4179
2021-07-26T15:00:45.834Z CNTRLR » [Node 045] Sending firmware fragment 336 / 4179
2021-07-26T15:00:52.433Z SERIAL « 0x01050013990171 (7 bytes)
2021-07-26T15:00:52.435Z SERIAL » [ACK] (0x06)
2021-07-26T15:00:52.438Z DRIVER « [REQ] [SendData]
callback id: 153
transmit status: NoAck
2021-07-26T15:00:52.441Z CNTRLR [Node 045] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:00:52.943Z SERIAL » 0x013500132d2e7a06014f44026359737b771ad83a6d3d5f6a98ef920045b9a1d39 (55 bytes)
9a4009ec6bd899faf6b41677742acec93e9ced025999c
2021-07-26T15:00:52.944Z DRIVER » [Node 045] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 153
└─[FirmwareUpdateMetaDataCCReport]
report #: 335
is last: false
2021-07-26T15:00:52.950Z SERIAL « [ACK] (0x06)
2021-07-26T15:00:53.007Z SERIAL « 0x0104011301e8 (6 bytes)
2021-07-26T15:00:53.008Z SERIAL » [ACK] (0x06)
2021-07-26T15:00:53.008Z DRIVER « [RES] [SendData]
was sent: true
2021-07-26T15:00:58.192Z SERIAL « 0x01100004000d0a32022134000001f600003e (18 bytes)
2021-07-26T15:00:58.194Z CNTRLR [Node 013] [~] [Meter] value[66049]: 49.5 => 50.2 [Endpoint 0]
2021-07-26 11:00:58.195 INFO ZWAVE: Node 13: value updated: 50-0-value-66049 49.5 => 50.2
2021-07-26T15:00:58.196Z SERIAL » [ACK] (0x06)
2021-07-26T15:00:58.197Z DRIVER « [Node 013] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: W
rate type: Consumed
value: 50.2
time delta: 0 seconds
2021-07-26T15:01:01.743Z SERIAL « 0x01050013990171 (7 bytes)
2021-07-26T15:01:01.744Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:01.745Z DRIVER « [REQ] [SendData]
callback id: 153
transmit status: NoAck
2021-07-26T15:01:01.746Z CNTRLR [Node 045] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:01:02.248Z SERIAL » 0x013500132d2e7a06014f44026359737b771ad83a6d3d5f6a98ef920045b9a1d39 (55 bytes)
9a4009ec6bd899faf6b41677742acec93e9ced025999c
2021-07-26T15:01:02.249Z DRIVER » [Node 045] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 153
└─[FirmwareUpdateMetaDataCCReport]
report #: 335
is last: false
2021-07-26T15:01:02.256Z SERIAL « [ACK] (0x06)
2021-07-26T15:01:02.553Z SERIAL « 0x0104011301e8 (6 bytes)
2021-07-26T15:01:02.555Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:02.556Z DRIVER « [RES] [SendData]
was sent: true
2021-07-26T15:01:10.165Z SERIAL « 0x01050013990171 (7 bytes)
2021-07-26T15:01:10.166Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:10.169Z DRIVER « [REQ] [SendData]
callback id: 153
transmit status: NoAck
2021-07-26T15:01:10.172Z CNTRLR [Node 045] Node 45 did not respond after 3 attempts, it is presumed dead
2021-07-26 11:01:10.176 INFO ZWAVE: Node 45 is now dead
2021-07-26T15:01:10.176Z CNTRLR [Node 045] The node is now dead.
2021-07-26T15:01:10.181Z SERIAL » 0x013500132d2e7a0601509e6918b7a32936325932860de38a713a3ba06e2dbe2ed (55 bytes)
9130914eff7b7062d3fb52dfc607c93a1af7d1f259aff
2021-07-26T15:01:10.182Z DRIVER » [Node 045] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 154
└─[FirmwareUpdateMetaDataCCReport]
report #: 336
is last: false
2021-07-26T15:01:10.185Z SERIAL » 0x01030016ea (5 bytes)
2021-07-26T15:01:10.186Z DRIVER » [REQ] [SendDataAbort]
2021-07-26T15:01:10.187Z CNTRLR [Node 045] Error while sending firmware fragment: Failed to send the command a
fter 3 attempts (Status NoAck)
2021-07-26T15:01:10.187Z CNTRLR [Node 045] Error while sending firmware fragment: Node 45 did not respond afte
r 3 attempts, it is presumed dead
2021-07-26T15:01:10.192Z SERIAL « [ACK] (0x06)
2021-07-26T15:01:10.249Z SERIAL « 0x0104011301e8 (6 bytes)
2021-07-26T15:01:10.250Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:10.250Z DRIVER « [RES] [SendData]
was sent: true
2021-07-26T15:01:10.251Z DRIVER « [RES] [SendData] [unexpected]
was sent: true
2021-07-26T15:01:10.251Z DRIVER unexpected response, discarding...
2021-07-26T15:01:10.253Z SERIAL « [CAN] (0x18)
2021-07-26T15:01:15.506Z SERIAL « 0x010500139a0073 (7 bytes)
2021-07-26T15:01:15.507Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:15.508Z DRIVER « [REQ] [SendData]
callback id: 154
transmit status: OK
2021-07-26T15:01:15.509Z DRIVER handling request SendData (19)
2021-07-26T15:01:15.509Z DRIVER no handlers registered!
2021-07-26T15:01:15.834Z CNTRLR [Node 045] Firmware update timed out
2021-07-26 11:01:15.835 INFO ZWAVE: Controller status: Node 45 firmware update FINISHED: Status -1, Time: undefined
2021-07-26T15:01:23.282Z SERIAL « 0x010b0004002d057a05010151f6 (13 bytes)
2021-07-26T15:01:23.284Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:23.285Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCGet]
total # of reports: 1
report number: 337
2021-07-26 11:01:23.286 INFO ZWAVE: Node 45: has returned from the dead
2021-07-26T15:01:23.287Z CNTRLR [Node 045] The node is now alive.
2021-07-26T15:01:23.287Z CNTRLR « [Node 045] Received Firmware Update Get, but no firmware update is in progress
. Forcing the node to abort...
2021-07-26T15:01:23.291Z SERIAL » 0x013500132d2e7a068151964b67132332644169931a025171ae03600245348f294 (55 bytes)
abf1d16859f4c85f082f1dfc9e3568f775ef3c4259b13
2021-07-26T15:01:23.292Z DRIVER » [Node 045] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 155
└─[FirmwareUpdateMetaDataCCReport]
report #: 337
is last: true
2021-07-26T15:01:23.298Z SERIAL « [ACK] (0x06)
2021-07-26T15:01:23.303Z SERIAL « 0x0104011301e8 (6 bytes)
2021-07-26T15:01:23.303Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:23.304Z DRIVER « [RES] [SendData]
was sent: true
2021-07-26T15:01:26.349Z SERIAL « 0x010500139b0072 (7 bytes)
2021-07-26T15:01:26.351Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:26.351Z DRIVER « [REQ] [SendData]
callback id: 155
transmit status: OK
2021-07-26 11:01:30.545 INFO APP: GET /health/zwave 200 8.147 ms - 1875
2021-07-26 11:01:36.655 INFO APP: GET / 304 1.236 ms - -
2021-07-26 11:01:36.984 INFO APP: GET /api/auth-enabled 304 6.664 ms - -
2021-07-26 11:01:37.327 INFO APP: GET /api/settings 304 54.434 ms - -
2021-07-26 11:01:37.628 INFO APP: GET /api/auth-enabled 304 2.166 ms - -
2021-07-26 11:01:48.006 INFO ZWAVE: Calling api beginFirmwareUpdate with args: [
45,
'ZEN77_V10_0.gbl',
<Buffer eb 17 a6 03 08 00 00 00 00 00 00 03 01 01 00 00 fa 06 06 fa 10 00 00 00 5b 8c 02 00 12 83 50 b1 e3 b1 36 9b 23 92 75 a7 f9 07 07 f9 24 00 00 00 6c dc ... 167093 more bytes>,
0,
[length]: 4
]
2021-07-26T15:01:48.016Z SERIAL » 0x010900132d027a01259c08 (11 bytes)
2021-07-26T15:01:48.016Z DRIVER » [Node 045] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 156
└─[FirmwareUpdateMetaDataCCMetaDataGet]
2021-07-26T15:01:48.021Z SERIAL « [ACK] (0x06)
2021-07-26T15:01:48.025Z SERIAL « 0x0104011301e8 (6 bytes)
2021-07-26T15:01:48.026Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:48.027Z DRIVER « [RES] [SendData]
was sent: true
2021-07-26T15:01:49.353Z SERIAL « 0x01130004002d0d7a02027aa0070000ff00002801b9 (21 bytes)
2021-07-26T15:01:49.355Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
Function: "unknown" => "unknown"
2021-07-26T15:01:49.356Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
ivation: "unknown" => "unknown"
2021-07-26T15:01:49.357Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:49.358Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 634
firmware id: 40967
checksum: 0
firmware upgradable: true
max fragment size: 40
additional firmware IDs: []
hardware version: 1
continues to function: unknown
supports activation: unknown
2021-07-26T15:01:53.507Z SERIAL « 0x01130004002d0d7a02027aa0070000ff00002801b9 (21 bytes)
2021-07-26T15:01:53.509Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
Function: "unknown" => "unknown"
2021-07-26T15:01:53.509Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
ivation: "unknown" => "unknown"
2021-07-26T15:01:53.509Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:53.510Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 634
firmware id: 40967
checksum: 0
firmware upgradable: true
max fragment size: 40
additional firmware IDs: []
hardware version: 1
continues to function: unknown
supports activation: unknown
2021-07-26T15:01:55.915Z SERIAL « 0x01130004002d0d7a02027aa0070000ff00002801b9 (21 bytes)
2021-07-26T15:01:55.917Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
Function: "unknown" => "unknown"
2021-07-26T15:01:55.917Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
ivation: "unknown" => "unknown"
2021-07-26T15:01:55.918Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:55.919Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 634
firmware id: 40967
checksum: 0
firmware upgradable: true
max fragment size: 40
additional firmware IDs: []
hardware version: 1
continues to function: unknown
supports activation: unknown
2021-07-26T15:01:56.382Z SERIAL « 0x010500139c0174 (7 bytes)
2021-07-26T15:01:56.385Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:56.386Z DRIVER « [REQ] [SendData]
callback id: 156
transmit status: NoAck
2021-07-26T15:01:56.388Z CNTRLR [Node 045] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:01:56.891Z SERIAL » 0x010900132d027a01259c08 (11 bytes)
2021-07-26T15:01:56.892Z DRIVER » [Node 045] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 156
└─[FirmwareUpdateMetaDataCCMetaDataGet]
2021-07-26T15:01:56.894Z SERIAL « [ACK] (0x06)
2021-07-26T15:01:56.898Z SERIAL « 0x0104011301e8 (6 bytes)
2021-07-26T15:01:56.898Z SERIAL » [ACK] (0x06)
2021-07-26T15:01:56.899Z DRIVER « [RES] [SendData]
was sent: true
2021-07-26T15:02:05.538Z SERIAL « 0x010500139c0174 (7 bytes)
2021-07-26T15:02:05.540Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:05.541Z DRIVER « [REQ] [SendData]
callback id: 156
transmit status: NoAck
2021-07-26T15:02:05.544Z CNTRLR [Node 045] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:02:06.046Z SERIAL » 0x010900132d027a01259c08 (11 bytes)
2021-07-26T15:02:06.047Z DRIVER » [Node 045] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 156
└─[FirmwareUpdateMetaDataCCMetaDataGet]
2021-07-26T15:02:06.049Z SERIAL « [ACK] (0x06)
2021-07-26T15:02:06.105Z SERIAL « 0x0104011301e8 (6 bytes)
2021-07-26T15:02:06.106Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:06.107Z DRIVER « [RES] [SendData]
was sent: true
2021-07-26T15:02:14.310Z SERIAL « 0x010500139c0174 (7 bytes)
2021-07-26T15:02:14.311Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:14.312Z DRIVER « [REQ] [SendData]
callback id: 156
transmit status: NoAck
2021-07-26T15:02:14.314Z CNTRLR [Node 045] Node 45 did not respond after 3 attempts, it is presumed dead
2021-07-26 11:02:14.315 INFO ZWAVE: Node 45 is now dead
2021-07-26T15:02:14.316Z CNTRLR [Node 045] The node is now dead.
2021-07-26 11:02:14.317 INFO ZWAVE: Failed to send the command after 3 attempts (Status NoAck) beginFirmwareUpdate undefined
2021-07-26T15:02:22.128Z SERIAL « 0x01130004002d0d7a02027aa0070000ff00002801b9 (21 bytes)
2021-07-26T15:02:22.130Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
Function: "unknown" => "unknown"
2021-07-26T15:02:22.130Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
ivation: "unknown" => "unknown"
2021-07-26T15:02:22.130Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:22.131Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 634
firmware id: 40967
checksum: 0
firmware upgradable: true
max fragment size: 40
additional firmware IDs: []
hardware version: 1
continues to function: unknown
supports activation: unknown
2021-07-26 11:02:22.133 INFO ZWAVE: Node 45: has returned from the dead
2021-07-26T15:02:22.133Z CNTRLR [Node 045] The node is now alive.
2021-07-26T15:02:22.536Z SERIAL « 0x01130004002d0d7a02027aa0070000ff00002801b9 (21 bytes)
2021-07-26T15:02:22.537Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
Function: "unknown" => "unknown"
2021-07-26T15:02:22.538Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
ivation: "unknown" => "unknown"
2021-07-26T15:02:22.538Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:22.539Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 634
firmware id: 40967
checksum: 0
firmware upgradable: true
max fragment size: 40
additional firmware IDs: []
hardware version: 1
continues to function: unknown
supports activation: unknown
2021-07-26T15:02:23.205Z SERIAL « 0x01130004002d0d7a02027aa0070000ff00002801b9 (21 bytes)
2021-07-26T15:02:23.207Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
Function: "unknown" => "unknown"
2021-07-26T15:02:23.207Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
ivation: "unknown" => "unknown"
2021-07-26T15:02:23.208Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:23.209Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 634
firmware id: 40967
checksum: 0
firmware upgradable: true
max fragment size: 40
additional firmware IDs: []
hardware version: 1
continues to function: unknown
supports activation: unknown
2021-07-26T15:02:23.609Z SERIAL « 0x01130004002d0d7a02027aa0070000ff00002801b9 (21 bytes)
2021-07-26T15:02:23.611Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] continuesTo [Endpoint 0] [internal]
Function: "unknown" => "unknown"
2021-07-26T15:02:23.611Z CNTRLR [Node 045] [~] [Firmware Update Meta Data] supportsAct [Endpoint 0] [internal]
ivation: "unknown" => "unknown"
2021-07-26T15:02:23.612Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:23.612Z DRIVER « [Node 045] [REQ] [ApplicationCommand]
└─[FirmwareUpdateMetaDataCCMetaDataReport]
manufacturer id: 634
firmware id: 40967
checksum: 0
firmware upgradable: true
max fragment size: 40
additional firmware IDs: []
hardware version: 1
continues to function: unknown
supports activation: unknown
2021-07-26 11:02:35.698 INFO ZWAVE: Calling api beginFirmwareUpdate with args: [
45,
'ZEN77_V10_0.gbl',
<Buffer eb 17 a6 03 08 00 00 00 00 00 00 03 01 01 00 00 fa 06 06 fa 10 00 00 00 5b 8c 02 00 12 83 50 b1 e3 b1 36 9b 23 92 75 a7 f9 07 07 f9 24 00 00 00 6c dc ... 167093 more bytes>,
0,
[length]: 4
]
2021-07-26 11:02:35.700 INFO ZWAVE: Failed to start the update: A firmware upgrade is already in progress! beginFirmwareUpdate undefined
2021-07-26T15:02:49.917Z SERIAL « 0x010e0004001b0832022134000000d91a (16 bytes)
2021-07-26T15:02:49.919Z CNTRLR [Node 027] [~] [Meter] value[66049]: 22.2 => 21.7 [Endpoint 0]
2021-07-26 11:02:49.919 INFO ZWAVE: Node 27: value updated: 50-0-value-66049 22.2 => 21.7
2021-07-26T15:02:49.920Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:49.922Z DRIVER « [Node 027] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: W
rate type: Consumed
value: 21.7
time delta: 0 seconds
2021-07-26T15:02:50.243Z SERIAL « 0x01140004001b0e3202216400002650000000000000f9 (22 bytes)
2021-07-26T15:02:50.244Z CNTRLR [Node 027] [~] [Meter] value[65537]: 9.806 => 9.808 [Endpoint 0]
2021-07-26 11:02:50.244 INFO ZWAVE: Node 27: value updated: 50-0-value-65537 9.806 => 9.808
2021-07-26T15:02:50.245Z SERIAL » [ACK] (0x06)
2021-07-26T15:02:50.246Z DRIVER « [Node 027] [REQ] [ApplicationCommand]
└─[MeterCCReport]
type: Electric
scale: kWh
rate type: Consumed
value: 9.808
time delta: 0 seconds
2021-07-26 11:03:09.417 INFO ZWAVE: Calling api beginFirmwareUpdate with args: [
45,
'ZEN77_V10_0.gbl',
<Buffer eb 17 a6 03 08 00 00 00 00 00 00 03 01 01 00 00 fa 06 06 fa 10 00 00 00 5b 8c 02 00 12 83 50 b1 e3 b1 36 9b 23 92 75 a7 f9 07 07 f9 24 00 00 00 6c dc ... 167093 more bytes>,
0,
[length]: 4
]
2021-07-26 11:03:09.419 INFO ZWAVE: Failed to start the update: A firmware upgrade is already in progress! beginFirmwareUpdate undefined
{"mode":"full","isActive":false}
The above was taken from the Debug menu within the ZwaveJS2MQTT web UI
and here is what's taken from the Z-Wave JS Logs option within Home Assistant. It took some time to navigate over, so here's what's was gathered. Please advise on what else specifically I should grab.
2021-07-26T15:00:52.441Z CNTRLR [Node 045] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:01:01.746Z CNTRLR [Node 045] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:01:10.172Z CNTRLR [Node 045] Node 45 did not respond after 3 attempts, it is presumed dead
2021-07-26T15:01:10.176Z CNTRLR [Node 045] The node is now dead.
2021-07-26T15:01:10.187Z CNTRLR [Node 045] Error while sending firmware fragment: Failed to send the command a
fter 3 attempts (Status NoAck)
2021-07-26T15:01:10.187Z CNTRLR [Node 045] Error while sending firmware fragment: Node 45 did not respond afte
r 3 attempts, it is presumed dead
2021-07-26T15:01:10.251Z DRIVER unexpected response, discarding...
2021-07-26T15:01:15.509Z DRIVER no handlers registered!
2021-07-26T15:01:15.834Z CNTRLR [Node 045] Firmware update timed out
2021-07-26T15:01:23.287Z CNTRLR [Node 045] The node is now alive.
2021-07-26T15:01:23.287Z CNTRLR « [Node 045] Received Firmware Update Get, but no firmware update is in progress
. Forcing the node to abort...
2021-07-26T15:01:56.388Z CNTRLR [Node 045] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:02:05.544Z CNTRLR [Node 045] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-07-26T15:02:14.314Z CNTRLR [Node 045] Node 45 did not respond after 3 attempts, it is presumed dead
2021-07-26T15:02:14.316Z CNTRLR [Node 045] The node is now dead.
2021-07-26T15:02:22.133Z CNTRLR [Node 045] The node is now alive.
```
[zwave_js.log](https://github.com/zwave-js/node-zwave-js/files/6879242/zwave_js.log)
Big fixed, should come over soon. Easy change.
2 Likes
jhein
August 5, 2021, 4:25am
10
Thanks for investigating & reporting!
jhein
August 15, 2021, 12:52am
11
I am on zwavejs2mqtt-addon 0.23.4 now, which should be ZwaveJS2Mqtt v5.4.5 according to the changelog, but I still can’t update target 1 on that one Red Dimmer. Could it be a hardware problem too? I remember having other problems with that one wall switch.
hmmm - strange. I was able to upgrade all 27 of my switches on an older version of zwavejs2mqtt on HA without issue.
Have you tried using the 'official updater to rule zwavejs in or out? Found here . If you have a windows laptop, its pretty simple to shut down HA, pull the USB stick, and use that on the windows machine to do the updates. You can skip all the exclusion/inclusion steps because your zwave usb has the device map already.
That might be a way to narrow in on hardware vs software problems.
Yep I opened it back up, he fixed it (again) and closed it again, but we will have to wait for the next rev for it to work. It was confirmed working by another contributor who actually built a new docker installation and tested with the actual switch though.
Should be soon ™.
1 Like
@jhein release was posted 5 hours ago if you have docker and want to build up your own temp installation outside of HA.
Probably a day or two away from frenck posting the HA add-on version.
2 Likes
jhein
August 17, 2021, 10:46pm
16
@kreene1987 worked like a charm this time. THANK YOU!
2 Likes