Hi All,
I have some issue’s with my z-wave integration and I can’t fix it by my self/with other topics.
My setup: Hardware
Raspberry PI 4B
AEON 700 Zwave stick
→ FW: v7.20.2
→ SDK: v7.20.2
Software
HAOS
Core2024.2.5
Supervisor2024.02.1
Operating System12.0
Frontend20240207.1
Zwave JS UI
*zwave-js-ui: 9.9.0
*zwave-js: 12.4.4
So, my first stick (AEON 500+) gave some problems (unexpected error) so I have shifted to the EAON 700 series. After (the firmware update and) the NVM restore I was able to retrieve all of the nodes in the Zwave JS ui integration.
After the configuration I was not able to control any of the Zwave devices. The controller is unable to transmit (‘controller is unable to transmit’ error). Beside that this happens the controller is also not able to move on after the interview of the nodes. The nodes are stuck on the ‘node info’ (and a few on ‘protocol info’).
So I have done some research on the internet;
[Controller is unable to transmit - only fix is to pull the plug!]
[Minimote (DSA03XXX-ZW) Interview stuck at Nodeinfo, ones which have been completed going back to Nodeinfo stage #1155]
In the next comment I will post a part of the log file. When I check the logs I would believe that the controller is receiving a lot of data about the nodes.
When I perform a soft reset the controller is able to work for about 2 - 5 min. After this time the unable to transmit problem occurs.
2024-03-04 22:18:40.701 INFO Z-WAVE: Controller status: Controller is unable to transmit
2024-03-04T21:18:40.747Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:40.787Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:40.849Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:40.875Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:41.045Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:41.069Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:41.132Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:41.259Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:41.339Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:41.384Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:44.780Z CNTRLR The controller is no longer jammed
2024-03-04 22:18:44.781 INFO Z-WAVE: Controller status: Controller is Ready
2024-03-04T21:18:44.783Z CNTRLR [Node 054] ping failed: Failed to send the command after 5 attempts (ZW0202)
2024-03-04T21:18:44.865Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:18:44.890Z CNTRLR The controller is jammed
2024-03-04 22:18:44.891 INFO Z-WAVE: Controller status: Controller is unable to transmit
2024-03-04T21:18:44.941Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:44.985Z DRIVER Dropping message with invalid payload
2024-03-04T21:18:48.972Z CNTRLR The controller is no longer jammed
2024-03-04 22:18:48.973 INFO Z-WAVE: Controller status: Controller is Ready
2024-03-04T21:18:48.974Z CNTRLR [Node 054] ping failed: Failed to send the command after 5 attempts (ZW0202)
2024-03-04 22:18:51.003 INFO APP: GET /health/zwave 301 1.049 ms - 191
2024-03-04T21:19:03.270Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:19:03.293Z CNTRLR The controller is jammed
2024-03-04 22:19:03.294 INFO Z-WAVE: Controller status: Controller is unable to transmit
2024-03-04T21:19:03.308Z DRIVER Dropping message with invalid payload
2024-03-04T21:19:07.297Z DRIVER Dropping message with invalid payload
2024-03-04T21:19:07.382Z CNTRLR The controller is no longer jammed
2024-03-04 22:19:07.383 INFO Z-WAVE: Controller status: Controller is Ready
2024-03-04T21:19:07.385Z CNTRLR [Node 054] ping failed: Failed to send the command after 5 attempts (ZW0202)
After the soft reset:
2024-03-04T21:21:31.765Z DRIVER Node 70, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
2024-03-04T21:21:31.766Z DRIVER Node 70, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
2024-03-04T21:21:31.767Z DRIVER Node 70, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
2024-03-04T21:21:31.770Z DRIVER Node 70, Endpoint 1: Trying to access endpoint instance before Multi Channel i
nterview
2024-03-04 22:21:31.773 INFO Z-WAVE: [Node 070] Metadata updated: 50-1-value-66049
2024-03-04 22:21:31.775 INFO Z-WAVE: [Node 070] Value added: 50-1-value-66049 => 0
2024-03-04T21:21:32.770Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:21:34.535Z DRIVER Dropping message with invalid payload
2024-03-04 22:21:50.315 INFO Z-WAVE: [Node 040] Metadata updated: 50-1-value-66049
2024-03-04 22:21:50.317 INFO Z-WAVE: [Node 040] Value updated: 50-1-value-66049 0 => 0
2024-03-04 22:21:50.326 INFO Z-WAVE: [Node 040] Metadata updated: 50-1-value-66049
2024-03-04 22:21:50.328 INFO Z-WAVE: [Node 040] Value updated: 50-1-value-66049 0 => 0
2024-03-04 22:21:51.727 INFO APP: GET /health/zwave 301 1.438 ms - 191
2024-03-04T21:21:52.379Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:21:52.650Z DRIVER Dropping message with invalid payload
2024-03-04T21:21:54.506Z CNTRLR [Node 054] The node did not respond after 1 attempts, it is presumed dead
2024-03-04T21:21:54.510Z CNTRLR [Node 054] ping failed: The node did not acknowledge the command (ZW0204)
2024-03-04T21:21:54.511Z CNTRLR [Node 054] ping failed: The node did not respond after 1 attempts, it is presu
med dead (ZW0202)
2024-03-04T21:21:56.511Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:22:10.727Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:14.882Z CNTRLR [Node 054] The node did not respond after 1 attempts, it is presumed dead
2024-03-04T21:22:14.884Z CNTRLR [Node 054] ping failed: The node did not acknowledge the command (ZW0204)
2024-03-04T21:22:15.265Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:22:16.105Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:16.199Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:16.340Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:16.402Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:16.428Z DRIVER Dropping message with invalid payload
2024-03-04 22:22:21.850 INFO APP: GET /health/zwave 301 1.824 ms - 191
2024-03-04 22:22:32.206 INFO Z-WAVE: [Node 029] Metadata updated: 49-1-Power
2024-03-04 22:22:32.210 INFO Z-WAVE: [Node 029] Value updated: 49-1-Power 0 => 0
2024-03-04 22:22:32.219 INFO Z-WAVE: [Node 029] Metadata updated: 49-1-Power
2024-03-04 22:22:32.221 INFO Z-WAVE: [Node 029] Value updated: 49-1-Power 0 => 0
2024-03-04T21:22:34.754Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:22:34.809Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:34.854Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:38.929Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:38.952Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:45.290Z CNTRLR [Node 054] The node is causing the controller to become unresponsive, it is pr
esumed dead
2024-03-04T21:22:45.293Z CNTRLR [Node 054] ping failed: Timeout while waiting for a callback from the controll
er (ZW0200)
2024-03-04T21:22:45.294Z CNTRLR [Node 054] ping failed: The node is causing the controller to become unrespons
ive, it is presumed dead (ZW0202)
2024-03-04T21:22:46.588Z CNTRLR The controller is jammed
2024-03-04 22:22:46.589 INFO Z-WAVE: Controller status: Controller is unable to transmit
2024-03-04T21:22:46.638Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:46.717Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:46.882Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:46.931Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:47.014Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:47.152Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:47.425Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:47.617Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:47.945Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:48.201Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:22:48.269Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:48.350Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:48.359Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:48.418Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:48.485Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:48.941Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:48.985Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.029Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.129Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.211Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.278Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.583Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.670Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.693Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.737Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.753Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.779Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.793Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.810Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.860Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.892Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.967Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:49.984Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.012Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.057Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.094Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.109Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.132Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.162Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.227Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.300Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.315Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.372Z DRIVER Dropping message with invalid payload
2024-03-04T21:22:50.677Z CNTRLR The controller is no longer jammed
2024-03-04 22:22:50.678 INFO Z-WAVE: Controller status: Controller is Ready
2024-03-04T21:22:51.278Z CNTRLR The controller is jammed
2024-03-04 22:22:51.279 INFO Z-WAVE: Controller status: Controller is unable to transmit
2024-03-04 22:22:51.970 INFO APP: GET /health/zwave 301 1.434 ms - 191
2024-03-04T21:22:52.300Z CNTRLR The controller is no longer jammed
2024-03-04 22:22:52.301 INFO Z-WAVE: Controller status: Controller is Ready
2024-03-04T21:22:52.303Z CNTRLR [Node 054] ping failed: Failed to send the command after 5 attempts (ZW0202)
2024-03-04T21:23:02.116Z CNTRLR » [Node 054] pinging the node...
2024-03-04T21:23:02.141Z CNTRLR The controller is jammed
2024-03-04 22:23:02.142 INFO Z-WAVE: Controller status: Controller is unable to transmit
2024-03-04T21:23:02.187Z DRIVER Dropping message with invalid payload
2024-03-04T21:23:02.232Z DRIVER Dropping message with invalid payload
2024-03-04T21:23:02.396Z DRIVER Dropping message with invalid payload
My solution; return to the gen5+ model of Aeotec.
I’m glad that the backup function is pretty oke from Aeotec (beside the fact that you need a Windows computer). Restored the old stick to the new one and everything is back online (90+ nodes).
