WS Hub 1.0.23

What changed since 1.0.22. Check logs now lives only inside WS Hub, so remembering the app name is enough. A person still starts every transmit.

This release is not published yet.

Updates

Check logs is in the app. The separate Desktop and app-menu Check logs icons are no longer created. After you start WS Hub once, leftover icons from an earlier version are removed if they started this program's checker. Other files with that name are left alone.

Check logs on this PC. In the WS Hub window, next to Open site console, Check logs compares the logs on this PC and opens the report in the browser. That works on any seat, including a PC that is not running the site server.

Check logs on the server. The Check logs button on the console's Log page still compares the logs on the site server's PC.

Station call in Setup. The DX cluster logs in with the Station call you set on Setup. If that field is blank, it uses the call from a running WSJT-X. If neither has a call, the status line says to set the station call in Setup. If the Setup call is different from a live WSJT-X, Setup shows a warning and does not change either one.

Installing from this page

Linux. Download wims-1.0.23-linux-x86_64.tar.gz and unpack it anywhere. Open the folder, open scripts, and double-click Install WS Hub. If the file manager asks once, choose Allow Launching, Execute, or Run. Then delete the download and double-click WS Hub.

Windows. Download wims-1.0.23-windows-x86_64.zip and extract it to C:\WIMS. Open C:\WIMS\scripts\windows and double-click Install-Wims.cmd. Then double-click WS Hub.

Assets

File	Use
wims-1.0.23-windows-x86_64.zip	Extract to C:\WIMS → Install-Wims.cmd, then WS Hub
wims-1.0.23-linux-x86_64.tar.gz	Unpack, open scripts, double-click Add WIMS to Desktop, then WS Hub

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

72c6d78aa3bf6ddff20b11fad2a6294cd6e1304e334072870128f08930e71011  wims-1.0.23-linux-x86_64.tar.gz
4f09aac0764cda1080cf9db1a4754e235abfda55abc467bd047c7e72de3afb87  wims-1.0.23-windows-x86_64.zip

WS Hub 1.0.22

What changed since 1.0.21. A first start on one PC now runs the site server itself when none is already on the network, including a station that only has WSJT-X. The console window also works with Ubuntu's snap Firefox. A person still starts every transmit.

Updates

A single PC just works. After a fresh install, double-click WS Hub. If no site server is already on the network, this PC starts one and opens the console at http://localhost:8787/. That includes a WSJT-X-only station, which used to hide the Site server option and look for a server on another machine. There is no built-in address of some other PC.

Several PCs on one network still share one server. If this PC already remembers a server on another host, or one is found on the LAN, that server is used and a second one is not started. Seat agents follow if the chosen server later changes.

Snap Firefox on Ubuntu. The dedicated console window now keeps its profile in a folder the snap is allowed to write (~/snap/firefox/common/…). If that window still does not stay open, the console opens in the usual browser instead. Two starts at the same moment no longer fight over the same profile.

Dock icon on Ubuntu. The WS Hub window now uses the WS Hub icon in the Ubuntu dock, not the generic Tk one. After you install this update, the first start rewrites the desktop and app-menu icons so that match works.

AP and low-confidence decodes. A decode that WSJT-X marks with an AP tag such as a2, or with a question mark when it is not sure, is still shown and its callsign is still read. The grid is taken from the message, not from the tag. A low-confidence decode is not stored as that station's confirmed grid.

Installing from this page

Linux. Download wims-1.0.22-linux-x86_64.tar.gz and unpack it anywhere. Open the folder, open scripts, and double-click Install WS Hub. If the file manager asks once, choose Allow Launching, Execute, or Run. Then delete the download and double-click WS Hub.

Windows. Download wims-1.0.22-windows-x86_64.zip and extract it to C:\WIMS. Open C:\WIMS\scripts\windows and double-click Install-Wims.cmd. Then double-click WS Hub.

Assets

File	Use
wims-1.0.22-windows-x86_64.zip	Extract to C:\WIMS → Install-Wims.cmd, then WS Hub
wims-1.0.22-linux-x86_64.tar.gz	Unpack, open scripts, double-click Add WIMS to Desktop, then WS Hub

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

c41e7fe3fd5ca2e55d6d7c834c7415ed9915fb3bc2f3686fd035358ecaf9238c  wims-1.0.22-linux-x86_64.tar.gz
ed440864f6529551c42d24ae235ff24324e9978961c032da5ff0809899ee4f9e  wims-1.0.22-windows-x86_64.zip

WS Hub 1.0.21

What changed since 1.0.20. The update button at the top of the WS Hub window now does the same job as Install this update on a Linux download, so you no longer need two buttons for one action. A person still starts every transmit.

