Repository navigation
Replies: 4 comments 2 replies
|
This is a genuine bug, not a usage issue — thanks for the clear report and screenshot. 🙏 Root cause: On broadcast/multicast (virtual) nodes, zwave-js exposes every value as write-only (a broadcast’s state can’t be read back). Z-Wave JS UI rendered every write-only boolean as a single fire-once button, and that button is hard-coded to always send Note the same limitation applies to Basic CC on broadcast/multicast, not just Binary Switch. A fix is on the way that restores the actuator-vs-trigger distinction so Binary Switch (and Basic) show a proper On/Off toggle on broadcast/multicast nodes, while genuine triggers keep their single button. I’ll link the PR here. |
|
Fix opened: #4751 — Binary Switch (and Basic) now render a proper On/Off toggle on broadcast/multicast nodes, so OFF works. Genuine momentary triggers (e.g. Identify, Meter reset) keep their single button. |
|
Wasn't sure if it was a bug or I was missing something, so opted for the discussion option. Thanks for the fix ! |
|
Any update on this? |
Uh oh!
There was an error while loading. Please reload this page.
Unlike the other command classes, I only see these that turn the device on (true). How to turn off (false?). Tried clicking again, but still true

All reactions