Church Remote setup & compatibility

Q-SYS UCI integration roadmap

See the current plan for Q-SYS UCI access in Church Remote, why discovery is on hold and how saved local equipment portals differ from native control.

Dedicated integration is on hold

Q-SYS UCI discovery and dedicated control have not been implemented. There is no confirmed automatic UCI finder, native Q-SYS remote or available Core for hardware testing. No release date is promised.

What can be prepared now

Ask your system designer which Core, software version, UCI deployment permissions and browser interface are intended for the room. Keep the authorized local address and access requirements with the equipment configuration. Do not share Core credentials or expose a control page publicly just to make it discoverable.

Existing local portal option

Saved Web Portals can save an authorized private equipment page if it works within Church Remote’s local, same-origin restrictions. This is not a guarantee that every Q-SYS UCI page is compatible and does not add UCI discovery or bypass a Core license.

Before a future release

We still need a supported way to identify the correct Core and UCI, vendor-license review and actual controller testing. UCI licensing varies with Core/software and deployment. Tell us your model and desired workflow through the integration-request form; keep passwords out of the message.

Need help or want this integration?

Send a setup question or integration request. Include the Church Remote version, product model/version and the step that failed. Keep passwords, API keys, pairing codes and private presentation content out of the message.

Guide checked November 14, 2026. Provider capabilities and terms can change.