What's new

BE86U worse wifi latency vs old ax86s

I have a client that keep jumping to the main router when the node is like -60dbm. It's my only wifi 7 client too.
Also why doesn't asus allows us to adjust tx power per node?! It would come in handy to avoid sht like this
I've never seen a client connect at -90dbm before, let alone one with a node close by with good reception.
1775906086268.png


1775906693979.png
 
Last edited:
I have a client that keep jumping to the main router when the node is like -60dbm. It's my only wifi 7 client too.
Also why doesn't asus allows us to adjust tx power per node?! It would come in handy to avoid sht like this
I've never seen a client connect at -90dbm before, let alone one with a node close by with good reception.
I think you’ll find @Tech9 often quotes the issues surrounding choice of node, and ultimately that it is the client that decides.

I agree per-node TX power would be good but it’s not part of the AiMesh system.

My own experience is that with IoT devices if they are smarter then you can set an in-device RSSI. Often though the dumb ones will just connect to the node that comes up first (especially when booting the AIMesh system) and if the RSSI is good enough for the settings in that device it does not bother to move.

Subsequently unplugging it and plugging it back in again, it may find the correct node i.e. it’s a timing of Main vs Node startup. IoT devices don’t physically move so you might consider binding them to a node. It’s messy but it works.

Non-IoT client devices will as noted in the posts below, “decide”. You can steer them with Smart Connect to a band, but unfortunately not to a node. You can “encourage” them with roaming assist RSSI settings but this is also not guaranteed.

As to your earlier post lamenting the absence of reporting of RSSI values on clients, as you run Merlin FW, try the Addon Wireless Report, it’s really quite good. See page 1 of the thread for passwordless ssh setup to work with nodes.


 
Last edited:
Also why doesn't asus allows us to adjust tx power per node?

I have a theory about why - consumer product and user friendliness. If you have options to adjust Tx power per device the wireless backhaul may be affected as well and break the mesh. The options provided ensure this is unlikely to happen. This is ASUS' approach on Broadcom hardware. Some other vendors using Qualcomm hardware rely on built-in self-adjusting. Devices targeting the business market have all the settings available, but most are deployed by professional services.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Back
Top