Disable Zwave things from file

Add-ons Bindings
1

I am setting up ZWave again after switching to OH2.4 and changing ZStick from gen2 to gen5

Frankly speaking ZWave in combination with OH is driving me nuts, when changing something it takes weeks to get it working reliable and things that do work suddenly stop working while adding new things.

Currently had it working with about 10 nodes. Added a Fibaro RGBW controller to the network and OH and all other nodes do not work anymore or do show response times of > 10 seconds.

One of the reasons might be that I have some ‘wall plug’ things, which are not plugged in. Even when not sending commands OH tries to communicate, which blocks ZWave communication to other devices until after a number of retries.

I know I can click 'disable’in the paper UI, but after a reboot they are enabled again. Is there a way to disable ZWave things through config file or via a switch in the UI ?
Wall plugs are movable and might noit always present, so it would be nice to be able to disable the thing while not creating errors in the items/sitemap.

Is there somebody using another ZWave controller in combination with OH ? One which does not delay communication with working devices in case a device becomes un-reachable ?

Any suggestions/experiences welcome.

2

I have not done this but you can enable/disable things via the REST api

image
image.png1078×555 48.7 KB

image
image.png1116×736 41.7 KB

The curl call is:

curl -X PUT --header "Content-Type: application/json" --header "Accept: application/json" -d "false" "http://openhab:8080/rest/things/mqtt%3Atopic%3ABathroomDoor/enable"

Payload is “false” to disable and “true” to enable

log

2019-01-06 12:01:29.546 [hingStatusInfoChangedEvent] - 'mqtt:topic:BathroomDoor' changed from ONLINE to UNINITIALIZED
2019-01-06 12:01:29.562 [hingStatusInfoChangedEvent] - 'mqtt:topic:BathroomDoor' changed from UNINITIALIZED to UNINITIALIZED (DISABLED)
2019-01-06 12:02:59.259 [hingStatusInfoChangedEvent] - 'mqtt:topic:BathroomDoor' changed from UNINITIALIZED (DISABLED) to INITIALIZING
2019-01-06 12:02:59.265 [hingStatusInfoChangedEvent] - 'mqtt:topic:BathroomDoor' changed from INITIALIZING to ONLINE
3

It’s possible to physically move them, but as a mains powered device, this will affect your zwave network. If they are moved, you will need to heal the mesh, so that the controller can figure out the new routes. After moving a mains device, I’ve seen it take a few heals to get things right. Disabling the Thing may prevent the binding from trying to communicate with the offline node, but the mesh will still be mixed up. Once the binding marks the node as offline, my understanding is that communication should stop, except for checking if it is online again. If a device does not have power and it is not marked offline, there may be a bug that should be reported. I suggest not moving the devices, or heal the network after the move.

As for enabling/disabling Things, you can also do this with JSR223-Jython.