Open PapaMater opened 1 year ago
See https://github.com/dlarrick/pykumo/issues/15
The Kumo Cloud app uses, inexplicably, a lookup table for C <-> F conversion. We haven't figured out a good reason for this.
The Kumo HA integration does processing solely in Celsius, the indoor unit API's native temperature unit. All conversion to F is done by Home Assistant itself. I would argue that HA's temperature conversion and display is more accurate.
If we wanted to precisely match the Kumo Cloud app, we'd have to:
The result would be a double conversion, since HA's own internal temperature unit is C.
Nobody has been interested enough to put together patches to implement this. Instead, anecdotally most users stop using the Kumo Cloud app except for occasional use.
Sorry for the long pause from open to review. Thanks for the explanation and I agree that some things clearly aren't worth the investment. One could likely get around this issue easily enough, but I believe this also caused issues when setting temp from this integration. I would love nothing more than to ditch Kumo altogether but have had my units go completely offline and unresponsive until they are allowed to phone home on restart. Probably an inappropriate place to ask, but is there any explanation and/or (hopefully) resolution for that behavior? I ask because I believe having a single point of control (be it Kumo App, or HA) is much more stable and reliable; ie makes the temp irregularity irrelevant. Much appreciation for putting this together though. Forcing devices/control into the cloud where they could decide to put up a paywall or stop supporting altogether is digital serfdom. My hat goes off anyone willing an able to give us back a slice of our autonomy.
See discussion in #105. TL;DR: Mitsubishi broke something, and I've done all the workarounds I can think of.
The target temperature displayed in home assistant is 1 degree F lower than the corresponding value in Kumo Cloud app