meteohub.de

Just had my second instance of Weewx (possibly triggered by also restarting my access point) crashing my MB station connection to the point it wouldn't restart from the GUI (had to SSH in to issue reboot command).

Console just says:

system (13.05.2022 21:01:45): Disconnected from WLAN or Internet, reconnect issued.
system (13.05.2022 21:01:52): Access point operation temporarily enabled.
system (13.05.2022 21:06:24): Disconnected from WLAN or Internet, reconnect issued.
system (13.05.2022 21:06:31): Access point operation temporarily enabled.
system (13.05.2022 21:11:04): Access point operation disabled 171572 secs after boot.
logger (13.05.2022 21:12:23): child process received timeout signal (14).
logger (13.05.2022 21:12:23): disconnect station 0 (Vantage): exit

Any idea what might be going on?

I think MB just didn't like your rebooting of the WLAN access point while in operation. That was going on
If you had shut down your MB until your AP finished rebooting and restarted it then after, the issue would most likely not have occurred.
Weewx is, by the way, depending on the station driver you use, usually sensisitve to losing connectivity, be it WLAN or LAN.
Imo that's a network issue and not an application issue.
The application tried to manage with it (see your log) but somehow failed.
When you reboot your smartphone while having a phone call, you don't blame the phone app for the connection being interrupted and not being reestablished, do you ?

Agreed... but my phone doesn't crash if I reboot the wifi when it's in use... I just drop the call. =/

I remember now I used to see this issue when I used weathercat over 22222 and wifi dropped. MB would lose it's mind and crash after a bit. Seems like a bug to me, but no matter. I've switched to another method for weewx and will let MB do it's thing without the loop protocol.

I get a similar behavior, albeit totally different kit... I've got a GW1000 set up as my station 1, running on a mesh wifi network (the MB and Gw1000 are connected to the same node, although one is on wifi, the other ethernet). Everytime there's a change on the mesh network MB "loses" the GW1000 and won't find it again until the MB is rebooted. That change can literally be anything on the wlan, so no real way to mitigate it, or really track down if it's a specific variable. So it happens every few days.

So I agree, this isn't really a network issue (networks are expected to be dynamic in some ways), the software should be able to handle it. Either that or let me set a reboot schedule for the MB (likely every 24hrs!).