Teken Posted August 21, 2014 Posted August 21, 2014 I thought it would be beneficial to many of us to know when a Run At Startup should be used and applied. I think knowing when not to use it is even more beneficial to the masses. What are the caveats of using this feature in ISY-994 Series Controller? Are there downsides in deploying too many and what defines too many? This would also be a good thread for those to supply their programs along with details of how they use, deploy, and the idea of the Run At Startup program. Much Thanks!
Xathros Posted August 21, 2014 Posted August 21, 2014 I have exactly one program that is set to "Run at Startup" I call other programs from that. Some of those call others. Building in some delays here and there, allows me to time phase startup runs so that they don't all just run at once as well as add some logic to decide what needs to run and what doesn't. -Xathros
Techman Posted August 21, 2014 Posted August 21, 2014 Seems it could best be used to send out an email indicating that the ISY is back up after a power failure
PurdueGuy Posted August 21, 2014 Posted August 21, 2014 I only have a few that run at startup, probably the same that many due: Reboot notification: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send Notification to 'All' content 'Startup' Else - No Actions - (To add one, press 'Action') DSCLink heartbeat ($Alarm_Heartbeat is init'ed to 2): If $Alarm_Heartbeat is not 0 Then Repeat Every 0 seconds Wait 10 minutes Send Notification to 'All' content 'Alarm Heartbeat' Else - No Actions - (To add one, press 'Action') DSCLink status: If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Resource 'Alarm - Get Status' Else - No Actions - (To add one, press 'Action') Leak sensor startup program: see here: http://forum.universal-devices.com/topic/11566-leak-sensors-a-suggested-complete-program-package/
Recommended Posts