Bruce (@bravenel), is there a guaranteed scheduling order of a systemStart trigger relative to when a driver, having an Initialize capability, receives a call to its initialize() routine on reboot?
In other words, are all drivers guaranteed to have received their initialize() calls before a Rule 5.1 with a systemStart trigger starts executing?
Understand that I am not asking about relative order that devices receive their initialize() calls. Instead, itās whether all drivers receive their initialize() calls before a Rule Machine 5.1 app receives its systemStart trigger.
So, I'm thinking that maybe the first thing any Rule triggered by "systemStart" needs to do is a delay, just to make sure anything that Rule's going to play with is awake.
Mike, can you recommend a delay value for that? Are we talking 1 second, 5 seconds, or? Thanks!