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

samboman commented 5 months ago

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] commented 5 months ago

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 commented 5 months ago

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

Impedanz commented 5 months ago

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

olealm commented 5 months ago

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 commented 5 months ago

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

98ultimate commented 5 months ago

Screenshot_20240205-182334~2.png

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

Nisssen commented 5 months ago

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

machadolucas commented 5 months ago

Same issue here after updating Home Assistant OS to 11.5

Dirkhaan commented 5 months ago

Same here, also after updating the HAOS to 11.5

Lantoit commented 5 months ago

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

Osconse commented 5 months ago

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

vilppuvuorinen commented 5 months ago

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 commented 5 months ago

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

98ultimate commented 5 months ago

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 commented 5 months ago

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 commented 5 months ago

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 commented 5 months ago

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

Osconse commented 5 months ago

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 commented 5 months ago

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 commented 5 months ago

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

Osconse commented 5 months ago

¿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 commented 5 months ago

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 commented 5 months ago

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

simonk0606 commented 5 months ago

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 commented 5 months ago

¿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 commented 5 months ago

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

Lantoit commented 5 months ago

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

Upgraded, complete reboot, still not functioning...

GHA2036 commented 5 months ago

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 commented 5 months ago

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 commented 5 months ago

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

Lantoit commented 5 months ago

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.

In my opinion is something different. From MelCloud I can retrieve some data, but not all information needed to manage the climate.

JohnS111 commented 5 months ago

Same problem for me after upgrade to 11.5 and supervisor 2024.1.6. Sadly, the system failed to backup the old version before updating. The "Home Assistant Google Drive Backup" add-on showed errors in the log to say it could not backup the system and yet it did not abort the update. HA details are: Core 2024.1.6 Supervisor 2024.01.1 Operating System 11.5 Frontend 20240104.0 MEL Cloud message says: We have detected excessive traffic from your account, your access to the service has been limited for a few hours.

tonicb78 commented 5 months ago

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.

In my opinion is something different. From MelCloud I can retrieve some data, but not all information needed to manage the climate.

I am also blocked from the app… with same message.

GHA2036 commented 5 months ago

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.

In my opinion is something different. From MelCloud I can retrieve some data, but not all information needed to manage the climate.

I am also blocked from the app… with same message.

Yes same message from the app. I suppose that HA push to many request to melcloud and lock the account

petebanham commented 5 months ago

This is not caused by a HA change. The same thing happened to me today after no change and working fine on 2024.1.6 The MEL cloud app worked at first so I though it was just HA but that then stopped too with "too many requests" error other have above. Cleary Mitsubishi have changed something their end :-(

iamtheeric commented 5 months ago

I can login on the MELCLOUD Website BUT as soon I try to select one climate device the site kicks me out with this message:

In summary: you can login trough web or app but as soon you try to control something it‘s over.

for the moment I deactivated the integration to cut traffic.

Hopefully this is just a temp. error otherwise I have climate devices for 12k€ without integration in my smart home. And I HATE the app. I didn’t even use the devices during the last weeks.

is anyone out there still able to control devices trough app or web?

HQOFIQ commented 5 months ago

Same here - as already stated above I can confirm that after the update of Home Assistant OS to 11.5 but unfortunately even after updating the Supervisor 2024.01.01 MELCloud is blocking me out because of excessive traffic ...

Cartman25 commented 5 months ago

Same problem after today update ! Core : 2024.1.6 Supervisor : 2024.01.1 Operating System : 11.5

iamtheeric commented 5 months ago

Let‘s see if it works again tomorrow if the integration is deactivated. If yes there must have been some change in the recent update which causes too much traffic to the MEL Servers.

orkunkoti commented 5 months ago

I haven't updated my HA and I don't use my heat pumps through HA, but I have automation installed. I tried to put scheduled event to next day using Android MELCloud, but account stopped working. So it looks that they have blocked all accounts, that have HA clients.

josefe17 commented 5 months ago

Definitely Mitsubishi has changed something on their part. I'm running Openhab instead and I get no control and the same error when I try to access via web. I haven't updated and changed anything on a while. If they limit access to external integrations to a point where it is not feasible to use it, this would be my way to go and send them away: https://github.com/SwiCago/HeatPump

calielc commented 5 months ago

Same problem here, it started just after upgrade OS to 11.5.

Also showing the problem into the MELcloud app

Emmpunkt commented 5 months ago

Same here after upgrade.

iamtheeric commented 5 months ago

Just for fun… try to use the group control:

This is still working with all possible control options (Web version and App).. they just blocked the option to control single devices or retreive single device info (except energy consumption).

I really hope that Mitsubishi isn‘t doing this on purpose. Excuse my crappy english, please.

Mascot68 commented 5 months ago

Let‘s see if it works again tomorrow if the integration is deactivated. If yes there must have been some change in the recent update which causes too much traffic to the MEL Servers.

That's my assumption. I was locked out of my melcloud account for a while earlier, with a "too many requests" error. I disabled the HA integration and waited a while, and I can use the app and webpage again.

elianbgr commented 5 months ago

There is light at the tunnel. The message is now different and hints at a problem in the MelCloud. Screenshot 2024-02-06 011329

iamtheeric commented 5 months ago

There is light at the tunnel. The message indicates a problem in MelCloud.

This is the message from the app. The too high traffic message is from the web page.

I‘m now able to control single devices in the app again since five minutes but homeassistant integration is still not working (after a full reboot btw)

Update: aaaand locked out again. I guess something has changed in the api which causes HA to generate too much requests and then it‘s being locked out.

Update 2: If you remove the integration and redo the setup you the account/devices are still being locked and the climate entities are not even being created. I give up for today. This is a dev task on ha or Mitsubishi end…

lourou commented 5 months ago

Same issue here. I've disabled "polling for updates" for now in HA, so that it stops requesting MELCloud and locking me out. I've also contacted support and asked for higher rate limiting. Let's see if this is a MELCloud temporary issue, and I hope it is!

lourou commented 5 months ago

This is a HTTP 429 error: Too Many Requests. On this endpoint only: https://app.melcloud.com/Mitsubishi.Wifi.Client/Device/Get?id=...&buildingID=...

guihom83 commented 5 months ago

Same here. Melcloud Say that m'y account IS locked by the way i Can still control Mitsubishi device with Alexa ... Maybe alexa communicate localy? If yes could be a nice enhencement

home-assistant / core