Upstreamed!

As of Home Assistant 2025.6, this integration is part of Home Assistant. This repository will no longer be updated. All users are encouraged to update to the build-in version.

Home Assistant integration for Bosch Alarm Panels, using the Mode 2 API.

Supported panels:

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

Based on the bosch-alarm-mode2 library, which uses subscriptions/push updates for panels that support it.

Provided entities

• AlarmControlPanel for each configured area, with the ability to issue arm/disarm commands. This entity reports state (disarmed, armed_away, etc), and contains custom attributes ready_to_arm (no|home|away), and a faulted_points counter.
• BinarySensor for each configured alarm point.
• Sensor entities for the panel's current faults, and the panel's history. The history itself is stored on a history attribute, as there is a limit to how much text a sensor can store in its state.
• Switch for each configured output. Note that for some panels, only outputs with the type set to "remote output" can be controlled via Mode 2 API.
• Lock for each configured "door" (Solution 4000, B Series and G Series panels only).
• A custom Service, called set_date_time, that can be used to set the time and date on the panel.

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

⚠️ Since the Mode 2 automation user has "superuser" priviledges, it bypasses the regularly-configured alarm pin: you will not be prompted for a User code when arming/disaming through the integration. The integration also supports (optionally) setting a Home Assistant-local pin to protect these operations -- it does not need to match any of the codes configured on the panel.

Installation

Footnotes

1. Firmware 2.0+ ↩

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