Building Automation Knowledge Base

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 After installing the Feenics Keep Bosch Service to integrate Bosch panels with Access Expert the service will not start Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Bosch Service and panels Cause A configuration issue is preventing the service from starting successfully Resolution The Feenics Bosch Service will fail to start for a number of reasons: 1. Check that the Feenics Keep Bosch Service exists and hasn't been deleted. "C:\BoschService" 2. The service is unable to authenticate to the Access Expert Instance.  Double-check the username and password being used for the service. Ensure they haven't been recently changed or the username and/or password is correct. Typically the username is Bosch with a configured password. 3. While attempting to start the Bosch service open Live monitoring and see if there is a failed login attempt or other related errors. 4. Open the Windows application log on the PC that has Access Expert and the Bosch service installed and check if there is an exception or a similar error like the following: 5. Install and use the SEQ Log to troubleshoot For Install Instructions for SEQ, see the following article:  https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-Installing-SEQ-Logs/ta- p/436521  Once installed, run the SEQ Log http://localhost:5341 while attempting to start the Bosch Service and see if errors are being posted. Example:   6. Check the last ping from the Bosch service to the Feenics host API : This date/time will give an idea of the last successful ping which can help target what may have been changed on the system or network that has affected the service. 7. Run the telnet command to access the Feenics host server If the DOS page is blank/black after hitting enter on the telnet command, that is a good sign. If there are any errors these can be a clue as to what is happening. If a firewall is blocking this connection you won't be able to reach the Feenics server.   Note: If the telnet command isn't recognized, telnet may not be enabled on the PC If none of these steps help to identify the issue, please open a Support case.

Issue Cardholders and door schedules are no longer working and they were yesterday Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause There is likely a holiday or holiday group that is affecting the entire system Resolution A holiday in Access Expert will make every schedule in that instance NOT run that day. Holidays are exceptions to a normally scheduled interval. The holidays within the system apply globally to all schedules. Schedules normally activate at the beginning of an interval and deactivate at the end, however, on a holiday, the schedules do not activate. This creates Holidays as global exceptions to schedules.   Example: A site recently lost all card access and schedules did not work on Veteran's Day. Not all cardholders were out of the office that day.  Reviewing the Instance's Holidays showed that Veteran's Day was configured, so schedules and cards were not working.   ** To resolve this issue: 1. The Veteran's Day holiday was deleted from the above list 2. Next, the controller(s) needed a right click and then "Push controller database" After doing this, the schedules and cardholder access worked normally.

  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

Issue An error may pop up when using Bosch RPS configuration software indicating there is an issue with the hardware key. The Bosch Panel is offline in Access Expert Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Bosch Panel using RPS (Remote Programming Software) SafeNet USB Driver Cause The USB hardware key may not be installed or the driver needs to be updated or repaired Resolution Note: This solution assumes that the Bosch panel has been online in Access Expert before.   While working with a Bosch panel to integrate with Access Expert, the RPS software is used to configure the Bosch panel. An error may pop up indicating there is an issue with the USB security dongle that is inserted into the PC to connect to the Bosch Panel using RPS. This error typically pops up when trying to login with RPS and making the connection to the panel in RPS. "Invalid or missing Hardware Key" Steps: 1. Check to make sure that the USB dongle is inserted into the PC RPS is installed on 2. Install, repair or update the Sentinel Driver in Windows Programs and Features  Navigate to Windows Programs and Features Right Click on the Sentinel Driver Select Repair       Clicked through Next and Install Prompted to restart the PC       Note: Before restarting the PC, Exit RPS, Stop and Exit Docker, Exit Access Expert and then Restart the PC. Once the restart is completed, restart RPS and connect the Bosch panel, there should not be an error with the hardware key. Restart Docker and Access Expert. The panel should show online in Access Expert.                Additional external reference from Bosch: https://community.boschsecurity.com/t5/Security-Intrusion/How-to-correct-the-Invalid-or-Missing-Hardware-Key-message-from/ta-p/2858

