Funny Situation; I have a Fibaro Doorsensor (the new model) that was never working with OH 1 on my desk. while working on the paper UI of OB2 I tipped at the sensor, and suddenly it worked with OH2. So I wanted to integrate it fully to my installation by setting the location, but found out that the thing could not be saved in paper UI, as parameter 70 “scene activation” was set to “0”, whereas the UI asked for “1” as the smallest acceptable number.
Changing it to “1” I could save the thing with the now correctly set location, but immediately it stopped working. Looking at the help text for parameter 70 it says, that “0” is allowed! How can I get it back?
Logging shows, that the Sensor is working “somehow” as I get lines like
"19:19:15.535 [WARN ] [class.ZWaveMultiInstanceCommandClass] - NODE 8: Originating Command Class ALARM (0x71) was on the root node." every time I take the sensor and the magnet apart/bringing them back together. But there are no logs for the associated items.
Additional Information: After upgrading I had all items that had been in the items file dubbled, as they where now also in the database. So I deleted the items in the items file, but found out that I still could not edit the ones in the database. I had to delete them too, and configured new ones, to make any changes. So it might be, that this Situation may also be affected by the “new” items.
P.S I also have a Fibaro Floodsensor here that never worked with OH1, but is reported online in OH2. Automatic generated items exist, but also show no reaction to anything the sensor reports (it gives “noise” on the device itself, so I know it is working"