Setpoint shift temperature is not send to KNX bus

I have connected my KNX system to HA. Now that the light, cover and temperature are already successfully integrated, I would also like to integrate the heating as well.

So I created a new entry in KNX.yaml:

climate:
  - name: "KNX_EG_kueche_heizen"
    temperature_address: "0/2/0"
    setpoint_shift_address: "0/2/1"
    setpoint_shift_state_address: "0/2/1"
    setpoint_shift_mode: "DPT9002"
    target_temperature_state_address: "0/2/2"
    setpoint_shift_min: -5
    setpoint_shift_max: 5
    temperature_step: 0.5

As I don’t have a separate state object for the setpoint shift, I use the same group address as for the setpoint shift.

Whenever I set a new temperature setpoint (or more precisely a setpoint shift) via the climate entity, I see the new setpoint until I reload the entity. After reloading, I always get the old setpoint and the setpoint has not been shifted in the KNX system.
When I take a look at the group monitor of the KNX integration, I never see an outbound telegram sent to the group address of the setpoint shift address.

Does anyone have any idea what could be wrong with my configuration?

HA Core version: 2025.2.0
KNX Integration version: 3.5.0 (I guess)

Hi :wave:!
setpoint_shift_state_address has to answer read-requests.

Thanks for your reply!
So I need to have a dedicated group address for the setpoit shift state? I found a few examples where it seems like the state address is optional. But then I will see if my heating actuator supports a setpoint shift state.

Would there be a way to solve the issue if it doen´t support a setpoint shift state? Like creating a template sensor with the setpoint shift, expose it to KNX and then read it for the climate entity?

No, wait… I just need to set the read flag for the group address of the setpoint_shift_address?!

Exactly.
setpoint_shift_state_address is not optional if you use setpoint_shift_address… but it can be set to the same address, that’s no problem.

1 Like