Building Automation Knowledge Base

Issue Why do the Architectural Guidelines specify a maximum of 1500 Extended Trend Logs in Automation Servers, whereas such a limitation did not exist with the Continuum Net Controllers, like the NetController II.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause EcoStruxure Building Operation's architectural guidelines specify a limit of 1500 Extended Trend Logs for the Automation Servers (AS-P/AS-B). Sites transitioning from Andover Continuum to EcoStruxure Building Operation need to understand the architectural differences that necessitate this limit. Resolution The architectural differences between Continuum and EcoStruxure Building Operation means that it is crucial that Extended Trend Logs are managed effectively to ensure ensuring optimal system performance.   In Continuum: Controller Role: Controllers do not participate in Extended Trend Log functionality beyond sending data from intrinsic logs upon request from Cyberstations. Log Management: Extended Trend Logs reside at and are managed by Cyberstations. Load Distribution: Multiple Cyberstations, configured to collaborate, maintain the Extended Trend Logs, minimizing the load on controllers.     This design puts very little load on the controllers when it comes to Extended Trend Log functionality.   In EcoStruxure Building Operation: Distributed Database Architecture: Extended Trend Logs are managed by the AS-P/AS-B servers. Server Load: The server performs tasks typically handled by multiple Cyberstations in Continuum, which often run on more powerful PC hardware. Performance Management: To prevent Extended Trend Log servicing from overwhelming the Automation Server's resources (CPU, memory), a limit of 1500 logs is enforced. Exceeding this limit can degrade server performance and potentially cause reboots due to critical memory usage.  This can be seen in the following example trace log entry: Nov 30 15:39:58 PSS-AS02 memcritsv[1011]: Memory usage critical!    

  Issue EcoStruxure Building Activate Flex Server doesn't pass the GSM Signal Strength test.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server must achieve a GSM Signal Strength greater than 14 to pass the test. If the signal strength is less than 14, the test will fail.   Resolution Below are the troubleshooting steps which should be checked/followed: Ensure the Gateway is located in an area with good network coverage. If possible, reposition the Gateway to improve signal strength. Verify that the APN settings for the SIM card in the Device Management Dashboard are correct. Change the network carrier and reconfigure the APN again

Issue The Access Expert Bosch integration User sync stopped working whereas previously the Users and their passcodes from the Bosch Panel could be brought into Access Expert using Import Configuration. Example: In the case below, there should be 4 Users, not 2 compared to Bosch RPS.   Note: User 0 is not counted Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Bosch Panel Integration Bosch Remote Programming Software (RPS) Docker Cause There was a September 2024 update from Feenics to fix a User synchronization defect and there are pre-requisites for the User synchronization to operate normally Resolution 1. Check the version number of Access Expert that is displayed when logging in. The version should be 24.9.1.0 or greater 2. Pre-requisites for the User synchronization     a. Area Authority Assigned     b. Person assigned to the User - the person cannot be blank. This can happen if LDAP is used     c. At least 1 Area Assigned To verify: In Access Expert> Access Configuration Select Area Assighnment 1, or 2, etc. Blank Person for a User Open Bosch RPS and connect to the panel, Expand User Configuration> User Assignments 3. Check Access Expert Live Monitoring and the Docker Logs  If the Import is still not working after ensuring Access Expert client software is up to date and the pre-requisites are set, check to see if there are any entries related to the Import or Users that may help troubleshoot by using Live Monitoring in Access Expert and/or the Docker Logs. An Example of the Docker Logs: Launch Docker> Under the Bosch Service> Logs (User 2 and 4 were not coming in prior to the Sep. Update) If the above steps do not resolve the issue, please open a case with Product Support for assistance.

  Issue Cardholders are getting automatically changed from Active to Inactive (deactivated). When the LDAP/AD integration is configured to map the Active Directory attribute UserAccountControl to Card Status in Access Expert; records that have useraccountcontrol = 512 (normal active account) are getting their cards deactivated. These records should NOT be deactivated.   An LDAP query mapped to UserAccountControl Card(s) showing Inactive in Access Expert   Event History record showing the date and time the cardholder record was set to Inactive by LDAP Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Active Directory Cause A version of the LDAP service less than 24.2.1 Resolution Manually set the cardholder to Active as a workaround Ensure the LDAP service installed is greater than version 24.2.1. See the following link to a KB article showing how to "Identify which LDAP service is currently installed" : https://community.se.com/t5/Building-Automation-Knowledge/Identifying-which-Access-Expert-LDAP-integration-version-is/ta-p/480424    If the version installed is older than 24.2.1, perform the following steps: Uninstall LDAP from Windows Programs and Features Navigate to C:\ProgramData\Feenics_LDAP and delete the .dat file Restart the PC Install an updated version of LDAP from Feenic's web site: https://s3.amazonaws.com/download.feenics.com/ldap/Feenics.Keep.Installer.ActiveDirectory.msi  Test to ensure the issue has been resolved with the updated LDAP service

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Issue If you are having trouble with the screen operation, you may need to re-calibrate the touch screen. Product Line ESMI Fire Detection. Environment FFSULH1001. FFSULH1002. FFSULH1003. Cause During shipping, the touch screen calibration may become misaligned. Resolution To calibrate the touch screen, do the following: Hold down the function button on the back of the main PCB and press and release the reset button, continue to hold down the function button firmly until the calibration screen appears this can take up to a minute Once the calibration screen has appeared you will be prompt with 5 crosshairs which you must press in turn. Note: Please note when pressing these crosshairs ensure you use your hand as it has been known to cause issues using tools or stationery as pointers

