@arthurlien Well that's a hard one to answer for sure, as I can't definitely say until I roll out the AiMesh setup (4 X AC68U AP's) properly to the house.
I'm hanging off doing that at present and just playing with them "on the bench" whilst following this thread and watching developments.
But I CAN say that under my current setup, which is 4 X TP-Link WDR-4300 "Wireless N" AP's set with identical SSIDs, I have a specific use case that requires this.
I have 2 X IP cameras which are in fixed positions but happen to both be within strong signal zones of at least 2 AP's.
These get triggered by movement and get recorded by software running on a macOS server.
I was finding that both cameras would randomly just disconnect at times and the recordings would be truncated or fail.
I fixed this on the current AP's by blacklisting the MAC addresses of the 2 X IP cams on all but the "closest" AP.
It's worked fine ever since.
Since I see no current way to achieve this "selective AP Node blacklisting/whitelisting" in AiMesh, my concern would be that the IP Cams will behave in the "old" way once I cut across to the AiMesh setup. To reinforce this I also note a lot of comments on here about how devices tend to initially connect to the closest/strongest Node but over time roam to the Router Node, even though that may not be the closest/strongest, which reinforces my concern.
This doubt plus the lack of guest networks across all Nodes is my main excuse for holding off. That and hoping there may be a new build soon that improves some of this.
If it was just me in the house I'd put them into position and see how it goes, but its NOT just me and other members of the household expect working Wifi at all times and if it fails it's always my fault!
If I do get a good chunk of hours on my own I may give it a go anyway ...
StephenH