#Z Wave Controller Unresponsive

1 messages · Page 1 of 1 (latest)

idle geyser
#

Hello,
I’m running HA version on Raspberry Pi 5.

  • Core: 2024.8.2
  • Supervisor: 2024.08.0
  • Operating System: 13.1
  • Interface utilisateur: 20240809.0
  • Z-Wave JS: 0.6.2
For zwave I’m using an Aeotec Gen 5 Zwave stick and Fibaro devices.
I’m using the add-on Z-Wave JS (Current version: 0.6.2) and the Zwave integration.
At one point it stopped working and I could not reach my devices at all.
I’ve tried:
  • to restart HA.
  • To unplung and replug the Aeotec stick
  • To restart Z-Wave JS.
  • To reinstall Z-Wave JS.
  • To also reinstall the integration.
  • To reload the Zwave Network.
  • To Rebuild Network route.
  • To Re-Configure the server.
  • To add an USB extender cable in case the f interference and rebuild the route.
  • I’m not using zwave JS UI.
  • I also reinstalled HA from scratch.
I’d like to avoid to restet the Aeoted stick and to have to add again all the device.
    What I see in the logs:
    …

2024-08-14T13:42:18.780Z CNTRLR The controller is unresponsive
2024-08-14T13:42:18.781Z DRIVER Controller missed Send Data callback. Attempting to recover…
2024-08-14T13:42:18.782Z CNTRLR Performing soft reset…
2024-08-14T13:42:19.787Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
…

grand canopy
#

Check logs if it always happens after a SendData request for a specific device

#

Should be around 30 seconds before that I think

idle geyser
idle geyser
# idle geyser <@173493678256422913> thanks a lot for your answer. In the log of the Z-Wave JS ...

@grand canopy what I see in debug mode:

2024-08-25T13:02:53.887Z DRIVER » [Node 018] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 19
└─[NoOperationCC]
2024-08-25T13:02:53.889Z SERIAL « [ACK] (0x06)
2024-08-25T13:02:53.898Z SERIAL « 0x0104011301e8 (6 bytes)
2024-08-25T13:02:53.898Z SERIAL » [ACK] (0x06)
2024-08-25T13:02:53.899Z DRIVER « [RES] [SendData]
was sent: true
2024-08-25T13:03:13.902Z SERIAL » 0x01030016ea (5 bytes)
2024-08-25T13:03:13.904Z DRIVER » [REQ] [SendDataAbort]
2024-08-25T13:03:23.903Z CNTRLR The controller is unresponsive
2024-08-25T13:03:23.905Z DRIVER Controller missed Send Data callback.

idle geyser
# idle geyser <@173493678256422913> thanks a lot for your answer. In the log of the Z-Wave JS ...

@grand canopy after I have the following in the logs:
controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-08-25T13:09:26.192Z DRIVER » [REQ] [GetControllerVersion]
2024-08-25T13:09:26.192Z SERIAL » 0x01030015e9 (5 bytes)
2024-08-25T13:09:27.194Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2024-08-25T13:09:28.296Z DRIVER » [REQ] [GetControllerVersion]
2024-08-25T13:09:28.297Z SERIAL » 0x01030015e9 (5 bytes)
2024-08-25T13:09:29.301Z CNTRLR Serial API did not respond, giving up
2024-08-25T13:09:29.302Z DRIVER destroying driver instance...
2024-08-25T13:09:29.304Z DRIVER all queues idle

idle geyser
grand canopy
#

Just to be sure, it's always node 18 triggering the issue?

#

If so, can you try removing it from the network?

idle geyser
# grand canopy Just to be sure, it's always node 18 triggering the issue?

@grand canopy thanks for your answer. In fact the node related to the SendData triggering the issue is not only Node 18, I updated the HA Core version and after if was Node 7. There is 25 devices and 10 are not ready among these 10 know 3 that are missing (2 plugs and a smoke detector). For the the rest I do not know what they are (I used a zwave stick from previous installation not done myself ). Then I can’t remove the devices with the classic removal process process, then I tried to remove the nodes that I do not know from he node interface in the Z Wave JS integration but I could’nt with the following error message:
zwave_error: Z-Wave error 202 - Failed to send the message after 3 attempts (ZW0202)

idle geyser
# idle geyser <@173493678256422913> thanks for your answer. In fact the node related to the Se...

@grand canopy I’ve restarted the Z Wave JS add on and I have:

