TCL Universal Bridge
Live: URC ↔ Hi-Fi Rose RS520 · Framework: Control4 · Josh AI

Make the device you love work with the system you already own.

TCL Universal Bridge is the Rosetta Stone for the smart home. Every premium ecosystem — Control4, URC, Josh AI — translates to one neutral vocabulary in the middle. A command from any controller reaches a device on any other ecosystem, through a stable /v2 contract that vendor firmware can't break.

Check compatibilitySee pricing →Maker tier from $9/mo

The hook

Don't rip it out. Bridge it.

The single most expensive sentence in this industry is "it's not compatible." The Compatibility Oracle turns it into a $9/month yes. Try it — no sign-up, no email gate.

Compatibility Oracle

Pick the system you own and the device you want to add. Get an instant verdict.

✓ Works with the Bridge

Control4 + Hi-Fi Rose RS520

TCL Universal Bridge translates between the two ecosystems. One adapter, no programming changes when vendors ship firmware.

Start free — $9/mo MakerGet a certificate

Ecosystems

One bridge. Three premium ecosystems. One live reference device.

Adapter status is honest. We ship the framework today and light up the device-host side of each adapter as vendor credentials and partnerships land — without changing the contract your system already targets.

Control4

Framework ready

Director API · EA / Core

EA-series (OS 3.3+) and Core-series (OS 3.4+) controllers. Adapter implements Director SEND_COMMAND today; full certification through DriverWorks in flight.

URC Total Control

Live

Accelerator 3 · IP driver

Custom IP driver targets the canonical /v2 contract. Same driver works against any device a future adapter brings online — no URC project changes when vendors ship firmware.

Josh AI

Partnership gated

Nimble intents · voice

Natural-language ingress lands on /v2/ingress/josh and resolves to any registered entity. Native Josh integration activates with Nimble DevSuite credentials.

Hi-Fi Rose RS520

Live

Reference device · live

The reference endpoint shipping today. Power, volume, source — controllable from any of the three ecosystems via the canonical model.

How it works

Hub-and-spoke, not point-to-point.

N ecosystems need N adapters, not N×(N−1) converters. Every adapter translates its vendor protocol into one canonical vocabulary — entities, capabilities, commands, state — and the router dispatches. Vendor protocol knowledge stops at the adapter boundary; everything past it is canonical.

When Hi-Fi Rose reshapes its control API in a firmware update — or Control4 ships an OS revision, or Josh changes a Nimble intent — only that one adapter changes. Your programmed system never does.

Canonical/v2 routercapabilities · entitiesControl4URCJosh AIHi-Fi Rose

The contract

One canonical surface. Two compatible versions.

The original /v1 Rose contract still works byte-for-byte — it's the proven wedge. The new /v2 universal surface adds entities, capabilities, and cross-ecosystem ingress. Both are versioned, both are tested per vendor firmware build.

  • GET /v2/entitiesDiscover every device across every adapter
  • POST /v2/commandSend a canonical command to any entity
  • POST /v2/ingress/:ecoNative payload from any controller, translated inbound
  • GET /v2/eventsServer-sent state changes, fanned out to listeners
  • * /v1/*Legacy Rose contract — re-implemented over the router, unchanged
curl
# Josh AI voice → Control4-only light, via the universal bridge
curl -X POST -H 'content-type: application/json' \
  -d '{"utterance":"turn on the living room lights"}' \
  http://127.0.0.1:8088/v2/ingress/josh

# Any controller → any entity, in canonical form
curl -X POST -H 'content-type: application/json' \
  -d '{"entityId":"rose:media_player:rose","capability":"source","action":"set","args":{"source":"optical"}}' \
  http://127.0.0.1:8088/v2/command

# Legacy URC IP driver still works — no programming changes
curl -X POST -H 'content-type: application/json' \
  -d '{"input":"EARC"}' \
  http://127.0.0.1:8088/v1/source

Adapter status

Honest about what's live and what's pending.

None of the three premium platforms publishes a fully open public API. We ship the complete framework today; each adapter's device side activates the moment real credentials are supplied.

AdapterLive

Hi-Fi Rose RS520

Live reference device. Power, volume, source — fully controllable from any ecosystem via the canonical model.

AdapterLive

URC Total Control

Custom IP driver targets /v2. Controller side wired; device-host side available with dealer Accelerator access.

AdapterFramework ready

Control4

Director SEND_COMMAND on EA-series (OS 3.3+) and Core-series (OS 3.4+). DriverWorks certification in flight.

AdapterPartnership gated

Josh AI

Voice/intent ingress on /v2/ingress/josh resolves to any registered entity. Native Nimble integration pending DevSuite credentials.