Nice. I’ll have to try again. I was just surprised that I got what I got.
I was hoping someone might be able to prescribe the best way to completely nuke my z-wave network in order to start from scratch. This is the third z-wave implementation that I’m using with HA and I just haven’t had it in me to keep up with the details. I have no idea what happened today, but that’s how it has always been with z-wave going back to the Vera 3 where I got my start. For whatever reason today, after rebooting HA, the model and manufacturer all got reset to “unknown”, a ton of new non-sensical entities got created, some nodes are listed as dead. It’s a disaster.
This is certainly the last chance that this foul technology gets with me. I was always a big proponent of it, but after so many years it starts to feel like an abusive relationship.
2 Likes
Are you running zwavejs or zwavejs2mqtt? Sounds like you didn’t properly install zwavejs2mqtt and the system is trying to use just zwavejs.
I didn’t try zwavejs2mqtt. I’m still in the camp that swears by less moving parts. This is the thing that has always driven me crazy about Z-Wave though - no matter if it was Vera, Homeseer, or any of the three Z-Wave stacks I’ve used under HA. I think the protocol itself has some issues and it’s just trying to do too much. I’ve begun to migrate some things to Zigbee2mqtt and others I am hardwiring (interface via Konnected). It seems that less is more with Z-Wave; too many nodes on a single network just leads to problems.
So I ended up going scorched earth. After copying my network key, I uninstalled the integration followed by the addon. Then reinstalled and configured both again. The saving grace here is that all of my line powered nodes and close to half of the battery powered nodes came back as fresh new entities. I’ve been going through the legwork of renaming, etc. but my workload for rebuilding has been considerably less than I anticipated.
New to the forum but have used Home Assistant for a while now.
Does anyone know if there will be a non-add-on “official” installation method for people who don’t have the access to add-ons?
I run Home Assistant in a non-supervised Docker container and I’m currently testing out zwavejs2mqtt. I want to keep running my zwavejs server in Docker but I also want to make sure that my z-wave system is future proofed and I’m not sure that using an “unofficial” method is best for that.
How likely is it that using the zwavejs2mqtt container will continue to be compatible with the zwavejs integration in the future?
1 Like
They use the same API. So the only way it wouldn’t work is if zwavejs2MQTT closes off the api access to node-zwave-js.
1 Like
I decided to install the beta of home assistant to try out the new feature allowing to configure a device.
I assume it’s not normal that I can’t enter any values for the parameters? More concretely I can pick an option from a list or click a switch, but where I need to enter a value that is not possible:
OK, so I guess the answer is likely no.
Or at least it doesn’t matter since the zwavejs2mqtt container should keep working.
And I just stumbled on this in the docs so it looks like the zwavejs2mqtt container is “officially” supported for now.
Thanks for the reply.
I have a WAPIRZ-1 Motion Sensor that no longer detects motion after I upgraded to Z-Wave JS 0.1.15. The temperature and battery sensors are still working but no motion detection. 0.1.16 does the same thing. I can go back to 0.1.14 and it works. Any ideas?
this has got to be one of the biggest steps/leaps in the current beta, Zwave device settings.
we need to applaud the dev’s for this. Was it @emontnemery? What a clean and complete interface this is becoming, and , nothing against the z2m interface, but what a relieve to the eye this is.
thanks for all the work!
(am confident the setting of parameters will follow soon)
So here is my entire logs file. I’m hoping somebody can help me here as I am pretty stumped. After a certain amount of time that appears to be anywhere from 4 hours to 5 days the whole network stops responding and I don’t see any glaring errors in the log.
# docker logs 5e8401e3ba4f
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] config.sh: executing...
[cont-init.d] config.sh: exited 0.
[cont-init.d] structure.sh: executing...
[cont-init.d] structure.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:40:45] INFO: Successfully send discovery information to Home Assistant.
2021-03-31T14:40:52.904Z DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
2021-03-31T14:40:52.931Z DRIVER version 7.0.1
2021-03-31T14:40:52.934Z DRIVER
2021-03-31T14:40:53.220Z DRIVER Dropping message because the driver is not ready to handle it yet.
2021-03-31T14:41:22.751Z DRIVER Dropping message because the driver is not ready to handle it yet.
2021-03-31T14:41:41.823Z CNTRLR beginning interview...
2021-03-31T14:41:41.829Z CNTRLR querying version info...
2021-03-31T14:41:43.118Z CNTRLR received version info:
controller type: Static Controller
library version: Z-Wave 4.54
2021-03-31T14:41:43.121Z CNTRLR querying controller IDs...
2021-03-31T14:41:43.206Z CNTRLR received controller IDs:
home ID: 0xee45c526
own node ID: 1
2021-03-31T14:41:43.208Z CNTRLR querying controller capabilities...
2021-03-31T14:41:43.287Z CNTRLR received controller capabilities:
controller role: primary
is in other network: false
is SIS present: false
was real primary: true
is a SUC: false
2021-03-31T14:41:43.289Z CNTRLR querying API capabilities...
2021-03-31T14:41:43.387Z CNTRLR received API capabilities:
serial API version: 1.1
manufacturer ID: 0x86
product type: 0x0101
product ID: 0x5a
supported functions:
· GetSerialApiInitData (0x02)
· FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION (0x03)
· ApplicationCommand (0x04)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· FUNC_ID_SERIAL_API_SOFT_RESET (0x08)
· UNKNOWN_FUNC_UNKNOWN_0x09 (0x09)
· UNKNOWN_FUNC_RF_RECEIVE_MODE (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)
· UNKNOWN_FUNC_SEND_DATA_META (0x18)
· 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)
· UNKNOWN_FUNC_FlashAutoProgSet (0x27)
· UNKNOWN_FUNC_NVMGetId (0x29)
· UNKNOWN_FUNC_NVMExtReadLongBuffer (0x2a)
· UNKNOWN_FUNC_NVMExtWriteLongBuffer (0x2b)
· UNKNOWN_FUNC_NVMExtReadLongByte (0x2c)
· UNKNOWN_FUNC_NVMExtWriteLongByte (0x2d)
· 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)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· FUNC_ID_ZW_ASSIGN_SUC_RETURN_ROUTE (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· FUNC_ID_ZW_SET_SUC_NODE_ID (0x54)
· FUNC_ID_ZW_DELETE_SUC_RETURN_ROUTE (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
· UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· UNKNOWN_FUNC_GET_PRIORITY_ROUTE (0x92)
· UNKNOWN_FUNC_SET_PRIORITY_ROUTE (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· 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)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xee)
· UNKNOWN_FUNC_UNKNOWN_0xEF (0xef)
2021-03-31T14:41:43.391Z CNTRLR finding SUC...
2021-03-31T14:41:43.473Z CNTRLR no SUC present
2021-03-31T14:41:44.053Z CNTRLR querying node information...
2021-03-31T14:41:44.258Z CNTRLR received node information:
controller role: primary
controller is a SUC: false
controller is a slave: false
controller supports timers: false
nodes in the network: 1, 3, 4, 5, 6, 7, 8, 11
2021-03-31T14:41:44.457Z CNTRLR [Node 001] trying to load device config
2021-03-31T14:41:44.627Z CNTRLR [Node 001] device config loaded
2021-03-31T14:41:44.635Z CNTRLR [Node 003] trying to load device config
2021-03-31T14:41:44.661Z CNTRLR [Node 003] device config loaded
2021-03-31T14:41:44.667Z CNTRLR [Node 004] trying to load device config
2021-03-31T14:41:44.708Z CNTRLR [Node 004] device config loaded
2021-03-31T14:41:44.715Z CNTRLR [Node 005] trying to load device config
2021-03-31T14:41:44.740Z CNTRLR [Node 005] device config loaded
2021-03-31T14:41:44.746Z CNTRLR [Node 006] trying to load device config
2021-03-31T14:41:44.764Z CNTRLR [Node 006] device config loaded
2021-03-31T14:41:44.771Z CNTRLR [Node 007] trying to load device config
2021-03-31T14:41:44.807Z CNTRLR [Node 007] device config loaded
2021-03-31T14:41:44.813Z CNTRLR [Node 008] trying to load device config
2021-03-31T14:41:44.849Z CNTRLR [Node 008] device config loaded
2021-03-31T14:41:44.857Z CNTRLR [Node 011] trying to load device config
2021-03-31T14:41:44.889Z CNTRLR [Node 011] device config loaded
2021-03-31T14:41:44.918Z CNTRLR setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2021-03-31T14:41:45.012Z CNTRLR serial API timeouts overwritten. The old values were: ack = 1000 ms, byte = 15
0 ms
2021-03-31T14:41:45.016Z CNTRLR Interview completed
Starting server on port 3000
2021-03-31T14:41:45.087Z CNTRLR [Node 001] The node is alive.
2021-03-31T14:41:45.091Z CNTRLR [Node 001] The node is ready to be used
2021-03-31T14:41:45.096Z CNTRLR » [Node 003] pinging the node...
2021-03-31T14:41:45.458Z CNTRLR » [Node 004] pinging the node...
2021-03-31T14:41:45.470Z CNTRLR » [Node 005] pinging the node...
2021-03-31T14:41:45.485Z CNTRLR » [Node 006] pinging the node...
2021-03-31T14:41:45.498Z CNTRLR » [Node 007] pinging the node...
2021-03-31T14:41:45.511Z CNTRLR » [Node 008] pinging the node...
2021-03-31T14:41:45.523Z CNTRLR » [Node 011] pinging the node...
ZwaveJS server listening on port 3000
Server listening on port 3000
2021-03-31T14:41:45.644Z CNTRLR [Node 003] The node is alive.
2021-03-31T14:41:45.648Z CNTRLR [Node 003] The node is ready to be used
2021-03-31T14:41:45.651Z CNTRLR « [Node 003] ping successful
2021-03-31T14:41:45.719Z CNTRLR [Node 004] The node is alive.
2021-03-31T14:41:45.722Z CNTRLR [Node 004] The node is ready to be used
2021-03-31T14:41:45.724Z CNTRLR « [Node 004] ping successful
2021-03-31T14:41:45.819Z CNTRLR [Node 005] The node is alive.
2021-03-31T14:41:45.822Z CNTRLR [Node 005] The node is ready to be used
2021-03-31T14:41:45.824Z CNTRLR « [Node 005] ping successful
2021-03-31T14:41:45.927Z CNTRLR [Node 006] The node is alive.
2021-03-31T14:41:45.932Z CNTRLR [Node 006] The node is ready to be used
2021-03-31T14:41:45.935Z CNTRLR « [Node 006] ping successful
2021-03-31T14:41:47.264Z CNTRLR [Node 007] The node is alive.
2021-03-31T14:41:47.267Z CNTRLR [Node 007] The node is ready to be used
2021-03-31T14:41:47.270Z CNTRLR « [Node 007] ping successful
2021-03-31T14:41:48.608Z CNTRLR [Node 008] The node is alive.
2021-03-31T14:41:48.612Z CNTRLR [Node 008] The node is ready to be used
2021-03-31T14:41:48.614Z CNTRLR « [Node 008] ping successful
2021-03-31T14:41:48.718Z CNTRLR [Node 011] The node is alive.
2021-03-31T14:41:48.721Z CNTRLR [Node 011] The node is ready to be used
2021-03-31T14:41:48.722Z CNTRLR All nodes are ready to be used
2021-03-31T14:41:48.724Z CNTRLR « [Node 011] ping successful
New client
2021-03-31T14:48:47.729Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-03-31T14:53:12.208Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-03-31T17:58:34.163Z CNTRLR « [Node 007] TODO: no handler for application command
2021-03-31T18:24:37.685Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-03-31T20:08:03.618Z CNTRLR « [Node 005] Received updated node info
2021-03-31T20:12:38.864Z CNTRLR « [Node 005] Received updated node info
2021-03-31T20:53:44.818Z CNTRLR « [Node 005] Received updated node info
2021-03-31T21:39:38.471Z CNTRLR « [Node 005] Received updated node info
2021-03-31T21:45:44.281Z CNTRLR « [Node 005] Received updated node info
2021-03-31T21:45:53.882Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-03-31T22:36:09.660Z CNTRLR « [Node 005] Received updated node info
2021-03-31T22:42:44.244Z CNTRLR « [Node 005] Received updated node info
2021-04-01T00:47:25.514Z CNTRLR « [Node 005] Received updated node info
2021-04-01T03:17:33.370Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-01T12:09:04.400Z CNTRLR « [Node 004] Received updated node info
2021-04-01T12:56:23.648Z CNTRLR « [Node 005] Received updated node info
2021-04-01T13:34:10.920Z CNTRLR « [Node 005] Received updated node info
2021-04-01T13:42:52.503Z CNTRLR « [Node 005] Received updated node info
2021-04-01T17:58:27.356Z CNTRLR « [Node 007] TODO: no handler for application command
2021-04-01T18:51:08.240Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-01T22:52:55.354Z CNTRLR « [Node 004] Received updated node info
2021-04-02T04:14:28.603Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T04:14:28.921Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:10.834Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:10.942Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-04-02T13:42:12.071Z CNTRLR [Node 008] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-04-02T13:42:12.601Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:12.708Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-04-02T13:42:13.820Z CNTRLR [Node 008] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-04-02T13:42:14.351Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:14.459Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-04-02T13:42:15.594Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
Unexpected error ZWaveError: Failed to send the message after 3 attempts
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2217:23)
at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2322:28)
at DoorLockCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:292:21)
at Proxy.DoorLockCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:140:15)
at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:699:14)
at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:16:44)
at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:33:91)
at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:92:99)
at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:45)
at WebSocket.emit (events.js:315:20) {
code: 18,
context: undefined,
transactionSource: ' at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2217:23)\n' +
' at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2322:28)\n' +
' at DoorLockCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:292:21)\n' +
' at Proxy.DoorLockCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:140:15)\n' +
' at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:699:14)\n' +
' at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:16:44)\n' +
' at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:33:91)\n' +
' at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:92:99)\n' +
' at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:45)\n' +
' at WebSocket.emit (events.js:315:20)'
}
2021-04-02T13:42:15.743Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-04-02T13:42:16.854Z CNTRLR [Node 007] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-04-02T13:42:17.377Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:17.495Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-04-02T13:42:18.607Z CNTRLR [Node 007] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-04-02T13:42:19.132Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:19.246Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
Unexpected error ZWaveError: Failed to send the message after 3 attempts
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2217:23)
at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2322:28)
at DoorLockCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:292:21)
at Proxy.DoorLockCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:140:15)
at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:699:14)
at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:16:44)
at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:33:91)
at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:92:99)
at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:45)
at WebSocket.emit (events.js:315:20) {
code: 18,
context: undefined,
transactionSource: ' at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2217:23)\n' +
' at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2322:28)\n' +
' at DoorLockCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:292:21)\n' +
' at Proxy.DoorLockCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/DoorLockCC.ts:140:15)\n' +
' at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:699:14)\n' +
' at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:16:44)\n' +
' at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:33:91)\n' +
' at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:92:99)\n' +
' at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:45)\n' +
' at WebSocket.emit (events.js:315:20)'
}
2021-04-02T13:42:22.617Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:22.732Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-04-02T13:42:23.845Z CNTRLR [Node 003] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2021-04-02T13:42:24.361Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:24.469Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2021-04-02T13:42:25.588Z CNTRLR [Node 003] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2021-04-02T13:42:26.104Z CNTRLR Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2021-04-02T13:42:26.211Z CNTRLR Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
Unexpected error ZWaveError: Failed to send the message after 3 attempts
at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2217:23)
at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2322:28)
at BinarySwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:111:21)
at Proxy.BinarySwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:124:14)
at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:699:14)
at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:16:44)
at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:33:91)
at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:92:99)
at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:45)
at WebSocket.emit (events.js:315:20) {
code: 18,
context: undefined,
transactionSource: ' at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2217:23)\n' +
' at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:2322:28)\n' +
' at BinarySwitchCCAPI.set (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:111:21)\n' +
' at Proxy.BinarySwitchCCAPI.<computed> (/usr/src/node_modules/zwave-js/src/lib/commandclass/BinarySwitchCC.ts:124:14)\n' +
' at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:699:14)\n' +
' at Function.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:16:44)\n' +
' at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:33:91)\n' +
' at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:92:99)\n' +
' at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:38:45)\n' +
' at WebSocket.emit (events.js:315:20)'
}
yes I agree this looks very nice (which is why I installed the beta 
)
Hope they can get it working so that you can actually use it to change all parameters.
For now the two workarounds I found are:
- use the service call “Z-Wave JS: Set a Z-Wave device configuration parameter” in developer tools instead
- shutdown Z-wave add-on in the supervisor and startup zwavejsmqtt. This option is not recommended because the zwavejs addon doesn’t know that I have changed a parameter on the device. Meaning that the device will behave how I have configured it but the displayed configuration in ZwaveJS is wrong. Perhaps this will autocorrect after some time.
Has anyone been able to successfully use the bulk set partial config parameters in the new RC version of 2021.04? I’ve tried it a million different ways with my Inovelli Red Dimmer switches (LZW31-SN), and it does nothing. The regular set parameter service call still works, but only for one parameter at a time.
Basing everything on this device, parameter 16:
https://devices.zwave-js.io/?jumpTo=0x031e:0x0001:0x0001:0.0
Here is an example service call below. Note that Home Assistant automatically (via dev tools) translated the hex values (i.e 0xff) to an integer. These do match up with the device in the ZWaveJS2MQTT control panel.
I have tried using single quotes, double quotes, no quotes, hex values, integers, device names instead of entity_id, etc. and the switch does nothing. I’ve also tried with just 1 or 2 parameters and same result with the bulk service call.
Any ideas?
service: zwave_js.bulk_set_partial_config_parameters
target:
entity_id: light.downstairs_lights
data:
parameter: '16'
value:
'255': '21'
'65280': '3'
'16711680': '10'
'2130706432': '3'
I had a nice surprise today. I was working on my daughter’s system and had a zwave switch that wouldn’t pair up. I remembered that the last time it was used the switch was on an iris system. I thought I would have to take it home to mess with it, but tried to exclude it and it worked. After that it easily paired up.
Send the full value as an integer ie:
service: zwave_js.bulk_set_partial_config_parameters
target:
entity_id: light.downstairs_lights
data:
parameter: 16
value: 52300392
1 Like
I tried that on 2021.4.0b0 and it didnt work. Just upgraded to b2 and just tried again…still no luck. I pulled a few values from the toolbox (link)
Works fine here, make sure you’re using the latest zwavejs2mqtt v3.0.x+
You can set parameters via the control panel as is 
Confirmed I’m on the right versions. Restarted everything just in case and still no luck. Setting a single parameter does still work, just not the bulk service. Guess Ill wait and see if others have luck or not.