Updates

One update action. On a Linux install in ~/.local/share/ws-hub, the button next to “Update available” is Install update (or Install 1.0.21 when that version is known). It downloads that release, checks SHA256SUMS, and replaces this copy the same way Install this update does. The previous copy is kept so Go back still works.

Git clones still pull with one click; the button is now Update WS Hub.

Windows copies that are not git clones still open the GitHub Releases page; the button is now Download update.

Install this update in the Updates list is unchanged: pick a version, including an older one, and install that.

Installing from this page

Linux. Download wims-1.0.21-linux-x86_64.tar.gz and unpack it anywhere. Open the folder, open scripts, and double-click Install WS Hub. If the file manager asks once, choose Allow Launching, Execute, or Run. Then delete the download and double-click WS Hub.

Windows. Download wims-1.0.21-windows-x86_64.zip and extract it to C:\WIMS. Open C:\WIMS\scripts\windows and double-click Install-Wims.cmd. Then double-click WS Hub.

Assets

File	Use
wims-1.0.21-windows-x86_64.zip	Extract to C:\WIMS → Install-Wims.cmd, then WS Hub
wims-1.0.21-linux-x86_64.tar.gz	Unpack, open scripts, double-click Add WIMS to Desktop, then WS Hub

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

03028be4e9eae6ece0308db6aed5bb1e5ead5cea0b0321e9703a859eacb4569d  wims-1.0.21-linux-x86_64.tar.gz
70ca34af03fd3a46681d31447ad8b253396982f7217fe875a57106425fa2b34e  wims-1.0.21-windows-x86_64.zip

WS Hub 1.0.20

What changed since 1.0.19. A Linux install from the download now knows its own build, so Restart site server no longer says the running copy is not the installed one. The call roster says when stations were heard but none are needed. A person still starts every transmit.

Restart site server

The installed copy is recognized. A download does not include git, so 1.0.19 could not tell the running server from the copy on disk and wrongly said the server came back but was not the installed copy. Each release now records its build, and Restart site server compares that. When a build cannot be identified, the window says so instead of reporting an error.

Call roster

Empty list. When no stations have been heard, the list still says no decodes yet. When stations were heard in the roster window (the current band and max age filters) but none are needed, it says how many, for example 20 decodes, none needed. If the Show menu, or the band or max age filters, hid every row, it says none match Show. Hover the line for a little more detail.

Settings folders (correction)

The console's browser profile is in ~/.local/state/wims. That folder does not hold the window position. Seat profile stays in ~/.local/share/wims. Settings stay in ~/.config/wims. Installing or updating does not touch them.

Installing from this page

Linux. Download wims-1.0.20-linux-x86_64.tar.gz and unpack it anywhere. Open the folder, open scripts, and double-click Install WS Hub. If the file manager asks once, choose Allow Launching, Execute, or Run. Then delete the download and double-click WS Hub.

Windows. Download wims-1.0.20-windows-x86_64.zip and extract it to C:\WIMS. Open C:\WIMS\scripts\windows and double-click Install-Wims.cmd. Then double-click WS Hub.

Assets

File	Use
wims-1.0.20-windows-x86_64.zip	Extract to C:\WIMS → Install-Wims.cmd, then WS Hub
wims-1.0.20-linux-x86_64.tar.gz	Unpack, open scripts, double-click Add WIMS to Desktop, then WS Hub

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

3dce090f8f6bfa3cf99c94b014e3f35228ee23f560e94c67e5b3f63f391d09aa  wims-1.0.20-linux-x86_64.tar.gz
1573f5369d4cf16adb891b9ca437f04ca696749d08e3bf89e32575d57918a4bc  wims-1.0.20-windows-x86_64.zip

WS Hub 1.0.19

What changed since 1.0.18. On Linux, Install WS Hub now puts the program in your home folder, so the download can be deleted. A person still starts every transmit.

Linux install

One place for the program. Unpack the download anywhere, Downloads is fine. Open the unpacked folder, open scripts, and double-click Install WS Hub (it was called Add WIMS to Desktop). WS Hub copies itself to ~/.local/share/ws-hub, the place Ubuntu uses for programs a person installs for themselves, and the WS Hub icon on the desktop and in the app menu starts that copy. When the message says so, delete the downloaded folder and the .tar.gz. They are not needed again.

Installing again. Doing the same with a newer download replaces the copy in ~/.local/share/ws-hub. The old copy is replaced only after the new one is fully in place, so a failed copy leaves the old one working.

