After the upgrade to OH 3 most of my Zwave items/channels are not updated when switched manually in the hardware. Using OH sitemaps to trigger an update works fine, but when using the actual hardware switch nothing happens;
I had the same problem, my light switches and outlets failed to generate any events in OH. Flipping things from any UI worked without issue (and things worked in the 2.x series).
I created everything in the new UI and imported my zwave items in the Dev tools; where I believe I went wrong was by not setting a profile on the link item page. After this all the outlets and light switches worked like before.
What I can’t figure out is that all of my door sensors continued to work the same and didn’t have the issue, which makes me think its something with my hardware.
Outlets - Leviton DZR15
Light switches - GE / Jasco 12722 (couple of other models for dimmers, but mainly those)
I am having a similar issue with Fibaro FGD212 Dimmer 2 modules not updating when pressing the physical switch on the wall. I am running the latest zwave snapshot as suggested. The normal switches work fine, only dimmers seem to be affected.
openhab> bundle:list -s | grep zwave
263 x Active x 80 x 3.1.0.202101180339 x org.openhab.binding.zwave
When an unsolicited “SWITCH_MULTILEVEL_REPORT” is received from pressing the dimmer switch there is no “STATE UPDATE” for the “switch_dimmer1” channel. Other channels like “sensor_power” are being updated as expected.
Just for grins, remove your FGD212 items from the UI and create them in a .items file. I ended up putting all of my zwave into OH this way and haven’t had a problem since.
Last I was aware, there is an issue with items linking to channels done through the GUI.
Just remember that you cannot configure devices if you do this. You will need to use other software in this case (sorry).
No - this has never been a problem. The issue was related to channel linking and it makes no difference if it is done through the UI or files (the binding has no knowledge of how an item is configured).
@chris, do you think this is a bug in the zwave code? When receiving an unsolicited “SWITCH_MULTILEVEL_REPORT” a “STATE UPDATE” is not being called.
I noticed the sensor power unsolicited command from the dimmer also does not contain the EP-1 context (guess it’s related to the device itself), but the STATE_UPDATE is still called.
Given the Fibaro FGD212 dimmer device only has one physical dimmer, would the dimmer device be required to send the EP context? or should the zwave binding use a default of EP-1 if there is no context in the received command?
This was working with my previous OH2.5 installation.
I had a similar problem with OH 3.0.1 - Release Build
I could only turn on the Z-Wave plug from UI, but not off.
The log showed events for on, but dead silent for off.
Upgrading to 3.1.0-SNAPSHOT - Build #2308 solved it.
Unfortunately I don’t have the log any more.
Do you use the web based UI for configuration? Once I updated to 3.1.0 using openhab-cli, openhab-cli will show the binding at 3.1.0 but the web based UI still shows 3.0.1 (even after reboot).