Issue Access Expert SEQ Log Installation Information Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause The SEQ Log is a valuable troubleshooting tool to be installed separately from Access Expert Resolution Overview Access Expert utilizes a system logging application called SEQ which is used for troubleshooting and diagnostic purposes. While this service is not technically required to run any of the Feenics services, it provides valuable information when troubleshooting. Downloading SEQ The latest version can be downloaded at https://getseq.net/Download Installing SEQ Once the MSI is launched the wizard will prompt for installation as shown in the following Figures. SEQ service installation dialog Once the SEQ logs are installed, click 'Browse Seq' button to open the log in the default browser. Bookmark or Favorite It may be beneficial to set the SEQ logs as a bookmark for easy access. The example below is from Chrome. SEQ Settings Click on the 'Settings' option at the top of the page to access and change the defaults. Initially after clicking on Settings, the API keys page opens. Add an API key if required. API Keys Retention Policy From the settings page, select 'Retention' from the left-hand side menu. Once at the Retention page, click add and set the retention policy. The Access Expert/Feenics default is 21 days. This is adjustable to your needs, however, it is recommended to never go below 7 days. Note: Seq will periodically delete events covered by the policy based on their timestamp. Disk space will be reclaimed by a background compaction process and may not be available immediately. Default is ‘all events’ Example Seq Log Note: Left Click once to expand an event and click it again to shrink it Tips and Troubleshooting Ensure SEQ is installed on the PC where the Access Expert client is installed or it cannot ingest the Access Expert events. If a reinstall of SEQ is needed, manually deleting C:\ProgramData\Seq and subfolders is required after uninstalling SEQ from Windows Control Panel> Programs and Features. The SEQ uninstall does not remove the folder, subfolders and files. If the folder and files are not removed, the installation will fail. Before reinstalling SEQ, Grant the User that is running the installation full permissions to C:\ProgramData\Seq and subfolders if they do not have them. Installing SEQ using Windows Power Shell can be useful since it gives some feedback if something isn't working. Running the MSI installer within Windows doesn't give any feedback.   Command syntax:  seq service install --listen=http://localhost:5341/ -u "YourPCName\admin" -p "YourAccountPassword" Note: The username must be specified as DOMAIN\user or MACHINE\user PowerShell Install Example: SEQ Log documentation: https://docs.datalust.co/docs/getting-started https://docs.datalust.co/docs/ingestion-troubleshooting

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 An explanation of Hosted backup options is needed to understand which objects are backed up and which are not. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause It's important to understand the backup options available for an instance. Resolution By default, each instance includes a one-year transactional history retention, giving one year of Event History backup. Additional event history retention time can be purchased if required, and such purchases will be visible under "Manage License." Example: Note: There are currently no configuration specific backups that are retained or that can be restored to reinstate deleted hardware or objects into an instance.    Recommendations: Exercise caution when deleting objects, especially controllers, from Access Expert. A prompt requests confirmation before deletion. Generate snapshots of controller configurations and other detailed objects. These snapshots serve as references in case of accidental object deletion, assisting the reconstruction of controllers or other objects with their original configurations. Summary reports can also be useful when trying to rebuild objects. For example: Inputs, Outputs, Readers, etc.

Issue Identify which Access Expert LDAP Active Directory Keep version is installed Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Access Expert LDAP Active Directory Keep Integration Active Directory Cause Windows Control Panel Programs and Features doesn't indicate which version of the LDAP Active Directory Keep Integration is installed Resolution Login to Access Expert and the Instance that has LDAP Active Directory Installed Navigate to the General Configuration Tab> LDAP Agents LDAP Right Click on the LDAP agent and select View Event History Note: You may need to change the Priority from 50 to 0 and the Date Range to see an event Expand (Click the plus sign) of one of the LDAP Events (i.e LDAP Agent - Started) The version of the LDAP Active Directory Keep installation will show

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 Access Expert LDAP agent unable to connect to Instance Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted LDAP agent installed OnPrem on-site server (Not the appliance installed by Feenics) Cause LDAP agent cannot connect because the Username/PW may be stored in a registry that is no longer valid Resolution Double-check the site setup documentation records that the Username/PW combination is correct Run the SEQ Log and see if there's an entry that indicates that the 'Ldap agent is not able to connect to the instance' Note: Earlier versions of the LDAP on-site installer did not remove all registry entries including username/pw, so an older username/pw combination may be used instead of an updated combination.  If the username or password was changed at some point or if alternate combinations were used for troubleshooting then an incorrect combination could be used by the LDAP agent to connect to the instance and it cannot. Check the login to Access Expert with one of the LDAP username/password combinations and if there are 2 (Users) listed in Access Expert, delete the username/pw combination that does not work in Access Expert. Regedit Backup and old Username/PW deletion To obtain a registry backup just in case before deleting an entry: https://support.microsoft.com/en-au/topic/how-to-back-up-and-restore-the-registry-in-windows-855140ad-e318-2a13-2829-d428a2ab0692  It is suggested to back up the entire Feenics.Keep.ActiveDirectory.Service subkey Open regedit and delete the imagepath subkey Windows Start/Run> regedit Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Feenics.Keep.ActiveDirectory.Service Right-click on the ImagePath subkey and select 'Delete' Only delete this subkey, not the other Reinstall the LDAP integration using the media received directly from Feenics or SE Product Support. i.e. Feenics.Keep.Installer.ActiveDirectory.msi The most recent version of the install can be found on Feenics site: Feenics Keep Active Directory LDAP Installation Media  During the installation ensure the tested username/pw combination is used Verify that the 'Feenics Keep Active Directory Service' starts successfully Go to Start>Run>Services.msc and click Ok Locate the 'Feenics Keep Active Directory Service' Right-click and select Start Open SEQ Log and verify that the Ldap agent is able to connect to the Instance. The SEQ entry at the top of this article 'Ldap agent is not able to connect to the instance.' should no longer appear in the SEQ log. The following entry should be there instead. Verify that the Access Expert Windows User(s) can now be used login to Access Expert

