Problem with a Climate Entity - Wrong Value / Attribute used for Target Temperature

[Tra1n84]

Hej,

I have noticed that an incorrect attribute is being used for the Target temperature at the module for Climate entities:

The climate module is using the Max. Temperature (see red marking, attribute max_temp) instead of Temperature (see green marking, attribute temperature). See Attributes for this Climate entity from the Developer Tools:

Could you please check this behavior? Or is something wrong on my side?

Thanks & Best regards Thomas

[patricknitsch]

I have the same problem at one from thirteen modules. The other modules work correctly.

[Tra1n84]

You're right. I dont have this with other Climate entities either. That's really strange as the other Climate entities tested are of the same Homematic type as the one with the described problem...

With another climate entity of the same model / interface it is correct:

Now the question is why?

[anarion80]

I have the same issue for only some climate entities. The issue happens here: https://github.com/matt8707/ha-fusion/blob/94cd223610a61d3510b303be745f140c27d6d855/src/lib/Components/WheelPicker.svelte#L54

value is -1 because my temp is with .1 precision: 12.3, and that doesn't match any calculated temperatures between min and max, so the first value is selected,

We should then somehow factor in the step, perhaps from target_temp_step you have in the screenshot above. But then my entities don't have that...:

[mucki12]

Sorry, but shouldn't this commit fix this: ?