Issue The Command Request / Command Response window is not available when using the Niagara G3 DMS driver. Product Line TAC IA Series Environment Niagara G3 Microsmart driver Cause This feature was present in the Niagara R2 driver but was not carried over to the Niagara G3 driver. Resolution The only available option is to tunnel to the Microsmart controllers using OPRIF for command requests and responses.

Issue UltiVist cannot communicate with the DMS panel over a serial connection due to incorrect port settings. Product Line TAC IA Series Environment UltiVist Software DMS Panel Cause The DMS panel’s serial COM port settings were reset to factory defaults, which do not match UltiVist’s required configuration. Resolution Configure the DMS panel’s serial COM port with the following settings to enable communication with UltiVist: Parameter Value Port PORT1 (typically) or PORT2 Baud Rate 9600 Stop Bits 1 Data Bits 7 Parity Even Mode Multi-drop Modem None Note: PORT1 is commonly used for UltiVist connections. Ensure these settings are applied after any factory reset.

Issue In a Niagara R2 and DMS integration, some points in the station are not updating after changes to the DMS database. Product Line TAC IA Series Environment Niagara R2 (all versions) DMS (all versions) Cause Controllers and associated DMS points were deleted as part of housekeeping. When points are deleted, added, or re-ordered in the DMS database, the Niagara R2 station does not automatically refresh its point list. Resolution Whenever DMS points are modified or the DMS database is downloaded via OPRIF, perform a re-learn of the DMS panel from the Niagara R2 station: In Niagara Workbench, right-click the DMS container. Select Go > PointListManager. Click GetPointListFromDevice to upload the current DMS database into the station. Important Notes: These steps will not affect existing objects under the specific DMS container. For detailed instructions, refer to the I/A Series Niagara DMS Serial Driver Engineering Guide (F-27071), section “Re-learning The DMS Panel.”

Issue Clarification is needed on whether the Ethernet NIM (Network Interface Module) settings are included when performing a DMS database backup. Product Line TAC IA Series Environment DMS-3500 with Ethernet NIM OPRIF 11.4 & 11.6 Cause Backup requirements can be confusing because the DMS database, controller databases, and NIM configuration are stored separately. Users may assume a single backup command covers all components, which is not the case. Resolution A complete DMS backup consists of three steps, all performed using OPRIF: Backup the DMS database Backup each individual MicroSmart controller database Backup Ethernet NIM configuration data separately Important Note: Echelon NIMs do NOT require backup. Ensure all three steps are completed during maintenance to guarantee full system recovery capability.

Issue On a DMS jobsite, the Operator Interface (OPRIF) does not display MicroSmart controllers on the screen. Although multiple controllers are confirmed to be communicating with the DMS, they do not appear in the controller list in OPRIF. Product Line TAC IA Series Environment OPRIF DMS MicroSmart Cause OPRIF displays controllers in groups of 32 per screen and reserves address slots even if they do not exist. If controller addresses start at 33 or higher, the first screen appears blank because it only shows addresses 1–32. Resolution Use the Page Down and Page Up buttons in OPRIF to navigate between controller lists: Page 1: Addresses 1–32 Page 2: Addresses 33–65

Issue A jobsite is visited periodically, and it appears that certain database elements have changed since the previous visit. These elements are not expected to change (unlike setpoints or schedules). The question is whether there is a built-in feature in a DMS panel or the OPRIF programming tool that provides database analysis. Product Line TAC IA Series Environment DMS OPRIF Cause The DMS product does not include built-in database analysis tools. Historically, supervisory computers provided this functionality using tools like UltiVist or SIGNAL, which could analyze databases and save information for future review. Resolution No built-in database analysis feature exists in DMS panels or OPRIF. When only OPRIF is available: Take screenshots of point configuration screens to store values for later comparison. DMS databases are not formatted for offline viewing, so direct comparison between copies is not supported. To compare two database states: Use a second DMS panel as a reference. For advanced analysis, consider using a supervisory computer with compatible tools (e.g., UltiVist, SIGNAL) if available.

