I’m up to 15 days now with firmware 2.0.0 and no switches have gone dead. Seems to have for sure fixed the issue for me.
1 Like
@Bry, good thought, but I think that only affects 2x, 3x and 4x presses. I had it on 300mS, but I just tried it with no delay and it still outputs the paddle presses (and is more responsive so I think I’ll keep it that way except on the dimmers where I want to recognize multiple presses).
On the ones you are having difficulty on can you do this?
- reboot the switch by pulling the air gap out for a couple of seconds
- In zwave js do an interview for that device
- Check in “groups” to make sure that you have an association setup for group 1 (lifeline) back to your controller (usually node 1).
Did that. I do have that association.
Will let you know if I see the problem again and whether those steps restore it.
1 Like
The new firmware seems to have solved the disconnect problems for me. I haven’t had any issues since the initial hiccup after installing the firmware.
I still find that zwave isn’t 100% reliable with Home Assistant scenes. Would love to get that sorted, but at least I don’t have to worry about the switches getting stuck anymore. Much better! Thanks!
The disconnects seem to be solved with the firmware, HOWEVER there is an annoying bug where the transition durations are being modded with 25, so any transition duration larger than 24 seconds ends up being less than 25 seconds. I don’t know if this bug is new in this firmware, but the problem doesn’t reproduce with my Leviton dimmer so it’s not Home Assistant or ZWave-JS that is doing it.
@EricM_Inovelli where would you like to track this? Also if you can tell me how to safely downgrade I can test whether the new firmware introduced the bug.
I’ll look into it. Can you give me some examples of how you are doing it? If you go into the zwave js gui and use switch multi level set with a duration it happens there?
Sure, here are a few examples done from Z-Wave JS UI:
- A 25 second transition. It takes 26 seconds.
- A 26 second transition. It takes 0.5 seconds.
- A 45 second transition. It takes 20 seconds.
- A Leviton dimmer with a 45 second transition. It takes 45 seconds.
25 second transition …
2026-04-07 19:13:55.676 INFO Z-WAVE: Calling api writeValue with args: [
{
nodeId: 279,
commandClass: 38,
endpoint: 0,
property: 'targetValue'
},
0,
null,
[length]: 3
]
2026-04-07 19:13:55.676 INFO Z-WAVE: Writing 0 to 279-38-0-targetValue
2026-04-07 19:13:55.680 DRIVER » [Node 279] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 6
└─[Security2CCMessageEncapsulation]
│ sequence number: 13
└─[SupervisionCCGet]
│ session id: 45
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 0
duration: 25s
2026-04-07 19:13:55.717 DRIVER « [Node 279] [REQ] [BridgeApplicationCommand]
│ RSSI: -65 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 74
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 45
more updates follow: true
status: Working
duration: 26s
2026-04-07 19:13:55.719 INFO Z-WAVE: [Node 279] Value updated: 38-0-targetValue 25 => 0
2026-04-07 19:14:21.777 DRIVER « [Node 279] [REQ] [BridgeApplicationCommand]
│ RSSI: -67 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 75
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 45
more updates follow: false
status: Success
duration: 0s
2026-04-07 19:14:21.777 CNTRLR « [Node 279] Received update for a Supervision session
2026-04-07 19:14:21.778 INFO Z-WAVE: [Node 279] Value updated: 38-0-currentValue 25 => 0
26 second transition …
2026-04-07 19:18:19.972 INFO Z-WAVE: Calling api writeValue with args: [
{
nodeId: 279,
commandClass: 38,
endpoint: 0,
property: 'targetValue'
},
0,
null,
[length]: 3
]
2026-04-07 19:18:19.973 INFO Z-WAVE: Writing 0 to 279-38-0-targetValue
2026-04-07 19:18:19.976 DRIVER » [Node 279] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 20
└─[Security2CCMessageEncapsulation]
│ sequence number: 15
└─[SupervisionCCGet]
│ session id: 47
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 0
duration: 26s
2026-04-07 19:18:20.010 DRIVER « [Node 279] [REQ] [BridgeApplicationCommand]
│ RSSI: -67 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 78
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 47
more updates follow: true
status: Working
duration: 1s
2026-04-07 19:18:20.011 INFO Z-WAVE: [Node 279] Value updated: 38-0-targetValue 25 => 0
2026-04-07 19:18:20.534 DRIVER « [Node 279] [REQ] [BridgeApplicationCommand]
│ RSSI: -65 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 79
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 47
more updates follow: false
status: Success
duration: 0s
2026-04-07 19:18:20.535 CNTRLR « [Node 279] Received update for a Supervision session
2026-04-07 19:18:20.536 INFO Z-WAVE: [Node 279] Value updated: 38-0-currentValue 25 => 0
45 second transition …
2026-04-07 19:29:25.188 INFO Z-WAVE: Calling api writeValue with args: [
{
nodeId: 279,
commandClass: 38,
endpoint: 0,
property: 'targetValue'
},
0,
null,
[length]: 3
]
2026-04-07 19:29:25.189 INFO Z-WAVE: Writing 0 to 279-38-0-targetValue
2026-04-07 19:29:25.192 DRIVER » [Node 279] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 87
└─[Security2CCMessageEncapsulation]
│ sequence number: 28
└─[SupervisionCCGet]
│ session id: 59
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 0
duration: 45s
2026-04-07 19:29:25.225 DRIVER « [Node 279] [REQ] [BridgeApplicationCommand]
│ RSSI: -67 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 98
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 59
more updates follow: true
status: Working
duration: 20s
2026-04-07 19:29:25.226 INFO Z-WAVE: [Node 279] Value updated: 38-0-targetValue 25 => 0
2026-04-07 19:29:45.448 DRIVER « [Node 279] [REQ] [BridgeApplicationCommand]
│ RSSI: -65 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 99
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 59
more updates follow: false
status: Success
duration: 0s
2026-04-07 19:29:45.449 CNTRLR « [Node 279] Received update for a Supervision session
2026-04-07 19:29:45.450 INFO Z-WAVE: [Node 279] Value updated: 38-0-currentValue 25 => 0
The Leviton dimmer with 45 second duration …
2026-04-07 19:33:48.895 DRIVER » [Node 015] [REQ] [SendDataBridge]
│ source node id: 1
│ transmit options: 0x25
│ callback id: 98
└─[Security2CCMessageEncapsulation]
│ sequence number: 217
└─[SupervisionCCGet]
│ session id: 10
│ request updates: true
└─[MultilevelSwitchCCSet]
target value: 0
duration: 45s
2026-04-07 19:33:49.036 DRIVER « [Node 015] [REQ] [BridgeApplicationCommand]
│ RSSI: -49 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 235
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 10
more updates follow: true
status: Working
duration: 44s
2026-04-07 19:33:49.038 INFO Z-WAVE: [Node 015] Value updated: 38-0-targetValue 16 => 0
2026-04-07 19:34:34.282 DRIVER « [Node 015] [REQ] [BridgeApplicationCommand]
│ RSSI: -50 dBm
└─[Security2CCMessageEncapsulation]
│ sequence number: 236
│ security class: S2_Authenticated
└─[SupervisionCCReport]
session id: 10
more updates follow: false
status: Success
duration: 0s
2026-04-07 19:34:34.283 CNTRLR « [Node 015] Received update for a Supervision session
2026-04-07 19:34:34.284 INFO Z-WAVE: [Node 015] Value updated: 38-0-currentValue 16 => 0
Thanks, I have logged this issue and the engineer is working to fix it.
1 Like
@EricM_Inovelli
Hi Eric,I recently updated my devices to FW: v2.1.0 SDK: v7.24.2 using the file from the Red-Series/Z-Wave/VZW31-SN-2-1-Switch/Beta/2.01/ directory.
Since the update, I have been unable to group my 3-way dimmers. I attempted to roll back to FW: v1.04, but the downgrade failed with an “Invalid firmware target” error.
Could you please advise on how I can successfully roll back the firmware or, alternatively, how to make FW: v2.1.0 work with a 3-way configuration?
Thanks,
Vladi
It is possible that you will need to delete your current associations and recreate them. So
Switch A > Switch B Group 3 & 4 (Maybe 2 depending on use but I always just do 3 & 4)
Switch B > Switch A Group 3 & 4
Change Parameter 59 to 3 on only one of the switches (the master).
@EricM_Inovelli
Hi Eric
This is what I repeated several times.
Associations looks like that
Kitchen Ceiling Dimmer:
Kitchen Ceiling Dimmer W2:
Kitchen Ceiling Dimmer:
Kitchen Ceiling Dimmer W2:
I have many 3-ways and 4-ways configuration in my Z-wave network. Never was a problem.
The only difference is FW version: v2.1.0 vs v1.02
The associations on those two specific devices worked just fine before I moved to v2.1.0
Regards
Vladi
That looks right. I will have to test it out, but the switch may require a factory reset if you haven’t already tried that. There is an SDK update so lots of “cobwebs” might still be intact. I tested vzw31 ↔ vzw32 and didn’t have any problems so I would think that vzw31 ↔ would work . . .
What security level is each device? S2, S0, or non-secure?
Also, after you have the security level confirmed and the associations are looking good like above, can you pull the air gap on each switch to reboot it. Then wait a little bit and retest it?