Skip to content

v0.8.13 — runtime IP-change failsafe & verified-owner release semantics

Choose a tag to compare

@tostmann tostmann released this 06 Jun 11:43
· 8 commits to master since this release

Highlights

Your SixBack's IP address can now change without stranding your speakers (Discussion #19). Migrated speakers store the SixBack base URL as a fixed IP. Until now, only a reboot made SixBack notice its own IP had changed. Now:

  • Runtime detection: a WiFi reconnect with a new IP triggers the re-point immediately — no reboot needed. Every migrated speaker is updated to the new address automatically (speakers already on the new base are skipped without a reboot).
  • Retry instead of give-up: if a speaker is offline during the run (typical after a router swap — speakers boot slower than the ESP), SixBack retries every 60 s for up to 20 minutes.
  • A DHCP reservation for the SixBack MAC in your router is still the recommended setup — then this never triggers.

Smarter ownership handling. A speaker is now only released to a foreign owner when that owner is verified — a live SixBack peer actually answering on that URL, or an explicit revert to the Bose cloud. A speaker pointing at a dead URL (stale base after an IP change, or a retired second stick) stays owned and is re-claimed automatically on the next auto-mode pass — this also works for models outside the auto-migrate whitelist, since the speaker was demonstrably migrated before.

Web UI: the left media sidebar now scrolls on short (laptop) viewports — the buttons at the bottom of the Stream/Spotify panels were unreachable (Discussion #15).

Web flasher: the source-code & bug-reports link is back (hero + footer).

Update

  • OTA: System → Check for update on your device (or wait for the periodic check).
  • Fresh install: https://sixback.io/

Verified end-to-end on test hardware (S3 + C6): runtime IP-change re-point, offline-retry, verified-owner release, auto-mode re-claim, sidebar scroll.