Fixed - Very poorly balanced RT-AX88U AiMesh running Merlin

[mswlogo]

I've been fighting with my AiMesh for quite a while with clients not on the optimal AiMesh node

Issue:
I run with a hardwired Backhaul
I have about 50 clients and two AX88U's running Merlin
I do run with split SSID's (2.4Ghz and 5.0Ghz) all the problems exist even with "Smart Connect" (one SSID for both)
I'd have situations where I'd see clients on absolutely the wrong node (connection with have to pass one node to reach the further node it connected to)
It's mainly due to boot up order, that the main AX88U comes up first, a whole bunch of clients end up on that router then the Slave AiMesh node comes up a couple minutes later
So I end up with like 45 devices on Main AX88U and 5 on the Slave AX88U
The smarter devices (e.g. phones and computers) would migrate to the best node, but a lot of dumb devices would stick. So next day it might be
40 and 10, still very lopsided
I have, lot's of smart devices, smart appliances, echo shows, 4 macs and many other iDevices, and a boat load of phones (I'm a mobile developer)
Oh and a Tesla that needs good wifi in the garage which is what started this whole mess
I hardwire as much as I can
1) AX88U is in the cellar in the ceiling in the corner closest to the Garage
2) AX88U is on main floor in a closet almost on the extreme the end of the house about 45 ft away (away from the garage)

Experimenting:
For grins, I turned off Hardwired Backhaul and instantly everything was like 20 and 30 (as they should be) and all the closest clients were on the correct node.
OMG, the back haul is broken. So I turn it back on, and every thing was still balanced.
So it's not the hardwire Backhaul, it's from flipping the switch, that causes it to drop all wifi clients and let everything reconnect with both nodes fully up.

