General
GRMS planning guide
Switch lookbook
Lighting control
Occupancy detection
Energy saver
Project timelineProducts
Release notes
Fleet Manager
Cloud API
401-D2
401-DFor partners
Partner portalBACnet/IP integration of AC units
BACnet/IP integration of AC units connects the guest room management system to the building management system (BMS) and exposes the occupancy state of the guest room so the AC unit can act based on this information.
How it works in a guest room
| Room status | Information flow | Events |
|---|---|---|
Occupied | Mount Kelvin → BMS | Mount Kelvin turns the lights on and sends the room status to BMS, which defines the AC unit actions. |
Unoccupied | Mount Kelvin → BMS | Mount Kelvin turns the lights off and sends the room status to BMS, which defines the AC unit actions. |
Mount Kelvin offers a default mapping of BACnet registers to rooms. The register information needs to be implemented in the BACnet master system by an automation specialist.
Please note that when using this integration, the practical HVAC setpoint changes need to be made in the BMS system. This gives the option of doing more complex logic, e.g. based on time of year or outdoor temperature via the BMS system by the general automation contractor.
Mount Kelvin 420 BACnet gateway
In order to set the HVAC units to eco-mode, they need to be connected into the system via the Mount Kelvin 420 BACnet gateway.
Only one BACnet gateway per hotel is required.
Networking requirements
BACnet objects
The core idea is to create BACnet objects with specific names for every room.
The format of the object name is Hnnn.sssNvMk where nnn is a room number and sss is a feature-dependent name. Multiple BACnet devices can be used as long as they do not have conflicting Mount Kelvin objects.
