The channel needs to be deleted from the database to completely remove it (which I’ve already done). To stop it doing anything, just unlink it.
Ok but when I unlink whole logic will not work. Unlinlk one item
automatically unlink second.
In paraller I’m trying to replace old binding to
org.openhab.binding.zwave-2.1.0-SNAPSHOT
I’ve found such directory
/var/lib/openhab2/tmp/mvn/org/openhab/binding/org.openhab.binding.zwave/2.0.0
and there is org.openhab.binding.zwave-2.0.0.jar
should I delete old jar and put new one? Is it enough?
Ok - then unfortunately you need to wait for the binding to be updated. At the moment builds are not working so there is no update until this is fixed -:
Do you know when release of 2.1 is planned?
I do not like manual installation from a snapshot and further manual upgrading and I afraid migration between to next snapshot version for sure there will be no migration scripts.
BTW I’ve upgraded to latest available build (I’m still waiting for the new build because it is not fixed) but like in 2.0 duplicated channels are visible for Flood Sensor.
I hope that in new buil it will be fixed and problem with triggering false alarm also will be solved.
Michał
I’m not sure-sorry.
This is expected as there has not been a new build for a few weeks. Hopefully this will be resolved in the next few days.
I’ve installed 2.1 from snapshoot, seems it works properly at least during 3 days I’ve not noticed this bug.