PLEG 6.0/PLC 6.2 causing deadlock, according to MCV support

Plugins & Plugin Development Program Logic (PLEG)
1

I reported a rather consistent restart problem I’ve been having to MCV support. They just go back to me with a conclusion after reviewing the logs:

PLEG is the root of the deadlock that causes the reboot which in turn results in a PLEG action I have defined to not complete.

I’ve attached the Status report.

Note that the action that seems to always cause the restart is the “MasterBR_LightOff” action.

2

I think 40 conditions is ‘soft’ limit. You have over a hundred.

Perhaps splitting the logic to multiple PLEG devics or running it on bridged Vera’s for logic that doesn’t need to be instant action (like motion sensors turning on lights).

Sir Richard is the man that can give you the plan.

3

Not going to argue that I haven’t got a lot of conditions. However, this one is the only one dead locking AFICT, so why wouldn’t others do the same…? (For instance it’s opposite: when the light gets turned on)

4

Actually the number of conditions does not bother me … it’s some wasted CPU cycles (evaluating conditions that are not participating in logic) … But CPU cycles are usually not a problem.

What worries me more is the Pushover Notifications. It would be interesting to see if you remove these if the problems disappear.
If you fire up a lot of actions they are queued. HTML request can take a while … which can cause the queue to backup. If the queue backs up to much … Vera Restarts.

You might use Vera Alerts as the front end for the Push Over Notifications. I take care to efficiently use Vera Resources to minimize these types of problems.

5

[quote=“RichardTSchaefer, post:4, topic:180006”]Actually the number of conditions does not bother me … it’s some wasted CPU cycles (evaluating conditions that are not participating in logic) … But CPU cycles are usually not a problem.

What worries me more is the Pushover Notifications. It would be interesting to see if you remove these if the problems disappear.
If you fire up a lot of actions they are queued. HTML request can take a while … which can cause the queue to backup. If the queue backs up to much … Vera Restarts.

You might use Vera Alerts as the front end for the Push Over Notifications. I take care to efficiently use Vera Resources to minimize these types of problems.[/quote]
Interesting.

I’ll try using VeraAlerts.

I added the pushover notification for that action because it was failing to complete, so I wanted to try and debug whether the issue was that the action didn’t fire or if it’s that something in the action caused Vera to restart. I’ve never received the notification and the light is not turned off, so it seems like the problem is that Vera restarts while attempting to execute the first action - turn off the light.