@sinemaker I went through something similar, where we added five new units to an existing, working-with-Kumo-and-HA system. For some reason, the new units had incorrect IP addresses after adding them to the integration.
Unfortunately, I don’t remember the full details, and I rebuilt my home network around the same time, changing IP address ranges and VLANs. So it’s possible that some of the issues I experienced weren’t Kumo or the Wi-Fi interfaces at all.
What I do remember is that I had to hand-edit the Kumo Cloud integration cache file, kumo_cache.json, and change the IP addresses for the units’ interfaces. The original, working unit had the correct address, but the other units had addresses from a different private network range (presumably from some default or temporary condition during setup).
Once I did that, and set the Kumo integration to prefer the cache file and rebooted HA, it all started working fine. (Or so I think I seem to maybe recall.)
The IP addresses can be hard to find in the long JSON file, but they’re under the key “address:”, and that’s the only key used for that purpose. (I think.) So, just do a quick search of the cache file for that key, and see if the addresses match what you expect. (And set the integration to prefer the cache file, and reboot.)
Thanks for the observations. My problem was actually a self-inflicted wound. I got my ip addresses backwards for my two new heat pumps. Once I fixed that everything worked perfectly.
I did a search but I could not find the answer. I have a cottage and I would like to be able to use my the home assistant at my house to pull up the info and control there Mitsubishi unit at the cottage. Can I do this or will it try and use a local IP address to always control it once configured, or will it always use the cloud to connect and control it remotely.
Got an email the other day that Kumo Cloud would be retired in favor of Comfort App by Mitsubishi. Anyone have an idea of this is going to just be a coat of paint or if there will be major changes on the back end?
At the very least I fear it’s likely to change the process of initial setup. Whether it totally disables the local-network API or not is anyone’s guess.
They’d pretty much need to update the firmware on the hardware interfaces for that to happen, right?
I take it as a generally positive sign that they’re releasing a new app; the Kumo Cloud app is pretty awful. (Which is why I never use it.)
I guess we’ll have to see if the new app includes updates to the firmware, and requires it to be installed to work. I don’t imagine the new app would install new firmware without notifying the user not to turn things off, etc., while the update takes place. So it’s not going to be a surprise.
Whether it’s good or bad news, I guess we wait and see.
(I am not going to be the first to install it, I can tell you that for certain!)
I’m about to spend a truckload of money on a Mitsubishi heatpump, that apparently comes with this Kumo thing. Anything I should know going into this? Two zones, both remotes are wireless and the only way to control the thing. It’s likely that will be fine for my partner, but I’d like to get it dialed in with homeassistant so I can see more graphs and any other data it has to share.
Be advised, as a new customer you are highly unlikely to be able to use the HA Kumo integration as things stand today.
TL;DR: Mitsubishi reworked their app and underlying cloud service and we can no longer get (or haven’t yet found) the info we need to talk to the units locally.
Honestly, I kinda regret my purchase. The hardware is incredible and I love the smooth, whisper quiet operation. But their software integration is lacking.
While my setup hadn’t yet stopped working, I felt it was only a matter of time and I’ve long been frustrated by the instability of the Kumo WiFi adapters. I recently took the leap to the ESPHome solution and am quite thrilled with it. The functionality and stability are what you’d expect.
I want to say a special thank you to @parkercat for your effort over the last several years making this custom component what it was. It provided the functionality we all needed and it’s unfortunate Mitsubishi has made keeping it up so challenging.
To be honest I’ll probably do the same if my indoor units stop working. We’re not quite giving up yet though – see the hass-kumo repo README for an update on the current situation.
I don’t use Home Assistant, but it looks pretty straight forward to create a plugin (custom component) so I am happy to create one if it would be helpful.
Hey all, major news: Thanks to ekiczek we have a new version of hass-kumo that should allow setting up new units using the Kumo v3 (“Climate”) APIs. Once the units are set up, it’s the same old local control that works well for so many people. This version is released as a beta (v0.4.0-beta) for now. If the Climate transition kept you from using hass-kumo, please give it a try and report success here, or raise any issues over on GitHub.
