The previous ecobee plugin read temperature to the tenth (.1) degrees (70.1, 70.2, 70.3). The current one reads temperature only to integer degrees (70,71,72) is there any way to get back that functionality?

When using the new integration of Ecobee with PG3 HomeKit, the extra precision is lost... it appears to be a HomeKit thing. If you were to use a pure (non-PG3) Ecobee pairing with a real Apple Hub or Apple Home, you would see the same thing.

I have experimented on Home Assistant where I have done an Ecobee integration with the HA version of HomeKit. Out of the box, I see the same whole degree reporting only. The odd exception I found is that there is a way with the HA Ecobee integration to HA HomeKit to extract (using templates) a temperature with more significant digits. In doing so, I did not go the extra mile to determine if I was seeing the Average Temp (Thermostat average with remotes) or the actual temperature of the thermostat sensor, but at the time I believed it was returning the sensor value in the thermostat.

To the best of my knowledge, the API connection to Ecobee method seemed to be the only way to get that extra precision. I too had the same issue as I used the ecobee thermostat temperature sensor to control all the programs I have for controlling my fans. That extra degree of control down to xx.x makes a big difference on controlling the fan speed and direction.

I was guessing that would be the reason, too bad, yes the extra precision really helps the math in my programs. HA sounds interesting but I’m afraid my systems are already too complex so I’d rather not add another system.

@ISY4Me

Ecobee linked via HomeKit in Home Assistant does show the temperature decimal as do each of the remote sensors.

4 hours ago, Diesel said:

Ecobee linked via HomeKit in Home Assistant does show the temperature decimal as do each of the remote sensors.

Looks like you are in Canada? What the HomeKit Accessory Protocol (HAP) gives in a fast and local connection, it takes back in a reduced feature set and, well, 'wonkyness'. The ecobee is likely set in degrees F, but HAP ships the data in C. So the tstat values are converted from F in ecobee, converted to C for HAP and converted back to F in plugin/HA. So in the US in degrees F, the double conversion hurts.

8 hours ago, ISY4Me said:

I have experimented on Home Assistant where I have done an Ecobee integration with the HA version of HomeKit. Out of the box, I see the same whole degree reporting only.

However, You can get the tenths on HA>Ecobee>Homekit device. There are sensor entities not exposed by the main controls presented in the default dashboard.

Go to Developer Tools > States and paste in sensor.*_current_temperature. That will give you the ecobee entity to use to get degrees F in tenths, see below. Oddly, in another "wonkyness" moment, my remote ecobee sensor does report in tenths via the default entity.

I'm not trying to steer this convo to HA; I'm guessing something like this is possible for the Ecobee HomeKit plugin.

@paulbates Yes, your neighbour in Canada 👋 Ecobee and Home Assistant are both set natively to C so no conversion or wonky behaviour here.

3 hours ago, Diesel said:

@paulbates Yes, your neighbour in Canada 👋 Ecobee and Home Assistant are both set natively to C so no conversion or wonky behaviour here.

👍 and I was not inferring the Canada or Celsius are wonky🤪. (I watched America try and fail at metric conversion in the 1970s and really wish we had finished the job). It's wonky to have to convert and convert back again.

Now they want to mess with keeping Daylight Saving time.

Every time some politicization tries to do what they think I need the short end of the stick is all get. ☹️