Wireless Report Wireless Report AiMesh v1.5.2 [2026-Apr-21] - WebGUI Table of all AiMesh connected devices (available in AMTM!)

[JB_1366]

v1.5.0-saves current column state on all tables on refresh. thx @scootertramp for testing.

 

[JB_1366]

v1.5.1-Added new device detection-the entire device row 'pulses' on new device detected. it checks known_macs.db located in your usb_path. If you ever want to start over, delete that file, your whole report will pulse. or you could delete any mac you want, to see it pulse.

 

[JGrana]

The pulsing works well. I deleted a few clients in the known_macs.db and they did show a slow pulse on the next scan. Then “unpulsed” after the following scan.
Very useful when adding new devices!

One comment - on the initial install/scan don’t pulse. I did a complete uninstall then install via amtm. When I went to the wireless report - they were all pulsing.
Just a recommendation.

 

[Untried3868]

Is there an SSID character limit in WR? I ask because it's cutting off the last character (16 17) of my SSID.

Edit: Correction, 17 characters. Math is hard apparently.

 

[jksmurf]

Is there an SSID character limit in WR? I ask because it's cutting off the last character (16) of my SSID.

Yep. It used to be even shorter, around 10, following an offline discussion with @JB_1366 I think it went to 15, but was never actually published AFAIK.

Whilst that field can go up to 32 on your router, it does make sense to cap it at some lower figure that doesn’t cause havoc with the other columns. I can’t see it getting even close to 32.

 

[ComputerSteve]

So this is a great script @JB_1366 !!
- do you think you can enhance it to actually transition or kick devices that seem to get stuck - Roaming assistant stinks =( It never actually does the kicking of certain devices - even with the threshold set to obscenely low numbers or vice versa very high numbers. I created on each node a script that would issue a bss transition and that seemed to work but this centralized thing if it could do the handling of that would be really cool.

 

[JB_1366]

So this is a great script @JB_1366 !!
- do you think you can enhance it to actually transition or kick devices that seem to get stuck - Roaming assistant stinks =( It never actually does the kicking of certain devices - even with the threshold set to obscenely low numbers or vice versa very high numbers. I created on each node a script that would issue a bss transition and that seemed to work but this centralized thing if it could do the handling of that would be really cool.

I will look into it, as i would also like this.

 

[JB_1366]

v1.5.2-added 'optional' RSSI STEERING. Disabled by default, select #5 in install menu. this only works on router/node refresh, its not ongoing.

The "Technical" Explanation​

Sets the RSSI Threshold for automatic client steering. If a device's signal drops below this value (e.g., -70 dBm), the script will forcibly deauthenticate (kick) the client, triggering it to re-scan the environment and roam to a closer node with a stronger signal.

The "User-Friendly" Explanation
This option manages Sticky Clients. It defines a 'minimum signal strength' for your devices. Once a device moves too far away and hits this limit, the script gives it a digital 'shove' so it stops clinging to a distant node and reconnects to the nearest one.

A "Short & Punchy" One-Liner
Automated client roaming: Kicks devices with poor signal to force them onto a better node.

Script also creates a running log of kicked clients in the USB_PATH directory : [EDIT] - it also puts an entry into syslog, for those who cant or dont want to check their usb_path.
[2026-04-21 06:04:27] [GT-BE98_Pro] Kicking B0:F7:C4:C7:58:6C on wl0.1 (-80 dBm)
[2026-04-21 06:04:33] [RT-AX86U_Pro] Kicking 8C:C1:00:1D:A9:CC on wl1.2 (-73 dBm)
[2026-04-21 06:04:33] [RT-AX86U_Pro] Kicking 80:60:B7:34:9A:58 on wl1.3 (-77 dBm)

 

[jksmurf]

A "Short & Punchy" One-Liner
Automated client roaming: Kicks devices with poor signal to force them onto a better node.

This will be very interesting ... as the 'dumb' devices likely have preset RSSI thresholds they are happy with, what logic actually causes them to go to a different node, if the node they were on, while weak, is still OK?

I have both dumb and smart devices i.e. the latter being ones with in-device RSSI thresholds that you can tune to do a similar thing, that do a few retries then actually move,
The dumb ones often don't move, even after being kicked. Like I said, it will be interesting.

 

[JB_1366]

This will be very interesting ... as the 'dumb' devices likely have preset RSSI thresholds they are happy with, what logic actually causes them to go to a different node, if the node they were on, while weak, is still OK?

I have both dumb and smart devices i.e. the latter being ones with in-device RSSI thresholds that you can tune to do a similar thing, that do a few retries then actually move,
The dumb ones often don't move, even after being kicked. Like I said, it will be interesting.

yes, you will have devices that refuse to roam, i have one in particular, nintendo-switch in deep sleep, would not move after multiple kicks, i had to manually move to correct node. Obviously, this isnt going to help 1 node setups, as much as multi-node setups. I woke up this morning, and had 3 devices that were kicked, all 3 roamed to better node. If this option doesnt work for you, you can just disable it.

 

[jksmurf]

yes, you will have devices that refuse to roam

I haven't checled the settings as it seems a bit like a Harry Potter #5, but would it be possible to have per SSID RSSI (i.e. limit it to IoT), per Node RSSI or even per device thresholds?

I woke up this morning

Always a good sign.

 

[JB_1366]

I haven't checled the settings as it seems a bit like a Harry Potter #5, but would it be possible to have per SSID RSSI (i.e. limit it to IoT), per Node RSSI or even per device thresholds?

View attachment 71379


Always a good sign.

you dont see a #5?

 

[jksmurf]

you dont see a #5?

Nope. See my screenshot. I updated it twice, via amtm, not au, just using wr, then 1.

 

[jksmurf]

Well that's weird, So I tried starting it using wr from the cmd line and it came up with the menu #5 now.

 

[JB_1366]

Nope. See my screenshot. I updated it twice, via amtm, not au, just using wr, then 1.

interesting, i went through all scenarios, uninstall, update, reinstall, all worked

 

[JB_1366]

Well that's weird, So I tried starting it using wr from the cmd line and it came up with the menu #5 now.

internet funk, i suppose

 

[jksmurf]

So 60 -85, single, global figure. OK.

• Could the lower end be lower please. Say -45dBm?
• Could we have a per SSID figure (to start with ... )

 

[jksmurf]

interesting, i went through all scenarios, uninstall, update, reinstall, all worked

Well, just so you know it might happen, in case someone else is as stunned as I was...

 

[JB_1366]

So 60 -85, single, global figure. OK.

• Could the lower end be lower please. Say -45dBm?
• Could we have a per SSID figure (to start with ... )

no and no, for now. there really is no need to kick a -45dbm, dont want to start mayhem on the router kicking all good dbm devices.

 

[jksmurf]

interesting, i went through all scenarios, uninstall, update, reinstall, all worked

So I tried on my second system. Same thing,
However after updating and it showing the #1-4 +e menu but no #5 menu, you exit then go back in again, it shows #5.

1, 2, 3, 4...