Fire a Rule when Thing goes OffLine or change its status

[rossko57]

The general idea works for me, example

Modbus error management in openHAB

Positive action Having seen that the error/timeout/retry loop can cause performance loss for survivors, and done what we can to optimize the loop, there is one more trick we could use. Simply not to enter the loop, or at least not so often. We’ve optimized our polling rate for normal use of course, but if we greatly reduce polling further after we’ve encountered a fault - we will also greatly reduce those time wasting error loops. We should still retry once in while, hoping that fault has been …

Make sure you are asking for a Thing that really does change. Not everything in a thing hierarchy goes offline when one part does. Look in the logs.