I found a logic error in my PLEG. Might have been causing an extra evaluation cycle. Let’s see if fixing it resolves the issue…
Apparently just got lucky during that 72 hour stretch. Have had 4+ restarts today when a PLEG was in the middle of taking action. All of these restarts have been the same lighting PLEG.
Am very upset I can get this stable. Should I be breaking down my big PLEGs into smaller PLEGs? Geez absolutely frustrating the lack of real information on why the restarts are happening. Playing the log now, but useless as far as I can tell…
[quote=“wilme2, post:42, topic:183969”]snip
All of these restarts have been the same lighting PLEG.
Should I be breaking down my big PLEGs into smaller PLEGs? [/quote]
So you have isolated the restarts to one PLEG.
There must be something that is different about this one to the other(s), perhaps the amount of triggers, conditions or actions. Only you know this.
I think you have answered your own question and should start breaking down the PLEG until it ceases to cause restarts.
Possibly you have reached the physical limit of one PLEG, only experimenting from here, will solve this interesting problem you have.
I saw some bad zwave messages in the log, and realized that same closet light is marked as ‘all routes failed’. Trying a heal and setting back to Vera Routing…
Maybe spread your actions to a few delayed actions.
Is there a limit on conditions/schedules/whatever on a single PLEG instance?
Do the PLEGS share any of the items, globally unique, share schedules/variables, etc.?
NO (Assuming Vera has no limit) and NO.
Apparently Z-wave issues were the cause of the restarts. I don’t know why the z-wave network became unstable after a few days, but moving back to Vera Routing and the associated nightly heals has re-stabilized the z-wave network. My Vera3 has been stable for the last 72 hours - the only restarts are the nightly heals, and the lighting PLEG is working as designed…