KNX Climate heating actuator MDT

Wasserspiele · December 14, 2023, 8:26am

Someone has a neat solution for integrating the valve into climate?

farmio · December 14, 2023, 9:41am

command_value_state_address:?

Wasserspiele · December 15, 2023, 8:38am

Thanks.

I’m struggeling when setting a new target temperature.

    - name: "Climate"
      temperature_address: "1/2/10"
      temperature_step: 0.5
      target_temperature_address: "3/3/2"
      target_temperature_state_address: "1/2/11"
      command_value_state_address: "3/2/2"
      min_temp: 18.0
      max_temp: 25.0

Values:
3/3/2: 20.5
1/2/11: 21
1/2/10: 20.2
3/2/2: 49%

I changed 1/2/11 from 20.5°C to 21.0°C- FHEM recognizes it correct, but HA still shows 20.5°C…

farmio · December 15, 2023, 9:00am

Hard to say without knowing your ETS GA connections or a Group monitor screenshot.

Wouldn’t you set 3/3/2 for the new value and get the new status from 1/2/11

Wasserspiele · December 15, 2023, 9:10am

Exactly what I would expect. I changed the value not via HA but via MDT Glass Push-button II Smart.

And I can confirm that the value for 1/2/11 is now 21 - the right new set target temperature.

But HA seems to not have received this value properly?

Okay group monitor proofes it was send:

Wasserspiele · December 15, 2023, 9:15am

Created a second example:

    - name: "EG Büro Heizung"
      temperature_address: "0/6/36"
      temperature_step: 0.5
      target_temperature_address: "3/3/3"
      target_temperature_state_address: "0/6/37"
      command_value_state_address: "3/2/3"
      min_temp: 18.0
      max_temp: 25.0

Changed from 19.5 to 20.0

But I’m wondering about this:

Maybe I need to check my ETS settings again…

farmio · December 15, 2023, 9:30am

Yes probably. And when you are at it, unless you use routing with multiple areas maybe try to clean up your individual addresses. 12.0.1 looks a bit awkward. This may lead to problems with couplers.

InventoCasa · January 31, 2024, 12:52pm

Hi,

I’m also struggeling with the correct config. My current config looks like it would work, but it doesn’t. I can set a target temp but the actuator seems to ignore it.
Here are some screenshots from ETS and HA - hopefully @farmio or somebody else can help me - Thank you in advance!

Lovelace dashboard:

Developer settings screen in HA:

KNX config in HA YAML config:
grafik

ETS:

farmio · January 31, 2024, 2:36pm

Hi !
1bit setpoint shift setup doesn’t work with HA.Id recommend to use 2byte float if your actuator supports it. Also see if you can get a GA with a dedicated state object.
A proper configuration should be found somewhere in this thread.

AndiE1234 · January 31, 2024, 10:38pm

I use the 2 Byte Shift. But after power off HomeAssistent and KNX at the same time the shift is back to 0.
Does have anyone a solution? Next week i will test shifting over the comfort setpoint. I don’t know If it works also with the Glastaster, but Not important because for the Temperature settings is use only HomeAssistent.

apfelklaus · February 2, 2024, 2:59pm

Hello together,

I have the issue that my thermostat in the UI is not working properly

If I use following config. The current and the target temperature is shown correctly:

climate:
  - name: "Büro Thermostat"
    temperature_address: "5/1/0" # Temperaturmesswert
    target_temperature_state_address: "5/1/1" # Aktueller Sollwert

but when I add the target temperature it’s not working properly → target_temperature_address

climate:
  - name: "Büro Thermostat"
    temperature_address: "5/1/0" # Temperaturmesswert
    target_temperature_state_address: "5/1/1" # Aktueller Sollwert
    target_temperature_address: "5/1/6" # Aktueller Sollwert

The temperature is changed successfully on the KNX bus and the MDT Glastaster II when I change it in the UI

But when I change the target temperature on the Glastaster II the UI / thermostat is not showing the new target temperature in the UI as before without:
target_temperature_address

The value is arriving correctly in home assistant:

also the legacy openHAB instance is showing the new target value from the bus correctly.

Is that a bug in Home Assistant or I’m configuring it wrong?

farmio · February 2, 2024, 3:10pm

Hi !

Is there a telegram received to your target_temperature_address after target_temperature_state_address? This would update the shown value.

apfelklaus · February 2, 2024, 6:15pm

You were right! My KNX electrician fixed it - hopefully everything keeps working

evolution100 · March 31, 2024, 7:28pm

Hi together,
i’m sorry… i’m an absolute newbie with a short question…
I added my heating actor to HA which is working fine. Now i want to add e.g. the
temperature_address to a card (only this value to the yaml) in my dashboard. How can i do this? i do not find this value as an entity

Like with the wind sensore

info_entities:
  - entity: sensor.wetterstation_windgeschwindigkeit

AndiE1234 · March 31, 2024, 7:41pm

 views:
   - path: default_view
     title: Home
     visible:
       - user: 83d0884f31b74d25a022ae9e5f99a344
     badges: []
     cards:
       - type: entities
         entities:
           - sensor.wetterstation_windgeschwindigkeit

evolution100 · March 31, 2024, 9:12pm

Sorry… i have a problem with the climate…

here more details

in my knx.yaml i defined

climate:
  - name: "Büro"
    temperature_address: "5/1/13" # Sensoren_Schalter-Temperatur
    setpoint_shift_address: "4/1/99"

so i get the heating control in the dash board.
Now i only want to use temperature_address in a room card

…
type: custom:room-card
title: Testzimmer
info_entities:

entity: climate.buro.???
…

but i do not know, how to have access to the temperature_address in the card

shot update…
I added in the knx.yaml an additional sensor
…
sensor:

name: “Test Heizsensor Büro”
state_address: “5/1/13”
type: temperature
…

with this i have an entity which i can use in the room-card. But is this the correct way, to set up ONE knx group address to more domains?