Richard,
I’ve been dealing with this for a few days now. I did not make any changes to my 2 PLEG devices governing my Security system. They were working perfectly and since the auto-update to 5.9 they are failing to run some Actions.
This is causing my alarm to go off, siren to sound, etc… when before the Alarm would properly be disabled.
How can I back-rev to 5.8?
I’m happy to try to troubleshoot the problem but I don’t know of any way to Debug PLEG - is there a debug logging we can enable?
I can post it but I cannot see how it will help. Worked perfectly in 5.7 and now most of the actions do not work after 5.8
You already know the plegs I have are complex. We need a way to debug these, without it we cannot do anything complex and be assured of ability to fix things when updates break them.
When I click on Status/Report button I get tons of errors on both PLEGs. One for almost every Condition - see attached image.
Now it makes sense why most of the Actions are not triggering. I have rebooted (unplugged) 3 times over the past 2 days to see if it will work. This is the first time I looked to get Status/Report.
Let me repeat… not a single thing has changed in the PLEG device since 5.7
Since many of these are not working properly, lets start with the easiest one…
Occupancy Tracking
dAaronHome & dAaronAway is on/off for a Virtual Device.
pAaronHome is a Ping Status device
Condition… setAaronHome : dAaronHome or pAaronHome
Action… setAaronHome : House Status SetVariable2 newVariable2=Home
As you can see by the attached Status Report, the Condition evaluates to True, but the Action is never completed - thus ‘Home’ is never put into the Variable.
The same problem with the Robyn ‘Home’ Conditions. BUT, the ‘Away’ Conditions work fine for Robyn & Aaron.
The latest report you sent does not work.
But I looked at the previous report …
And the Status report shows that the properties Variables2 was set to Home at 6:10 PM and set to something else at 4:48 PM witch corresponds to you leaving.
Do you have something that Arms/disarms this PLEG ?
I do see that Robyn’s status in Variable3 was set at 9:45 AM
But the conditions that should have changed it fired at: 11:09 AM and 5:43 PM
So it looks like the PLEG was bypassed until just after she arrived but before you arrived.
I suggest you set the Debug Level to 2 (See the LOG command). Close the window that log file that is displayed … Save the config.
Then record what is happening for a day. Email me the results.
Update:
Yesterday I decided maybe the 5.9 autoupdate did not work 100%… so I manually ran the updates. That seemed to help though I have a few unresolved issues.
testing today…
Working:
detecting Ping Sensor and setting to user to Home
Not Working:
manually setting Virtual Devices change from ON (home) to OFF (away) - Condition/Action should change Variable Container from Home to Away, it is not.
Status report shows Condtion evaluating correctly… but Action does not seem to be occuring.
Attached PLEG LOG and Status Report (html format)
Please check the files before you post them.
The last two status reports did not work. The first one did.
It may seem redundant … by I can’t zero in on the problem without detailed information.
I need a status report that goes along with the log file that leads up to the problem.
As well as an indication of which condition(s) you suspect is not working.
Once again the Status report did not work. So it’s not the upload. It the way you are capturing the Status report. Please try to open the file that you save and make sure there is Correct data in it. It looks like the empty shell of the UI5 control panel.
Here is the list of events that Vera has called me (So I see the triggers, and the side effects of the actions, since you have device properties for Variable Container)
TriggerPoipertyUpdate (Vera calling me to tell me something about a trigger has changed)
PropertyUpdate (Vera calling me to tell me something about a device property has changed)
TriggerConditon: Where I call some action. (This is a subset of the log you sent me, less important stuff removed, and many of the false triggers that did not cause any PLEG logic to fire)
Fri Feb 14 12:41:46.884 - TriggerPropertyUpdate:Name:pAaronHome State:true Device:186
Fri Feb 14 12:41:46.884 - TriggerPropertyUpdate:Name:pAaronAway State:false Device:186
Fri Feb 14 12:55:47.703 - TriggerPropertyUpdate:Name:pAaronHome State:false Device:186
Fri Feb 14 12:55:47.703 - TriggerPropertyUpdate:Name:pAaronAway State:true Device:186
Fri Feb 14 12:56:47.781 - TriggerPropertyUpdate:Name:dAaronHome State:false Device:140
Fri Feb 14 12:56:47.781 - TriggerPropertyUpdate:Name:dAaronAway State:true Device:140
Fri Feb 14 12:56:47.781 - TriggerCondition:setAaronAway
Fri Feb 14 12:56:47.783 - PropertyUpdate:vAaron: from:Home to:Away
Fri Feb 14 12:56:47.783 - TriggerCondition:setNotOccupied
Fri Feb 14 12:56:47.785 - PropertyUpdate:vOccupied: from:Yes to:No
Fri Feb 14 12:56:47.787 - PropertyUpdate:vSecurity: from:Stay to:Away
Fri Feb 14 12:58:47.886 - TriggerPropertyUpdate:Name:pAaronHome State:false Device:186
Fri Feb 14 12:58:47.886 - TriggerPropertyUpdate:Name:pAaronAway State:true Device:186
Fri Feb 14 13:02:48.176 - TriggerCondition:setAaronAway
Fri Feb 14 13:02:48.178 - PropertyUpdate:vAaron: from:Home to:Away
Fri Feb 14 13:02:48.178 - TriggerCondition:setNotOccupied
Fri Feb 14 13:02:48.178 - TriggerPropertyUpdate:Name:dAaronHome State:false Device:140
Fri Feb 14 13:02:48.178 - TriggerPropertyUpdate:Name:dAaronAway State:true Device:140
Fri Feb 14 13:03:48.180 - PropertyUpdate:vOccupied: from:Yes to:No
Fri Feb 14 13:03:48.182 - PropertyUpdate:vSecurity: from:Stay to:Away
Fri Feb 14 13:04:48.297 - TriggerPropertyUpdate:Name:pAaronHome State:false Device:186
Fri Feb 14 13:04:48.297 - TriggerPropertyUpdate:Name:pAaronAway State:true Device:186
Fri Feb 14 13:09:48.589 - TriggerCondition:setAaronAway
Fri Feb 14 13:09:48.591 - PropertyUpdate:vAaron: from:Home to:Away
Fri Feb 14 13:09:48.591 - TriggerCondition:setNotOccupied
Fri Feb 14 13:09:48.591 - TriggerPropertyUpdate:Name:dAaronHome State:false Device:140
Fri Feb 14 13:09:48.591 - TriggerPropertyUpdate:Name:dAaronAway State:true Device:140
Fri Feb 14 13:09:48.593 - PropertyUpdate:vOccupied: from:Yes to:No
Fri Feb 14 13:09:48.594 - PropertyUpdate:vSecurity: from:Stay to:Away
Fri Feb 14 13:42:50.563 - TriggerPropertyUpdate:Name:dRobynHome State:true Device:178
Fri Feb 14 13:42:50.563 - TriggerPropertyUpdate:Name:dRobynAway State:false Device:178
Fri Feb 14 13:42:50.563 - TriggerCondition:setRobynHome
Fri Feb 14 13:42:50.565 - PropertyUpdate:vRobyn: from:Away to:Home
Fri Feb 14 13:42:50.565 - TriggerCondition:setOccupied
Fri Feb 14 13:42:50.567 - PropertyUpdate:vSecurity: from:Away to:Stay
Fri Feb 14 13:42:50.570 - PropertyUpdate:vOccupied: from:No to:Yes
Fri Feb 14 13:44:50.687 - TriggerPropertyUpdate:Name:dRobynHome State:false Device:178
Fri Feb 14 13:44:50.687 - TriggerPropertyUpdate:Name:dRobynAway State:true Device:178
Fri Feb 14 14:05:51.902 - TriggerPropertyUpdate:Name:dAaronHome State:true Device:140
Fri Feb 14 14:05:51.902 - TriggerPropertyUpdate:Name:dAaronAway State:false Device:140
Fri Feb 14 14:05:51.903 - TriggerCondition:setAaronHome
Fri Feb 14 14:05:51.905 - PropertyUpdate:vAaron: from:Away to:Home
Fri Feb 14 14:05:51.917 - TriggerPropertyUpdate:Name:pAaronHome State:true Device:186
Fri Feb 14 14:05:51.917 - TriggerPropertyUpdate:Name:pAaronAway State:false Device:186
Fri Feb 14 14:14:52.492 - TriggerPropertyUpdate:Name:dRobynHome State:true Device:178
Fri Feb 14 14:14:52.492 - TriggerPropertyUpdate:Name:dRobynAway State:false Device:178
Fri Feb 14 14:14:52.492 - TriggerCondition:setRobynHome
Fri Feb 14 14:15:52.500 - TriggerPropertyUpdate:Name:dRobynHome State:false Device:178
Fri Feb 14 14:15:52.500 - TriggerPropertyUpdate:Name:dRobynAway State:true Device:178
Fri Feb 14 14:51:54.686 - TriggerPropertyUpdate:Name:pAaronHome State:false Device:186
Fri Feb 14 14:51:54.686 - TriggerPropertyUpdate:Name:pAaronAway State:true Device:186
Fri Feb 14 15:07:55.637 - TriggerPropertyUpdate:Name:pAaronHome State:true Device:186
Fri Feb 14 15:07:55.637 - TriggerPropertyUpdate:Name:pAaronAway State:false Device:186
Fri Feb 14 16:04:59.041 - PropertyUpdate:vRobyn: from:Home to:Away
Fri Feb 14 16:23:0.208 - TriggerPropertyUpdate:Name:dRobynHome State:true Device:178
Fri Feb 14 16:23:0.208 - TriggerPropertyUpdate:Name:dRobynAway State:false Device:178
Fri Feb 14 16:23:0.208 - TriggerCondition:setRobynHome
Fri Feb 14 16:23:0.211 - PropertyUpdate:vRobyn: from:Away to:Home
Fri Feb 14 16:23:0.214 - TriggerPropertyUpdate:Name:dRobynHome State:false Device:178
Fri Feb 14 16:23:0.214 - TriggerPropertyUpdate:Name:dRobynAway State:true Device:178
Fri Feb 14 16:24:0.299 - TriggerPropertyUpdate:Name:dRobynHome State:true Device:178
Fri Feb 14 16:24:0.299 - TriggerPropertyUpdate:Name:dRobynAway State:false Device:178
Fri Feb 14 16:24:0.299 - TriggerCondition:setRobynHome
Fri Feb 14 16:25:0.306 - TriggerPropertyUpdate:Name:dRobynHome State:false Device:178
Fri Feb 14 16:25:0.306 - TriggerPropertyUpdate:Name:dRobynAway State:true Device:178
I do see Robyn coming and going as reflected by Vera calling this PLEG and indicating the changes to the Variable Container variables.
That’s because setRobynAway remained true (because of pAaronAway) even when you toggled dAaronHome.
The actions only fire when conditions go from False to True.
A bug prior to 5.7 allowed these to fire in some cases.
You may have been dependent on the bug;
Looks like Robyn left around 10:02
Condition setRobynAway went true 4 minutes later at 10:06 and remained true until the time of the report (10:27)
You toggled dRobynHome/Away around 10:27
setRobynHome toggled with it at 10:27
Wow, that is likely it… the bug did what I wanted it to do!
The idea:
Ping Sensor (pRobynAway) is the ‘autodetect’ method
Virtual Device (dRobynAway) is the “manual override”
Do I need to keep them in separate Conditions? Or an easier/better way?
… this actually brings up an interesting feature I was thinking about requesting. Ability to link multiple Conditions to the same Action. Or at least copy a set of actions to another action… since creating actions is pretty tedious, especially when triggering scenes.
If you always want a condition to call actions when it is evaluated to true … even if it is already true … rename the condition from XXXX to _XXXX
The underscore as the first character of the Condition name changes the behavior for the condition.
[quote=“RichardTSchaefer, post:18, topic:179512”]If you always want a condition to call actions when it is evaluated to true … even if it is already true … rename the condition from XXXX to _XXXX
The underscore as the first character of the Condition name changes the behavior for the condition.[/quote]
does it only evaluate the condition IF one of the variables in the condition changes - or?
Does it only evaluate the condition IF one of the variables in the condition changes - or?
Close … It only looks at the result of an evaluation if one of the input variables in the condition changes … or if it references another condition, then it’s value had changed by legitimate change’s of it’s inputs. The latter I refer to as cascading conditions.
So logically there is a dependency graph (of relationships) between inputs and conditions … if an input does not participate in the dependency graph … it is ignored for that condition.