@Coltean 

 

Hey

 

Im guessing when you say you have adopted the AP, then you are running a controller?

 

If so have you enabled Fast Roaming and AI Roaming?   Without this enabled you are leaving the roaming to the device, and they tend to be awful at at.   Enabling fast roaming and AI roaming should force this to move across when a better AP is available.

 

I would also recommend dual band 11k report, this way it can roam 2.4 to 5ghz at the same time..

 

Hey, Yes I am running a software controller on my server. I’ll give those settings a try and see how it does. I appreciate the prompt response ! Cos

@Coltean 

 

No worries and welcome

 

Yeah hopefully that is all that is required, keep us posted on how you get on

 

Check the logs once you have it enabled and look for roaming events similar to below

 

@Philbert 

 

I managed to find most of the settings you described. I guess some of the settings may be obsolete or hidden away in the new UI. The BasementAP is still not reporting any clients. 
 

I went ahead and turned off both radios on the upstairs AP. The connected clients dropped to 0 as expected. The basement AP remained at 0 clients as well, but most of my devices seemed to have jumped on with network access - but no clients reporting in the controller.

 

Not sure if this is designed to worked this way or I may be missing a set up step. 
 

 

 

 

@Coltean 

 

Hey

 

Sorry for the slow reply

 

I think I see your issue here!    The version of the controller you are running is SDN v3   -   This is no longer supported and you should update to SDNv4.  It is likely the AP is actually working ok, but as its not supported on that controller one of the symptoms is no stats available, exactly what you have

 

So the AP in the basement, you can try clicking the UP arrow under actions to see if you can get this to firmware 2.4 the same as the other one.

 

 

However.. a better option is to just update to v4 SDN, its a bit of work but worth it..    are you running a Software Controller or an OC200/300?

 

backup the controller first!

 

If OC then download the latest firmware for that from the TP Link Support site and manually upgrade the controller (this wont auto update as its a major change)

Firmware you are looking for it   OC200(UN)_V1_1.8.0 Build 20210406

 

If Software.. do the same for it, but use the latest software version.

 

This link below might help you more

https://static.tp-link.com/Omada%20Controller%20Upgrade%20Guide_20200615.pdf

 

Once you are on V4 of the controller, restore the config then I strongly advise you check for updates on the APs, they should be running firmware 5.0.x    firmware 2.x is really old now

 

 

 

@Philbert 

 

Hello!

 

I am running software controller on my NAS. I didn't even think about the version and firmwares. It does make 100% sense on what you are saying and I think that may be the issue thinking about it. I'll give it a shot later today and get everything up to date.

 

I really appreciate your time and help on this!

 

Will report back once I get this done 

@Philbert Hey! You were spot on! I didnt realize I disabled my update tag on my docker Omada Controler Image and was stuck on V3. Managed to launch V4.4 and booted a new image. I decided to start fresh and adopt all the AP's to the new controler. All works beautifully now - clients roam as they should between the two APs. Rookie mistake on my part - I do appreciate the insight and help on this.