Create a PLEG from previously utilizing Combination switches and vitural.

datammwv · March 3, 2014, 9:29pm

I currently utilizing a combination virtual switch to do the following…

Turn on a lights when a unarmed door is opened, only during evening hours, then turn the lights off at various time segments after door is closed.

I am trying to convert this to a PLEG along with first checking if “living room already on” don’t turn on again and do NOT turn off when door is closed. (ie if sitting watching tv in living room and son comes home opens door and closes door don’t turn that living room light back off.
Richard mentioned the following to me…

The following can be used to map a combination switch into a single condition in PLEG.

First bind your inputs. In the combination plugins, you reference these, but do not give them a name. In PLEG you name each input.
Say you had three triggers in Combination Plugin.
You would have 3 input triggers in PLEG … each with a user defined name, i.e. t1, t2, t3

Create a condition that emulates the combination switch. In this case the condition is also named. Because we can have multiple ones (equivalent to multiple combination switches).
Combination1 t1 + t2 + t3 > 2
In this case the threshold is 2. So if all three triggers are true at the same time the condition Combination1 will be true.

Add your actions to Combination1
This is equivalent to creating a scene that is triggered by the Combination switch.

So I have started the folllowing in a PLEG

Step 1. No issues I created input for each of multiple combinations switches I utilize.
a. Front door is tripped & Back door tripped
B. Barn door is tripped
c. armed room sensor tripped & Arduino motion sensor tripped.
My 1st question lies is that for scenario a & b ; with combination switch I also had a Evening virtual switch turn on 20 minutes prior to sunset and another scene turn the virtual switch off 2 hours before sunrise. ; and c did the same by having another scene with a schedule for 10:00pm on virtual switch and 5 am off virtual switch.

Do I just create these times under schedules under inputs in PLEG. I don’t understand how to get the schedule working in PLEG
Step 2. Richard says create
combination that includes both inputs from a.
combination that include barn door only,
combination that includes armed sensor 1 or arm sensor 2 tripped.
Have no idea what choice to choose on the condition screen… trigger, schedule property, etc…
Then where is the schedule fall into place?
Then where does the check exist that family room light is already on so do not shut off when doors close for example a.

Needless to say haven’t even thought about step 3 in Richards explanation but it appears it is selecting the different conditions created in step 2 and then telling that conditions to in example a. turn on family room light, turn on porch light, turn on hallway light. Wait 2 minutes turn off porch light & hallway light, if family room light was already on prior to this condition turning it on leave on otherwise shut family room light off now.

For scenario B, if barn door is tripped and it was after hours immediately email & sms. If still tripped after 2 minutes enable siren.

For scenario C, if armed motion sensor durring special sleep hours turn on hallway light wait 5 minutes turn off if no motion now. If motion stilll then leave on.

Bulldoglowell · March 3, 2014, 9:58pm

Adding the Day/Night Plugin is a good idea, and you can set it to adjust for when you like Night to begin and end. Example: I use 30min after sunset and 30minutes prior to sunrise. I will assume you installed that…

so, you have a lot going on here so I’ll start you with Scenario A:

you want to DoSomething when Front Door is Tripped and Back Door is Tripped.

Inputs
FrontDoorTripped (Sensor indicates Tripped)
BackDoorTripped (Sensor Indicated Tripped)
BarnDoorTripped (Sensor indicates Tripped)
ArmedRoomSensorTripped (Armed Sensor Indicates Tripped)
ArduinoMotionTripped (Arduino Motion Sensor indicates Tripped)
IsNight (DayNight indicates Night)

Total of 6 Devices, Total of 6 Inputs, Agreed?

Then, select Conditions and create a condition for BothDoorsTripped. Whe you create a condition, there is a space for its name and a place for the argument.

Condition
BothDoorsTripped = FrontDoorTripped AND BackDoorTripped

This will return a true statement (and a resulting True Condition) if both doors are in the tripped state at the same time. This condition will remain true as long as those sensors are both tripped.

You can use the state of a condition in another condition, or fire an Action by using the Actions Tab and entering (just like a scene) actions that will occur when the Condition becomes True.

Does that help?

Actions

DoSomething

datammwv · March 3, 2014, 10:50pm

I created the inputs. as pic1 shows
I created the condition I thought pic2
I created the action as pic3.

What happens now is anytime of day when we open the front door or back door the lights come on

You mentioned front door and back door tripped. I want it to be either the front or back trip turn lights on.
I believe my screw up is something in pic2 the condition.

front_door_trigger_tripped or back_door_trigger_tripped + Start_evening_end_evening

When in inputs I put into schedule the Start_evening_end_evening see PIC4

Bulldoglowell · March 3, 2014, 11:11pm

so you have great progress, just add It_Is_Night_Time to your expression for the condition and it will only fire at night

[quote=“datammwv, post:3, topic:179931”]You mentioned front door and back door tripped. I want it to be either the front or back trip turn lights on.
I believe my screw up is something in pic2 the condition.[/quote]

You see, you need parentheses to force your desired logic.

A or B and C means
Return True if (1) A is true or, (2) if both B and C are true

So you want
A AND (B OR C)
Return True if (1) A is true and (2) either B is True or C is True

Very different expressions.

so again, force the logis with the parentheses…

[quote=“datammwv, post:3, topic:179931”]front_door_trigger_tripped or back_door_trigger_tripped + Start_evening_end_evening

When in inputs I put into schedule the Start_evening_end_evening see PIC4[/quote]

So, here you should try:

(front_door_trigger_tripped OR back_door_trigger_tripped) AND Start_evening_end_evening

this returns true if either the front door is tripped or the back door is tripped and the StartEveningEndEvening Schedule is true

You getting there?

datammwv · March 3, 2014, 11:43pm

Yes getting there. I made it become night and open door and lights came on. then lights went off in correct order.
Now is there a way that prior to the door being open it looks at the “family room light” if this light is on then when the action of turning it off when door closed it doesn’t.

I believe I will have to change the action that triggers for this condition because I cannot use immediately turn on family room light, hallway light, & front porch light. Wait 2 minutes turn off front porch & hall way. Wait 2 more minutes shut off family room light.

My thought is I have to have a check status of family room light if equal to on then don’t shut off later in action against this condition…

Bulldoglowell · March 3, 2014, 11:58pm

[quote=“datammwv, post:5, topic:179931”]Yes getting there. I made it become night and open door and lights came on. then lights went off in correct order.
Now is there a way that prior to the door being open it looks at the “family room light” if this light is on then when the action of turning it off when door closed it doesn’t.

I believe I will have to change the action that triggers for this condition because I cannot use immediately turn on family room light, hallway light, & front porch light. Wait 2 minutes turn off front porch & hall way. Wait 2 more minutes shut off family room light.

My thought is I have to have a check status of family room light if equal to on then don’t shut off later in action against this condition…[/quote]

Exactly right, but I think it is easier than you may think…

Add a Trigger:

FamilyRoomLightOn (Device is Turned On)

Add that trigger to your Condition this way:

LightOnCondition = !FamilyRoomLightOn AND [the rest of your expression]

or exactly the same thing…
LightOnCondition = NOT FamilyRoomLightOn AND [the rest of your expression]

This will prevent the Condition from becoming True if the family room light is on. (we are looking to turn it on only if it is not on already)

And if you don’t turn it on, then you don’t have to turn it off…

got it so far?

datammwv · March 4, 2014, 12:43am

created input

family_room_light_on

if light is turned on

No problem… then you lost me completely.

Goto conditions page
Went down to condition:trigger
put this line in…
!family_room_light_on and front_door_trigger_tripped or back_door_trigger_tripped + it_is_night_time

But when open doors if family room light off will turn it on along with others and will shut off all lights in 2 minutes then toggle all them back on for 2 minutes then toggle all of them & the third time it shut all off & left all off.
But when open doors if family room light already on will turn other two lights on, wait 2 minutes toggle off then all 3 lights back on, wait another 2 minutes and toggle all lights off and on. wait again toggle off then on…

what am I missing? Would there almost need to be two condition for this scenario.
1 condition checks if family room light is on and it is evening and either front door or back door opens then ACTION 1 (Turn on hallway light and front porch light wait 2 minutes turn off hallway & front porch)
2nd condition check if family room light is off and it is evening and either front door or back door open then ACTION 2 (turn on Family room, hallway & porch then wait 2 minutes turn off family room, hallway & front porch)
If this is the way? Where do i put 2nd condition in this plug in? is there a way in condition trigger to put multiple conditions?

Bulldoglowell · March 4, 2014, 12:52am

Remember to force your logic with parentheses, but your thinking is right

Try This:

!family_room_light_on AND (front_door_trigger_tripped OR back_door_trigger_tripped) AND it_is_night_time

There are actually 2 ways that this will return True so one condition statement has two possible ways to become true:

!family_room_light_on AND front_door_trigger_tripped AND it_is_night_time
or
!family_room_light_on AND back_door_trigger_tripped AND it_is_night_time

Not sure what you are saying here:

But when open doors if family room light off will turn it on along with others and will shut off all lights in 2 minutes then toggle all them back on for 2 minutes then toggle all of them & the third time it shut all off & left all off.
But when open doors if family room light already on will turn other two lights on, wait 2 minutes toggle off then all 3 lights back on, wait another 2 minutes and toggle all lights off and on. wait again toggle off then on…

Can you post your PLEG status report?

RichardTSchaefer · March 4, 2014, 12:55am

To add a new condition … go to the Conditions tab … and then click Add Row. It’s pretty obvious how to delete a condition.
You might want to learn how to group term using parenthesis.

So you should have:

YourConditionName ( (!family_room_light_on and front_door_trigger_tripped) or back_door_trigger_tripped ) and it_is_night

You can break this into multiple Conditions:
Condition1 (!family_room_light_on and front_door_trigger_tripped)
Condition2 Condition1 or back_foor_tripped
Condition3 Condition2 and it_is_night

@Bulldoglowell probably interpretted your condition properly.
Breaking it up into multiple conditions is like using parenthesis.
But if there are no actions, or as you progress, there is no time stamp, for the condition and it’s is only referenced in one place … you can collapse them.

datammwv · March 4, 2014, 2:21am

I must have to much on my mind… Was not following anything… I didn’t even have an add… Then stepped back and realized a grave mistake… Was in PLTS not PLEG. That is why not making any since to me… Conditions have a WHOLE different look then conditions in PLEG.

Deleted everything out of PLTS and recreated in PLEG

C1 = !family_room_light_on and Front_door_tripped or back_door_tripped and Night_time_arrived
C2 = family_room_light_on and Front_door_tripped or back_door_tripped and Night_time_arrived

Then on following action
A1 with c1 turns on family room light, hall way, & front porch then turns off in order
A2 with C2 turn on hall way & front porch does nothing to family room.

So all my logic works. When open front door w/o family room light on turn on and turns off. When open front door w/ family room light on leaves it alone & doesn’t shut off.

Nothing happens when move back door with family room light on or off? I did check my event view and see back door tripped
36 2014-03-03, 21:19:56.684 S 24 BACK DOOR Tripped 0

Bulldoglowell · March 4, 2014, 2:31am

family_room_light_on and Front_door_tripped or back_door_tripped and Night_time_arrived

are you sure you don’t want:

family_room_light_on and (Front_door_tripped or back_door_tripped) and Night_time_arrived

datammwv · March 4, 2014, 2:58am

I have it this way and nothing works anymore.
c1 !family_room_light_on and (Front_door_tripped or back_door_tripped) and Night_time_arrived
c2 family_room_light_on and (Front_door_tripped or back_door_tripped) and Night_time_arrived

[table]
[tr]
[td]Manual Scroll
Mon Mar 03 21:38:40.732 - Entry:NOW
Mon Mar 03 21:38:40.732 - EvalConditions:Condition:C1 Trigger:nil Result:false
Mon Mar 03 21:38:40.732 - EvalConditions:Condition:C2 Trigger:nil Result:false
Mon Mar 03 21:38:40.732 - TriggerCondition:None
Mon Mar 03 21:38:40.732 - SweepDB:NOW
Mon Mar 03 21:38:40.733 - CheckRegistration:First:9733009393
Mon Mar 03 21:38:40.733 - Registration:Registered: true $1$1J4tlX5J$DQdLjWk40W2MZyN4RArdAA
Mon Mar 03 21:38:40.733 - Registration:PLC[4]: 85 PLEG#: 1 PLTS#: 1
Mon Mar 03 21:39:40.742 - DelayedEval:Tripped :0=1
Mon Mar 03 21:39:40.742 - DelayedEval:Tripped :0=1
Mon Mar 03 21:39:40.742 - DelayedEval:Status :0=0
Mon Mar 03 21:39:40.742 - DelayedEval:Fake: Property Change for: Night_time_arrived
Mon Mar 03 21:39:40.742 - DelayedEval:Status :0=1
Mon Mar 03 21:39:40.742 - DelayedEval:Status :0=1
Mon Mar 03 21:43:41.025 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:43:41.025 - TPU:Tripped :1=1
Mon Mar 03 21:43:41.025 - TriggerPropertyUpdate:Name:Back_door_tripped State:true Device:24
Mon Mar 03 21:43:41.025 - EvalConditions:Multi Trigger:Back_door_tripped
Mon Mar 03 21:43:41.025 - EvalConditions:Condition:C1 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:43:41.025 - EvalConditions:Condition:C2 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:43:41.025 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393900374.1186, oseq = 1393900380.3282},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = true, seq = 1393901024.6096, oseq = 1393900346.8681},}
Mon Mar 03 21:43:41.031 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:43:41.031 - TPU:Tripped :0=1
Mon Mar 03 21:43:41.031 - TriggerPropertyUpdate:Name:Back_door_tripped State:false Device:24
Mon Mar 03 21:43:41.031 - EvalConditions:Multi Trigger:Back_door_tripped
Mon Mar 03 21:43:41.031 - EvalConditions:Condition:C1 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:43:41.031 - EvalConditions:Condition:C2 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:43:41.031 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393900374.1186, oseq = 1393900380.3282},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901024.6096, oseq = 1393901030.5594},}
Mon Mar 03 21:44:41.041 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:44:41.041 - TPU:Tripped :1=1
Mon Mar 03 21:44:41.041 - TriggerPropertyUpdate:Name:Back_door_tripped State:true Device:24
Mon Mar 03 21:44:41.041 - EvalConditions:Multi Trigger:Back_door_tripped
Mon Mar 03 21:44:41.041 - EvalConditions:Condition:C1 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:44:41.041 - EvalConditions:Condition:C2 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:44:41.041 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393900374.1186, oseq = 1393900380.3282},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = true, seq = 1393901041.2993, oseq = 1393901030.5594},}
Mon Mar 03 21:44:41.043 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:44:41.043 - TPU:Tripped :0=1
Mon Mar 03 21:44:41.043 - TriggerPropertyUpdate:Name:Back_door_tripped State:false Device:24
Mon Mar 03 21:44:41.043 - EvalConditions:Multi Trigger:Back_door_tripped
Mon Mar 03 21:44:41.043 - EvalConditions:Condition:C1 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:44:41.043 - EvalConditions:Condition:C2 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:44:41.043 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393900374.1186, oseq = 1393900380.3282},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:44:41.057 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:44:41.057 - TPU:Tripped :1=1
Mon Mar 03 21:44:41.057 - TriggerPropertyUpdate:Name:Front_door_tripped State:true Device:12
Mon Mar 03 21:44:41.057 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:44:41.057 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.057 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.057 - SaveDB:{{name = ‘Front_door_tripped’, state = true, seq = 1393901057.0499, oseq = 1393900380.3282},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:44:41.065 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:44:41.065 - TPU:Tripped :0=1
Mon Mar 03 21:44:41.065 - TriggerPropertyUpdate:Name:Front_door_tripped State:false Device:12
Mon Mar 03 21:44:41.065 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:44:41.065 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.065 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.065 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393901057.0499, oseq = 1393901064.8899},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:44:41.074 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:44:41.074 - TPU:Tripped :1=1
Mon Mar 03 21:44:41.074 - TriggerPropertyUpdate:Name:Front_door_tripped State:true Device:12
Mon Mar 03 21:44:41.074 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:44:41.074 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.074 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.074 - SaveDB:{{name = ‘Front_door_tripped’, state = true, seq = 1393901073.7944, oseq = 1393901064.8899},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:44:41.074 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:44:41.074 - TPU:Tripped :0=1
Mon Mar 03 21:44:41.074 - TriggerPropertyUpdate:Name:Front_door_tripped State:false Device:12
Mon Mar 03 21:44:41.074 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:44:41.074 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.074 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:44:41.074 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393901073.7944, oseq = 1393901074.2096},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:48:41.306 - Entry:NOW
Mon Mar 03 21:48:41.306 - EvalConditions:Condition:C1 Trigger:nil Result:false
Mon Mar 03 21:48:41.306 - EvalConditions:Condition:C2 Trigger:nil Result:false
Mon Mar 03 21:48:41.306 - TriggerCondition:None
Mon Mar 03 21:48:41.306 - SweepDB:NOW
Mon Mar 03 21:48:41.308 - CheckRegistration:First:9308109393
Mon Mar 03 21:48:41.308 - Registration:Registered: true $1$1J4tlX5J$DQdLjWk40W2MZyN4RArdAA
Mon Mar 03 21:48:41.308 - Registration:PLC[4]: 85 PLEG#: 1 PLTS#: 1
Mon Mar 03 21:48:41.316 - DelayedEval:Tripped :0=1
Mon Mar 03 21:48:41.316 - DelayedEval:Tripped :0=1
Mon Mar 03 21:48:41.316 - DelayedEval:Status :0=0
Mon Mar 03 21:48:41.316 - DelayedEval:Fake: Property Change for: Night_time_arrived
Mon Mar 03 21:48:41.316 - DelayedEval:Status :0=1
Mon Mar 03 21:48:41.316 - DelayedEval:Status :0=1
Mon Mar 03 21:49:41.342 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:49:41.342 - TPU:Tripped :1=1
Mon Mar 03 21:49:41.342 - TriggerPropertyUpdate:Name:Front_door_tripped State:true Device:12
Mon Mar 03 21:49:41.342 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:49:41.342 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.342 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.342 - SaveDB:{{name = ‘Front_door_tripped’, state = true, seq = 1393901341.5518, oseq = 1393901074.2096},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:49:41.345 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:49:41.345 - TPU:Tripped :0=1
Mon Mar 03 21:49:41.345 - TriggerPropertyUpdate:Name:Front_door_tripped State:false Device:12
Mon Mar 03 21:49:41.345 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:49:41.345 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.345 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.345 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393901341.5518, oseq = 1393901344.7094},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:49:41.350 - SetArmed:0
Mon Mar 03 21:49:41.357 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:49:41.357 - TPU:Tripped :1=1
Mon Mar 03 21:49:41.357 - TriggerPropertyUpdate:Name:Front_door_tripped State:true Device:12
Mon Mar 03 21:49:41.357 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:49:41.357 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.357 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.357 - SaveDB:{{name = ‘Front_door_tripped’, state = true, seq = 1393901356.9087, oseq = 1393901344.7094},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:49:41.362 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:49:41.362 - TPU:Tripped :0=1
Mon Mar 03 21:49:41.362 - TriggerPropertyUpdate:Name:Front_door_tripped State:false Device:12
Mon Mar 03 21:49:41.362 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:49:41.362 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.362 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:49:41.362 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393901356.9087, oseq = 1393901362.2697},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901041.2993, oseq = 1393901042.5894},}
Mon Mar 03 21:50:41.400 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:50:41.400 - TPU:Tripped :1=1
Mon Mar 03 21:50:41.400 - TriggerPropertyUpdate:Name:Back_door_tripped State:true Device:24
Mon Mar 03 21:50:41.400 - EvalConditions:Multi Trigger:Back_door_tripped
Mon Mar 03 21:50:41.400 - EvalConditions:Condition:C1 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:50:41.400 - EvalConditions:Condition:C2 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:50:41.400 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393901356.9087, oseq = 1393901362.2697},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = true, seq = 1393901400.3694, oseq = 1393901042.5894},}
Mon Mar 03 21:50:41.402 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:50:41.402 - TPU:Tripped :0=1
Mon Mar 03 21:50:41.402 - TriggerPropertyUpdate:Name:Back_door_tripped State:false Device:24
Mon Mar 03 21:50:41.402 - EvalConditions:Multi Trigger:Back_door_tripped
Mon Mar 03 21:50:41.402 - EvalConditions:Condition:C1 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:50:41.402 - EvalConditions:Condition:C2 Trigger:Back_door_tripped Result:false
Mon Mar 03 21:50:41.402 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393901356.9087, oseq = 1393901362.2697},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901400.3694, oseq = 1393901401.8793},}
Mon Mar 03 21:50:41.440 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:50:41.440 - TPU:Tripped :1=1
Mon Mar 03 21:50:41.440 - TriggerPropertyUpdate:Name:Front_door_tripped State:true Device:12
Mon Mar 03 21:50:41.440 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:50:41.440 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:50:41.440 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:50:41.440 - SaveDB:{{name = ‘Front_door_tripped’, state = true, seq = 1393901439.69, oseq = 1393901362.2697},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901400.3694, oseq = 1393901401.8793},}
Mon Mar 03 21:50:41.443 - TriggerPropertyUpdate:Tripped
Mon Mar 03 21:50:41.443 - TPU:Tripped :0=1
Mon Mar 03 21:50:41.443 - TriggerPropertyUpdate:Name:Front_door_tripped State:false Device:12
Mon Mar 03 21:50:41.443 - EvalConditions:Multi Trigger:Front_door_tripped
Mon Mar 03 21:50:41.443 - EvalConditions:Condition:C1 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:50:41.443 - EvalConditions:Condition:C2 Trigger:Front_door_tripped Result:false
Mon Mar 03 21:50:41.443 - SaveDB:{{name = ‘Front_door_tripped’, state = false, seq = 1393901439.69, oseq = 1393901442.5694},{name = ‘Night_time_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Day_time_has_arrived’, state = false, seq = 0, oseq = 0},{name = ‘Family_room_Light_on’, state = false, seq = 1393899374.2779, oseq = 1393900224.8279},{name = ‘C1’, state = false, seq = 1393899305.6711, oseq = 1393899307.4303},{name = ‘C2’, state = false, seq = 1393899380.1427, oseq = 1393899385.3823},{name = ‘Back_door_tripped’, state = false, seq = 1393901400.3694, oseq = 1393901401.8793},}[/td]
[/tr]
[/table]

