Mitsubishi MELCLOUD integration with Home Assistant

DamijanD · February 8, 2024, 12:10pm

I tried with restart and now it is OK. Weird that only one sensor was missing.

vilppuvuorinen · February 8, 2024, 2:52pm

There seems to be some variance in how different ATW devices report the flow temps. Getting it right across the whole product line would be quite a hassle.

If you really want to dig out this info I’d suggest you look into publishing the raw data (device_conf and state) from MELCloud as extra state attributes here:

github.com

home-assistant/core/blob/69af00b36054032b3ffee063f0ec7f7effd4ab9e/homeassistant/components/melcloud/water_heater.py#L73


      
          
          async def async_turn_on(self, **kwargs: Any) -> None:
              """Turn the entity on."""
              await self._device.set({PROPERTY_POWER: True})
          
          async def async_turn_off(self, **kwargs: Any) -> None:
              """Turn the entity off."""
              await self._device.set({PROPERTY_POWER: False})
          
          @property
          def extra_state_attributes(self) -> dict[str, Any] | None:
              """Return the optional state attributes with device specific additions."""
              data = {ATTR_STATUS: self._device.status}
              return data
          
          @property
          def temperature_unit(self) -> str:
              """Return the unit of measurement used by the platform."""
              return UnitOfTemperature.CELSIUS
          
          @property

The raw data can be found through these properties:

github.com

vilppuvuorinen/pymelcloud/blob/a0f2a66c755b7c3e5835936fac4bb40a44802b7c/pymelcloud/device.py#L43


      
          self.device_id = device_conf.get("DeviceID")
          self.building_id = device_conf.get("BuildingID")
          self.mac = device_conf.get("MacAddress")
          self.serial = device_conf.get("SerialNumber")
          self.access_level = device_conf.get("AccessLevel")
          
          self._use_fahrenheit = False
          if client.account is not None:
              self._use_fahrenheit = client.account.get("UseFahrenheit", False)
          
          self._device_conf = device_conf
          self._state = None
          self._device_units = None
          self._energy_report = None
          self._client = client
          
          self._set_debounce = set_debounce
          self._set_event = asyncio.Event()
          self._write_task: Optional[asyncio.Future[None]] = None
          self._pending_writes: Dict[str, Any] = {}

This should allow you to do some templating to turn that data into sensors on home assistant.

trozman · February 8, 2024, 5:04pm

Thanks for the tip (not mixing REST and integration) and all the work.
My REST sensor is working again (since 8. 2. 2024 0:00). Yesterday I changed REST polling from 1 to 3 mins, not sure if this helped.
But the integration is not working yet (installed update, re-added etc).
I would love to use only one (e. g. your integration) but it does not provide all the data my heatpump sends. For example: compressor frequency, defrost state, last legionella date, …
Are there any plans to add them to the integration? I can provide names of these attributes, if it helps.

vilppuvuorinen · February 9, 2024, 5:15am

