Using PLEG to set device variables

Plugins & Plugin Development Program Logic (PLEG)
1

I read that PLEG is more reliable than normal vera scenes, at making sure devices are in their expected state even if a vera reboot occurs.

So, as I begin converting scenes to PLEG, I wonder if you can recommend a best practice for ramp ups, without creating an action for each brightness.

So, I created properties for each device I currently ramp up. If I create a cRampup condition, and I set a condition to say, b]cRampup condition,[/b] = tVswitch1 and(cRampTest;NOW >00:10:00) where 10 seconds is purely for testing, how can I have the target devices ramp up in 30 minute intervals, but not create a separate ACTION for each ramp up?

In other words, I do not mind creating multiple conditions, and can a condition trigger a property change on a device light level without resorting to creating an action for multiple light levels at different times?

Is this possible? I saw an app called WAKEUPRAMP, but am unsure if it is still maintained, and if it supports UI5…Soon to need to support UI7 by end of the year (Spoke with Colin @ MIOS this past CES, who indicated we must all migrate to UI7 in 2015).

Thank all for your suggestions !

2

You can arrange a ramping value using a Conditional expression:

Schedules
Rtick OnType: Interval 00:10:00, OffType: Interval 00:00:01

Conditions
Ramp Rtick ? Ramp + 1 : Ramp

Each ten seconds, when Rtick becomes true, Ramp will be increased by one.

The tricky part is managing the boundary conditions and controlling when it runs. Part of this could look like this:

Rrun Ramp < 100 and
Rreset
Ramp Rreset ? 0 : Rrun and Rtick ? Ramp + 1 : Ramp

If Ramp has Repeat set on, you could use its Action to send the current value using the {(Ramp)} syntax for the newLoadlevelStatus value.

The suggestions above are to show the mechanism of a PLEG ramp. Personally I would not want PLEG running an evaluation cycle every ten seconds 24/7 so that I could get a ramp two or three times a day. There are alternatives:

You could use a slower tick with a larger step. If you are already using NOW in your PLEG, it is running every minute anyway. You could use NOW as the tick and make the step 6.

If you need a fast tick, you could use a SelfTrigger Schedule that gets started when you want to start the ramp and restarted when it stops as long as the ramp has not reached the final value.