Vera Really slow!
Also what is arm disarm for PLEG

Bulldoglowell · March 4, 2014, 3:25am

post this status report

datammwv · March 4, 2014, 3:42am

Program Logic Event Generator

Device ID: 812014-03-03 22:42:32.118 PLC Version: 6

Registration

You have 1 licenses, which allows for 4 PLEG and/or PLTS plugins.
Your license key is: $1$1J4tlX5J$DQdLjWk40W2MZyN4RArdAA
Triggers

Name Description State Last True Last False
Front_door_tripped FRONT DOOR is tripped false 2014-03-03 22:41:20.408 2014-03-03 22:41:24.748
Back_door_tripped BACK DOOR is tripped false 2014-03-03 22:41:14.562 2014-03-03 22:41:14.579
Night_time_arrived Day or Night indicates Night time. false 0 0
Day_time_has_arrived Day or Night indicates Day time. false 0 0
Family_room_Light_on Family Room Light is turned on false 2014-03-03 22:41:21.628 2014-03-03 22:42:06.767
Conditions

Name Repeat Expression State Last True Last False
c1 No NOT(Family_room_Light_on) AND Front_door_tripped or Back_door_tripped and Night_time_arrived false 2014-03-03 22:41:20.413 2014-03-03 22:41:21.633
c2 No Family_room_Light_on and (back_door_tripped or Front_door_tripped) and Night_time_arrived false 0 0
Actions