Please see the previous message in this thread (Mitsubishi MELCLOUD integration with Home Assistant - #736 by vilppuvuorinen) for a suggestion for a way to accomplish exactly that. I don’t know how easy it is to get merged without heavily curating that list.

It would allow you to use template sensors against the extra state the same way you are using those rest sensors now.

trozman · February 9, 2024, 10:58am

Thanks, I didn’t quite understand at the first glance, but after re-reading I realized you wanted to explain just that.
How would a template sensor for these extra states look like? Are there any examples available?
BTW: Integration works again (I had to delete - re-add it, not only disable).

AWM · February 11, 2024, 10:45pm

Hello Trozman, Vilpu,
I did make something to get the values of my PUD-SWM80YAA Ecodan based on two REST sensors, one to update the API key and one to get the values and extract them to separate template sensors.
I am no programmer, but I use it already some months now.
Communication got worse after new-year, with almost daily hichups, but it keeps working.
Hope this could help you both for the integration of the ASHP series through melcloud.

trozman · February 12, 2024, 7:52am

Thanks for the examples @AWM . I already use something very similar to your example of REST sensor to get data from PUD-SHWM140YAA, I was asking if there is a possibility (and an example) to use only MELCloud integration to get additional sensors.

Chrissi28 · February 12, 2024, 8:24am

Hello everyone,
short info for you.
I have just spoken to Mitsubishi Electri as MelCloud access has stopped working (too much traffic on the account).

Mitsubishi no longer supports third party providers as they send too many requests, so a limiter has been set!

The Melcoud will probably be revised this year, let’s see what comes next.

Protoncek · February 12, 2024, 10:08am

Hm… .that’s interesting… it seems that development goes in the opposite way of logical one… a man would expect that big companies will support integration into smarthome systems to increase sell, but quite opposite is happening: life 360 has ended in february, then Facebox…, now MelCloud doesn’t work…
where are we going?

litio2001 · February 12, 2024, 10:28am

Thanks for the information, for several days HA has not given me any data on the integrated machines and I see that they have just “limited” access to third parties.

stevevg · February 12, 2024, 11:58am

IMHO many companies started offering cloud integrations for free to be more appealing towards customers. Sooner or later, they discovered that the one-shot cost did not pay, as these systems do have a cost for companies, and companies found these not being sustinable in the long term. Moreover, they always look for a profit, better if recurrent.
See the rumors about Alexa, with amazon willing to introduce a subscription/pay-per-use model for advanced features.
Basically, we are going towards a future with companies offering these services with a subscription model, unfortunately for us customers.

trozman · February 12, 2024, 12:41pm

I just had a long talk with local Mitsubishi representative (they called me, because I sent them an email few days ago). A short summary:

he had no idea about the polling limitation and outages
the communication within Mitsubishi El. is bad
they are discussing opening a local API
they’re developing new version of MELCloud app, which will be released soon
general strategy is that they will not limit 3rd party integrations
he will forward my request for detailed allowed polling info and clearer and more transparent communication with customers to higher instances in Japan.

Don’t rely on this, not sure how much of this is actually true.

My suggestion:
Send them emails, wake them up (Contact form for EMEA: Contact Us on the EMEA web site | Contact | MITSUBISHI ELECTRIC EMEA)

maxime1992 · February 13, 2024, 5:03pm

Thanks Trozman for the link, I just took 10mn to write an email and:

share the frustration of the community with the recent changes and the rate limiting
share the fact that since the issue, a lot of people have lost trust in relying on the cloud solution and that they are going to build / use esp32 board to gain local control
beg them to ofer a way to locally control the device using the wifi without having to use an esp32

I hope a lot more people take the time to send similar emails so that hopefully they listen and make good changes!

maxime1992 · February 13, 2024, 5:12pm

On a different note, I just found out this:

Original source here (select country “Ireland” or it doesn’t show up…)

I’m going to try that out.

jorge.lanita · February 13, 2024, 7:08pm

But the date is 2022 !!!

maxime1992 · February 13, 2024, 8:45pm

I was so focused on the text I forgot to check the date… My bad sorry. And like a dumbass I therefore tried it and wondered why it didn’t work

maxime1992 · February 13, 2024, 9:06pm

Would anyone happen to know if it’d be possible to build something like GitHub - rospogrigio/localtuya: local handling for Tuya devices but to communicate locally with our Mitsubishi device using Wifi? I’ve been successfully using localtuya, it’s awesome. I wonder how hard that’d be to replicate for this use case. Prob not easy but does anyone have an idea?

I’m guessing it may be “unpossible” as apparently the wifi device checks for Mitsubishi certificates… So if we try to man in the middle we’ll just get an error with the certificates I guess…

domerich · February 16, 2024, 12:36pm

I had the same issue after upgrading today. I disabled the integration, waited until I could log in from my App again, then enabled the Integration and it worked normally.

Protoncek · February 16, 2024, 1:14pm

Well, all i can say is that i wish i swapped to local (esphome) earlier. Having external temperature sensor is light years better when we’re talking about heating with climate (can’t say about cooling yet…). Temperature is as I set it on my climate and it’s way more stable than with original (built-in) one.

So, hopefully → goodbye melcloud…

AWM · February 17, 2024, 9:06am

Hello David,
sorry for the late response, I am not an active user of thid forum.
I am making a website (in Dutch) to explain how I use the melcloud integration.
It can be found:
https://sites.google.com/myuba.be/homeassistant/home/melcloud

You can use Google Translate (right mouse) it should work and explain itself.
PS: My file is not made to be used as a package, I am not familiar with packaging.
I just found out the code to get it working and hope that the Melcloud integration on HACS could take advantage of that to integrate the extra sensors of a ASHP.

The integrations is like this:
In Configuration. yaml
sensor: !include melcloud.yaml
Your melcloud.yaml has to be changed for login/password/device ID and building ID.
Hope this helps.
Walter