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

[miguelpruivo]

Using NR integration, started experiencing this issue today, been using it for more than a year without issues — created another account but it was immediately locked with the same error after a couple of requests (10 more or less).

This completely breaks functionality and makes my unit "non smart" as I bridge it from NR to HK and I refuse to use their crappy/broken app. I don't even need their cloud, just give ma local API and I'm perfect with it, tbh, I'd even rather. We all would get happy: they save hosting and I keep it local, but oh... they want your data! I forgot about that.

Anyhow, please let me know if someone find a solution. Now I have my unit "lock" binded to a non accessible account and Im getting the too many requests error. They don't even have a ticket/support page for MELCloud ffs.

[nitrosurf]

hi, I just re-enabled the melcloud integration. everything is ok, everything works like before

[tonicb78]

hi, I just re-enabled the melcloud integration. everything is ok, everything works like before

Same here

[ZoomeoTooknor]

hi, I just re-enabled the melcloud integration. everything is ok, everything works like before

I reload integration but always same issue

[paolobosco]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

[tonicb78]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

[paolobosco]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

Disable integration. While disabled, disable polling. Wait some hours, maybe try by your phone: when you are able to access one device, reenable the integration.

or, at least, it worked for me.

[timok77]

I have same problem, i'm using same username for HA integration and phone app, my wife have different account to melcloud and application is still working fine, so for the future - use different usernames for integration. Looks that they just block usernames, not IP addresses.

[samboman]

They don't even have a ticket/support page for MELCloud ffs.

They do have a support/ticket in the (iOS) app.

[wessa66]

Hi all I see the exact same behaviour from the mobile app and HA and I can´t even use their own homepage https://app.melcloud.com/ so I think it´s some problem in their end or if they have limited the allowed call frequency as Adax(heaters) did a few month ago.

Update After I registered a new guest account in Melcloud I can access the devices via https://app.melcloud.com/ now I have added a new integration in HA with new account and disabled the "old" integration, so I can rotate on those accounts let see if I need to more guestaccounts...

[Impedanz]

Remove and reconfig the Integration Not working for me. Interessting is the fact that the Problem Starts for everyone with the Last Update..

Edit: App is working without Problems! I can Control everything.

[GHA2036]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

Disable integration. While disabled, disable polling. Wait some hours, maybe try by your phone: when you are able to access one device, reenable the integration.

or, at least, it worked for me.

Hello, same for me. after waiting the night and desactivating polling before activating integration works for me. As many of us I think HA change something with the new update in the polling method. I have encounter the problem just after core update. 5 minutes before update everything works fine and stop to be available just after update.

[wessa66]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

Disable integration. While disabled, disable polling. Wait some hours, maybe try by your phone: when you are able to access one device, reenable the integration. or, at least, it worked for me.

Hello, same for me. after waiting the night and desactivating polling before activating integration works for me. As many of us I think HA change something with the new update in the polling method. I have encounter the problem just after core update. 5 minutes before update everything works fine and stop to be available just after update.

But isn´t the polling done by the integration it self? as you will get a graph from the temp sensor in the gui.

[paolobosco]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

Disable integration. While disabled, disable polling. Wait some hours, maybe try by your phone: when you are able to access one device, reenable the integration. or, at least, it worked for me.

Hello, same for me. after waiting the night and desactivating polling before activating integration works for me. As many of us I think HA change something with the new update in the polling method. I have encounter the problem just after core update. 5 minutes before update everything works fine and stop to be available just after update.

But isn´t the polling done by the integration it self? as you will get a graph from the temp sensor in the gui.

You can disable polling in the integration options.

as I am getting temperature data from other sensors I am not able to assist on the side of getting temperature. I suspect, at this moment, you shall choose between a working integration (without polling, including temperature) or a blocked (form MEL) integration.

[GHA2036]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

Disable integration. While disabled, disable polling. Wait some hours, maybe try by your phone: when you are able to access one device, reenable the integration. or, at least, it worked for me.

Hello, same for me. after waiting the night and desactivating polling before activating integration works for me. As many of us I think HA change something with the new update in the polling method. I have encounter the problem just after core update. 5 minutes before update everything works fine and stop to be available just after update.

