out_of_range error with Bosch BTH-RM230Z

[leow149]

Home Assistant 2025-12-24 00_26_31.json

Bug: out_of_range during calibration loop in Advanced Heating Control (Bosch thermostat BTH-RM230Z)

Summary

Using the blueprint panhans/advanced_heating_control.yaml with a Bosch thermostat model BTH-RM230Z causes the automation to fail with out_of_range during the calibration step when calling number.set_value on the local temperature calibration entity.

Environment

• Home Assistant: 2025.12.4
• Blueprint: panhans/advanced_heating_control.yaml
• Thermostat model: Bosch BTH-RM230Z
• Climate entity: climate.thermostat_wohnzimmer
• Calibration entity: number.thermostat_wohnzimmer_local_temperature_calibration
  • min: -5
  • max: 5
  • step: 0.1

Reproduction steps

1. Configure the blueprint with the Bosch thermostat (BTH-RM230Z) and an external temperature sensor.
2. Let the automation run until the calibration logic is triggered.
3. The automation attempts to write a calibration value using number.set_value.
4. The script aborts with out_of_range.

Actual behavior

• number.set_value is called with an absolute temperature value (e.g. 21.5).
• The calibration entity expects an offset in the range -5 … +5.
• Home Assistant throws out_of_range and the automation stops.

Expected behavior

The blueprint should treat Bosch BTH-RM230Z calibration as an offset-based calibration and:

• use calibration_common, or
• convert absolute temperatures to offsets, and
• clamp and round values to the entity’s min, max, and step.

Suspected cause

Bosch devices are grouped with DPH valves, causing the DPH calibration path to write absolute temperatures into an offset-style calibration entity.

Suggested fix

• Exclude Bosch devices (BTH-RM230Z) from the DPH valve group, or
• Detect offset-style calibration entities and route them through calibration_common, or
• Clamp and round calibration values before calling number.set_value.

[panhans]

Hi, thanks for reporting. I revised the calibration logic and this should be fixed with the next stable release. But if you like you could test it by yourself:

https://github.com/panhans/HomeAssistant/blob/xmas_release/blueprints/automation/panhans/advanced_heating_control.yaml

[leow149]

Can't import sadly. Fails with this error:

Invalid blueprint: extra keys not allowed @ data['blueprint']['input']['toggle_section']['input']['input_fallback_outside_temperature_unavailable']['selecor']. Got {'boolean': None}

[panhans]

Sry, there was a typo. Feel free to try again.

//EDIT: but I think I there is another issue with another feature. Will fix it in the next minutes.

//EDIT2: fixed :P

[leow149]

trace automation.ah_wohnzimmer 2025-12-28T22_20_00.071251+00_00.json

The automation still calculates the thermostat calibration incorrectly by treating the calibration entity as an absolute temperature instead of a temperature offset.
It attempts to set the calibration value to approximately the external sensor temperature (21.3 °C) rather than the expected offset ( 0.6 °C).
Because the calibration number entity is limited to a range of -5 to +5, this value is clamped to the maximum, resulting in a calibration of +5.
The trace shows that the number.set_value service is executed successfully, so no error is raised even though the result is wrong.

//EDIT: I also see those two errors in my logs:

Quelle: helpers/script.py:2064
Integration: Automation (Dokumentation, Probleme)
Erstmals aufgetreten: 23:03:19 (24 Vorkommnisse)
Zuletzt protokolliert: 23:49:04

AH Wohnzimmer: Choose at step 4: default: If at step 8: If at step 2: Repeat at step 1: Error executing script. Error for if at pos 4: missing_target_temperature_entity_feature
AH Wohnzimmer: Choose at step 4: default: If at step 8: If at step 2: Error executing script. Error for repeat at pos 1: missing_target_temperature_entity_feature
AH Wohnzimmer: Choose at step 4: default: If at step 8: Error executing script. Error for if at pos 2: missing_target_temperature_entity_feature
AH Wohnzimmer: Choose at step 4: default: Error executing script. Error for if at pos 8: missing_target_temperature_entity_feature
AH Wohnzimmer: Error executing script. Error for choose at pos 4: missing_target_temperature_entity_feature

Quelle: components/automation/__init__.py:799
Integration: Automation (Dokumentation, Probleme)
Erstmals aufgetreten: 23:03:19 (4 Vorkommnisse)
Zuletzt protokolliert: 23:49:04

Error while executing automation automation.ah_wohnzimmer: missing_target_temperature_entity_feature

[panhans]

Could you try the latest version?

[leow149]

Hi, sorry for the late reply.
I still get this error with the latest version: missing_target_temperature_entity_feature

EDIT:

The entity has those features:

hvac_modes:
  - "off"
  - heat
  - cool
min_temp: 5
max_temp: 30
target_temp_step: 0.5
current_temperature: 22.5
target_temp_high: 30
target_temp_low: 22
current_humidity: 31.49
hvac_action: idle
friendly_name: Thermostat Wohnzimmer
supported_features: 386

[panhans]

In the trace log you've posted there is no error shown. But the current state of your thermostat is unusal, especially the temperature:

"climates_information": [
  {
    "entity_id": "climate.thermostat_wohnzimmer",
    "state": "heat",
    "temperature": null,
    "current_temperature": 22
  }
]

The calibration values get clamped by the min and max of the calibration entity:

"calibration_changes": {
  "climate.thermostat_wohnzimmer": [
    {
      "calibration_entity": "number.thermostat_wohnzimmer_local_temperature_calibration",
      "value": 5,
      "select": null,
      "value_old": "0"
    }
  ]
}

Could you try setting the temperature by calling this action in the developer tools?

action: climate.set_temperature
target:
  entity_id: climate.thermostat_wohnzimmer
data:
  temperature: 20

[leow149]

That action throws the following error:

"Die Aktion 'Temperatur einstellen' wurde mit dem Parameter 'Soll-Temperatur' verwendet, die Entität unterstützt diesen jedoch nicht."

("The 'Set temperature' action was used with the 'Target temperature' parameter, but the entity does not support this.")

[panhans]

Ok, bei dir fehlt das temperature feature, wie bspw. hier:

hvac_modes:
  - "off"
  - auto
  - heat
min_temp: 4
max_temp: 35
target_temp_step: 0.5
current_temperature: 21.5
temperature: 22
hvac_action: heating
friendly_name: Esszimmer Thermostat Links
supported_features: 385

Daher schlägt der Standardbefehl zum setzen der Zieltemperatur fehl. Hast du das thermostat in einem besondern modus? Preset / Automatikmodus?

[leow149]

Das Thermostat hat 3 Modi, manual, schedule und pause. Es steht gerade auf manual

[panhans]

Da gab es wohl eine Änderung bei Z2M. Aktuell lässt sich bei dem Bosch Thermostat nur eine obere und untere Grenze setzen.

home-assistant/core#159272
Koenkk/zigbee2mqtt#30287

Mit einem rollback von z2m, geht's wohl wieder: home-assistant/core#159272 (comment)

Die Frage ist, ob das so gewollt ist, oder ein Fehler. Du kannst ja gern in dem Thread von z2m mal einen Kommentar dalassen. Ich würde sonst die Blueprint so umbauen, dass diese Grenzen gesetzt werden, vllt. zusätzlich noch einen offset wert zulassen um die das Temperaturfenster nach belieben zu öffnen.