Readded today again and now it seems completely broken? My flow and return temp are basically stuck on 21 degrees which is not true. However tank temperature, outdoor temp and indoor temp looks corerct and gets updated.
Anyone discovered the max polling rate of the API? I tried 3 minutes but after couple of hours I guess my key hits a rate limit because I stopped getting values from the official Melcloud integration. Lowering the polling rate to 10 minutes seem to work. Anyone seen what the limit is? 
Hi guys, for our Airbnbs we have the āDiamondā ACs installed with the i-see Sensor. Now I hoped to get the occupancy to see which room is currenly occupied. If there is nobody the temperature could be lowered in winter or higher in summer.
Is there any way to get this out of the API?
Hi,
I did the integration with melcloud and from time to time this message appears:
023-09-10 00:05:17.211 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.ac_sala_room_temperature is taking over 10 seconds
I have 2 air conditioners and the message for both appears.
They are 2 meters from the WiFi router and I have no network problems at home.
Is there any parameter that I can change to make these messages disappear?
Thanks
Is there any parameter that I can change to make these messages disappear?
If the Wi-Fi interfaces on your units are like mine, thereās nothing you can do about occasional drop outs. For all that itās cheap and easy to create all kinds of reliable, Wi-Fi connected devices with $10 worth of ESP32 hardware and free software, the network stack on Mitsubishiās Wi-Fi interfaces is reported to be terrible.
My own experience aligns with that. All six of my units drop off from time to time. Never all at once, and my Wi-Fi network is otherwise solid. Itās just the Mitsubishi interfaces, doing their unreliable thing. (They really should be ashamed of themselves for selling the Wi-Fi interfaces for hundreds of dollars. A teenager with $20 and a soldering iron could do better.)
Yeah I bought the official one used for 300.USD. It looks cheap as hell. However it does work. But when you consider that you can buy a smartphone for 100 usd which has wifi and a hell of a lot mode. The price is just insane.
When my pump finally dies I will for sure make sure to sell all the parts that I canā¦
Will buy Nibe next time, I have been very disappointed with Mitsubishi. Low COP, very loud outdoor unit, no price adaption etc.
Hello Dave,
I think I have found a working principle.
It is documentend in my melcloud.yaml example.
melcloud.yaml
I hope this works for you.
Walter
Hi all, I am a HA beginner.
I donāt get how to create automations using the melcloud integration and my Air pumps.
Everything works through the dashboard and the default card, for example change fanspeed etcā¦
But creating an automation only allows to change HVAC mode as standard, not change fanspeed or anything else.
I have read through last 100 or so post here and I find only one person asking the same question, but his screenshot doesnt work for me. Please advise:
Nothing happens on this event. How can I do this?
Also please if anyone knows how to ignite the āisaveā function on my air pump (Mitsubishi Hero 2 LN35) , to easily toggle the saved preset mode and back, I would be very thankful.
Best,
Hi Walter, thanks for this - itās taken me a while to find time to try it. I tried pasting it into my packages directory but Iām getting errors like Invalid config for 'homeassistant' at packages/melrest.yaml, line 7: expected a dictionary for dictionary value 'packages->melrest', or pasting it into configuration.yaml I get end of the stream or a document separator is expected
How did you use it?
Iām using this command to and it worked for a while. But it just stoppped working and the rest is giving this fault message. Anybody a idea how to fix this issue?
Logger: homeassistant.components.rest.util
Source: components/rest/util.py:37
Integration: RESTful (documentation, issues)
First occurred: 8 januari 2024 om 23:54:43 (33618 occurrences)
Last logged: 23:26:29
REST result could not be parsed as JSON
This morning I installed updates for Home assistant Core (and another update which I donāt know the name of). After that my melcloud integration (the extra sensors besides the standard melcloud) doesnāt work anymore. It says āentity sensor.ecodan_cmdā not available.
Anyone having the same problem?
after the latest HA update, my Melcloud integration fails again and while re-adding the integration was successful, nothing works. The error is now :
File ā/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.pyā, line 1060, in raise_for_status
raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 429, message=āThis request has been throttled due to an excessive amount of traffic to our service.ā, url=URL(āhttps://app.melcloud.com/Mitsubishi.Wifi.Client/EnergyCost/Reportā)
Same issue here after the update.
Still not working 
Yeah, it died here, too. āDelete and re-addā integration didnāt help right away, but after an hour, two began to work again, so now it works.
But this was final āover the edgeā trigger for me. Iām already making esphome modules for my climates and Iām gonna change them all in near future. No more Melcloud for me.
I got this throttled error too. Time to have a look at the ESP I think. The same happened to Telldus 
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/components/melcloud/sensor.py", line 192, in async_update
File "/srv/homeassistant/lib/python3.11/site-packages/homeassistant/components/melcloud/__init__.py", line 99, in async_update
File "/srv/homeassistant/lib/python3.11/site-packages/pymelcloud/device.py", line 85, in update
File "/srv/homeassistant/lib/python3.11/site-packages/pymelcloud/client.py", line 182, in fetch_device_state
aiohttp.client_exceptions.ClientResponseError: 429, message='This request has been throttled due to an excessive amount of traffic to our service.', url=URL('https://app.melcloud.com/Mitsubishi.Wifi.Client/Device/Get?id=
It looks like the throttling is user-based. My Melcloud Android App also says āWe have detected excessive traffic from your account, your access to the service has been limited for a few hoursā. I havenāt even used the app, and HA has adjusted the temp max once an hour. Thereās something weird here, maybe thereās a tight loop checking the cloud service for sensor values or the state too often?
Same problem here. If you could provide some links/resources to migrate to esp, thatād be great.
2 Likes
Exactly this link, yes, thanks. I should add, though that perhaps a level converter is a good idea to insert between ESP and climate, since climate works with 5V while ESP has only 3.3V, so it can happen that communication will be poor (or even none). It could be perfect, thoughā¦ so, a bit of testing is needed, i guess.