Actions for Condition: c1

Immediate

Device Action Arguments
Family Room Light SetTarget newTargetValue=1
Hallway Light SetTarget newTargetValue=1
Family Room Plug SetTarget newTargetValue=1
Front Porch SetTarget newTargetValue=1
Delay 45

Device Action Arguments
Family Room Plug SetTarget newTargetValue=0
Family Room Light SetTarget newTargetValue=0
Hallway Light SetTarget newTargetValue=0
Front Porch SetTarget newTargetValue=0
Actions for Condition: c2

Immediate

Device Action Arguments
Hallway Light SetTarget newTargetValue=1
Family Room Plug SetTarget newTargetValue=1
Front Porch SetTarget newTargetValue=1
Delay 45

Device Action Arguments
Family Room Plug SetTarget newTargetValue=0
Hallway Light SetTarget newTargetValue=0
Front Porch SetTarget newTargetValue=0

datammwv · March 4, 2014, 4:00am

Not being a programmer and learning to be a programmer; case matters and location of parentheses. However nothing works on the PLEG.

Well It appears that the day/night plugin is not registering night. Even though it is.
I click on the icon (that is showing moon) and then it changed it to night and status then shows true.

Is there soemthing another way to NOT use the day/night plugin and choose the times I want?

Even though I can see door being triggered open and My Night plugin is set to night.

