AlCalzone
AlCalzone
See https://github.com/zwave-js/node-zwave-js/issues/3892
A similar issue happens on the Heatit Z-TRM6 DC. Somehow this even leads to the parameter name getting deleted from the config metadata: ``` 2025-12-05 13:37:20.627 DRIVER ยป [Node 002]...
Can you collect Z-Wave logs so I can see in which context this appears?
Yes, loglevel debug please. I'll need several seconds before the crash, ideally just capture the last minute or so, including the error trace like you just did.
Thanks that should help narrow it down. Looking at that log, I think the error message is also wrong. The gist of the problem: **Device sends report while SPAN out...
@eric10k93 I'll work on fixing the crash, but the root cause is that this device has poor connectivity (and the noise level for the Long Range channel is a tad...
The controller is already using the maximum transmit power, and the incoming frames that are picked up show an RSSI ``` RSSI: -100 dBm ``` below the background noise near...
Finding a good position can really be a matter of trial and error. For example, the background noise on my desk is about 10 dBm less than on the top...
TODO: - [x] Handle Request Protocol CC Encryption command
As of the last PR, Z-Wave JS can include simulated devices with NLS and perform protocol-level encryption for the simulated controller. The Z-Wave stack draft has a few issues though...