PLEG 5.9 vs 6.5 evaluating differently - 2 states same time? Logs attached

Plugins & Plugin Development Program Logic (PLEG)
1

Richard,
My logic has not changed since my reinstall 2 days ago. On v5.9 everything was working very well, until it got corrupt. My logic has not changed.

I turned on PLEG logging today and looked it over I found several places where PLEG looks like it is evaluating conditions to be true at the same time, when they cannot be.

Fri Apr 04 20:02:46.949 - EvalConditions:Condition:RobynHome Trigger:secAway Result:true
Fri Apr 04 20:02:46.949 - EvalConditions:Condition:RobynAway Trigger:secAway Result:true

… I think it is not impossible. Here’s the Conditions:

AWAY = !Robyn or (!RobynPhone AND (!RobynPhone; NOW > 3:00))
HOME = Robyn or RobynPhone

… this exact logic was working fine in 5.9, it has not changed at all.
… Robyn is a button on a MultiSwitch and RobynPhone is the Ping Sensor device.

logs and Status Report attached.

Also, I’m seeing several times where it looks like the same Condition is triggering twice in a row
thx for the help

2

My analysis follows … you could have done the same.
Look for first time both were true in the log … this was at: 18:43:42
And this was caused by the trigger: RobynPhone becoming true.
But looking at the SaveDB just prior to this (Which holds the state information for all of the Variables …) the occupancy Switch Robyn is false.

So that’s why both conditions are TRUE

3

I figured out the OR with RobynAway was be causing the problem - rare timing issue.

I’m still have in major issues with things triggering that should not be - It was worked perfectly in 5.9 for months. Today I pulled the Status Reports from v5.9 back on 3/11 and made sure it was the same…it is.

I need help finding out why things are triggering when no one is home and no Inputs should be changing at all! AND I’m seeing looping occurring with Security and Occupancy… again, no one is home, no inputs should be changing at all.

Logs attached shooing looping when no one was home - no inputs should have been changing.

4

Richard,
I have tried adjusting my logic, moving things around a bit, but I’m still getting triggers firing when I think they should not be.
My logic was the same in 5.9 and over the past 2 days I’ve been trying to adjust to see if it was timing issues or something but having no luck.

I attached a log (PLEG-226) showing issues…

[ul][li]Away triggers (as expected), quickly followed by Stay triggering (which should not)[/li]
[li]StaySecure triggers (as expected), quickly followed by Stay triggering (which should not)[/li][/ul]

Also, in a separate case (PLEG-227) I have a Condition that is simple yet not working…
Guest or Aaron or Robyn
… Repeat is checked but still, changing any Input (Aaron, Robyn) the Action is not triggering?

Please take a quick look, I’m sure you’ll see something I’m missing.

thanks!

5

I need status reports to go with the logs.

6

Richard,
This morning I woke up to Looping of triggers and had to pull the power on the Vera.

About 30% of the time I open any of my 3 PLEG devices and choose Status/Report, I get multiple errors… “Error Getting status of: Vacation”

reports & new logs attached in ZIP

7

If you are working from multiple computers you must always REFRESH your browser (F5) when you start accessing Vera.

The only thing that Vera updates reliably to it’s web client is the status needed to update the dashboard.
Everything else can be out of date …
That’s why there is the Vera Two Step when you think there is a problem:

  1. Restart Vera (So that it starts from a clean state)
  2. Refresh your Browser (F5) so that it caches the latest info.
    Now the two should be in sync … at least for a while.
8

[quote=“RichardTSchaefer, post:7, topic:180572”]If you are working from multiple computers you must always REFRESH your browser (F5) when you start accessing Vera.

The only thing that Vera updates reliably to it’s web client is the status needed to update the dashboard.
Everything else can be out of date …
That’s why there is the Vera Two Step when you think there is a problem:

  1. Restart Vera (So that it starts from a clean state)
  2. Refresh your Browser (F5) so that it caches the latest info.
    Now the two should be in sync … at least for a while.[/quote]

Still happens… I just has the LUA errors occur. So I did a Reload & F5… LUA errors still. SO, I unplugged and restarted Vera… no more LUA errors BUT I still get multiple errors like… “Error Getting status of: Vacation”

PLEG and Vera logs attached

9

If you are failing and it takes a REBOOT to clear the problem … it sounds like you are running out of memory because your logs are going into memory.

Do you have a USB stick enable for logging ? Do you use it ALL the time ?

The

Error Getting status of: Vacation

Do you have a condition called Vacation ?
Do you have a Notification for when a condition called Vacation is satisfied ?

10
Away triggers (as expected), quickly followed by Stay triggering (which should not) StaySecure triggers (as expected), quickly followed by Stay triggering (which should not)

These appear to be because AwayON is true at the same time as StayON, StayON turns false shortly after.
But it’s hard to follow because you are running scenes and I do not know the details of coupling of parameters you have.
PLEG does not appear to be doing anything wrong.

You would be better off using a STATE variable in PLEG if these are mutually exclusive states.

11

[quote=“RichardTSchaefer, post:10, topic:180572”]

Away triggers (as expected), quickly followed by Stay triggering (which should not)
StaySecure triggers (as expected), quickly followed by Stay triggering (which should not)

These appear to be because AwayON is true at the same time as StayON, StayON turns false shortly after.
But it’s hard to follow because you are running scenes and I do not know the details of coupling of parameters you have.
PLEG does not appear to be doing anything wrong.

You would be better off using a STATE variable in PLEG if these are mutually exclusive states.[/quote]

I’m trying to keep it simple by using MultiSwitch as the State tracking method. I think Rex’s beta code (calls ‘break’ first) fixed the issues… keeping fingers crossed.

If there was an easy way to “tie” a PLEG State variable to MultiSwitch, would that help this?
… Maybe something you can look at whit your plugin consolidation project?