DisplayHUB / Knowledge wiki
This is an old revision of the document!
Table of Contents
DisplayHUB Encoder Aio
Controller-free encoder mode
DisplayHUB Aio runs on the Android Encoder without a DisplayHUB Controller. Starting with Encoder 1.1.57, it sends playback commands using existing DisplayHUB player protocols: Android TV and Fire TV decoder commands, Roku channel launches, webOS local service commands, VizioOS local commands where available, and Tizen command polling. No player update or app-store release is required.
The subscription service issues a renewable Encoder session through the fields already understood by deployed players. These sessions do not register devices against ordinary Controller seats. Entering a raw Aio Stripe subscription ID in a Controller is still rejected.
Use a trusted local network that allows device-to-device communication, UDP discovery, and local HTTP commands. Guest Wi-Fi, client isolation, VLAN rules, or firewalls can prevent discovery or playback. Legacy players and the Encoder must use the same public internet egress address for subscription validation. IPv6 addresses that differ by device, separate VPNs, or different internet gateways can prevent session validation.
Set up Aio
- Connect the HDMI source, USB capture device, and Android Encoder. Grant the Android camera, audio, USB, and notification permissions required by the selected input.
- Open the Encoder configuration page from a browser on the same network.
- Open Aio Settings, enter the subscription ID for an active or trialing DisplayHUB Aio plan, and activate it.
- The Encoder starts its configured input when Android permissions and input settings allow it. Compatible decoders on the local network are discovered and sent the live stream.
An Aio subscription is separate from a regular controller subscription. Aio plans are not valid for ordinary controller playback; use the Switch to controller mode option before moving to a controller-based installation.
Starting with Encoder 1.1.58, Aio Settings remains available when the configuration page is opened directly, even if a Controller address is already saved. Opening the configuration page from a Controller hides Aio controls. The Aio header collapses or expands the section, and Aio Settings expands it automatically.
Stream delivery
By default, Aio uses WebRTC delivery. Enable Only send the HLS compatibility stream when a decoder or network requires HLS. HLS can add more playback delay than WebRTC.
Roku and VizioOS commands use HLS automatically. Roku requires the DisplayHUB channel to be installed and network app control enabled. webOS and VizioOS require their existing DisplayHUB local command service to be available. Tizen requires the DisplayHUB player to be running; it discovers the Encoder through the existing command endpoint on port 8081.
Keep the Encoder and decoders powered and connected to the same routable LAN. Aio discovery runs only while Aio mode is enabled. A decoder that becomes available after startup is discovered automatically.
Discovery uses SSDP announcements and a bounded private IPv4 sweep for networks up to /23. Larger networks rely on discovery announcements. A device must expose a recognized DisplayHUB app or command service before the Encoder sends playback to it. Compatibility with RDK, Xfinity, and other players without a confirmed command interface is not established.
Encoder features
The Encoder's local input, USB IR, and compatible HDHomeRun tuner controls remain available. The HDHomeRun guide is provided locally by the Encoder. For XMLTV, configure a Guide ID and API key in Advanced Settings; Aio downloads and caches the guide directly on the Encoder, without a Controller. Other centralized device-management features still require a Controller.
The Encoder can switch to controller mode without a separate installer. Google Play billing is not currently supported for Aio; follow the billing option shown for the subscription.
Android encoder setup | Android controller setup | Knowledge home
Read-only public knowledge base, maintained through the site's deployment files. Powered by DokuWiki. Device and firmware behavior must be qualified on your actual equipment.
Start here