Climate
Bosch thermostat
bosch-thermostat/home-assistant-bosch-custom-component · vv0.28.2
HACSCloud polling
HA custom component for Bosch thermostats
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
climate | Thermostat | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
water_heater | Water heater (as a thermostat) | |
select | Mode picker (as switches) |
What people report
Works with older Bosch EasyControl CT200 and IVT/Buderus gateways, but new firmware (4.02+, 5.4) repeatedly broke it, and newer IVT models are not supported. Maintainers rely on user debug scans.
- Works3
- Partly works1
- Not working2
- Requested1
- Won’t be supported1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Bosch CT200 firmware 4.02.02 | Works Cloud | Unsupported-firmware error after Jan 2024 update; closed completedSaved copySame issue on both the latest core and on 2024.1.3 as well. 2024-01-13 12:11:47.945 INFO (MainThread) [custom_components.bosch] Setting up Bosch component version 0.24.1. 2024-01-13 12:11:47.946 DEBUG (MainThread) [custom_components.bosch] Initializing Bosch integration. 2024-01-13 12:11:47.958 DEBUG (MainThread) [custom_components.bosch] Checking connection to Bosch gateway as 111111111. 2024-01-13 12:11:49.627 ERROR (MainThread) [custom_components.bosch] You might have unsupported firmware version 04.02.02 Excerpt saved from GitHub on 2026-10-23. | Issue #370 · 2024-01 | |
| Bosch EasyControl CT200 | Works Cloud | Added in 2021 via XMPP; newer firmware needs updatesSaved copyAdd Easycontrol support (CT200) But need https://github.com/bosch-thermostat/bosch-thermostat-client-python/pull/17 before Excerpt saved from GitHub on 2026-10-23. | PR #65 · 2021-04 | |
| Bosch RC300 gateway (IVT/HTTP) | Works | Tested firmware 04.08.02; recording sensor fixesSaved copySummary Comprehensive fixes for recording sensors, database resilience, deprecation warnings, and sensor state updates. Tested with RC300 gateway (IVT/HTTP, firmware 04.08.02). ### Changes in v0.28.7 (latest) 1. Recording Sensor Fallback for Slow Gateways (cydrezz#1) - File: `sensor/recording.py` - Issue: Gateways like KM100 have 2-3h lag writing recording data. Code searched for exact last-hour timestamp → not found → `STATE_UNAVAILABLE` ("Unbekannt"). - Fix: Fallback logic in `find_idx()` uses latest available value if ≤6h old. If >6h → warning log about possible clock sync issue + … Excerpt saved from GitHub on 2026-10-23. | PR #523 · 2026-01 | |
| Bosch CT200 with EU firmware 05.04.00+ | Partly works Cloud | Cannot use XMPP; needs POINTT cloud OAuth, PR not mergedSaved copyEasyControl devices (e.g. CT200) with EU firmware >= 05.04.00 cannot use the XMPP protocol. They must connect through the Bosch POINTT cloud API using OAuth2 / SingleKey ID authentication. Changes: - config_flow.py: route EASYCONTROL device type to a two-step OAuth flow instead of XMPP. * Step 1 (easycontrol_serial): user enters the device serial number. The config flow builds and displays the SingleKey ID authorisation URL. * Step 2 (easycontrol_oauth): user pastes the redirect URL received after browser login; the flow exchanges the code for tokens, verifies the connection with … Excerpt saved from GitHub on 2026-10-23. | PR #536 · 2026-03 | |
| Bosch CT200 firmware 5.4.0 | Not working Cloud | Firmware 5.4.0 broke the plugin; POINTT OAuth work pendingSaved copy> Error in HA: Config problem > > EasyControl app ver 5.6.0 (Android) Bosch CT200 firmware ver 5.4.0 > > Can one of you or both create a debug_scan as described in the message and upload it here so the developpers can update the HA-plugin to make it compatible with the new firmware version We can't run a debug scan when the plugin won't load, as the action is unavailable. This is the sum total of the logs I can provide, which I got by enabling debug logging for the plugin then trying to reload it. ``` 2025-06-03 22:01:48.606 INFO (MainThread) [custom_components.bosch] Setting up Bosch … Excerpt saved from GitHub on 2026-10-23. | Issue #484 · 2025-06 | |
| Bosch iCom_Low_NSC_v1 firmware 04.06.07 | Not working | No entities, unsupported firmware warningSaved copyConfigure RELOAD logs: 2023-09-28 22:20:00.029 WARNING (MainThread) [custom_components.bosch] Unloading Bosch module. 2023-09-28 22:20:00.033 DEBUG (MainThread) [custom_components.bosch] Closing connection to gateway. 2023-09-28 22:20:00.033 INFO (MainThread) [custom_components.bosch] Setting up Bosch component version 0.23.2. 2023-09-28 22:20:00.034 DEBUG (MainThread) [custom_components.bosch] Initializing Bosch integration. 2023-09-28 22:20:00.034 DEBUG (MainThread) [custom_components.bosch] Checking connection to Bosch gateway as * 2023-09-28 22:20:01.013 ERROR (MainThread) … Excerpt saved from GitHub on 2026-10-23. | Issue #328 · 2023-09 | |
| Bosch WebKM300 diagnostic module | Requested | Sensors/relays via REST API; not in device listSaved copyAdditionally to my KM100, I use a KM300 which comes with several sensor / relay attachments. Those sensors could be configured as e.g. temperature (PT1000). In parallel to KM100/KM200 the KM300 provides a REST API to query those values. (In ioBroker I already used the km200 adapter to communicate with the KM300 and it worked right out of the box.) Currently the KM300 works in a first version by providing the gateway information like FW version etc. It would be nice to have support for the IO's of the KM300. I'd assume following steps: 1. Collect information about the REST API of the KM300 (I … Excerpt saved from GitHub on 2026-10-23. | Issue #288 · 2023-04 | |
| IVT K40 RF gateway | Won’t be supported Cloud | Unknown error on XMPP; maintainers pointed to bosch-homecom-hassSaved copyI am trying to connect my IVT heat pump gateway (model K40 RF) to Home Assistant. Despite using valid credentials (Login/Pass from the device label), I am encountering "Unknown error" when using XMPP configuration. Gateway ID:102013396 Model identified by Fing: K40RF-051441 I have attached screenshots of the configuration and errors. Could you please advise how to proceed or if additional logs are needed to add support for this device? Excerpt saved from GitHub on 2026-10-23. | Issue #559 · 2026-05 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Cloud polling
Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 1,514 (0.21%) |
|---|---|
| GitHub stars | 319 |
| Latest version | v0.28.2 (2026-10-22) |
| Set up in the UI | Yes |
| Maintainers | @pszafer |
| License | Apache-2.0 |
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| cydrezz/bosch-custom-component-ha-pro | ★ 3 | 2026-10-09 | HA custom component for Bosch thermostats |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
