Thermostat automation: Script needs streamlining

[123 (Taras)]

@schnillerman

Just issue the same script commands twice with a delay between

It’s easy to use repeat for this purpose. The service call will be repeated only the number of times necessary or until it reaches a maximum number of attempts.

Repeat automation if service-script fails

The challenge is that there is nothing that tells you the switch failed to turn on other than you visually inspecting the log for errors. When the script commands the switch to turn on but it fails to turn on, does the switch’s state value still indicate that it is off? If it continues to report off even after being commanded to turn on, you can try this technique. In your existing script where it turns on the switch, replace the service call with a repeat that turns on the switch every 10 se…

For added robustness, add an if-then after the repeat to check if the service call was ultimately successful. If it wasn’t then, at a minimum, post a notification reporting the failure.

---

FWIW, I have a ‘goodnight’ script that runs through a long list of things to lock, turn off, etc. For my situation, it doesn’t employ repeat (to try multiple times) but a wait_for_trigger with a timeout. For example, after locking a doorlock, it waits for the lock’s state to change to ‘locked’. If it fails to change within the timeout period, the script announces the failure (and then proceeds to execute the balance of the script).