Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[bug] Invalid data with Danalock V3-BTZE
See original GitHub issueVersion
Build/Run method
- Docker
- PKG
- Manually built (git clone - npm install - npm run build )
zwavejs2mqtt version: 1.0.0-beta.0.8c826f1 (Windows Server 2019 Datacenter)
Describe the bug Danalock V3-BTZE not updating status. ZWave-JS logs showing Message with invalid data received. Dropping it
To Reproduce Manually turn Danalock or use proprietary app to change lock status.
Expected behavior It should update with every status change of the phisical lock status.
Additional context This might be bug in node-zwave-js, I cannot decide. Node info: node_2.zip ZWave.log: zwavejs_108.zip Relevant zwave.log excerpt : From 19:36:24.884 to 19:36:26.529: Normal operation (open attempt and required update went well) From 19:36:43.504 to 19:36:44.992: Erroneus operation (close attempt returns invalid data message)
19:36:24.884 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:24.884 SERIAL » [ACK] (0x06)
19:36:24.885 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:24.893 SERIAL » 0x01110013020a9880a0c05375e6895f9c056765 (19 bytes)
19:36:24.893 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 103
└─[SecurityCCNonceReport]
nonce: 0xa0c05375e6895f9c
19:36:24.895 SERIAL « [ACK] (0x06)
19:36:24.901 SERIAL « 0x0104011301e8 (6 bytes)
19:36:24.901 SERIAL » [ACK] (0x06)
19:36:24.902 DRIVER « [RES] [SendData]
was sent: true
19:36:24.932 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:24.933 SERIAL » [ACK] (0x06)
19:36:24.933 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:24.937 SERIAL » 0x01030016ea (5 bytes)
19:36:24.937 DRIVER » [REQ] [SendDataAbort]
19:36:24.943 SERIAL « [ACK] (0x06)
19:36:24.945 SERIAL » 0x01110013020a9880b4902ce551b8e3d60568b1 (19 bytes)
19:36:24.945 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 104
└─[SecurityCCNonceReport]
nonce: 0xb4902ce551b8e3d6
19:36:24.947 SERIAL « [ACK] (0x06)
19:36:24.954 SERIAL « 0x0104011301e8 (6 bytes)
19:36:24.955 SERIAL » [ACK] (0x06)
19:36:24.956 DRIVER « [RES] [SendData]
was sent: true
19:36:24.976 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:24.976 SERIAL » [ACK] (0x06)
19:36:24.977 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:24.984 SERIAL » 0x01030016ea (5 bytes)
19:36:24.984 DRIVER » [REQ] [SendDataAbort]
19:36:24.988 SERIAL « [ACK] (0x06)
19:36:24.989 SERIAL » 0x01110013020a9880598ec55ea71e8ee405691e (19 bytes)
19:36:24.989 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 105
└─[SecurityCCNonceReport]
nonce: 0x598ec55ea71e8ee4
19:36:24.999 SERIAL « [ACK] (0x06)
19:36:25.003 SERIAL « 0x0104011300e9 (6 bytes)
19:36:25.004 SERIAL » [ACK] (0x06)
19:36:25.004 DRIVER « [RES] [SendData]
was sent: false
19:36:25.005 CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
19:36:25.021 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:25.021 SERIAL » [ACK] (0x06)
19:36:25.022 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:25.029 SERIAL » 0x01030016ea (5 bytes)
19:36:25.030 DRIVER » [REQ] [SendDataAbort]
19:36:25.035 SERIAL « [ACK] (0x06)
19:36:25.038 SERIAL » 0x01110013020a9880f18088948062d21b056ac4 (19 bytes)
19:36:25.038 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 106
└─[SecurityCCNonceReport]
nonce: 0xf18088948062d21b
19:36:25.044 SERIAL « [ACK] (0x06)
19:36:25.045 SERIAL « 0x0104011300e9 (6 bytes)
19:36:25.045 SERIAL » [ACK] (0x06)
19:36:25.046 DRIVER « [RES] [SendData]
was sent: false
19:36:25.046 CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
19:36:25.051 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:25.051 SERIAL » [ACK] (0x06)
19:36:25.052 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:25.064 SERIAL » 0x01030016ea (5 bytes)
19:36:25.064 DRIVER » [REQ] [SendDataAbort]
19:36:25.076 SERIAL « [ACK] (0x06)
19:36:25.077 SERIAL » 0x01110013020a9880cd3a4d0e9b3fdaec056ba5 (19 bytes)
19:36:25.078 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 107
└─[SecurityCCNonceReport]
nonce: 0xcd3a4d0e9b3fdaec
19:36:25.081 SERIAL « [ACK] (0x06)
19:36:25.082 SERIAL « 0x0104011300e9 (6 bytes)
19:36:25.082 SERIAL » [ACK] (0x06)
19:36:25.084 DRIVER « [RES] [SendData]
was sent: false
19:36:25.085 CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
19:36:25.187 SERIAL » 0x01110013020a9880cd3a4d0e9b3fdaec056ba5 (19 bytes)
19:36:25.188 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 107
└─[SecurityCCNonceReport]
nonce: 0xcd3a4d0e9b3fdaec
19:36:25.190 SERIAL « [ACK] (0x06)
19:36:25.191 SERIAL « 0x0104011300e9 (6 bytes)
19:36:25.191 SERIAL » [ACK] (0x06)
19:36:25.192 DRIVER « [RES] [SendData]
was sent: false
19:36:25.192 CNTRLR The controller response indicated failure after 2/3 attempts. Scheduling next
try in 1100 ms.
19:36:26.204 SERIAL « 0x010700136b000066e6 (9 bytes)
19:36:26.204 SERIAL » [ACK] (0x06)
19:36:26.205 DRIVER « [REQ] [SendData]
callback id: 107
transmit status: OK
19:36:26.205 DRIVER handling request SendData (19)
19:36:26.205 DRIVER no handlers registered!
19:36:26.251 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:26.252 SERIAL » [ACK] (0x06)
19:36:26.252 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:26.259 SERIAL » 0x01030016ea (5 bytes)
19:36:26.265 DRIVER » [REQ] [SendDataAbort]
19:36:26.267 SERIAL « [ACK] (0x06)
19:36:26.268 SERIAL » 0x01110013020a9880b8baedf25e63ddab056cd2 (19 bytes)
19:36:26.268 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 108
└─[SecurityCCNonceReport]
nonce: 0xb8baedf25e63ddab
19:36:26.270 SERIAL « [ACK] (0x06)
19:36:26.272 SERIAL « 0x0104011300e9 (6 bytes)
19:36:26.272 SERIAL » [ACK] (0x06)
19:36:26.273 DRIVER « [RES] [SendData]
was sent: false
19:36:26.276 CNTRLR The controller response indicated failure after 1/3 attempts. Scheduling next
try in 100 ms.
19:36:26.317 SERIAL « 0x0123000400021d9881301d559b0c15a71d5307a067c46b977f05e2a086302217a (37 bytes)
3ba82988d
19:36:26.317 DRIVER Message with invalid data received. Dropping it:
0x0123000400021d9881301d559b0c15a71d5307a067c46b977f05e2a086302217a3ba82988d
19:36:26.317 SERIAL » [ACK] (0x06)
19:36:26.378 SERIAL » 0x01110013020a9880b8baedf25e63ddab056cd2 (19 bytes)
19:36:26.378 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 108
└─[SecurityCCNonceReport]
nonce: 0xb8baedf25e63ddab
19:36:26.380 SERIAL « [ACK] (0x06)
19:36:26.389 SERIAL « 0x0104011301e8 (6 bytes)
19:36:26.389 SERIAL » [ACK] (0x06)
19:36:26.390 DRIVER « [RES] [SendData]
was sent: true
19:36:26.394 SERIAL « 0x010700136c00000c8b (9 bytes)
19:36:26.394 SERIAL » [ACK] (0x06)
19:36:26.395 DRIVER « [REQ] [SendData]
callback id: 108
transmit status: OK
19:36:26.411 SERIAL « 0x010700136c00000285 (9 bytes)
19:36:26.412 SERIAL » [ACK] (0x06)
19:36:26.412 DRIVER « [REQ] [SendData]
callback id: 108
transmit status: OK
19:36:26.413 DRIVER handling request SendData (19)
19:36:26.417 DRIVER no handlers registered!
19:36:26.447 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:26.448 SERIAL » [ACK] (0x06)
19:36:26.449 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:26.456 SERIAL » 0x01110013020a98807b06ee70c01fd356056d3c (19 bytes)
19:36:26.457 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 109
└─[SecurityCCNonceReport]
nonce: 0x7b06ee70c01fd356
19:36:26.459 SERIAL « [ACK] (0x06)
19:36:26.465 SERIAL « 0x0104011301e8 (6 bytes)
19:36:26.466 SERIAL » [ACK] (0x06)
19:36:26.469 DRIVER « [RES] [SendData]
was sent: true
19:36:26.487 SERIAL « 0x010700136d00000385 (9 bytes)
19:36:26.487 SERIAL » [ACK] (0x06)
19:36:26.488 DRIVER « [REQ] [SendData]
callback id: 109
transmit status: OK
19:36:26.519 SERIAL « 0x0121000400021b9881f0a3492de1883565393e749769b1067e7bd5f449411badd (35 bytes)
dfb52
19:36:26.519 SERIAL » [ACK] (0x06)
19:36:26.524 CNTRLR [Node 002] [~] [Door Lock] currentMode: 255 => 0 [Endpoint 0]
19:36:26.525 CNTRLR [Node 002] [~] [Door Lock] outsideHandlesCanOpenDoor: true,false, [Endpoint 0]
false,false => true,false,false,false
19:36:26.526 CNTRLR [Node 002] [~] [Door Lock] insideHandlesCanOpenDoor: true,false,f [Endpoint 0]
alse,false => true,false,false,false
19:36:26.527 CNTRLR [Node 002] [~] [Door Lock] latchStatus: "closed" => "open" [Endpoint 0]
19:36:26.528 CNTRLR [Node 002] [~] [Door Lock] boltStatus: "locked" => "unlocked" [Endpoint 0]
19:36:26.529 CNTRLR [Node 002] [~] [Door Lock] doorStatus: "closed" => "open" [Endpoint 0]
19:36:26.529 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCCommandEncapsulation]
│ sequenced: false
└─[DoorLockCCOperationReport]
current mode: Unsecured
active outside handles: true, false, false, false
active inside handles: true, false, false, false
latch status: open
bolt status: unlocked
door status: open
19:36:43.504 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:43.504 SERIAL » [ACK] (0x06)
19:36:43.505 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:43.507 SERIAL » 0x01110013020a988047df587d988d7b71056e24 (19 bytes)
19:36:43.507 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 110
└─[SecurityCCNonceReport]
nonce: 0x47df587d988d7b71
19:36:43.510 SERIAL « [ACK] (0x06)
19:36:43.516 SERIAL « 0x0104011301e8 (6 bytes)
19:36:43.517 SERIAL » [ACK] (0x06)
19:36:43.518 DRIVER « [RES] [SendData]
was sent: true
19:36:43.543 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:43.543 SERIAL » [ACK] (0x06)
19:36:43.544 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:43.546 SERIAL » 0x01030016ea (5 bytes)
19:36:43.546 DRIVER » [REQ] [SendDataAbort]
19:36:43.554 SERIAL « [ACK] (0x06)
19:36:43.555 SERIAL » 0x01110013020a988058a6b56914d24381056fa1 (19 bytes)
19:36:43.555 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 111
└─[SecurityCCNonceReport]
nonce: 0x58a6b56914d24381
19:36:43.557 SERIAL « [ACK] (0x06)
19:36:43.568 SERIAL « 0x0104011301e8 (6 bytes)
19:36:43.568 SERIAL » [ACK] (0x06)
19:36:43.569 DRIVER « [RES] [SendData]
was sent: true
19:36:43.646 SERIAL « 0x010700136f0000098d (9 bytes)
19:36:43.647 SERIAL » [ACK] (0x06)
19:36:43.647 DRIVER « [REQ] [SendData]
callback id: 111
transmit status: OK
19:36:43.682 SERIAL « 0x0123000400021d988120ea396aa70b16dcba8e274cd8a1d7c0971647dffc0f974 (37 bytes)
1374cd98e
19:36:43.683 DRIVER Message with invalid data received. Dropping it:
0x0123000400021d988120ea396aa70b16dcba8e274cd8a1d7c0971647dffc0f9741374cd98e
19:36:43.683 SERIAL » [ACK] (0x06)
19:36:43.728 SERIAL « 0x0123000400021d988120ea396aa70b16dcba8e274cd8a1d7c0971647dffc0f974 (37 bytes)
1374cd98e
19:36:43.728 DRIVER Message with invalid data received. Dropping it:
0x0123000400021d988120ea396aa70b16dcba8e274cd8a1d7c0971647dffc0f9741374cd98e
19:36:43.728 SERIAL » [ACK] (0x06)
19:36:44.916 SERIAL « 0x010700136f0000880c (9 bytes)
19:36:44.916 SERIAL » [ACK] (0x06)
19:36:44.916 DRIVER « [REQ] [SendData]
callback id: 111
transmit status: OK
19:36:44.917 DRIVER handling request SendData (19)
19:36:44.917 DRIVER no handlers registered!
19:36:44.938 SERIAL « 0x0108000400020298402b (10 bytes)
19:36:44.938 SERIAL » [ACK] (0x06)
19:36:44.939 DRIVER « [Node 002] [REQ] [ApplicationCommand]
└─[SecurityCCNonceGet]
19:36:44.945 SERIAL » 0x01110013020a98807e63b0f192e356e0057003 (19 bytes)
19:36:44.945 DRIVER » [Node 002] [REQ] [SendData]
│ transmit options: 0x05
│ callback id: 112
└─[SecurityCCNonceReport]
nonce: 0x7e63b0f192e356e0
19:36:44.947 SERIAL « [ACK] (0x06)
19:36:44.953 SERIAL « 0x0104011301e8 (6 bytes)
19:36:44.953 SERIAL » [ACK] (0x06)
19:36:44.954 DRIVER « [RES] [SendData]
was sent: true
19:36:44.967 SERIAL « 0x0121000400021b9881e89460da2ebfa1e70ebd901ec46b4a1c583b1eea74d665e (35 bytes)
508b2
19:36:44.968 DRIVER Message with invalid data received. Dropping it:
0x0121000400021b9881e89460da2ebfa1e70ebd901ec46b4a1c583b1eea74d665e508b2
19:36:44.968 SERIAL » [ACK] (0x06)
19:36:44.991 SERIAL « 0x01070013700000049f (9 bytes)
19:36:44.992 SERIAL » [ACK] (0x06)
19:36:44.992 DRIVER « [REQ] [SendData]
callback id: 112
transmit status: OK
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (9 by maintainers)
Top Results From Across the Web
[bug] Invalid data with Danalock V3-BTZE · Issue #1402 - GitHub
Describe the bug. Danalock V3-BTZE not updating status. ZWave-JS logs showing Message with invalid data received. Dropping it. To Reproduce
Read more >FAQ Danalock V3
FAQ Danalock V3, frequently asked questions on Danalock smart lock installation and usage. Didn't you find what you're looking for? Contact Support.
Read more >Danalock V3-BTZE not working in openHAB 3.1.0.M4 - Bindings
It seems that Danalock V3 stopped working with last Openhab update. ... Deleted data direct from controller with Z-Wave PC Controller 5.
Read more >Danalock V3 BT Euro
Violating these guidelines may be dangerous, illegal or otherwise detrimental. Further detailed information is provided in this manual. Terms of use. The ...
Read more >My Danalock v3 Z-Wave Configuration 5. Step Solution
The only one i get is “Poly-control Danalock V3 BTZE” The biggest problem for me is that i cant do the Call service...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@LordMike can you put that into a separate issue please? This is unrelated aside from the fact that it displays the same error.
I already had a “fix” for this, but it aborts the ongoing transmission instead of just not queuing the duplicate response. I’ll post a PR shortly for you to test.