Issue The network card is not working on the PC.  Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series TAC I/NET, TAC Vista Environment PC Network Interface Card Cause Require a method to test the network card. Resolution Assuming you have the correct protocols loaded:- Open up a command prompt and type ‘ipconfig’(1) then press enter to get a list of the available network cards. Find the specific network card by name (2) Record the IP Address (3) assigned to the card, e.g. 192.168.5.90 If the card is unplugged (4) connect a network cable and start back at step 1 If the network card does not appear in Device Manager check the drivers are correctly installed for the card and when installed correctly start back at step 1. If the network card still does not appear it could be disabled.  In Network Connections right click the adaptor and select Enable (5) and start back at step 1. After these steps if the network card still does not appear when running ipconfig it is most likely damaged. If/when an IP Address is successfully obtained open a Command Prompt and type ping followed by the IP Address of the card, for example ping 192.168.5.90 (1). A functioning card will respond with 4 successfully replies (2) and the associated statistics (3) As additional information a good first step would be to "ping 127.0.0.1". This will not test a network card but indicates that the TCP/IP protocol is installed and functioning on the host PC.

  Issue Schedule a meeting on a day when the site will be closed early. Steps are needed to ensure a door can be configured for 'card only' mode for the meeting. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause At times it's necessary to schedule a meeting on a day when the site will be closed early. Steps are needed to ensure a door can be configured for 'card only' mode for the meeting and then revert back to the normal schedule or extend the meeting until the end of the standard schedule. Resolution Steps to configure a door(s) with a schedule using holidays and 2 T&Ps to temporarily place the door in Card Only mode and then revert back to the standard schedule. In this example, the standard schedule Unlocks the door from 8a-5p.   Create a Holiday (Early Meeting) for the meeting date and ensure a Holiday Group Membership is selected Configure a schedule(Leave Early) for the meeting date(s) and length of the meeting. Select the Holiday Group in this example named 'Early Meeting Test' in the far right drop-down. The Holiday Group is needed for this to work. Note: The short-duration example was used while testing this multiple times a day. Configure a T&P (Early Meeting TP) to temporarily change the reader mode to 'Card Only' using the schedule (Leave Early). Select the Leave Early schedule and the 'Schedule-Became-Active' Event, the reader mode and the reader(s). The "Indefinite" duration drop-down selection worked. The other drop-down options did not work for this schedule implementation. Configure a T&P (Early Meeting Cancel) to cancel the Temporary Reader mode and revert control back to the standard schedule and to Unlock the door. Select the Leave Early schedule and the 'Schedule-Became-Inactive' Event, the reader mode and the reader(s). Extend the meeting to the end of the standard schedule if needed to keep it in card-only mode. Testing Results: At 3:55p the Leave Early meeting schedule became active and the TP changed the reader mode to card only. * Please disregard the Door held open highlights in the following snapshots At 4:00p the Leave Early meeting schedule became inactive and the TP canceled the temporary reader mode. The door Unlocked in this example after control was handed back to the standard schedule.

