Wireless Report

[JB_1366]

Looking for feedback, the reason why I started the script was because ASUS web UI doesn't show aimesh node rssi for wireless devices, plus its nice to see all wireless devices in one spot. Asus firmware takes way to long to to adjust devices to correct router/node, not to mention after router reboots, node seems lost trying to move devices to correct router/node. I have to manually reboot node, which seems to fix, but sometimes i have to power cycle node, as restart sometimes doesnt work. anyhow, give me the good/bad/ugly, additions/substractions. Using YazDHCP to show pretty hostnames.

click side by side view button

 

[JGrana]

Github link?

 

[Tech9]

Looking for feedback, the whole purpose for this script was to load balance router/aimesh-node wireless devices. Asus firmware takes way to long to to adjust devices, not to mention after router reboots, node seems lost trying to move devices to correct router/node.

The UI is definitely pretty, but how is the script helping with load balancing? The clients decide where to connect and the reason for the imbalance is the fact AiMesh is multi-AP system with no per device Tx power control. If your nodes are at less than -60/65dBm signal level between them - you're out of luck.

 

[JB_1366]

The UI is definitely pretty, but how is the script helping with load balancing? The clients decide where to connect and the reason for the imbalance is the fact AiMesh is multi-AP system with no per device Tx power control. If your nodes are at less than -60/65dBm signal level between them - you're out of luck.

it lets me see a snapshot, to manually bind devices to where I know they should be, instead of waiting 1 day for fw to try and adjust. as I've been playing around the last couple of weeks, i know exactly where they should be, so after a reboot, i bind them to correct router/node, then I unbind them once they are there..they pretty much stick after that..just being geeky I guess.

 

[visortgw]

it lets me see a snapshot, to manually bind devices to where I know they should be, instead of waiting 1 day for fw to try and adjust. as I've been playing around the last couple of weeks, i know exactly where they should be, so after a reboot, i bind them to correct router/node, then I unbind them once they are there..they pretty much stick after that..just being geeky I guess.

Unless you move devices, why unbind them?

 

[JB_1366]

Unless you move devices, why unbind them?

I find if I keep the bind on, some devices don't like it, and they start greying themselves out in Asus device list, weird i know, so the way I've done it works for me.

 

[Tech9]

to manually bind devices to where I know they should be

I know AiMesh is difficult to tune, but... you have GNP/Network available, no? Make SSID1 at AP1, SSID2 at AP2 and SSID3 at AP1/AP2. Clients moving around connect to SSID3, the rest non moving connect to SSID1 and SSID2 accordingly where they belong to. The moment you turn the routers ON your clients will have no choice but connect to the right APs and you don't have to do anything manually. No script needed.

 

[jksmurf]

Looking for feedback

I think it looks fantastic, I think I’ve mentioned in another thread I have a very crude script that performs a similar function (now run from main, but accesses the nodes) via ssh only.

It shows MAC addresses as well as RSSI numbers, as it’s for troubleshooting like you, but I don’t think your layout has room for that too, if you’d like customization maybe you could have selectable options for what to show / not show.

Mine groups by node similar to yours, but has the devices subgrouped by SSID. I think that would be messy on your screen though.

Other feedback would be does it auto refresh and how long does it take?

But honestly these are minor comments, it is a really nice piece of, well done you.

Asus firmware takes way to long to to adjust devices to correct router/node

Yep, all that. I have set in-device RSSI in my Shelly IoT devices which moves them ok and HA recently improved this for ESP32 devices, but you have to be patient.

You could start playing around with RA Roaming Assistant dBm but mine is off for 2.4Ghz anyway. Or if I you use it with the two settings Trigger and Steering (for each band) in Smart Connect, but taking that path is like going down a rabbit hole … the cleverer devices like phones will decide themselves anyway.

 

[JB_1366]

I think it looks fantastic, I think I’ve mentioned in another thread I have a very crude script that performs a similar function (now run from main, but accesses the nodes) via ssh only.

It shows MAC addresses as well as RSSI numbers, as it’s for troubleshooting like you, but I don’t think your layout has room for that too, if you’d like customization maybe you could have selectable options for what to show / not show.

Mine groups by node similar to yours, but has the devices subgrouped by SSID. I think that would be messy on your screen though.

Other feedback would be does it auto refresh and how long does it take?

But honestly these are minor comments, it is a really nice piece of, well done you.



Yep, all that. I have set in-device RSSI in my Shelly IoT devices which moves them ok and HA recently improved this for ESP32 devices, but you have to be patient.

You could start playing around with RA Roaming Assistant dBm but mine is off for 2.4Ghz anyway. Or if I you use it with the two settings Trigger and Steering (for each band) in Smart Connect, but taking that path is like going down a rabbit hole … the cleverer devices like phones will decide themselves anyway.

all columns are sortable, so ssid column would group all together per main/node view.