Sendspin’s C++ client adopts encrypted, paired connections

Device makers must adapt to new identities and pairing records as the audio client implements the release-candidate protocol.

Sendspin’s C++ client adopts the 1.0 release-candidate protocol with encrypted connections and pairing before a server can start playback. Applications can explicitly allow unpaired access, but that exception does not persist across a restart on its own.

Kevin Ahrendt’s implementation gives an upgraded device a new key-based identity and changes how applications store pairing records. Device makers must update their integration; an existing server will see a new client that needs pairing. The work was exercised on ESP32 hardware and against the updated Python server.

The client needs aiosendspin 10 on the server, which is still under development. Separate server corrections keep older Python and JavaScript clients able to pair during the transition.

Sendspin’s C++ client adopts encrypted, paired connections

From the source

Sendspin/sendspin-cpp

Sendspin/aiosendspin