Aimesh Sticky Client Issue

[ComputerSteve]

I have had so many problems with AiMesh not reliably being able to kick my Mac even with roam assistant enabled and the setting changed to a drastically low number. I read about this and apparently it’s a known issue something that has to do with sticky clients. Does anyone have any suggestions on how to fix this problem. Do any Merlin compatible routers actually roam properly. Right now I have a GT-Ax11000 pro main router and 4 XT8 Nodes and the Mac will never roam. This also happened when I had the RT-AX88U and RT-AX86U node combination. I can forcefully make it roam by disconnecting the client and then re-enabling it but it doesn’t do it automatically. I also found that if there was a way to make AiMesh use this type of BSS request
disassoc_imminent = 1 instead of what it currently does of = 0 it would work. However without scripts and using HostAPD it’s not possible.

 

[Tech9]

If your client never roams - it sees good signal from single AP. You have too much Wi-Fi. I don't know where do you live, but in US/CA region your routers blast close to 5000mW on single channel. I have 4x APs on 400mW total in >6000sqft house in CA region.

 

[ComputerSteve]

If your client never roams - it sees good signal from single AP. You have too much Wi-Fi. I don't know where do you live, but in US/CA region your routers blast close to 5000mW on single channel. I have 4x APs on 400mW total in >6000sqft house in CA region.

I understand that concept. That isn’t what I’m talking about! I’m talking about even if I remove all my nodes, and just keep my main router with 1 node. My Mac will stay connected to the main router till it’s basically an unusable signal, and never choose to roam. I thought AiMesh is supposed to handle this? I’ve watched all the marketing. I’ve seen it talk about this seamless roaming thing. this is not what is happening. Instead my Mac will stay stuck. I’m asking are there any fixes for that. I can fix it with scripting.. however I don’t know why this isn’t being addressed. It’s not making this system as efficient as it should be.

 

[Tech9]

I thought AiMesh is supposed to handle this?

No, roaming is client's decision. The APs can only encourage roaming using different techniques, but AiMesh has limited options. If your APs are spaced at around -70dBm signal, the APs and clients support 802.11k/v/r, the roaming assistant is actually working, etc. - your client will roam. This document may give clues what may be wrong:

Wi-Fi roaming support in Apple devices

Supported Apple devices and Cisco networks recognize each other, allowing the devices and network to use the latest Wi-Fi technologies to optimize the experience.

support.apple.com

Check support forums for tips about possible client settings modification. It will be hardware specific.

 

[ComputerSteve]

You’re absolutely right that roaming is client-driven, but ASUS AiMesh doesn’t hold up to its own marketing. They advertise seamless roaming, yet in reality, Roaming Assistant often doesn’t work as intended—it’s passive, triggers too late, and in many cases doesn’t even kick the client when it drops below the configured RSSI threshold.
This is especially obvious with MacBooks and iOS devices, which are notorious for sticking to distant or the wrong nodes. ASUS users have reported this for years, and it’s not just “client behavior”—because these same devices roam just fine on systems like Eero, UniFi, Deco, and even Google Nest.
The real issue seems to be how ASUS handles roaming internally:

• No real-time steering logic.
• Weak or inconsistent 802.11k/v implementation.
• No proper BSS transition enforcement.
• Poor node load awareness.

So while yes, clients decide when to roam, ASUS gives them very little help, unlike other mesh systems that actually encourage or even push the client to move. The sticky client issue isn’t universal—it’s an ASUS problem. If AiMesh wants to be taken seriously, it needs smarter logic, better enforcement of roaming standards, and more transparency about what it’s really doing under the hood. I am hoping that in future firmware updates these problems will be addressed.

 

[Tech9]

So while yes, clients decide when to roam, ASUS gives them very little help, unlike other mesh systems that actually encourage or even push the client to move.

Agree and my own observations are similar. Lack of individual APs Tx power control in AiMesh is enough to cause severe roaming issues. When playing with AiMesh I also found Roaming Assistant non-working on different firmware versions or it disconnects the clients and they re-connect to the same weak AP. Perhaps different hardware with different drivers and home AIO devices mainly designed to work as single AP holding all clients until the signal dies completely is causing this behaviour. AiMesh is like a patch software on top of what Broadcom is doing on driver level. Qualcomm based Eero, Nest, Deco, etc. have mesh features built-in and supported by the chip manufacturer. Some newer models do environment assessment and auto-tune the system for optimal roaming.

The reason I don't recommend Asus with AiMesh when Ethernet is available and multi-AP system is needed (Unifi, Omada) or when the user requirements are "easy button" installation with minimum play with settings to make things work (Eero, Deco, Nest).

 

[hancox]

You’re absolutely right that roaming is client-driven, but ASUS AiMesh doesn’t hold up to its own marketing. They advertise seamless roaming, yet in reality, Roaming Assistant often doesn’t work as intended—it’s passive, triggers too late, and in many cases doesn’t even kick the client when it drops below the configured RSSI threshold.
This is especially obvious with MacBooks and iOS devices, which are notorious for sticking to distant or the wrong nodes. ASUS users have reported this for years, and it’s not just “client behavior”—because these same devices roam just fine on systems like Eero, UniFi, Deco, and even Google Nest.
The real issue seems to be how ASUS handles roaming internally:

• No real-time steering logic.
• Weak or inconsistent 802.11k/v implementation.
• No proper BSS transition enforcement.
• Poor node load awareness.

So while yes, clients decide when to roam, ASUS gives them very little help, unlike other mesh systems that actually encourage or even push the client to move. The sticky client issue isn’t universal—it’s an ASUS problem. If AiMesh wants to be taken seriously, it needs smarter logic, better enforcement of roaming standards, and more transparency about what it’s really doing under the hood. I am hoping that in future firmware updates these problems will be addressed.

I have found outright disabling roaming assistant makes overall roaming better. YMMV. (2 nodes in a rectangular house)

 

[Tech9]

Yes, because your 2x APs are far enough and the clients have 2x choices only.

With 5x APs AiMesh - good luck. @ComputerSteve network must be covering open space football field or a home with double layer metal mesh in the walls. I still believe too much Wi-Fi is the issue. This client with up to 40mW radio has no idea where to connect with >4W available Wi-Fi around. Very strong near AP is not the best choice for the client. Even with my UniFi system if I stay just next to one of the APs with signal level -20dBm or stronger the client in my hands will try to connect to further located AP first.