Issue What is the best way to completely clear an existing database from DMS3500 and DMS350A before reinstalling? Product Line TAC IA Series Environment DMS3500 DMS350A Cause When reinstalling a database, remnants of the previous database may cause conflicts or unexpected behavior. A full hardware-level clear is required to ensure the old database is completely removed. Resolution For DMS3500: Connect via OPRIF and enter Command Mode. Type the command: DBCLR After completion, log back into the DMS3500 and begin the new database installation. For DMS350A: Sign on using the keypad. Enter the command: DBCLR For each connected DCM: Set all 8 toggle switches to ON. Cycle power to the DCM. Wait 10 seconds, then re-address the DCM and cycle power again. Once complete, use OPRIF to start the database installation. Note: The DBCLR command combined with setting toggle switches to ON is considered a hardware-level database clear, ensuring no residual data remains.

Issue Customers need guidance on migrating DMS-3500 systems to the Building Operation platform. Product Line EcoStruxure Building Operation, TAC IA Series Environment DMS-3500 EcoStruxure Building Operation Cause The DMS-3500 system and its databases are not compatible with Building Operation. Schneider Electric does not provide a supported migration path for these legacy systems to Building Operation. Resolution   Direct migration is unsupported. To integrate DMS-3500 data into Building Operation, use a Niagara device as a gateway between the two systems.  

Issue A MicroSmart controller with revision 9 firmware needs to broadcast a point value to other MicroSmart controllers running revision 10 and 11 firmware under the same DMS. The broadcast is not working as expected. Product Line TAC IA Series Environment MicroSmart controllers connected to a DMS Cause Peer-to-peer data sharing was introduced starting with revision 10 MicroSmart firmware. Controllers running revision 9 do not support peer-to-peer communication, so they cannot broadcast or receive values directly. Resolution To enable value sharing: Link the sending point and receiving points to the DMS. Use the sending DMS point in conjunction with the receiving DMS point within the programming logic. The value will then propagate down to the MicroSmart controllers through the DMS.

Issue Backup and Restore assures that Building Operation server data can be restored after a hardware failure or data loss. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Enterprise Server Automation Server Workstation Cause Restore is the process of restoring data to an original or former state. Using restore, you can revert back to a previous snapshot of the server data despite any configuration changes made since the last backup. In Building Operation, restore is designed to be a manual rather than an automatic process to avoid the accidental overwriting of current server data. For convenience, Building Operation displays only the backup files that apply to the selected server.  For more information on making a backup, see Backup of Struxure EcoStruxure Building Operation AS and ES. Resolution Restore an Enterprise Server Backup Set If restoring to a previous snapshot of the database that is currently running, start with step 6. If restoring a database that is different from the one currently running, start with step 1. Launch Building Operation Software Administrator Click the Stop Service button and then click OK. Go to the Enterprise server database folders; C:\ProgramData\Schneider Electric EcoStruxure\Building Operation X.X\Enterprise Server Change the name of the current database folder to something that identifies it with the project's name (Example outlined in red: db changed to Old_db). Make a duplicate of the "db - Copy" folder (Example outlined in orange). It is important to always maintain a clean database folder by making copies. After first installing EBO, a copy should be made of the original "db" folder. Copies of this folder should be made before restoring databases or creating new ones from then on. Change the name of the "db - Copy" folder to "db" (Example outlined in blue: db - Copy changed to db).     Launch Building Operation Software Administrator, click Start Service, and then OK.   Launch EcoStruxure WorkStation and log into the enterprise server Select the enterprise server and go to the Main Menu > Actions > Restore.   In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Note: If a backup set is seen in red, it means that the backup is not compatible with the current version of the server. The backup has to be the exact same version as the server including any hotfixes or service packs.   Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed-up data will be available. Note: The server name is part of the restore data. Therefore, if you rename a server after a backup, a restore process will revert back to the previous server name.       Replace an Automation Server with a Restore Note: The automation server restore should be done by logging directly into the automation server. Launch StruxureWare WorkStation and log into the enterprise server or the automation server;   Select the automation server and go to the Main Menu > Actions > Restore.   In the Restore Options window, there are a few different options that can be selected. If the desired .xbk file to be restored has already been imported into the current database, it will be visible in the "Available restore points" window. To import the file into the database, select the "Import Backup Set" button and browse to the .xbk file. After selecting the backup set, choose to perform a Configuration only or All data restore. Click Restore. Select Yes to restore. Click Close, the restore is now complete. The server will restart, causing the current user to be logged off. After a couple of minutes the server will restart, log into WorkStation and the backed up data will be available.

