As we all know, scheduled tasks keep failing. Many have tried varies ideas of kick starting the schedules or events to keep them running. Some have suggested tying motions or temp sensors to apps since event driven automations work. The issue here is the events are sporadic (too many, too few, not reliable, need more cats).
I built an Arduino project this summer that basically monitors the flow of water in a sump pump and also monitors radon (technically not that selective, other radioactive nuclides would also be picked up), but the point is one of the sensors fires every minute and another every five minutes. So I tied some apps that are more critical that they run periodically to the five minute attribute, and other than being off a few seconds here or there, it works flawlessly.
I have an Armada of Arduinos, so this weekend I was thinking about setting one up with the intended purpose of scheduling. I can easy modify it to work at intervals of 1, 5, 10, 15, etc. minutes with very little effort by setting different attributes (subscribe to the one you want). The only thing left is scheduled jobs that should occur at specific times. I have thought of a couple of ways to accomplish. Either create a schedule table directly into the Arduino, use a PC to talk to the Arduino over the USB port (crank up Visual Studio), or even use a Smart App. All have advantages and disadvantages, but overall, I think my scheduling issues could be behind me or at least improved with respect to reliability.
Technically it would be a Hardware Pollster (@geko).
And before you say it, yes, I know a database fix is coming today. Not to be pessimistic, but scheduling has never been reliable. Schedules have died for years (yes, more than one, makes it sound more dramatic). The second coming is as much a sure thing as the schedules being fixed today.