Lately, my OnePlus 6T phone running Android 11 has been disconnecting from my EAP245 randomly while in use. I've noticed this happening when sitting just a few feet away from the EAP245. This happens randomly, and at times the phone remains disconnected for a while. Sometimes, when the phone reconnects, it chooses to connect to an EAP615-Wall which is much further away, on the floor above and in the opposite corner of my house. If I wait enough, the phone might reconnect to the EAP245, but this doesn't always happen. If I disconnect my phone from wifi, and reconnect it, it does end up connecting to the EAP245, but it might get disconnected again. From what I can tell, no other clients exhibit this behavior... but most of my clients are static and are bound to AP specific SSIDs.
A couple of details about my setup:
- Controller - 5.0.30 on Raspberry Pi 4, running ubuntu 18.04
- Living room (second floor): EAP245v3 - 5.0.4
- Third floor: EAP615-Wall - 1.0.2
- Fourth floor: EAP615-Wall - 1.0.2
- Router: TL-R605 - 1.1.1
- Fast roaming and AI roaming is enabled
- All three access points have a 5g only SSID that my phone is connected to
- The EAP245 has 8 clients connected to 5g SSID and 14 clients connected to a 2.4g SSID
- Load balancing and force disassociation is disabled
- both Wall units have transmission strength set to medium.
- each access point has a specific SSID that I connect static clients to (e.g. smart thermostats, chromecasts, etc)... not sure if this was a bad idea
I'm wondering if there is a good way to determine if the issue is in the Omada setup, or a problem with my phone. Particularly, I'm wondering if there is a way to see if the EAP245 is force disassociating the phone for whatever reason, via logs. Any other debugging guidance would be much appreciated.