I had a routine that had a dependency on Saturday at a specific time suddenly yesterday (Tuesday) start firing, shutting off most of my lights at odd times of the day. Always a pleasant event, with the wife WTF’ing (ok I was too)…
The routine is designed to shut the lights off Saturday night at 11:50pm if there had been no motion in a room for the past hour:
Location mode: Away, Home, Night, Not Home - precondition
Bedroom Motion Sensor: no motion for 1 hour
Run scene: Good Night
From the History I could see this routine was firing an hour after Bedroom Motion Sensor logged No motion, starting on the second No Motion event of the day. Never mind that it wasn’t Saturday at 11:50pm, the thing fired at 7:11am, 8:32am, 11:03am, 2:42pm, 4:28pm… you get the idea.
But wait: it gets better! If there was an intervening motion event on the bedroom sensor during the 1 hour period, it still fired!!! Wait, what? Yep.
6:11am No motion
7:11am Routine activated
7:32am No motion
8:32am Routine activated
Double head turner. Ready for a triple?
The hub rebooted due to the firmware update, and even after the reboot this was still going on.
This was PERSISTENT corruption in the routine data of some sort.
After realizing this, I went into the routine and saved it and wouldn’t you know it… problem disappeared.
This is what I get for migrating early from a Webcore piston (story for another post)… VERY disconcerting.