[SOLVED] Simple Switch OFF rule

[vzorglub (Vincent Regaud)]

Hello,
First of all you should not use Thread::sleep in rules unless REALLY necessary, that’s why:

(OH 1.x and OH 2.x Rules DSL only] Why have my Rules stopped running? Why Thread::sleep is a bad idea

EDIT: While the general advice in this article still applies (i.e. it’s always worth while to make short running rules), the problem described in this article only applies to OH 1.x and Rules DSL in OH 2.x. In OH 3 and beyond, this is no longer a problem so if your rules stop running in any version of OH released in the last two years (as of this edit in 1/2023) this is not your problem. By way of explanation, in OH 3 each rule gets it’s own thread. It is no longer possible for a rule to starve…

You have two options here, you can use a timer or the expire binding
I will show you the expire binding solution

Install the expire binding
Create a switch item:

Switch KMotionPresence_Timer { expire="1m, command=OFF }

This item, when turned ON will turn itself OFF after 1 minute unless updated to ON
So, knowing that, your rule becomes:

rule "Presence in Kitchen changed"
when
    Item KMotionPresence changed
then
        KMotionPresence_Timer.sendCommand(ON) //Start timer whenever presence changes in the Kitchen
end

rule "Kitchen Presence Timer expires"
when
    Item KMotionPresence_Timer changed to OFF
then
    if(KMotionPresence == OFF && LightRoofKitchen.state == ON) {
        logInfo("RULE", "Light switched OFF, because of no presence")
        LightRoofKitchen.sendCommand(OFF)
    }
end