Issue What SQL collation does Security Expert use? Product Line EcoStruxure Security Expert Environment Security Expert server Microsoft SQL Server Cause Need to know the SQL collation used in Security Expert databases. Resolution The default collation is SQL_Latin1_General_CP1_CI_AS. This is the only supported collation and is set by default during installation and creation of the Security Expert databases.   Changing the collation can have serious ramifications to the stability and operation of Security Expert and is not supported.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Issue Fire Panel unable to display the Media Gateway Card version in system information. Product Line ESMI Fire Detection. Environment FFSULH1007. Cause Panel message output on Media Gateway Card TCP/IP port not functioning and impacting BMS integration with the panel.  Resolution The Media Gateway Card firmware needs to be updated. Follow the steps below to update the Media Gateway Card firmware.   Prerequisites An SD card and SD card reader is required to make a bootable SD card for the firmware update files.   Prepare the SD card The first stage to update the firmware of the media gateway card is to prepare and install the firmware file onto the SD card. The media gateway card requires a micro-SD card. The firmware file is approx. 320MB, so select an SD card with suitable memory size. Format the SD card. Open up Win32Diskimager software. You should see the screen appear below. Click on the open file tab and then select the firmware file. When the firmware is selected it will populate the image file box. Click on the ‘Write’ tab and you should then get a pop-up screen shown below. Click on the ‘Yes’ tab. The firmware will now install onto the SD card. When you see the pop-up screen ‘Write Successful’ appear click on the ‘OK’ tab. The firmware is now loaded onto the SD card. Close down the Win32Diskimager software and eject the SD card form the PC. Install the Firmware Install jumper link onto the middle and top pin of X7 (as per the image below). There is a sliding cover on the socket. First slide the cover to unlock it, then hinge it up. Place the SD-Card in the socket. Hinge down the cover, then slide it to lock it as below The media gateway must be restarted to initiate the installation of firmware. This is done by pressing the reset button, shown in the picture below. The Media Gateway card has a set of 6 LEDs that indicate the status of the card. During normal operation one of the LEDs flashes regularly once each second. After a few seconds you will see a moving pattern progressing through the six LEDs. This indicates that the installation is in progress. The installation will take a few minutes to complete. Note: During this time the panel may display a fault condition that the media gateway card is not present or not working correctly. You can ignore this fault indication. When the firmware installation on the media gateway card is complete, the pattern displayed on the six LEDs will change. Instead of a moving pattern progressing through the six LEDs, all six LEDs will flash on and off together. Once you see this pattern, with all the LEDs flashing together, you should uninstall the jumper, remove the micro-SD-card, and then press the reset button. The media gateway will restart then running the newly installed firmware. It will take a few seconds for the media gateway board to achieve its normal operating state. If the panel displayed a fault indication that the media gateway board was missing, this fault should clear. The ESMI ULTIMA panel now needs to be rebooted to accept the updates from the media gateway card.13. Once the ESMI ULTIMA panel has initialised the firmware installation is now complete.  