But isn´t the polling done by the integration it self? as you will get a graph from the temp sensor in the gui.

You can disable polling in the integration options.

as I am getting temperature data from other sensors I am not able to assist on the side of getting temperature. I suspect, at this moment, you shall choose between a working integration (without polling, including temperature) or a blocked (form MEL) integration.

same. I use aqara sensor for the temp. I've just check the state of the HVAC temperature sensor and its not working. without polling i'm able to get the energy sensor and hvac control but temperature are not available. so if you have an external sensor you should manage it without problem.

[wessa66]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

Disable integration. While disabled, disable polling. Wait some hours, maybe try by your phone: when you are able to access one device, reenable the integration. or, at least, it worked for me.

Hello, same for me. after waiting the night and desactivating polling before activating integration works for me. As many of us I think HA change something with the new update in the polling method. I have encounter the problem just after core update. 5 minutes before update everything works fine and stop to be available just after update.

But isn´t the polling done by the integration it self? as you will get a graph from the temp sensor in the gui.

You can disable polling in the integration options.

as I am getting temperature data from other sensors I am not able to assist on the side of getting temperature. I suspect, at this moment, you shall choose between a working integration (without polling, including temperature) or a blocked (form MEL) integration.

Thx for that, I wasn´t aware of that setting

[pxFIN]

They don't even have a ticket/support page for MELCloud ffs.

They do have a support/ticket in the (iOS) app.

Android app has as well possibility to send support requests.. but it is unknown if they bother to answer (sent one yesterday so far without a reply)

[wessa66]

Everything back to normal after I disabled the integration for three hours and renabled it while disabling automatic polling. I have independent temperature sensors across the house and I can live without polling data from MELCloud.

I have disabled polling but too late, I have been already blocked again…

Disable integration. While disabled, disable polling. Wait some hours, maybe try by your phone: when you are able to access one device, reenable the integration. or, at least, it worked for me.

Hello, same for me. after waiting the night and desactivating polling before activating integration works for me. As many of us I think HA change something with the new update in the polling method. I have encounter the problem just after core update. 5 minutes before update everything works fine and stop to be available just after update.

But isn´t the polling done by the integration it self? as you will get a graph from the temp sensor in the gui.

You can disable polling in the integration options. as I am getting temperature data from other sensors I am not able to assist on the side of getting temperature. I suspect, at this moment, you shall choose between a working integration (without polling, including temperature) or a blocked (form MEL) integration.

same. I use aqara sensor for the temp. I've just check the state of the HVAC temperature sensor and its not working. without polling i'm able to get the energy sensor and hvac control but temperature are not available. so if you have an external sensor you should manage it without problem.

agree, I need the temp from the devices as I´m using that in my automations

[Razer2015]

