Room zones / radiator thermostats (ETRVs) not discovered as climate entities

[janfuu-cpu]

Integration version

v1.0.1

Home Assistant version

2026.7.2

Connection type

Cloud (POINTTAPI)

Device & firmware

CT200, 05.04.00

System layout

No response

What happened?

I am using the Bosch EasyControl (CT200) gateway with 5 smart radiator thermostats (ETRVs) paired. In the official Bosch EasyControl app, all 5 thermostats are properly configured and assigned to their respective rooms.

However, the Home Assistant integration does not discover or create individual climate entities for these rooms.

Devices and Entities Status

The integration successfully discovers the following 5 main devices:

• Boiler
• EasyControl Gateway
• Heating Zone
• Hot Water Tank
• Solar

Under "Heating Zone", there are 19 entities exposed, but they only contain system metrics (e.g., Boiler power, Boot duration, etc.). The actual individual rooms/zones are completely missing from Home Assistant.

Expected behavior

The integration should discover and create 5 distinct climate entities for the rooms configured in the app:

1. Wohnzimmer
2. Küche
3. Schlafzimmer
4. Badezimmer
5. Kammer

Diagnostics

I have successfully downloaded the diagnostics data from the integration page. I am attaching the json file to this issue so you can inspect the API paths and mapping for this specific hardware/firmware setup.

Thank you so much for your amazing work on this integration!

Diagnostics file

config_entry-bosch-01KXXPQ9SXZVQN87KZ84BP8K26.json

Debug log (if relevant)

Checklist

• I removed/redacted any tokens or callback URLs from everything I pasted
• I checked existing issues for duplicates

[LukyHurdy1]

Hi, I have the same problem, did anyone manage to solve it? I really miss the radiator heads setup.
thank you

[LukyHurdy1]

Hello all,
Does anyone really have any idea how to connected Bosch heads?
The application works correctly, it has to work somehow :-D
thank you Lukas

[jfhautenauven]

Hello folks, just migrated to this "new" forked version, and indeed, I can confirm, I'm not seeing my bosch heads coming back up, they are not discovered by the integration ... @CaseyRo : could you please reintroduce support for ETRVs ? Thanks in advance.

Setup :

CT200 FW05.04.00
ERTV : 12
Hot boiler tank (200L)
POINTTAPI (since XMPP doesn't work anymore in my case)

[jfhautenauven]

@CaseyRo : BTW, absolutely no issue to be a tester of this integration if needed :)

[jfhautenauven]

@janfuu-cpu

I checked your logs, and I can for sure compare with mine. It seems the integration only looks up for one zone : zn1, then stops.
I had written a similar integration for Jeedom domotica platform a few years back, and I remember quite good there was a pointer to use to navigate on each "zone". There is an URL giving the list of Zones, then you have to manually iteration and look up for each individual zone.

Didn't check the code of this integration yet, but it seems to me, the zone discovery is not done properly ...

[jfhautenauven]

Pretty sure this is incorrect :

zones/zn1 ... means it will never go check the other zones ...

back in the days, I used to query this url on the XMPP paths :
/bridge/zones/list

I would then iterate on that list to discover all zones, then I would have created devices in Jeedom to reflect these zones and then update them based on their ID's during the refresh data phase ...

Same for devices --> /bridge/devices/list
The device exposed the zoneId of the zone it was attached to

On the old protocol, the setpoints where linked to the zone itself (eg. /bridge/zones/zn2/temperatureHeatingSetpoint), whereas the device was the carrier of the information about percentage opened of the valve, signal strength etc.

Here is a schema

My good old code for reference :

https://github.com/jfhautenauven/plugin-boschthermostat

Pay attention to how the discovery and fetch of the data is done in this class : should be straight forward to illustrate what I said above :

https://github.com/jfhautenauven/plugin-boschthermostat/blob/main/core/class/boschheatingsystem.class.php

[CaseyRo]

Thanks a lot @jfhautenauven — your analysis (here and via mail) was spot on, and genuinely helpful. 🙏

Confirmed: the integration polled /zones/zn1 and nothing else. My own CT200 is a single-zone setup, so the hardcoding never hurt me — but @janfuu-cpu's diagnostics show allowedZones: [1, 2, 3, 4, 5, 6], meaning the rooms live at /zones/zn2–zn6 and we simply never looked there.

Fixed on master:

• The coordinator now queries the /zones listing and walks every zone it returns (exactly the discover-then-iterate pattern you described from your Jeedom plugin).
• One climate entity is created per discovered zone, and each zone device is named after its room from /zones/znX/name — so you should see Wohnzimmer, Küche, etc. as separate climate entities.
• Single-zone setups are untouched (no entity renames/orphans).

What I need from you: I can't test multi-zone against my own hardware. I'll cut a pre-release — @jfhautenauven and @janfuu-cpu, since you both kindly offered: please install it and report back whether your rooms appear. Once confirmed, I'll tag a stable release and then look at per-zone valve/battery/RF-signal sensors from /devices as a follow-up.

[jfhautenauven]

@CaseyRo : you're a fast one :) I was about to send a PR to implement that stuff.
Will send other things :) I'll test your latest changes this evening :) and provide some logs coming from my own setup :)

[jfhautenauven]

@CaseyRo : your new version does what I expect I think, BUT, there is a little something missing IMHO, the name of the zones is included in the data payload, but it is encoded ... decoding it from base64 would be of great help :)

I've sent a PR your way with that :)

[jfhautenauven]

@CaseyRo : here is a dump done with latest beta version. Should contain plenty information for what you need. All zones and all the hardware. Been cautious and redacted more than what i redacted by default by the integration.

The zone names have been replaced with Zone Test 1 → Zone Test 10, always encoded in Base64.
Personal/installer information has been replaced with REDACTED.
identificationKey, serial number, UUID, etc. have been replaced with REDACTED.
Tokens, address, device ID, etc. remain REDACTED.

Bosch_EasyControl_dump_REDACTED.txt

[CaseyRo]

v1.2.0-beta.2 is out: https://github.com/CaseyRo/ha_bosch/releases/tag/v1.2.0-beta.2

@jfhautenauven's PR #12 is merged — zone names are now base64-decoded (so rooms show as Flur/Zentrale instead of Rmx1ci9aZW50cmFsZQ==), and the four solar sensors are skipped when the API reports the solar circuit as unavailable (no more ghost entities on non-solar installs). Merci! 🙏

@jfhautenauven @janfuu-cpu — when you have a moment, please update to beta.2 (HACS → Bosch → redownload, pick the beta) and confirm:

1. your rooms appear with their real names, and
2. (jfhautenauven) the ghost solar entities are gone for newly-set-up entries — existing orphans from beta.1 need a one-time manual delete from the entity registry.

Once you both confirm, I'll tag stable 1.2.0 and then start on the promised follow-up: per-zone valve/battery/RF-signal telemetry from /devices (the dump you posted is exactly what I need for that — thanks).

[jfhautenauven]

@CaseyRo : it mostly works, but there is still something odd ... the zone for my living room (which should be the master zone, the same as CT200) is still missing. Gonna check ... The rest is working ... but not ready yet for stable release, still need to check some things.