Issue BACnet requires applications to listen on the same port across the IP subnet to receive BACnet discovery broadcasts. Two applications running on the same machine can not use the same port as the Listening Port. Product Line EcoStruxure Building Operation, Continuum, TAC I/A Series Environment Building Operation Enterprise Server I/A Series WorkPlace Tech Continuum Cyberstation Cause The site can not provide a separate machine or VM for each BACnet application, which is recommended for independent operation. Resolution With this configuration, one application will act as BBMD to receive and distribute BACnet Broadcast Messages. The other application will act as a Foreign Device, relying on BBMD to relay BACnet Broadcast messages. Once BACnet devices and the Application, configured as Foreign Device, have shared their IP and Port, messages between them will be unicast and will not pass through the BBMD. Ensure one application can be configured as a BACnet BBMD and the other as a Foreign Device. Configure one as BBMD, usually EBO Enterprise Server Configure the other application as a Foreign Device referencing the BBMD IP and Port

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Data cannot be seen on Partner Portal for RS485 devices. Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Data for the Modbus devices can be seen on third-party tools like Modscan but not on the Partner Portal. Resolution Follow the steps below if the Flex Server RS485 port is not sending any data: Ensure connections are made according to the installation instructions. Verify the correct port is configured. Double-check that the connections are not reversed. Inspect for any loose wires. Confirm the Modbus/BACnet ID is correct. Verify the baud rate configured for the end device. Check for any loose wire strands shorting on the bus or to the ground. Ensure no Modbus device is connected to the BACnet bus, or vice-versa. Confirm the number of devices in the loop matches the specifications in the installation instructions. Check if the loading of devices causes significant changes in resistance. Do not connect more than two resistors on a single bus. Ensure cables used are as per the specifications in the installation instructions.

Issue Cannot activate a license on an Automation Server although the entitlement works on other Automation Servers. The Device Administrator output is similar to the following:   Activate failed: ASEmbeddedAPI internal error: Binary response does not contain feature information Error status information: FNO server response: =V(BACK_OFFICE%DEBACK_OFFICE+]\fK%MDEVICEID|0}~;DEVICEID/jlSk\}K qq7!vi%DCH'~A%05pQWN]G|3^Jk+yaz_Kx/:Dy&w F7BWWN#`Ex|6S.d<Y^nV~@?*C.D0])"KO?[pS#GH|aMe+i|@4's9kNE\7gfocfVbRf$1VuH>sdp_JN6%4B.n|Zm$]wi9M|F8#Hrw~/L4%XU<?8o="P1S$uW6Fu5vAsAz|l>8.@XA|.'[v_ekh_P}c7 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause When an Automation Server fails in the field an RMA (Return Material Authorization) request is made, and the license is returned for re-use in the replacement Automation Server. Once this occurs the serial number of the faulty Automation Server is blacklisted to ensure that it cannot be licensed and reused. Resolution If the device was mistakenly added to the blacklist please supply the Automation Server serial number to Support. If an RMA number does not exist in the licensing system for this Automation Server, the support team can make a request to have the server removed from the blacklist.

