Realtime Controller (RTC)
The Realtime Controller module runs an optional Rust sidecar for centralized, event-driven zone policies on the LAN. Use it when you want reactive control (for example occupancy → lighting) with low latency and a clear sync model from the main controller.
Purpose
| Without RTC | With RTC |
|---|---|
| Legacy event redirections and controller-side loops handle many reactive cases | Sidecar owns selected realtime policies; controller syncs definitions and monitors health |
| Suitable for many sites | Preferred when you need stronger event-driven INX-style control and Level 2 BACnet paths that depend on RTC |
Setup
- Enable Realtime Controller under Modules.
- Review status, sync, and sidecar health on
/modules/realtime-controller. - Apply or migrate policies as documented for your release (replacing selected event redirections when appropriate).
- Keep software versions aligned when using HA redundancy.
Operators
- Watch module health after network or firmware changes
- Use Operations → Events for the event log; prefer RTC for policies that have been moved off legacy redirections
- Coordinate with BACnet/IP Level 2 requirements when BMS COV / authoritative reads need RTC