Your settings stay. Settings and remembered data are not in the program folder. They live in ~/.config/wims (log choice, contest rules, cluster settings, heard grids, seats), ~/.local/share/wims (seat profile, browser profile), and ~/.local/state/wims (console window). Installing or updating does not touch them. The launcher's details log in the program's scratch folder is carried over.

A git clone stays put. If the folder is a git clone, Install WS Hub does not copy it. The icon points at the clone, as before.

Update from the window. A copy in ~/.local/share/ws-hub can now update itself. In Updates, pick the version and click Install this update. WS Hub downloads that release's Linux file, checks it against SHA256SUMS, and swaps it in. Go back returns to the copy it replaced. Windows copies that are not git clones still open the release page.

Icons

No leftover WIMS icon. Installing removes an old WIMS icon on the desktop and in the app menu when it starts WS Hub, whatever form it has: the 1.0.x icon, the oldest icon that ran python -m wims.launcher, or one whose folder is the WIMS program. Icons for other programs are left alone.

An icon that points at Downloads (from installing 1.0.18 there) is rewritten to point at ~/.local/share/ws-hub.

Installing from this page

Linux. Download wims-1.0.19-linux-x86_64.tar.gz and unpack it anywhere. Open the folder, open scripts, and double-click Install WS Hub. If the file manager asks once, choose Allow Launching, Execute, or Run. Then delete the download and double-click WS Hub.

Windows. Download wims-1.0.19-windows-x86_64.zip and extract it to C:\WIMS. Open C:\WIMS\scripts\windows and double-click Install-Wims.cmd. Then double-click WS Hub.

Assets

File	Use
wims-1.0.19-windows-x86_64.zip	Extract to C:\WIMS → Install-Wims.cmd, then WS Hub
wims-1.0.19-linux-x86_64.tar.gz	Unpack, open scripts, double-click Add WIMS to Desktop, then WS Hub

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

a39180ed4aaa80956a47e7a539c5ac83123aa93799dc65168e2326145ca5da1f  wims-1.0.19-linux-x86_64.tar.gz
0c10820dbe2429266c878f2bc200f12eabed7608b4b020c724571aa03e41ff76  wims-1.0.19-windows-x86_64.zip

WS Hub 1.0.18 (formerly WIMS)

What changed since 1.0.17. WIMS is now called WS Hub, with a new icon. Double-click WS Hub on the Desktop or in the Start menu (Linux: the app menu). A person still starts every transmit.

New name and icon

WS Hub. The Desktop icon, the Start menu entry, the Linux app menu entry, and the launcher window title say WS Hub. The icon is white WS over HUB on the same blue square, in the same style as WS Skim.

One icon, not two. The first time the updated launcher opens, it renames an existing WIMS Desktop icon to WS Hub. Adding the icon again (Linux: Add WIMS to Desktop; Windows: Add WIMS to Desktop.bat or Install-Wims.cmd) also removes the old WIMS icon and Start menu entry. If the old picture still shows after an update, log out and back in so the desktop reloads it.

Updates keep working. The GitHub project is now wa1hco/WS-Hub. GitHub forwards the old WIMS address, so the Updates list in 1.0.17 finds this version. Folder names, file names, and settings are unchanged.

Installing from this page

Linux. Download wims-1.0.18-linux-x86_64.tar.gz and unpack it. Open the folder, open scripts, and double-click Add WIMS to Desktop. Then double-click WS Hub. If the file manager asks once, choose Allow Launching, Execute, or Run.

Windows. Download wims-1.0.18-windows-x86_64.zip and extract it to C:\WIMS. Open C:\WIMS\scripts\windows and double-click Install-Wims.cmd. Then double-click WS Hub.

Operate roster

Country. A Country column shows each station's DXCC entity (Uruguay for CX4BAN), so you can read it without knowing prefixes.

One needed word. The badge that said needed names one reason: grid, state, DXCC, CQ zone, ITU zone, continent, or call. When that word is shown, the extra mult badge is hidden. Contest rows have no place word, so mult stays there.

Show menu. The needed only checkbox is a show menu: Needed, Needed and CQ, Needed and CQ or 73 (stations free to call), and All.

Approximate heading. When a station has no grid, Az DX and km use the middle of its DXCC country and show as approximate, for example ~260°. No grid square is guessed.

Remembered grid. WIMS keeps the last grid it heard for each call. A tail-end with no grid gets that square on the roster and on the record WIMS forwards, and Work fills WSJT-X's DX Grid from it. A rover square from an earlier hearing is marked grid assumed. A three-letter KG4 call counts as the United States.

Call roster rules. The contest-rules line under Call roster moved into a tooltip. Hover the heading to read it.