Unrelated learnings:
Binding works like SH*T (it just stops things from rebalancing) [didn't retry binding after I came up with the work around below]
If you do use binding and want to move a client to another node, ignore the low power warning message, which is bogus
Optimize seemed useless too. If you ran Optimize (hardwired backhaul off) it ran a lot like a fresh boot that everything would connect to the primary first.
Flipping the hardwired backhaul switch was the best "Optimization" I could do
Pretty disappointed that ASUS does this and I may look elsewhere next time around

Solution:
How can I automate simulating flipping that hardwired backhaul switch? like this

This may require Merlin

Setup a boot script that does /sbin/service restart_wireless a couple minutes after router boots
It needs to be done TWICE, it partially rebalances the first time, but the 2nd time it seems to be fully balanced (i.e. fully optimized)
So there are two scripts, one to restart wireless twice and another to run that script 2 minutes after boot and set up a cron job to run that script once a day
The cron job might be overkill, but won't hurt.

Scheduled Reboot will NOT solve this, if anything it will make it worse and make you regularly unbalanced (i.e. unoptimized)

If anyone knows a better way to resolve this, let me know

In Administration
Enable jffs
Enabled ssh

ssh [email protected]

cat << 'EOF' > /jffs/scripts/services-start
#!/bin/sh

# --- Schedule nightly WiFi reset at 3:00 AM ---
cru a WiFiReset "0 3 * * * /jffs/scripts/wifi_reset.sh"

# --- Run once 2 minutes after boot ---
(
sleep 120
/jffs/scripts/wifi_reset.sh
) &

EOF

chmod 755 /jffs/scripts/services-start

cat << 'EOF' > /jffs/scripts/wifi_reset.sh
#!/bin/sh

logger -t wifi_reset "Starting WiFi reset sequence"

logger -t wifi_reset "Restart #1 initiated"
/sbin/service restart_wireless

sleep 60

logger -t wifi_reset "Restart #2 initiated"
/sbin/service restart_wireless

logger -t wifi_reset "WiFi reset sequence complete"

EOF

chmod 755 /jffs/scripts/wifi_reset.sh

This is an alternative to the above two scripts, If you don't want the cron job then just do this:

cat << 'EOF' > /jffs/scripts/services-start
#!/bin/sh

# Run everything inside a background subshell
(
# Wait 2 minutes after boot
sleep 120

logger -t wifi_reset "Starting WiFi reset sequence"

# First wireless restart
logger -t wifi_reset "Restart #1 initiated"
/sbin/service restart_wireless

# Wait 60 seconds
sleep 60

# Second wireless restart
logger -t wifi_reset "Restart #2 initiated"
/sbin/service restart_wireless

logger -t wifi_reset "WiFi reset sequence complete"

) &
EOF

chmod 755 /jffs/scripts/services-start

Try before you buy:
If you have a hardwired backhaul
reboot, observe how messed up things are
then flip the hardwired switch off/on
then observe again

or

reboot, observe how messed up things are
ssh in
/sbin/service restart_wireless
wait 1 min
/sbin/service restart_wireless
then observe again

Absolutely everything is connected where it should be, near immediately

 

[jksmurf]

I've been fighting with my AiMesh for quite a while with clients not on the optimal AiMesh node

Liked your post not for the solution, if ASUS was working properly you shouldn’t need to implement a script, but for the thought process trying to address issues a number of us have experienced at various stages. Well done you .

 

[Tech9]

make you regularly unbalanced

What makes you "unbalanced" is the fact both routers run on full power by default. Unfortunately, AiMesh doesn't have per device Tx power control and your band-aid solution will be always temporary. Router + AP Mode configuration will give you more control, but you'll lose Guest Network propagation to "nodes". Get Omada or UniFi on your next upgrade.

 

[mswlogo]

What makes you "unbalanced" is the fact both routers run on full power by default. Unfortunately, AiMesh doesn't have per device Tx power control and your solution will be always temporary. Router + AP Mode configuration will give you more control, but you lose Guest Network propagation to "nodes". Get Omada or UniFi on your next upgrade.

No way. That's a band-aide and would defeat the purpose of having a Mesh in the first place. That's what ChatGPT suggested.

You want overlap. You're saying turn down the power on the primary so far 1/2 the house won't see it, at all.
So that they will wait for the node that is closer to come up.
Now the primary Node will run like sh$t and not reach the garage or much of anything.

This would not work well with Mesh or AP
I didn't see you said power tweaking with AP only, but even if you could on Mesh it's not good.

I want full power on two extreme ends of the house. One end to reach the garage and the other to reach blink cameras way out in the yard

The problems is sequencing, and the solution was to let devices pick the strongest (at the same point in time). Many devices are too dumb to reevaluate later.

I'll update my post with router locations

Almost every device in the house could connect to either router and run ok. It was really reaching the garage with one and the blink cameras on the other.
And no, I don't want to run an AP in the garage, been there done that, electronic don't like it when it's 0F out.

And running AP Mode I did consider, but it's a lot less work to use a Mesh if you can get it work. And that would be harder to get every device on the optimal node.
The wifi restart comes up in unison on both nodes so devices can easily pick the best node every time.

I don't have to do anything now, everything optimally connects and don't have to mess with non overlapping channels from two routers and neighbors or play with power.
And I get max reach on both ends of the house.

 

[Tech9]

That's what ChatGPT suggested.

Follow ChatGPT advice then. No problem.

 

[Tech9]

Almost every device in the house could connect to either router and run ok.

Yes, the reason for your imbalance. You have too much overlap between the two APs and your devices just connect to the first seen. This is not a Mesh. This is a Mess. I have 4x APs in my home and don't need to restart anything. ChatGPT will help you further. Good luck!

 

[mswlogo]

Follow ChatGPT advice then. No problem.

I ignored ChatGPT advice, because it was giving me the same advice you just suggested

I do appreciate your sharing ideas, but using AP mode and messing with power with be a total time suck and terrible results.

One router is just barely reaching the garage on one end and the other is barely reaching the furthest blinks. And reduction in power on either and I'll lose them, period.

I could lock clients down using two SSID's on two routers, but that would be a ton of work.

 

[mswlogo]

Yes, the reason for your imbalance. You have too much overlap between the two APs and your devices just connect to the first seen. This is not a Mesh. This is a Mess. I have 4x APs in my home and don't need to restart anything. ChatGPT will help you further. Good luck!

It's working perfect now. And I only need two nodes. I guess that's why you need 4 AP to fill in the gaps you made by turning down the power.

It's a bug in ASUS that it just doesn't do this in the first place or give an option to do it. You want the nodes to come up simultaneously so dumb devices pick the best one.
It does have a really stupid mode "Roaming Assistant" of doing something like this per node, but it's almost as dumb as turning down the power on AP nodes.
If power drops below threshold then roam. That would be a nightmare using that.

It should just periodically renegotiate any node, by time [off hours], when all nodes are UP. Which is WHAT I DID. Because it may find a better node, and does.

Don't need the ChatGPT digs, really. Because ChatGPT gave that same advice you did and I ignored it as it was really terrible advice.
But if it works for you, tweaking power on every AP to get 50 devices connecting where you want, and messing with all the channel clash, enjoy.

If I did what you suggest I'd have to put an AP in the garage and way out in the yard.
Because we don't want them too strong or something in the house might connect to them. Can't have any overlap, right. That's insane.

So in the extreme, why not have an AP for every client device with the lowest power possible? If 4 is good, 16 has to be better, right?
That's exactly the way you're thinking. And in the extreme yeah, it would work.

If I could double the power on one, and run no mesh, I would.

Sorry if my script was overwhelming for you. It's pretty damn simple and works great.

The main problem is not power, it's that it comes up sequentially, script solves the sequential problem.

Everybody, reconnect, when all mesh nodes are up. That's all it does.

I'm using the least nodes to get the two extremes of coverage I need and I should not care what overlaps (clients should find the best one, and they can, and now they do, when shown all the options at the same point in time)

 

[Tech9]

The main problem is, not power, it's that it comes up sequentially, this solves the sequential problem.

Well... if constant rebooting is your choice - continue doing it. I have some doubts many people will be very pleased with such a fix. If you want permanent fix advice, let me know. I can only give you a hint - router/AP too close with signal too strong is seen as less preferable connection by your devices. Your routers depending on the region use up to 1000mW power per radio. I use 40mW on 2.4GHz band and 100mW on 5GHz band and my devices roam between the APs perfectly. I never reboot anything unless software update requires it. Tuning a system needs some understanding of how Wi-Fi works. High power AP 30dBm to low power client 12-14dBm at distance and through walls is not a good Wi-Fi.

If I could double the power on one, and run no mesh, I would.

No. You'll only create disbalanced links. You don't change the power of the client. Wi-Fi is 2-way communication. If you stopped here to learn something - good. If you stopped here to advertise your rebooting as a solution - bad. There is no sequential power up problem. Your devices will be messed up again on next re-connect. You know it, but don't know why it happens.

 

[jksmurf]

It's mainly due to boot up order, that the main AX88U comes up first, a whole bunch of clients end up on that router then the Slave AiMesh node comes up a couple minutes later
So I end up with like 45 devices on Main AX88U and 5 on the Slave AX88U

Just a data point on this statement btw, as I have observed similar behaviour, but if I let it settle, the mostly IoT 2.4Ghz clients gravitate to the closest node and eventually find what I consider to be a reasonable balance.

I use AiMesh, Smart Connect and it seems to work pretty well on my local system. The remote system is all wired backhaul so has different parameters.

There’s so many variables though, with everyone’s systems and conditions, it must be really, really difficult for the system designers to work out configurations that will bracket the greater proportion of users needs.

 

[Tech9]

really difficult for the system designers to work out configurations

It's super easy if you have the control options. The reason I recommended upgrade to system with everything needed out of the box. AiMesh is mostly testing your luck. Some other home "mesh" systems do the tuning automatically. At least make an attempt.

 

[mswlogo]

Just a data point on this statement btw, I have o served the same behaviour, but if I let it settle, the mostly IoT 2.4Ghz clients gravitate to the closest node and eventually find what I consider to be a reasonable balance.

I use AiMesh, Smart Connect and it seems to work pretty well on my local system. The remote system is all wired bsckhaul so has different parameters. There’s so many variables though, with everyone’s systems and conditions, it must be really, really difficult for the system designers to work out configurations that will bracket the greater proportion of users needs.

There were some that were just not moving. Some, it didn't really matter all that much, they would run fine on either. Some would move, and some that did move would take a long long time move. This way, if I get a power glitch, or I do want to reset things, I'm fully optimized in 3 minutes.
And like I said the, Tesla is what started this, and it was stuck on the wrong node, and I had to reboot the car to get it move if it landed on the wrong node.

I updated the OP, with a simpler alternate, just do it on boot only. That's when it's the worst. And for folks that do daily reboot to resolve other issues, this is a must.
And I also added manual steps to test it before adding any scripts, to just see if it's worth it. Try it.

I always thought it was resolving itself. But it wasn't when I looked closer and part of that resolution was some clients eventually rebooted or maybe they eventually do renegotiate.
But it was always always heavily lopsided with way to many devices connecting to the worse placed node, the primary, (but it's the best place for the garage and needs max power)

Oh, and now when I reboot just the primary, everything is perfect too. It's win win. So simple.

I've always run split SSID's I had a few odd devices over the years that just refused to connect. Like a furnace that had older tech and was 2.4Ghz but if it was joined it just wouldn't connect at all. Anything I know needs speed, I put on 5Ghz (regardless if it's weak). Anything that needs range and doesn't need bandwidth I put on 2.4Ghz.
Having that control has been really helpful. Letting devices decide and bounce between, not helpful.

For the most part, only the phones, AppleTV, Echo Shows's are on 5Ghz. All computers are wired and most everything else is on 2.4Ghz.

 

[mswlogo]

Well... if constant rebooting is your choice - continue doing it. I have some doubts many people will be very pleased with such a fix. If you want permanent fix advice, let me know. I can only give you a hint - router/AP too close with signal too strong is seen as less preferable connection by your devices. Your routers depending on the region use up to 1000mW power per radio. I use 40mW on 2.4GHz band and 100mW on 5GHz band and my devices roam between the APs perfectly. I never reboot anything unless software update requires it. Tuning a system needs some understanding of how Wi-Fi works. High power AP 30dBm to low power client 12-14dBm at distance and through walls is not a good Wi-Fi.



No. You'll only create disbalanced links. You don't change the power of the client. Wi-Fi is 2-way communication. If you stopped here to learn something - good. If you stopped here to advertise your rebooting as a solution - bad. There is no sequential power up problem. Your devices will be messed up again on next re-connect. You know it, but don't know why it happens.

You didn't read my post

All you need is this on boot, that's it, and you do need to do it twice

sleep 120
/sbin/service restart_wireless
sleep 60
/sbin/service restart_wireless

Since I had bothered to add a boot script, I figured it won't hurt to add 1 more line for a cron job. There are other bugs in ASUS routers, really.
I have seen a few other issues, that I just lived with and that nightly wifi restart might clear those up too, it's totally harmless.

I have very little doubt, most would be overjoyed with this and makes the ASUS AiMesh work so much better it's not funny.
I was thinking of replacing it before I found this work around
It's why I took the time to share it

Yes, it is absolutely, beyond a doubt, a sequential power up problem.