Another thing to monitor is the AP that your AG is connected to. I noticed tonight that it connected to a new AP–one that is across the house and on the second floor–right before the AG went offline. I went into the UniFi controller and locked it to the closest indoor AP until I get the outdoor AP set up. The signal immediately improved from -78 dB to -61 dB.
I should have asked this earlier as well, but what is your Configuration Source set to in Home Assistant? Is it Cloud or Local?
I would try changing it to the other one just to see if that stabilizes your communication with Home Assistant at all
I’ve tried both as part of the troubleshooting steps with no impact to persistent and intermittent dropouts. By default, I’ll always choose local over cloud.
Note all AG devices have static IP addresses assigned in addition to AP binding (bonded to closest AP). Both have rock solid sub -55dBm levels, so signal strength can be ruled out as an issue!
On another related note, I took a deeper dive into my Asus system logs and discovered 3 concurrent entries aligned to one of my AG devices (i.e. Open Air), that likely points to a Network level issue with how the Asus AI-Mesh system is handling these particular AG units on a high device count network.
I’m approaching this iteratively by adjusting and enabling ‘universal beamforming’ and ‘airtime fairness’. The network management UI is highly configurable (albeit not as advanced as the Unifi system, but for consumer grade equipment, the entire network infrastructure is at prosumer level).
I’ll also share these findings with the AG engineering team to further help you and the AG broader technical team on future native FW releases, as part of your SDLC regression testing phases.
If you have any other insights to help to resolve this, I’m always grateful!
@MallocArray, one other thing… not sure what to make of this, but I’m seeing the HA AirGradient logs showing FW Turned OFF, followed all sensors “became unavailable” 10 minutes later?
In fact, I’m seeing the AG logs displaying a continuous cycle of sensor state changes (e.g. ‘changed to xyz’) occurring throughout on its own.
I changed mine from Cloud configuration source to Local for testing and I don’t even see a Firmware sensor under Diagnostic anymore. I just deleted the old entry and am changing back to Cloud to see if that adds the sensor.
Multiple items being unavailable looks to be related to it losing connection, but not sure why it shows Firmware turning off.
Those logs messages about disconnecting weak signal strength station is very odd, since you show that they have high strength and I see your Roaming Assist is set to lower than -70 but you could also try disabling that feature just to see.