S2 switches not updating state when apps give command

C-8 Pro hub, version 2.3.9.176

I have 8 identical Inovelli Z-Wave on-off switches (LZW30-SN). Six of them are S2 authenticated, while the other two are S0. I’ve noticed an issue with the S2 switches I’d like to troubleshoot.

In the "devices" tab, all switches (S2 and S0) accept "on" and "off" commands instantly, and "Current States - switch" updates immediately. However, when I send a command via a Hubitat app (e.g., Button Controller 5.1, Simple Automation Rules, Rule Machine), the S2 switches respond to the command but don’t update the “Current States - switch” value.

The issue is, for example, when the switch is off, the first toggle works correctly, but the state doesn’t update, so the app still thinks the switch is off. This causes all subsequent toggle commands to try to turn the switch on, so nothing happens. If I manually press "on" in the devices tab, the state updates, allowing the next toggle to work correctly. The S0 switches don't have this behavior at all, they work fine.

I haven’t seen any errors in the logs, but I’m wondering if anyone has had similar issues or if there’s something else I can check.

I managed to patch over the issue by adding a "refresh" command with a one second delay before the "toggle" command, but I expect this won't work super reliably, so if anyone has any suggestions for more fundamental fixes, that would be great!

That is super strange. They should update status instantly. Can you post a screen shot of your entire z-wave details page (use windows snip)

What driver are you using for these switches?

Also update your platform to .197 and see how it behaves (you can always roll back)

What driver are you using? .. Some Z-Wave devices won't respond with an update when using Supervision, because supervision responds with success.. The driver can be updated to fix this.

2 Likes

Problem exists on firmware versions 1.17 (old beta), 1.20 (latest production), and 1.22 (latest beta).

Thanks! Updating to .197 didn't fix the issue.

I've tried three drivers for the switches, 1.17 (old beta), 1.20 (latest production), and 1.22 (latest beta).

Please see below for the details - it's a lot of devices, so I put a red box around the names of these switches.

By the looks of it you have at least 2 ghosts which may be hindering response. (61 & 69) I would get rid of those and see how things behave.

Removing those two ghosts didn't change the behavior. Rebooted hub and rebuilt database after removing, gave it a few hours for the mesh to correct if anything changed, still no dice.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.