Limitations in Synergis Softwire 11.5.2 - Synergis Softwire 11.5.2

Synergis™ Softwire Release Notes 11.5.2
Product
Synergis Softwire
Content type
Release notes
Version
11.5
Release
11.5.2
Language
English
Last updated
2024-09-13

Synergis™ Softwire 11.5.2 includes the following known limitations.

Limitations first reported in Synergis Softwire 11.5

Interface module Issue First reported in Description
DDS 3478111 11.5.0 The DDS controller integrations with Synergis Softwire do not support PIN credentials.
Mercury 3841828 11.5.0 Mercury does not support strict and hard antipassback when the Activate global antipassback setting is enabled on the Access Manager role in Config Tool.
Mercury 3765594 11.5.0 When the Mercury controller loses connection to Synergis Softwire, but is still connected to the SIO boards, the controller validates the facility code before the credential.
Synergis IX 4010624 11.5.1 Heath status messages only display the first 32 characters of expander module names.
Synergis IX 3467851 11.5.0 The access denied reason is sometimes incorrect when a cardholder has an access rule with an active schedule and an access rule that is out of schedule assigned to different doors or intrusion detection areas for Synergis IX.

Limitations first reported in Synergis Softwire 11.4

Interface module Issue First reported in Description
Mercury 3296053 11.4.0 On an HID Signo reader, when the LED color is set to Off, the LED turns blue. The LED turns off only after an access grant.
Mercury 3243920 11.4.0 Enrolling more than 15 MR62e panels on an LP1502 controller turns them offline.
Workaround:
  1. Log on to the controller through the Synergis Appliance Portal.
  2. Enable the following settings:
    • No ACR without door
    • Two OSDP readers per reader port
  3. Click Save.
Synergis IX 3334687 11.4.0 Changing in Config Tool the properties of a schedule that is already in use by a Synergis IX unit does not update the Synergis IX unit.
Workaround: Sync manually.

Limitations first reported in Synergis Softwire 11.3

Interface module Issue First reported in Description
Axis 3091604 11.3.3 The Door forced open event can still be generated in Security Center, even if the door input is shunted.
BEST Wi-Q 2981102 11.3.1 If a BEST Wi-Q controller loses connection with the gateway for 24 hours, it only comes back online when daily polling occurs.
Workaround: If you do not want to wait for the daily polling time to reconnect, you can force polling to occur by badging an invalid card six times, or entering an invalid PIN six times on the lock. Alternatively, you can power cycle the lock by removing the batteries, waiting five minutes, and then reinserting them.
BEST Wi-Q 2973721 11.3.1 By default, there is a sixty-second delay when manually unlocking doors from Security Desk that depends on the beacon time configured through the BEST Wi-Q gateway. Decreasing the beacon time decreases the battery life of the BEST Wi-Q lock.
Mercury 2938709 11.3.0 The PIN value is not included in Access granted and Access denied events for Mercury controllers.
Synergis IX 2967251 11.3.0 When using RS-485 readers on Synergis IX, 26-bit credentials might be reported as 34-bit credentials.
Workaround: You can enroll the same card data as a 34-bit credential and it works correctly.
Synergis IX 2047917 11.3.0 For Synergis IX controllers, if you force open a door, and leave it open, the Door open too long event is not generated because the Forced open state has a higher priority alarm condition than the Left open state.
Synergis IX 2990788 11.3.0 Offline expanders on Synergis IX controllers cause module restart messages to be generated on the Intrusion Manager every minute.
Workaround: Delete expanders that are not physically present.

Limitations first reported in Synergis Softwire 11.2

Interface module Issue First reported in Description
All 2814411 11.2.0 Global antipassback does not work with more than 50,000 cardholders.
Allegion Schlage ENGAGE IP 2821885 11.2.0 The door lock state of FE410 Control locks is always displayed as locked in Security Center regardless of the deadbolt state.
ASSA ABLOY IP 2673023 11.2.1 When the lock is in passage mode, the Override unlock schedule action in Security Desk does not override the state of the door lock.
Mercury 2862470 11.2.1 When you create a hardware zone using a Mercury input that is offline, the Active state event you configured on the Properties page of that zone is triggered.
Workaround: Do one of the following:
  • Use I/O zones instead of hardware zones.
  • Create the hardware zone, select all required inputs, select a Normal state event, but leave the Active state event blank. Save the configuration, and then set the Active state event.
Mercury 2697326 11.2.0 When an interlock area is accessed by a REX, the interlock might not be applied correctly if the Door opened event is received before the Door locked event.
Workaround: Use Mercury's native interlock feature by enabling the Mercury native area control option in the Synergis Appliance Portal.