Decimal Precision Differs on Climate entity vs related Temp and Humidity Entities.

[gregorymartin]

Is it possible to adjust the decimal precision to match across the entire Device? Right now I see:

• Device current temp: rounded to nearest degree
• Device point: one decimal place
• Device humidity two decimal places
• Current temp entity: one decimal
• Current humidity entity: one decimal

I think 1 decimal all around would be appropriate.

Image to illustrate:

[dlarrick]

I'll take a look through, but I'm not sure how much of this is under the integration's control. I recall one spot where we set precision but maybe there are others where we could.

[barndawgie]

I get totally different precision on my install:

[gregorymartin]

Ah, for the entities, I manually adjusted the precision in their settings. It’s the climate entity’s precisions that are really the question.

[dlarrick]

Hmm, all the sensors defined in https://github.com/dlarrick/hass-kumo/blob/master/custom_components/kumo/sensor.py declare that they are PRECISION_TENTHS. Are you sure you're using those sensors, not a template (as was necessary when this integration was first published)?

Also: the default precision for Climate entities is TENTHS for celsius, WHOLE for farenheit. I'm concerned that if we hard-code the precision there to TENTHS then adjusting setpoints will become difficult using up/down buttons. But feel free to experiment and share your findings here.

[zach-rosen]

Because Kumo seems to use a lookup table to convert from C to F, there's a lot of "rounding" that happens during conversion both ways. However, I've found (anecdotally) that controlling via F using tenths of a degree does allow a more accurate setting after Kumo has converted it internally back to C using its LOT.

I've added the following override kumo/climate.py

    @property
    def precision(self):
        """Return the precision of the system."""
        return PRECISION_TENTHS

adjusting setpoints will become difficult using up/down buttons

simple-thermostat lets you set this in the card, but it also looks like Climate entity has a target_temperature_step property you could customize.

[zach-rosen]

BTW, you SHOULD be able to customize precision from config.yaml…

  homeassistant:
    customize: 
      climate.kitchen:
        precision: 0.1

    def state_attributes(self) -> dict[str, Any]:
        precision = self.precision
        ATTR_CURRENT_TEMPERATURE: show_temp(hass, self.current_temperature, temperature_unit, precision)

... but state attributes don't look impacted by the setting:

	min_temp: 60
	max_temp: 80
	current_temperature: 70
	temperature: 65
	precision: 0.1

I think this is an HA bug but can't seem to track it down.