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).
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).
Same problem here. My environment is OpenHab 3.0.1 (docker), installed on intel nuc with aeotec Z-Stick Gen5. With openhab 2.X (docker) works fine. I noticed the problem is related only to fibaro Z-Wave devices. I have three devices (FGS211 Relay Switch 1x3kW) that control lights and after OH upgrade I no longer receive status updates when I switch device manually.
I tried to change some related thing “Configuration Parameters” (ex. Polling Period) with no success. I tried also 3.1.0 milestone and snapshot docker version but situation doesn’t change.
So far I’ve only tested one Z-Wave module. I have several running on a RPi3 with OH2. Now I’d like to see that I can get one working on a RPi4 with OH3, to understand how OH3 works before moving and rebuilding everything. In my old system I fiddled with just about every setting. Now I’d like to avoid that.
My plug is a: TZWP-102 Telldus socket and energy meter (Swedish).
Old system had a controller from UZB – Z-Wave.Me
New system has Z-Stick Gen5 (not the PLUS, but the one needing a USB HUB to work )
It doesn’t sound too promising if a lot of people experience problems.
Hi,
I have the same problem on two different setups, one using openhabian (latest, ie snapshot version of openhab) and one using docker using 3.1.M5. I can update z-wave devices through the ui but when updating devices manually, the ui isn’t updated.
This is really strange and I think it might have something to do with the Z-wave hw. I used to have a zwave.me gpio board, version 2. The board crashed a week ago and I replaced it with the latest model (ZMMERAZ2).
The old board worked fine with (at least) openhabian and M4 but the new board doesn’t (or rather works as above)
Have no clue right now what to try next. Plan for trying out the z-way just for reference.
I add below zwave log with the hope that someone could find out the problem. This log is related to a manual switch (OFF and ON). As you can see item status is sent to the Z-Wave network but the OH can’t update the fibaro switch item status.
)