Send commands to writable points from device details or a floor plan to adjust setpoints and control equipment operation.
Command and control is a building-level feature. Select a building from the sites list before you command points.
Commanding and controlling equipment lets you adjust setpoints and variables to influence how equipment operates. You can only perform these actions on writable points.The command dialog is the same across integrations. BACnet devices, API thermostats, and other connectors all use this write-back flow. The underlying protocol depends on the data source, not on the dialog itself.
Writable points accept commands from Cloud BMS. Read-only points report measurements and status but do not accept writes. See Points for the difference between read-only and writable point types.To enable or disable writability on a point, modify it from device details or use points batch update.
From device details, click a writable point value. From a floor plan, click the edit icon next to a writable point.
2
Configure the command
Set the command parameters in the Action section.
The command dialog shows action, value, duration, and reason fields with current levels at the bottom
Hide Command parameters
Field
Description
Priority
The command action to apply (Override, Set, Auto, or Release). See the action mappings below.
Value
The value to write (for example, 62.6 °F for a temperature setpoint). Use the + and - buttons to adjust.
Duration
How long the command remains active before auto-reverting (hours and minutes)
Reason
A predefined reason from the dropdown
Permanent
Check this to make the command persist without auto-reverting
Specific Reason
A free-text note explaining why you made the change
The bottom of the dialog displays the current levels and their values. Click Activity Log in the upper-right corner to view the full command history for this point.
3
Submit the command
Click Save Changes to send the command to the device.
Cloud BMS uses a BACnet-inspired priority model for writable points. The same command dialog appears for BACnet and non-BACnet integrations, such as REST API thermostats. How each action maps on the device depends on the connector.BACnet points that accept commands have 16 priority levels (1 is highest, 16 is lowest). When every level is empty (null), the point uses a fallback / default value (Relinquish_Default in BACnet). That fallback is not a 17th BACnet priority. Some interfaces label it as level 17 for display only.Override and Set turn different knobs under the hood, even when the visible value looks the same.
Action
What it writes*
Description
Override
Priority 8*
Temporary exception in the priority array. Takes precedence over lower-priority automation.
Set
Fallback / default*
Changes the fallback or default value.
Auto
—
Clears an Override
Release
—
Clears a Set
*Typical for most BACnet and Niagara deployments. Connectors and site standards can differ.Override, Auto, and Set borrow Niagara-style action names. Release is a Cloud BMS action that clears a Set.In Niagara-style control, Set keeps a non-null fallback so sequences and logic keep a reliable baseline. Use the priority array (including Override) for programmed automation and temporary exceptions.To make Set write to priority 16 instead of the fallback or default, enable Set in Slot16 (Niagara) on the point. Configure that option from device details, device templates, or points batch update.
Schedules, OSS, and FTT can also write to points at specific priority levels. When a schedule is actively commanding a point, the command dialog shows the schedule’s priority level. See schedule command levels for details.
