Skip to content

Z-Wave JS 0.10.0 Crash #3952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
gmrandom opened this issue Feb 25, 2025 · 7 comments
Open

Z-Wave JS 0.10.0 Crash #3952

gmrandom opened this issue Feb 25, 2025 · 7 comments

Comments

@gmrandom
Copy link

Describe the issue you are experiencing

Updated to 0.10.0, started experiencing sporadic Z-Wave JS crashes.

The addon log shows this trace right before crashing

ZWaveError: Security class for node 6 is not yet known! (ZW1402)
    at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6059:23)
    at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6259:28)
    at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6377:29)
    at Proxy.sendReport (file:///usr/src/node_modules/@zwave-js/cc/src/cc/SupervisionCC.ts:102:20)
    at reply (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5140:9)
    at Driver.handleRequest (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5185:12)
    at Driver.handleUnsolicitedMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4689:5)
[01:29:50] WARNING: Halt add-on

I have restored previous version backup and issue has not occurred again since.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Z-Wave JS

What is the version of the add-on?

0.10.0

Steps to reproduce the issue

  1. Install 0.10.0
  2. Wait
    ...

System Health information

There are currently no repairs pending

Anything in the Supervisor logs that might be useful for us?

No supervisor logs look clean.

Anything in the add-on logs that might be useful for us?

ZWaveError: Security class for node 6 is not yet known! (ZW1402)
    at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6059:23)
    at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6259:28)
    at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6377:29)
    at Proxy.sendReport (file:///usr/src/node_modules/@zwave-js/cc/src/cc/SupervisionCC.ts:102:20)
    at reply (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5140:9)
    at Driver.handleRequest (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5185:12)
    at Driver.handleUnsolicitedMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4689:5)
[01:29:50] WARNING: Halt add-on

Additional information

No response
@gmrandom gmrandom mentioned this issue Feb 25, 2025
Open
@AlCalzone
Copy link
Contributor

Any chance you have driver logs on loglevel debug from before the crash? I would need some context of what lead to this error.

@gmrandom
Copy link
Author

Unfortunately no, I rolled back to 0.9.0 and the problem is not reproable there. Does the stack trace/error code above help?

@AlCalzone
Copy link
Contributor

No I'd need to see communication from before to know how it came to that situation

@gmrandom
Copy link
Author

gmrandom commented Mar 1, 2025

I was able to retrieve the log file from the crash, however the log level is info, not debug.

core_zwave_js_2025-02-24T01-50-29.379Z.log

This was referenced Mar 11, 2025
Open
Open
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Mar 31, 2025
@AlCalzone
Copy link
Contributor

Sorry, I missed that reply. There actually seems to be something in the logs that might explain the behavior:

2025-02-24T01:29:37.479Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 166
                                    │ extensions:
                                    │ · type: SPAN  sender EI: 0x518087a72192d4dedca14bf55b962c33
                                    │ security class:  S2_Authenticated
                                    └─[SupervisionCCGet]
                                      │ session id:      48
                                      │ request updates: false
                                      └─[NotificationCCReport]
                                          notification type:   System
                                          notification status: 255
                                          notification event:  Heartbeat
2025-02-24T01:29:37.480Z CNTRLR   [Node 006] [Notification]
                                    type:  System
                                    event: Heartbeat
2025-02-24T01:29:37.529Z DRIVER   Dropping message with invalid payload
2025-02-24T01:29:37.529Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Duplicate command (sequence number 166)
2025-02-24T01:29:37.674Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_CannotDecode
2025-02-24T01:29:37.675Z CNTRLR   [Node 006] Message authentication failed, cannot decode command.
2025-02-24T01:29:37.710Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_CannotDecode
2025-02-24T01:29:37.710Z CNTRLR   [Node 006] Message authentication failed, cannot decode command.
2025-02-24T01:29:38.339Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_CannotDecode
2025-02-24T01:29:38.340Z CNTRLR   [Node 006] Message authentication failed, cannot decode command.
2025-02-24T01:29:38.443Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_CannotDecode
2025-02-24T01:29:38.443Z CNTRLR   [Node 006] Message authentication failed, cannot decode command.
2025-02-24T01:29:38.522Z DRIVER   Dropping message with invalid payload
2025-02-24T01:29:38.522Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Duplicate command (sequence number 166)
2025-02-24T01:29:38.888Z DRIVER   Dropping message with invalid payload
2025-02-24T01:29:38.888Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Duplicate command (sequence number 166)
2025-02-24T01:29:41.507Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_CannotDecode
2025-02-24T01:29:41.507Z CNTRLR   [Node 006] Message authentication failed, cannot decode command.
2025-02-24T01:29:41.566Z DRIVER   Dropping message with invalid payload
2025-02-24T01:29:41.566Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Duplicate command (sequence number 167)
2025-02-24T01:29:41.688Z DRIVER   Dropping message with invalid payload
2025-02-24T01:29:41.688Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Duplicate command (sequence number 167)
2025-02-24T01:29:41.698Z DRIVER « [REQ] [SendData]
                                    callback id:            80
                                    transmit status:        NoAck, took 5740 ms
                                    routing attempts:       34
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Resort to Direct
                                    TX channel no.:         1
                                    route failed here:      11 -> 6
2025-02-24T01:29:41.703Z DRIVER » [Node 006] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      81
                                  └─[Security2CCNonceGet]
                                      sequence number: 156
2025-02-24T01:29:41.712Z DRIVER « [RES] [SendData]
                                    was sent: true
2025-02-24T01:29:42.005Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_NoSPAN
2025-02-24T01:29:42.005Z CNTRLR » [Node 006] No SPAN is established yet, cannot decode command. Requesting a non
                                  ce...
2025-02-24T01:29:50.836Z DRIVER « [REQ] [SendData]
                                    callback id:            81
                                    transmit status:        NoAck, took 9120 ms
                                    routing attempts:       33
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    routing scheme:         Explorer Frame
                                    TX channel no.:         1
                                    route failed here:      15 -> 6
2025-02-24T01:29:50.839Z DRIVER » [Node 006] [REQ] [SendData]
                                  │ transmit options: 0x05
                                  │ callback id:      82
                                  └─[Security2CCNonceReport]
                                      sequence number:  157
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0xc6a3086bcc4808f0fd83e435c9988163
ZWaveError: Security class for node 6 is not yet known! (ZW1402)
    at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6059:23)
    at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6259:28)
    at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6377:29)
    at Proxy.sendReport (file:///usr/src/node_modules/@zwave-js/cc/src/cc/SupervisionCC.ts:102:20)
    at reply (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5140:9)
    at Driver.handleRequest (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5185:12)
    at Driver.handleUnsolicitedMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4689:5)
[01:29:50] WARNING: �[33mHalt add-on�[0m

@AlCalzone AlCalzone mentioned this issue Mar 31, 2025
Open
@AlCalzone
Copy link
Contributor

I've opened an upstream issue for this: zwave-js/zwave-js#7702

@github-actions github-actions bot removed the stale label Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gmrandom @AlCalzone