KNX Integrate Busch Jaeger 6124 Room Temperature Controller in Cooling Mode

Configuration
1

Hello everyone!

my KNX setup has been woking smoothly for years and so did Home Assistant. This included nine climate controllers (Busch Jaeger 6124/01 ~built 2014) controlling corresponding valves for the floor heating. Up until now I was able to set the base_target_value_heating via climate.target_temperature_address and it directly corresponded to current_target_value via climate.target_temperature_state_address.

Now our new heat pump is capable of cooling, so I configured one of the climate sensors for cooling, which seemed quite straight forward:

  • DPT 1.100 (from HA or heatpump) sets the controller to “cooling”
  • DPT 9.001 to set the temperature
  • If target < current, open valve

But the controller behaviour changed quite a lot after activating cooling. I basically have these GAs right now:

  • base_target_value_heating: Set comfort heating temperature as baseline
  • current_target_value: Output whatever the controller calculates as the target temperature
  • target_value_heating: Set or output the desired temperature in heating mode
  • target_value_cooling: Set or output the desired temperature in cooling mode

This leaves me with two options to set the temperature, none of which really works in HA:

  • I could set the base_target_value_heating, but base_target_value_cooling is derived by adding 4K (configurable, but always ≥ 1K). This means setting this value to 21 °C sets an effective cooling target temperature of 21 °C +4K = 25 °C. Setting the slider in HA to 21 °C makes it immediately flip to 25 °C :-1:

  • I could directly set the GA for target_value_cooling and it directly corresponds to current_target_value. But what if it’s winter? Then I’d have to set the GA for target_value_heating instead. I can not use the same GA for both values as the controller makes sure that the dead zone is used, so setting target_value_heating to 21 °C when in cooling mode pushes target_value_cooling and current_target_value to 25 °C again :-1:

From the top of my head I would need something like separate target_temperature_cooling_address and target_temperature_heating_address in the KNX config, but I suppose that is not the correct way to do it. The controller sadly doesn’t support setpoints.

I’m open for suggestions. Did you have similar problems? How did you solve it? Is there anything obvious I’m missing or is there anything missing in my description?

Thanks!
Oli

2

Hi :wave:!
I’d have 2 ideas

  • use 2 separate climate entities
  • use a new (or internal) GA for setting target value and forward to cooling/heating based on current mode in an automation
1 Like
3

Can someone support me with the yaml code to get the temperature Busch Jaeger 6124/01? I tried
knx:
sensor:
- name: “Temperatur Wohnzimmer”
temperature_address: “1/1/36”
type: string

- name: "Temperatur Wohnzimmer1"
  state_address: "1/1/19"
  type: 2byte_float

in the group monitor on HomeAssistant I see 0x0c34 21.52, but in HomeAssistant I get Unavailable.

4

Please have a look at the documentation: https://www.home-assistant.io/integrations/knx/#sensor
There’s no “temperature_address” for sensor entities.

5

I do not get it. in group monitoron HA I see:

17:52:08.225 + 00:00.826 1.1.29 Busch-Jaeger Elektro Taster WZ RTR 12 4/0/17 Geräteregelung Wo GroupValueWrite Incoming 0x0c01 20.5

Source is 1/1/29 and Destination is 4/0/17

So it is not possible to get the payload/value into a sensor?

6

You’ll likely want this, not the source. Source is an IA (Individual Address eg. 1.2.3) whereas destination is a GA (Group Address eg. 1/2/3).
The addresses in configuration are always GAs.