How device support works

A device can reach Connect+ in one of three ways. Which one applies to a given model determines where you check for support, and how you claim it.

1. Native devices

The device speaks to Connect+ directly, using firmware built against the Xyte device API. Nothing sits in between: the device registers itself and streams its own telemetry.

Support is a property of the device firmware, so if a manufacturer ships Xyte support in the product, it works. To add one, see Claiming a native device.

2. Local-network devices, through a Connect+ Edge

Devices that live on a customer's LAN and have no cloud of their own are reached by a Connect+ Edge — a small agent installed on that network. The Edge discovers the device, polls it over its native protocol (SNMP, PJLink, a vendor HTTP API, and others), and relays telemetry and commands back to the portal.

Support here is per model, because each one needs a driver on the Edge:

• Brands & Models — the models an Edge can monitor today.
• Device Setup Parameters — what has to be enabled or configured on the device itself, per manufacturer, before an Edge can reach it.

To add one, see Claiming local network devices.

3. Cloud-managed devices, through a Cloud Connector

Devices already managed in a vendor's own cloud — Zoom Rooms, Microsoft Teams Rooms, Crestron XiO, Q-SYS Reflect, and others — come in through a Cloud Connector. You authorize the connector once against the vendor platform, and its devices sync into Connect+ and stay in sync.

Support here is per vendor platform rather than per model: if the platform is covered by a connector, the devices it manages come with it. See Supported Devices for the current list, and Claiming a Cloud 2 Cloud device to add one.

Which applies to my device?

If your model isn't listed, see Requesting support for a new model.