BACnet/IP
The BACnet/IP Server module exposes lighting groups on the Aida Controller as BACnet/IP points for a building management system (BMS). The controller is a single BACnet device on UDP port 47808; PoE nodes never speak BACnet directly.
Enable it under Modules → BACnet/IP Server.
When to use it
| Path | Protocol | Typical use |
|---|---|---|
| BACnet/IP (this module) | BACnet/IP | BMS graphics, schedules, municipal submittals |
| Public REST | HTTPS /aida/api/* | Scripts and non-BACnet integrators — see API Docs — Controller |
Levels
| Level 1 (available) | Level 2 (roadmap) | |
|---|---|---|
| Reads | ReadProperty on cached group aggregates | + SubscribeCOV; RTC-backed authoritative state |
| Writes | WriteProperty → same control path as UI / Public API | + richer override / DR objects |
| Sensors | Occupancy, lux, temperature, sound when present | + CO₂, humidity, and related |
Default deployments use Level 1. Document Level 1 limitations (no COV, no CO₂ BACnet points, and so on) in municipal submittals when applicable.
Setup
- Sign in as a role that can manage modules.
- Open Modules and enable BACnet/IP Server.
- Configure device instance, bind address, and which groups to export.
- Allow UDP 47808 on the controller VLAN.
Writable points (dim, power, CCT) dispatch through the same execution path as operator commands. Read-only sensor points reflect polled and event-driven state.
BMS acceptance (checklist summary)
- Confirm unique BACnet device instance on the Owner network
- Agree group name prefixes for graphics
- Verify ReadProperty / WriteProperty on power, dim, and CCT for a pilot group
- Verify occupancy / lux (and other Level 1 sensors) where fixtures provide them
- Export object inventory for as-builts after commissioning
Related
- Realtime Controller — Level 2 / event-driven paths
- API Docs — Controller
- Municipal-style projects — coordinate PICS with your Aida account team