@bpwwer,

This has happened a few times before and happened again tonight.  I quick power off/power on from a lightning strike caused Polisy to reboot.  Everything came back up except for the Ambient Weather node server.  A restart gets it working again, but thought you'd want to know that manual intervention is needed.

I'm attaching the log package.  The Polisy reboot occurs around 17:50.

AmbientWeather_6-27-2022_93008_PM.zip

When the node server starts it queries AmbientWeather for information about your weather station(s).  It appears that your network is not fully initialized and the query fails

Query failed: HTTPSConnectionPool(host='api.ambientweather.net', port=443): 
Max retries exceeded with url: /v1/devices?applicationKey=7651edae3d7b44ee8ab5c3359b0c99469f30bf3d2a1d4f2c995b25d9c01a2cd3&apiKey=7407c4813e0f41f38be31752905a03377c3e1c41b3dd40b69f74fe4086fbebc8 
(Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x8030f0970>: 
Failed to establish a new connection: [Errno 8] Name does not resolve'))

It's failing because it can't resolve the name "api.ambientweather.net" to an IP address.  It does re-try multiple times as you can see by the "Max retries exceeded" part of the message.

There's nothing the node server can do to make name resolution work on your network while it's starting.

You say this has happened a few times before.  You really should consider a UPS for your Polisy and avoid disruptions due to quick power off/power on occurrences.  

Thanks @bpwwer and @slimypizza,

My network is an Apple Extreme setup which is about the be replaced with a Unifi system.  This may improve name resolution.  Bob, thanks for dissecting the log file for the root cause.

A battery backup for Polisy is definitely on the list of To Do's.