Is My AV Gear Supported? [Hint: It’s Not a Yes-or-No Question]

A 200-line equipment list can tell you exactly what devices are going into your meeting rooms or AV systems. But it doesn’t tell you what you’ll actually be able to monitor or do once those devices are connected.

The reason is simple: the word “supported” means different things in different vendor and integrator contexts. One monitoring platform might have a full driver for one device, letting you see its status and performance and control it remotely. For another device, the same platform could provide detailed information but not let you send commands to the device. For a third device, the platform might only report whether the device is online. All three devices can legitimately be described as “supported,” even though the user experience for each is very different.

That’s why AV and IT teams responsible for those devices need to be clear what “supported” means before deployment, rather than finding out once the system is up and running. What exactly will they be able to see? What exactly will they be able to control remotely? And what needs to happen first for those capabilities to work?

In this blog, we’ll discuss the different levels of AV device support, what determines the coverage you get, and what to look for when reviewing an equipment list.

What Does “Supported” Actually Mean?

• Full monitoring and control: Detailed information about the device, plus remote commands such as rebooting it.
• Full monitoring: Detailed information about the device, without remote commands.
• Basic monitoring / heartbeat: A simple check that tells you whether the device is online or offline, even without a dedicated driver.
• Native: Monitoring functionality is built into the device itself, so no separate edge driver is required.
• Cloud-to-cloud: Device information comes through the manufacturer’s cloud.
• Not supported yet: There’s currently no available monitoring path for the device.

The key distinction here is between monitoring and control. Detailed monitoring tells you what’s happening with a device. Control means you can do something about it remotely, such as rebooting it or sending a supported command. Having one doesn’t necessarily mean you have the other.

Don’t Overlook the Connection Path 

“Support” is also not determined by the device or the platform alone. How the device connects to the monitoring platform can also affect what you can see and do. The same device can expose different information and commands through a local network connection than it does through, for example, the manufacturer’s cloud.

Even devices from the same manufacturer can offer different levels of support. A control processor or touch panel might have a full driver that provides detailed monitoring and remote commands, while a camera from the same brand might only provide a heartbeat. Seeing a manufacturer’s name on a supported-device list doesn’t necessarily tell you what to expect from every product the company makes.

In a very real way, the connection path determines the level of device “support” you actually get. It comes down to what each type of path gives the monitoring platform access to. A manufacturer’s cloud, for example, may only make certain device information and commands available, while a local driver may be able to communicate directly with the device and do more.

Make Sure the Device is Ready for Monitoring

The connection path tells you what a device can provide. The next question is whether the device is configured to provide it. Even when detailed monitoring and control are supported, you may need to configure the device first. For one device, that may not be a big deal. But hundreds or thousands of devices across an enterprise deployment are another story altogether.

And “configuration” can be simple or complex, too. It can mean enabling a particular setting or protocol, providing administrator credentials, or updating the device’s firmware. Some commercial displays, for example, need network control enabled and a network-ready standby mode selected. Without those settings, the display may disappear from monitoring as soon as it goes to sleep. Other devices rely on protocols like Telnet or PJLink, which may need to be enabled before the platform can communicate with them.

Credentials can make a difference, too. Without the required credentials, a device that normally provides detailed information may fall back to basic heartbeat monitoring.

It’s worth sorting configurations and credentials out before the system goes live. Otherwise, the fleet of devices you expected to monitor in detail may show up with limited information - or simply disappear from monitoring altogether. 

Check the Equipment, Not Just the Model Number

Once you know what level of support you need, check it against the equipment in your planned deployment. Don’t assume that a model is unsupported simply because its exact model number doesn’t appear on a supported-device list. In some cases, one driver works across an entire product family, including models that aren’t listed individually.

Then ask five questions about each device:

1. What can I monitor?
2. What can I control remotely?
3. How does it connect?
4. What setup does it require?
5. What happens if there’s no full driver?

Together, those answers give you a much clearer picture of what “supported” will mean in practice. You’ll know what information you can get from each device, what you can do remotely, and what you need to have in place to get the level of monitoring you expect.

How Xyte Handles Device Support

For a planned deployment, the challenge is getting those answers across an entire equipment list before anything goes live. That’s where Xyte comes in.

Xyte brings devices into a single monitoring environment through three main paths: native integrations built directly into devices, cloud-to-cloud connectors that bring in data from manufacturer platforms, and edge connectivity for devices on the local network.

This lets AV and IT teams monitor devices across manufacturers through a single platform and, where supported, manage them remotely. Xyte’s supported-device list is updated daily, and we can check your equipment list to determine the level of support available for each device.

Send us your equipment list, and we’ll give you a coverage report showing what you can monitor and control, how each device connects, and what you’ll need to set up before deployment.

‍

‍