Issue An alarm is configured to be triggered by an event and when the event occurs, the Sound Effect (.wav) file configured for the alarm does NOT sound. Playing the .wav file on the PC outside of Access Expert works and it also works within the Access Expert Sound Effects Window.  Product Line EcoStruxure Access Expert Environment Access Expert Hosted v3 Cause The site IT may have blocked one or more ports Resolution Ensure that the Sound effect can be played from the Sound Effects window in Access Expert. If not, test the .wav file(s) in a different program i.e. Windows Media Player to make sure the PC can play sound files. Windows contains quite a few standard .wav files that can be used to test and they are located in the  C:\Windows\Media folder.   If all the above steps work then ensure that these ports below are not blocked as they are needed for Access Expert to function. download.feenicshosting.com tcp/443 keepevents.feenicshosting.com tcp/443 ocsps.ssl.com tcp/80 crls.ssl.com tcp/80 keepapi.feenicshosting.com tcp/443 connect.feenics.com tcp/443

Issue "Access Denied - Invalid Card Format" in live monitoring when the Door Relocks There is no error when the card is presented and the door unlocks normally Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause There is some type of electromagnetic interference affecting the reader Resolution There are at least 2 different situations where this has been observed: 1. When using entry and exit readers that are very close together 2. A strong LED light that was close to an entry reader. In this case, there was no exit reader   The resolutions are to move/remove the device causing the interference or in the case of the LED light to ground the shield wire of the reader to the panel. This stopped the error from happening.

Issue Access Expert On-Premise setup needs procedures and tools to backup and restore the database Product Line Access Expert Environment Access Expert Premise Software V3 MongoDB Cause The procedures for backing up and restoring the MongoDB is documented online at the link below. https://docs.mongodb.com/manual/tutorial/backup-and-restore-tools/ However, these instructions do not outline how to use the commands (mongodump and mongorestore) within the Windows OS environment using specific examples. Resolution The following procedures are designed to fill in the gap for Access Expert administrators who need to do manual MongoDB Backup and Restore. These procedures assume that Access Expert V3 has been installed and is functioning normally. You will need 2 separate Command Prompts, run as Administrator, open for these procedures. Mongo DOS Shell to attach to and run commands within MongoDB environment Standard DOS Shell to run the Mongo backup and restore commands MongoDB Backup Ensure MongoDB service is running (Start> Run> services.msc) Open a Command Prompt as Administrator (referred to as the Mongo DOS Shell) Type mongo(command) Type show dbs (command) - shown above, to give a list of the dbs available) If the MongoDB service is "Running," but the client cannot connect when typing mongo, it's probably because the path to the mongo bin folder hasn't been added to the PC's environment. To Add a local path locations variable to a PC environment https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ee537574(v%3Doffice.14) Ex. C:\Program Files\MongoDB\Server\3.6\bin (This will vary based on the version of Mongo) Open another Command Prompt as Administrator (Standard DOS Shell) Use the CD command to navigate to where you would like the backup files to be created Ex. C:\Data mongodump (command) The mongodump command creates the dump folder with admin, Keep, Signalr subfolders MongoDB Restore In the (Mongo DOS Shell) Prompt show dbs (command) use Keep (command) (Case sensitive) db.dropDatabase() (command) Use the Command Prompt as Administrator (Standard DOS Shell) mongorestore (command) The window should indicate "Finished Restoring Keep.Events," "done" and RESTORE COMPLETE If there are “E11000 duplicate key error collection” Keep.Events errors, it’s because the collection events are already in the folder and need to be deleted first.   Steps to correct the E11000 duplicate issue: (Stop the service, delete and recreate the DB folder, restart service) Right-click on the MongoDB service and Stop (you can’t delete files while the service is running) Delete C:\Data\db folder (not the Data, only DB) MANUALLY CREATE THE DB FOLDER - Right Click > New Folder and name it DB Restart the MongoDB service - this creates the necessary files in the DB folder Once these steps have been done, rerun the mongorestore command mongorestore (command) Verify that users can log into Access Expert with this database

  Issue After adding a new group with limited permissions to a User, the User cannot change their password or Login to the Instance. The Error 'Password is incorrect' is displayed When trying to change the password the dialog box may flash, but not continue. If you click the Ok button again, it will show the 'Password is incorrect' box. Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause A User Group with restricted access to specific objects didn't have permissions to the Instance object Resolution Add permissions to the User Group If 'All Types' are a part of a UserGroup then the 'Instance' object is included. However, if specific object permissions are selected for the User Group then the 'Instance' Read permission must be added at a minimum for the User to have access to the Instance. If the User is required to change their password then they will also need Publish permissions. Original Changed

