I would like an enhancement in core binding APIs. Sometime my rule or binding goes spooky. There should be a quick and universal way to disengage all communications with that device from OH. Imagine a clutch in your bike / car.
This can also be useful during hardware maintenance/reconfiguration, we don’t want those rules kicking in and activating devices.
The APIs can also be useful toimplement emergency (911) themes. Like fire, theft, assault, lockdown, locks-open, so that hackers/viruses if any or regular rules couldn’t override the emergency theme for lockdown period.
Currently I implement this in bindings individually. I got a binary channel called “Enabled”. When its OFF, the thing handler discards all updates from device and forbids outgoing commands to that device, from OH side the thing is locked in a given state. The state of that device can still be overriden using physical switch, because not all vendors support this kind of lockdown behavior.