PLEG and daily startup

Plugins & Plugin Development Program Logic (PLEG)
#1

Hi,

I have made a PLEG scene to power on and off the GroupSLK in the morning and in the evening, at different days on different times.
But now It is not working, I think something is wrong with the conditions, but i can’t figure out what.

Can someone set me in the right direction?

Danny

PLEG GroupSLK
Device ID: 722013-10-17 11:18:56.965 PLC Version: 5.1
Schedules
Name Type Time Days Random On Delay Off After Type OA Time OA Days Random Off Delay
Mowodovr_6_9 Weekly 06:00:00 1,3,4,5 None Weekly 09:00:00 1,3,4,5 None
Dizazo_8_10 Weekly 08:00:00 2,6,7 None Weekly 10:00:00 2,6,7 None
Modidozo_22_0 Weekly 00:00:00 1,2,3,4,7 None Weekly 23:59:00 1,2,3,4,7 None
vrzazo_22_2 Weekly 22:00:00 5,6 None Weekly 02:00:00 6,7 None

Conditions
Name Expression
OnEarly Dizazo_8_10 OR Mowodovr_6_9
OffEarly (NOT Dizazo_8_10) OR (NOT Mowodovr_6_9)
OnLate vrzazo_22_2 OR Modidozo_22_0
OffLate (NOT vrzazo_22_2) OR (NOT Modidozo_22_0)

Actions
Actions for Condition: OnEarly
Immediate
Device Action Arguments
GroupSLK On/Off SetTarget newTargetValue=1
Actions for Condition: OffEarly
Immediate
Device Action Arguments
GroupSLK On/Off SetTarget newTargetValue=0
Actions for Condition: OnLate
Immediate
Device Action Arguments
GroupSLK On/Off SetTarget newTargetValue=1
Actions for Condition: OffLate
Immediate
Device Action Arguments
GroupSLK On/Off SetTarget newTargetValue=0

#2

Show a status report …
Which condition dod not work as expected ?

Did you disarm the PLEG ?

#3

OK, here is the status report, thought I send that one…
The PLEG schedule is armed, yes.

On Thuesday the GroupSLK on/off should be on between 8 and 10 in the morning set in schedule Dizazo_8_10, but it tuned off on 08:00 (time in the Vera is correct, checked that first)

I found a something writing this down… On Mididozo_22_0 is 00:00:00 the on time…

Schedules
Name Type Time Days Random On Delay Off After Type OA Time OA Days Random Off Delay State Last Schedule
Mowodovr_6_9 Weekly 06:00:00 1,3,4,5 None Weekly 09:00:00 1,3,4,5 None false 2013-10-17 06:00:00.100
Dizazo_8_10 Weekly 08:00:00 2,6,7 None Weekly 10:00:00 2,6,7 None false 2013-10-15 08:00:00.100
Modidozo_22_0 Weekly 00:00:00 1,2,3,4,7 None Weekly 23:59:00 1,2,3,4,7 None true 2013-10-17 00:00:00.100
vrzazo_22_2 Weekly 22:00:00 5,6 None Weekly 02:00:00 6,7 None false 0
Conditions
Name Expression Last True State
OnEarly Dizazo_8_10 OR Mowodovr_6_9 2013-10-17 06:00:00.103 false
OffEarly (NOT Dizazo_8_10) OR (NOT Mowodovr_6_9) 2013-10-15 08:00:00.108 true
OnLate vrzazo_22_2 OR Modidozo_22_0 2013-10-17 00:00:00.106 true
OffLate (NOT vrzazo_22_2) OR (NOT Modidozo_22_0) 2013-10-15 00:00:00.147 true
Actions
Actions for Condition: OnEarly
Immediate
Device Action Arguments
Slaapkamer groep aan/uit SetTarget newTargetValue=1
Actions for Condition: OffEarly
Immediate
Device Action Arguments
Slaapkamer groep aan/uit SetTarget newTargetValue=0
Actions for Condition: OnLate
Immediate
Device Action Arguments
Slaapkamer groep aan/uit SetTarget newTargetValue=1
Actions for Condition: OffLate
Immediate
Device Action Arguments
Slaapkamer groep aan/uit SetTarget newTargetValue=0

#4

Am I correct to think, the mistype on Modidozo_22_0 with starttime 00:00:00 in stead of 22:00:00 was the problem?

Danny

#5

I had no way to comment on this … since I could not see a problem.
But based on his naming convention … you are probably right.
I could not figure out why he would use a timer that was on all but 1 minute a day.