The Bosch intrusion panel extension 4.4 includes the following known limitations.
Issue | Description |
---|---|
3474092 | Connecting to the intrusion panel using an external B426 Ethernet module on
Bosch B or Bosch B/G-series panels might prevent the integration from functioning
correctly. This is because the Bosch panel causes data overflow errors on the B426
module in some cases. Workaround: Connect to the intrusion panel using an
onboard Ethernet module.
|
1285216 | The only card types that can be synchronized with Bosch intrusion panels are Wiegand 26 bits, Wiegand 37 bits no facility code (H10302), and Wiegand 37 bits with facility code (H10304). |
1285213 | In Bosch RPS, if a passcode length is configured for an intrusion panel, the
length of the PIN credential of the cardholders mapped to users on that panel must
match. If no passcode length is configured on the panel, the length of the PIN must be 3 to 6 digits long. |
1285210 | The Force push to panel feature takes a long time to complete because all disabled users on the panel are enabled before they are deleted. |
1285209 | For cardholders to be pushed to the panel, they must each have at least one PIN credential configured in Security Center. If the PIN of a cardholder that was already pushed to the panel is removed or disabled in Security Center, that cardholder is deleted from the panel the next time a sync occurs. |
1285206 | To be able to modify Bosch intrusion panel users, you must be granted all Access control management privileges, and all privileges required for modifying intrusion detection units. |
1285205 | In Bosch RPS, a user is considered disabled if it does not have at least one authority level above zero. Disabled users cannot be retrieved from the panel and mapped in Security Center. |
1285204 | A user cannot share the same passcode as another user or use another user's
duress code as a passcode. NOTE: Each passcode has four duress codes. For example,
the duress codes of the passcode 5678 are 5676, 5677, 5679, and 5670.
|
1212736 | B6512, B8512, and B9512 intrusion panels: If the card type configured in Bosch RPS is 37 bits with facility code, in Security Center, when you click Pull from panel, no users are retrieved. |
1184480 | In Security Center, you can assign the
passcode used by the Installer to another intrusion panel user. When you try to push
the new user to the panel, the sync fails. NOTE: The Installer is only displayed in
Bosch RPS, and cannot be viewed or modified in Security Center.
Workaround: Make
sure no users have the same passcode as the Installer.
|
794915 | If you use Security Center Config Tool to delete an input, output, or area that is configured and still in use on a panel, the panel will go offline and stay offline. |
772026 | Mode 2: If an intrusion detection area is instantly master armed, and then it is perimeter armed without first disarming the area, the alarm is no longer reported by the panel to Security Center, but it appears on the keypad. |
772023 | Custom event names and descriptions are not localized. |
772021 | Arming delay must be configured from Bosch RPS. |
771997 | Entry delay is ignored if the intrusion detection area is instantly armed. |
771995 | GV4 v2, Mode 2: The panels might stop responding due to a TLS
vulnerability. Workaround: To try and resolve this issue, you can update
your registry keys. For more information, see the Microsoft hotfix 3155464.
|
771994 | Mode 1: If you reset the TCP connection, the panel restarts. |
771914 | GV4 v2, Mode 2: When you add the intrusion detection unit in Security Center, non-configured outputs on the panel are created in Security Center. |
771835 | For GV4, B series, and G series panels, you can only find out which input is responsible for an alarm if it is still in an active state when the input status is polled. |
771833 | GV2, GV3: You can only find out which input is responsible for an alarm when you receive the event in Security Desk. The alarm event might be reported with a delay, due to the Abort Window RPS configuration. |
771829 |
|
771825 | GV2: Custom events are not reported in Security Desk. |
771824 | GV4 v2, Mode 2: Intrusion detection area, input, and output names cannot be
read from the panel. Workaround: Change the intrusion detection area,
input, and output names from Security Center. The names are pushed to the panel.
|
723216 | When you Force arm an area, the inputs are bypassed, but they are not reported as bypassed. |
643372 |
|
154224 | Security Center does not support the
following for use with the B426 Ethernet Network Interface Module:
|
94231 | GV3 panels support 32 areas, but only support eight intrusion detection areas in Security Center. |