> ## Documentation Index > Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Cisco RoomOS > Connect Cisco RoomOS to KODE OS for other data > Connect Cisco RoomOS to KODE OS for other data integration ## Overview Use this integration to connect Cisco RoomOS collaboration endpoints to KODE OS. You discover room systems and poll meeting-room device status and telemetry for workspace operations. | Property | Value | | ------------------- | -------- | | **System Type** | Other | | **Communication** | REST | | **Collection** | Pull | | **Collection Mode** | SNAPSHOT | ## Supported Capabilities * Discover Devices & Points * Collect Sensor Data ## Prerequisites * An active account with Cisco RoomOS and access to their API or developer portal * Username and password credentials for the Cisco RoomOS system * KODE OS environment with access to Data Sources ## Configure Connector in KODE OS 1. Navigate to **Data Sources** in your building 2. Click **API Catalog** and search for **Cisco RoomOS** 3. Click **+ Add Datasource** 4. Fill in the fields below and complete the three-page setup flow | Field | Required | Type | Description | | ------------ | -------- | -------- | -------------------------------------------------------- | | **URL** | Yes | text | The base URL or IP address of the external system | | **Username** | Yes | text | The username for authenticating with the external system | | **Password** | Yes | password | The password for authenticating with the external system | ## Discover Devices and Points After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Cisco RoomOS system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the [Discovery guide](/products/integrations/capabilities/discovery). ## Devices and Points When you discover devices from Cisco RoomOS, KODE OS maps them to the following device types and data points: ### Connected Device Canonical Type: `default` | # | Point | Description | Unit | Writable | Collection | | -- | ---------------------------------- | ------------------------------------------------------------------------------------------ | ---- | -------- | ---------- | | 1 | `status` | Current operating status | -- | No | Polling | | 2 | `air_quality_index` | Composite air quality index | -- | No | Polling | | 3 | `ambient_temperature` | Current temperature reading (°C) | °C | No | Polling | | 4 | `relative_humidity` | Relative humidity level (%RH) | %RH | No | Polling | | 5 | `microphone_%s_connection_status` | Device connectivity status | -- | No | Polling | | 6 | `microphone_%s_ec_reference_delay` | Microphone echo cancellation reference delay | -- | No | Polling | | 7 | `microphone_%s_mute` | Microphone mute state | -- | No | Polling | | 8 | `ethernet_%s_mute` | Ethernet audio input mute state | -- | No | Polling | | 9 | `ethernet_%s_packet_lost` | Ethernet packets lost count | -- | No | Polling | | 10 | `ethernet_%s_packet_received` | Ethernet packets received count | -- | No | Polling | | 11 | `hdmi_%s_mute` | HDMI audio input mute state | -- | No | Polling | | 12 | `usbc_%s_mute` | USB-C audio input mute state | -- | No | Polling | | 13 | `connector_%s_%s_connected` | **True** -- device is connected and reporting / **False** -- device is not responding | -- | No | Polling | | 14 | `connector_%s_%s_hdcp_state` | HDCP content protection state | -- | No | Polling | | 15 | `webcam_mode` | Current webcam operating mode | -- | No | Polling | | 16 | `webcam_status` | Webcam operating status | -- | No | Polling | | 17 | `availability_status` | Room availability status | -- | No | Polling | | 18 | `volume` | Total volume measured | % | No | Polling | | 19 | `volume_mute` | Volume mute state | -- | No | Polling | | 20 | `ultrasound_volume` | Ambient sound level | -- | No | Polling | | 21 | `people_count_capacity` | Number of people currently detected in the space | -- | No | Polling | | 22 | `people_count_current` | Number of people currently detected in the space | -- | No | Polling | | 23 | `people_presence` | People presence detection status | -- | No | Polling | | 24 | `room_in_use` | Whether the room is currently in use | -- | No | Polling | | 25 | `t3alarm_detected` | **True** -- t3alarm\_detected is active / **False** -- t3alarm\_detected is not active | -- | No | Polling | | 26 | `ultrasound_presence` | Ambient sound level | -- | No | Polling | | 27 | `presentation_mode` | Active presentation sharing mode | -- | No | Polling | | 28 | `hdmi_%s_mode` | HDMI input mode | -- | No | Polling | | 29 | `hdmi_%s_delay_ms` | HDMI audio delay (ms) | -- | No | Polling | | 30 | `line_%s_connection_status` | Device connectivity status | -- | No | Polling | | 31 | `line_%s_delay_ms` | Line audio delay (ms) | -- | No | Polling | | 32 | `measured_hdmi_arc_delay` | Measured HDMI ARC audio delay (ms) | -- | No | Polling | | 33 | `measured_hdmi_delay` | Measured HDMI signal delay (ms) | -- | No | Polling | | 34 | `reported_hdmi_cec_delay` | HDMI CEC reported delay (ms) | -- | No | Polling | | 35 | `availability` | Room availability indicator | -- | No | Polling | | 36 | `presenter_detected` | **True** -- presenter\_detected is active / **False** -- presenter\_detected is not active | -- | No | Polling | | 37 | `music_mode` | Music playback mode | -- | No | Polling | | 38 | `mute` | Audio mute state | -- | No | Polling | | 39 | `noise_removal` | Ambient sound level | -- | No | Polling | | 40 | `level` | Current level value | -- | No | Polling | | 41 | `state` | Current operating state | -- | No | Polling | | 42 | `connector_%s_%s_signal_state` | Video signal detection state | -- | No | Polling | | 43 | `airplay_status` | AirPlay connection status | -- | No | Polling | | 44 | `main_video_mute` | Main video output mute state | -- | No | Polling | | 45 | `main_video_source` | Active video input source | -- | No | Polling | | 46 | `active_connector` | Currently active input connector ID | -- | No | Polling | | 47 | `background_mode` | Virtual background mode | -- | No | Polling | | 48 | `frames_availability` | Frames feature availability | -- | No | Polling | | 49 | `frames_status` | Frames feature status | -- | No | Polling | | 50 | `fullscreen_mode` | Fullscreen display mode | -- | No | Polling | | 51 | `mode` | Current operating mode | -- | No | Polling | | 52 | `on_monitor_role` | Monitor role assignment | -- | No | Polling | | 53 | `connected` | **True** -- device is connected and reporting / **False** -- device is not responding | -- | No | Polling | | 54 | `detected_connector` | Detected input connector ID | -- | No | Polling | | 55 | `flip` | Video flip/mirror state | -- | No | Polling | | 56 | `lighting_conditions` | Ambient lighting conditions assessment | -- | No | Polling | ## What Data You Get ### Point History Time-series readings including status, air\_quality\_index, ambient\_temperature, relative\_humidity, microphone\_%s\_connection\_status, microphone\_%s\_ec\_reference\_delay, microphone\_%s\_mute, ethernet\_%s\_mute, and 48 more, collected at regular intervals from connected devices ### Polling Schedule * **Point History** For more details on collection modes, see the [Data Collection guide](/products/integrations/capabilities/data-collection). ## Use Cases Once connected, this integration enables you to: * Centralize Cisco RoomOS data in your building operations dashboard * Correlate data from this system with other building systems for comprehensive analytics ## Troubleshooting Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Verify the username and password are correct and the account has not been locked in the Cisco RoomOS system. Verify the connector credentials have sufficient permissions in the Cisco RoomOS system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration. Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Cisco RoomOS API.