I installed a VZW31-SN as my first Inovelli product about 24 hours ago. It has been working fine up until I went to change the button delay parameter from 0ms to 300ms. As soon as I submitted that change, the lights controlled by the switch blinked 3 times and shut off. Since then, all configurations parameters have remained empty. Attempting to set any parameters results in a failure message in zwave-js-ui running on Home Assistant.
I have done about a dozen or so factory resets (paddle up + config until red) and have pulled the air gap for 20+ seconds several times. I have also restarted my Home Assistant VM and reinstalled zwave-js-ui to no avail. The configuration parameters remain empty, and the device is non-responsive to manual configurations at the switch like setting dimmer mode or single pole mode. Attempting to reinstall the latest production firmware to Target 0 gives me an error message that the target is invalid. I can still include and exclude the switch but cannot configure anything.
Any assistance would be greatly appreciated as I have an order of 10 more on the way!
stu1811
September 26, 2024, 4:53pm
2
How far is the switch from the controller? Is the controller plugged into USB2 or USB3? Are you using a 3ft or 1m USB extension cable?
Zooz 800 controller is in the next room about 15-18ft. away. It is plugged directly into USB3 on my Proxmox server without any extension cable.
There is no direct line of sight from the controller to the switch, but the doors to both rooms are open and more or less facing each other. At worst there would be 2 interior drywall walls between them. I have not noticed issues with connectivity or unreasonable delays when including/excluding or sending an on/off command remotely (which is about the only thing that works). Ping responses are near instantaneous.
As an example, here is the debug output when I go to set the config for Dimming Speed Up (Remote) from 0 to 500ms:
2024-09-26 12:30:16.463 INFO APP: GET /health/zwave 301 0.654 ms - 162
2024-09-26 12:30:45.769 INFO Z-WAVE: Calling api writeValue with args: [
{ nodeId: 14, commandClass: 112, endpoint: 0, property: 1 },
5,
null,
[length]: 3
]
2024-09-26 12:30:45.769 INFO Z-WAVE: Writing 5 to 14-112-0-1
2024-09-26 12:30:45.811 ERROR Z-WAVE: Unable to write 5 on 112-0-1: Fail
2024-09-26 12:30:45.811 INFO Z-WAVE: Success zwave api call writeValue { status: 2 }
2024-09-26 12:30:46.483 INFO APP: GET /health/zwave 301 0.284 ms - 162
2024-09-26 12:30:46.877 INFO Z-WAVE: [Node 014] Value updated: 112-0-1 0 => 0
PJF
September 27, 2024, 10:02pm
5
Do you see messages containing “Security2CCMessageEncapsulation” or “security class: S2_Authenticated” in the log when you try to set the value?
Here is the zwavejsui log for setting parameter 1 on a switch.
2024-09-27T21:56:17.721Z DRIVER » [Node 166] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 239
└─[Security2CCMessageEncapsulation]
│ sequence number: 176
│ security class: S2_Authenticated
└─[SupervisionCCGet]
│ session id: 34
│ request updates: true
└─[ConfigurationCCSet]
parameter #: 1
reset to default: false
value size: 1
value format: UnsignedInteger
value: 25
2024-09-27T21:56:17.729Z SERIAL « [ACK] (0x06)
2024-09-27T21:56:17.730Z SERIAL « 0x010401a90152 (6 bytes)
2024-09-27T21:56:17.730Z SERIAL » [ACK] (0x06)
2024-09-27T21:56:17.731Z DRIVER « [RES] [SendDataBridge]
was sent: true
2024-09-27T21:56:17.815Z SERIAL « 0x011d00a9ef00000803a7beb1b67f00000319a38d00030100007f7f7f7f7f87 (31 bytes)
2024-09-27T21:56:17.816Z SERIAL » [ACK] (0x06)
2024-09-27T21:56:17.817Z DRIVER « [REQ] [SendDataBridge]
callback id: 239
transmit status: OK, took 80 ms
repeater node IDs: 25, 163, 141
routing attempts: 1
protocol & route speed: Z-Wave, 100 kbit/s
routing scheme: LWR
ACK RSSI: -89 dBm
ACK RSSI on repeaters: -66 dBm, -79 dBm, -74 dBm
ACK channel no.: 0
TX channel no.: 0
2024-09-27T21:56:17.899Z SERIAL « 0x011a00a80001a6119f03fc00732ef257c6a2e3afa100dbab3800a705 (28 bytes)
2024-09-27T21:56:17.901Z SERIAL » [ACK] (0x06)
2024-09-27T21:56:17.901Z DRIVER « [Node 166] [REQ] [BridgeApplicationCommand]
│ RSSI: -89 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 252
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 34
more updates follow: false
status: Success
duration: 0s
2024-09-27T21:56:17.904Z DRIVER all queues idle
I have since re-included the switch without security to see if that would change anything. This was the log output without security:
2024-09-27T23:35:16.435Z DRIVER all queues idle
2024-09-27 18:35:26.671 DEBUG SOCKET: Event ZWAVE_API emitted to zNmk_h3uaooSjjqNAAAD
2024-09-27 18:35:26.672 INFO Z-WAVE: Calling api writeValue with args: [
{ nodeId: 14, commandClass: 112, endpoint: 0, property: 1 },
5,
null,
[length]: 3
]
2024-09-27 18:35:26.672 INFO Z-WAVE: Writing 5 to 14-112-0-1
2024-09-27T23:35:26.672Z CNTRLR [Node 014] [setValue] calling SET_VALUE API ConfigurationCCAPI:
property: 1
property key: undefined
optimistic: true
2024-09-27T23:35:26.673Z DRIVER all queues busy
2024-09-27T23:35:26.674Z SERIAL » 0x011700a90001000e096c019d057004010105250000000002e4 (25 bytes)
2024-09-27T23:35:26.674Z DRIVER » [Node 014] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 2
└─[SupervisionCCGet]
│ session id: 29
│ request updates: true
└─[ConfigurationCCSet]
parameter #: 1
reset to default: false
value size: 1
value format: UnsignedInteger
value: 5
2024-09-27T23:35:26.681Z SERIAL « [ACK] (0x06)
2024-09-27T23:35:26.683Z SERIAL « 0x010401a90152 (6 bytes)
2024-09-27T23:35:26.684Z SERIAL » [ACK] (0x06)
2024-09-27T23:35:26.684Z DRIVER « [RES] [SendDataBridge]
was sent: true
2024-09-27T23:35:26.701Z SERIAL « 0x011d00a90200000100a77f7f7f7f01010300000000020100007f7f7f7f7f90 (31 bytes)
2024-09-27T23:35:26.701Z SERIAL » [ACK] (0x06)
2024-09-27T23:35:26.701Z DRIVER « [REQ] [SendDataBridge]
callback id: 2
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
routing scheme: LWR
ACK RSSI: -89 dBm
ACK channel no.: 1
TX channel no.: 1
2024-09-27T23:35:26.707Z SERIAL « 0x011300a8000001000e056c021d020000a7007f7f98 (21 bytes)
2024-09-27T23:35:26.708Z SERIAL » [ACK] (0x06)
2024-09-27T23:35:26.708Z DRIVER « [Node 014] [REQ] [BridgeApplicationCommand]
│ RSSI: -89 dBm
└─[SupervisionCCReport]
session id: 29
more updates follow: false
status: Fail
duration: 0s
2024-09-27T23:35:26.709Z CNTRLR [Node 014] [setValue] result of SET_VALUE API call for ConfigurationCCAPI: (Su
pervisionResult)
status: Fail
2024-09-27T23:35:26.709Z CNTRLR [Node 014] [setValue] not updating value
2024-09-27 18:35:26.709 ERROR Z-WAVE: Unable to write 5 on 112-0-1: Fail
2024-09-27 18:35:26.710 INFO Z-WAVE: Success zwave api call writeValue { status: 2 }
2024-09-27T23:35:26.710Z DRIVER all queues idle
2024-09-27T23:35:27.711Z DRIVER all queues busy
2024-09-27T23:35:27.712Z SERIAL » 0x011100a90001000e0370050125000000000319 (19 bytes)
2024-09-27T23:35:27.712Z DRIVER » [Node 014] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 3
└─[ConfigurationCCGet]
parameter #: 1
2024-09-27T23:35:27.717Z SERIAL « [ACK] (0x06)
2024-09-27T23:35:27.720Z SERIAL « 0x010401a90152 (6 bytes)
2024-09-27T23:35:27.721Z SERIAL » [ACK] (0x06)
2024-09-27T23:35:27.721Z DRIVER « [RES] [SendDataBridge]
was sent: true
2024-09-27T23:35:27.737Z SERIAL « 0x011d00a90300000100a77f7f7f7f01010300000000020100007f7f7f7f7f91 (31 bytes)
2024-09-27T23:35:27.737Z SERIAL » [ACK] (0x06)
2024-09-27T23:35:27.737Z DRIVER « [REQ] [SendDataBridge]
callback id: 3
transmit status: OK, took 10 ms
routing attempts: 1
protocol & route speed: Z-Wave, 40 kbit/s
routing scheme: LWR
ACK RSSI: -89 dBm
ACK channel no.: 1
TX channel no.: 1
2024-09-27T23:35:27.744Z SERIAL « 0x011600a8000001000e08700601010000000000a7007f7f97 (24 bytes)
2024-09-27T23:35:27.745Z SERIAL » [ACK] (0x06)
2024-09-27T23:35:27.745Z CNTRLR [Node 014] [translateValueEvent: value updated]
commandClass: Configuration
endpoint: 0
property: 1
propertyKey: undefined
internal: false
secret: false
event source: undefined
2024-09-27T23:35:27.746Z CNTRLR [Node 014] [~] [Configuration] 1: 0 => 0 [Endpoint 0]
2024-09-27T23:35:27.746Z CNTRLR [Node 014] [translateValueEvent: value updated]
is root endpoint: true
is application CC: true
should hide root values: false
2024-09-27 18:35:27.746 INFO Z-WAVE: [Node 014] Value updated: 112-0-1 0 => 0
2024-09-27T23:35:27.747Z DRIVER « [Node 014] [REQ] [BridgeApplicationCommand]
│ RSSI: -89 dBm
└─[ConfigurationCCReport]
parameter #: 1
value size: 1
value: 0
2024-09-27T23:35:27.747Z DRIVER all queues idle
2024-09-27 18:35:42.553 INFO APP: GET /health/zwave 301 0.409 ms - 162
2024-09-27T23:35:46.427Z DRIVER all queues busy
2024-09-27T23:35:46.428Z SERIAL » 0x0103003bc7 (5 bytes)
2024-09-27T23:35:46.428Z DRIVER » [REQ] [GetBackgroundRSSI]
2024-09-27T23:35:46.431Z SERIAL « [ACK] (0x06)
2024-09-27T23:35:46.433Z SERIAL « 0x0107013ba2a1a1a9c9 (9 bytes)
2024-09-27T23:35:46.433Z SERIAL » [ACK] (0x06)
2024-09-27T23:35:46.435Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -94 dBm
channel 1: -95 dBm
channel 2: -95 dBm
channel 3: -87 dBm
2024-09-27T23:35:46.437Z DRIVER all queues idle
PJF
September 30, 2024, 12:03am
7
It appears you are communicating with the switch, it’s just not accepting the value. Maybe you just got unlucky and the switch went bad.
Yeah, the Z-Wave functionality appears to work just fine, and I suspect that maybe the firmware that came on the switch is just corrupted. It’s almost as if some of the parameters and other data are not stored in their expected memory locations.
I am communicating with @Lance_Inovelli by email and will continue that route once I am able to test with the new switches I have coming this week. Appreciate your input @PJF .
