Relay v0.7.19 · beta

Downloads

One executable, one config file, no runtime to install. Pick the package that matches the device that will run your relay.

Packages

Every package is self-contained — the .NET runtime is bundled inside the executable. Each download has a matching .sha256 file; verify before you run it.

Windows x64 · 42.7 MB
SHA-256fece076813f24eac8eba410a20b729d1cf923d7ce6730402268d919ad66fa231
Linux x64 · 42.4 MB
SHA-25608686a1bdf226b40efbcbd8487e631d0fc23a7c6f2263fb75914e56f321cd408
Linux arm64 · 40.3 MB
SHA-256baba947892d016b1b97f34f34bbf54262c980a843566e47789e324ea67f4bb89

Not sure which Linux package? uname -m answers it: x86_64 → x64, aarch64 → arm64. On Synology, Unraid, or a Raspberry Pi, arm64 is usually the one. The build manifest is at MANIFEST.md.

Docker — one image, amd64 + arm64. No runtime to install. The relay must run with --network host: SSDP discovery and the Roku's ECP / Companion ports do not survive a bridge network. Per-household values come from an env file at runtime — never baked into the image:

docker pull ghcr.io/bbapplied/esplex-relay:0.7.19

docker run -d --name esplex-relay --network host --restart unless-stopped \
  --env-file /opt/esplex-roku-relay/relay.env \
  -v /opt/esplex-roku-relay/appsettings.json:/opt/esplex-roku-relay/appsettings.json:ro \
  ghcr.io/bbapplied/esplex-relay:0.7.19

curl http://localhost:18080/v1/selfcheck

The image is public: no login, no account, no key to pull it. /v1/selfcheck is the single URL to paste into a support report — it lists exactly what is missing from your configuration.

Install steps

The same instructions ship as INSTALL.md inside every package. This is the short version.

Linux (x64 or arm64)

# 1. unpack somewhere permanent
sudo mkdir -p /opt/esplex-roku-relay
sudo unzip relay-linux-x64-v0.7.19.zip -d /opt/esplex-roku-relay
cd /opt/esplex-roku-relay

# 2. edit the four values in appsettings.json
#    Relay.Upstream          your bridge URL
#    Relay.PublicBaseUrl     this device, e.g. http://192.168.1.50:18080
#    Feed.RokuEcpBase        your Roku ECP, e.g. http://192.168.1.60:8060
#    Feed.RokuCompanionBase  your Roku companion, e.g. http://192.168.1.60:8324

# 3. secrets, never in appsettings.json
cp relay.env.example relay.env && chmod 600 relay.env
#    put Relay__EdgeKey (from your invite) into relay.env

# 4. run it, or install the systemd unit
sudo cp relay.service /etc/systemd/system/esplex-roku-relay.service
sudo systemctl daemon-reload && sudo systemctl enable --now esplex-roku-relay
curl http://localhost:18080/healthz

Windows (x64)

# 1. unzip anywhere permanent, e.g. C:\esplex-roku-relay
# 2. edit the four values in appsettings.json (same four as above)
# 3. copy relay.env.example to relay.env, add Relay__EdgeKey, save
# 4. double-click start.bat  (or run Relay-win-x64.exe from a console)
# 5. open http://localhost:18080/healthz in a browser

What a healthy start looks like

$ curl http://localhost:18080/not-configured
{"configured":true,"empty_names":[]}

$ curl http://localhost:18080/healthz
{"status":"ok","bridge":"up","config":{"public_base":true,"roku_ecp":true,
 "roku_companion":true,"player_allowlist_n":0}, ..., "version":"0.7.19"}

If configured is false, empty_names names exactly what is missing. The relay answers 503 not_configured on real routes until then — it will never guess a destination.

Verifying your download

# Linux / macOS
sha256sum -c relay-linux-x64-v0.7.19.zip.sha256

# Windows PowerShell
Get-FileHash .\relay-win-x64-v0.7.19.zip -Algorithm SHA256

Rollback

Keep the previous zip. To go back: stop the service, restore the old folder, start it again. Nothing outside that folder is written, apart from the cache and state directories the relay creates next to the executable.