TX groups show only when there is something to know: an overlap or a blocked Work is never hidden. The Work and Halt status line is short (Working K1ROV/R on flex); hover it for the details.

Goals and logs

Checklist replaces WSJT-X Colors under Just operating, and adds continent and zone lines.

Worked but not confirmed. Award and checklist goals flag a place that is worked but not confirmed when a new station is heard, and skip it when that station was already worked in the goal's scope. WIMS reads the LoTW file GridTracker keeps on this PC to tell what is confirmed.

Logging a contact clears that station's mult on the roster.

Spotted (DX cluster)

Operate has a Spotted list of DX cluster spots on any band, separate from the live roster. It uses the roster's columns and the same needed word. A spot on a band with no WSJT-X running is marked QSY and scores a little lower. Checkboxes for SSB, CW, FT8, FT4, and Other filter the list by mode. A click selects the station and does not transmit.

Antennas

The seat checkbox Antennas reads rotator headings from hamlib rotctld, and Operate shows the antenna, its heading, and whether it is connected.

Launcher

• Restart site server restarts the server on this PC only. A server on another PC is left running.
• The site console window remembers its size and place on this PC.
• Linux: a new user double-clicks Add WIMS to Desktop in scripts. A missing Python or Tk is a plain message that names the package.

Assets

File	Use
wims-1.0.18-windows-x86_64.zip	Extract to C:\WIMS → Install-Wims.cmd, then WS Hub
wims-1.0.18-linux-x86_64.tar.gz	Unpack, open scripts, double-click Add WIMS to Desktop, then WS Hub

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

11cd58a84e749bc452bc1528f2714c90c773c39afa949344e5c3c3a3c9558240  wims-1.0.18-linux-x86_64.tar.gz
77c66a8472cda0522d2c5720f67e85aeeea896c2241f5fd0d2eda2f4b9b79e93  wims-1.0.18-windows-x86_64.zip

WIMS v1.0.17

WIMS 1.0.17

What changed since 1.0.16. Double-click WIMS on the Desktop or in the Start menu. A person still starts every transmit.

Launcher

One front door. The Desktop icon, the Start menu entry, scripts/start-wims.sh, and the Windows WIMS shortcut open the same window.

One launch path. Operate from that window and Start-Wims-Solo share one start: the port check, the seat reading, the network default, the log and rules, the browser, the messages, and the details log.

Updates. The list shows every version, newest first. That includes published releases and version tags that have no release page of their own, so the versions after 1.0.10 are on the list. Hover a row to read that version’s notes. The date is this PC’s local day, so a tag from late in the evening stays on that day. The row tip includes the local time. Check now looks immediately. While the window is open, WIMS also looks in the background about every three hours, and never more often than every 15 minutes. Install this update and Go back are buttons. An install runs only from Install this update.

Restart needed. The site server reports the revision it loaded (server_rev). The window compares that with the copy on this PC. When both revisions are known and they differ, Restart site server is marked Restart needed: the server is running older code than what is installed. The title line shows the launcher revision (the code this window loaded when it opened) and the server revision (the code the site server loaded at start). After an install, the Updates list says Restart server to finish the update. A server that does not report a revision is left unmarked.

Second double-click. When the window is already open, another double-click un-minimizes it, raises it, and focuses it. The site console stays as it was. If that window does not answer, WIMS says what to do next. A port that is already in use says what to do next.

Other tools and window size. The closed window ends at the Other tools… checkbox. Checking it opens the extra tools underneath: screenshots, the desktop shortcut, the details log, the site URL, the Solo lab, and role cards, including home Operate and Inhibit. The window grows to fit, up to the screen, and then those tools scroll. Unchecking returns the window to the compact height.

Log page, Log to use, and challenges

Log is its own page. It is the list of contacts WIMS checks for needed and already worked. The goal on Setup decides what counts. The log you picked stays put when the goal changes.

Log to use is that choice. The page shows the name, the path, the contact count, and the cutoff. A saved choice reloads without a restart. The goal suggests a log only when nothing is saved: a contest suggests the newest matching N1MM log; just operating, an award, or a custom list suggests the WSJT-X log. Look again finds a new contest file and leaves the chosen log chosen.

Count only since changes which contacts count as already worked. The logger’s file stays as it is.

• Whole log counts every contact.
• Start now counts contacts logged after you pick it. That cutoff is how a fresh challenge starts on the log you chose (for example, countries worked from this moment).
• This year counts contacts since January 1.

How often a station counts (once per band, and the other scopes on Setup) still applies inside that window.

When the chosen log is a WSJT-X file, WIMS reads each radio’s wsjtx_log.adi (or the one shared file, when you set one). The page says when a log is missing or unreadable. A WSJT-X log has no contest name or exchange, and the page says so when a contest goal is using that file.

