DisplayHUB / Knowledge wiki
Table of Contents
DisplayHUB AIO
Controller-free encoder mode
DisplayHUB AIO runs on the Android Encoder without a DisplayHUB Controller. Use one encoder to send its configured input to compatible DisplayHUB players on the local network.
Only one DisplayHUB AIO encoder per network. Multiple AIO encoders can send conflicting playback commands. For more than one encoder, use a DisplayHUB Controller (full system) instead; run the encoders in Controller mode, not AIO mode.
See the DisplayHUB AIO product page for single-input streaming, single-source digital signage, and a comparison with the Controller/full system.
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
Start the five-day DisplayHUB AIO free trial / sign up. Card required. After five days, the plan costs US $9.99/month unless canceled. The plan covers one AIO encoder and its compatible players on the local network, not additional independent sources.
Copy the subscription ID from the AIO confirmation page and keep it private. Manage billing or cancel using that ID and the billing email.
- 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.
The AIO settings section 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 header shows one shortcut: Controller when it is available and AIO is off, otherwise AIO Settings. The AIO section header collapses or expands its settings, and AIO Settings expands it automatically. The one-AIO-encoder-per-network warning remains visible when the settings section is collapsed.
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 commands use HLS automatically. Roku requires the DisplayHUB channel to be installed and network app control enabled. webOS requires its DisplayHUB local command service to be available. Samsung/Tizen requires the DisplayHUB player to be running; the Encoder listens for its command polling on port 8081 only while AIO is active. Keep that port reachable and unused by another service on the Encoder. A TV that has already saved a Controller address continues polling that Controller until it becomes unavailable; do not operate both command sources for the same TV.
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.
The AIO settings show network-scan progress, the number and types of players found, scan completion even when no players are found, and Samsung/Tizen listener errors. The scan repeats automatically after completion.
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.
Digital signage
DisplayHUB AIO can also operate as a standalone digital-signage source. Its included Overlay Editor combines the configured video with text, logos, images, slideshows and supported widgets for menus, announcements, promotions or information displays. Design and apply the layout on the Encoder, then distribute it to compatible DisplayHUB players without a separate Controller. The one-AIO-encoder-per-network limit applies to digital signage too. Use authorized media and any required third-party widget subscriptions.
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