Skip to content

Releases

WiFi Insight 2.1.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 18:22
51e2eec

Gentler scanning on routers that limit one-channel scans or check for radar in the background, a repair that keeps nearly everything still readable, and a page that waits while its tab is hidden.

  • repair keeps much more of a damaged database. It copied with sqlite3's .dump, which reads a table from the start up to the first damaged page, then from the end back to the last one, and loses everything between: with two damaged pages in a day of samples, 3660 of 5760 were kept. The firmware's sqlite3 3.25.3 (Merlin 386.1 to 3004.388.5) also reads a damaged page differently from one run to the next, and now and then kept only the rows before the damage (365 of 5760 in a test). Now each table is copied in chunks of 100 rows, and a chunk that fails is read again row by row, so only the rows on damaged pages are lost (5550 in the first case, 5701 every time in the second). If sqlite3 itself crashes on a damaged page, the copy keeps everything before it and carries on after it, and a damaged end of a table that reads as a nonsense row number no longer sends the copy through billions of empty rows. A database nothing can be read from is left as it is.
  • repair never writes through a link. It made the new copy at a fixed name in the data folder (wifiinsight.db.new), on a drive others may be able to write to. Someone able to put a link there while it ran could have had it create a file elsewhere on the router instead, as root, with rows from the damaged database. The copy is now made in a folder of its own, created just then under a name nobody can guess, and moved into place.
  • Gentler one-channel scans on drivers with a cool-down (thanks to Squall Leonhart for measuring it): an RT-AX88U takes a single-channel scan only every 10.2 s, however often it's asked. WiFi Insight was asking every 2 s until it did, so most requests were refused. Now it learns how long the driver needs between them and waits that out: about one request in two is refused once, instead of four or five for every channel, and no channel is skipped. Spread-out scans are at least 20 s apart (they could be a few seconds apart within a minute), or longer if the driver needs it, coming back down a second at a time once it doesn't.
  • Background radar checks are left alone. With zero-wait DFS, acsd can have a 5 GHz radio listen to another channel for radar before moving there, for a minute (ten on weather-radar channels), and the driver refuses scans meanwhile. A scan now waits up to 90 s for the check to end (sampling carries on), or leaves that band for the next scan, and spread-out scans skip that minute. Such a refusal is no longer taken for a driver that refuses full scans, which used to switch the band to one channel at a time. debug shows the radio's check status (wl dfs_ap_move).
  • Scan now isn't held up by spread-out scans. On routers that refuse full 5 GHz scans, a spread-out scan kept the radio for half a minute or more, and Scan now waited for it without a word to the page, which said after 15 s that the router didn't start the scan. Spread-out scans now let go of the radio between channels, so Scan now starts within seconds, and the page knows at once that it's under way; if another scan really does keep it waiting for over a minute, the page says so.
  • The page doesn't redraw in a hidden tab (thanks to Squall Leonhart): while the tab is in the background or the window is minimised, the charts aren't redrawn and the data isn't refreshed. When you come back, the page fetches anything it skipped and then redraws, so the data is as fresh as with the tab open and older figures never flash up meanwhile. In Firefox, charts drawn in the background could stay blank until hovered.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/2.1.0/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 2.0.0...2.1.0

WiFi Insight 2.0.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 12:36
025fe08

