Imports devices managed in Cisco Webex Control Hub — RoomOS endpoints, boards and desks — with live status and command support.

Prerequisites

To use the Cisco Control Hub cloud API with Xyte, make sure you have:

• Required account / tenant: Webex organization
• Required access: Control Hub admin access
• Required plan / license: Trial or paid subscription
• Where to verify: Webex Control Hub

Status and sync

• Xyte reads each device's connection status from Control Hub on every sync, every 15 minutes.
• A device shows as online when Control Hub reports it as Connected or Connected with issues. Any other status shows it as offline.
• Status changes appear in Xyte on the next sync.
• If a device is removed from Control Hub, Xyte doesn't mark it offline. It's removed from Xyte after a while.

Authorization with the Cisco Webex Control Hub.

Steps

1. Visit your tenant on Xyte

2. Go to "Cloud Connectors" and add a new "Cisco Control Hub" connector.

3. Click "Authorize"

4. Copy and open the "Authentication Link" and enter the "Passcode" (copy from the same place as the link).

5. Click "Continue"

6. You will be redirected to Cisco Control Hub (also Webex)

7. Login if you are not signed in

   

8. Click "Accept" to authorize the Xyte connection with the listed required Permissions

   

Collected information

Device Information

Not all device models provide all data points

• ID
• Status (online / offline)
• Display name and room / workspace location
• Product and device type
• Serial number
• MAC address and IP address
• Software version and upgrade channel
• SIP URLs
• Connected peripherals (cameras, touch controllers, room navigators) — also imported as child devices

Device telemetry

Collected for devices that support the Webex device API (xAPI):

📘

Device telemetry uses the spark:xapi_statuses permission. Connectors authorized before this permission was introduced keep working normally but report only online/offline status — re-authorize the connector to enable the full telemetry below.

• System: uptime, volume, microphone mute
• Video inputs: connector type, signal state, and resolution per input
• Cameras: pan / tilt / zoom position, speaker-track and presenter-track status
• Room analytics: room occupancy (people count), people presence, room-in-use, ultrasound presence, ambient temperature, relative humidity, air quality index, ambient noise level, sound level, T3 emergency-alarm detection
• Peripherals: name, type, connection status, software version, and upgrade status per connected peripheral
• Network: IP address, gateway, subnet mask, MAC address, link speed, active interface, VLAN, Wi-Fi status (plus SSID and signal strength when on Wi-Fi), and the upstream switch name, port, and platform (learned via CDP/LLDP) — useful for physically locating a device
• Health / diagnostics: active alarm count, summary, and highest severity, taken from the device's own self-diagnostics
• Registration: Webex registration, SIP registration (with failure reason), provisioning status, and a derived registered indicator that flags devices that are online but unable to join calls

Room sensor readings (temperature, humidity, air quality) come from sensor-equipped models and peripherals (for example a Room Navigator); devices without sensors report them as "Not Available".

Network details refresh less frequently than the rest of the telemetry (approximately every fourth polling cycle).

Remote commands

• Reboot: Restart the device.

The above might change as the Webex device APIs are extended

Additional information

Connector root space name: Cisco Control Hub

If deleted and re-added:

⚠️

Deleting this connector will remove all imported devices and their data. This action cannot be undone.

• A new connector will be created upon re-adding.
• If the name Cisco Control Hub already exists, the new connector will be named Cisco Control Hub 1.
• The device tree will be re-imported under the new connector.
• The tree hierarchy will not be deleted.

After you submit, you'll see a confirmation that your credentials were submitted. Authorizing the integration and syncing devices can take up to 72 hours — you'll be notified when it's done.

For error messages and what to do about them, see the Cisco Control Hub troubleshooting guide.