Issue Steps to backup within EcoStruxure Building Operation (EBO) Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation site with AS and/or ES Backup, Automation Server, Enterprise Server, Workstation, .xbk, xbk, backup set, db backup, db_backup Cause Must an AS or ES be stopped in order to do a full backup? Is a raw copy of the database folder from within Windows Explorer sufficient for backing up an ES?  For instructions on how to restore a backup in StruxureWare/EcoStruxure Building Operation, see How to restore a EBO server backup set. Resolution No need to stop AS or ES: EBO freezes the database during backup. Configuration changes are queued until backup completes; historical data is buffered. Do not use raw folder copy: Always use the built-in backup function. Three rules to remember: Restores must use the same software revision. Do not rename the backup set. If renaming is needed, zip the backup and rename the zip file. Default backup schedule: Every Sunday at 1:00 AM. When creating a backup, give the appropriate prefix to the standard name format. See screenshot below. The backup file will be shown as the screenshot below. Should the backup name need to be changed, then either create a new backup, or zip up the backup using the new name. Backup Procedure Enterprise Server (ES) Automation Server (AS) In Workstation, select the Server in the System Tree. Go to Actions → Backup. In Backup Options: Include column: Select servers to include. Backup content: All Data: Historical + configuration databases. Configuration only: Configuration database only. Add a Backup set description (up to 255 characters). Click Backup. Verify that each backup succeeded and click Close. Backup file location: C:\ProgramData\Schneider Electric\StruxureWare\Building Operation 1.X\Enterprise Server\db_backup\LocalBackup or C:\ProgramData\Schneider Electric\EcoStruxure\Building Operation 2.X\Enterprise Server\db_backup\LocalBackup   Backup Files of AS: Log in to AS from Workstation. Navigate to System → Backup and Restore → Backup sets → Local. Right-click the backup file → Save To... (choose folder on HDD).

Issue When planning an upgrade to EcoStruxure Building Operation (EBO) 7.x or the latest version for existing sites, users often want to complete engineering work before applying commercial licenses through Software Companion. Product Line EcoStruxture Building Operation Environment EcoStruxture Building Operation Project Configuration Tool 2.0 Cause Software Companion only provides Engineering licenses for new sites, but not existing sites. This limitation means that existing sites cannot be engineered without applying the commercial license first. Resolution To engineer or upgrade existing sites before applying commercial licenses, use Project Configuration Tool (PCT) v2: PCT is a standalone engineering platform, independent of the live system. It allows flexible design and upgrade workflows without impacting production. After engineering or upgrading: Deploy the EcoStruxure BMS server to the live site directly from PCT, or Use an XBK backup and import for deployment. Recommended Steps Download and Install PCT v2.x Windows Installer – v2.2.1.12 Ubuntu Installer – v2.2.1.12 Release Notes v2.2.1 Create or Import Existing Site in PCT Use the Import XBK backup feature for existing sites. Perform Engineering and Upgrade Tasks Configure controllers, graphics, and logic as needed. Validate compatibility with the target EBO version. Deploy to Live Site Either direct deployment from PCT or export XBK and restore on the live server. Additional Resources Project Configuration Tool – Support Tools Specification Sheet

Issue After installing and configuring the LP4502 (online) and downstream devices per the Installation instructions, KGC devices remain offline. (See highlighted snapshot below) Link to Kone Integration Instructions: Access Expert Kone Elevator Integration  Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Kone Elevator Integration LP4502 Comm2 with Micro-B USB adapter (Pluggable USB2-OTGE100) Cause Using the LP4502 comm2 port with a Micro-B USB adapter for elevator communication on a separate subnet is NOT supported. Note: Other Elevator integrations (Thyssen Krupp, Otis) support this setup, which can cause confusion. Resolution 1. Use Comm1 for LP4502 to connect to the internet and site instance. 2. Ensure LP4502 and Kone elevator equipment are on the same subnet. 3. Configure site IT switch: Block internet-to-Kone communication. Allow local traffic on port 2005. KGC downstream IPs must communicate with the LP4502 primary NIC IP. Once completed, the LP4502 and the KGC downstreams will come online and will communicate with the Kone Elevator equipment. Summary KGC downstream devices fail to come online when LP4502 is configured using Comm2 with a Micro-B USB adapter. This setup is not supported for Kone Elevator integration.  

