Moode hangs(?) after ~24h

[taynaron]

I've set up moode to enable the backup hotspot; and it does seem to turn on when it loses wifi. How does moode detect that? Maybe I can piggyback some restart of the network stack off that?

[Tim Curtis]

I've set up moode to enable the backup hotspot; and it does seem to turn on when it loses wifi. How does moode detect that? Maybe I can piggyback some restart of the network stack off that?

The Hotspot is auto-activated during moode startup if no ip address has been assigned to wlan0 interface.

[jwpope]

By default

- Before a DHCP lease expires, the client sends a request to the DHCP server to renew the lease
- If DHCP server is not available the client keeps trying until the lease expires and then it either keeps the IP address or it reverts to requesting a new IP address.  It does this until the DHCP server comes back online and can service the request.

Typically the DHCP server is a service running on a residential Router and so no DHCP prolly means the Router has crashed or was turned off.

I'm beginning my hunt on this same issue of WiFi going dead on a day timescale since updating to 9.3.0 w/RPi 3B+ and Zero 2W. On the 3B+ I took your hint to plug in the Ethernet vs. power cycling as I have been doing to regain WiFi and bang - myplayer.local reappears on the eth0 and more surprisingly wlan0 livens up again. I had already set the WiFi to STATIC, so that should eliminate DHCP. Will continue the hunt and pay closer attention to moode.log as it gets wiped on restart. My current change is to use an SSID that is on just ONE of my two access points to remove roaming between AP in my house. I also changed to a 5GHz only SSID vs. 2.4/5GHz SSID that might be band steering related, which should work with the 3B+ but clearly won't work on a Zero 2W which is 2GHz WiFi only. WiFi is a pair of HPE InstantON AP22. DHCP is from pfsense.

This may predate 9.3.0, but I'm doing a daily reboot on my Zero 2W as a work around now. I have a watchdog running every 15 minutes and do see where "ping 1.1.1.1" fails which I could use as a reboot trigger.