PG3 Not Recovering After Power Failure

[AllDigital]

In the last year we have had 3-4 power outages at my house. Three of them related to city work. After the power comes back on the EISY recovers 100% and functions normally, but the nodes in the PG3 all seem to be stuck. I've got a Ring plug-in and an Elk M1 plug-in configured in the PG3. Last night we had another 3 hour city power outage. I went to test my doorbell and motion integration this afternoon and sure enough it didn't work, nor did my Elk integrations. This is really annoying, since we are often gone and depend on those for security. We never had any issues under the old ISY99i, but with PG3 it never seems to recover correctly. When I launched the PG3 dashboard (after logging into it) the PG3 and plug ins looked fine, but they said they had been up for one week and three days (not possible with a three hour outage). The Elk Controller and the Ring would not populate in my EISY Admin device, but in the dashboard they showed connected. So I did a manual restart of the ring plug-in and it showed up correctly and started functioning. I also did a reset of the Elk plug-in and it reset its uptime, but even 5 minutes later it still did not show up. So I stopped and started the Elk plug-in and then it came online and worked. This is an easy enough fix, but having them go cold on me when I don't know it is a huge issue. Does anyone know how to force PG3 and the plugins/nodes to recover better after an extended power outage?

[MJones02]

I have the exact same issue.  I wonder if it is related to the sequence that the eisy,  ode servers and Internet access comes back up after the power outage.  I know how to identify the node server issues and you can manually restart but I am looking for a way to control from an eisy program.  I do not see any such actions exposed to eisy programs.  Is the restart command available via the pg3 node server api and could a network resource be used to trigger it?

[BobM99]

I had this problem when I changed eisy from wired to Wifi connection. Changing it back to a wired connection fixed the problem

Edited November 23 by BobM99

[AllDigital]

Mine is only running in a wired configuration. But that could indicate it is a timing or sequence issue between the internet restoring and the PG3 restoring. It seems like fixing it with an external network resource like MJones02 suggests could work but also seems like a hack. For an automation platform it seems like there should be more robust recovery or retry built into PG3 or the connections between EISY and PG3.