Problem with item state variable

[vzorglub (Vincent Regaud)]

While you rule may work, it is holding on a thread for a potentially long time and that’s dangerous:
See:

(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…

There is a better approach using timers:
Your rule would become:

var timer = null // global variable
var secondsCounter = 0
rule "Turn Sump Pump On - Afternoon"
when
    Time cron "40 06 10 ? * * *"
then
    Sump_Pump.sendCommand(ON)
    timer = createTimer(now, [ |
        if(!ZWaveNode2ZEN15PowerSwitch_ElectricMeterAmps.Watts.state > 275) {
            logInfo("mySumpLog", "Seconds (" + secondsCounter.toString + "): " + ZWaveNode2ZEN15PowerSwitch_ElectricMeterAmps.Watts.state)
            timer.reschedule(now.plusMillis(1000))
        } else {
            timer = null
            secondsCounter = 0
            Sump_Pump.sendCommand(OFF)
        }
    ])
end