There are a couple if discussions arounnd this topic but there is a specific issue that causes troupble sind MDT did not do a good job in directly forwarding a operation mode states object itself. Otherwise the visualization of the status will not be up to date. Luckily I had to self that already before switching to home assistant.
At least MDT forwards a non DPT compliant object:
The type is actually defined by some KNX extension.The first Nibble of the 1 Byte contains the information while the upper 2nd Nibble contains additional status information which we do not care. We can of course filter it but have to also send it back to knx so we can use it for our climate entity. So here is a simple procedure:
- Consider the propriataty “HVAC Status” as a 1 byte sensor in your knx.yaml
sensor:
- name: "hvac_status"
state_address: "2/0/5"
type: 1byte_unsigned
-
Create a dummy group address in your ETS to maintain the required operation_mode_state_address object for homeassistant. ETS allows to add such dummy devices.
-
Expose the address which you use for the entity attribute “operation_mode_state_address” of the respective climate entity in your knx.yaml expose
expose:
- type: "1byte_unsigned"
address: "2/0/6"
entity_id: "sensor.hvac_mode_status"
- Translate the hvac_status sensor entity (of step 1) to the exposed attribute hvac_mode_status of step 3 in your configuration section with a template filtering values
sensor:
- platform: template
sensors:
hvac_mode_status:
value_template: >
{{int(1) if is_state('sensor.hvac_status','33') else int(2) if is_state('sensor.hvac_status','34') else int(3) if is_state('sensor.hvac_status','36') else int(3)}}
- Assign the same group address of sensor.hvac_mode_status to the operation_mode_state_address attribute of your climate entity
- name: "Example Climate Entity"
...
operation_mode_state_address: "2/0/6"
...
Of course let’s discuss if there are better ideas or improvements.
!