The following issues are resolved in the OnGuard plugin 5.1.1.
Issue | Description |
---|---|
3297323 | Under certain conditions, events that are saved in the database by the plugin could also be saved in the proxy. This could cause the events to be raised more than once if the plugin loses connection with the proxy. |
3258612 | OnGuard 8.1 panels that are in multiple warning states are not properly displayed in Security Center. |
3258468 | The OnGuard plugin does not support custom cardholder fields that use the int64 data type. |
3255180 | Certain offline events and updates from OnGuard do not come across correctly while the proxy is offline. |
3254304 | Changes made to visitors in OnGuard 8.1 are not updated in Security Center until after a manual synchronization. |
3245340 | When the live updates are active and the Security Center, including those who are inactive. | option is selected, a synchronization pulls all cardholders into
3237799 | The OnGuard proxy does not receive events that occurred while it was offline. |
3217328 | Alarms acknowledged in OnGuard while the proxy is disconnected do not get acknowledged in Security Center and never get removed from the proxy's alarm cache. |
3014272 | You cannot select inputs for some OnGuard events when configuring event-to-actions. |
3012238 | On some systems, polling for device status can crash the OpenAccess API service. |
3014716 | The default proxy setting for polling the hardware status of OnGuard devices is False, which can cause incorrect device status reports after a manual synchronization. |