BMS integration guide
How to Connect Motorized Blinds to a Building Management System
A reliable connection requires a defined boundary between the blind motor, local controller, gateway or relay interface and the BMS. This guide helps the project team document that boundary before procurement.
Four parts of the system
Blind and motor
The physical blind, curtain track and selected motor determine load, voltage and available control interface.
Local interface
A motor receiver, RS485 controller, dry-contact input or wall control translates commands into movement.
Gateway or panel
A project-side gateway, actuator, or relay panel may connect the motor interface to KNX, BACnet, or another BMS layer only when the exact interface and third-party hardware are confirmed for the project.
BMS and commissioning
The approved project scope must identify which party maps required commands, feedback, alarms, schedules, and scenes and who tests the complete path.
Define the interface boundary
| Topic | Saiwenna / motor-side review | Integrator / project-side review |
|---|---|---|
| Motor | Available motor interface, voltage and local controls | Power circuit, cable route and panel coordination |
| Commands | Supported open/close/stop or protocol commands | BMS points, scenes, schedules and overrides |
| Feedback | Whether selected motor/controller exposes status | How status is mapped, displayed and alarmed |
| Gateway | Confirm motor-side compatibility | Gateway selection, supply, programming, and testing responsibility assigned in the approved project scope |
| Testing | Motor-side sample and operating check | End-to-end bench test, site commissioning and handover |
Connection options
Dry contact
A relay panel sends simple commands. It is straightforward, but position feedback and advanced addressing are not automatic.
RS485
A controller sends protocol commands over a wired bus. Addressing, topology, termination and protocol support must be checked.
KNX gateway or actuator
The project team must assign interface selection, datapoint mapping, and commissioning responsibility. Motor-side electrical and command compatibility must be verified for the selected configuration.
Procurement and commissioning checklist
- Blind schedule with type, dimensions, quantity and zones
- Motor voltage, position and power drawings
- Selected interface and exact controller/gateway model
- Open, close, stop, position, fault and override requirements
- Addressing, group and scene schedule
- Bench-test sample and acceptance criteria
- Site wiring inspection, functional test and handover owner
- Spare motors, controls and documented replacement process
FAQ
Can a BMS connect directly to every motor?
No. Some motors accept a defined wired protocol or dry-contact input; others require a receiver, controller, actuator or gateway. Confirm the exact motor-side interface.
Who is responsible for the gateway?
The project specification must assign responsibility for third-party gateway selection, supply, programming, motor-interface verification, and commissioning. No default split applies unless it is agreed in the quotation.
Should the team test before ordering?
For integrated projects, a representative bench test is strongly recommended where practical, especially when feedback, third-party gateways or custom commands are involved.
Related guides and product paths
Continue with the most relevant selection, specification or application resource.
Related Engineering Cases
See how related product, drawing and control questions are handled at their verified project stage.