[Node 028] ping successful
2024-08-25T21:40:51.248Z CNTRLR [Node 028] Interviewing Version...
2024-08-25T21:40:51.248Z CNTRLR » [Node 028] querying the CC version for Version...
2024-08-25T21:41:12.508Z CNTRLR [Node 007] The node did not respond after 1 attempts, it is presumed dead
2024-08-25T21:41:12.508Z CNTRLR [Node 007] The node is dead.
2024-08-25T21:41:12.510Z CNTRLR [Node 007] ping failed: The node did not acknowledge the command (ZW0204)
2024-08-25T21:41:12.510Z CNTRLR » [Node 007] querying node info...
2024-08-25T21:41:42.527Z CNTRLR The controller is unresponsive
2024-08-25T21:41:42.528Z DRIVER Controller missed Send Data callback. Attempting to recover...
2024-08-25T21:41:42.529Z CNTRLR Performing soft reset...
2024-08-25T21:41:43.534Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-08-25T21:41:44.637Z CNTRLR

idle geyser
grand canopy
#

I'm not sure from the logs if it's actually node 7. Make sure to put the logs on level debug

idle geyser
# grand canopy I'm not sure from the logs if it's actually node 7. Make sure to put the logs on...

@grand canopy when I restart the add on before the node part I also have:

registered
2024-08-26T08:17:24.483Z CNTRLR querying Serial API capabilities...
2024-08-26T08:17:24.637Z SERIAL » 0x01030007fb (5 bytes)
2024-08-26T08:17:24.638Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-08-26T08:17:25.656Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2024-08-26T08:17:25.758Z DRIVER » [REQ] [GetSerialApiCapabilities]
2024-08-26T08:17:25.759Z SERIAL » 0x01030007fb (5 bytes)
2024-08-26T08:17:26.762Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.

grand canopy
#

Sounds like you need to unplug the stick for a few seconds

idle geyser
# grand canopy Sounds like you need to unplug the stick for a few seconds

@grand canopy , I unplugged the stick for 5 min put it back and now I have the following in the logs:

2024-08-26T19:54:21.195Z DRIVER » [Node 018] [REQ] [SendData]
│ transmit options: 0x25
│ callback id: 19
└─[NoOperationCC]
2024-08-26T19:54:21.196Z SERIAL « [ACK] (0x06)
2024-08-26T19:54:21.205Z SERIAL « 0x0104011301e8 (6 bytes)
2024-08-26T19:54:21.206Z SERIAL » [ACK] (0x06)
2024-08-26T19:54:21.206Z DRIVER « [RES] [SendData]
was sent: true
New client
2024-08-26T19:54:41.207Z SERIAL » 0x01030016ea (5 bytes)
2024-08-26T19:54:41.209Z DRIVER » [REQ] [SendDataAbort]
2024-08-26T19:54:51.209Z CNTRLR The controller is unresponsive
2024-08-26T19:54:51.210Z DRIVER Controller missed Send Data callback. Attempting to recover...
2024-08-26T19:54:51.211Z CNTRLR Performing soft reset...
2024-08-26T19:54:51.214Z SERIAL » 0x01030008f4 (5 bytes)
2024-08-26T19:54:51.214Z DRIVER » [REQ] [SoftReset]
2024-08-26T19:54:52.217Z CNTRLR Failed to execute controller command after 1/

grand canopy
#

So, node 18 again. Does the stick ever recover on its own? If so, wait 10 minutes or so, then try excluding it.
If not, and you're on firmware 1.2, I could edit the node out of the controllers memory.

idle geyser
# grand canopy So, node 18 again. Does the stick ever recover on its own? If so, wait 10 minute...

@grand canopy The stick recovered once on its own but it was 12 days ago.
Since then it did not happen again, then I can’t exclude it myself.
Regarding firmware I’m on 1.1 please see below:

"firmwareVersion": "1.1",
"deviceConfig": {
"filename": "/data/db/devices/0x0086/zw090.json",
"isEmbedded": true,
"manufacturer": "AEON Labs",
"manufacturerId": 134,
"label": "ZW090",
"description": "Z\u2010Stick Gen5 USB Controller",

Is it possible for you to do something with this firmware version ?

Would it be possible for you to have a deeper look if I provide you with the access to my HA?

Thanks again for your help.

grand canopy
#

No, it would have to be 1.2
You can try disabling soft reset and the automatic controller recovery in the options and see if it recovers on its own then.

#

Does node 18 still exist btw? Can you bring it closer to the controller temporarily?

idle geyser
# grand canopy No, it would have to be 1.2 You can try disabling soft reset and the automatic c...

@grand canopy , I disabled soft reset and the automatic controller recovery option in the add on, and it recovered on its own, some devices are still not working but most are.
The steak is then in start ready all the time.
Regarding node 18, I tried to do a « remove failed » in the integration but it failed as before with the same Z-Wave error 202. I was able to do a « Delete » in the integration but I think the node will still be paired with the controller and that it won’t change anything?