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

[jksmurf]

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.

Fair enough. Was just RSSI numbers I had (have) to set for some of my in-device RSSI's to force some of my Shelly units to a node literally 2 or 3 feet away (where they end up with -23dBm (as measured by the device, not the Router, which is slightly different)... but they refused to go there unless I dropped the figure quite low). Here is an example:

 

[JB_1366]

Fair enough. Was just RSSI numbers I had (have) to set for some of my in-device RSSI's to force some of my Shelly units to a node literally 2 or 3 feet away (where they end up with -28dBm... )

this is why i developed this addon. You would think Asus could fix/perfect this, its their software. why would a device at -42, roam to a node with -73, makes no sense.

 

[jksmurf]

this is why i developed this addon. You would think Asus could fix/perfect this, its their software.

It's the holy grail, for what I would like it for; robust connections that find the strongest node and stay there.

But it isn't all ASUS fault to be fair, if cheap IoT device manufacturers have a wibbly-wobbly wifi stack, fixed thresholds that allow weak connections, ASUS can't cater for those AND the decent ones at the same time.

 

[JB_1366]

I forgot to mention, it also puts an entry into syslog, for those who cant or dont want to check their usb_path.

 

[scootertramp]

Must be funk free today. Updated to 1.5.2 using amtm u. Went into Wireless Report with wr and
could see option 5.

 

[JB_1366]

Must be funk free today. Updated to 1.5.2 using amtm u. Went into Wireless Report with wr and
could see option 5.

@jksmurf needs to upgrade his AOL

 

[scootertramp]

Cool. I like the syslog functionally.
<12>1 2026-04-21T12:01:53-04:00 rt-be88u Wireless - - [meta sequenceId="1155"] Report: [XT8DOWN] Kicking 16:67:22:16:E9:71 on wl1.1 (-71 dBm

 

[jksmurf]

Cool. I like the syslog functionally.
<12>1 2026-04-21T12:01:53-04:00 rt-be88u Wireless - - [meta sequenceId="1155"] Report: [XT8DOWN] Kicking 16:67:22:16:E9:71 on wl1.1 (-71 dBm

Did it move to a better node and stay there?

 

[scootertramp]

Did it move to a better node and stay there?

No It wasn't likely to move . I still have that unit bound to the first floor router. I just wanted to see what happens knowing it
will drop from mid forties to around 72 when I moved it up to the second floor. What did happen is it switched from 5G
to 2.4G with a rssi of around mid fifties. When I brought it back to the first floor it switched back to 5G after some time.
At some point I need to play around again with the couple of units that can be moved around (phone,laptop and tablet).

 

[aru]

I noticed something curious in the WebGUI table: the row for my "Cordless vacuum cleaner" (connected to a node) is occasionally blinking/flashing.

Here is my current environment:

Router/Nodes: GT-AX6000 (Primary) + GT-AX6000 (Nodes)

Script Version: v1.5.2

Device RSSI: -50 dBm (Stable)

Device Uptime: 04d 17h

I’ve attached a screenshot for your reference. Does the blinking indicate a specific event, such as a recent roam, a change in RX/TX rates, or perhaps a signal threshold alert?

 

[jksmurf]

I noticed something curious in the WebGUI table: the row for my "Cordless vacuum cleaner" (connected to a node) is occasionally blinking/flashing.
I’ve attached a screenshot for your reference. Does the blinking indicate a specific event, such as a recent roam, a change in RX/TX rates, or perhaps a signal threshold alert?

Yes (see changelog in link below); however 4 days of uptime does not sound like a "recent joiner". I am not sure how long recent joiners pulse for... maybe if you click refresh it will mark it as "Ah, I know you now..."

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

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

www.snbforums.com

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.

 

[scootertramp]

Yes (see changelog in link below); however 4 days of uptime does not sound like a "recent joiner". I am not sure how long recent joiners pulse for... maybe if you click refresh it will mark it as "Ah, I know you now..."

When I tested that after the update my new joiner only pulsed until the next refresh.