Thanks for your feedback.

Overwiew

Standalone Room Navigators previously did not report environmental metrics such as temperature and humidity. With recent enhancements, these environmental metrics are now exposed through a dedicated new xAPI node. This allows customers to collect and monitor environmental data independently from the internal room sensors, providing greater flexibility and insight into room conditions.

By leveraging third-party occupancy sensors and the expanded environmental telemetry from standalone Navigators, organizations can improve workspace utilization accuracy and gain valuable environmental insights to optimize comfort, safety, and energy efficiency.

Third-party occupancy sensors

RoomOS currently provides the RoomAnalytics RoomInUse status as the primary indicator of whether a room is occupied. This status is derived from various RoomOS signals such as active calls, local activity, people presence, and people count, depending on the device capabilities, sensors, and configuration.

A new third-party occupancy input can influence the same RoomAnalytics RoomInUse state. Through macros or external integrations, RoomInUse can now be set based on events from external occupancy sensors.

This feature is particularly useful for:

• Supplementing the device’s built-in sensing capabilities.
• Reporting occupancy in spaces without a full video system, such as focus rooms, wellness rooms, mother’s rooms, or other shared areas where occupancy data is valuable.
• Supporting standalone Room Navigator deployments for room booking and occupancy reporting.

In standalone Room Navigator room-booking setups, RoomInUse can also enable Cisco’s automatic Check-in/Check-out behavior where configured, even if no video system is installed in the room.

Room Environmental xAPIs

RoomOS now reports aggregated environmental metrics for both inside-room and outside-room locations, sourced from Cisco Room Navigators equipped with environmental sensors.

• A Navigator configured as inside the room contributes to the InsideRoom room-level environmental statuses.
• A Navigator configured as outside the room contributes to the OutsideRoom room-level environmental statuses.

Previously, environmental readings from outside Navigators were not exposed through room-level xAPI values, and inside-room environmental data was reported per device rather than as aggregated room-level values.

These environmental metrics include temperature, humidity, and air quality, enabling facility managers and analytics tools to monitor and optimize workspace conditions effectively.

Room Environmental xAPI list

This release introduces enhanced xAPI capabilities to support third-party occupancy sensors and comprehensive environmental monitoring for Cisco Room Navigator devices.

Third-party occupancy input

You can now set the RoomInUse status using third-party occupancy sensors with the following command:

xCommand RoomAnalytics RoomInUse Set

Parameters:

State: InUse or NotInUse
ID: Identifier for the sensor or integration
Duration: Duration in seconds for which the state should be maintained

Example:

xCommand RoomAnalytics RoomInUse Set State: InUse ID: "third-party-sensor-1" Duration: 300

Occupancy status monitoring

xStatus RoomAnalytics OccupancySensor[n] ID
xStatus RoomAnalytics OccupancySensor[n] RoomInUse
xStatus RoomAnalytics RoomInUse

The overall xStatus RoomAnalytics RoomInUse includes third-party occupancy input as part of the room occupancy state.

Inside-room environmental statuses

Aggregated environmental data from inside-room Cisco Room Navigators is accessible through:

xStatus RoomAnalytics InsideRoom AmbientTemperature
xStatus RoomAnalytics InsideRoom RelativeHumidity
xStatus RoomAnalytics InsideRoom AirQualityIndex

Outside-room environmental statuses

Aggregated environmental data from outside-room Cisco Room Navigators is accessible through:

xStatus RoomAnalytics OutsideRoom AmbientTemperature
xStatus RoomAnalytics OutsideRoom RelativeHumidity
xStatus RoomAnalytics OutsideRoom AirQualityIndex

Limitations

The current implementation does not support the following:

• Native discovery, pairing, or vendor-specific setup for third-party occupancy sensors.
• Prebuilt integrations for specific third-party sensor vendors.
• Third-party environmental sensor integration.
• People count, temperature, humidity, or air quality data from third-party occupancy input

Requirements

To validate third-party occupancy input, you need:

• Admin, Integrator, or RoomControl-level access to the device xAPI.
• A macro, local integration, or external service capable of executing xAPI calls.
• A third-party occupancy sensor or system accessible through your chosen macro or integration.

To validate environmental values, you need:

• Cisco Room Navigators with supported environmental sensing.
• Each navigator must be assigned a specific location (InsideRoom or OutsideRoom) through the touch panel configuration.

RoomOS uses the navigator's configured location to place its environmental readings into the appropriate room-level aggregate: InsideRoom or OutsideRoom.

Example Occupancy Integration

A typical third-party occupancy integration works like this:

1. A third-party sensor detects occupancy.
2. A macro or external integration receives the sensor event.
3. The integration calls xAPI to set RoomInUse.
4. RoomOS updates RoomAnalytics RoomInUse.
5. The integration refreshes or clears the state as sensor input changes.

Example when occupancy is detected:

xCommand RoomAnalytics RoomInUse Set State: InUse ID: "sensor-1" Duration: 300

Example when the sensor reports that the room is no longer occupied:

xCommand RoomAnalytics RoomInUse Set State: NotInUse ID: "sensor-1"

If a duration is used, the integration should refresh the InUse state before the duration expires if the room is still occupied.

If multiple third-party occupancy sources are used, each source should use a stable ID so that its state can be monitored separately.

Environmental xAPI behavior

The environmental xAPIs report room-level values, not raw per-panel readings.

For inside-room values, RoomOS aggregates readings from Navigators configured as inside the room.

For outside-room values, RoomOS aggregates readings from Navigators configured as outside the room.

This makes it possible for integrations, monitoring tools, and dashboards to consume both inside-room and outside-room environmental values through xAPI.

Environmental xAPI values are based on supported Cisco Room Navigator environmental readings. This release does not ingest or aggregate environmental data from third-party sensors.

Known behavior and limitations

• Third-party occupancy input controls RoomInUse state only. It does not provide people count, temperature, humidity, or air quality data.
• A macro or external integration is required to connect a third-party occupancy sensor to RoomOS. RoomOS does not directly discover or manage the third-party sensor.
• If a duration is used when setting RoomInUse, the third-party integration is responsible for refreshing the state before the duration expires.
• Environmental statuses depend on supported Cisco Room Navigator hardware, placement, and configured touch panel location.