Open jtfidje opened 6 months ago
Here is a log line with the issue represented:
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:599
Integration: Sensor (documentation, issues)
First occurred: 10:12:57 (2 occurrences)
Last logged: 10:12:57
melcloud: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 599, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1259, in async_device_update
await self.async_update()
File "/usr/src/homeassistant/homeassistant/components/melcloud/sensor.py", line 172, in async_update
await self._api.async_update()
File "/usr/src/homeassistant/homeassistant/components/melcloud/__init__.py", line 71, in async_update
await self.device.update()
File "/usr/local/lib/python3.12/site-packages/pymelcloud/device.py", line 85, in update
self._state = await self._client.fetch_device_state(self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/pymelcloud/client.py", line 182, in fetch_device_state
async with self._session.get(
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 1194, in __aenter__
self._resp = await self._coro
^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 693, in _request
resp.raise_for_status()
File "/usr/local/lib/python3.12/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/Device/Get?id=XXXXXX&buildingID=YYYYY')
Actual values in log replaced with dummy values... They were just integers.
Via my support kinnan.dk I have been told they introduced rate limitations Feb 5 2024 our of the blue. I have complained as I think that is unacceptable without any warning and time to get things adjusted.
Same here, no more home heating. Is there any change this plugin can be updated?
Had no problem until I two days ago upgraded to 2024.2.1, from 2024.1.6. Then I lost all melcloud climate.* entities. Restored my partial backup to 2024.1.6 same day, entities and functionality came back. Still working today. So obviously not only a melcloud issue. There must be something changed in 2024.2.1 that creates problems with the melcloud integration.
I contacted Mitsubishi support and they answered that they have set a rule for how many questions can go thru from a third party software (homeasisstant for example), asked now how the rule is set requests/time.. Answer i got in Swedish: Mitsubishi Electric har infört en trafikbegränsning för att få ner en allt ökande extern trafik till Melcoud systemet. Denna trafik kommer från externa tredje parts appar som automatiskt loggar in och frågar om temperaturer och driftläge, ofta flera gånger per minut. Det som händer är, att om någon användare försöker logga in onormalt många gånger per timme, kommer systemet att blockera inloggning i ett par timmar. Sedan går det att logga in igen men om samma inloggningsmönster händer igen kommer kontot att blockeras igen. För att återställa tillgängligheten till det normala måste antalet frågor/inloggningar som görs minskas. Då kommer användaren tillåtas ansluta igen när den aktuella blockeringstiden går ut.
I use 2024.1.6 and got same problem. I'm afraid to think about DIY controller for Mitsu :(
Update on my end, i missed the previous fix for HA. See: https://github.com/home-assistant/core/issues/109728 My MELCOUD was banned also, Disabled the plugin, updated to the 2024.2.1 release. And waited 2 hours for the ban to lift. Its been working fine ever since, i did not lose any settings /devices on the upgrade.
> Its been working fine ever since It works fine till the next restart HA
> Its been working fine ever since It works fine till the next restart HA
Unable to reproduce, after HA restart its still fine. Did you upgrade to 2024.2.1? You say you are still on 2024.1.6 And yes that version has the issue. (because MELCOUD changed their hammer limits)
Unable to reproduce, after HA restart its still fine. Did you upgrade to 2024.2.1? You say you are still on 2024.1.6 And yes that version has the issue. (because MELCOUD changed their hammer limits)
I was still on 2024.1.6 and didn't have this issue. Updated directly to 2024.2.1 an hour ago and my climate control stopped working
Update: Reverted back to OS 11.4 and Core 2024.1.6. Climate control is working again
I was still on 2024.1.6 and didn't have this issue. Updated directly to 2024.2.1 an hour ago and my climate control stopped working
Update: Reverted back to OS 11.4 and Core 2024.1.6. Climate control is working again
It can stop work after couple of restarts HA. I make new entity and restarted HA 2024.1.6 2 times. MELCloud stoped work.
Workaround: Use a 2'nd and a 3'rd or 4'th account installed via Melcloud-App. So you're able to connect over the App to you Machine.
Hello, I am running into the same issue, but also the app is not connecting properly. In the main window I see the unit, it says it is on and gives the current temp, but when I click on it, it says that it cannot connect to the MELCloud. It seems that the user is blocked completely. I do not have other accounts.
EDIT: just got this message back from them: "We have detected excessive traffic from your account, your access to the service has been limited for a few hours."
Same issue here after updating to Haos 11.5 on february 5th. Tried to downgrade to 11.4. But the issue came back. Still in HA core 2024.1. i don't do any updates because I am not at home for 3 weeks...
I'm on latest fw and the connections seems to be lost all together. Also I'm not able to connect anymore via MELCloud app. Looks like my IP is banned or the service is down.
Update: after disableling the MELCloud intergration for a few hours it seems that my ban is lifted and the intergration works again for me.
I can confirm it. The integration works (again), but only with the polling disabled. Otherwise the user get banned for 2-3 hours. The only drawback I could find till now is the missing current temperature, which is annoying, but not really critical.
IMHO, the only possible alternative would be to have the API details to connect directly to the unit, being this already accessible in the local network.
The integration works (again), but only with the polling disabled.
Where / how did you change the polling settings please @archipita ?
The integration works (again), but only with the polling disabled.
Where / how did you change the polling settings please @archipita ?
At config of integration
The integration works (again), but only with the polling disabled.
Where / how did you change the polling settings please @archipita ?
Go to the MELCloud integration, then press on the 3 dots beside the Integration entries (right side) and click on System Options. There, disable the second entry (polling).
Thanks!
The integration works (again), but only with the polling disabled.
Where / how did you change the polling settings please @archipita ?
Go to the MELCloud integration, then press on the 3 dots beside the Integration entries (right side) and click on System Options. There, disable the second entry (polling).
You are able to control the AC system when disabling polling?
I'm still on the old version ( OS 11.4 and Core 2024.1.6) and have no issues with polling enabled, but as soon as I disable it I can't control the system through HA anymore. All AC's just become "unavailable"
You are able to control the AC system when disabling polling?
Hi, in my case yes, I can still control everything. the only drawback is that you do not get the current temp and consumption (see below).
Thanks! Apparently for me disabling it just removed all values and I think I might've had to wait some time before new values were added. Currently running it on the latest HA with polling disabled. Did have to disable the MelService for a few hours to get rid of the "excessive traffic" error but all is good now.
Is it possible to make polling interval as a setting in order to avoid ban from melcloud?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Annoying policy. Issues don't automatically resolve themselves..
Is it possible to make polling interval as a setting in order to avoid ban from melcloud?
The problem
Other issues of this problem were locked prior to the new release of HA. After upgrading, the integration worked fine until just now, where my account again was rate limited.
Is there something else that can be done here?
What version of Home Assistant Core has the issue?
core-2024.1.6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
MELCloud
Link to integration documentation on our website
No response
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