PLEG actions no longer completing

Plugins & Plugin Development Program Logic (PLEG)
#1

I have PLEG turn on several lights at sundown. It all used to work fine. Now it seems that it will turn on only the first light. I watched the events in SSH and it didn’t even seem to try to trigger the others. (I am very new to SSH maybe I didn’t look at the right thing). I saw another post where multiple actions are not completing, but I seem to have higher version numbers which hopefully the problem was is fixed. Any help is greatly appreciated!

Vera3 Firmware: 1.7.830
PLC: 8.16
PLEG: 8.11

#2

Did your turn on debugging logging for the PLEG device ?
Try to reorder your actions … maybe your first device is not responding.

#3

Reordering seems to have no effect, other than whatever is first is the only thing executed. All devices are connected and promptly respond to any command given outside of PLEG.

This is the PLEG log after triggering the “Sunset”

The Sun setting trigger a condition that checks if certain lights are already on. If they are not on, then they are turned on to specific levels. If they are on then nothing happens.

TriggerPropertyUpdate:Status Thu Aug 18 09:33:53.755 - TPU:Status :0=0 Thu Aug 18 09:33:53.756 - TriggerPropertyUpdate:Name:Sunset_has_arrived State:true Device:45 Thu Aug 18 09:33:53.757 - FireAction:Nothing found for:Sunset_has_arrived Thu Aug 18 09:33:53.758 - TPU:Status :0=1 Thu Aug 18 09:33:53.759 - TriggerPropertyUpdate:Name:Sunrise_Has_Arrived State:false Device:45 Thu Aug 18 09:33:53.760 - FireAction:Nothing found for:!Sunrise_Has_Arrived Thu Aug 18 09:33:53.761 - EvalConditions:Multi Trigger:Sunset_has_arrived Thu Aug 18 09:33:53.762 - EvalConditions:Multi Trigger:Sunrise_Has_Arrived Thu Aug 18 09:33:53.764 - EvalConditions:Condition:SunsetArrivedNoLightsOn Trigger:Sunset_has_arrived Result:true Thu Aug 18 09:33:53.765 - TriggerCondition:SunsetArrivedNoLightsOn Thu Aug 18 09:33:53.778 - EvalConditions:Condition:SunsetArrivedNoInsideLightsOn Trigger:Sunset_has_arrived Result:true Thu Aug 18 09:33:53.780 - TriggerCondition:SunsetArrivedNoInsideLightsOn Thu Aug 18 09:33:53.789 - EvalConditions:Condition:SunriseArrived Trigger:Sunset_has_arrived Result:false Thu Aug 18 09:33:53.790 - FireAction:Nothing found for:!SunriseArrived Thu Aug 18 09:33:53.792 - SaveDB:{{name = 'Sunset_has_arrived', state = true, seq = 1471530833.7566, oseq = 1471530676.1154},{name = 'SunsetArrivedNoLightsOn', state = true, seq = 1471530833.7645, oseq = 1471530676.1399},{name = 'SunsetArrivedNoInsideLightsOn', state = true, seq = 1471530833.7792, oseq = 1471530676.1425},{name = 'SunriseArrived', state = false, seq = 1471530676.1454, oseq = 1471530833.79},{name = 'Sunrise_Has_Arrived', state = false, seq = 1471530676.1256, oseq = 1471530833.76},{name = 'Front_Porch_Light_Level_Status', state = '0', seq = 1471530776.1334, oseq = 1471530667.1566},} Thu Aug 18 09:33:53.804 - SaveDB:Memory:356772 Thu Aug 18 09:33:53.807 - RunNext:Action:SunsetArrivedNoLightsOn Index:1 Thu Aug 18 09:33:53.821 - SaveActionDB:{} Entry:NOW Thu Aug 18 09:35:17.714 - WatchTriggerProperties:Sunset_has_arrived: urn:rts-services-com:serviceId:DayTimeStatus45 Thu Aug 18 09:35:17.716 - WatchProperties:Front_Porch_Light_Level_Status: 13:urn:upnp-org:serviceId:Dimming1:LoadLevelStatus Thu Aug 18 09:35:17.720 - EvalConditions:Condition:SunsetArrivedNoLightsOn Trigger:nil Result:true Thu Aug 18 09:35:17.721 - EvalConditions:Condition:SunsetArrivedNoInsideLightsOn Trigger:nil Result:true Thu Aug 18 09:35:17.723 - EvalConditions:Condition:SunriseArrived Trigger:nil Result:false Thu Aug 18 09:35:17.724 - TriggerCondition:None Thu Aug 18 09:35:17.730 - SweepDB:NOW Thu Aug 18 09:35:17.740 - SaveDB:Memory:332909 Thu Aug 18 09:35:17.754 - CheckRegistration:Subsequent:396 Thu Aug 18 09:35:19.536 - CheckRegistration:First:9919035174 Thu Aug 18 09:35:19.575 - RegisterMessage:Installed: 1452975656 You have 1 license, which allows a total of 4 PLEG and/or PLTS plugins. Thu Aug 18 09:35:19.576 - Registration:Registered: true $1$1vKuEXMI$k89CwSAitJt50AeMYYSMBo Thu Aug 18 09:35:19.577 - Registration:PLC[4]: 47 PLEG#: 4 PLTS#: 0 Thu Aug 18 09:35:27.103 - DelayedEval:Status :0=0 Thu Aug 18 09:35:27.104 - DelayedEval:Status :0=1 Thu Aug 18 09:35:27.105 - WatchProperties:Old: 0 New: 30 Thu Aug 18 09:35:27.106 - DelayedEval:Fire: Front_Porch_Light_Level_Status Property: LoadLevelStatus Thu Aug 18 09:35:27.107 - EvalConditions:Condition:SunsetArrivedNoLightsOn Trigger:Front_Porch_Light_Level_Status Result:true Thu Aug 18 09:35:27.139 - EvalConditions:Condition:SunsetArrivedNoInsideLightsOn Trigger:Front_Porch_Light_Level_Status Result:true Thu Aug 18 09:35:27.141 - EvalConditions:Condition:SunriseArrived Trigger:Front_Porch_Light_Level_Status Result:false Thu Aug 18 09:35:27.143 - SaveDB:{{name = 'Sunset_has_arrived', state = true, seq = 1471530833.7566, oseq = 1471530676.1154},{name = 'SunsetArrivedNoLightsOn', state = true, seq = 1471530833.7645, oseq = 1471530676.1399},{name = 'SunsetArrivedNoInsideLightsOn', state = true, seq = 1471530833.7792, oseq = 1471530676.1425},{name = 'SunriseArrived', state = false, seq = 1471530676.1454, oseq = 1471530833.79},{name = 'Sunrise_Has_Arrived', state = false, seq = 1471530676.1256, oseq = 1471530833.76},{name = 'Front_Porch_Light_Level_Status', state = '30', seq = 1471530927.1054, oseq = 1471530776.1334},} Thu Aug 18 09:35:27.235 - SaveDB:Memory:357184

