Loose all nodes after updating from 8.22.0 to 8.22.1

[jyvern]

Checklist

• [ ] I am not using Home Assistant. Or: a developer has told me to come here.
• [X] I have checked the troubleshooting section and my problem is not described there.
• [X] I have read the changelog and my problem is not mentioned there.

Deploy method

Docker

Z-Wave JS UI version

8.22.1

ZwaveJS version

11.8.0

Describe the bug

After autoupdating with watchtower to version 8.22.1, all nodes disapeared and I have this kind of message : 2023-08-07T20:27:24.115Z CNTRLR [Node 006] is unknown - discarding received command... 2023-08-07T20:27:24.116Z DRIVER « [Node 006] [REQ] [ApplicationCommand] [discarded] └─[CRC16CCCommandEncapsulation] └─[MeterCCReport] type: Electric scale: V rate type: Consumed value: 233.207 time delta: 5 seconds prev. value: 233.71

To Reproduce

Just try the 8.22.1 version

Expected behavior

No more nodes displayed in UI

Additional context

No response

[danodemano]

I just upgraded to 8.22.1 from 8.18.1 (docker) and noticed the same thing. My controller comes up as online but the log is flooded with those [discarded] messages and none of the nodes show up. It's for sure something specific to this version as a rollback to 8.18.1 resolved it. I have an older AEON Labs Gen5 USB stick if that's relevant. Example log entry:

2023-08-07T21:25:04.295Z SERIAL « 0x01180004002812320221740006bff600000000000000000000f3              (26 bytes)
2023-08-07T21:25:04.296Z SERIAL » [ACK]                                                                   (0x06)
2023-08-07T21:25:04.296Z CNTRLR   [Node 040] is unknown - discarding received command...
2023-08-07T21:25:04.296Z DRIVER « [Node 040] [REQ] [ApplicationCommand]                              [discarded]
                                  └─[MeterCCReport]
                                      type:       Electric
                                      scale:      W
                                      rate type:  Consumed
                                      value:      442.358
                                      time delta: 0 seconds

[icemarkom]

I just had the same happen to me. I am using AEOTEC Z-Stick (I believe the original v5). Downgrading back to 8.22.0 resolved the immediate issue.

[stevemcgf]

I also experienced the same problem. Downgrading fixes the issue.

[chrisdfw]

I am seeing the same issue.

[kpine]

Please post a full driver debug log, not short snippets. https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

For a workaround, disable soft reset in the Z-Wave settings panel. https://github.com/hassio-addons/addon-zwave-js-ui/issues/553#issuecomment-1668734975

[djak250]

Same. So glad a rollback was all that was needed... would've been terrible to build the whole network again.

[snowboardjoe]

Disabling the soft reset option immediately resolved the problem--no roll back needed here.

[digitalcardboard]

Please post a full driver debug log, not short snippets. https://zwave-js.github.io/zwave-js-ui/#/troubleshooting/generating-logs?id=driver-logs

For a workaround, disable soft reset in the Z-Wave settings panel. hassio-addons/addon-zwave-js-ui#553 (comment)

This got me going again, but would love to understand a proper resolution.

[mt0321]

Home Assistant Z-Wave JS UI add on issue for reference: https://github.com/hassio-addons/addon-zwave-js-ui/issues/553

Controller: Nortek GoControl HUSBZB-1

I don't have full debug logs because I rolled back (to 8.19.0 - what I had on hand) and that fixed it. But here are the logs I do have.

                                    · UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
                                    · UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
                                    · FirmwareUpdateNVM (0x78)
                                    · GetRoutingInfo (0x80)
                                    · UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
                                    · GetPriorityRoute (0x92)
                                    · SetPriorityRoute (0x93)
                                    · UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
                                    · UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
                                    · UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
                                    · UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
                                    · UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
                                    · UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
                                    · UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
                                    · UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
                                    · UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
                                    · UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
                                    · UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
                                    · UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
                                    · UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
                                    · undefined (0xee)
                                    · UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
2023-08-08T05:00:44.324Z CNTRLR   Performing soft reset...
2023-08-08T05:00:44.346Z CNTRLR   Waiting for the controller to reconnect...
2023-08-08T05:00:45.851Z CNTRLR   Waiting for the Serial API to start...
2023-08-08T05:00:48.978Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-08T05:00:49.065Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-08T05:00:49.168Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-08T05:00:49.266Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-08T05:00:50.854Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
                                  nds...
2023-08-08T05:00:50.882Z CNTRLR   Serial API responded
2023-08-08T05:00:51.164Z CNTRLR   querying version info...
2023-08-07 22:00:54.769 INFO APP: GET /health/zwave 200 71.085 ms - 2140
2023-08-08T05:01:18.964Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-07 22:01:24.982 INFO APP: GET /health/zwave 200 6.188 ms - 2140
2023-08-08T05:01:48.964Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-07 22:01:55.261 INFO APP: GET /health/zwave 200 7.692 ms - 2140
2023-08-08T05:02:18.981Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-07 22:02:25.462 INFO APP: GET /health/zwave 200 4.956 ms - 2140
2023-08-08T05:02:48.962Z CNTRLR   [Node 056] is unknown - discarding received command...
2023-08-07 22:02:55.664 INFO APP: GET /health/zwave 200 3.815 ms - 2140
2023-08-08T05:03:07.507Z DRIVER   Dropping message because network keys are not set or the driver is not yet rea
                                  dy to receive secure messages.
2023-08-08T05:03:08.100Z DRIVER   Dropping message because network keys are not set or the driver is not yet rea
                                  dy to receive secure messages.

Pattern repeats...

2023-08-08T05:08:13.511Z DRIVER   Dropping message because network keys are not set or the driver is not yet rea
                                  dy to receive secure messages.

[jonofmac]

Also seeing this issue. 8.22.1 breaks without any errors in my case. It doesn't ever seem to successfully connect to my zwave stick. Just says it wasn't ready, then never retries. 8.22.0, it retries and everything works.

[AlCalzone]

I can reproduce with my old Razberry.

[jonofmac]

I did a boot with the log set to silly. Not a lot in it after several seconds.

Seems to have something to do with secure nodes, which I do have on my network.

2023-08-08T08:08:56.781Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:08:58.024Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:08:58.557Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:08:58.634Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:09:00.178Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:09:00.718Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:09:03.361Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:09:03.897Z DRIVER   Dropping message because the driver is not ready to handle it yet.
2023-08-08T08:09:07.790Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:07.794Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:08.437Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:10.218Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:10.763Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:11.298Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:13.603Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:14.137Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:20.266Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.
2023-08-08T08:09:20.808Z DRIVER   Dropping message because network keys are not set or the driver is not yet ready to receive secure messages.```

[ocalvo]

I have lost about 50% of the nodes from my network. Down to 63 nodes from 138 nodes.

What steps can I take to recover without having to readd all the nodes?