Restart a thing if connection is lost or if no new data within xx seconds

[matze.lingen (Matthias K.)]

Hi everybody,
i have a little problem, i have some “things” witch stop recivieng data from here to then. i hafe to disable the thing and enable it again and everything starts working again.
now i searching for a solution witch check the last timestemp of the last recive from an item and the connection state from a thing and if the connection is lost or the last timestemp of an item is older than xx secionds than i want to disable and enable the thing to get it back to work.
so has someone a hint or a solution for me?
thanks in advanced
matze

[Matze0211 (Matthias)]

To get the time off the last update: you can use a profile

To detect thing status: that’s available via rules, you can even trigger a rule of a thing status is changing

[matze.lingen (Matthias K.)]

a profile? hmm i have to look who this works.
ok the rule have i seen put how can i do an “disable” and “enable” or restart of a thing. i don´t find this in blocky. or do i have to write a rule by my self?

[Matze0211 (Matthias)]

You need to use the restapi the enable / disable a thing.
If you search the forum, you should find several examples

[rpwong (Russ)]

I don’t know how to do that in Blockly, but in RulesDSL it’s something like this.

Renew bridge connection with rule after midnight

If you’re using Rules DSL, set up an API token and then use a rule like this to disable and re-enable the thing. I’ve shown the cron as 1:30am every day. when Time cron "0 30 1 ? * * *" then //Header for REST authentication //https://community.openhab.org/t/javascript-syntax-to-insert-api-token-into-sendhttpgetrequest/116798 val headers = newHashMap("Authorization" -> "Bearer INSERT-API-TOKEN-HERE", "WWW-Authenticate"-> "Basic") //disable the thing sendHttpPutRequest("h…

Note that this is an OH3 example, and may have changed somewhat in OH4.

I recommend disabling/enabling on a schedule so that you’re being proactive. Then it’s a simple CRON rule that doesn’t care about the actual status of the thing.

[justaoldman (Justan Oldman)]

tactical fix yea sure set up a rule and reinitialize the thing on a recurring basis.
long term strategic fix trouble shoot why you are having to take this action.
What is actually causing the thing to become unresponsive is what I would be chasing if this was happening on my systems.

[rlkoshak (Rich Koshak)]

In JS Scripting there is a setEnabled() function you can use to enable/disable the Thing.

In the Marketplace there is a generic rule template you can install and use to call a rule of the own when the Things go OFFLINE.

Thing Status Reporting [4.0.0.0;4.9.9.9]

[logo] A rule that triggers when a Thing changes its status and calls a user defined rule with the Thing and information about the Thing. The conditions of the called script are enforced so events can be filtered there (e.g. only process changes from ONLINE to some other status). The following properties are passed to the called rule: Property Contents thingID The UID of the Thing that changed status oldStatus The status the Thing was in before the change oldDetail Some Thing stat…

If the Thing remains ONLINE and you can only detect it’s broken because some Items so updating, you can use the Threshold Alert rule template to again call a rule of your own when an Item doesn’t update for a given amount if time. Threshold Alert and Open Reminder [4.0.0.0;4.9.9.9]

The hard part will be mapping the Item to the Thing which isn’t so easy. I would add that as Item metadata.

[Matze0211 (Matthias)]

@rlkoshak

In JS Scripting there is a setEnabled() function you can use to enable/disable the Thing.

Is this something (relatively) new?

[rlkoshak (Rich Koshak)]

Not really. I think it’s been a part of the GraalVM JS helper library since the beginning. I know there is similar functionality in jRuby as well.