My Building communicates between software modules, the network, and other Leviton equipment on the IP network. Most of this communication is TCP/IP communication, however, some of it is UDP/IP. This article document what type of communication is required between various parts of the system, it's orgin, and it's destination. This will help you to create the appropriate firewall and routing rules to have a successful network deployment.
My Building uses the following ports for communication between various devices in the system. Device layout is documented in My Building System Architecture, only summary information is proivded herein:
The Ports List
My Building uses the following ports for communication between various devices in the system. Device layout is documented in My Building System Architecture, only summary information is proivded herein:
| Protocol Common Name | Source->Destination | Protocol/Port # | Purpose/Notes |
|---|---|---|---|
| MQTTS | Room Controller->MQTT Broker | TCP 8883 | TLS with AES Encryption |
| MQTTS | MQTT Broker (Building) -> MQTT Broker Central | TCP 8883 | Only in multi-building system architectures |
| DHCP | Room Controller->DHCP Server DHCP Server->Room Controller | UDP 67 UDP 68 | Static addressing is possible but not recommended |
| DNS | Room Controller->DNS Server | UDP 53 | Required when DHCP is used |
| NTP | Room Controller -> NTP Server My Building -> NTP Server | UDP 123 | for time synchronization, can be turned off |
| API | My Building Phone App -> My Building | TCP 443 | Access to API calls. Secured with TLS with AES encryption as well as user tokens drive by a user permissions model. Certificate is a private certificate unique per project. |
| HTTP/HTTPS | Client Computer -> My Building Phone App -> My Buildilng | TCP 80,443 | Secured with TLS with AES encryption as well as user tokens drive by a user permissions model. Certificates used for web browser access can be automatically generated by Lets Encrypt, provided by user, or used insecure. |
| SMTP | My Building -> SMTP Server | 25 | Outbound email, alarms/alerts, account validation. Port number, username, password is configurable. |
| BACnet | BAS/BMS Controller -> My Building | UDP 45808* | BACnet is a protocol defined by ASHRAE for communication between Building Management Systems (BMS) and/or Building Automation Systems (BAS) to other devices. |
| TCP/ASCII | My Building Phone App -> Room Controller | TCP 57786 | Only needed when direct access to room controller is needed and when phone is on lighting control network. |
BACNet
If your project requires BACnet communication, which is often used to exchange sensor data with the BAS/BMS system and or allow the BAS/BMS system to control the lighting system, it will use either the BACnet/IP or BACnet/SC protocol. Which one is required is Lev determined by your BAS/BMS system provider as that is the system to which we are interfacing. BACnet/IP is a UDP protocol that operates on Port 45808 and as such requires local access to the BAS/BMS. If local access is not possible, the BACnet/BBMD protocol can be implemented which in effect creates a UDP<->TCP/IP gateway for only Bacnet data. This will need to be coordinated with the Leviton Field Tech and the BAS/BMS provider.More Questions?
Please leave reply below or email LCTechSupport@Leviton.com
Last edited:
