node-zwave-js: Motion sensor connected via USB power stops detecting motion

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?

NO, my problem is NOT within Home Assistant or the ZWave JS integration

Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?

NO, my problem is NOT within Z-Wave JS UI

Checklist

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.

Describe the bug

What causes the bug?

What do you observe? After restarting the host system, some the Aeotec multisensor 7 sensors stop sending motion events.

What did you expect to happen? Never

Steps to reproduce the behavior:

Restart the ZwaveJS
Trigger motion event in a multisensor 7 device.

Log is filled with:

2023-04-22T02:45:04.494Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -73 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_NoSPAN
2023-04-22T02:45:04.498Z CNTRLR » [Node 020] No SPAN is established yet, cannot decode command. Requesting a non
                                  ce...
2023-04-22T02:45:04.510Z SERIAL » 0x012000a90114149f027f01d6ce365a83c881a8168e0b874c6c55ba05000000009 (34 bytes)
                                  ec2
2023-04-22T02:45:04.512Z DRIVER » [Node 020] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x05
                                  │ callback id:      158
                                  └─[Security2CCNonceReport]
                                      sequence number:  127
                                      SOS:              true
                                      MOS:              false
                                      receiver entropy: 0xd6ce365a83c881a8168e0b874c6c55ba
2023-04-22T02:45:04.519Z SERIAL « [ACK]                                                                   (0x06)
2023-04-22T02:45:04.522Z SERIAL « 0x010401a90152                                                       (6 bytes)
2023-04-22T02:45:04.524Z SERIAL » [ACK]                                                                   (0x06)
2023-04-22T02:45:04.526Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2023-04-22T02:45:04.534Z SERIAL « 0x011d00a99e00000100b77f7f7f7f00000300000000030100007f7f7f7f7f1d    (31 bytes)
2023-04-22T02:45:04.535Z SERIAL » [ACK]                                                                   (0x06)
2023-04-22T02:45:04.538Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            158
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -73 dBm
                                    ACK channel no.:        0
                                    TX channel no.:         0
2023-04-22T02:45:04.547Z SERIAL « 0x012a00a8000114219f0367011241badc6634d40626ed61ea8238361db49db6900 (44 bytes)
                                  bf276a24eac39ded800b890
2023-04-22T02:45:04.551Z SERIAL » [ACK]                                                                   (0x06)
2023-04-22T02:45:04.554Z CNTRLR   [Node 020] [~] [Battery] level: 100 => 100                        [Endpoint 0]
2023-04-22T02:45:04.556Z CNTRLR   [Node 020] [~] [Battery] isLow: false => false                    [Endpoint 0]
2023-04-22T02:45:04.559Z DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -72 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 103
                                    │ extensions:
                                    │ · type: SPAN
                                    │   sender EI: 0xbadc6634d40626ed61ea8238361db49d
                                    └─[BatteryCCReport]
                                        level:  100
                                        is low: false

Device information

Manufacturer: Aeotec Model name: Multisensor 7 Node ID in your network: 20

How are you using `node-zwave-js`?

zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
ioBroker.zwave2 adapter (please specify version)
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)
Other (please describe)

Which branches or versions?

version: node-zwave-js branch: zwave-js-ui branch:

Did you change anything?

yes (please describe)

If yes, what did you change?

No response

Did this work before?

Don’t know, this is a new device

If yes, where did it work?

No response

Attach Driver Logfile

zwave_js.log

About this issue

Original URL
State: closed
Created a year ago
Comments: 29 (11 by maintainers)

Most upvoted comments

I think I fundamentally dont understand the migration process. It seems that the config is now managed inside the add-on itself. The instructions are not very clear.

If you are using Z-Wave JS UI, then you configure it in its settings, not by the add-on settings. This documented in the add-on docs.

After setting the config inside the ZwaveUI addon, my network basically goes down:

Because the network cache is stored in the add-on, and there’s no migration of that. The cache needs to be re-populated by interviews, as Al has said. If you don’t want to re-interview, you can follow the minimal downtime migration guide.

kpine on May 12, 2023