Issue How to collect log files from the Project Configuration tool 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the PCT, log files should be provided. Resolution Collect log files through the Web interface on both Windows and Ubuntu installations: Logon to PCT server, Click Diagnostic  Click Collect logs Log starts collecting. After the log collection process is complete, the file will either be saved to the browser's default download location or a window will pop up asking where to save the ZIP file. Select the desired location then click Save   Log collector tool for PCT for Ubuntu: If the PCT web interface is unavailable, you can use the Log Collector tool to gather log files. This tool is included with the PCT installation on Ubuntu, eg. pct-2.1.1.8-log-collector-ubuntu. Give the file proper permission to be able to run as an executable either using chmod command:  chmod +x pct-2.1.1.8-log-collector-ubuntu​ or via file properties, as shown in below screenshot: Run the log collector tool. ./pct-2.1.1.8-log-collector-ubuntu​ A zip file containing the required log files will be saved in the same folder where the log collector tool is located.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Caution While removing gateway cover: Open the gateway screws and delicately remove the top cover. Take extra care during this step, as the top cover is connected to the antenna cable via a thin wire. After opening the top cover, you will be able to see the top view of the board, please insert the active SIM card in the designated slot. Once the Sim Card is properly inserted, fix the screws back and ensure that the 4G&Wi-Fi Antenna is attached properly. If the antenna cable remains disconnected from the board, then the GSM will not work. Issue SIM card not being detected and internet is not connecting automatically when SIM card is inserted inside the Gateway.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Some network service providers have a username, password and SIM PIN set by default when they issue the SIM to the customer. If the Gateway is using the SIM for internet, it requires any username, password and SIM PIN to be disabled before inserting the SIM inside the Gateway.  Resolution Contact the Network service provider directly to disable the username and password. The Network service provider can disable the username and password from the backend. For disabling the SIM PIN follow the below procedure: Steps to follow to unlock SIM PIN An example YouTube video on the steps detailed below can be seen at: How to unlock your SIM Card Upon receiving the SIM kit (note down the PUK number and also note down the SIM PIN if available) Insert the SIM card to a Mobile device/cellular device Type in the SIM PIN from the Step 1 and Unlock the SIM Navigate to the settings page – Network section - SIM settings - SIM PIN - Disable the SIM PIN option SIM CARD SETTINGS           SIM PIN DISABLED Reconfirm if the SIM PIN is disabled by reinserting the SIM from the SIM tray and check if it asks for PIN. If the SIM PIN is successfully disabled, it will not ask for SIM PIN at startup. If it still asks, repeat Step 4. Insert the SIM inside the Gateway SIM Slot and check for network connectivity and that the gateway goes online. After inserting the SIM card properly, power up the gateway and allow the gateway to boot up. This process may take up to 5 minutes. Once completed, the device should come online and can be provisioned through a partner portal   In case the SIM PIN is unavailable An example YouTube video on the steps detailed below can be seen at: How to Unlock Sim Card / Sim locked by Pin Code or PUK Code  Insert the SIM card into a Mobile device/cellular device Type in incorrect PIN more than 4 times till it asks to enter PUK code. Contact the Network Service Provider and perform the verification and obtain the PUK Code for the SIM from the Network provider directly Type the PUK code into the mobile device in the PUK code page Navigate to the Network settings - SIM PIN - Set a SIM PIN inside the settings Use this SIM PIN to Disable the SIM PIN lock. Reconfirm that the SIM PIN is disabled by reinserting the SIM from the SIM tray and check that it does not request a PIN.

Issue It is not possible to login to an Automation Server and it fails with the error "Domain Controller version too low' for certain users. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause Remnants of an EcoStruxure Building Operation domain exist in the controller where it has not been removed completely and it is set as the Default Logon Domain. Resolution Login with Administrative Rights: Use a user account with Administrative rights in the Local or another domain explicitly using the Domain name. Delete Partial Domain: Once successfully logged in, delete the offending partial domain. Retry Login: Attempt to log in again. Additional Information: Ensure that the domain is completely removed to avoid future login issues. Verify that the Default Logon Domain is correctly set after removing the partial domain.

  Issue There are issues for Flex Server to synchronize time with the Real Time Clock (RTC). Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The RTC parameter fails the synchronization test.  Resolution Check the voltage of the coin cell using a multimeter. If the voltage is less than 3.3V, replace the coin cell. If the voltage is equal to or greater than 3.3V and the test still fails, report the issue to technical support.

Issue EcoStruxure Building Activate Flex Server fails the Wi-Fi Signal Strength test.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause If the Flex Server Gateway is configured on Wi-Fi, it must achieve a RSSI value greater than -75 or value does not go below -80 more than 3 times. If these conditions are not met, Gateway will fail the test.   Resolution Below steps should be checked/followed to check the issue: Check Network Type: Ignore this issue if gateway is using a GSM network Verify Wi-Fi Receiver: Ensure the Wi-fi receiver is properly inserted into the USB port of the gateway Optimize Placement: Make sure the Gateway is near or in line of sight with the router to improve signal strength. Restart Router: Restart the router and check with your network provider for any issues.