Entware is no longer needed, routers with two radios on one band (or four radios) are supported, and the history database is checked before every use. With these changes the history moves to a wifiinsight folder on the USB drive when you update (a rename on the same drive: nothing is copied), hence the new major version.

  • Entware isn't needed any more. WiFi Insight uses the firmware's own sqlite3 (every Merlin from 386.1 has one with what it needs: 3.25.3, or 3.42.0 from 3004.388.6), and Entware's only where the firmware has none. The history goes in a wifiinsight folder on the USB drive itself (/tmp/mnt/<drive>/wifiinsight, the drive Entware is on if you have it), as Skynet keeps its data; with several drives and no Entware, the installer asks which. An existing install moves its history there from Entware's /opt/var/lib/wifiinsight when you update: a rename on the same drive, so it's the same file and nothing is copied, with sampling and scans held off meanwhile; a link is left at the old path. The history is never kept in RAM: if the drive isn't mounted, nothing is written until it is. wifiinsight.sh migrate does the move on its own, and history kept by an earlier uninstall --keep-data is picked up by the next install and moved the same way.
  • Routers with two radios on one band, or four radios. The GT-AX11000, GT-AX11000 Pro and ZenWiFi Pro XT12 (two 5 GHz radios), the GT-AXE16000 (two 5 GHz, a 6 GHz and a 2.4 GHz radio) and the GT-BE98 Pro (a 5 GHz, two 6 GHz and a 2.4 GHz radio) used to be refused by the check: their two radios on one band would have written over each other, and on the four-radio routers the 2.4 GHz radio wasn't read at all. Now each radio is kept apart, with its own button, history, scans and results, named as on the router's own Wireless pages: 5 GHz-1 and 5 GHz-2, or 6 GHz-1 and 6 GHz-2. Routers with one radio per band keep their history as it was. The layouts come from the Asuswrt-Merlin source; they haven't run on these routers yet, so a report from one is welcome.
  • The history database can't be turned against the router. It lives on the USB drive, which a guest Samba or anonymous FTP share, or anyone with the drive in hand, may be able to write to. A database someone put there with an extra table, trigger or view could have made sqlite3 write files as root (a CHECK constraint calling writefile() does, even on sqlite 3.42.0). Now every sqlite3 run checks first that the database holds only what WiFi Insight creates, and stops if it doesn't; the syslog and status say so, and repair won't touch it. The page also treats its numbers as numbers, so nothing from the database can add markup to it, and WiFi Insight never writes through a link left in its folder.
  • One-channel scans are spread out, as a fallback only. On routers that refuse full 5 GHz scans, 1.3.0 scanned the band one channel at a time in a burst of up to two and a half minutes at every scheduled scan. A full scan is still always tried first, and the first refusal still gets that burst. After that, each scheduled scan starts a sweep spread over about a third of the scan interval instead (10 minutes with 30-minute scans: 2 channels a minute on a 19-channel band, at most 3), then rests until the next one. It skips a minute while your own Wi-Fi traffic is high, but not for longer than the scan interval, and never runs in quiet hours. Each channel is one short trip off your channel rather than many in a row. Scheduled scans retry a full scan every 6 hours, and the spreading stops as soon as one works or the router moves to another channel. Routers whose full scans work never do any of this. Scan now still scans the whole band at once. A new cron job, wifiinsight_trickle, runs it.
  • When your router refuses 5 GHz scans on a DFS channel, the page says what avoids it. Some routers refuse full 5 GHz scans while on a DFS channel; many don't (an RT-AX86U in Europe scans them fine). Only when your router's scans were refused, or had to go one channel at a time, while it's on a DFS channel, the Spectrum, Site Survey and Channel Statistics now add that a channel outside 52–144 avoids it (in Wireless → General, un-tick "Enable 160 MHz" and "Auto select channel including DFS channels"), and what that costs. Thanks to SashaSolitaire for finding it!
  • Radar lines are read in a moment. When a new radar detection appeared in the syslog, WiFi Insight read every radar line in it again, starting about a dozen small programs per line: on a router with many detections that kept it busy for a minute or two, at low priority. Now it's one pass (1800 lines: 1 second instead of 2 minutes), with the same times and radios as before.
  • 320 MHz on 6 GHz is read correctly. On Wi-Fi 7 routers (RT-BE96U, RT-BE92U, GT-BE19000AI, GT-BE98 Pro), a 6 GHz radio at 320 MHz showed as 160 MHz, drawn around the wrong channel.
  • Hidden networks from your own devices count as yours. An AiMesh node's hidden backhaul or a Wi-Fi 7 router's extra links have no name, so they counted as neighbours and as interference. A hidden network whose address matches one of your named networks' in all but the first byte and the last 4 bits, which only the same device shares, now counts as yours.
  • A warning when the history drive has no journal. On ext2, FAT, exFAT, NTFS, or ext4 made without a journal (amtm offers that), a power cut while the drive is writing can damage the database, as happened on a GT-AX6000. check, status, debug and the Settings tab now name the drive's filesystem and say so, and the damaged-database warning mentions it. ext3/ext4 with a journal are fine.
  • An old copy hands over to the installed script. The install command downloads the script to /tmp/wifiinsight.sh, and that copy stayed there until a reboot: running it later (sh /tmp/wifiinsight.sh scan, say) ran the old version's code, which made a 1.3.0 router look like 1.2.0. Now install removes that copy when it's done, and a copy whose version differs from the installed one says so and runs the installed script instead (except for install, update, uninstall, check and version).
  • Scan now also refreshes the channel tile, which could show the old channel for up to a minute after a channel change.
  • If you go back to an earlier version, its cron jobs don't include wifiinsight_trickle: a reboot removes it, or run cru d wifiinsight_trickle.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/2.0.0/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.3.0...2.0.0

WiFi Insight 1.3.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 09:13
0d1fa9c
  • Scans that cover only part of the band are stored as such. A scan taken one channel at a time, or one the driver stopped early, used to be saved as if every channel had been scanned, so the channels it missed showed up as empty and quiet, and Quietest options could suggest them. Now only the channels a scan covered are stored. Where the latest scans didn't cover a channel, Load per channel and Quietest options use the newest scan within the previous 6 hours that did, and Site Survey and Networks per channel keep the networks it heard there. The page says when it does.
  • One channel at a time, without skipping channels. On routers that take a single-channel scan only every so often, WiFi Insight now waits on each channel until the driver takes it, instead of moving on after 20 seconds, so no channel is left out. It stops when nothing has been taken for a minute, or after 150 seconds, and the next scan carries on from there. Once the driver has refused a full scan on a channel, WiFi Insight tries a full scan just once on later scans there, not for 20 seconds, and gives it the full 20 seconds again every 6 hours. Sampling carries on during one-channel scans.
  • Quiet channels count as scanned. A channel can give exactly the same figures twice when nothing is on it, which looked like a channel the scan never reached: its figures weren't stored, and at the end of the band it set off a needless second scan. Now a channel where the scan heard a network counts as reached too.
  • repair runs the full check. It used SQLite's quick check, which doesn't compare indexes with their tables, so some damage passed as fine. It now runs the full integrity check (a minute or so on a large database).
  • Safer weekly compaction. The weekly VACUUM rewrites the whole database, the riskiest write if the power goes. It now runs only when a quarter or more of the file is free space, and keeps its temporary copy on the USB drive instead of in the router's memory.
  • Guest networks on more slots (3006.102's Guest Network Pro) are recognised as yours.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.3.0/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.2.1...1.3.0

WiFi Insight 1.2.1

Choose a tag to compare

@github-actions github-actions released this 12 Nov 08:35
aa85145
  • 5 GHz scans on routers that refuse a full scan. On a DFS channel, some drivers refuse every full 5 GHz scan ("Scan Rejected"), so the Spectrum, Site Survey and Channel Statistics stayed empty on 5 GHz. Some of them still take one channel at a time: an RT-BE88U took every single-channel scan. WiFi Insight now falls back to that when the full scan is refused: one channel after another, each retried for up to 20 seconds, giving up after three refused in a row or 150 seconds. Where the driver only takes one now and then, the next scan carries on where this one stopped, so the band fills in over a few scans. scan, Scan now and the syslog say so, for example "one channel at a time (full scan refused: wl said "Scan Rejected" for 20 s)". Routers whose full scans work aren't affected. Thanks to SashaSolitaire, EmeraldDeer and ColDen for the tests!
  • When scans fail, the page says why. The Spectrum, Site Survey and Channel Statistics said "No scans yet" even when scans ran and the radio refused them. They now say what happened to the band's last scan, quoting the driver, and on 5 GHz that some routers refuse scans while on a DFS channel. When older scans are shown, the Spectrum subtitle mentions a failed scan after them.
  • A damaged database is reported, and repair fixes it. After a power cut, a database on a USB drive can be damaged ("database disk image is malformed"), and charts get gaps or stop updating. WiFi Insight now notices, logs it once, and says so on the page and at the end of status. wifiinsight.sh repair rebuilds the database from everything still readable, with sampling and scans paused meanwhile, and keeps the damaged copy next to it (wifiinsight.db.bad). On a sound database it changes nothing. Thanks to ColDen for the report!
  • Networks per channel shows Yours only when it heard other access points of yours (an AiMesh node, say). A router doesn't hear its own network when it scans, so without nodes the legend said Yours with nothing to show; the subtitle now explains that the shaded area is the router's channel.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.2.1/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.2.0...1.2.1

WiFi Insight 1.2.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 19:09
eeba486
  • Measured spectrum. During every neighbour scan the radio also measures each channel it visits: airtime used by other networks, non-Wi-Fi energy (microwaves, baby monitors, Bluetooth…), energy it couldn't decode, and the noise floor. WiFi Insight now saves those figures, and the Spectrum heatmap, Load per channel and the quietest-channel suggestions use them instead of an estimate built from the networks heard. Tick Others Wi-Fi, Non-Wi-Fi and Unclassified to choose what counts, or switch to Estimated for the old view. Channel Statistics adds a noise floor for every channel. Figures are stored only for the channels a scan actually reached (the driver keeps older figures for the rest). The figures start with the first scan after updating (press Scan now to start sooner), and the page says so until then. Routers whose driver doesn't report per-channel figures keep the estimate. Tested on an RT-AX86U (3004.388); the GT-AX6000 (3006.102) reports the same figures, and WiFi Insight reads them too.
  • Complete scans on busy routers. With traffic on the router's channel, the driver can stop a 5 GHz scan partway: an RT-AX86U reached channels 36–104 of 36–140 on every daytime scan, so networks and figures on the rest of the band were missing. WiFi Insight now notices and scans the remaining channels right away (one more short Wi-Fi hiccup, only when it happens). scan, Scan now and the syslog then say, for example, "stopped at 104 and finished with a second scan".
  • Weather-radar channels marked. Channels 120, 124 and 128 (5600–5650 MHz) are shared with weather radars. Quietest options, the channel axes of the Spectrum, the Signal map and the Channel Statistics charts, the tooltips and the Networks table mark them, and wider blocks that include them, as DFS · weather radar, in the 135 countries and territories that allow Wi-Fi there (from the router's country code). When a block without them is about as quiet, Quietest options suggests that one instead. A note under Quietest options explains the radar check: before using a DFS channel the router listens for radar for 1 minute, or 10 minutes on the weather-radar channels in Europe and other countries on European rules.
  • Fixed: routers with a 6 GHz radio were refused with "This router has two 5 GHz radios" (GT-AXE11000, RT-BE92U, RT-BE96U, GT-BE19000AI): the 6 GHz band code was read as 5 GHz. All three bands are read correctly now, including 320 MHz channels on 6 GHz, and Channel Statistics suggests the quietest 40 to 320 MHz blocks there. Thanks to BobWadd for the RT-BE96U report! Routers with two radios on the same band (GT-AX11000, ZenWiFi Pro XT12) are still refused for now.
  • A menu for the terminal, ready for amtm. Run /jffs/addons/wifiinsight/wifiinsight.sh with no arguments for a menu: status, scan now, collection (on, scans paused or off), update, reinstall, debug report, amtm updates on or off, and uninstall (it asks first). amtm opens the same menu.
  • amtm can update WiFi Insight (amtmupdate) along with your other scripts. It installs the latest release, prints two lines and logs the details to /tmp/wifiinsight/amtmupdate.log. To keep amtm from updating it, choose Turn amtm updates off in the menu (or set AMTM_UPDATE=off in the config); update still works.
  • Try unreleased changes: wifiinsight.sh update dev installs the newest code on main (update dev <branch> for another branch of this repository; pull requests from forks are refused), keeping your settings and history; menu option 8 does the same. status, debug and the page's footer say when a development version is installed. update and amtm only ever install releases, and take a development version back to the latest release.
  • New command: wifiinsight.sh collection on|paused|off, the same as Settings → Collection on the page.
  • Updating no longer runs an extra neighbour scan when you already have history, so update finishes sooner without a Wi-Fi hiccup.
  • The page: card descriptions sit on one line under the title, the Spectrum and Load per channel subtitles are shorter, the footer is just the status line, and DFS and radar are only mentioned on 5 GHz (2.4 and 6 GHz have no DFS channels). scan and the syslog say how many channels were measured, and debug prints the radio's country code.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.2.0/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.1.0...1.2.0

WiFi Insight 1.1.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 07:42
60a314c
  • Quiet hours. Settings → Quiet hours: mark the half hours of the week when the router shouldn't run its scheduled neighbour scans, so there's no Wi-Fi hiccup while you're gaming, streaming or on a call. Click or drag on the week grid, or start from a preset (evenings, work hours, weekends). Sampling carries on, since it doesn't touch Wi-Fi, and Scan now still works. Times are the router's local time. Thanks to jksmurf for the idea!
  • Collection: On, Scans paused or Off. Scans paused keeps sampling but runs no scheduled scans until you switch back. Off stops sampling and scanning without uninstalling: the page, settings and history stay as they are.
  • Insight shows when it's quiet ("Quiet until 20:00" next to Scan now, a note at the top and a marked row on the spectrum), and when scans are paused or collection is off.
  • 5 GHz scans on routers with Merlin 3006.102 (GT-AX6000, RT-BE88U and other Wi-Fi 7 models): the Spectrum, Site Survey and Channel Statistics stayed empty on 5 GHz while 2.4 GHz worked. WiFi Insight gave each scan 9 seconds, and a 5 GHz scan on these drivers can take longer. It now waits for the driver to finish: up to 20 seconds on 2.4 GHz and 45 seconds on 5 and 6 GHz, and up to 20 seconds more when the radio is busy with another scan. Thanks to ColDen and AvalonOC for the reports!
  • When a band's scan fails, Scan now says why, quoting the driver (for example: 5 GHz: no results, wl said "Not Ready" for 45 s), and so do the syslog and wifiinsight.sh scan, which now prints each band's result.
  • status and debug show the collection mode and the quiet hours, and status says when it's quiet now.
  • The config file has two new settings, COLLECTION and QUIET, added with their defaults when you update. See the README.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.1.0/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.0.11...1.1.0

WiFi Insight 1.0.11

Choose a tag to compare

@github-actions github-actions released this 06 Nov 08:37
32007e8
  • Routers on Merlin 3006.102 (the GT-AX6000, RT-AX86U Pro, RT-AX88U Pro and the Wi-Fi 7 models): their newer driver prints airtime statistics in a newer layout (version: 4, channels such as 100/80 instead of hex codes, an extra busy column, and on Wi-Fi 7 models a chspec header). On the RT-BE88U the router check refused it ("No radio provides the airtime statistics"); on the GT-AX6000 the check passed, but no samples were recorded, so the charts stayed empty. WiFi Insight now reads every layout. Thanks to the RT-BE88U and GT-AX6000 owners who sent their output!
  • The router check now reads a row of airtime statistics exactly as sampling does, so a layout WiFi Insight can't read is reported at install instead of showing up as empty charts. When the driver answers with an error, the check quotes it.
  • update and the install command now get the latest release instead of the newest code on GitHub, so unreleased changes never reach your router. update also won't replace a newer version with an older release unless you use update force.
  • The install command in the README now downloads from the latest release: https://github.com/IfSugar/wifiinsight/releases/latest/download/wifiinsight.sh.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.0.11/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.0.10...1.0.11

WiFi Insight 1.0.10

Choose a tag to compare

@github-actions github-actions released this 05 Nov 07:42
8b0d59d
  • wifiinsight.sh debug is now a complete report for bug reports and router reports. It starts with the WiFi Insight version, router model, firmware, BusyBox and sqlite3 versions and Smart Connect, and covers every radio, including a fourth one, with its band type and driver version. It still prints no network names, MAC addresses or IP addresses, and works without installing (sh /tmp/wifiinsight.sh debug).
  • New issue forms for bug reports, install or setup problems, router reports and feature requests, plus a security policy for reporting problems privately.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.0.10/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.0.9...1.0.10

WiFi Insight 1.0.9

Choose a tag to compare

@github-actions github-actions released this 04 Nov 23:41
259dd84
  • Fixed: charts went empty after about 9 hours of history. The Insight and Troubleshooting charts and the tiles showed "No samples in this range yet", and update printed [: Argument list too long. On Merlin, the shell can hand at most 128 KB to some of the commands the script uses, and a day of samples is about 350 KB, so the data was dropped from the file the page reads. The script now writes the data files without going through that limit. Your history was never lost: once you update, the charts fill straight away.
  • Fixed the same limit for the Spectrum heatmap, which would have gone empty after about three days of scans, and for radar events in a very long syslog, which were no longer picked up.
  • The router check showed a negative number of MB free for a USB drive with more than 2 TB free, because Merlin's shell arithmetic is 32-bit. The check itself was right; only the number was wrong.
  • Releases are now tested on a shell set up like Merlin's, with only the BusyBox commands Merlin includes, using a full day of samples, a week of scans and a long radar log. A command Merlin lacks, or data that's too big for it, now fails the release instead of breaking on routers.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.0.9/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.0.8...1.0.9

WiFi Insight 1.0.8

Choose a tag to compare

@github-actions github-actions released this 04 Nov 22:10
813c814
  • The addon no longer keeps user1.asp free. It takes the first free addon page slot, skips slots other addons already use, and keeps its slot across reboots and updates. The RESERVED_PAGES setting is gone; an old line for it in your config is ignored.
  • The router check now refuses routers with two radios on the same band, such as 5 GHz-1 and 5 GHz-2 on a GT-AX11000, and routers with four radios. WiFi Insight keeps history per band, so those radios would overwrite each other's data. Support for them is planned. Dual-band routers and 2.4 + 5 + 6 GHz tri-band routers pass as before.

Install or update

Over SSH on the router:

curl -fsL --retry 3 "https://raw.githubusercontent.com/IfSugar/wifiinsight/1.0.8/wifiinsight.sh" -o /tmp/wifiinsight.sh && sh /tmp/wifiinsight.sh install

Already installed? Run /jffs/addons/wifiinsight/wifiinsight.sh update. Your settings and history are kept.

Full diff: 1.0.7...1.0.8