See what's been requested
without picking up a phone.
ESPLEX Companion is a small Roku channel for a shared Plex library. It shows what has been requested, whether it has downloaded yet, and where it stands — then jumps you straight into Plex when it's ready.
What it actually does
Requests already live in Seerr; the library lives in Plex. This puts the two on the TV in one place, in plain language, instead of a browser tab on a phone.
What's been asked for
Everyone in the household can see the queue: what was requested, by whom, and when it showed up.
Where it stands
Requested → searching → downloading → in the library. No more guessing whether it's stuck or just slow.
Straight into Plex
When something is ready, the channel launches Plex on the TV and starts it. It is a shortcut, not a second player.
Three parts, one small system
The data lives on the Plex server, the TV lives on your home network, and the two cannot talk directly. So there is a thin relay in between — that is the only thing you install.
The Roku has no way to reach a server outside your network, and Roku channels are not allowed to launch other channels. Something on your LAN has to hold the data and press the button — that is the relay.
Ship it with no configuration and it refuses to do anything: /not-configured
reports exactly what is missing, and it never guesses a destination. No config, no traffic.
The relay fetches the queue and the artwork, caches them locally, and launches Plex. It never writes to your library and never changes a request.
What you need
Beta invites are handed out one household at a time, so not everyone has all of this. If a line is missing, tell me before you start.
- A Roku device — any current Roku or Roku TV on the same network as the relay.
- A Plex server with the bridge — the bridge runs on the server (Docker) and is set up by whoever runs the household's server.
- One always-on device for the relay — a small PC, a NAS, a Raspberry Pi, a Docker host — anything that stays on and sits on the same network as the TV.
- Your invite details — the bridge address and access key, which come with the beta invite. The relay is useless without them, and that is deliberate.
Install in four steps
The full detail — including rollback — is in INSTALL.md inside the download.
Unpack and configure
Unzip the package somewhere permanent, then fill in four values in
appsettings.json: the bridge URL, this device's own URL, and the Roku's
ECP and companion addresses.
Start it once
Run the relay as-is. It should come up and honestly report it is not configured yet:
/not-configured lists what is empty, everything else answers
503.
Add your invite key
Copy relay.env.example to relay.env, set
chmod 600, and put the access key from your invite in it. Keys live there,
never in appsettings.json.
Restart and check
Restart the relay and open /healthz. When the four config booleans are
true and the bridge reads up, the TV will find it.
Then keep it running
As a service
The package ships a systemd unit. Copy it, adjust the paths if your folder differs, then
systemctl enable --now. Logs land in the journal.
With start.bat
The Windows package loads relay.env and starts the relay for you. To keep it
running after sign-out or reboot, register the same script in Task Scheduler.
Sanity check — ad-hoc start and the two routes worth knowing (Linux x64 shown):
cd /opt/esplex-roku-relay
./Relay-linux-x64 --urls http://0.0.0.0:18080
curl http://localhost:18080/not-configured # which values are still empty?
curl http://localhost:18080/healthz # bridge up? version correct?
This is a beta, and it is honest about that
Please read this before installing. ESPLEX Companion is a beta built for a small household and a few friends. It is not a commercial product: there is no support desk, no uptime promise, and no warranty. The Roku channel is installed directly onto your device during setup rather than from the Roku Channel Store, and it may need re-installing after Roku updates. If it breaks, I want to hear about it — that is the point of a beta.
What it will never do. It does not sell, share, or publish your viewing data. It does not touch your library. It does not collect anything from this page — no analytics, no cookies, no trackers.
Questions, bugs, or a request to be removed from the beta: esplexops@gmail.com.