Zniffer fails to decode S2 messages after stopping Z-Wave network

[kpine]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?

I was using the Zniffer in ZUI, sniffing network activity from a separate ZUI instance. I called driver.resetSPAN(256) to allow the Zniffer to decrypt messages, which was working. Then I stopped the ZUI running the Z-Wave network (USB stick still plugged in), and afterwards was getting exceptions on the application console and the Zniffer could no longer decode the S2 messages.

I purposefully ran ZUI in separate instances to make it easier to stop the network.

In this setup the node was a Long Range node.

What did you expect to happen instead?

The Zniffer would still be able to decode the messages even with the other Z-Wave JS offline. I repeated the experiment using the Silicon Labs Zniffer application and it was successful.

Steps to reproduce the behavior:

1. Start a ZUI instance to run the Z-Wave network
2. Start another ZUI instance to run the Zniffer and start it
3. Use driver function driver.resetSPAN(256) to force re-sync to allow Zniffer to decrypt
4. Cause some traffic to be produced, e.g. trigger a door open sensor, observe zniffer traffic is decrypted
5. Stop the ZUI running the Z-Wave network
6. Cause some traffic to be produced, e.g. trigger a door open sensor, observe exceptions on the console and decode errors in the Zniffer

Anything else we should know?

Here's a screen capture showing the same scenario but with SiLabs Zniffer. You can see on line 7 was when I stopped ZUI, and line 24 was when I unplugged the controller. The Zniffer was still able to capture and decode the messages.

Software versions

Driver (node-zwave-js): 14.3.8

Z-Wave JS UI: 9.30.1

Z-Wave Controller (Stick/Dongle/...)

UZB7 for Z-Wave network
800 dev kit for Zniffer

Device information

ZSE41 door sensor included with LR

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

Zniffer console log

2025-02-06 20:55:59.678 INFO APP: Version: 9.30.1
2025-02-06 20:55:59.679 INFO APP: Application path:/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui
  ______  __          __                      _  _____     _    _ _____ 
 |___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
    / /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |  
   / /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |  
  / /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_ 
 /_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|

2025-02-06 20:55:59.682 WARN STORE: scenes.json not found
Logging to file:
	/tmp/zui2/store/logs/zniffer_2025-02-06.log
ZWaveError: The message payload is invalid! (ZW0003)
    at validatePayloadInternal (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/@zwave-js/core/src/util/misc.ts:42:9)
    at Function.validatePayload.fail (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/@zwave-js/core/src/util/misc.ts:58:35)
    at parseMPDU (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/zwave-js/src/lib/zniffer/MPDU.ts:131:20)
    at Zniffer.handleDataMessage (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/zwave-js/src/lib/zniffer/Zniffer.ts:544:17)
    at Zniffer.serialport_onData (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/zwave-js/src/lib/zniffer/Zniffer.ts:485:15)
    at ZnifferParser.emit (node:events:524:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushObjectMode (node:internal/streams/readable:538:3)
    at ZnifferParser.Readable.push (node:internal/streams/readable:393:5)
    at ZnifferParser._transform (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/@zwave-js/serial/src/parsers/ZnifferParser.ts:87:10) {
  code: 3,
  context: 'Unsupported channel 4. MPDU payload: 0xd050444f10000127810095009f032a00eb58fb6ab2586ff7143f2fbf225cc13275007ac0a7',
  transactionSource: undefined
}
ZWaveError: The message payload is invalid! (ZW0003)
    at validatePayloadInternal (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/@zwave-js/core/src/util/misc.ts:42:9)
    at Function.validatePayload.fail (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/@zwave-js/core/src/util/misc.ts:58:35)
    at parseMPDU (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/zwave-js/src/lib/zniffer/MPDU.ts:131:20)
    at Zniffer.handleDataMessage (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/zwave-js/src/lib/zniffer/Zniffer.ts:544:17)
    at Zniffer.serialport_onData (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/zwave-js/src/lib/zniffer/Zniffer.ts:485:15)
    at ZnifferParser.emit (node:events:524:28)
    at addChunk (node:internal/streams/readable:561:12)
    at readableAddChunkPushObjectMode (node:internal/streams/readable:538:3)
    at ZnifferParser.Readable.push (node:internal/streams/readable:393:5)
    at ZnifferParser._transform (/nix/store/m48r7nvb80cvvg0yjjybdh0d9nx45vrx-zwave-js-ui-9.30.1/lib/node_modules/zwave-js-ui/node_modules/@zwave-js/serial/src/parsers/ZnifferParser.ts:87:10) {
  code: 3,
  context: 'Unsupported channel 4. MPDU payload: 0xd050444f10000127810095099f032b0085d4ab5a65f80ef32597d5160a4fab1fc717399cf7',
  transactionSource: undefined
}

Zniffer debug log snippet

The first message was right before I shut down the ZUI instance, the message after is after shutting down ZUI. The decode errors continue, but there were only the two exceptions.

2025-02-07T04:57:33.497Z ZNIFFR « [256 » 001]                                                         [d050444f]
                                  │ sequence no.:       0
                                  │ channel:            3
                                  │ protocol/data rate: Z-Wave Long Range, 100 kbit/s
                                  │ TX power:           -6 dBm
                                  │ RSSI:               -76 dBm
                                  │ noise floor:        -107 dBm
                                  │ ack requested:      true
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 42
                                    │ security class:  S2_Authenticated
                                    └─[SupervisionCCGet]
                                      │ session id:      54
                                      │ request updates: false
                                      └─[NotificationCCReport]
                                          notification type:   Access Control
                                          notification status: 255
                                          notification state:  Window/door is open
2025-02-07T04:57:33.577Z ZNIFFR « [256 » 001]                                                         [d050444f]
                                  │ sequence no.:       0
                                  │ channel:            3
                                  │ protocol/data rate: Z-Wave Long Range, 100 kbit/s
                                  │ TX power:           -3 dBm
                                  │ RSSI:               -72 dBm
                                  │ noise floor:        -107 dBm
                                  │ ack requested:      true
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_CannotDecode
<.. more of the same ..>

[zwave-js-bot]

👋 Hey @kpine!

It looks like you copied the contents of a logfile. Please attach it as a file instead, so it is easier to work with.
Note: You can just drag & drop files into the textbox. Just make sure to use a supported file extension like .log or .txt