Changelog
Newest first. Each entry names the version your install should report, so one
curl http://localhost:18080/v1/selfcheck tells you whether you are current.
2026-11-18 — relay 0.7.19, per-household identity
- Each relay declares which household it belongs to. Enrollment carries the
household id,
/healthzreports it back (auth.household_id,auth.household_declared), and the bridge answershousehold_mismatch:truerather than quietly serving a relay that declares a different household. Packages and the Docker image are 0.7.19.
2026-11-18 — relay 0.7.18, scope declared at enrollment
- The relay states its scope when it enrolls, so the bridge mints a token for the
device that actually asked and the relay can report its own scope in
/healthz(auth.scope.devices,auth.scope.source).
2026-11-18 — bridge 0.9.119 → 0.9.123
- per-household credential enforcement, tenancy scope, rate limiting.
2026-11-18 — relay 0.7.17
- New:
/v1/selfcheck. One JSON to paste into a support message: version, uptime, what is configured, what your Roku answers, and aproblemslist. Emptyproblemsmeans everything the relay needs is present. - Docker image published (
ghcr.io/bbapplied/esplex-relay, amd64 + arm64, public — no login to pull) alongside the three standalone packages. Run it with--network host.
2026-11-18 — Roku channel 1.1.2026111802 (beta 893692)
- The profile screen now says which relay it is talking to. Open
ABOUT YOU and the last line reads something like
relay 0.7.17 · ok. A relay that reports problems showsrelay 0.7.17 · 2 issuesinstead, and an older relay with no health check simply shows no line — nothing is guessed. - No relay on your network? The manual-IP panel now also says where to get one:
esplex.bbapplied.com/downloads. - Published to the beta channel on 2026-11-18. A device picks the new build up on its next channel-store check, not instantly.
2026-11-18 — relay 0.7.16, first public packages
- Standalone packages for Windows x64, Linux x64 and Linux arm64: single executable,
.NET runtime bundled,
appsettings.json+thumbs/beside it. - Nothing is hard-coded to one household any more. Bridge URL, this device's public
base, the Roku's ECP/Companion addresses and the upstream all come from your config. Missing values
fail loudly (
/openanswers 503) instead of silently pointing at someone else's TV. - Fling allow-list. The relay only asks the Roku player you named to start playback.
2026-11-17 — relay 0.7.15, household access keys
- A household can carry its own bridge key instead of the shared one; enrollment is staged and off by default until each household is invited.
2026-11-17 — relay 0.7.14, public edge
- The relay reaches the server over a public HTTPS edge, so a household no longer needs a tailnet or VPN between its network and the server.
2026-11-17 — relay 0.7.13, the relay finds itself
- SSDP responder: the Roku channel discovers the relay on the local network automatically instead of needing an IP typed in. Settings that block multicast still fall back to config, then to manual entry.
2026-11-16 — first store build
- Roku channel 1.1.1 submitted as the first packaged build, with the household-neutral demo mode used for store artwork only.