ZenWiFi BT10 5GHz

[JamiryoFC]

I upgraded from a 2-node TP-Link Deco X60 v3.20 mesh to a 2-node ASUS ZenWiFi BT10 mesh. Both systems are placed in the exact same locations as before. The BT10 nodes use 10 Gbps wired Ethernet backhaul, ethernet backhaul mode is on and MLO fronthaul is enabled.
My phone does NOT support 6 GHz, so it always connects on 5 GHz.

In a spot where the Deco satellite used to show full signal bars, the BT10 sometimes drops to 1 bar, yet real-world speeds are the same or slightly better than before.
What could explain lower signal bars/RSSI readings while throughput remains the same or improves? Could it be differences in signal-bar mapping, roaming/steering behavior between nodes, DFS channels, channel width (80/160 MHz), or Asus settings like Roaming Assistant/WiFi Agile Multiband? What settings should I check to stabilize coverage reporting and roaming?
The interesting part is this: In the back room where the Deco’s main router had zero signal, the BT10’s main unit now shows full bars. So the BT10’s primary unit clearly has much stronger coverage than the Deco.


However, in that same spot, the BT10 satellite node sometimes shows only 1 bar on my phone, and I can’t understand why the coverage would drop there.

 

[Tech9]

Look at Wireless Log, find your test client, watch the RSSI and link rates. One bar closer to the node sound like your test client is still connected to the main router and not the node.

 

[jksmurf]

Look at Wireless Log, find your test client, watch the RSSI and link rates. One bar closer to the node sound like your test client is still connected to the main router and not the node.

Yep; Sounds like (per your observations) stronger signals from your new BT10 units so once connected at the acceptable RSSI it’s hanging on to the client like a limpet (sticky clients), even as you migrate far from the main towards the much closer node.

You may be able to change that behaviour for that client (you’ll need to see if you’re happy with how other clients behave with new settings) by changing the limiting RSSI in roaming assist (wireless professional) for the band (probably 5GHz) it’s connected at.

Failing that (or in addition) you could try to tweak Smart Connects Steering Trigger and STA settings, although these tend to be more for when to give up on 5GHz and at least get you connected at 2.4GHz. I don’t have BE units so I’m not sure what effect MLO may have.

At least for you, your TX power is the same on both units, for those of us with mixed main and node devices it’s yet another factor, with clients often preferring the higher TX devices and no way under AiMesh to individually balance these out.

I think you’ll find many posts here referencing clients deciding about connectivity, so there’s no guarantees the above will give you the (absolutely reasonable) expected transition from main to node or node to node at say the mid point. Try RA first maybe, test it with the one device, see how the others behave. My experience is that it’s an absolute balancing act between having a device connect at all and hanging on too long.

I’m not convinced ASUS have the default (i.e. it should just work) settings right, but to be fair, there’s so many combinations and permutations of settings, devices, topography and physical layouts, it’s a hard ask to get it right. You can spend hours, days, weeks tweaking (I know I have), for both bands and still end up with just “the best compromise”.

 

[Tech9]

I wouldn't replace the Deco X60 in first place. At least not now. This model is older, but Qualcomm Dragonwing NPro hardware with Qualcomm SON (Self-Organizing Network) set of features. Variation of this hardware is used in SMB access points (Ubiquiti UniFi, HPE Aruba) with more granular control. TP-Link made it Plug-and-Play in their Deco sets. In wired configuration and common 80MHz channel bandwidth (for non-DFS range) Deco X60 can do >800Mbps to wireless clients from both Main and Satellite units.

 

[JamiryoFC]

On my ASUS ZenWiFi BT10 AiMesh setup, I’m seeing a strange difference in “beamforming” related values between the main router and the node.
How I found it: I SSH’d into both units and checked the wireless driver/NVRAM/“wl” outputs for beamforming-related parameters (same firmware, same settings). The main unit reports a value around 255, while the AiMesh node reports around 111.

Questions:

1. Is it normal for AiMesh nodes to show different beamforming levels/values than the main router?
2. Could this simply be a driver/UI scaling or a reporting quirk (not a real functional difference)?
3. Can this difference impact client throughput, roaming, or stability (especially with wired backhaul)?

Setup notes: BT10 main + 1 node, Ethernet backhaul enabled, same SSID on 2.4/5/6 GHz.
Thanks!

 

[Tech9]

You don't have to worry about any of this. The way it is set is the way ASUS needs it to be set. Wireless drivers and AiMesh are closed source components and there is nothing to be optimized by the user. You may look to satisfy your curiosity, but don't touch unless you want to reset everything and start over. What matters to you is the user experience. If it's good - keep the set. If it isn't - send it back.

 

[JamiryoFC]

You don't have to worry about any of this. The way it is set is the way ASUS needs it to be set. Wireless drivers and AiMesh are closed source components and there is nothing to be optimized by the user. You may look to satisfy your curiosity, but don't touch unless you want to reset everything and start over. What matters to you is the user experience. If it's good - keep the set. If it isn't - send it back.

I only changed the region (country/locale setting) to allow a higher 5 GHz transmit power. After that change, my coverage improved a lot: across the whole apartment the worst 5 GHz signal I typically see is around -62 dBm, and roaming is now basically perfect (clients move between main/node cleanly, no sticky behavior or random drops).

 

[Tech9]

I only changed the region (country/locale setting) to allow a higher 5 GHz transmit power.

This action is:
- illegal
- almost guaranteed temporary until next reboot

 

[degrub]

I only changed the region (country/locale setting) to allow a higher 5 GHz transmit power. After that change, my coverage improved a lot: across the whole apartment the worst 5 GHz signal I typically see is around -62 dBm, and roaming is now basically perfect (clients move between main/node cleanly, no sticky behavior or random drops).

Reboot and make sure you are on the correct region. Stay legal and don't annoy the neighbors, at least.

 

[JamiryoFC]

Reboot and make sure you are on the correct region. Stay legal and don't annoy the neighbors, at least.

I dont think i bother neighbors bc rn the wifi signals equals to my previous mesh system. Btw i rebooted system bc tech9 informed me that it's illegal. Still, thank you for your time and replies.