Just created a new guest account and sent 100 (or 99) requests to the /EnergyCost/Report endpoint until I got rate limited. After that the /User/ListDevices endpoint still seemed to work so I spammed another 100 or so requests there too until that one got blocked too. Then tested the the same endpoints with my main account and those still worked. So it seems like it's account based rate limit and it's 100 requests in X minutes. Still unsure what the time limit is but judging from the error message in the website, I'm going to guess it's hour or two (will test in an hour to see if I'm still blocked).

Edit: Neither endpoint working after an hour. Will see after 2 hours. Edit2: Seems like I'm still blocked even after 2 hours. They've set really ridiculous limits. Edit3: After 3 hours the /User/ListDevices is again working but weirdly the /EnergyCost/Report is still blocked. Edit4: I spammed around 50 queries to /User/ListDevices and it got blocked again. But it got unblocked after an hour. /EnergyCost/Report is still blocked even after 4 hours. Edit5: /EnergyCost/Report is still blocked even after 5 hours. Edit6: /EnergyCost/Report is still blocked even after 6 hours.

[FIFO0406]

Hello, same here but I’ m still in 11.4 so this problem is not linked to 11.5 upgrade…

[coolkeve]

I just disable for a couple of hours the integration and it's working again... until the next limit reached ?

[Jajjaman]

Same problem here. Probably something at Mitsubishis side as I haven't upgraded HA yet.

[GuidoKiener]

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

Also showing the problem into the MELcloud app

I did not yet the update to 11.5 and I have same problem.

[zaniyah]

¿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

See also https://github.com/geoffdavis/esphome-mitsubishiheatpump and https://github.com/SwiCago/HeatPump which it uses.

I see that a workaround has already been issued as a PR and reviewed, so I expect to see an update to this component with a change to the polling intervals to 5min+, but this is not a permanent fix as Mitsubishi might (probably will) make another breaking change. The only way to avoid this is to use something else.

[petebanham]

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!

Hi, sorry for the stupid question, but how did you disable polling without disabling the whole integration please?

[zaniyah]

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!

Hi, sorry for the stupid question, but how did you disable polling without disabling the whole integration please?

Go to settings -> integrations -> Melcloud. Under Integration Entities, click on the three dots and choose "system options". Uncheck "enable polling for updates".

Then make an automation to automatically poll it yourself, but make sure you keep the frequency low to something like every 10 min+.

[lourou]

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!

Hi, sorry for the stupid question, but how did you disable polling without disabling the whole integration please?

Settings > Devices & Integrations > MELCloud > Click the 3 dots on the right of your account > System Options

[petebanham]

@vilppuvuorinen

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!

Hi, sorry for the stupid question, but how did you disable polling without disabling the whole integration please?

Settings > Devices & Integrations > MELCloud > Click the 3 dots on the right of your account > System Options

Doh! Thanks, I looked there and missed it, and there are only 2 option as well! Thanks

[plouf34]

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!

Hi, sorry for the stupid question, but how did you disable polling without disabling the whole integration please?

Go to settings -> integrations -> Melcloud. Under Integration Entities, click on the three dots and choose "system options". Uncheck "enable polling for updates".

Then make an automation to automatically poll it yourself, but make sure you keep the frequency low to something like every 10 min+.

Thanks; how do you create an automation to poll it every 10 min for example? Could you push the yaml of your automation?

[petebanham]

@vilppuvuorinen sorry to tag you directly but just to let you know that I tried manually appling this fix which I see is targeted for 2024.2, however it didn't work for me. https://github.com/home-assistant/core/pull/109750 I manually updated the 3 lines and added the new one into __init__.py inside the container and restarted HA. Initially the integration would not start as it errored, something about invalid or unknown user_update_interval (sorry it was late last night and i didn't capture the error) so I removed that line and just left the 3 increased values. The integration then started and this morning it was part working in that I had sensors again but not the heating climate entity but when I reloaded the integration just now I hit the throttle limit again.

[Tryum]

I see that a workaround has already been issued as a PR and reviewed, so I expect to see an update to this component with a change to the polling intervals to 5min+, but this is not a permanent fix as Mitsubishi might (probably will) make another breaking change. The only way to avoid this is to use something else.

As a non invasive workaround, I'm wondering how easy it'll be to use esphome with the remote transmitter plugin to replicate remote commands... There are options that are not even available through the melcloud app (night mode, sleep fan speed).

[ep1p]

Interestingly, when I went to use the MELCloud app this morning, I was locked out, but I can still control things from Home Assistant! I'm still using 2024.1.5.

I also note that on iPhone they updated the app 4 days ago so wonder if they have done something general to break that!

[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 Gracias

Consulte también https://github.com/geoffdavis/esphome-mitsubishiheatpump y https://github.com/SwiCago/HeatPump que utiliza.

Veo que ya se emitió y revisó una solución alternativa como PR, por lo que espero ver una actualización de este componente con un cambio en los intervalos de sondeo a 5 minutos o más, pero esta no es una solución permanente como Mitsubishi podría (probablemente lo hará) hacer. Otro cambio radical. La única forma de evitarlo es utilizar otra cosa.

Thanks

[joseprl89]

Just to sum up my understanding in case anyone can correct it:

• 429 errors means MELCloud is rate limiting the number of requests HomeAssistant is performing
• Increasing the poll period would probably mitigate the issue
• This rate limit applies to the MELCloud user, so reaching it in HomeAssistant also locks you on the app/website
• This wasn't happening until very recently, so my guess is that MELCloud introduced this rate limit recently OR for some reason the integration is polling more frequently (I don't see a good reasoning for this currenly).
• Disabling the integration is the prudent approach until a proper solution is put in place, so as to avoid bricking MELCloud's apps/website.

