Finished fetching melcloud_custom (success: False)

[jburdy]

Hello,
All my entities have been "unavailable" for a few hours. However, I can still control them from the iPhone app and the MELCloud website. I've activated the debug logs from the integration settings but that's all I get.

...
hass  | 2024-02-05 16:53:19.327 DEBUG (MainThread) [custom_components.melcloud_custom] Finished fetching melcloud_custom-Entree data in 0.235 seconds (success: False)
hass  | 2024-02-05 16:53:19.472 DEBUG (MainThread) [custom_components.melcloud_custom] Finished fetching melcloud_custom-Haut  data in 0.195 seconds (success: False)
hass  | 2024-02-05 16:53:19.496 DEBUG (MainThread) [custom_components.melcloud_custom] Finished fetching melcloud_custom-Carnotzet  data in 0.268 seconds (success: False)
...

How can I investigate further?
Many thanks in advance,

[mupfpilou]

Same issue here :(

[mupfpilou]

Looks like Mitsubishi might have put a rate limit...

Error requesting melcloud_custom-x data: 429, message='This request has been throttled due to an excessive amount of traffic to our service.',

[ollo69]

We have to wait a couple of days. Could be just related to server maintenance.

[mupfpilou]

Working via app though
Hope it is only a temporary measure from Mitsu

[jburdy]

It's annoying that we have to go through their cloud. The devices respond in http (but require login/pass) isn't there a local API that can be used?

[ollo69]

There is a project based on tasmota that require to connect an ESP Module replacing the Mitsubishi WiFi module.
I started to implement this some times ago, but than I abandoned. If API cloud will become unusable I will come back to that solution.

https://isaiahchia.com/2022/06/16/integrating-mitsubishi-air-con-hvac-with-home-assistant-via-nodemcutasmota/

[mupfpilou]

Nothing found to discuss directly with the original wifi module ?
It would be great to not replace all these expensive wifi modules :(

[ollo69]

No as I know. I suppose that wifi module use proprietary language protocol to exchange data with Melcloud services.

[limkinZero]

You should use Ecodan local with a esp32 card. You will forget Melcloud forever. https://github.com/rbroker/ecodan-ha-local El lun, 5 feb 2024, 19:14, Julien Burdy ***@***.***> escribió:

…

It's annoying that we have to go through their cloud. The devices respond in http (but require login/pass) isn't there a local API that can be used? — Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADLQJD4AR5IDXJQISIV2GI3YSEOO7AVCNFSM6AAAAABC2MNF42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRXGY4DIOJSGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ollo69]

Just following native integration suggestion, I drastically reduce the polling frequency to once in 15 minutes in last release, hoping that it's enough.
Honestly I think that this change will make this integration quite unusable and so I will probably move shortly to replace WiFi module with an ESP module. I don't think I'll miss Melcloud feature....

[mupfpilou]

Thx for the quick update
I agree its not ideal but it is still worth something for people that invested in these wifi modules and not familiar with ESP stuff !
Personally, I have 5 units, and DIY ESPHome x5 cost some bucks, plus DIY work with cables / firmware / whatever ;)

[mupfpilou]

By the way, just tested 0.3.2, still unavailable sensors and theses logs on my 5 units

Error requesting melcloud_custom-xxx data: 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')
Error requesting melcloud_custom-xxx data: 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')
Error requesting melcloud_custom-xxx data: 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')
Error requesting melcloud_custom-xxx data: 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')
Error requesting melcloud_custom-xxx data: 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')

My account is no more unavailable via the app, but sensors are still not there
Could it be related to this specific URL "/EnergyCost/Report" ?

I will try again tomorrow morning and will keep you informed

[ollo69]

I suppose that we need to wait some times so that rate limit is removed, let's see what happen in next hours

[jburdy]

There's an http server in the wifi modules (mine's a MAC-577IF2-E). Can't we use it to control them locally? There really is something behind it, but I don't have the credentials.

Try this on one of your devices: http://192.168.1.189/apinfo

I'd rather hack the current modules than do DIY and throw them in the garbage can.

[Grabauskas]

Could it be that they've recently implemented rate limiting? I'm experiencing a similar issue in the app with additional details.