This is a new one for me (well apparently not that new because I can see from the logs it has been doing every day since 3/12 ~ which was prob the last time I rebooted and cleared them):
This basic rule that just states:
When Time of Day is 3:00 AM ... Toggle [a virtual button]
when i check the logs of that device is it being toggled at 10:00 AM like clockwork. - and the rule even shows this in details:
As noted in the title, hub time is correct and all my other basic rules that use time of day are working properly at the expected time.
I can easily delete this rule and read add it if that will fix it but before I do I figured I would ask the community for advice, has anyone encountered this?
I can't explain why that's happening, but while you're looking into this, I'd also deconflict this with when the hub's own overnight stuff is scheduled -- IIRC, 3am is when it defaults to doing a local backup, for example.
For my own regularly-scheduled maintenance-related rules, I've started doing an small timing offset just to ensure that rule doesn't collide with something else timing-wise... For example, instead of running at 3:00 am, I run it at something like 3:08 am.
1 Like
good idea, and actually something I do on server schedules ~ I didn't even consider for this simple rule
update: I went to change it and the next scheduled was still saying 10:00 ~ odd. So I changed to "sunset" then back to time of day, then it took as 3:10 AM
1 Like
try a reboot with rebuild
I guess there’s no harm in doing so, though my last reboot before today was a reboot/ rebuild/ clear logs kind of reboot ~ I won’t know if that would have corrected it since I manually updated already- but I will know if that changes it.