Thanks!

#4

Any ideas? I discovered that Lua restarts everytime a pleg event fires. This is why only the first item works.

To be clearer:

Trigger happens → pleg conditions met so start actions → start 1 action → Lua restarts.

#5

I realize this is an old thread but I am having a similar problem so I thought I’d ask in case someone can help me resolve this issue…

I just upgraded to VeraPlus on UI7. I’ve unpaired and deleted the switches from my old setup and paired and added them to the new VeraPlus.

In the process of rebuilding my PLEG setup from scratch I’ve come across a problem with an action that is supposed to turn on 3 separate dimmer switches to a specific “loadleveltarget” value (100%).

It seems that it is only turning on the first device in the list and when it does it turns it on to it’s last “loadleveltarget” value.

Any idea what’s happening here? Let me know if you need to see a log or something to help me troubleshoot.

Thanks!

#6

Post a PDF of the status report…

#7

Post a PDF of the status report…[/quote]

Here you go… Action in question is c_fr_mot_on (and accompanying actions c_fr_mot_keep and c_fr_mot_off)

When c_fr_mot_on is true, it should turn on 3 Family Room lights (Main, Wall and Fire) to 100%. Instead it turns on just Main or sometimes Main and Wall but never all 3. Also sometimes turns on to last level and not 100%.

