Closed rgerrans closed 6 years ago
Wanted to follow-up to see if any had a chance to look I to this?
Not a fix, but a workaround: I have the same problem with a couple of different dimmers, only for switching off. One I resolved by changing the speed that the dimmer dims at (usually a config option, I found using open-zwave control panel), the other by sending the command to switch off, but splitting the flow via a 2sec delay, and sending it again, this results in the status being updated to the correct value.
I have to say that I'd always presumed this was a problem with open-zwave or the dimmers themselves, so hadn't bothered to report it as a problem here...
Thanks. Now that Homeseer has an MQTT plugin I ended up going that route for my ZWave needs.
Devices that do not properly implement status updates typically need to be polled from the OZW lib at regular intervals. I had the same problem with a (long gone) HomePro dimmer module...
Resolving. This is not a node-openzwave problem, but a limitation in the underlying OZW library.
If I change my Cooper dimmer from on/off it's reporting an intermediate dim level instead of the final. Here is an example of going from off to full on at a switch push. openzwave-shared is reporting a final value of 6 but if I run the same experiment with MinOZW I can clearly see the final value of 99 in the logs. Below are logs from both experiment.
node-openzwave-shared
MinOZW