I have several apps in Rule Machine that are time of day triggered. I have found that if the hub is rebooted after the start trigger then the app does not pick up where it left off unless I open the app and hit run. One case involves the cycling of an electric heater overnight that is turned on/off between two times depending on the reading from a temperature sensor. If the heater is on when the reboot happens then the heater never turns off overheating the room. Any tips?
Check out this hidden gem:
Basically you'd add another Trigger of type Location Event, and select System Start so the rule evaluates on every hub restart. I'll leave it to you to set up the rule logic to avoid unintended consequences.
I would also add a second "failsafe" rule to turn off the heater (and any other problematic devices) independently of the existing rule. I set these up (usually tied to sunset+ or -sunrise) for fans, certain outlets, anything that produces heat, even reset speaker volumes, etc.
3 Likes
What is the setup of the rule and actions? Wait for Events are supposed to make it through a Hub reboot and be unaffected. At least that is the theory.
A lot of this also depends on setup of the overall rule. Required Expressions have an option to be evaluated on system startup. That can help depending on the rule structure.
Finally, for your Heater example, it might be better to split on and off into two different rules. This way the off rule will trigger with any temperature reading above the determined level. It might take a few minutes after a system reboot, but would still prevent the heater from running all night.
2 Likes
