Excellent. Thanks.
Phew... I'm not the only one...
How much do I win....? 
A free C8 Pro...
1 Like
There should be points awarded for problems 'solved'. Maybe fewer for those identified, lol. With a free hub as a prize at the end of the month, lol.
1 Like
If only we had a method to measure that... 
I don't think the problem is with the dashboard at all. All the tile does is call the setThemostatCoolingSetpoint or setThermostatHeatingSetpoint command method in the driver, and it sends it a value which comes from the current value for thermostatHeatingSetpoint or the thermostatCoolingSetpoint it gets from the driver, +/- the increment value set in the tile settings. The driver handles any conversions for types or scales used.
You should see the same behavior if using the setpoint commands on the driver page, as that is all the dashboard tile is calling. It must be something in the Homekit Integration, in how the current value of the setpoint comes in to the driver, and/or what the integration does after the Hubitat driver updates the setpoint values.
Just checked on this...set my Ecobee to 86 (was 87.1) and the set point is not moving around on the dashboard tile, stays stuck at 86, and same on the HomeKit Ecobee Device page and the thermostat itself. Also have Ecobee community integration and set point is stable there as well.
I have a different model Ecobee ("Smart Thermostat Enhanced") so maybe something due to that? Seems like if this were due to a general rounding issue on Legacy dashboards I'd have the same problem. This is on C8-Pro, 2.4.2.125.
2 Likes
For my Mitsubishi driver's the conversion was in the driver and needed some fudge factor or something similar to get it to work for certain values. I'm sure Victor will sort it out.
2 Likes
This ^^^ 
2 Likes
