Apple Homekit looks better, but it will be sent the target temperature to the reading group address
and not to the additional writing group address which is responsible for adjusting the target temperature.
The integration in the Google Assistant is also wrong. Here only the current temperature is displayed
and you can not set the target temperature at all.
Now my question:
Are these still all bugs or have I set anything wrong?
Here is my entry in the “configuration.yaml” and the group addresses from the ETS5
Same problem here. My configuration is via direct target temperature setting. It’s working fine on Hass but not working at all in Google Home.
Appart from that, I’m a noob too but I think you have a configuration misunderstanding (or is it me?).
Your installation seems to be direct setting like mine. Setpoint shift one is supposed to send steps to rise/lower the temperature as far as I understand it (ie: add 2 steps of 0.5º to current target temp).
According to the Hass KNX climate page:
If your device doesn’t support setpoint_shift calculations (i.e. if you don’t provide a setpoint_shift_address value) please set the min_temp and max_temp attributes of the climate device to avoid issues with increasing the temperature in the frontend.
So… where does “state target temperature” go? I don’t know. I just run an automation on startup to read state target temperature (which I keep in a sensor) and then update the component’s target temperature. This is the way it worked for me.
Please someone correct me if I am wrong so that I can fix my config too
Just in case someone is struggling with a Feller (Schneider) thermostat and a Hager Heating actuator, I’m using the following configuration to get it controlled with HA: