hamradiotools

Nexus 1.10.1

Released 1 September 2026. The current release is 1.24.0. Download it · Every version

<!-- Post-release work lands HERE, above the released section. A released section is immutable history: folding new entries into it claims unshipped work as shipped, which has had to be repaired on main once already. -->

Fixed

  • A popped-out waterfall no longer strands itself across a restart.

    If Nexus closed while the waterfall (or any pane) was popped out to its own window, the next launch could show the pane as still popped out — with no window anywhere and the docked copy gone — and it stayed that way every launch. The boot-time tidy-up that re-docks stale pop-outs ran before the saved UI state finished loading, so its correction was overwritten by the very staleness it had just fixed. Writes that land during that window now survive the load. Reported on a FlexRadio 6400M; nothing rig-specific.

  • The Connect map remembers your layers.

    Which layers you had on — parks, MUF, aurora, spots, all of them, and their opacities — reset to defaults on every launch, while the projection pick right beside them was remembered. The layer set now persists the same way: the map opens as you left it, and choosing a view preset afterwards still applies that preset's layers. Asked for from the field (#199).

  • A rig keyed the moment Nexus started, when PTT was set to RTS.

    On radios whose Hamlib backend declares hardware flow control — the TS-2000 it was reported on, and most Kenwoods and several Yaesus — choosing RTS as the PTT method on the CAT port let the Windows serial driver take the RTS line as flow control and hold it up for the whole session. On a Digirig-style interface that line is the key, so the transmitter keyed at launch and nothing could release it until the app closed. RTS cannot be flow control and the key at the same time, so when you declare RTS keying on such a radio Nexus now tells the rig-control daemon to run without hardware flow control, and the key line starts low and follows PTT. Other PTT methods and declared handshake settings are untouched. From a field report (vk6mo); needs an on-air bench pass, and if your radio's CAT menu has RTS flow control switched on it may need switching off to match.

  • US stations no longer all show the same heading in Spots.

    Every United States row read "~309°" (or whatever one number your QTH gives) — the bearing to the country's reference point in Kansas — while the spot itself was carrying the station's own grid. A spot that carries a grid, from your own decodes or off the skimmer wire, now shows the real heading to that station, unmarked; only a truly grid-less spot keeps the approximate "~" country heading. Reported from the field the day it was asked about.

  • macOS: CAT works again on a Mac without Homebrew.

    1.10.0 fixed the app not finding the Hamlib it ships (#190) — and the copy it then found was broken on exactly the Macs the bundling exists for: the bundled Hamlib library still looked for Homebrew's libusb at its absolute Homebrew path, so on a Mac without it the rig tools died on launch and Test CAT reported the rig never answered at any speed. 1.9.2 had worked on the same machines only because it never found the bundled tools and quietly used a Hamlib already installed there. Three fixes: the shipped library now points at the libusb shipped beside it; the release check now sweeps every shipped binary for paths that would not exist on an operator's Mac (it had checked only the one binary that was already correct); and a bundled tool that cannot start no longer stops Nexus from falling back to a Hamlib already on the machine. From two macOS field reports, an IC-756PROIII and an IC-7300 — both radios are fine; neither was ever asked anything.

  • Linux: the GStreamer warning at startup is gone, and RX capture gets more slack.

    The AppImage now bundles GStreamer's plugin-loader helper and points the app at it, so the "External plugin loader failed" warning no longer appears (the alert tones already worked — the fallback it warned about was doing the job, minus its crash isolation). Separately, the sound-card capture buffer on Linux now asks for about 100 ms of slack instead of the driver's default few milliseconds: a busy desktop scheduling Nexus late was overrunning the capture, and every overrun drops audio — which on FT8 is a torn symbol and a lost decode, not just a log line. Windows and macOS are untouched. From a Linux field report; the reduction in "buffer underrun or overrun" messages is the thing to watch for.

  • eQSL works for accounts with more than one QTH profile.

    eQSL requires a QTH Nickname to tell those profiles apart, and Nexus never sent one — so such an account could not authenticate at all: the inbox sync failed and uploads bounced. There is now a QTH Nickname field beside your eQSL username in Settings; it rides the inbox request and each uploaded record exactly as eQSL's own specs spell it. Single-profile accounts need nothing and see no change. From a field report.

  • The phantom "is calling you" is gone.

    Finishing an FT8 contact could pop "so-and-so is calling you" seconds later — about the station you had just worked, whose RR73 was the tail of your own QSO — and switching bands could do the same before a single new decode, replaying an old caller from the previous band. Reported on 1.9.2 and 1.10.0 with a screenshot that caught it live; the alert was re-judging old decodes every cycle as the QSO state moved on around them. It now only ever speaks for a decode that just arrived. A station genuinely calling you — including the one answering your CQ — alerts exactly as before.

Added

  • Scripts can play the rig's voice memories through Nexus.

    The rig-sharing port (NET rigctl, :4532) now answers \send_voice_mem <n> and \stop_voice_mem — the same spellings Hamlib's own tools use — so an external script can trigger DVS playback on a rig that supports it (Yaesu's PB command, among others) while Nexus stays connected. The radio itself keys for the playback, exactly as if you had pressed the memory button on the front panel, and a rig that doesn't support voice memories over CAT says so in the CAT diagnostics. Raw CAT passthrough remains deliberately unsupported: a scoped verb is a promise Nexus can keep; an open pipe to the transmitter is not. From an FT-991A field request.

  • Confirmation opportunities can be switched off.

    The Needed board and the decode chips include a "Confirm" tier — stations you have worked but not confirmed, your LoTW confirmation chances. It stays on by default; operators who chase contacts rather than confirmations can now turn it off under Settings ▸ Spots & Alerts ▸ Alerts, and both the board rows and the chips follow. A station that is also a new band keeps its row and only loses the Confirm chip. Asked for by KD9TAW.

  • World Radio League joins the connectors.

    Paste your WRL API key (their Integrations ▸ Developer API page) into Settings ▸ Logging & Connectors and every logged contact streams to your World Radio League logbook as it lands, alongside the existing QRZ/ClubLog/eQSL/HRDLog pushes. The key is checked against the service the moment you save it — a typo fails right there with a plain message, not on your first QSO — and your destination logbook is worked out at the same time, so there is nothing else to set up. Stored write-only in the OS keychain, like every other credential. Failed uploads retry with backoff; a revoked key tells you to fix it in Settings.

  • dB reports to comments, like WSJT-X.

    Turn on Settings ▸ Digital ▸ Logging Behavior ▸ "dB reports to comments" and every FT-mode contact logs its exchanged reports into the QSO's comment — "FT8 Sent: -07 Rcvd: -12", the same format WSJT-X writes, byte for byte, so the two programs' logs read alike. Off by default, exactly as WSJT-X ships it. Asked for by KD9TAW.

Changed

  • The TV page is now the real Connect view, not a summary.

    1.10.0's "Connect on a TV" served a plain digest — a band table and some numbers. It now serves Connect itself: the same map with every layer (grayline, spots, MUF, aurora, satellites, parks on the air), the same panes, live in any browser on your network — a shack TV, a Fire Stick's browser, a tablet — as a wall display. Still read-only in the strict sense: the server accepts nothing but reads, a short fixed list of propagation and space-weather feeds is all a browser can ask for, and everything else is refused. Your log, your needs board and the frequency you are on are still never sent; the setting's own text now also says that the picture includes the callsigns of stations heard and spotted, because it does. The simple summary still answers at /connect/data.json for anything scripted against it.

Every version