Created Second PLEG, First PLEG stopped working

Plugins & Plugin Development Program Logic (PLEG)
#1

Good morning everyone,

Yesterday I created a second PLEG to control some lighting around my house. Since creating this second PLEG my schedule based PLEG stopped working. Any suggestions on what to look at to remedy this issue, I tried searching the forums through Google but didn’t find anything.

Here is a link to a forum post of my first PLEG setup: http://forum.micasaverde.com/index.php/topic,18998.msg142981.html#msg142981

Here is the report for the new PLEG I created yesterday:

House Lighting

Device ID: 512014-01-17 09:20:25.170 PLC Version: 5.5

Triggers

Name	Description	Last Trigger	State
BackDoorUnlock	 PIN Code #* is entered on Back Door	2014-01-16 21:37:50.129	true
Night	 Day or Night indicates Night time.	2014-01-16 21:39:35.184	false
BackDoorLock	Back Door: Lock button is pressed	2014-01-17 07:53:43.111	true
Schedules

Name	Type	Time	Days	Random On Delay	Off After Type	Off Time	Off Days	Random Off Delay	State	Last Schedule
LightOffSched	Weekly	23:30:00	1,2,3,4,5,6,7	None	None			None	false	2014-01-16 23:30:00.103
Conditions

Name	Expression	Last True	State
FloodOn	Night	2014-01-16 21:39:35.185	false
FloodOff	not Night or LightOffSched	2014-01-16 23:30:00.106	true
_KitchenOn	Night and BackDoorUnlock	2014-01-16 21:39:35.190	false
_KitchenOff	Night and BackdoorLock	2014-01-16 21:39:35.204	false
Actions

Actions for Condition: FloodOn

Immediate

Device	Action	Arguments
G_Flood Light	SetTarget	 newTargetValue=1
Flood Lights	SetTarget	 newTargetValue=1
Actions for Condition: FloodOff

Immediate

Device	Action	Arguments
G_Flood Light	SetTarget	 newTargetValue=0
Flood Lights	SetTarget	 newTargetValue=0
Actions for Condition: _KitchenOn

Immediate

Device	Action	Arguments
Kitchen Lights	SetTarget	 newTargetValue=1
Actions for Condition: _KitchenOff

Immediate

Device	Action	Arguments
Kitchen Lights	SetTarget	 newTargetValue=0
#2

Looks like the Logic is detecting the inputs … and computing the conditions.

Did you ARM the PLEG ?

#3

Both PLEGs are armed, it is the Space Heater PLEG that isn’t working, here it the status report:

Scheduled Bathroom Heat

Device ID: 382014-01-17 13:18:50.948 PLC Version: 5.5

Schedules

Name	Type	Time	Days	Random On Delay	Off After Type	Off Time	Off Days	Random Off Delay	State	Last Schedule
WeekdayAM	Weekly	06:30:00	1,2,3,4,5	None	Weekly	08:00:00	1,2,3,4,5	None	false	2014-01-17 06:30:00.105
WeekdayPM	Weekly	21:30:00	1,2,3,4,5	None	Weekly	23:00:00	1,2,3,4,5	None	true	2014-01-16 23:11:46.551
Conditions

Name	Expression	Last True	State
HeaterOn	WeekdayAM or WeekdayPM	2014-01-16 23:11:46.555	true
HeaterOff	Not HeaterOn	2014-01-16 08:00:00.102	false
Actions

Actions for Condition: HeaterOn

Immediate

Device	Action	Arguments
Bathroom Heat	SetTarget	 newTargetValue=1
Actions for Condition: HeaterOff

Immediate

Device	Action	Arguments
Bathroom Heat	SetTarget	 newTargetValue=0
#4

Do you still have your log from 21:30 to 23:30 last night ?
Can you email it to me: schaefer@rts-services.com

#5

which log are you referring to and where is it located?

#6

Richard do you mean the LuaUPnP.log? If so I just looked through the log and it starts at 5:30AM today.

#7

I was hoping you still had the LuaUPnP.log
There are a couple of folks that have reported problems with the OFF time in PLEG schedules not running.
It’s intermittent … I am looking for more information for people’s logs and usage to help identify the problem.

#8

Richard, that is good to know however since creating the second PLEG the first PLEG doesn’t start or stop.

Sent from my SCH-I535 using Tapatalk

#9

The problem is because of the bug … your heater is stuck on the ON state … So it will not start again.

If it’s before 21:30:00 … restart your vera …
If it’s after 21:30:00
Open the PLEG … goto to the Input Timers … For Timer WeekdayPM
Click DoItNow
This will turn the timer OFF
Restart your vera.

#10

Thanks for the clarification. It is before 21:30 so I went in and told Vera to reboot. I will give this a try and let you know the results.

Sent from my SCH-I535 using Tapatalk

#11

Opps … got the time wrong … Run the DOIT so the timer shows off … Then Restart Vera.

#12

Running the DOIT and then rebooting fixed the problem. Thank you for your help

Sent from my SCH-I535 using Tapatalk

#13

When this happens again … and it will … since I have not found the bug … please snap the status report and grab a copy of the log file.