Thank you very much for your help! Its really appreciated!!
Unfortunately I got a new (old) problem with one of my “Fibaro Dimmer 2” 's. When I operate the dimmer using the switch on the dimmer, this information is not sent to Openhab. The firmware version is different from the ones working. This one has firmware version 3.4 (not working). The rest has version 3.5 (working). All setting looks identical. I tried mapping all channels but no luck. I also set the Lifeline to the controller.
The reports are being sent to the root endpoint - not endpoint 1. If you have changed from an older version of OH, then it might not be a bad idea to exclude the device and add it back so that the associations are completely reset.
Over the past couple of years there have been a lot of changes to ZWave associations - there are now something like 6 different versions of association command classes, and OH 2.4 and above had to change the way this was set to use the newer command class versions. Sometimes this doesn’t get reset, and a complete reset of the device might be the best option.
I just made some findings regarding this Fibaro Dimmer 2, firmware 3.4:
Association Groups: If I set “1: Lifeline” to Controller AND “2: Send BASIC SET command class S1” to Controller, Openhab gets updated on the following channels when I control the dimmer using the switch on the dimmer: “Sensor Power” and “Dimmer Switch 1”. But there is a small bug: When the light is turned on using the switch on the dimmer, Openhab shows the dimming as 100% even though it is dimmed (eg. to 45%). (All this is different from firmware 3.5!)
Chris: I made a factory reset of my z-wave stick, and re-paired all my z-wave devices a few days ago so this should be OK i guess.
Probably this is because of what the device is sending although without the debug log, it’s hard to be 100% sure. You should not need to use the BASIC class - this will cause problems and we should try and work out what is wrong rather than try and fix the problems caused by the workarounds.
Yes, this should be fine if the device was reset. Do you have a debug log from the new inclusion and initialisation? I’d need to see how the device was configured.