Family_room_Light_on AND (back_door_tripped OR Front_door_tripped) AND Night_time_arrived
!Family_room_Light_on AND (back_door_tripped OR Front_door_tripped) AND Night_time_arrived

[code]Program Logic Event Generator

Device ID: 812014-03-03 23:02:57.698 PLC Version: 6

Registration

You have 1 licenses, which allows for 4 PLEG and/or PLTS plugins.
Your license key is: $1$1J4tlX5J$DQdLjWk40W2MZyN4RArdAA
Triggers

Name Description State Last True Last False
Front_door_tripped FRONT DOOR is tripped false 2014-03-03 23:02:13.428 2014-03-03 23:02:17.698
Back_door_tripped BACK DOOR is tripped false 2014-03-03 22:41:14.562 2014-03-03 22:41:14.579
Night_time_arrived Day or Night indicates Night time. false 0 0
Day_time_has_arrived Day or Night indicates Day time. false 0 0
Family_room_Light_on Family Room Light is turned on true 2014-03-03 23:02:06.168 2014-03-03 23:01:31.107
Conditions

Name Repeat Expression State Last True Last False
c1 No !Family_room_Light_on AND (Front_door_tripped OR Back_door_tripped) AND Night_time_arrived false 2014-03-03 22:41:20.413 2014-03-03 22:41:21.633
c2 No Family_room_Light_on AND (back_door_tripped OR Front_door_tripped) AND Night_time_arrived false 0 0
Actions

