Issue
Sigma controllers generate alarms, but these alarms are not received or displayed at the Enterprise Server during normal operation. However, when alarms are manually triggered from the Enterprise Server, they are received correctly.
Product Line
EcoStruxure Building Operation, Satchwell BAS & Sigma
Environment
- Building Operation Enterprise Server
- Satchwell Sigma
Cause
This behavior is typically caused by firewall restrictions:
- When the Enterprise Server initiates communication with Sigma controllers, alarm messages are allowed through the firewall and displayed correctly.
- When the Sigma controllers initiate communication (i.e., during normal operation), the firewall may block these inbound messages, resulting in delayed or missing alarms.
Resolution
To resolve this issue, allow inbound communication to the Enterprise Server on UDP port 49152.
Firewall Configuration Options:
-
If Windows Firewall is not used:
Refer to your firewall vendor’s documentation for instructions. -
If Windows Firewall is used but managed by IT:
Contact your IT department to request the necessary exception. -
If Windows Firewall is used and you have access:
You can manually add the exception or use the unofficial tool SBO Firewall Config.Note: While not officially supported, this tool has been successfully used at various sites.
For manual configuration steps, refer to:
Using Sigma on Windows 7 with Firewall
⚠️ Important Notice
Sigma is not supported in EBO 2022 and later.
To continue supporting Sigma devices, you can implement a multi-version system:
- Keep Enterprise Servers with Sigma devices on Building Operation 3.2.
- Add a Building Operation 2022 or later Enterprise Central
- Upgrade the rest of the system to Building Operation 2022 or later.
You will not be able to upgrade EcoStruxure Building Operation servers that contain unsupported protocols, objects, or devices. Attempting to do so will result in failed upgrades or loss of functionality.
