Wireless Report for AIMesh v1.1.0 - Mar 13, 2026

[JB_1366]

As long as your using it to cross reference specific device roles you wish to target as I described above, you'll be fine going forwards. It should exclude devices like media bridges once correctly implemented.

yes, anything other than >2, ignored

 

[ExtremeFiretop]

yes, anything other than 2, ignored

Happy to help where I can. So with a target value of 2, your script will only detect AiMesh nodes, and not APs/repeaters. If the script is designed to work on APs/Repeaters, than you should also allow values of 3.

Maybe something to test at some point? Unless of course you already know how it behaves on those devices. For our script we only cared about AiMesh devices, so we strictly look for value 2.

 

[visortgw]

v1.0.6-install option for °F or °C
@visortgw - only 1 node needs to authenticate for install. let me know if it worked.

​

@JB_1366 : It continues to prompt for password of non-Merlin AiMesh node after confirming installation complete:

==================================================
              WIRELESS REPORT AIMESH             
==================================================
 STATUS: [Ready] Latest available is v1.0.6
==================================================

  (1)  Install Wireless Report
  (2)  Uninstall Wireless Report
  (3)  Check/Update Latest Script
  (4)  Temperature Unit: °F(def) or °C
  (e)  Exit

==================================================
 Selection: 3
[!] Wireless Report is not installed.
 Would you like to install it now? (y/n): y
[*] Checking for USB Storage...
[+] USB Found: Using /tmp/mnt/TheS1RsUSB/gen_report for history.
[*] Verifying Passwordless SSH Environment...
[*] Testing Passwordless SSH to Node (192.168.222.254) on port 22022... AUTHENTICATED
[*] Testing Passwordless SSH to Node (192.168.222.253) on port 22022... AUTHENTICATED
[*] Testing Passwordless SSH to Node (192.168.222.250) on port 22022... AUTHENTICATED
[*] Testing Passwordless SSH to Node (192.168.222.252) on port 22022... FAILED
[*] Processing Wireless Report Files...
[*] Mounting Wireless Report TAB to Wireless menu...

SUCCESS: Installation complete!

Press [Enter] to [email protected]'s password: [email protected]'s password:

 

[JB_1366]

@JB_1366 : It continues to prompt for password of non-Merlin AiMesh node after confirming installation complete:

==================================================
              WIRELESS REPORT AIMESH            
==================================================
 STATUS: [Ready] Latest available is v1.0.6
==================================================

  (1)  Install Wireless Report
  (2)  Uninstall Wireless Report
  (3)  Check/Update Latest Script
  (4)  Temperature Unit: °F(def) or °C
  (e)  Exit

==================================================
 Selection: 3
[!] Wireless Report is not installed.
 Would you like to install it now? (y/n): y
[*] Checking for USB Storage...
[+] USB Found: Using /tmp/mnt/TheS1RsUSB/gen_report for history.
[*] Verifying Passwordless SSH Environment...
[*] Testing Passwordless SSH to Node (192.168.222.254) on port 22022... AUTHENTICATED
[*] Testing Passwordless SSH to Node (192.168.222.253) on port 22022... AUTHENTICATED
[*] Testing Passwordless SSH to Node (192.168.222.250) on port 22022... AUTHENTICATED
[*] Testing Passwordless SSH to Node (192.168.222.252) on port 22022... FAILED
[*] Processing Wireless Report Files...
[*] Mounting Wireless Report TAB to Wireless menu...

SUCCESS: Installation complete!

Press [Enter] to [email protected]'s password: [email protected]'s password:

did it still install?

 

[visortgw]

did it still install?

Now that I checked further, yes it did! Thanks.

 

[JB_1366]

Now that I checked further, yes it did! Thanks.

v1.0.7- fix install

 

[visortgw]

Absolutely beautiful! Question: Is there anything that you can do to keep everything to one line in the side by side comparison? It appears that those "phantom" SSIDs are causing it to go to two lines for the primary router.

 

[jksmurf]

Absolutely beautiful!

It’s good isn’t it !

If you get a chance have a wee look at the suggestions I made here (edited a few times), a few to do with screen real estate, see if there’s anything you (or anyome else think is a good idea) consensus wise.

At the end of the day it’s @JB_1366 baby and the improvements are more cosmetic than functional (deg C to F already addressed thank you), but I think it would enhance a great little Addon.

 

[visortgw]

Absolutely beautiful! Question: Is there anything that you can do to keep everything to one line in the side by side comparison? It appears that those "phantom" SSIDs are causing it to go to two lines for the primary router. View attachment 70714
View attachment 70715

In looking at the data more, I see some inconsistencies between SSID and BAND:

1. Subnet 222 (primary network) should be either 5 or 6 GHz — 2.4 GHz is enabled, but nothing connects using it at the present time.
2. Subnet 52 (GetYourOwnDarnInternet) should be 2.4 GHz only.
3. Subnet 53 (Searching...) should be 2.4 GHz only.
4. Subnet 54 (TheS1RsGuests) should be 5 GHz only.

 

[JB_1366]