Issue Are stainless steel pockets suitable for use in seawater/saltwater applications? Product Line Field Devices. Environment STR Sensor. Cause Customer asking if stainless steel pockets are suitable for use in seawater/saltwater applications. Please note that the answer would need to cover both static (stationary) water and flowing water in the pipe, because seawater/saltwater has different effects on metals depending on whether it is moving or not. Resolution Highest corrosion class is Class III for stainless steel, which seems not suitable for intended application.   ISO 12944 Impact Interior Exterior C1 Very low Heated buildings with clean air, such as offices, shops, schools, hotels, etc. None C2 Low Buildings not heated, where condensation may occur, such as warehouses and sports halls. Atmosphere with low pollution. For example in the country. C3 Middle Buildings for production with high atmospheric humidity and some air pollution such as food manufacturers, breweries, dairies and laundries. Urban and industrial areas, moderate sulphur dioxide pollution. Coastal areas with low salt content. C4 High Chemical manufacturers, swimming baths and ship- and boatyards by the sea. Industrial areas and coastal areas with moderate salt impact. C5-I Very high - Industry Buildings or areas with almost permanent condensation and with high pollution. Industrial areas with high humidity and aggressive atmosphere. C5-M Very high Buildings or areas with almost permanent condensation and with high pollution. Industrial areas with high humidity and aggressive atmosphere.  

Issue Building Commission (EBC) self closes at Login screen in Windows. It seems to be after application is unused for an extended period of time. Product Line EcoStruxure Building Operation Environment Building Commission Tool Cause There is a fault in Microsoft.ui.xaml.dll as observed in the Windows Event Viewer. Resolution Uninstall the application via Windows Add or Remove Programs Reinstall the application via the Microsoft Store Open this link in a browser Building Commission - Free download and install on Windows | Microsoft Store Click Open in Store App button in upper right by sign-in

  Issue How to program the function buttons in Esmi Fire Panel Product Line ESMI Fire Detection Environment FFSULH1001. FFSULH1002. FFSULH1003. FFSULH1005. Cause Customer wants the specific buttons for specific actions. Resolution Up to 24 customer specific, on-screen function buttons may be configured to provide control, disablement and engineering functions. The function buttons can be configured to be either available or hidden for each log-in profile. The following procedure describes how to: Set function button attributes/properties. Allocate function buttons to user groups.  Create password specific user accounts for inclusion within a nominated user group. Setting attributes Function buttons (inputs) may be set to operate by association to output devices with the same properties e.g. a security input will activate any device that has security ticked as part its output properties, or as part of a cause-and-effect rule where the function button is the “Cause”.   With Loop Explorer open, select the Configure menu button and select System Manager to open the function button configuration page. Select the 'Details' button to open the properties section of the function button that you wish to configure. Note: Input Properties The properties page allows the user to configure the input action and associated messages, to set individual colours and either to work as a latched (cleared on user interface reset) or toggled action (press function button to operate and again to turn off). Mapping to zones is optional, and the location text is the name given to the function button when completed. Feature Groups There are 4 default user groups that can be configured with specific permissions for different users.     When configured, the function buttons will be included as selectable options in each of the feature groups. It should be noted that if a function button is allocated to the Logged-out group, then it will be present alongside the User Options button when all other user groups have been logged out. Note that at this level then the user options are limited to system information and basic panel tests such as display colour and LED function. Function buttons allocated to User level 2 and 3 may be accessed using the default login codes. If users are to be allocated unique numerical codes, then it would be advisable to change the panel default level 2 and/or 3 codes where required.

