Free · No sign-up

Will it work?

The most expensive sentence in the smart-home industry is "it's not compatible." Check any device against the system you already own — get the answer in one click.

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.

/v2 · Adapter capability matrix

What each adapter exposes

Every ecosystem plugs into the bridge as an adapter with two possible roles. As a device host it surfaces its devices as canonical entities the others can drive; as a controller it translates inbound actions (keypad presses, voice intents, driver calls) into canonical commands. The matrix below is the source of truth for which capabilities are live today.

Device-host role — capabilities exposed to other ecosystems
AdapterPowerVolumeSourceTransportBrightnessClimateLockPosition (shades)ColorScene / activate
Control4
control4
URC Total Control
urc
Hi-Fi Rose
rose
Josh AI
josh
Controller role — actions translated into canonical commands
AdapterPowerVolumeSourceTransportBrightnessClimateLockPosition (shades)ColorScene / activate
Control4
control4
URC Total Control
urc
Hi-Fi Rose
rose
Josh AI
josh

Adapter notes

  • Control4. Full peer. Device-host enumerates Director devices; controller side ingests DriverWorks proxy actions and writes state back as C4 variables.
  • URC Total Control. Controller-side fully live (Accelerator 3 IP driver → canonical). Device-host is scaffold until the dealer-gated URC accessory surface is wired.
  • Hi-Fi Rose. Device-host only. Transport endpoints are unverified (Phase 2) and intentionally not advertised, so /v2 rejects them with capability_unsupported.
  • Josh AI. Voice-first controller: structured Nimble intents and raw utterances both parse into canonical commands. Device-host stays gated on DevSuite access.

Legend: live · scaffold (gated on vendor SDK) · not applicable.

How the verdict works

  • ✓ Works natively — the vendor ships direct integration. No bridge needed.
  • ✓ Works with the Bridge — TCL Universal Bridge translates between the two ecosystems through the canonical /v2 contract. Your programmed system never changes when vendors ship firmware.
  • Not yet supported — adapter is on the roadmap. Email-capture feeds the priority queue.