PLEG stops responding after actions are processed

I am rather new to PLEG and trying to create a logic that allows 3 lights to be controlled by two motion sensors. I started with the exmple in [url=http://forum.micasaverde.com/index.php/topic,14709.0.html]http://forum.micasaverde.com/index.php/topic,14709.0.html[/url] and modified form there but now I think something I did may be causing things to crash or become hung. Here is my scenario. I have a stairwell in my house that I want to control via motion. It’s a windy staircase so two motion sensors are needed to catch both someone entering from above and from below. There are three lights that need to be controlled. My motion sensors have a 7 minute timeout. I also want the ability to flip the light to manual as per the example. I created a logic using one motion and one light which worked great. I then modified it for the other lights and the other motion sensor. Now when one sensor trips some but usually not all 3 of the lights will turn on and then everything else seems to stop processing. I cannot do anything inside the PLEG device including view Report, Status and Logs. Any help with the logic or why it is is unstable would be exrememly appreciated. Here is my configuration.

[code]Triggers

LightBHCHOn Whenever the Back Hall CH is turned on
MotionBackHall Whenever Back Hall Motion detects motion whether is armed or disarmed
LightBHSCOn Whenever the Back Stairs SC is turned on
LightDHSCOn Whenever the Down Hall Sc is turned on
NoMotionBackHall Whenever Back Hall Motion stops detecting motion whether is armed or disarmed
NoMotionUpstairs Whenever Upstairs Motion stops detecting motion whether is armed or disarmed
MotionUpstairs Whenever Upstairs Motion detects motion whether is armed or disarmed

Conditions

Name Repeat Expression
TurnOnBHCH No !LightBHCHOn and (MotionBackHall or MotionUpstairs) AND ((!LightBHCHOn;MotionBackHall) or (!LightBHCHOn;MotionUpstairs))
TurnOnBHCH No !LightDHSCOn and (MotionBackHall or MotionUpstairs) AND ((!LightDHSCOn;MotionBackHall) or (!LightDHSCOn;MotionUpstairs))
TurnOnBHCH No !LightBHSCOn and (MotionBackHall or MotionUpstairs) AND ((!LightBHSCOn;MotionBackHall) or (!LightBHSCOn;MotionUpstairs))
AutoOnBHCH1 No TurnOnBHCH; LightBHCHOn > 15
AutoOnDHSC1 No TurnOnBHCH; LightDHSCOn > 15
AutoOnBHSC1 No TurnOnBHCH; LightBHSCOn > 15
TurnOffAutoOnBHSC No AutoOnBHSC1 and LightBHSCOn and (LightBHSCOn;NoMotionBackHall) and (LightBHSCOn;NoMotionUpstairs) and (NoMotionBackHall; now > 3:00) and (NoMotionUpstairs; now > 3:00)
TurnOffAutoOnDHSC No AutoOnDHSC1 and LightBHSCOn and (LightDHSCOn;NoMotionBackHall) and (LightDHSCOn;NoMotionUpstairs) and (NoMotionBackHall; now > 3:00) and (NoMotionUpstairs; now > 3:00)
TurnOffAutoOnBHCH No AutoOnBHCH1 and LightBHSCOn and (LightBHCHOn;NoMotionBackHall) and (LightBHCHOn;NoMotionUpstairs) and (NoMotionBackHall; now > 3:00) and (NoMotionUpstairs; now > 3:00)
TurnOffManualOnBHSC No !AutoOnBHSC1 and LightBHSCOn and (LightBHSCOn;NoMotionBackHall) and (LightBHSCOn;NoMotionUpstairs) and (NoMotionBackHall; now > 3:00:00) and (NoMotionUpstairs; now > 3:00:00)
TurnOffManualOnDHSC No !AutoOnDHSC1 and LightDHSCOn and (LightDHSCOn;NoMotionBackHall) and (LightDHSCOn;NoMotionUpstairs) and (NoMotionBackHall; now > 3:00:00) and (NoMotionUpstairs; now > 3:00:00)
TurnOffManualOnBHCH No !AutoOnBHCH1 and LightBHCHOn and (LightBHCHOn;NoMotionBackHall) and (LightBHCHOn;NoMotionUpstairs) and (NoMotionBackHall; now > 3:00:00) and (NoMotionUpstairs; now > 3:00:00)

Actions

Actions for Condition: cTurnOffAutoOnBHCH

Device Actions:

Immediate

Device Action Arguments
Back Hall CH SetLoadLevelTarget newLoadlevelTarget=0
Actions for Condition: TurnOffAutoOnBHSC

Device Actions:

Immediate

Device Action Arguments
Back Stairs SC SetLoadLevelTarget newLoadlevelTarget=0
Actions for Condition: TurnOffAutoOnDHSC

Device Actions:

Immediate

Device Action Arguments
Down Hall Sc SetLoadLevelTarget newLoadlevelTarget=0
Actions for Condition: TurnOnBHCH

Device Actions:

Immediate

Device Action Arguments
Back Hall CH SetLoadLevelTarget newLoadlevelTarget=100
Actions for Condition: TurnOnBHCH

Device Actions:

Immediate

Device Action Arguments
Back Stairs SC SetLoadLevelTarget newLoadlevelTarget=100
Actions for Condition: TurnOnBHCH

Device Actions:

Immediate

Device Action Arguments
Down Hall Sc SetLoadLevelTarget newLoadlevelTarget=100[/code]

Try to reload Vera and also refresh your browser

Thanks for the Reply. Sorry I should have mentioned I did both of those. I had also recently upgraded from UI5 to UI7. I thought maybe this was UI7 bug related so I downgraded back to UI5.

in that case you must upgrade the PLEG and PLC Plugins. There is a. Topic near the top how to do that. Sorry I am on a mobile device and it’s not convenient to look it up for you.

I followed the update procedure here [url=http://forum.micasaverde.com/index.php/topic,14446.0.html]http://forum.micasaverde.com/index.php/topic,14446.0.html[/url] after I upgraded to UI7 and after I downgraded to UI5. I have also uninstalled and re-installed the plugins and typed the configuration from scratch but no matter what I do I encounter this issue.

Sounds like the VERA is busy, maybe rebooting. Is this a VERA lite? Have you run the Logger then tried to trigger them and see what it spits out?

Do you have other problems ?
Is your Vera Restarting ?
Do you have enough free memory for the Apps your are running ? (Are you on a Vera Lite ?)
Have you looked in your Vera Log file to see if there are any obvious errors ?

When you downgraded to UI5 … did you restore a backup from when you were on UI5 ? A backup from UI7 may have problems …

I have resolved the issue but no I didn’t seem to have any other problems.
I am running Vera3 and only a small handful of apps.
The issues started on UI5. I upgraded to UI7 to see if that would make a difference and it only got worse. I then downgraded back to UI5 since I can’t stand UI7. Restoring my vera3 to when I had just the one light and sensor working is what seems to have fixed it. I have since put all the sensors and lights back in and it works well now. So something either related or unrelated to PLEG hosed my VERA 3 Config but it wasn’t the PLEG Config because that is currently working.
Unfortunately I have no experience with using the VERA logging so I didn’t take a look. I guess I really need to brush up on how to enable and access the VERA Log Files.

Anyway thanks for trying to help.