MELCloud - Error - "This request has been throttled due to an excessive amount of traffic to our service"

[samboman]

The problem

UPDATE / EDIT: It is not related to the HA upgrade. It is related to some change MELCloud have done on their servers.

2024-02-05 17:04:27.418 ERROR (MainThread) [homeassistant.components.climate] melcloud: Error on device update! Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 573, in _async_add_entity await entity.async_device_update(warning=False) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1216, in async_device_update await self.async_update() File "/usr/src/homeassistant/homeassistant/components/melcloud/climate.py", line 125, in async_update await self.api.async_update() File "/usr/src/homeassistant/homeassistant/components/melcloud/init.py", line 107, in async_update await self.device.update() File "/usr/local/lib/python3.11/site-packages/pymelcloud/device.py", line 86, in update self._energy_report = await self._client.fetch_energy_report(self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/pymelcloud/client.py", line 195, in fetch_energy_report async with self._session.post( File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 1194, in aenter self._resp = await self._coro ^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 693, in _request resp.raise_for_status() 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')

What version of Home Assistant Core has the issue?

core-2024.1.6

What was the last working version of Home Assistant Core?

core-2024.1.5

What type of installation are you running?

Home Assistant Container

Integration causing the issue

MELCloud

Link to integration documentation on our website

https://www.home-assistant.io/integrations/melcloud

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @vilppuvuorinen, mind taking a look at this issue as it has been labeled with an integration (melcloud) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of melcloud can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign melcloud Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

melcloud documentation melcloud source _{^{(message by IssueLinks)}}

[tonicb78]

Same issue here after updating HA. Climate entity is not created.

[Impedanz]

Thank you for opening that issue! Same Error here after Update :*(

[olealm]

Same issue here after updating Home Assistant OS to 11.5. Climate entity unavailable. Tried deleting and re-adding my heatpump, but climate entity was not created.

[helio58]

Same problem no climate entity. Climate entity unavailable . Core 2024.1.6

[98ultimate]

Melcloud app on android gives this warning message. Can not access heat pump now.

[Nisssen]

Same issue here after updating Home Assistant OS to 11.5. Climate entity unavailable.

[machadolucas]

Same issue here after updating Home Assistant OS to 11.5

[Dirkhaan]

Same here, also after updating the HAOS to 11.5

[Lantoit]

Same issue, I've downgraded Ha to previous version without success.

[Osconse]

Same problem. I have even restored a Home Assistant backup and it still doesn't work

[vilppuvuorinen]

Well we had a good run with this thing.

I'm guessing the only option is would be to drastically reduce the polling frequency to once in 10-20 minutes and hope the load will be acceptable. Let's see how it goes.

The best workaround is to replace the wifi module with a ESP and cut out the cloud component entirely.

[Beamer28582]

Same her. In spite of Backup it doesn‘t work.

[98ultimate]

The best workaround is to replace the wifi module with a ESP and cut out the cloud component entirely.

Lets hope 500€ wifi module is not useless forever. Waiting useful solution from Mitsubishi if wifi module becomes useless.

[EGDimitrov]

I have the same problem after update. Terrible... Give us a solution please...The problem is with the home assistant, because the Melcloud application on my phone works without any problems.

[tonicb78]

Well we had a good run with this thing.

I'm guessing the only option is would be to drastically reduce the polling frequency to once in 10-20 minutes and hope the load will be acceptable. Let's see how it goes.

The best workaround is to replace the wifi module with a ESP and cut out the cloud component entirely.

I was thinking some months ago to build the esp32 module, we should avoid any types of cloud integrations.

[Flowlance]

Same issue in home assistant on docker. MelCloud app works fine

[Osconse]

Hace algunos meses estuve pensando que al construir el módulo esp32, deberíamos evitar cualquier tipo de integraciones en la nube.

Where can I find information about replacing the wifi module with an esp32?

[tonicb78]

Where can I find information about replacing the wifi module with an esp32?

Check this:

https://community.home-assistant.io/t/mitsubishi-ac-with-wemos-d1-mini-pro/107007/286

[EGDimitrov]

A little while ago I got supervisor 2024.01.1 upgrade. After the upgrade everything work again!!!! Yeeeeeeeeeeeeee

[Osconse]

¿Dónde puedo encontrar información sobre cómo reemplazar el módulo wifi con un esp32?

Mira esto:

https://community.home-assistant.io/t/mitsubishi-ac-with-wemos-d1-mini-pro/107007/286 Thanks

[Osconse]

Hace un tiempo obtuve la actualización supervisor 2024.01.1. Después de la actualización, ¡todo vuelve a funcionar! Yeeeeeeeeeeeee

I just updated to 2024.01.1 and it does NOT work for me...😭😭

[Dirkhaan]

Did you do a complete reboot, because it worked for me after a complete reboot!

[simonk0606]

Same problem! I've rebooted all, nothing better for now ! But I'm not sur I had the correction 2024-01-1. Where can I check it ?

[Osconse]

¿Hiciste un reinicio completo porque funcionó para mí después de un reinicio completo?

I have turned off the host completely and restarted Home Assistant again but it still doesn't work. It gives me this error: Error: 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')

[Impedanz]

Complete reboot(unplug Power), no newer Updates available, melcloud Not working after 11.5 Update

[Lantoit]

Did you do a complete reboot, because it worked for me after a complete reboot!

Upgraded, complete reboot, still not functioning...

[GHA2036]

Same for me. I've tried to restore from a backup created just before update without succes. Complete reboot and reload of the integration doesn't solved the problem.

[tonicb78]

Same for me. I've tried to restore from a backup created just before update without succes. Complete reboot and reload of the integration doesn't solved the problem.

It is blocked from their site, they are blocking the users or IPs and only allow to use their sh*tty app. Seems they are doing a Haier.

[samboman]

Error report it in the MELCloud app. 😀 If you can, it is so bad. 🫣