PLEG Weirdness

Plugins & Plugin Development Program Logic (PLEG)
1

I’m using a PLEG v5.0 for repeat notifications. The conditions are interdependent, meaning that condition 2 requires condition 1 to be true in order for condition 2 to also be true. This had been working, and then I changed the interval. Now I am getting condition 2 == true seemingly without condition 1 == true and, as a result, I’m only getting the first notification and none subsequent.

Note the last true times at right. How is it possible for condition 2 to be true without condition 1?
[table]
[tr]
[td]DoorLeftOpen BigDoorOpen AND (BigDoorOpen; NOW > 10:00) And Armed == 1[/td][td]2013-09-03 15:35:35.103[/td]
[/tr]
[tr]
[td]LeftOpenRepeat DoorLeftOpen AND ((LeftOpenRepeat; BigDoorOpen) OR (LeftOpenRepeat; NOW > 10:00))[/td][td]2013-09-03 16:50:35.123[/td]
[/tr]
[/table]

Notification was sent at 15:35 and no subsequent repeats.

Edit: I also just realized that the Last True times listed on the status page are an hour ahead of both the local Vera time and the time displayed in the Last Trigger field. Looking at wrong PLEG.

2

Please send the WHOLE Status report … not a clipped down version.
Add your comments about what you do not understand.

3

Attached are two status reports for a repeating door open reminder PLEG. The PLEG is supposed to notify me every 10 minutes if the door is left open.

StatusOpen.pdf shows the report after the door has been opened for one and a half hours. There was only one notification sent(the first 10 minutes) when there should have been 8. Notice also that the times are all off and not properly updated.

StatusClosed.pdf shows the status report for the same PLEG only seconds later, but the door has now been closed. Notice the times have been updated. But, notice that the Last True times for the two conditions are different. My interpretation is that the time for condition 2 should never be more recent than condition 1. But, the status report shows different.

I had not paid close attention to this PLEG before as it seemed to be working. It would nag me incessantly so I changed the open period from 5 minutes to 10. Now it will only send the first notification and the status times don’t look right.

I have reloaded Vera without it making a difference.

4

A NOW trigger will not cause the Database to be saved … so the status will not show.
(This minimizes log file entries … because it fires every minute … and saving a parameter always writes to the log file … this is important for those that do not have USB memory stick to capture the Vera Log).

If you want to see the status of conditions that are tripped by NOW create a dummy trigger … then trip it … then do your status report. I have not looked at the reports yet.

5

[quote=“RichardTSchaefer, post:4, topic:176761”]A NOW trigger will not cause the Database to be saved … so the status will not show.
(This minimizes log file entries … because it fires every minute … and saving a parameter always writes to the log file … this is important for those that do not have USB memory stick to capture the Vera Log).

If you want to see the status of conditions that are tripped by NOW create a dummy trigger … then trip it … then do your status report. I have not looked at the reports yet.[/quote]

Ok! Combine that with the fact that I was incorrectly notifying on the first condition, rather than the second, it suddenly all makes sense. I’m working again.

Thanks Richard.