What's new

Wireless Report v1.3.7 [2026-Apr-11] - WebGUI Table of all connected Client Devices showing RSSI (available in AMTM!)

JB_1366

Regular Contributor
WIRELESS REPORT v1.3.7
Released April 11, 2026

WHAT IS IT FOR: WIRELESS REPORT gives you an overall snapshot of your wireless network in a sortable/graphical table, including signal strength (RSSI) of connected devices on nodes, details which the ASUS Network Map lacks. The report script installs a tab at the end of the Wireless menu in the ASUS WebGUI, where you can click column headers to sort/view data associated with connected devices. Several of the columns are designed for alternate viewing options, e.g. MAC address / IP address and SSID / Wireless INTERFACE.

WHY: The reason I created the script was because the ASUS WebGUI does not show AiMesh node information. The absence of the RSSI parameter on nodes was actually the main reason I started this addon. It is also useful to see all wireless devices in one tab, on one table or side by side. ASUS firmware takes way too long to adjust devices to connect to the correct router/node; using the report, I can manually adjust the connectivity of client devices easier and faster.

PREREQUISITES: As one of the main reasons for using WIRELESS REPORT is to view connection details on nodes, if your system has a MAIN Router and one or more nodes, for WIRELESS REPORT to be able to access node data, you will need to install password-less SSH access to each node.

For password-less SSH access refer the steps in post #16 of this thread prior to installing WIRELESS REPORT.
As noted above, this method applies equally to nodes running stock FW or Merlin FW. Only the MAIN must be running Merlin FW.

NON-PREREQUISITES:

Whilst not an absolute, if you would like your WIRELESS REPORT tables to show pretty-looking HOSTNAMES rather than the default MAC addresses, you should consider manually assigning often used, known Clients with "Manually Assigned IP addresses" by populating your LAN DHCP reservations in the LAN, DHCP Server Tab and (if you have GNP) in the Guest Network Pro, <Selected Guest Network>, Advanced Settings, Manually Assigned IP around the DHCP lists option of the WebGUI.

As the MAIN will be running Merlin anyway, whilst you can use the Stock WebGUI for this, consider installing YazDHCP, an easier to use interface for manual assignments, that can import and export DHCP assignments and combines both MAIN and GNP manual assignments into one interface.  YazDHCP is not the subject of this addon, but can be installed via amtm (option j7).

INSTALLATION:

Installation takes two mandatory steps, followed by some optional configuration.

Step 1. Initiate the installation.

There are two ways to initiate the addon installation:

i. Via AMTM; from the amtm menu, simply select "wr".

OR

ii. Manually, via SSH, from the MAIN Router.
Code:
curl -sfL --retry 3 https://raw.githubusercontent.com/JB1366/Wireless_Report/main/wirelessreport.sh -o /tmp/wirelessreport.sh && sh /tmp/wirelessreport.sh install

Note that both methods only initiate the install screen, the installation is NOT COMPLETE at this point.

Once the install is initiated into amtm, you will be presented with the upper part of this screen, with menu items (1) to (4) and (e):

1775992475728.png


Step 2: Run the actual WR install (1). You will only need to do this once, and on subequent updates :

i.e. Select option (1). You will see:
  • A check for USB storage;
  • Status of the passwordless SSH environment you set up above as a prerequisite i.e. it will tell you if it is working correctly;
  • Processing of the Wireless Report files; and
  • A completion message, with a reference to use option (4) to set custom nicknames of your router devices
At this point WIRELESS REPORT (WR) is ready to view in the WebGUI, however I suggest you consider reviewing the optional configuration whilst still in the amtm menu.

OPTIONAL CONFIGURATION (in WR menu):

As per the screenshot above, there are two items (3) and (4) to configure.
  • Option (3) is used simply to modify your Temperature Units from F (default) to C or vice-versa; it also amends the date format to a non-US format.
  • Option (4) is used to modify the names of your Router or Node. 

    Note that the default names are the MODEL number of your device e.g. RT-AX88U_Pro or RT-AX3000. WIRELESS REPORT suffixes the default names with (MAIN) or (NODE). If you have more than one Node, the Nodes are all named on one line, with a "|" separator. The last node is then suffixed by the term (NODES). If you amend the Router/Node name using option 4, you can call it anything you wish, within a 24 character limit. The terms (MAIN) or (NODE) will be automatically appended to any name you give it. If you wish to retain the Model number, then you must type that in as part of the new name e.g.
Default:
RT-AX88U_Pro → RT-AX88U_Pro (MAIN)
RT-AX3000 → RT-AX3000 (Node)

Using Nicknames:
Master Bedroom → Master Bedroom (MAIN)
Kat's Room → Kat's Room (NODE)
RT-AX88U_Pro (MB) → RT-AX88U_Pro (MB) (MAIN)
RT-AX3000 (Kat's Room) → RT-AX3000 (Kat's Room) (Node)

1775992475735.png


VIEWING WIRELESS REPORT:

In ASUS WebGUI, simply go to Advanced Settings, Wireless, select the rightmost tab "Wireless" and click Refresh.

  • The tables will display all your connected clients, for MAIN and NODES, with HOSTNAME, IP ADDRESS (or MAC), RSSI, RX/TX, SSID (or INTERFACE), BAND and CLIENT UPTIME.
  • All columns w.e.o. IP ADDRESS and SSID are alphabetically or numerically sortable.
  • The total number of connected devices are shown; and the number connected to each Router/Node.
  • The RSSI are graded (and colour-coded) by Excellent, Good, Fair or Poor connectivity.

1775992475742.png

1775992475752.png

Viewing options include:
  • Hover over the "WIRELESS REPORT" text in the header for script version
  • A dropdown for adjusting the Auto-Refresh Interval
  • Tabular Viewing options "Stacked" (Default) showing MAIN, then (ALL) NODES; "All devices", without stacking and "Side by Side".
UPDATES:

WIRELESS REPORT can be updated either:

(a) via amtm: from amtm simply type wr, select option (1) which will install the update then press (e) to exit.
(b) via SSH: from your terminal window, issue the cmd

Code:
sh /jffs/addons/wireless_report/wirelessreport.sh install

You can also add an alias to the profile.add file in /jffs/configs/profile.add e.g.
Code:
alias wr="sh /jffs/addons/wireless_report/wirelessreport.sh install" # Allows Wireless Report install script to be run from anywhere, including root.

and issue this to restart profle.add:
Code:
source /jffs/configs/profile.add
After that you can run wr_install or whatever alias you choose, from root.

UNINSTALLATION:

To uninstall:

(a) From amtm simply run wr, select option (2), which will uninstall the files, but will take you back to the WIRELESS REPORT Install Menu. At this point, simply exit using (e).
(b) From an SSH Terminal run:
Code:
sh /jffs/addons/wireless_report/wirelessreport.sh install
(or your chosen alias)
then as per (a) select option (2), which will uninstall the WR files, but will take you back to the WIRELESS REPORT Install Menu. Again, at this point, simply exit using (e).

WIRELESS REPORT is free to use under the GNU General Public License version 3 (GPL 3.0).

This project is hosted on GitHub

If you have any questions, please feel free to post in the thread.

Instructions created by @jksmurf, most excellent job!!

CHANGELOG:
v1.3.7-minor adjustments
 
Last edited:
Github link?
 
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.
 
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.
 
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?
 
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.
 
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.
 
Last edited:
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 work, well done to 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 Smart Connect, play around with the two settings Trigger and Steering (for each band), but taking that path is like going down a rabbit hole … the cleverer devices like phones will decide themselves anyway.
 
Last edited:
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. default is manual refresh, with 30sec/1min auto refresh.
all columns are sortable, mac/ip-address, ssid/iface columns are toggleable(I had ip-address toggled), so ssid column would group all together per main/node view. default is manual refresh, w/auto refresh selectable of 30sec/1min.

Screenshot 2026-03-05 170035.png


Screenshot 2026-03-05 170336.png
 
Last edited:
I'd be interested in what I could learn about my network using your script: router, four (4) AiMesh nodes, and roughly ninety (90) clients total.
 
I'd be interested in what I could learn about my network using your script: router, four (4) AiMesh nodes, and roughly ninety (90) clients total.
You'll be scrolling for days .... :)
 
Where is the script?

The UI is beautiful indeed... for monitoring, for whoever wants to stare at router's GUI. For optimizing AiMesh manually by reconnecting and binding devices to different nodes... the idea was first used in 1878.

1772791142006.png
 
Code:
curl -sL --retry 3 https://raw.githubusercontent.com/JB1366/Wireless_Report/main/wr_install.sh -o /tmp/wr_install.sh && sh /tmp/wr_install.sh




Initial Release - passwordless-SSH to all nodes, are a prerequisite. YazDHCP for pretty Hostnames, not necessary.
 
Last edited:
Code:
curl -s -L https://raw.githubusercontent.com/JB1366/Wireless_Report/main/wr_install.sh -o /tmp/wr_install.sh && chmod +x /tmp/wr_install.sh && sh /tmp/wr_install.sh

Initial Release
Awesome, will try soon. Before I install it … thinking ahead … in case it goes pear shaped, how do I uninstall it?

Also, if folks haven’t got automatic (no intervention required) login access to nodes it will not show node data, correct? So any install notes would need to clarify this eventually I guess.
 
Last edited:
Awesome, will try soon. Before I install it … thinking ahead … in case it goes pear shaped, how do I uninstall it?
there's an uninstall, also helps if your passwordless ssh-keys are all setup, it authenticates before install. and YazDHCP for purty Hostnames
 
Last edited:
Code:
curl -s -L https://raw.githubusercontent.com/JB1366/Wireless_Report/main/wr_install.sh -o /tmp/wr_install.sh && chmod +x /tmp/wr_install.sh && sh /tmp/wr_install.sh

Initial Release
Any chance you could make the ssh port configurable?
 
passwordless is working fine per that post. Your scripts are set-up to use the default port 22.
I do not run on the default port for ssh access. Just looking to see if it could be a configuration option.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Back
Top