This isn’t directly helpful, but FWIW, when I was having a mini-split system put in earlier this year, the A/C contractor I used had very little clue about home automation compatibility at all. I had to badger them to give me access to their (Mitsubishi originated) internal documentation, intended for installers, to get details I needed.
I ended up with just the WiFi adapter, no MK, plus the standard (dumb) handheld remote, and it’s worked just fine for me. Mostly Home Assistant turns the unit on and off and sets the temperature, and when I need “local override” the remote is easy enough to dig out of its drawer.
I have the same setup and by leveraging this integration, some external z-wave temperature sensors (better accuracy based on room placement than the onboard temperature from what I can tell), and some automations, I’ve been able to create a fairly robust, multi-zone, “smart” thermostat.
Thank you everyone for the additional information, it really helped me sell it to my other half. We are going to have z-wave motion/temp sensors in every room already, so I will be able to work out a robust enough system to make the family happy.
Just for completeness, there are a couple other ways to control these units via Home Assistant, building or re-purposing hardware to talk to the unit’s CN105 interface (the same port the WiFi interface plugs in to). If you Google for “mitsubishi” and “cn105” and “home assistant” you’ll find those projects.
I’m biased, of course, since I wrote this Kumo integration but if you want to do more work but do this this more cheaply and/or without any dependence on a cloud service at all, you might consider those other options.
Follow up question about this. Like most stories I have heard so far, the HVAC installer really has no clue about integrating with existing home automation, so I have to ask the people who make it happen.
I am putting in a 1.5 ton ducted unit, and 4 cassettes. The installer indicated that without a connected temperature probe for each unit, I would be unable to fully turn the fans off. Do you know if this is true, or just a limitation of the KUMO app?
Another question I was unable to get a definitive answer to: do I need 1 WiFi adapter for each unit, or just a single one for the “central” unit?
In my case, each unit has its own wifi adapter. I do not have external Mitsubishi temperature sensors, there are build in sensors on the unit. My understanding is the external sensors are for accuracy.
I’m actually a Mitsubishi Technical Advisor. Yes, If you want to have the fans shut off when satisfied, you must use the remote sensor. The internal sensor will get fooled by the coil without air moving across it.
One wifi adapter per indoor unit is required.
My 3 indoor units each have their own WiFi adapter. The outdoor unit is not part of the KumoCloud architecture, from what I can tell. I’ve been hoping to find a way to get current power levels via API, but instead I’ve installed a Shelly EM to measure the energy consumed by the system as a whole.
I have one remote sensor for a zone that serves a large area. I was able to purchase it aftermarket and install & pair it myself. The sensor is at a distance from the unit, so it’s measuring the temperature of the room more accurately rather than just the intake air. The remote sensors also have a humidity sensor, which the indoor units (at least my model) do not. With the exception of the humidity display, this unit appears identical to the others via KumoCloud app or in HA.
I am having an issue with the script getting the correct IP address for each of my 5 units and the Kumo controller.
I can look at the kumo_cache.json and see all the units and all of the information is correct - except the IP, so all of the API calls are failing since the IPs being used don’t exist. I would try to change them manually in the cache file, but I don’t know which unit is which when I look up connected clients in UniFi.
I’ve tried opening the app several times, that works fine and I can control the units. I’ve deleted the cache, and uninstalled and reinstalled the integration several times, but same results each time.
Edit: I also ran through the Wifi setup wizard in the Kumo Cloud app and reconnected all of the units, but no change.
What’s a “Kumo controller”? Each indoor unit has its own WiFi adapter; the outdoor unit has none (may not even have a CPU).
What’s the manner of the incorrect-ness in the IP addresses? Are they old/stale addresses? In the wrong network? Missing entirely?
If all else fails, the MAC addresses are written on the enclosure of the WiFi adapters, so if you can correlate that way you can edit your kumo_cache.json and it should work. Once you have it working make sure to turn on the “prefer cache” setting.
Sorry - Kumo Station (PAC-WHS01HC-E)… but I guess that’s irrelevant - it has a Kumo Cloud Adapter (PAC-USWHS002-WF-1) plugged into it.
The IPs are for the correct network, but they are old. They happen to be sequential, but I don’t recall ever setting them manually, so I’m guessing it’s held on to them from when they were first added to my network. My UniFi controller reports them as different IPs.
I have the MSZ-GLxxNA units, which as far as I can tell have the wireless units built in, because there’s no extra adapters visible and when I open the cover, I don’t see an adapter, so I’m not sure how to get the MAC address.
I will see if I can identify them and update the cache file. Thanks for your help.
My units are also MSZ-GLxxNA and definitely needed a separate WiFi adapter. It’s installed behind a pop-out panel on the bottom right corner of the indoor unit (the L-shaped panel with a bunch of punch-out discs in it, though none of mine are punched out).
Has anyone had issues signing in? I’ve gone through both the UI and the config file, and I get invalid password every time. I’ve change my login and password to avoid special chars, etc, and nothing seems to help. However, I have hit the Kumo API manually and my password works just fine. So it appears to perhaps be something related to how HA stores the password?
Hi all, first off thanks to those who created this. I migrated over to this after the IFTTT announcement and this more functional, and much more reliable than the IFTTT/Kumo app combined function. I have a question though, does anybody use HA to replicate the low temp switchover to your homes primary heating system and how do you accomplish this? I.e. through the Kumo app, my split systems shut off at 25F outside temp, and turn on the heat via our Nest thermostats, and vice versa turn off the oil heat when above 25 and turns on the splits. The setting for this is in the installer settings in the Kumo app.
Also does anyone know a way to pull to HA the real time outdoor temp measurement from the outdoor sensor wired into the Kumo station (this is also visible in the installer settings on the Kumo app under ‘advanced’)?
While I haven’t done this yet, it is on my list to do. Basically you need to leverage an HA integration that gives you outdoor temperature (I’m using Dark Sky). In my case, I have a set of automations for each Kumo unit that turn heat/cool/off based on time, temp, etc. You would simply need to add outdoor temp as one off the conditions in such a case.
As far as the outdoor temp from the Kumo Station: it’s likely to be possible (we pull the temperature and humidity from separate indoor sensors now), but someone with a Kumo Station is going to have to figure it out. If you have an IP address (either from kumo_cache or through some other means) and some Python skills you could try to connect to the Kumo Station using the existing pykumo library and see what you get.
Thanks! Unfortunately I have 0 coding skills, I was surprised I managed to get HACS setup without issue. The Kumo Station is being picked up by the current integration. It shows as thermostat called “Kumo Station” which physically does nothing. The Kumo app does the same thing except if you click on it in the Kumo app it prompts you to let you know the Kumo Station is running properly. The actual readout for the outdoor temp isn’t shown there, for some reason Mitsubishi has it buried in the installer settings. I didn’t know that people could have Kumo without the station, so makes sense its not in the integration. I may manually shut this function down and use the weather forecast to duplicate the function like gregory suggested.
but if you want to do more work but do this this more cheaply and/or without any dependence on a cloud service at all, you might consider those other options.
