home-assistant.io/source/_integrations/bosch_alarm.markdown
Sanjay Govind 2a09cd15c9
add documentation for reconfig flow in bosch_alarm (#38414)
* add documentation for reconfig flow in bosch_alarm

* add documentation for reconfig flow in bosch_alarm
2025-04-08 17:38:21 +02:00

2.8 KiB

title, description, ha_category, ha_release, ha_iot_class, ha_config_flow, ha_codeowners, ha_domain, ha_platforms, ha_integration_type
title description ha_category ha_release ha_iot_class ha_config_flow ha_codeowners ha_domain ha_platforms ha_integration_type
Bosch Alarm Integrate Bosch Alarms.
Alarm
Sensor
2025.4 Local Push true
@mag1024
@sanjay900
bosch_alarm
alarm_control_panel
sensor
integration

The Bosch Alarm Panel {% term integration %} allows you to connect your Bosch Alarm Panel to Home Assistant to control and monitor your Bosch Alarm Panel.

{% include integrations/config_flow.md %}

Supported devices

  • Solution 2000/3000/4000
  • B Series: B3512/B4512/B5512/B6512
  • G Series: B8512G/B9512G
  • AMAX 2100/3000/4000
  • D7412GV4/D9412GV4 1

Provided entities

The following {% term entities %} are provided:

Alarm Control Panel

This integration adds an Alarm Control Panel device for each configured area, with the ability to issue arm/disarm commands. This entity reports state (disarmed, armed_away, etc.).

Sensor

A sensor is provided per area that lists how many points are currently in a faulted state.

Authentication

The primary means of authentication for the Mode 2 API is the Automation passcode. It needs to be at least 10 characters long, and it is different from the User code -- a shorter numeric pin used to arm/disarm the panel. The integration will prompt for the required passcodes, which depend on the panel type.

Panel Code
Solution User 2
B Series Automation
G Series Automation
AMAX Both

{% important %} Since the Mode 2 automation user has "superuser" privileges, it bypasses the regularly configured alarm pin: you will not be prompted for a User code when arming/disarming through the integration. {% endimportant %}

If your authentication changes, the integration will automatically prompt you to enter the new credentials.

Reconfiguration

This integration supports reconfiguration, so it is possible to change the configuration such as the IP Address after it is configured.

Troubleshooting

Diagnostics information

Consider uploading the diagnostics file along with your issue report to allow faster triaging and pinpointing the issue. The information contained in the generated diagnostics file is redacted to avoid any sensitive information while still remaining useful for developers to fix the issue.

Removing the integration

This integration follows standard integration removal. No extra steps are required.

{% include integrations/remove_device_service.md %}


  1. Firmware 2.0+ ↩︎

  2. The user needs to have the "master code functions" authority if you wish to interact with history events. ↩︎