Limitations in deister proxSafe plugin 3.2.2 - The deister proxSafe plugin 3.2.2 includes the following limitations. - deister proxSafe 3.2.2 - Plugin and extension guides

deister proxSafe Plugin Guide 3.2.2

Product
proxSafe
Content type
Guides > Plugin and extension guides
Version
3.2
Release
3.2.2
ft:locale
en-US
Last updated
2026-01-21

The deister proxSafe plugin 3.2.2 includes the following limitations.

Issue First reported in Description
3514337 3.2.2 If only the PIN option is selected in the Authentication section of the Properties tab, any cardholders with conflicting PINs are not exported to deister Commander.
Workaround: PIN codes must be unique throughout the system.
3207412

3207409

3.2.2 If you create or edit asset group and then edit another existing group without saving your initial changes, the plugin deletes the newly created group and discards all pending modifications..
Workaround: To avoid losing your changes, always save your changes before editing another group.
3043977 3.2.0 A key assignment can be pushed to cardholder when the plugin is showing a warning that indicates that the cardholder has been assigned multiple schedules.
2421809 3.2.0 In the entity browser of a Federated system, all terminals, lockers, and assets related to the deister proxSafe plugin have tile plugin icons ()
2145246 3.1 You cannot connect multiple plugin roles to the same plugin database, or the same instance of Commander.
2145180 3.1 You do not receive a notification if you are trying to synchronize more cardholders than the deister proxSafe terminal allows.
2144627 3.1 Temporary access rules are interpreted as permanent access rules.
751272 3.0 You cannot limit the number of events received from the proxSafe system. As a result, if the proxSafe Commander Connect system is disconnected from Security Center, the deister proxSafe plugin might not be able to reconnect to the proxSafe Commander Connect system if too many events occurred while the connection was down.
748214 3.0 Synchronizing a large Security Center cardholder group (~4000 cardholders) with deister Commander can take hours.
Workaround: Synchronize smaller groups of cardholders.
744236 3.0 Users must have the Modify tile plugin privilege in order to manually release assets.
742270 3.0 The number of entities that are supported on the deister proxSafe system are based on C4 terminals, not C1, C2, or C6 terminals.
742136 3.0 If a cardholder is a member of more than one cardholder group, and each group has a different schedule assigned, the schedule that takes priority for that cardholder is undefined on the proxSafe system.
Workaround: Assign a schedule for the individual cardholder.
726263 3.0 Locker entities are always displayed as online in Security Center, even when they are offline in deister Commander.