Scenes
A Scene is a named group of writable points together with one or more modes. Each mode defines a value for every point in the scene. Applying a mode commands all of the scene’s points to that mode’s values in a single action.
Scenes capture an intentional building state — Occupied, Unoccupied, Curtail — once, so it can be recalled in one action instead of writing each point individually. A scene is a control convenience layered on point writes; it does not poll, trend, or hold any live state of its own.
Model
A scene has three parts:
| Part | Description |
|---|---|
| Points | The writable points the scene controls (e.g. s.5.9,
s.5.12). |
| Modes | Named states the scene can be set to (e.g. occupied,
curtail). |
| Values | One value per point, per mode — what each mode commands. |
Every mode covers the full point set: each point has exactly one
value in each mode. A scene is referenced by its scoped id
sn.<n> (e.g. sn.4).
Modes
Modes are the states a scene switches between. A mode has:
A name — a free-form label, shown verbatim (e.g.
Occupied,DR_Curtail). Names are unique within the scene, must start with a letter or underscore, and contain only letters, numbers, and underscores.A stable id — assigned when the mode is created and fixed for the life of the mode. References to a mode bind to this id, not the name, so renaming or reordering a mode never breaks them.
Applying a Scene
Applying a mode writes the scene’s values to its points: each point is set to its value for that mode, in a single batch write. The scene is recorded as the writer, so each point’s level view shows the scene by name. If any point is unbound or not writable, the apply fails as a whole — there is no partial apply.
An apply is an operator override. By default it writes at the
Manual level (8) and expires after
one hour, after which the points release and automated control
— a schedule, for example — resumes. The expiration can be set to any
duration up to a day.
Managers have two additional controls:
Level — apply at Emergency (
1), Utility (5), or Manual (8), for an override that must win over higher-priority automation.Permanent — hold the values with no expiration, until explicitly superseded.
Collaborators always apply at the Manual level with a bounded expiration, so a collaborator apply can never become a permanent hold.