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.

Performance downgrade in node interviewing after 6.6.0

See original GitHub issue

Hello, I am seeing a performance downgrade in node interviewing after updating to zwavejs 6.6.0. Prior to 6.6.0, the nodes completed the interview in about 30-60 minutes (60 nodes). However, after updating to 6.6.0 I am at over 2 hours with about 25% of the nodes being complete and many of the powered nodes showing as Dead, which has never happened before.

Log appears to be full of NoAck messages:

02:10:38.185 DRIVER » [Node 092] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      171
                      └─[NoOperationCC]
02:10:38.187 SERIAL « [ACK]                                                                   (0x06)
02:10:38.193 SERIAL « 0x0104011301e8                                                       (6 bytes)
02:10:38.194 SERIAL » [ACK]                                                                   (0x06)
02:10:38.194 DRIVER « [RES] [SendData]
                        was sent: true
02:10:38.709 SERIAL « 0x01080004005c0284072e                                              (10 bytes)
02:10:38.710 SERIAL » [ACK]                                                                   (0x06)
02:10:38.713 DRIVER « [Node 092] [REQ] [ApplicationCommand]
                      └─[WakeUpCCWakeUpNotification]
02:10:38.714 CNTRLR « [Node 092] received wakeup notification
02:10:51.338 SERIAL « 0x01070013ab01052367                                                 (9 bytes)
02:10:51.338 SERIAL » [ACK]                                                                   (0x06)
02:10:51.340 DRIVER « [REQ] [SendData]
                        callback id:     171
                        transmit status: NoAck
02:10:51.343 CNTRLR   [Node 092] Node 92 did not respond after 1 attempts, it is presumed dead
02:10:51.348 CNTRLR   [Node 092] The node is now dead.
02:10:51.349 SERIAL » 0x010800135c010025ac30                                              (10 bytes)
02:10:51.349 DRIVER » [Node 092] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      172
                      └─[NoOperationCC]
02:10:51.350 SERIAL » 0x01030016ea                                                         (5 bytes)
02:10:51.350 DRIVER » [REQ] [SendDataAbort]
02:10:51.350 CNTRLR   [Node 092] ping failed: Failed to send the command after 1 attempts (Status No
                      Ack)
02:10:51.350 CNTRLR   [Node 092] ping failed: Node 92 did not respond after 1 attempts, it is presum
                      ed dead
02:10:51.350 CNTRLR » [Node 092] querying node info...
02:10:51.351 CNTRLR » [Node 092] pinging the node...
02:10:51.352 CNTRLR   [Node 092] Interview attempt (4/5) failed, node is dead.
02:10:51.359 SERIAL « [ACK]                                                                   (0x06)
02:10:52.362 CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
                      n 100 ms.
02:10:52.463 SERIAL » 0x01030016ea                                                         (5 bytes)
02:10:52.464 DRIVER » [REQ] [SendDataAbort]
02:10:52.545 SERIAL « 0x0104011301e8                                                       (6 bytes)
02:10:52.546 SERIAL » [ACK]                                                                   (0x06)
02:10:52.547 DRIVER « [RES] [SendData]
                        was sent: true
02:10:52.549 DRIVER « [RES] [SendData]                                                  [unexpected]
                        was sent: true
02:10:52.549 DRIVER   unexpected response, discarding...
02:10:52.550 DRIVER « [RES] [SendData]                                                  [unexpected]
                        was sent: true
02:10:52.550 DRIVER   unexpected response, discarding...
02:10:52.566 SERIAL « [CAN]                                                                   (0x18)
02:10:52.568 CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
                      n 1100 ms.
02:10:52.569 SERIAL « [CAN]                                                                   (0x18)
02:10:53.670 SERIAL » 0x01030016ea                                                         (5 bytes)
02:10:53.671 DRIVER » [REQ] [SendDataAbort]
02:10:53.809 SERIAL « [ACK]                                                                   (0x06)
02:10:53.817 SERIAL » 0x010800135c010025ad31                                              (10 bytes)
02:10:53.817 DRIVER » [Node 092] [REQ] [SendData]
                      │ transmit options: 0x25
                      │ callback id:      173
                      └─[NoOperationCC]
02:10:53.819 SERIAL « [ACK]                                                                   (0x06)

I have attached Zwavejs silly logs. zwavejs_359.log

Issue Analytics

State:
Created 3 years ago
Comments:16 (8 by maintainers)

Top GitHub Comments

1reaction

AlCalzonecommented, Mar 5, 2021

Good luck 😐

1reaction

maivorbimcommented, Mar 5, 2021

Thank you for your time and effort to reach out to external parties! I was afraid of this answer, but cannot lie that I have also thought of it myself. Especially since using the stick method is something that is not recommened in the HA docs: https://www.home-assistant.io/docs/z-wave/adding

I will try a couple of more heals and if that does not solve it I will have to reinclude all devices again. Thank you again for your help. Closing this issue for now as it appears to be specific to my installation.