I installed an Iris Plug in my bathroom connected to a bidet. Goal was to save money as we donāt use this particular toilet from 12 am to 6 am. Sometimes if my mother-in-law is over, she might use it but I donāt care.
Set up a rule under RM for this. The trigger was a certain time (12 am.)
Action was off with a 6 hour delay then back on thinking it would spring back to life at 6 am.
Wife just yelled that the toilet seat was cold and sent me into a panic. Problem is that it was 7:45 pm. It was working nice and toasty earlier today.
Removed rule and turned it back on remotely (which gave me great satisfaction.)
Please help. And yes, I could probably get it working via Simple Lighting but Iām OCD stubborn.
The way that the OP has it is actually a lot simpler. Having no conditional checks is easier for the hub to accomplish and both have the exact same number of scheduled jobs. the only difference is when the second job gets scheduled. With a specific trigger it gets scheduled at that time the day before (it's a cron) but with the delay it's scheduled at midnight. So, this method is a lot simpler and easier than the conditional.
Wait....so the rule you showed me wasn't the rule that failed but one you just wrote? Well, fix the AM/PM thing,turn on logging and if it fails again, post the logs. Because if that is failing we got bigger problems.
Okay...but we have to wait until the rule doesn't work correctly and then analyze the logs. The logs won't show anything now. You should be able to go into the rule's properties page (gear icon) and see the scheduled task to turn it off at midnight. Then after midnight, that page will show a scheduled task to turn it on at 6 am.
Agreed. Iāve encountered this before and went with simple lighting but Iām trying to wrap my head around all the options and nuances of RM before delving into more complex automations.
Really? I don't really see why he'd need simpler. He's got the rule. It should work. If he didn't know where to start i'd agree but he's got the rule, why pull it out and change it now?
Ok got what you are saying. I actually assumed the a separate delay counter would be calculated for the full delay instead of a another trigger point. So I agreed with you on that.
But, if you are anything like me and update your hub or do a reboot while the delays are active, when the hub restarts it wonāt remember those delays and the delayed actions will not be executed until the next cycle. So his wife will be sitting on a cold seat again for a day.
It is my understanding that the delays are scheduled so unless the the hub was offline at the time of the scheduled delay the action would still occur. The scheduled delay should survive the reboot.
Interesting. Not from my experience but that was from the first few months with my hub starting back in May. Since then I have avoided the long delays. Possibly something addressed with later OS updates.