Issue What is the maximum number of site codes that can be loaded into a Continuum system? Product Line Andover Continuum Environment AC-1 and AC-1 Plus modules Cause Network design limitations Resolution There is no limit to the number of site codes that can be loaded in a Continuum system.  However, each door can contain a maximum of four (4) site codes.  In the case of an AC-1 module, if it loses communication with its associated Netcontroller, it will only allow access from the first two fields.

Issue When opening (pulling up) the sunblind, it stops at the end of runtime and then rolls back down. Similarly, when closing (pulling down), it stops at the end of runtime and then rolls back up. Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment Lonworks devices including REG-N MSE4 (SVEA 32237-346) Sunblind actuators Cause The actuator is preconfigured for venetian blinds, which include lamella angle adjustments. For simple sunblinds, these parameters cause unintended motor actions after reaching the end position. Resolution For non-venetian blinds: Set the following parameters to zero: UCPTdownPanelAngle UCPTupPanelAngle UCPTpanelTurnTime UCPTpanelTurnTimeBottom Ensure SNVTsetting commands have zero in the rotation part. This disables unnecessary panel angle adjustments and prevents rollback after full movement.

Issue A single folder on a jobsite computer contains multiple DMS backups performed over several years. Each backup consists of multiple files, but they are not grouped by name or date, making it difficult to identify and retrieve complete backups. Product Line TAC IA Series Environment DMS35, DMS350A, and DMS3500 (revisions 9, 10, and 11) Cause Multiple backups were saved in the same directory without a naming convention or date-based grouping, resulting in a disorganized collection of files. Resolution A complete DMS database backup consists of the following files: For DMS35 and DMS3500: filename.IOC – Stores DMS point IDs, records, and alarm parameters. filename.UC – Stores DMS point configuration elements. filename.PG – Stores DMS tables and schedules. filename.UDP – Stores UDPs in the DMS panel. For DMS350A: Includes the four files above plus: filename.Dxx – Stores DCM tables, schedules, and other elements (where xx = DCM address 01–32). filename.Uxx – Stores DCM UDPs (where xx = DCM address 01–32). Recommendation: To simplify future retrieval, create a folder for each backup and name it using a clear convention (e.g., Backup_YYYYMMDD_SiteName ). Move all related files into that folder immediately after performing the backup.