-uberpixel

#8

c_fr_lt_all_off also fails to consistently turn off all of the Family Room Lights like it’s supposed to.

-uberpixel

#9

[quote=“uberpixel, post:8, topic:193397”]c_fr_lt_all_off also fails to consistently turn off all of the Family Room Lights like it’s supposed to.

-uberpixel[/quote]

I don’t really see any problems in the PLEG.

But I have had a lot of problems trying to send multiple z-wave requests simultaneously. To the point I personally consider it a best-practice not to try to send multiple “Immediate” z-wave requests. What can happen is that if the z-wave network is not perfect, the requests get queued - and essentially if you have more than two requests held up, Vera is programmed to assume the z-wave network is deadlocked and Vera restarts. So my recommendation is to see if Vera is restarting when you have this issue with not all of the lights switching off/on as expected. If you are deadlocking, it would cause Vera to restart almost exactly 30 seconds after the action fires…

#10

I think you may be right. I?ll check the logs for a restart when I have a chance.

This morning I made a scene that turns all the lights on simultaneously and had the action run the scene. The results were the same so I think it?s a Zwave network problem. Any way to fix this?

That said, I?m able to turn on all the lights simultaneously via Alexa and that works consistently with no issues. Seems unlikely that Vera would route the Zwave commands differently whether triggered by PLEG, Vera scene or Alexa.

-uberpixel

#11

Well, not route differently on the z-wave network, but I believe they can execute/queue differently. Now I don’t want Richard to get on my case, but I have had situations in the past where a PLEG scene would deadlock while a standard Vera scene with the same actions would complete.

And as far as what you can do on the z-wave side - while UI7 does not have a network heal, it does still have an update neighbors button. So a mini-heal specific to a particular device that you might be having trouble with…

#12

Okay - I take this back. I have not been able to duplicate this behavior and may have jumped to this conclusion as I was in a rush during testing.

I think this is either a PLEG issue with UI7 or the VeraPlus. Or at least there is something up with the way that PLEG and Vera are communicating the actions’ intentions. I had this exact logic setup in UI5 on a Vera3 with these same switches and never had any issues.

I have tried removing and re-adding the 3 lights that I am trying to turn on/off with this PLEG action and have the same results.

Basically, the first light in the list will turn on but the other 2 will not. Sometimes 2 of 3 will come on but never all 3 and usually just the first.

A trial “Vera” Scene successfully turns all lights on simultaneously.

I tried setting up the action to “runscene” as a test with my scene name in the “Scenenameornumber” field but it will not trigger - even if I run directly from the Logic Actions editor page. Not sure if I’m missing something obvious here to make this test work?

Any other thoughts? Would a log file help to troubleshoot?

-uberpixel

#13

I have 3 exterior lights controlled by a virtual switch. If the VS is on or off, I have PLEG set up as a trigger with conditions based on those triggers and an action to turn on/off the 3 switches with a VeraMate alert. I have schedules and such set up but those actions operate the VS. I also did not see anything in your PLEG to warrant the behavior you are seeing but perhaps the VS may make the actual action simpler for Vera.

#14

A few more pieces of information…

All three dimmer switches are in the same plastic outlet box. They are all different brands (Evolve, Linear and GE). Any chance the switches are causing each other interference? I tried moving my Veraplus within 6 feet and still had problems.

Next I tried using a PLEG action to simultaneously fire 3 lights in different outlet boxes including one of the lights in the previously mentioned 3 gang box. They turn on and off without any problems.

-uberpixel

#15

Just a quick update - I have things working properly now. I made 2 changes at the same time so I’m not sure which one fixed it.

I removed the Evolve dimmer from the 3-gang box and replaced it with a new Inovelli dimmer. No real reason why I chose to remove the Evolve other than it was one of the older dimmers that I have.

I also did a full factory reset on the VeraPlus.

After making these 2 changes PLEG is firing my actions as expected.

-uberpixel