Commands
The primary purpose of the Commands tab is to enable bidirectional communication. It allows you to configure how a user or a system rule can send instructions back to the physical world—such as adjusting a thermostat, dimming lights, or moving window blinds.
Scope & Capabilities
Covers three main areas:
1. Command Configuration & UI Definition
Enable/Disable: You can choose which commands from the underlying class (e.g., ComfortControlDigitalTwinDef) are active. For example, if a specific room type doesn't have motorized blinds, you can disable the blind command for that definition.
UI Elements: You can specify how the command appears to the end-user in the Digital Twin UI or mobile app (e.g., using a Slider for temperature, a Toggle for lights, or a Button for blinds).
Constraints: You define the "safety boundaries" for the controls, such as:
Min/Max values: (e.g., preventing a user from setting the temperature below 18°C or above 24°C).
Step sizes: (e.g., temperature adjustments in increments of 0.5°C).
2. Command Mapping
This is the most critical technical step. You must map each command to a specific Product.
This mapping ensures that when a user moves a slider in Planon, the system knows exactly which external gateway and protocol to use to deliver that command to the physical device.
3. Template Inheritance
Because this is at the Definition level, any configuration you set here is automatically inherited by every individual Digital Twin created from this definition. This ensures consistency across hundreds of desks or rooms without manual per-device setup.
Examples
AirTemperatureSetpoint: to send a new target temperature to an HVAC system.
PositionSetpoint: to control the height or tilt of window blinds (0% to 100%).
LuminancePositionSetpoint: to adjust lighting brightness or turn lights on/off.