Operations
Operations covers day-to-day monitoring and runtime control on the controller. Use these pages after devices are commissioned.
Sidebar section: Operations.
Dashboard
Home overview for the site:
- Device and group counts, online status
- System health (version, uptime, cloud sync)
- Recent activity and discovery status
- When licensed, compact AI Monitors gauges with links into monitor dashboards
Control
Manual control for operators:
- Filter by device, group, or facility zone
- Send lighting, shade, and other capability-based commands
- Live state preview over WebSocket
Prefer groups or zones for multi-device actions; use device detail for one-off changes.
Schedules
Time-based policies that keep running on the edge:
| Typical types | Examples |
|---|---|
| Time clock | Occupied / after-hours lighting |
| Dusk-to-dawn / shade | Façade and daylight-linked behavior |
| Power-save | Load reduction windows |
Create and edit schedules, assign groups, enable/disable, Run now, and review execution history. Circadian-style lighting may also be driven by the Circadian module and Automation task.
Events
Two tabs on one page:
| Tab | Purpose |
|---|---|
| Event redirections | Rules that map incoming events to actions (CRUD, test, YAML import/export) |
| Event log | Historical events with filter, detail, and clear |
Event redirections are not the same as Automation scripts. Sites using Realtime Controller may move reactive zone policy to RTC instead of legacy redirections.
Automation
Scriptable tasks (builtin and custom):
- List, create, edit, pause/resume, Run now, and history
- Bundled tasks such as circadian-lighting that link to modules
- Immutable versions when tasks are updated
Use Automation for durable edge logic; use MCP / Platform Assistant to propose and install changes when entitled.