I have reached out to Mitsubishi to see if there's public documentation about the MELCloud API and its rate limits. As I imagine this is a cost saving effort on their part, I also requested whether there's a possibility to connect directly to the devices rather than go through their cloud (they save the server cost, we don't depend on 3rd parties).

Will report back their answer when it comes.

[oakmountainsweden]

where is this __init__.py file ? Can you point out where?

@vilppuvuorinen sorry to tag you directly but just to let you know that I tried manually appling this fix which I see is targeted for 2024.2, however it didn't work for me. #109750 I manually updated the 3 lines and added the new one into __init__.py inside the container and restarted HA. Initially the integration would not start as it errored, something about invalid or unknown user_update_interval (sorry it was late last night and i didn't capture the error) so I removed that line and just left the 3 increased values. The integration then started and this morning it was part working in that I had sensors again but not the heating climate entity but when I reloaded the integration just now I hit the throttle limit again.

[leor7446]

Hi everyone

I'm using Jeedom instaed of HA and the problem is the same so i think that the new behaviour isn't due to HA but due to MelCloud. I called support hotline france 0810407410, he told me that he had not been informed of this change which occurred at midnight and that he had contacted melcloud support but that he had no response currently.

[joseprl89]

Hi everyone

I'm using Jeedom instaed of HA and the problem is the same so i think that the new behaviour isn't due to HA but due to MelCloud.

Looking at the code changed in https://github.com/home-assistant/core/pull/109750, the previous change to the line of code defining the poll interval was 4 years ago, so I'm fairly positive that's the case.

[petebanham]

where is this __init__.py file ? Can you point out where?

@vilppuvuorinen sorry to tag you directly but just to let you know that I tried manually appling this fix which I see is targeted for 2024.2, however it didn't work for me. #109750 I manually updated the 3 lines and added the new one into __init__.py inside the container and restarted HA. Initially the integration would not start as it errored, something about invalid or unknown user_update_interval (sorry it was late last night and i didn't capture the error) so I removed that line and just left the 3 increased values. The integration then started and this morning it was part working in that I had sensors again but not the heating climate entity but when I reloaded the integration just now I hit the throttle limit again.

It in the directory that the integration is installed in and that will depend on your installation type. On my docker system it is in /usr/src/homeassistant/homeassistant/components/melcloud (within the container and not on the host)

[paolobosco]

Just to sum up my understanding in case anyone can correct it:

• 429 errors means MELCloud is rate limiting the number of requests HomeAssistant is performing
• Increasing the poll period would probably mitigate the issue
• This rate limit applies to the MELCloud user, so reaching it in HomeAssistant also locks you on the app/website
• This wasn't happening until very recently, so my guess is that MELCloud introduced this rate limit recently OR for some reason the integration is polling more frequently (I don't see a good reasoning for this currenly).
• Disabling the integration is the prudent approach until a proper solution is put in place, so as to avoid bricking MELCloud's apps/website.

I have reached out to Mitsubishi to see if there's public documentation about the MELCloud API and its rate limits. As I imagine this is a cost saving effort on their part, I also requested whether there's a possibility to connect directly to the devices rather than go through their cloud (they save the server cost, we don't depend on 3rd parties).

Will report back their answer when it comes.

Thank you for asking to MEL. I hope for a positive answer. However, please note that in the Agreement we all accepted to use MELCloud it is forbidden to use third party application (unless authorized). In my Terms&Conditions (italian) it is stated at 3.7.

[wessa66]

Just to sum up my understanding in case anyone can correct it:

• 429 errors means MELCloud is rate limiting the number of requests HomeAssistant is performing
• Increasing the poll period would probably mitigate the issue
• This rate limit applies to the MELCloud user, so reaching it in HomeAssistant also locks you on the app/website
• This wasn't happening until very recently, so my guess is that MELCloud introduced this rate limit recently OR for some reason the integration is polling more frequently (I don't see a good reasoning for this currenly).
• Disabling the integration is the prudent approach until a proper solution is put in place, so as to avoid bricking MELCloud's apps/website.

