Compatibility and limitations
Server
Section titled “Server”| Area | Supported/current expectation |
|---|---|
| Host architecture | 64-bit amd64 or arm64 Linux |
| Container tooling | Docker Engine and Compose v2 |
| Display model | Linux host connected directly to the display |
| Runtime profiles | Wayland, X11, DRM/KMS, and explicitly supported headless builds |
| GPU acceleration | Available when compatible hardware and /dev/dri are exposed |
| HDMI-CEC | Optional when compatible /dev/cec* devices are exposed |
| Network model | Trusted LAN; token plus VPN/protected proxy across untrusted networks |
Companion projects
Section titled “Companion projects”| Project | Current requirement |
|---|---|
| RelayTV for Android | Android 8.0+ (minSdk 26), Android 15 target |
| RelayTV for Home Assistant | RelayTV HA 0.4.0+ requires Home Assistant 2026.7+ |
Important limitations
Section titled “Important limitations”- RelayTV is not a smart-TV app or Chromecast receiver.
- Hardware architecture does not guarantee 4K, HDR, codec, audio-passthrough, or CEC behavior. Validate the actual host/display chain.
- mDNS discovery may not cross VLANs, routed networks, or VPNs.
- Media-server and IPTV playback still depend on upstream reachability and the operator’s authorization to use each source.
- A healthy API does not prove the physical graphics/audio path works.
- Companion app behavior can lag new server endpoints; review each project’s current release notes and known limitations.
Canonical compatibility sources
Section titled “Canonical compatibility sources”- Server installation
- Runtime matrix
- Android compatibility
- Home Assistant compatibility and limitations
Reviewed 2026-08-29.