State Management, Conditional Logic, Room Automation & Scheduling Triggers

Est. 60 minCompetency: Manage whole-room state and automate with conditions and schedules.

Learning objectives

Maintain room-wide state across all devices.
Use conditional logic for automation.
Implement scheduling triggers.
Keep state consistent across errors.

Vocabulary

Room state: The combined state of all devices: power, source, call, audio.
Conditional logic: If/then rules that automate behavior.
Scheduling trigger: A time-based event (e.g. auto-shutdown at 6 pm).
Occupancy sensor: A sensor that detects presence; can trigger automation.

Lesson content

Whole-room state is more than the display. It is power, source, call status, camera preset, audio level, and occupancy — all kept consistent so the room behaves predictably.

Whole-room state model

room = {
  power       : OFF,           // OFF | ON | STANDBY
  source      : NONE,          // LAPTOP | CODEC | NONE
  call        : IDLE,          // IDLE | CONNECTING | ACTIVE
  camera      : WIDE,          // WIDE | TIGHT | TRACK
  audio       : { level: 50, mute: false },
  occupancy   : true,
}

Conditional automation

If occupancy goes false for 10 min and no call, prompt auto-shutdown.
If a call connects, mute program audio and route camera to the codec.
If source changes to CODEC, raise volume to the conferencing preset.

Scheduling triggers

1Auto-shutdown at building close to save lamp life and power.
2Auto-power displays before the first scheduled meeting.
3Do not schedule destructive actions without a safe window.

Consistency over cleverness

Every automation must leave the room in a known state. An automation that saves power but leaves the codec in an unknown call state costs more in support than it saves.

Worked example

Occupancy sensor reports empty for 10 minutes, no active call, source still laptop: the panel shows 'Auto-shutdown in 1 min — tap to keep room on.' If no touch, the room shuts down to standby. State stays consistent; the next user gets a clean start.

Implementation checklist

✓Whole-room state modeled and kept consistent.
✓Conditional automations defined with safe conditions.
✓Scheduling triggers tested against real schedules.
✓Every automation leaves a known state.

Downloadable study guide

study-guide.txtcopy-paste ready

01. Room state = power + source + call + camera + audio + occupancy.
02. Automate with conditions; always leave a known state.
03. Scheduling triggers: auto-shutdown, pre-meeting power-up.
04. Never schedule destructive actions without a safe window.