Does anyone else have any experience with a #Mitsubishi #HeatPump that uses a #thermostat with #Kumo cloud support?
We've had ours a year. The Kumo app is just as bad as everyone said (worse actually, that could be a whole other post--it's pretty clearly using a homegrown cross-platform UI toolkit)), but there is a HomeBridge plugin, so at least I can adjust the temperature without using the app and use the app only for scheduling. But none of that is my issue.
Periodically the Mitsubishi thermostat forgets to change the temperature.
We have a trivial program. All week set to 66F at 6am, set to 61F at 8pm.
It has never failed to turn the temperature up. But every few weeks or months it forgets to turn it down. I'll be lying in bed and feeling hot, notice the fans are running, check the temp and see that it claims to be running the program, but it's not. In fact, it's running the heat even though it's a degree above 66F and over an hour since the scheduled drop.
I can futz around with the Kumo app, but it doesn't fix it. I have to manually set the temp to 61F. It happened twice last week.
I've tried disconnecting HomeBridge, just to be sure it isn't interfering. I've tried it with the WiFi hotspot the installers put in (they got tired of debugging WiFi issues for customers). I've tried it with mine. I've erased the schedule and started over.
I cannot believe they released a thermostat with this basic an issue. I've complained via the AppStore. I've complained via a contact address on the website. I'll be complaining to the installers when they do a checkup in a few weeks.
This is nuts. Are they relying on cloud access to do the change? I haven't been able to identify any networking issues at failure time, but their cloud service flakes out every week or so. Is there some obscure C to F conversion bug? (I suspect that's why it reads a degree higher than the set temperature most of the time.)
How could you get something this basic this wrong?
Heat pump and air exchange work great though.