Building Automation Knowledge Base

Issue The “User Last Active” field does not update when users access controlled elevators using their access cards. As a result, users who primarily use elevators are incorrectly marked as inactive and automatically disabled after 90 days, despite regular use. Product Line EcoStruxure Security Expert Environment Security Expert Elevator integrations (e.g., OTIS, low-level relay) User inactivity policies (e.g., auto-disable after 90 days) Cause The “User Last Active” feature is designed to track access events at doors or keypads. When a reader expander is configured in elevator mode, the system does not associate elevator access with standard access events. Therefore, elevator usage does not update the “User Last Active” timestamp. Note: The current documentation does not clearly state that elevator access is excluded from this feature. It only references doors and keypads, which may lead to confusion. Resolution If tracking elevator access as part of user activity is required, we recommend submitting a feature request through your local Solution Category Management team. This ensures the request is formally reviewed and prioritized for future development.   Workaround: Create a Report of Disabled Users Open the User Report. Add a filter: Disable User equals Yes disabled user filter Save the report layout for future use. For detailed steps on applying filters in reports, refer to the Security Expert Community Post Security Expert User Reports.

  Issue It is not clear if an INET SubLAN device, such as an MCU, is counted as a connected device for licensing purposes. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation version 7.0 onwards Cause With the re-introduction of INET in EBO 7.0, it is unclear how INET SubLAN devices contribute to the connected device license count.  Resolution INET SubLAN devices below a host INET device increase the connected device count. As a result, a connected device license is required for each SubLAN device. Ensure that your system has sufficient connected device licenses to accommodate all INET SubLAN devices added under host INET controllers.

Issue The Otis Destination Dispatch integration with Access Expert is not enforcing badge requirements for access to restricted floors. Users can select any elevator key without presenting a badge. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Mercury EP/LP4502 controller Otis Destination Dispatch elevator Compass System Cause The issue stems from missing routing table entries in the Mercury EP/LP4502 controller. These entries are essential for enabling communication between the Otis system and the Access Expert controller, which is required to enforce badge-based access restrictions. Resolution To resolve the badge enforcement issue: Verify Routing Table Entries on the LP/EP4502 controller’s web interface. Ensure the following entries are present: 192.168.50.0 – Enables communication with the Otis Compass Server. 192.168.1.0 – Enables communication with the Otis Destination Entry Computer. Important: If either entry is missing, the systems will not communicate properly, and badge enforcement will fail. Refer to the Hardware Setup section in the integration guide for detailed instructions: Access Expert Otis Elevator Integration Guide   Detailed instructions for installing the Otis Destination Dispatch Access Expert Integration can be found in the Access Expert Otis Elevator Integration with Destination Dispatch Knowledge Base article.