HA KNX Climate does not generate unique ID

Configuration
,
1

Hey Guys,

I’m facing the following issue:

Schermafbeelding 2021-04-12 om 19.18.19
Schermafbeelding 2021-04-12 om 19.18.191319×100 40.2 KB

with the configuration below. Can someone tell me why this error is happening? I know the value 6/1/0 and 6/1/1 are re-occuring but the could not be changed due to limitations in the KNX application.


  climate:
    - name: 'Klimaatregeling Hal'
      setpoint_shift_address: '1/2/2'
      setpoint_shift_mode: 'DPT9002'
      temperature_step: 0.5
      target_temperature_state_address: '1/2/1'
      operation_mode_address: '1/2/3'
      operation_mode_state_address: '1/2/4'
      temperature_address: '6/1/1'
    
    - name: 'Klimaatregeling slaapkamer rechts'
      setpoint_shift_address: '1/0/2'
      setpoint_shift_mode: 'DPT9002'
      temperature_step: 0.5
      target_temperature_state_address: '1/0/1'
      operation_mode_address: '1/0/3'
      operation_mode_state_address: '1/0/4'
      temperature_address: '6/1/0'
      
    - name: 'Airco Slaapkamer rechts'
      on_off_address: '3/0/8'
      on_off_state_address: '3/0/0'
      temperature_step: 0.5
      min_temp: 5
      max_temp: 25
      target_temperature_address: '3/0/7'
      target_temperature_state_address: '3/0/7'
      controller_mode_address: '3/0/9'
      controller_mode_state_address: '3/0/1'
      temperature_address: '6/1/0'
      
    - name: 'Airco Slaapkamer links'
      on_off_address: '3/1/8'
      on_off_state_address: '3/1/0'
      temperature_step: 0.5
      min_temp: 5
      max_temp: 25
      target_temperature_address: '3/1/7'
      target_temperature_state_address: '3/1/7'
      controller_mode_address: '3/1/9'
      controller_mode_state_address: '3/1/1'
      temperature_address: '6/1/1'
    
    - name: 'Airco woonkamer'
      on_off_address: '3/2/8'
      on_off_state_address: '3/2/0'
      temperature_step: 0.5
      min_temp: 5
      max_temp: 25
      target_temperature_address: '3/2/7'
      target_temperature_state_address: '3/2/7'
      controller_mode_address: '3/2/9'
      controller_mode_state_address: '3/2/1'
      temperature_address: '6/1/1'
2

temperature_address is used for unique_id now. As a workaround you can use the expose function to clone the group address (its value) to a different (unused) group address for the second climate device.

3

Hi, Same problem for me. Could you be so kind to publish an example config? I cannot understand how to clone the adress using the expose fuction.

4 
knx:
  expose:
    - type: temperature
      entity_id: <first climate entity id to clone the temperature from>
      attribute: current_temperature
      address: <any unused GA that will be used in the second climate entity>

this should work. You may find warnings in the logs about HA not being able to read from the new address.

1 Like
5

Tank you! I works :grinning:

6

This should be fixed in 2021.5
The unique_id is now generated from multiple GAs so you can remove the expose again.

7

Hi Matthias,

Thanks! i’m updating now. will let you know if there are any issues.

8

It will probably leave an orphan entity after you changed the GA. You can delete it and rename the entity_id and name (remove “_2”) of the new entity.
Or you delete the entity before updating.

9

The issue is resolved, thanks for the effort!

1 Like
10

im not sure why this says fixed ?
i cant give a unique id to a climate sensor so i cant expose it to google home

11

What do you mean? All knx entities have a unique_id, that’s not separately configurable.

12

I guess I was referring to climate group in general that still doesn’t have a uid so I can expose it to Google home for example