# MelCloud polling issues

**URL:** <https://community.openenergymonitor.org/t/melcloud-polling-issues/25518>\
**Category:** Heatpump\
**Tags:** melcloud\
**Created:** [6 February 2024 14:02 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518 "2024-02-06T14:02:06Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\
**Post date:** [6 February 2024 14:02 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/1 "2024-02-06T14:02:06Z")

</div>

> [@Anyone monitoring a new R32 Ecodan?](https://community.openenergymonitor.org/t/anyone-monitoring-a-new-r32-ecodan/19577/236):
>
> P.S. Annoyingly the Mitsubishi person looking at my data yesterday on MelCloud means my pymelcloud script can’t connect as it is being throttled.

Off-topic: how often are you usually polling MelCloud? I used to be able to get away with every minute but occasionally had to drop to 2 minutes. I now keep it at 2 minutes, which is just about usable still, and I don’t have to worry about it sometimes stopping. You might be able to get some data if you throttle back on the polling.

---

<div class="post-metadata">

**Author:** ![ajdunlop](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@ajdunlop](https://community.openenergymonitor.org/u/ajdunlop)\
**Post date:** [6 February 2024 14:20 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/2 "2024-02-06T14:20:47Z")

</div>

> [@Timbones](#):
>
> Off-topic: how often are you usually polling MelCloud? I used to be able to get away with every minute but occasionally had to drop to 2 minutes. I now keep it at 2 minutes, which is just about usable still, and I don’t have to worry about it sometimes stopping. You might be able to get some data if you throttle back on the polling.

I think it is set to 2 mins but I’ve realised that the systemd restart for my script was misconfigured so may have been bombarding it with connection attempts.

---

<div class="post-metadata">

**Author:** ![ivy](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/i/bc8723/32.png) [@ivy](https://community.openenergymonitor.org/u/ivy)\
**Post date:** [7 February 2024 11:26 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/3 "2024-02-07T11:26:26Z")

</div>

Looks like they’ve started limiting 3rd party access to MelCloud in the last couple of days as my script also has been getting throttling errors - [MELCloud - Error - "This request has been throttled due to an excessive amount of traffic to our service" · Issue #109728 · home-assistant/core · GitHub](https://github.com/home-assistant/core/issues/109728) has some more details on this, doesn’t look like there’s a hard limit currently.

---

<div class="post-metadata">

**Author:** ![greentangerine](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/greentangerine/32/12689_2.png) [@greentangerine](https://community.openenergymonitor.org/u/greentangerine)\
**Post date:** [7 February 2024 11:33 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/4 "2024-02-07T11:33:32Z")

</div>

Same here using pymelcloud and uploading to emoncms.

Was fetching every 60s but moved to 5 minutes and now working ok.

---

<div class="post-metadata">

**Author:** ![ajdunlop](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@ajdunlop](https://community.openenergymonitor.org/u/ajdunlop)\
**Post date:** [7 February 2024 14:18 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/5 "2024-02-07T14:18:40Z")

</div>

Well that’s annoying. I’ll try every 5 mins later.

Maybe I need to look into that local solution.

---

<div class="post-metadata">

**Author:** ![greentangerine](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/greentangerine/32/12689_2.png) [@greentangerine](https://community.openenergymonitor.org/u/greentangerine)\
**Post date:** [7 February 2024 15:09 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/6 "2024-02-07T15:09:48Z")

</div>

It was working OK for a while at 5 minutes and now getting the error again. Annoying as three of the values feed into the Heatpump app.

Doesn’t appear to be any official comment from Mitsubishi on this. Maybe it’ll fix itself …

---

<div class="post-metadata">

**Author:** ![ajdunlop](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/a/6bbea6/32.png) [@ajdunlop](https://community.openenergymonitor.org/u/ajdunlop)\
**Post date:** [7 February 2024 16:21 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/7 "2024-02-07T16:21:36Z")

</div>

It is annoying that they don’t provide a proper API with clear fair usage parameters

---

<div class="post-metadata">

**Author:** ![greentangerine](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/greentangerine/32/12689_2.png) [@greentangerine](https://community.openenergymonitor.org/u/greentangerine)\
**Post date:** [8 February 2024 22:02 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/8 "2024-02-08T22:02:32Z")

</div>

I’m now on 10 minutes polling interval for 13 hours and no throttling.

Some official output from Mitsubishi would be helpful.

---

<div class="post-metadata">

**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\
**Post date:** [22 February 2024 09:52 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/9 "2024-02-22T09:52:54Z")

</div>

23 posts were split to a new topic: [WiFi + MQTT dongle for Mitsubishi Ecodan](https://community.openenergymonitor.org/t/wifi-mqtt-dongle-for-mitsubishi-ecodan/25628)

---

<div class="post-metadata">

**Author:** ![mjr](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mjr/32/19990_2.png) [@mjr](https://community.openenergymonitor.org/u/mjr)\
**Post date:** [9 February 2024 23:38 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/16 "2024-02-09T23:38:44Z")

</div>

I think I will add a configuration option to my melcloud-mqtt script to set the user agent to one you get from your browser, to make it harder to distinguish from you leaving a browser open on their web app.

Does anyone know if the meldec proxy still works?

---

<div class="post-metadata">

**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\
**Post date:** [10 February 2024 00:03 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/17 "2024-02-10T00:03:26Z")

</div>

> [@mjr](#):
>
> Does anyone know if the meldec proxy still works?

I tried it a while ago, but didn’t manage to make it work. Maybe I’ll give it another go…  
Thanks for the reminder, I’d forgotten about this one.

---

<div class="post-metadata">

**Author:** ![mjr](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/mjr/32/19990_2.png) [@mjr](https://community.openenergymonitor.org/u/mjr)\
**Post date:** [11 February 2024 11:06 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/21 "2024-02-11T11:06:51Z")

</div>

> [@Timbones](#):
>
> I tried it a while ago, but didn’t manage to make it work. Maybe I’ll give it another go…

Ah so I see. If melcloud is encrypting and locked to a certificate chain, that is rather difficult to break. Intercepting the cn105 connector seems a more likely path to success.

I wonder what happens to our MMSP payments if Melcloud blocks us or, more generally, breaks. I wonder whether our MMSP provider would read from emoncms.

---

<div class="post-metadata">

**Author:** ![markocoheat](https://community.openenergymonitor.org/letter_avatar_proxy/v4/letter/m/9e8a1a/32.png) [@markocoheat](https://community.openenergymonitor.org/u/markocoheat)\
**Post date:** [11 February 2024 22:16 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/23 "2024-02-11T22:16:16Z")

</div>

> [@mjr](#):
>
> I wonder what happens to our MMSP payments if Melcloud blocks us or, more generally, breaks. I wonder whether our MMSP provider would read from emoncms.

I think a conversation with DESNZ to allow “jailbreaking” under MMSP where it’s clear that it’s being jailbroken for the better might soon mitigate any hadaches there!

(I should think they like OEM - and if not they should as it’s done more than any formal MMSP option)

---

<div class="post-metadata">

**Author:** ![greentangerine](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/greentangerine/32/12689_2.png) [@greentangerine](https://community.openenergymonitor.org/u/greentangerine)\
**Post date:** [15 February 2024 17:54 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/30 "2024-02-15T17:54:30Z")

</div>

> [@greentangerine](#):
>
> I’m now on 10 minutes polling interval for 13 hours and no throttling.

Just for final info, I did try moving back to 5 minute polling again but it failed after a while.

10 minutes works without issue so I’ve rebuilt my feeds to expect 600s as the interval.

---

<div class="post-metadata">

**Author:** ![MyForest](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/myforest/32/16336_2.png) [@MyForest](https://community.openenergymonitor.org/u/MyForest)\
**Post date:** [16 February 2024 02:00 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/31 "2024-02-16T02:00:39Z")

</div>

I know I moan about this more than anyone else, but at the moment I seem to be getting alone fine with 2-minute polling:

 ![image](https://community.openenergymonitor.org/uploads/default/original/3X/1/4/140452c33d854444743d75cc9d18cdc1e4a0987d.png)

As you all know I chased and chased this with the technical team inside Mitsubishi and wasn’t able to get any improvement.

---

<div class="post-metadata">

**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\
**Post date:** [16 February 2024 08:58 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/32 "2024-02-16T08:58:41Z")

</div>

> [@greentangerine](#):
>
> I did try moving back to 5 minute polling again but it failed after a while.

That’s unfortunate. Maybe it doesn’t like odd numbers? How many requests are you making each time?

> [@greentangerine](#):
>
> I’ve rebuilt my feeds to expect 600s as the interval

I only use timeseries type for feeds these days, so changing the interval isn’t an issue.

---

<div class="post-metadata">

**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\
**Post date:** [4 April 2024 10:53 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/33 "2024-04-04T10:53:44Z")

</div>

I thought I would try 1 minute polling again, but only while the heat pump was running. Worked great for a few hours until I got the dreaded “We have detected excess traffic from your account” message. Turned it off for a bit and went back to 2 minute interval after an hour.

So that limitation seems to be here for good.

---

<div class="post-metadata">

**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\
**Post date:** [21 April 2024 23:31 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/34 "2024-04-21T23:31:25Z")

</div>

12 posts were split to a new topic: [MELCloud Service Outage - April 2024](https://community.openenergymonitor.org/t/melcloud-service-outage-april-2024/26033)

---

<div class="post-metadata">

**Author:** ![Timbones](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/timbones/32/20308_2.png) [@Timbones](https://community.openenergymonitor.org/u/Timbones)\
**Post date:** [24 May 2024 16:30 UTC](https://community.openenergymonitor.org/t/melcloud-polling-issues/25518/37 "2024-05-24T16:30:28Z")

</div>

A post was merged into an existing topic: [MELCloud Certificate Issues - May 2024](https://community.openenergymonitor.org/t/melcloud-certificate-issues-may-2024/26189/3)
