I have had my airgradient running for a few months now on my wifi network, but yesterday it started failing to connect to the wifi (based on the airgradient dashboard I guess around 0230 on the 30th) and I have no idea why. I didn’t change anything on the wifi and neither did I do anything to the airgradient as far as I’m aware.
It is an airgradient one v9, and it just keeps trying to connect to the wifi now. I can log in to the airgradient when it enters the phase where you have 180 s to connect to it, and I can see that all the network details look fine (it can see the wifi network that it should connect to).
I have been debugging this problem for a few hours already and I have no idea what to do here.
I checked my routers event log and there I found the following related to the airgradient (mac address 84:fc:e6:07:6f:e8), but unfortunately it seems to only save log for a short time, which means that it does not have the part where the airgradient first lost connection.
Tue Apr 30 17:32:51 2024 daemon.notice hostapd: wlan0: STA 84:fc:e6:07:6f:e8 IEEE 802.11: authenticated
Tue Apr 30 17:32:51 2024 daemon.info hostapd: wlan0: STA 84:fc:e6:07:6f:e8 IEEE 802.11: authenticated
Tue Apr 30 17:32:51 2024 daemon.notice hostapd: ssi_signal:-4400
Tue Apr 30 17:32:51 2024 daemon.notice hostapd: wlan0: STA 84:fc:e6:07:6f:e8 IEEE 802.11: associated (aid 3)
Tue Apr 30 17:32:51 2024 daemon.info hostapd: wlan0: STA 84:fc:e6:07:6f:e8 IEEE 802.11: associated (aid 3)
Tue Apr 30 17:32:51 2024 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 84:fc:e6:07:6f:e8 nr_enabled=0 btm_supported=0 cell_capa=0 SignalStrength=-44 SupportedRates=139 150 130 132 12 24 48 96 108 18 36 72 HT_CAP=116E HT_MCS=FF 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 assoc_req=00003A016003A6CA7F1284FCE6076FE86003A6CA7F12406631040300000F466C6578696E65742D322E3447487A01088B9682840C18306030140100000FAC040100000FAC040100000FAC02000432046C1224482D1A6E111CFF00000000000000000000000100000000000000000000DD070050F202000100
Tue Apr 30 17:32:51 2024 daemon.notice hostapd: wlan0: STA 84:fc:e6:07:6f:e8 RADIUS: starting accounting session B3BC46D01E21F39F
Tue Apr 30 17:32:51 2024 daemon.info hostapd: wlan0: STA 84:fc:e6:07:6f:e8 RADIUS: starting accounting session B3BC46D01E21F39F
Tue Apr 30 17:32:51 2024 daemon.notice hostapd: wlan0: STA 84:fc:e6:07:6f:e8 WPA: pairwise key handshake completed (RSN)
Tue Apr 30 17:32:51 2024 daemon.info hostapd: wlan0: STA 84:fc:e6:07:6f:e8 WPA: pairwise key handshake completed (RSN)
Tue Apr 30 17:32:51 2024 daemon.notice hostapd: ssi_signal:-4100
Tue Apr 30 17:32:51 2024 kern.warn kernel: [ 119.607719] [4294949256] mtlkW(_mtlk_core_add_ieee_addr_entry:8360): CID-0000: 84:FC:E6:07:6F:E8 already in widan black list
Tue Apr 30 17:32:52 2024 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 84:fc:e6:07:6f:e8
Tue Apr 30 17:32:52 2024 user.warn drvhlpr[6449]: [0357154316] drvhlprW[_mtlk_irba_packet_processor:522]: APP notifications arrived out of order (current SN: 3, received SN: 1)
Tue Apr 30 17:32:52 2024 user.warn drvhlpr[6449]: [0357154771] drvhlprW[_mtlk_irba_packet_processor:522]: APP notifications arrived out of order (current SN: 1, received SN: 4)
Tue Apr 30 17:32:53 2024 user.notice lan-follow-wan: turning ON IPv6 on LAN
Tue Apr 30 17:32:55 2024 user.notice firewall: Reloading firewall due to ifup of wan6 (eth1)
Tue Apr 30 17:32:55 2024 user.notice ddns-scripts[15297]: myddns_ipv4: PID '15297' started at 2024-04-30 17:32
Tue Apr 30 17:32:55 2024 daemon.info dnsmasq-dhcp[7083]: DHCPDISCOVER(br-lan) 84:fc:e6:07:6f:e8
Tue Apr 30 17:32:55 2024 daemon.info dnsmasq-dhcp[7083]: DHCPOFFER(br-lan) 192.168.0.176 84:fc:e6:07:6f:e8
Tue Apr 30 17:32:55 2024 daemon.warn dnsmasq-dhcp[7083]: Error sending DHCP packet to 192.168.0.176: Operation not permitted
Tue Apr 30 17:32:55 2024 daemon.info dnsmasq[7083]: read /etc/hosts - 4 addresses
Tue Apr 30 17:32:55 2024 daemon.info dnsmasq[7083]: read /tmp/hosts/odhcpd - 0 addresses
Tue Apr 30 17:32:55 2024 daemon.info dnsmasq[7083]: read /tmp/hosts/dhcp.cfg02411c - 2 addresses
Tue Apr 30 17:32:55 2024 daemon.err dnsmasq-dhcp[7083]: failed to read /etc/ethers: No such file or directory
Tue Apr 30 17:32:55 2024 user.warn ddns-scripts[15297]: myddns_ipv4: Service section disabled! - TERMINATE
Tue Apr 30 17:32:55 2024 user.warn ddns-scripts[15297]: myddns_ipv4: PID '15297' exit WITH ERROR '1' at 2024-04-30 17:32
Tue Apr 30 17:32:57 2024 daemon.err hostapd: nl80211: sending/receiving GET_STA_MEASUREMENTS failed: -14 (Bad address)
Tue Apr 30 17:32:57 2024 kern.warn kernel: [ 125.471697] [4294949843] mtlkW(_mtlk_core_get_station_measurements:16026): CID-0000: station 84:FC:E6:07:6F:E8 not found
Tue Apr 30 17:32:57 2024 daemon.err hostapd: nl80211: sending/receiving GET_STA_MEASUREMENTS failed: -14 (Bad address)
Tue Apr 30 17:32:57 2024 kern.warn kernel: [ 125.499875] [4294949845] mtlkW(_mtlk_core_get_station_measurements:16026): CID-0000: station 84:FC:E6:07:6F:E8 not found
Tue Apr 30 17:32:58 2024 daemon.notice hostapd: wlan2: DFS-CAC-COMPLETED success=1 freq=5280 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5290 cf2=0 timeout=60
Notably it says something about the device being added to widan blacklist though I have no idea what that is, and when I search online nothing seems to pop up either. Any suggestions on what I could try?