So I’m not sure where to start, but my Vera Plus restarts are WAY higher than normal. Like running almost any scene or Reactor activity set will trigger it - and often the actions don’t complete obviously. I ran through the log to see if anything jumped out, and noticed this IP a few times in red… and it’s my Samsung Gear S3 watch - no clue why it would be on Vera, and even more concerned with some user/pass in there… Any ideas?!
The big suspect for me here is WWN. I banished that plugin a long time ago. It really wreaked havoc with my system. I wasn’t happy, because I have Nest thermostats exclusively in my house, but having my Vera tanking all the time was worse. That was my experience. For the record, my system got a lot more stable when I stopped using PLEG, and that’s a big part of the reason I wrote DelayLight, and then Reactor.
Agreed - I’ve moved 95% of my pleg stuff in Reactor. I’ll need to learn more about sitesensor for replacing darksky. I use it to determine cloud cover for gloomy conditions (which turns on more lights, and turns off if sun returns, etc.)
Yeah WWN very well could be causing issues - I use ecobee for thermostat, and this is all for the Next Protects… but I like the idea of having them tied into the automation for turning on lights, disabling hvac in event of alarm, etc.
But I’m seeing small things like using Autovera (via tasker) trigger a single virtual switch, which only does 2 things: Disarm the alarm panel and then unlock deadbolt. Even that tiny activity triggered a restart the other day. That was probably the worst “easy” thing that triggered it. The other large scenes (both native scene or using Reactor to carry actions) is almost 100% restart occurrence. But those scenes (morning and goodnight) run many things, harmony, alarm (only goodnight), ecobee, etc.
Recalling that my own Vera Plus was randomly doing Luup reloads as recently as last month, I can tell you the two (and probably only two) things I did that quited it down:
I (re-)ran the code by @rafale77 which (re-)enabled “Reload on Time Jumps”…
…and I rebooted my Vera using Settings > Network > Reboot. I have a strong suspicion that this second move was the more effective of the two. It had been a mighty long time since doing a restart of that nature.
No random restarts (ok, maybe one) since then! I realize all of this may not help with your particular issue, but it can’t hurt, eh??
We know that Vera generally degrades the larger your Z-Wave network becomes, and ironically, it has been shown that leaving the stacking of (many) multiple jobs in a row will cause her to behave erratically.
May I suggest porting some of those Arm/Disarm toggles over to Reactor (maybe a dozen at a time, until the problem abates), since you can there introduce a [Delay] action between batches.
This advice comes on the heels of a separate discussion in which we all essentially agree that such delays are key to keeping Vera from puking on long chains of actions (i.e. Mode change panel).
