Actions not triggering

Plugins & Plugin Development Program Logic (PLEG)
1

Please forgive any oversights, I’m new to both Vera and PLEG. I have a Vera Plus, and just installed PLEG this morning and have been doing some testing. For some reason my actions never seem to fire.

I’ve removed all but some very basic stuff:
Triggers:
I have two, Scene controller button presses. These are actually Lutron Pico’s using the Caseta plugin

tCorollaPico_1 Corolla Pico: scene number 1 is activated
tOutbackPico_1 Outback Pico: scene number 1 is activated

Conditions:
cPicoTest tCorollaPico_1

I.e. when the first button is pressed

Actions:
cPicoTest Immediate - 1

The action is to a device, with SetLoadLevelTarget = 100

The weird thing is that the logs show PLEG seeing the button being hit, and evaluating the condition to be true, but the action doesn’t occur. If I click the “Do It Now” button in the actions interface the action does run. So it seems PLEG sees the input, can do the action manually, evaluates the condition properly, but just doesn’t when it is all automatic. Oh yeah, and I’ve checked that PLEG is armed. :slight_smile:

Here is from setting the debug logs to their own file:

Wed Mar 09 11:44:23.570 - SaveDB:Memory:322069 Wed Mar 09 11:44:24.173 - CheckRegistration:First:1457545464 Wed Mar 09 11:44:24.214 - RegisterMessage:Installed: 1457539015 90 Day Evaluation Period which allows a total of 4 PLEG and/or PLTS plugins. Wed Mar 09 11:44:24.215 - Registration:Registered: true $0$12345678$9 Wed Mar 09 11:44:24.216 - Registration:PLC[4]: 122 PLEG#: 1 PLTS#: 0 Wed Mar 09 11:44:33.101 - DelayedEval:sl_SceneActivated :1=1 Wed Mar 09 11:44:33.101 - DelayedEval:sl_SceneActivated :1=1 Wed Mar 09 11:44:33.102 - WatchProperties:Old: 60 New: 60 Wed Mar 09 11:44:33.102 - WatchProperties:Old: 100 New: 100 Wed Mar 09 11:44:33.103 - WatchProperties:Old: 100 New: 100 Wed Mar 09 11:49:26.245 - TriggerPropertyUpdate:sl_SceneActivated Wed Mar 09 11:49:26.246 - TPU:sl_SceneActivated :1=1 Wed Mar 09 11:49:26.246 - TriggerPropertyUpdate:Name:tCorollaPico_1 State:true Device:93 Wed Mar 09 11:49:26.247 - EvalConditions:Multi Trigger:tCorollaPico_1 Wed Mar 09 11:49:26.248 - EvalConditions:Condition:cPicoTest Trigger:tCorollaPico_1 Result:true Wed Mar 09 11:49:26.249 - SaveDB:{{name = 'tCorollaPico_1', state = true, seq = 1457545766.2467, oseq = 0},{name = 'tOutbackPico_1', state = true, seq = 1457540523.0492, oseq = 0},{name = 'pDiningRoomLightLevel', state = '60', seq = 1457542215.7426, oseq = 1457542210.6994},{name = 'pMusicCabinetLevel', state = '100', seq = 1457541711.6589, oseq = 1457540523.6425},{name = 'pPianoLevel', state = '100', seq = 1457541711.6735, oseq = 1457540523.6567},{name = 'cPicoTest', state = true, seq = 1457543664.6135, oseq = 0},} Wed Mar 09 11:49:26.254 - SaveDB:Memory:346615 Wed Mar 09 11:50:1.707 - RunNext:Condition:cPicoTest Index:1 Wed Mar 09 11:50:1.708 - SaveActionDB:{}

So when I hit the button on the remote this line appears: Wed Mar 09 11:44:33.101 - DelayedEval:sl_SceneActivated :1=1
And goes through: Wed Mar 09 11:49:26.254 - SaveDB:Memory:346615

Then when I hit “Do It Now” in PLEG I get the last two lines.

Am I just missing something simple? I’ve restarted LUUP/LuaUPnP multiple times and the same results.

2

I think I figured it out on my own, because it was simple. :slight_smile:

I used the same button to trigger some Vera scenes. I had turned off the scenes, but I missed one. I guess that caused a conflict, which I’m pretty sure I read about on here, which is why I tried disabling them in the first place. I’ve deleted them all now just to be sure.

3

Make sure you POST a PDF of the STATUS report from the Control tab.

There are two reasons the Actions might not fire:

  1. You have the PLEG in BYPASS mode.
  2. Your condition is ALREADY true, and you have not marked the condition with “REPEATS” enabled.
4

[quote=“RichardTSchaefer, post:3, topic:191511”]Make sure you POST a PDF of the STATUS report from the Control tab.

There are two reasons the Actions might not fire:

  1. You have the PLEG in BYPASS mode.
  2. Your condition is ALREADY true, and you have not marked the condition with “REPEATS” enabled.[/quote]

I wish I had read this a couple hours ago. It has been a very frustrating day… :slight_smile:

So since these are scene controllers I need to set them to repeat. I just confirmed that in testing. Also I’ve noticed that when restarting LUUP it acts like the button was hit again, I guess because it is checking the status of everything when it starts up and triggering what matches based on the last button hit. So I guess I’ll have to put in some code to check if the button was hit in the last few seconds to keep that from happening.

I think I’m starting to get the logic. I have until Monday off now due to weather so I’ll have some time to play and figure out the logic.

5

So I got this working with the time math so that I could have repeat turned on and not get weirdness. The weirdness was two fold, first after a restart things would retrigger, which in a lot of cases would probably be fine but for this it was not. Secondly setting the home to away caused the house to get set to home, which caused the house to get set to away… you get the point.

I’ve included the status report. One question remains, is there a better way to do the time logic:

((tCorollaPico_5 and #Now - #tCorollaPico_5 < 3) or (tOutbackPico_5 and #Now - #tOutbackPico_5 < 3) or (tCarportPico_8 and #Now - #tCarportPico_8 < 3)) and pMode == 1

That certainly works, but if there is a more streamlined or efficient way to do it I’m all for it. Took me a few tries to get all the typos out, and it is a little complicated to read. :slight_smile: