The add-on was updated, but the add-on repository still needs to be updated for HA to know about it. (which hasn’t happened yet).
2 Likes
My zwave suddenly isn’t working and I’ve got the following error in my logs:
Failed to set the Z-Wave JS add-on options: not a valid value for dictionary value @ data['options']. Got {'device': '/dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller
Is this related?
edit: I was able to resolve this. Somehow the zwave addon got set to not start at boot. I did not change this, but once I started the addon and re-set the option to start at boot - everything seems fine.
1 Like
Lets hope it happens before supervisor 2023.10.1 thats now showing available automatically updates.
There’s no relationship with Supervisor, unless that is requiring a minimum HA version.
Yup, just updated Supervisor and old Zwave JS UI still works fine…
JS ui 2.0.2 is now showing available.
Once installed along with
supervisor 2023.10
and soft reset disabled
and controller unplugged and replugged
and host rebooted (raspberry pi and no VM involved)
Issue is the same, constant driver restarts and loss of zwave while everything is rescanned.
I do have logs, from before i disabled soft reset, after i disabled it and replugged the (aeotec gen5+) controller, and also after the JS UI 2.0.2 update… but watching the live logs, everything looks exactly the same.
Update, logs below.
I am aware I have one dead node on the network (node 112). After trying everything else, I can only assume that’s causing this catastrophic failure.
After restore, everything working perfectly again, with known dead node causing no issues
2023-10-04T19:10:46.144Z CNTRLR « [Node 004] ping successful
2023-10-04T19:10:48.106Z CNTRLR [Node 036] The node is alive.
2023-10-04T19:10:48.154Z CNTRLR Retrieving priority route to node 36...
2023-10-04T19:10:48.156Z CNTRLR [Node 036] The node is ready to be used
2023-10-04T19:10:48.171Z CNTRLR « [Node 036] ping successful
2023-10-04T19:10:51.193Z CNTRLR [Node 073] The node is alive.
2023-10-04T19:10:51.290Z CNTRLR Retrieving priority route to node 73...
2023-10-04T19:10:51.295Z CNTRLR [Node 073] The node is ready to be used
2023-10-04T19:10:51.327Z CNTRLR « [Node 073] ping successful
2023-10-04T19:10:54.918Z CNTRLR [Node 112] The node did not respond after 1 attempts, it is presumed dead
2023-10-04T19:10:54.921Z CNTRLR [Node 112] The node is dead.
2023-10-04T19:10:54.922Z CNTRLR All nodes are ready to be used
2023-10-04T19:10:54.927Z CNTRLR [Node 112] ping failed: The node did not acknowledge the command (ZW0204)
2023-10-04T19:10:54.944Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-10-04T19:10:55.148Z DRIVER no handlers registered!
2023-10-04T19:11:42.208Z CNTRLR » [Node 112] pinging the node...
2023-10-04T19:12:00.154Z CNTRLR The controller is unresponsive
2023-10-04T19:12:00.163Z DRIVER Attempting to recover unresponsive controller...
2023-10-04T19:12:00.170Z CNTRLR The controller does not support soft reset or the soft reset feature has been
disabled with a config option or the ZWAVEJS_DISABLE_SOFT_RESET environment va
riable.
2023-10-04T19:12:00.175Z DRIVER Recovering unresponsive controller failed. Restarting the driver...
2023-10-04T19:12:00.185Z CNTRLR [Node 014] Deleting SUC return route failed: Timeout while waiting for a callb
ack from the controller (ZW0200)
2023-10-04T19:12:00.188Z CNTRLR [Node 014] Assigning SUC return route failed: The driver is not ready or has b
een destroyed (ZW0103)
2023-10-04T19:12:01.249Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2023-10-04T19:12:01.250Z DRIVER version 12.0.2
2023-10-04T19:12:01.251Z DRIVER
2023-10-04T19:12:02.281Z CONFIG version 12.0.2
2023-10-04T19:12:03.767Z CNTRLR querying Serial API capabilities...
2023-10-04T19:12:03.783Z CNTRLR received API capabilities:
firmware version: 1.2
manufacturer ID: 0x86
product type: 0x01
product ID: 0x5a
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· ApplicationCommand (0x04)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SerialAPISetup (0x0b)
· SetRFReceiveMode (0x10)
· UNKNOWN_FUNC_SET_SLEEP_MODE (0x11)
· FUNC_ID_ZW_SEND_NODE_INFORMATION (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_R_F_POWER_LEVEL_SET (0x17)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· EnterBootloader (0x27)
· UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMWriteLongBuffer (0x2b)
· ExtNVMReadLongByte (0x2c)
· ExtExtWriteLongByte (0x2d)
· NVMOperations (0x2e)
· undefined (0x2f)
· undefined (0x37)
· undefined (0x38)
· UNKNOWN_FUNC_ClearNetworkStats (0x39)
· UNKNOWN_FUNC_GetNetworkStats (0x3a)
· GetBackgroundRSSI (0x3b)
· undefined (0x3c)
· UNKNOWN_FUNC_RemoveNodeIdFromNetwork (0x3f)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· FUNC_ID_ZW_CREATE_NEW_PRIMARY (0x4c)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· AssignPriorityReturnRoute (0x4f)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· AssignSUCReturnRoute (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· AssignPrioritySUCReturnRoute (0x58)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· undefined (0x5f)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· FirmwareUpdateNVM (0x78)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· FUNC_ID_APPLICATION_SLAVE_COMMAND_HANDLER (0xa1)
· UNKNOWN_FUNC_UNKNOWN_0xB4 (0xb4)
· UNKNOWN_FUNC_WATCH_DOG_ENABLE (0xb6)
· UNKNOWN_FUNC_WATCH_DOG_DISABLE (0xb7)
· UNKNOWN_FUNC_WATCH_DOG_KICK (0xb8)
· UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
· UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· FUNC_ID_ZW_SET_PROMISCUOUS_MODE (0xd0)
· FUNC_ID_PROMISCUOUS_APPLICATION_COMMAND_HANDLER (0xd1)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xee)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
2023-10-04T19:12:03.784Z CNTRLR querying version info...
2023-10-04T19:12:03.795Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 6.07
2023-10-04T19:12:03.796Z CNTRLR querying protocol version info...
2023-10-04T19:12:03.806Z CNTRLR received protocol version info:
protocol type: Z-Wave
protocol version: 6.7.0
appl. framework build no.: 97
2023-10-04T19:12:03.807Z CNTRLR querying serial API setup capabilities...
2023-10-04T19:12:03.821Z CNTRLR supported serial API setup commands:
· GetSupportedCommands
· SetTxStatusReport
· SetPowerlevel
· GetPowerlevel
· GetMaximumPayloadSize
2023-10-04T19:12:03.822Z CNTRLR querying controller IDs...
2023-10-04T19:12:03.832Z CNTRLR received controller IDs:
home ID: 0xfb046add
own node ID: 1
2023-10-04T19:12:04.087Z CNTRLR supported Z-Wave features:
· SmartStart
2023-10-04T19:12:04.088Z CNTRLR querying controller capabilities...
2023-10-04T19:12:04.118Z CNTRLR received controller capabilities:
controller role: primary
is the SUC: true
started this network: true
SIS is present: true
was real primary: true
2023-10-04T19:12:04.119Z CNTRLR Enabling TX status report...
2023-10-04T19:12:04.168Z CNTRLR Enabling TX status report successful...
2023-10-04T19:12:04.190Z CNTRLR finding SUC...
2023-10-04T19:12:04.234Z CNTRLR This is the SUC
2023-10-04T19:12:04.235Z CNTRLR querying additional controller information...
2023-10-04T19:12:04.375Z CNTRLR received additional controller information:
Z-Wave API version: 8 (legacy)
Z-Wave chip type: ZW050x
node type Controller
controller role: primary
controller is the SIS: true
controller supports timers: false
nodes in the network: 1, 4, 8, 9, 11, 12, 14, 15, 17, 18, 19, 20, 21,
22, 23, 24, 34, 36, 38, 39, 41, 42, 43, 44, 47, 48, 49, 51, 53, 55, 56, 60, 62
, 64, 65, 66, 67, 68, 69, 70, 71, 73, 78, 79, 80, 81, 82, 94, 99, 110, 111, 11
2, 113, 114, 117, 118, 125
2023-10-04T19:12:04.792Z CNTRLR [Node 001] Embedded device config loaded
2023-10-04T19:12:04.799Z CNTRLR [Node 004] Embedded device config loaded
2023-10-04T19:12:04.810Z CNTRLR [Node 008] Embedded device config loaded
2023-10-04T19:12:04.819Z CNTRLR [Node 009] Embedded device config loaded
2023-10-04T19:12:04.844Z CNTRLR [Node 011] Embedded device config loaded
2023-10-04T19:12:04.884Z CNTRLR [Node 012] Embedded device config loaded
3 Likes
Hm… this is strange… I have no dead nodes and the same problem.
Anyhow, thanks for confirmation that 2.0.2 does not solve the problem, this saved quite some time to retry…
Shame it is not fixed, as this is effectively prohibiting us from updating HA to 2023.10, as version 2.0+ of Zwave JS UI is required for zwave network 
Fix might be coming, stay updated here too: Z-Wave JS failure · Issue #3234 · home-assistant/addons · GitHub
(Looks like there is some issue with Aeotec Gen5 sticks firmware triggering new features in zwave js, maybe the dead node some people have mentioned is just co-incidence)
This sounds good.
All 3 points match:
-having the z-wave issue
-having the Aeotec Gen5 stick
-having failed nodes that cannot be removed
Hopefully the fix is there soon.
1 Like
Your theory holds.
I do NOT have dead nodes, have an Aeotec 5+ on latest firmware so supports smartstart, on a Pi4, have upgraded to JsUI 2.02 and 2023.10, soft reset is Off
and Do not have the issue.
My difference is I do not have any weird dead nodes I cannot remove - I only have the standard once in a while drop off and back with a ping dead nodes 
That said it’s (the JsUI console) actually notably more responsive… So I’ll give them that.
1 Like
Also not having fdead nodes and seeng some successes I also made another retry to update and it went smooth this time. No issues whatsoever!
I did run into problems with this Zwave bug also, needed 4 days to fix it. As I had to restore a 9 GB backup multiple time’s, which takes hours.
Well, I used this situation also simultaneously to make the switch from HA Supervised to HAOS, because the devs completely destroyed everything, that has made Supervised the best version, we had.
I’m running Zwave with the Zwave.me 500gen stick. ZwaveJS addon and ZwaveJS integration.
After trying out all the possible combi’s of updates of HA Core, Zwave JS and all kinds of resets (HA restart, system restart, unplugging the USB stick and so on, after days of swetting here in the midnight hours and shortage on sleep, it looks, I have it back to stable.
Things, I did found out here on the forums and by trial and error finally got me there, I hope. It runs now for 2 days fine.
I never had issues with dead nodes, never ever. That may be the Zwave.me stick, I never heard of people with this stick having dead nodes. Allmost all this issues affect people with Aeotec sticks. So, even without dead nodes Zwave did fall down here.
Now stable with:
- HAOS 10.5
- HA core version 2023.10.0
- HA Supervisor version 23.10.0
- Zwave JS addon 0.1.94
- Zwave JS integration, driver 12.0.2, software 1.32.1
- Zwave JS addon configured with USB stick device as /dev/serial/by-id
- Zwave JS addon configured with 500 series controller soft-reset disabled
I hope, this sum-up helps someone… 
1 Like
If you have a 9GB backup, that could be the recorder data. I skipped the mariaDB plugin when doing restores and selected everything else (individual zwave plugin restores didnt fix the issues, and caused more).
Skipping that large database (but only 1.3GB in my case) made the restore much quicker.
@raman325 it looks like node jwave js on GitHub is now merged to Release v12.0.3 with the fixes
Is this something you can pull into a ZUI release?
I don’t have the ability to release ZUI itself, just the addon. I did submit a PR to bump the version in the official addon as well as in the ZUI repo - that will need to get merged, then released, then we can update the addon
1 Like
Somehow the zwave addon got set to not start at boot. I did not change this, but once I started the addon and re-set the option to start at boot - everything seems fine.
The exact same thing happened to me.
I really wish the addons and integrations pages were one tap away from each other, like tabs on a page or something.
Looks like the GitHub repo ZUI is now bumped and includes the new version of node zwave js.
Looking at what’s been done, I’m 99% sure this will fix the driver restarts issue for most people 
- with aetotec gen5 controllers and also at least one of the others too
Exact same here.
It took me a while to recognize that the zwave JS was disabled (and still is on boot - never changed that).
So no backup restore was needed in my case (fortunately).
I am on:
HAOS
Home Assistant 2023.10.0
Supervisor 2023.10.0
Operating System 10.5
Frontend 20231002.0 - latest
Z-Wave JS Current version: 0.1.94
“driverVersion”: “12.0.2”,
“serverVersion”: “1.32.1”,
Aeotec Z-Stick Gen5
I am still unclear about how to set the soft-reset option.
Any suggestion? What is it good for vs. Ping?
zwave-js-ui: 9.1.0
zwave-js: 12.0.3
The above seems to have resolved the issue I initially reported for this post (specifically fixes in zwave-js 12.0.3)
1 Like
As it’s not hyper-urgent in my case, will there be a fix that will be part of a regular update so I can wait and relax?