I have reached out to Mitsubishi to see if there's public documentation about the MELCloud API and its rate limits. As I imagine this is a cost saving effort on their part, I also requested whether there's a possibility to connect directly to the devices rather than go through their cloud (they save the server cost, we don't depend on 3rd parties). Will report back their answer when it comes.

Thank you for asking to MEL. I hope for a positive answer. However, please note that in the Agreement we all accepted to use MELCloud it is forbidden to use third party application (unless authorized). In my Terms&Conditions (italian) it is stated at 3.7.

We have recently seen the exact same behaviour on the HA integration against Adax wall heaters, and the developer of that int... was forced to decrease the poll rate.

[durix75]

I called my local mitshubisi hotline. it seems they are aware of the issue and said a fix will be delivered in the coming hours / days Let follow up

[paolobosco]

Just to sum up my understanding in case anyone can correct it:

• 429 errors means MELCloud is rate limiting the number of requests HomeAssistant is performing
• Increasing the poll period would probably mitigate the issue
• This rate limit applies to the MELCloud user, so reaching it in HomeAssistant also locks you on the app/website
• This wasn't happening until very recently, so my guess is that MELCloud introduced this rate limit recently OR for some reason the integration is polling more frequently (I don't see a good reasoning for this currenly).
• Disabling the integration is the prudent approach until a proper solution is put in place, so as to avoid bricking MELCloud's apps/website.

I have reached out to Mitsubishi to see if there's public documentation about the MELCloud API and its rate limits. As I imagine this is a cost saving effort on their part, I also requested whether there's a possibility to connect directly to the devices rather than go through their cloud (they save the server cost, we don't depend on 3rd parties). Will report back their answer when it comes.

Thank you for asking to MEL. I hope for a positive answer. However, please note that in the Agreement we all accepted to use MELCloud it is forbidden to use third party application (unless authorized). In my Terms&Conditions (italian) it is stated at 3.7.

We have recently seen the exact same behaviour on the HA integration against Adax wall heaters, and the developer of that int... was forced to decrease the poll rate.

Yep! also Haier: https://github.com/Andre0512/hon/blob/a9e2cd0c059f7423a766f0ee0e8fb1c32ce96af1/takedown_timeline.md#L1

[joggs]

as a quick fix we could lower the poll rate, so it looks more decent in Mitsubishish logs if they start looking into it

[guihom83]

I just called Mitsubishi technical support, it seems that there is a technical problem. They took my MELCloud login for investigation.

By the way, I managed to lock my account just by playing with the application, the integration is disabled.

[scroll]

I just called Mitsubishi technical support, it seems that there is a technical problem. They took my MELCloud login for investigation.

By the way, I managed to lock my account just by playing with the application, the integration is disabled.

How one calls Mitsubishi support :) I can't even find an official email or support page.

[dasom78]

Hello, contacted support by email this morning. they answered 2h later to tell me they are currently facing technical issues on the MELCLOUD and are working on a solution.

No estimates on when it will get back to normal, but at least the guy did not answer we were no longer allowed to pool their data !

[Zefke]

Switched off the HA integration for a couple of hours, turned it ON again, new logon and it seems to be working for now. The crappy app also needed a new logon... Hope that someone writes some kind of local HA integration (I really hate the Melcloud, as its interface is a POS and it has been letting me down before..)

[miguelpruivo]

Today it's back working again — changed my polling from 30 seconds to 1 minute, but it would be good to know how much polling one should be using and their limitations to prevent being blocked.

[mafonso]

it seems they are aware of the issue and said a fix will be delivered in the coming hours / days

I don't believe they will fix it. This change was not a the result of a wider change that affected this service. It was implemented by user login, so that each user has a quota. This had to be implemented in the service itself, so it was deliberate. There is nothing to "fix" but company policies.

Unfortunately Mitsubishi has a crappy web app, that they shoved into a web view on their mobile apps. Little or none investment in having a native app. And then they shaft the users that use the API to have a better experience and make a better use of their devices. One of the reasons I choose Mitsubishi was because I had the possibility of using such API. The least they could do it to provide an end-user API if they don't want to bother with a better app.

[lourou]

I've received a response from MELcloud Support over email:

On Tue, Feb 6, 2024, at 11:21, Alexy M. wrote:

Hello, We are experiencing a malfunction on the Melcloud application. Our teams are working to solve the problem Regards, Alexy M. After sales support technician