Issue Information is needed about the Access Expert Kone Elevator Integration Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Kona Elevator integration information  Resolution Overview: Destination Dispatch is a licensed feature for Access Expert and used when customers are modernizing their elevator systems or deploying newer ones which do not utilize the relay-based approach for floor control and selection. Within Access Expert, 3 different elevator platforms are supported which include Otis, Kone and ThyssenKrupp. For this document, we will focus on a KONE deployment. It is important to note that a single Access Expert can support multiple integrations at the same time. The KONE integration supports up to 128 total floors of control. When using front and rear entry points within the elevator cabs), each entry point is considered a separate destination. This means a 32- story building using front and rear entry points will result in 64 individual destinations.   A KONE protocol was created so that the LP controllers can manage access for the KONE Elevator Group Controller. Mercury will support configuration for Destination Operation Panels (DOPs), Car Operation Panels (COPs), and turnstiles. This feature is supported on the LP4502, and EP4502. The support for KONE Elevators was added in firmware 1.25.5.   Prerequisites: 1. Access Expert System 2. KONE Destination Dispatch License - FN-DEST-KONERS 3. Appropriate Reader Licenses 4. AX-LP4502 5. Coordination with the Elevator Contractor A KONE Elevator Destination Dispatching System mode was created within Access Expert so that the LP4502 intelligent controller can inform a KONE DEC (Destination Entry Computer, E.g. touch screen or keypad) allowed and authorized floors for a cardholder. This feature is only supported on the LP4502. Note: Other Elevator Destination Dispatch integrations i.e. Thyssen Krupp and Otis use the 2 nd port on the LP4502 controller to communicate with the elevator equipment on a separate subnet. ** The Kone Destination Dispatch integration does NOT support using the 2 nd comm port on the LP4502 to communicate with the Kone elevator equipment. If you attempt to do this, you will be unable to connect to the KGCs, and they will not come online. If you use the Kone elevator simulator for testing, there will not be any response from the KGCs even though you can ping the IP addresses.   Controller Page 1. On the LP4502 controller page, navigate to the "Destination Dispatch" Tab. 2. Select Kone. 3. Enable "Has front and rear floors" if your Kone setup has front and rear floors. Make sure to take into consideration this flag when assigning elevator floors access. It is also recommended to consider the door when creating names. Examples like 2F or 2R are beneficial to system operators. 4. Set the Maximum Cabin Configurations. This is the number of Kone Cabin Access configurations that can be stored on the controller. 5. Press Save. 6. From the "Add Downstream" dropdown, select Kone KGC under the network port. 7. Enter the Display Name to be applied to be used.  8. Enter the KONE primary KGC IP address and Port. 9. Leave 2005 as the default port number. Press Save 10. Repeat steps 6 to 8 for the Backup KGC. 11. Issue a "Push Controller Database" command.   Reader Page Once the Interface Controller has been saved, add/Navigate to a reader attached to the Controller, and move to the elevator tab. The Reader does not reside on the KONE KGC downstream. The KGC downstream is only used to configure the controller with the Primary/Backup KGCs. The readers must be on the regular Mercury downstream modules or attached to the LP4502. Because of this, the actual reader setup is similar to a regular door/elevator deployment with the addition of new settings on the Elevator Tab. Once the Elevator Type is set to Destination Dispatch, a series of settings will be enabled and displayed. You will be presented with a WARNING Message when the Elevator Type is selected. This message is normal and you should select YES. 1. On the reader page, navigate to the "Elevator" tab. 2. Select "Kone Destination Dispatching" as the Elevator Type. 3. Select the Kone Operation Type. Please note that Kone does not support mixing Remote Call Giving Interface (RCGIF or turnstiles) with Destination Operation Panel (DOP) and/or Car Operation Panel (COP). Only one is supported at a time. 4. Depending on the Operation Type, specify the fields. 5. If desired, select an Override Elevator Access Level. This will allow a set of floors to be public during defined schedules. 6. Press Save. Kone Cabin Access Page 1. Navigate to "Access Configuration" on the Main Ribbon bar. 2. Go to "Kone Cabin Access". 3. Click on "Add Kone Cabin Access". 4. Enter a Display Name. 5. Enter the allowed cabins (up to 255). You can use the following formats to enter values: 1-10,15,16. 6. Press Save. Person Page Once the reader has been saved navigate to the person(s) who you want to grant access to the destination dispatch and select the new destination dispatch tab at the bottom of the page this will take you to a new Destination dispatch tab. To add an Elevator user setting, simply select the elevator type you wish to grant access to and click the add button. You will be prompted to select a controller. If there are no active LP4502 elevator controllers, then the dropdown will be empty meaning the user needs to add a valid controller. 1. On the person page, navigate to the "Destination Dispatch Settings" tab. 2. On the "Kone Settings" tab, click on "Add Kone Setting". 3. Select the Kone controller and press OK. 4. Enter the Default Floor. 5. Enter the Default Floor Side. 6. Select a Cabin Access 7. Select the Kone Elevator flags to be applied to the person. 8. Press Save.  *Users must configure the Instance Settings to reflect the correct number of floors. The Cab used will be sent by the Kone system to Keep on an 'Access Granted' and displayed in event data. Masks Kone has Global and Specific Masks that are used when setting schedules. These can be set and cleared by right-clicking on the controller and selecting the appropriate option. Setting the Global Mask opens the Global Mask Configuration window. To add a floor configuration, click the "Add Floor Configuration" button, then select the desired floors. From there the options for each floor can be selected by setting the appropriate flags for the floor. Click "OK" to save the changes. Other Information: Each Elevator Manufacturer has specific settings, commands or fields when deploying the Destination Dispatch integration. The following are specific to KONE: Supported Reader Types: 1. Destination Operation Panel (DOP) – Destination operation panels are located outside of the elevator car. Each of these will be configured as a separate reader. 2. Car Operation Panel (COP) – Destination operation panels are located inside the elevator cab. Each of these will be configured as a separate reader. 3. Turnstile (RCGIF) – Turnstiles are half-height sensor barrier solutions designed for public and commercial buildings and airports. Each turnstile will be configured as a reader and must use a Mercury reader port.

