github Sendspin/sendspin-cpp-cli v1.0.1
sendspin-cli 1.0.1

one hour ago

A fix for local pairing on Home Assistant OS, and a config file in the Linux packages. The
player still speaks Sendspin 1.0.0-rc1, and nothing breaks for CLI users: every flag, config
key, control-socket message, state-file format and exit code from 1.0.0 works the same way.

Fixed issues

  • Local pairing works on Home Assistant OS. --pairing-token-endpoint now answers a peer
    whose address is one of this host's own, as well as peers on the endpoint address's subnet.
    Music Assistant runs on the host network, so its fetch of 172.30.32.1 was masqueraded to
    the host's LAN address and refused with 403. Music Assistant then logged
    Fetching the local token of <id> failed: HTTP 403 and never paired by itself. Other
    machines on the LAN are still refused. (#134)

Packaging

  • The .deb, .rpm and Arch packages install /etc/sendspin-cli.conf. It is the fully
    commented example, so nothing changes until you edit it. Upgrades keep your edits: it is a
    deb conffile, an rpm %config(noreplace) and an Arch backup. The package still doesn't
    enable or start the service. Installation → Packages walks through configuring it. (#130)

Full changelog: v1.0.0...v1.0.1

What this build is

sendspin-cli 1.0.1. The version of the sendspin-cpp library it is linked against
is pinned at build time and printed on the second line of sendspin-cli --version,
alongside this one on the first.

Installing, verifying SHA256SUMS and the macOS Gatekeeper situation are in the
wiki — Installation,
or Getting Started on a Raspberry Pi
for the two 32-bit ARM archives. Each archive also carries its own BUILD-INFO.txt,
with the install command already filled in for its platform. The .deb, .rpm and
.pkg.tar.zst packages install the same binary under /usr; see
Packages.

The macOS binary and the .pkg around it are unsigned — ad-hoc signed, which is
the minimum an arm64 Mach-O needs to execute at all, and carries no developer identity
— so Gatekeeper refuses them until you say otherwise. Said here rather than only behind
a link because it is worth knowing before you download; what to do about it is under
the macOS installation guide.

The Windows zip is unsigned as well, so SmartScreen may warn the first time it runs.
Getting Started on Windows
has a guided installer that checks the zip against SHA256SUMS before installing it.

  • README — what it is, how to run
    it, and how to contribute
  • Contributors — development,
    testing, CI, and release guidance
  • Roadmap — what is still owed,
    item by item

Don't miss a new sendspin-cpp-cli release

NewReleases is sending notifications on new releases.