Actions for Condition: c1

Immediate

Device Action Arguments
Family Room Light SetTarget newTargetValue=1
Hallway Light SetTarget newTargetValue=1
Family Room Plug SetTarget newTargetValue=1
Front Porch SetTarget newTargetValue=1
Delay 45

Device Action Arguments
Family Room Plug SetTarget newTargetValue=0
Family Room Light SetTarget newTargetValue=0
Hallway Light SetTarget newTargetValue=0
Front Porch SetTarget newTargetValue=0
Actions for Condition: c2

Immediate

Device Action Arguments
Hallway Light SetTarget newTargetValue=1
Family Room Plug SetTarget newTargetValue=1
Front Porch SetTarget newTargetValue=1
Delay 45

Device Action Arguments
Family Room Plug SetTarget newTargetValue=0
Hallway Light SetTarget newTargetValue=0
Front Porch SetTarget newTargetValue=0[/code]

RichardTSchaefer · March 4, 2014, 4:17am

Toggle the Day or Night switch … so that the PLEG will sync up with it.

Notice from the Status report that the Night_time_arrived trigger is false. That’s because an event has not happened yet.

datammwv · March 4, 2014, 4:28am

Yes, I am noticing that even though the ICON shows moon it thinks it is day!
Is there another way other then the day/evening plugin to schedule these that is more reliable?
Does day & night get confused a lot?

RichardTSchaefer · March 4, 2014, 4:46am

It’t not confused … it’s just not initialized.

PLEG will be out of sync until Day Or Night transitions next … witch is at sunrise and sunset each day.
However you can manually set the day and night settings … That’s a feature of that plugin. It allows you to override the automatic setting so you can test/force day or night behavior.

PLEG works based on events when things happen. When you first define triggers … They can be out of sync until the events happen.

datammwv · March 4, 2014, 1:47pm

For my next one that I wish to do you have examples of how to read a motion sensor that I can pull from. But what I need to know is that for my motion sensors I do not want to use the day/evening plugin because that is not time I wish to arm and trigger on motion with those sensors. Is this where I use schedule from the input screen tab? have start time day of week 10pm have end time day of week 5:00am. Then do I just tell the condition to use that names schedule IE s1. Then S1 and motion sensor1 or motion sensor 2…

Bulldoglowell · March 4, 2014, 2:10pm

To be clear, you only want the sensors to be triggered when:

a) they are ARMED (sensors can function in two states; armed and not armed)

and

b) During a Schedule

or, just B?