Issue Will we be able to use our Schneider Electric Workbench (Tech Laptop) to connect to the Honeywell Supervisor? Product Line TAC IA Series Environment I/A Series AX (all versions) I/A Series N4 (all versions) Cause The NiCS statement within the license controls the sharing of data and usage of Workbench on a G3 (AX) platform. Resolution The answer depends upon the NiCS statement within the Honeywell Supervisor license. If the Honeywell license accept.wb.in statement is open, the SE brand Workbench would be able to connect and engineer. Based on past experience, the accept.wb.in statement is typically set to webs and can only be accessed by a Honeywell licensed Workbench. The NiCS statement for the Jace is setup to prevent connection by a non-SE brand Workbench. The statements that control sharing of data (accept.station.in and accept.station.out) have always been open. Unfortunately prior to AX version 3.6, the Niagara driver point discovery process utilized some Workbench functionality to perform the connection and use basically defeating the main purpose of the NiCS statement. This meant that the points needed to be added manually. The software was corrected in 3.6 to allow discovering of points regardless of the NiCS accept.wb.in statement. The points will be able to be discovered with the Honeywell Supervisor as long as AX version 3.6 or higher is being used.

Issue EBO Automation Servers may fail to synchronize time with configured Network Time Servers. The system log reports: chronyd[1566]: Can't synchronise: no majority This error occurs when multiple configured NTP servers report significantly different times, preventing the NTP service from establishing a consensus. Product Line EcoStruxure Building Operation Environment Building Operation Automation Servers Cause EcoStruxure Building Operation uses chronyd as the time synchronization daemon on Automation Servers. chronyd is part of the Chrony suite, designed for fast and accurate time sync, especially on embedded systems or devices with intermittent connectivity. Why the Error Occurs: Equal Weighting of Servers: chronyd treats all configured NTP servers equally. There is no concept of “Primary” or “Secondary” in its logic. Quality-Based Evaluation: chronyd continuously assesses each server based on: Round-trip delay Jitter Offset Historical stability Majority Consensus Requirement: chronyd attempts to find a majority agreement among the sources. If the servers report significantly different times, and no consensus can be reached, synchronization fails with the error: Can't synchronise: no majority No Failover Logic: chronyd does not switch between servers. It uses both the Primary Network Time Server and Secondary Network Time Server concurrently to calculate the most accurate time based on latency and jumps.  Example Scenario: If Server A reports UTC+10:00 and Server B reports UTC+10:05, chronyd may reject both if it cannot determine which is correct, resulting in no synchronization. Resolution 1. Use a Single Reliable NTP Server Configure only one NTP server to avoid conflicting time sources. This ensures chronyd has a clear reference and avoids “no majority” errors. 2. Ensure NTP Server Stability To maintain reliable time synchronization, verify the following: Reachability Use ping <ntp_server> from a device on the same subnet as the AS to confirm the server is reachable. Ensure UDP port 123 is open for NTP traffic through any firewalls. Time Accuracy Use tools like ntpq -p <ntp_server> or chronyc sources to check the server’s reported time and offset. Avoid servers with large offsets or jitter values. Latency Prefer servers geographically close to the site or hosted within the same network. High latency can cause chronyd to reject the server as unreliable. Consistency Ensure the NTP server is synchronized with a reliable upstream source. Avoid mixing public and private NTP servers unless they are known to be in sync. Redundancy (if needed) If multiple servers are required, ensure they are synchronized with each other. Use trusted pools like NTP Pool Project for reliable public servers. Monitoring Periodically check synchronization status via WebStation or system logs. Look for chronyd messages indicating sync success or failure.

Issue Customer is unable to install the Security Expert Mobile app on newer Android devices. The app does not appear in the Google Play Store. Reported devices and OS versions: Samsung A15/A16 running Android 16, OneUI 7 Samsung S22 Ultra running Android 15, OneUI 7 Product Line EcoStruxure Security Expert Environment  Application: Security Expert Mobile App Platform: Android devices Store: Google Play Store Affected OS: Android 15 and Android 16 UI Version: OneUI 7 Cause The updated version of the Security Expert Mobile app has not yet been released on the Android Play Store. It is undergoing Cyber Security penetration testing and review, which is expected to complete by end of Q1 2026. Resolution Currently, the Security Expert Mobile app is not available for download on Android. Follow these steps for a workaround: Use the Protege Mobile app as an alternative: Go to the Google Play Store link. Download and install Protege Mobile. Log in using existing Security Expert credentials: Open the Protege Mobile app. Enter your Security Expert username and password. Confirm connectivity to your Security Expert system. Plan for future availability: The official Security Expert Mobile app for Android will be released after the Cyber Security review process (ETA: end of Q1 2026).