Issue What new features are planned for inclusion in future product releases? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Access Expert, EcoStruxure Security Expert Environment All product ranges Cause Information required on future Product Marketing plans. Resolution This document is no longer published on the Download Center by Product Management. For further information on the future product planning please contact the Product Manager for the specific product in your region. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com

  Issue When adding an onboard downstream device (Ex. LP1502) with 4 Engage wireless gateways installed the onboard downstream device shows as 'Unknown' and will not come online Product Line EcoStruxure Access Expert Environment Access Expert v3 Hosted Cause If the onboard downstream controller(Ex. LP1502 - onboard) was not being used prior to commissioning and addressing the Engage Gateways then it is likely there is an address conflict. Resolution Check all the downstream device addresses by going to Hardware Provisioning> Downstreams If one of the Engage addresses is 0 then it is likely conflicting with the onboard downstream controller's address 0. Go back through commissioning the Engage gateway devices and re-address them. Before After Once the gateway devices have been re-addressed not using address '0' they should all come online as well as the onboard downstream controller and it should not show as 'Unknown'.

  Issue Access Expert Exceptions for specific dates using holiday durations with an example Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Instructions with an example are needed to allow exceptions to the standard schedule for specific dates and times Resolution At times it's necessary to have schedule exceptions for meetings or other reasons where the date, day, and time need to be specified outside of the standard 8-5 schedule.   In order to configure this within Access Expert use the following method: Verify the main schedule and check the days and times  Note: Adding a schedule duration(interval) to the main schedule allows exceptions to be added however, they will not be specific to a date. The interval add will be for whatever days are selected going forward. For example, All Monday or all Tuesdays in the future for the time specified.   The above schedule works normally from 8AM - 3:45PM and for all Thursdays going forward the door will unlock from 4PM - 4:05PM To specify a specific date and time for an exception to the main schedule an additional schedule and a holiday group is needed. Create another schedule in addition to the standard schedule with the days and times needed. Example: Wed7-19 & Th7-20 Council (Council Meeting 6-7p) From the Access Configuration tab, select Holidays and create a holiday for the specific date(s) needed (Start and End Dates) and select the checkbox for Special Date Example: 7/19 and 7/20/23 Council Meeting Select the Edit Holiday Group Names button and select one of the default groups and edit the name to be descriptive then Save. From the Holiday Group Membership drop-down select the newly added Group just renamed and click Ok and then Save Note: The exception schedule will not work unless a Holiday Group has been added Go back to the new schedule that was created earlier and select the drop-down under Always Active On. Select the checkbox next to the Holiday just created and Click OK then Save. A completed schedule with Wednesday and Thursday exceptions that have 7-19 & 7/20/23 specified as holiday durations. This will unlock the door during the normal schedule 8-5p Lock the door from 5-6p Unlock the door from 6-7p for Wednesday and Thursday 7/19/23 and 7/20/23 Lock the door at 7p for Wednesday and Thursday 7/19/23 and 7/20/23   The holiday exception locked at 4:05p up until 6p The holiday exception schedule locked the door at 6p