In looking at the data more, I see some inconsistencies between SSID and BAND:

1. Subnet 222 (primary network) should be either 5 or 6 GHz — 2.4 GHz is enabled, but nothing connects using it at the present time.
2. Subnet 52 (GetYourOwnDarnInternet) should be 2.4 GHz only.
3. Subnet 53 (Searching...) should be 2.4 GHz only.
4. Subnet 54 (TheS1RsGuests) should be 5 GHz only.

looks like you need to reinstall, node titles are wrong, AI made some boo boos when we were fixing schmit, if you click on ssid, its toggled with iface, that will show wl0.1 etc, to check if 2.4g is wrong.. ip/mac-add is also a toggle. I thought i had filtered out those long hex ssids.will look into it.

v1.0.8-fix hex/backhaul on ssid scans

 

[visortgw]

looks like you need to reinstall, node titles are wrong, AI made some boo boos when we were fixing schmit, if you click on ssid, its toggled with iface, that will show wl0.1 etc, to check if 2.4g is wrong.. ip/mac-add is also a toggle. I thought i had filtered out those long hex ssids.will look into it.

Thanks for your quick responses. Reinstalling (uninstall followed by install) doesn't change anything. Bands still are showing impossible values based upon configuration.

 

[jksmurf]

Hmm ok so I’ve got a wee bit of a different issue devices wise, which I didn’t notice before as my remote site only had IoTs connected at the time.

Both sites on 1.0.8 but I’m not seeing my at least 9 devices currently connected to the main network on my local system. Will check on my remote later when I know some folks have connected.

Note sure how it checks the Wireless interface i.e. wl0.1, wl1.1 etc but I noticed when I was setting up my crude version of this app that oddly, they were either different for different node models or the interface sent to those two models was different.

 

[Martinski]

In looking at the data more, I see some inconsistencies between SSID and BAND:

1. Subnet 222 (primary network) should be either 5 or 6 GHz — 2.4 GHz is enabled, but nothing connects using it at the present time.
2. Subnet 52 (GetYourOwnDarnInternet) should be 2.4 GHz only.
3. Subnet 53 (Searching...) should be 2.4 GHz only.
4. Subnet 54 (TheS1RsGuests) should be 5 GHz only.

The GT-BE98 Pro is a quad-band router, and the virtual interfaces for the wireless radios don't follow the standard "pattern" used for dual-band and tri-band routers:

2.4 GHz	wl3.x
5 GHz-1	wl0.x
6 GHz-1	wl1.x
6 GHz-2	wl2.x

Note the 2.4 GHz maps to wl3.x interfaces, *not* to wl0.x as usually expected.
This is probably the reason the script is reporting the wrong band associated with each wireless subnet, since it's mixing up the 2.4 GHz, 5 GHz, and 6 GHz interfaces.

Just my 2 cents.

 

[jksmurf]

This is probably the reason the script is reporting the wrong band associated with each wireless subnet, since it's mixing up the 2.4 GHz, 5 GHz, and 6 GHz interfaces.

I’d imagine also the reason why it fetches devices on one node but not in two others in my remote network. Thanks @Martinski.

Going to be interesting to see if the script can interrogate a full set of known interfaces (does such an animal exist?) and if they don’t exist move on until it gets a set that do.

 

[Martinski]

I’d imagine also the reason why it fetches devices on one node but not in two others in my remote network. Thanks @Martinski.

Yes, it's very likely. If the script is associating each wireless network with the wrong virtual interface, all bets are off.

Going to be interesting to see if the script can interrogate a full set of known interfaces (does such an animal exist?) and if they don’t exist move on until it gets a set that do.

The script has to map each wireless band to the correct virtual interface based on the known router model. That's what I ended up doing in YazFi and scMerlin when the tri-band and quad-band routers started showing up.

A simple search for "GT-BE98_PRO" in the YazFi or scMerlin script will point you to the code.

 

[JB_1366]

I spoofed in node names to test logic, seems correct, as i only have wl0 & wl1, no wl3 to test 2.4g.

v1.0.9-updated tri-quad band logic, thanks @Martinski.

 

[visortgw]

View attachment 70721

I spoofed in node names to test logic, seems correct, as i only have wl0 & wl1, no wl3 to test 2.4g.

v1.0.9-updated tri-quad band logic, thanks @Martinski.

Appears to work great now for GT-BE98 Pro, GT-AX6000, and GT-AXE16000:

 

[JGrana]

I uninstalled the older version. Then, reinstalled v1.1.0.
The install correctly did NOT include that non-node AX58u.
I am not seeing any node information after the main router screen. In fact, scrolling just shows the main routers information again (although the devices are in a different order. On the main router first screen, I can toggle between IP and MAC. On the repeated next screen it won't toggle.

 

[jksmurf]

I’m seeing some but still not seeing results fot all active interfaces on my various routers/nodes in either network. I think the reference @Martinski gave you should have a master list but FYI here are mine, for my limited set.

 

[visortgw]

And v1.1.0 apparently adds hostnames for AiMesh nodes without the need for YazDHCP! Awesome work, @JB_1366!