This is not fully true. I sometimes had the situation that there were people who immediately said something like “This is a problem that I know and it is easy to deal with.” And in my opinion it is better to wait for such an answer than having people dig into megabytes of logs in the first place. But this is debatable
This looks to be caused by the device sending the BASIC_SET command, which contains no information about what type of sensor it is. This command class is (was!) then linked to the BINARY_SENSOR class, and with no type of sensor, it just triggers all types.
I’ve removed this link, but now it will not trigger at all. Ideally the device should be configured to send the BINARY_SENSOR command, but I don’t see any way to control this, so I don’t see how it is possible for the binding to know what the sensor type is.
Please keep in mind that it worked perfectly under the “old” zwave binding, with exactly the same settings. There must be (i.e. “is”) a way to distinguish between the two sensors.
I understand that you changed something. How do I get this into my system? Remove the thing and add it again? (or can I just edit the json? )
Wait for the next export to Github (usually weekly) then the snapshot build need to compile the changes into the OH snapshot.
If you are running OH older than 2.5M3 you can use this script to install the new binding. (not sure if 2.5M3 works)
You then need to delete & re-discover the Thing. It should have the same ID so your Items & rules should still work properly.
No - not with the BASIC command class - ONLY with the BINARY_SENSOR command class.
It may be that this is all just down to the BASIC command class being mapped to the BINARY_SENSOR in the database. This might be the problem and I’ve now fixed that.
Okay. I never said is should be the BASIC command class
That sounds like a logical explanation for the effect that we see.
Thank you so much in advance Chris. Unfortunately I won’t be able to test that on a short term, but hopefully by next week. I will keep you guys posted.
To get the latest binding fixes you likely need to manually install a snapshot binding.
@5iver wrote a scout that worked prior to M3 but I have not tried it on that version. I may be able to test later this week since I am setting up another M3 installation for testing some new devices.
I installed the "org.openhab.binding.zwave-2.5.0-20191015.051545-123.jar " version yesterday. It works so far but does not recognize the PSM02 sensor as such and the things remains an initializing state even after more than 12 hours.
I deleted the thing in the Paper UI, rediscovered it, added it from the inbox and waited for something to happen.The title of the thing-page says " Z-Wave Node 008 (013C:0002:0002:1.0). It never gets detected as a “PSM02 Slim Multisensor” as in the normal version of the binding.
It works in the sense that messages are received, but there is no change regarding the behaviour that I described as the initial problem.
I guess there is some mess with cached data, maybe the xml files…?