Issue Steps for Troubleshooting Readers Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause Readers are offline or not returning the correct card data Resolution Common Issues Issue Solution My reader is not returning any data when I present a card Check to make sure the technology card you are using matches the requirements of the card reader. A prox card will not work on an iClass reader. Check the Reader wiring to confirm CLK and DATA on wired correctly. Check that the Reader addressing matches the reader port. Check the power being supplied to the reader. Multiclass readers cannot be powered off S2 (green boards). They require an external power supply. Bluetooth readers cannot be powered off the S2 (green) boards. The power required by the Bluetooth readers is directly related to the range at which the Bluetooth readers are programmed to work. My reader is returning different results every time I swipe my card. Check the power to the reader. If the reader requires more power than the board can provide, use a dedicated power supply. My reader is returning the correct number of bits but the encoded card information is incorrect. Check to make sure your CLK and DATA wires are not switched. If the CLK and DATA wires are switched the 0's and 1's will be inverted causing the card number reported to be wrong.  My reader is returning the correct number of bits but the raw HEX data is all 0's.  This is most often caused by a bad reader or a bad port on the Mercury board. Check the reader wiring and power first, then try the reader on a different port.    My EP1501 uses the Reader 1 port for my SIO, how do I utilize the on-board reader? The on-board reader for the EP1501 is placed on the internal port and is physically placed on Reader 2 (TB3); it should still be addressed as reader address '0' in Feenics. I wired my reader to Reader 1 on the board, what's my reader address? All reader addresses are -1 from the physical port the reader is wired to. Reader wired into Reader 1 is address 0. I don't understand what to set my offline access method to. No Change: Reader access will remain in the 'Online Access Method'. Facility Code Only: Only the facility code is required to receive and access granted event. Unlock: The reader will unlock during its offline state. Lock Down: The reader will be locked down during its offline state. OSDP Reader goes offline when I select 'Secure Channel'. From the top menu bar select 'Start Linking Mode'. The OSDP reader will come back online. Please Note: The OSDP reader must be new or never have been configured for Secure Channel previously. If it was previously configured for Secure Channel it will need to be reset with a config card. My Engage NDE/LE lock is showing a Magnetic Tamper Follow the manufacturers instructions to calibrate the door sensor. My reader is posting "Access Granted - Not Used" events. This can happen for two reasons. First, the cardholder badged at the door but never opened the door to enter. Second, the door does not have a door contact wired at the door and one is programmed into the system. Since there is no device telling the system if the door was used, the system reports no door use. My reader is posting "Access Denied" events immediately after "Access Granted" events. Whenever troubleshooting event data always be sure to expand the event message to learn more. If the event is returning data is without a card read following the first access event, it suggests there may be power coming back into the comms, or are sending feedback into the comms loop. You can test this by Does removing the load (pull the output/strike) oof the terminal render the same results? Is there any change when placing the reader directly onto the Mercury board? A thorough investigation of the power wiring on the board will help isolate the location of the issue. My reader is posting "Access Denied - Incomplete Card or PIN Sequence" The Card and PIN reader mode requires a valid PIN sequence followed by a valid card read. The Incomplete Card or PIN Sequence can occur Only the card was presented to the reader. Only the PIN Code was entered at the reader. The card was presented before the PIN code was entered. Keep in mind, if someone enters a random PIN sequence at a reader and happens to guess a valid PIN but does not present a card, this event will show. The reader is producing an "Unidentified Person on Site" event. This event is produced when a controller grants access at a reader to a cardholder that is on the controller database, but that is not currently within the Feenics Database. This can happen if a controller missed an event when a person was deleted from the database. The system will delete this card from the controller after this event. The next step is to identify the person and remove them from the building. The reader is posting "Access Denied - Invalid Facility Code" but showing the correct Facility Code in the expanded event data. This can occur if the Card Format programmed with the appropriate Facility Code on the controller does not have the correct parity bits for the card being used. The Mercury Service checks the Card number, the Facility Code, and the parity bits in that order. Due to this, when creating a card format, the parity bit is often the last part of the Card Format to be checked. Access Denied - Card/Pin Not Found The User does not have access to the door. Add the User to the door through an Access Level    

Issue Unable to bring interfaces(downstream devices) online, showing as unknown Product Line EcoStruxure Access Expert Environment Access Expert in Cloud or On-Premise SSC (Security System Controller) Downstream controllers Cause Offline interfaces can occur under a number of circumstances, below are the most common reasons. The controller is not yet active. Once all interfaces, readers, and I/O have been added, it’s important to remember set the device as active. Interfaces were added to the controller after it was made active. The controller requires a reboot to download the correct configuration. Dipswitches and addressing on the board may be incorrect Check Wiring  Resolution Go through the following steps to get interfaces online Set the device as active (Go go back to the controller page ) Reboot the controller (containing the interface) Check that the DIP switch settings are correct on the controller (see the Mercury hardware manual) Switches 1-5 on an interface module set the address in binary, this means 32 addresses are available (0-31). Users must set the correct address inside Access Expert that matches the DIP switch value. Switches 6 & 7 set the Baud rate, both on for default 38400. Switch 8 should be off to disable AES key encryption. (Communication is instead encrypted over TLS 1.2) Note: The orientation of the DIP switches may be upside down compared to some labels on other connectors, so it's easy to have everything inverted. On this MR52 board, the On label on the connector is DOWN. These dip switches are configured for address 0, baud rate 38400, and no encryption. Check wiring Ensure that the panels are wired correctly. Verify your RS485 communication and refer to the hardware installation guides Verify End of Line Termination Verify End of line termination jumpers are set, refer to hardware installation guides