I have a mitsubishi MSZ-FH09NA. I could buy and install the wireless access point to use Kumo Cloud, but I've read nothing but bad reviews. Because of that I grabbed a sensibo, but I'm not very thrilled with it. It only supports about half of the functions of the mini-split.
Could you provide any feedback on Kumo Cloud? Is it as bad as the reviews say?
I had my Mitsubishi mini-split installed about a year ago. Initially all it had was the wireless remote (which is IR). It's okay for basic functions and setting timers but i really wanted more.
I bought the wireless access point which allows you to control the unit remotely with your smart phone or tablet. Last year, I don't know if was their app or their cloud (or both) but response was horrible. About half the time I couldn't connect to it to control it. After the spring of this year there have been several app updates (and maybe cloud updates too) and these problems have vanished. I am always able to connect.
One important feature that having their cloud control adds that wasn't available before (at least I don't think it was available) is the ability to schedule settings for daily or any/every day of the week. I find it very useful for keeping the room comfortable for times of heaviest use and to combat humidity at times where it tends to go up.
I really appreciate the feedback. Outside of Alexa, are you able to hook it up to any other systems?
I think I'm going to give it a shot. The sensibo is ok, but it loses a decent chunk of the functionality of my remote (different airflow programs, can't control the horizontal airflow).
We have a Kumo cloud hooked up to a Mitsubishi mini split. Took about 5 minutes to install. Itโs in an office so we only use it when we are in the room. Installed it back in May and itโs been working great since then. Both via the Kumo Cloud app and Alexa. If I had to do it again Iโd still buy it.
Got everything installed and kumo cloud all setup. I'm much happier with it than a sensibo. I'll be digging into IFTT today. Thanks for the recommendations everyone!
I've just had the a/c installed, but have not yet had a chance to use the Driver for integration. You will have to ask the developer if he's willing to release it to you, as he did for me.
Anyone who has this setup can you let me know, is the "off" option available?? I need to be able to set either heat, cool, auto, dry, AND OFF from within HE.
Thx in advance!
I'd consider writing an integration for Kumo. I am currently writing (incredibly slowly) an integration for the European MelCloud. I'd still recommend looking around for other options, but I may get to this at some point.
Very amusing cultural reference, unfortunately it's mostly boutique craft beers here nowadays
I might be able to get something basic going fairly easily, but I should get something out for the European version first. Let me see where I get to in the next few weeks.
That's an idea, maybe I should charge $1.99 a month if I develop a driver.... . Just kidding, hopefully I can get something going soon for you guys. I'm also happy for anyone else to step in and get started on one.
Based on the connector the wifi adapter uses, and the similar Mitsubishi PAC-US444CN-1 thermostat interface, I wonder if these mini-splits really just talk serial to whatever controller box gets hooked to them. Could be a more reliable, and less expensive, way to control them compared to the wifi box.
Maybe less expensive, but at $150 ea, I'm happy to have the redundancy. HE, in my home with 2 units, has proven not reliable. For me, HVAC should really be reachable, period. So a thermostat, and kumo supported by Mitz, for remote control and HE as a convenience for home automation links is a great mix... for me.
That said, I see why a wired serial link would be a smoother way to fiddle its knobs๐
I'm not sure whether the US adaptors offer this, but the Aus/NZ API documentation talks about being able to control them completely within the local LAN. From memory it talked about issuing a command and getting back the xml as a response that can be used in future requests for the same command.
I haven't looked at it closely for the Aus/NZ (MelView) or Eurpoean (MelCloud) drivers I am writing, but am keen to include it. I'll take a look at the US documentation when I get around to writing the code, hopefully they offer the same feature.
I've got one installed, and another 2 to do. I can confirm the docs say it'll work locally if iNet is down... but the caveat is only for ad-hoc changes, i.e. schedules created in kumo cloud obviously won't be heard if the internet is down. And the kumo cloud schedule is wholly separate from a local thermostat schedule. It operates on a transactional basis, so whichever timer goes off overwrites the last command regardless of which schedule set it. I have the US PDFs of the 2.9 technical and owners manuals and the kumo cloud wifi adapter manual, if that's helpful, lmk. But in all honesty I find they have a lot of pictures, and very little information.