I was just making a similar rule couple days ago, the rule was bailing out during the wait command, light left on, motion inactive long past the wait duration. I thought it could be a re-triggering of the event that is messing it up.. used the private boolean as a token to prevent that. No luck.
I have created automations in varios platforms. I never could create one with Hubitat. It is so complicated. Even the basic rules never works with my thermostat. I am about to send this hub to the trash an buy a new thermostat compatible with HomeKit and forget about this little box for all. 😡
👍 - _also_ for the YT algo! 😊
You cannot emphasize enough that Rule Machine is *_TRIGGER_* DRIVEN; Beginners sometimes struggle to understand this...
Excellent point. Actions only occur in a Rule Machine rule after the Trigger Event occurs.
great information!
For simple applications, you've made it harder. Prefer the old method...
I was just making a similar rule couple days ago, the rule was bailing out during the wait command, light left on, motion inactive long past the wait duration. I thought it could be a re-triggering of the event that is messing it up.. used the private boolean as a token to prevent that. No luck.
Try posting a screenshot of your rule at community.hubitat.com. The online community will help get you sorted out.
I have created automations in varios platforms. I never could create one with Hubitat. It is so complicated. Even the basic rules never works with my thermostat. I am about to send this hub to the trash an buy a new thermostat compatible with HomeKit and forget about this little box for all. 😡