I've attached a project that does this.

The hardest part of this one is the long time intervals. The timer node uses a "long" value to count microseconds, so a timer can only count up to about 35 minutes. I hadn't thought to put a limit on the max seconds node, I'll do that in the next update.

To get around that I made a "long timer" node group, in which a timer set to 30 minutes (in the project it's at 1 second so we can see what's happening, change the max seconds value to 1800 for 30 minutes) triggers an incrementor. When the incrementor is full, the timer is done. This is a pretty ugly node group because of the overlap. I should eventually change the timer so it can deal with longer intervals. The last piece of this is that because all numbers in Embrio are from 0 to 1, you have to calculate the appropriate increment value. So if you want it to last for 8 hours, that's 16 ticks at 30 minutes each, so 1 / 16 makes for an increment of .062. I set all the increment values in the main control agent already.

That's the hard part. Next I made an "on off timer" node group, which is just two of these long timers. The first one kicks off the second one when it finishes. Finally on the main control agent, I used 3 of these on off timers, hooked them up to run in sequence, and attached their triggers to the on/off triggers on the switch.

The trick is using "reusable node groups" effectively. If you need help with those this video explains them: http://embrio.io/project...ts/reuseable-node-groups

Sounds like you should consider using a RTC then you can do the math based on reading the actual time and you are not dependent on constant power so you could implement low power options