Issue Need to analyze Modbus RTU communication packets for SpaceLogic controllers. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Multi-purpose Controller (MPC) Building Operation Room Controller (RPC) Cause MP and RP controllers do not support packet logging or viewing on their modbus serial ports. Additionally, RP controllers lack transmit/receive LEDs for Modbus, making diagnostics more difficult. For differences between Automation Server and MP/RP controller Modbus operations, refer to the article: Modbus in the MP and RP Controller Introduction  Resolution Wireshark Installation Install the latest Wireshark application from: Wireshark • Go Deep | Download Click on the "download" icon and select your operating system Launch the downloaded setup file to install Wireshark. The default installation options can typically be used, unless the user has a specific reason to select others. Modbus RTU capture extension for Wireshark The Github project can be found at: GitHub - jzhvymetal/WiresharkSerialAdapter: Wireshark Serial Adapter for Windows Navigate to the latest version and download WireSharkSerialAdapter.exe  With this file downloaded, navigate to the Wireshark application folder and locate the following subfolder. If it does not exist, create it.  Copy WireSharkSerialAdapter.exe into this folder. NOTE: This is not an executable to be launched by the user. Wireshark will execute it as an additional capture option. USB-to-RS485 communications adapter Install the USB-to-RS485 adapter to PC. Wire the RS-485 adapter to the SpaceLogic RS-485 port to be captured. Check Device Manager -> Ports to determine the COM port number it is using. Wireshark Configuration Launch the Wireshark application. The initial start-up screen will list the available capture ports. This list will be different for each user’s computer, depending on its configuration. Below is an example of what this screen looks like:  In this list, Serial Port Adapter (WireSharkSerialAdapter.exe) should be an option. Click on the settings icon  to the left to bring up the setup options:  Launch Windows Device Manager to confirm the COM port assigned to the connected USB-485 adapter Select this COM port and set the baud rate, byte size, parity and stop bits of the Modbus RTU channel to be monitored. Use the Interframe settings shown in the screenshot above. Select User DLT 147 as the Wireshark DLT. Save these settings. Returning to the main screen, select Preferences from the Edit pull-down menu and navigate to Protocols:  Expand Protocols and select DLT_User. Click on Edit to add an entry to the Encapsulation Tables. Click the “+” button to add a DLT  Select User 0 (DLT = 147) and manually edit the Payload dissector to be mbrtu:  Click OK and return to the main screen Wireshark Capturing With the COM port properly configured, a traffic capture is initiated by double-clicking the selected COM port. The content of the capture will depend on the connected devices. The following is an example of the active window panes:  The main pane is an overall summary of the Modbus RTU traffic, with a brief description of each message type. When a frame is selected in this pane, the lower-left pane contains a breakdown of the packet content by field-type, and the lower-right packet is the packet content in hexadecimal format. The selected frame number is displayed in the packet details frame on the lower left, as well as the contents of the Modbus message. In this example, the results of the Modbus Read Holding Request for 6 registers is shown. The Wireshark capture is stopped by clicking on the red square, second from the left

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When hosting objects from EWS/Smart Connector, such as Security Expert, into EcoStruxure Building Operation (EBO), additional or mismatched object names can result in unresolved bindings and duplicate EWS IDs. Common symptoms include:  - Duplicate EWS IDs with different names - Unresolved or broken bindings - Binding loss after deleting containers   Duplicate EWS IDs with different names Unresolved or broken bindings     Product Line EcoStruxure Building Operation, EcoStruxure Security Expert. Environment EcoStruxure Building Operation Enterprise Server (ES) Security Expert Smart Connector Integration EcoStruxure Web Service (EWS) Cause Typical reasons for this to occur: Hosted object names do not match those in Security Expert. Deleting containers without proper renaming can cause binding loss. Resolution   Best Practices for Future Hosting Always rename the hosted object in EBO before rehosting from the hardware folder. This ensures that existing bindings are preserved. Avoid hosting the entire `SecurityExpertServer` container—only host changed or new objects. For Unbound or Irrelevant Objects: - If objects have no bindings, naming is not critical from an EBO perspective - Delete the container and rehost the object from the **Hardware folder**.   To Retain Existing Bindings  Identify the correct object name in the Hosted Containers folder  Copy the name to avoid typos. Delete the duplicate object with the correct name. Rename the existing EWS ID to match the copied name. Save the rename Verify bindings: Right-click the renamed object Select Delete Click Show References Confirm bindings are still valid. Click No to cancel deletion. Repeat this process for each object (inputs, outputs, doors, etc.) that has existing bindings.