Check logs on the Log page, and the Desktop Check logs icon, lead with a short summary. Show details lists contacts missing from a log. Copies of the same file — the same path, the same file on disk, or the same bytes — count as one log. The check groups by call, band, mode, and a three-minute window, so a large log finishes in about a second.

Goal on Setup is Contest, Award, Just operating, or Custom, then a second menu. DXCC, Worked All States, and VUCC use the log as the already-worked list. Just operating uses WSJT-X Colors. A checklist can add state or province, and call, each overall, per band, or per mode. County and callsign prefix show, and stay off. A contest choice saved by the older Setup menu is kept. Each control under Setup → Advanced has a short tip on hover and on the ? beside it.

N1MM tab

The N1MM tab is the list of several stations at once. It shows on every page when two or more stations are heard. With one station, or none, the tab stays off the other pages. Opening the N1MM page directly still shows the tab selected, and the station list stays on the single-station view until more than one station is heard.

Operate roster

Message. The roster keeps the text after the callsigns — a report, a sign-off (RR73 or 73), a grid, or leftover QSY or free text — and shows it in Message, just after Calling. Hover the cell for the full decode. A saved column set gains Message once. Transmit is unchanged.

Max age. The menu reads 15 sec, 30 sec, 1 min, 2 min, 3 min, 5 min, and off. The times are the same as before, labeled in seconds and minutes so “2 min” sits apart from the 2M band checkbox.

A seat you mark decode-only shows a decode badge, and Work on that row is refused. A TX-capable seat shows TX. Until you mark a seat, live instances stay TX-capable.

Fixes

• A dial that is already the real frequency stays on that band. A Flex at 28.074 MHz stays 10 m. IF-to-RF mapping turns on only for seats you mark, by rig name or N1MM station, on Setup or the seat page.
• Work and Halt can leave this PC toward the WSJT-X that sent the decode, including when both programs are on this computer. When there is no route, the message is a plain sentence.
• A decode that arrives before the first status from that copy of WSJT-X stays off the roster. It remains in Band Activity.

WIMS 1.0.10

WIMS 1.0.10 (GA)

Allow-list source packages for testers (stdlib Python).
Windows zip is tree-only until the bundled CPython+Tk runtime lands;
Install still uses/finds system Python ≥ 3.10.

Assets

File	Use
wims-1.0.10-windows-x86_64.zip	Extract to C:\\WIMS → Install-Wims.cmd
wims-1.0.10-linux-x86_64.tar.gz	Unpack → ./install.sh

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

0d9300e85e94998c38d84e6d6af19192aa10f9e2ae080f779df9dde76cb110cd  wims-1.0.10-linux-x86_64.tar.gz
ee41f3531b80db137cd8192da6bbadf0c4230991d7f399942c5dcb84b0a6a5bb  wims-1.0.10-windows-x86_64.zip

WIMS 1.0.9

WIMS 1.0.9 (GA)

Allow-list source packages for testers (stdlib Python).
Windows zip is tree-only until the bundled CPython+Tk runtime lands;
Install still uses/finds system Python ≥ 3.10.

Assets

File	Use
wims-1.0.9-windows-x86_64.zip	Extract to C:\\WIMS → Install-Wims.cmd
wims-1.0.9-linux-x86_64.tar.gz	Unpack → ./install.sh

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

90c01b2175b4806b9ad9136e1e660b0f7c0f781432d328910343c10c800d05ab  wims-1.0.9-linux-x86_64.tar.gz
1139befe4cbb60f9452cce5edfb2eb9b6286cd82dd2078b62a421acf9acd32d8  wims-1.0.9-windows-x86_64.zip

WIMS 1.0.8

WIMS 1.0.8 (GA)

Allow-list source packages for testers (stdlib Python).
Windows zip is tree-only until the bundled CPython+Tk runtime lands;
Install still uses/finds system Python ≥ 3.10.

Assets

File	Use
wims-1.0.8-windows-x86_64.zip	Extract to C:\\WIMS → Install-Wims.cmd
wims-1.0.8-linux-x86_64.tar.gz	Unpack → ./install.sh

Install

See INSTALL.md and docs/tester_quickstart.md.
Sibling digi app builds: wsjtx-inhibit Releases.

Checksums

7efd5ce31d41ae44a7c82ad1e73e74a6334dadc1302bd2e37ca3f55ce43e8eb5  wims-1.0.8-linux-x86_64.tar.gz
878822df29c1d33a7d56d753030a7b6214178e4663e280d591b8c2154c17e263  wims-1.0.8-windows-x86_64.zip