Thing Status API - can't get sample code to work

[rossko57]

@Kim_Andersen

The only bad issue is, it needs to be done to every thing.

You cannot make a Group of Things to listen out for in a rule, but you can have a (NGRE) rule listen to all Thing status changes. That rule can then filter out certain classes of Things and/or events.

Monitoring Thing Status

You can achieve that by being creative with the next-gen rule engine (NGRE) and the core.GenericEventTrigger module type and listen to a certain type of event, here ThingStatusInfoChangedEvent. Unfortunately the trick is, this module type is “internal” so you can’t see it in Paper UI. But you can use the Karaf console to add the rule anyway. Create a file somewhere on your filesystem, for instance /tmp/thingstatus.json with this content: [ { "uid": "thingStatusChanged", …

A practical example exploiting Yannick’s method to listen to Modbus poller type things only. Because I wasn’t very comfortable with writing NGRE, it actually transmits events to a DSL rule for further action.

Modbus error management in openHAB

This is a more developed solution to automatically disable failed Modbus Things, and re-enable periodically to attempt recovery. There are two parts to it. But first, create a dummy Item to use as a communication tool between the rules // catcher for Modbus Poller Thing status changes String MBpollerChanged "Failed Modbus UID [%s]" <tools> {autoupdate="false", expire="20m,state= "} I send commands here, rather than state updates, so that a flurry of incidents in quick succession will be hand…