# \[APP\]\[Pro\] MELCloud (Classic), MELCloud Home & MELCloud Extension - Take control of your heat pump

**URL:** <https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094>\
**Category:** Apps\
**Tags:** app, devices, homey-pro\
**Created:** [December 4, 2022, 9:18pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094 "2022-12-04T21:18:26Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![stig\_hansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stig_hansen/32/47991_2.png) [@stig\_hansen](https://community.homey.app/u/stig_hansen)\
**Post date:** [September 7, 2023, 1:36pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/41 "2023-09-07T13:36:38Z")

</div>

Hei  
thanks for one great app and well taken car of, i was wondering is it possible to get a card or somthing for reading temp from a external sensor and not be controlled from the internal on?? as it seems to uppdating rely slow not only in to homey but also to Melcloud app?  
also is there a setting in this app or a card for enabling circulation mode? i dont seem to find it in any of the options?  
brg  
stig Hansen

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [September 7, 2023, 2:08pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/42 "2023-09-07T14:08:05Z")

</div>

Hi @stig_hansen,

Homey policy does not allow an app controlling physical devices to communicate with other apps.

I created a separate app where I make MELCloud able to communicate with an exterior temperature sensor: [Extension pour MELCloud Appli pour Homey | Homey](https://homey.app/fr-fr/app/com.mecloud.extension/MELCloud-Extension/) but I don’t aim to add new features than the only existing one for the moment.

Anyway I don’t think it would solve your issue: any card would communicate with MELCloud API, which may be the bottleneck for responsivity…

Kind regards

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [September 7, 2023, 2:10pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/43 "2023-09-07T14:10:38Z")

</div>

@stig_hansen, what do you call “circulation mode”?

Theoretically I implemented all the features available with the MELCloud official app / API, unfortunately the others are available only in the physical device or with the remote control.

---

<div class="post-metadata">

**Author:** ![stig\_hansen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/stig_hansen/32/47991_2.png) [@stig\_hansen](https://community.homey.app/u/stig_hansen)\
**Post date:** [September 7, 2023, 2:45pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/44 "2023-09-07T14:45:59Z")

</div>

hei ahhh i understand and thanks fro rely fast reply and explination 😄

---

<div class="post-metadata">

**Author:** ![Logchem](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/logchem/32/68609_2.png) [@Logchem](https://community.homey.app/u/Logchem)\
**Post date:** [September 11, 2023, 6:05am UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/45 "2023-09-11T06:05:34Z")

</div>

In the 21.1.0 release the app has stopped working. The flows has errors and for that reason the cooling temp was set to 5 degrees celsius. Can I go back to the previous version?

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [September 11, 2023, 7:02am UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/46 "2023-09-11T07:02:17Z")

</div>

Hi @Logchem, should be fixed with 21.1.1. Can you please confirm? Sorry for the inconvenience ☹

---

<div class="post-metadata">

**Author:** ![Logchem](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/logchem/32/68609_2.png) [@Logchem](https://community.homey.app/u/Logchem)\
**Post date:** [September 11, 2023, 7:36am UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/47 "2023-09-11T07:36:26Z")

</div>

> [@OlivierZal](#):
>
> 21.1.1

Just tested everything and it looks like everything is working again in release 21.1.1 🙂

---

<div class="post-metadata">

**Author:** ![clindh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/clindh/32/60091_2.png) [@clindh](https://community.homey.app/u/clindh)\
**Post date:** [September 25, 2023, 9:01pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/48 "2023-09-25T21:01:54Z")

</div>

You can read the current fan speed into a variable using Logic, but is it possible to **set** the fan speed from a variable?

I have a ”Silence my fan” flow for watching TV, and would like to restore the fan speed after X hours to the speed that was current when I started the flow

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [September 25, 2023, 9:26pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/49 "2023-09-25T21:26:49Z")

</div>

Hi @clindh, I think that [CountDown Appli pour Homey | Homey](https://homey.app/fr-fr/app/nl.bevlogenheid.countdown/CountDown/) or [Chronograph Appli pour Homey | Homey](https://homey.app/fr-fr/app/nl.fellownet.chronograph/Chronograph/) could do the job.

---

<div class="post-metadata">

**Author:** ![clindh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/clindh/32/60091_2.png) [@clindh](https://community.homey.app/u/clindh)\
**Post date:** [September 26, 2023, 9:43am UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/50 "2023-09-26T09:43:26Z")

</div>

Thanks. I have the “after X hours” working already though - the problem is that in the _Set fan speed to_-card you select the speed from a menu, I see no way to set it from a variable. Can it be done from HomeyScript somehow, or can maybe @OlivierZal can implement support for setting it from variable, as an option?

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [September 26, 2023, 10:10am UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/51 "2023-09-26T10:10:59Z")

</div>

Hi @clindh, indeed I didn’t well understand your need yesterday.

It should be settable with the same value than the one you get, since each label is actually a “number string” value as follows:

```auto
"values": [
            {
              "id": "0",
              "title": {
                "en": "Automatic",
                "fr": "Automatique",
                "nl": "Automatisch",
                "sv": "Automatiskt",
                "no": "Automatisk",
                "da": "Automatisk",
                "es": "Automático"
              }
            },
            {
              "id": "1",
              "title": {
                "en": "Very slow",
                "fr": "Très lente",
                "nl": "Zeer langzaam",
                "sv": "Mycket långsam",
                "no": "Veldig sakte",
                "da": "Meget langsom",
                "es": "Muy lento"
              }
            },
            {
              "id": "2",
              "title": {
                "en": "Slow",
                "fr": "Lente",
                "nl": "Langzaam",
                "sv": "Långsam",
                "no": "Sakte",
                "da": "Langsom",
                "es": "Lento"
              }
            },
            {
              "id": "3",
              "title": {
                "en": "Medium",
                "fr": "Moyenne",
                "nl": "Medium",
                "sv": "Medium",
                "no": "Medium",
                "da": "Medium",
                "es": "Medio"
              }
            },
            {
              "id": "4",
              "title": {
                "en": "Fast",
                "fr": "Rapide",
                "nl": "Snel",
                "sv": "Snabb",
                "no": "Rask",
                "da": "Hurtig",
                "es": "Rápido"
              }
            },
            {
              "id": "5",
              "title": {
                "en": "Very fast",
                "fr": "Très rapide",
                "nl": "Zeer snel",
                "sv": "Mycket snabb",
                "no": "Veldig rask",
                "da": "Meget hurtig",
                "es": "Muy rápido"
              }
            }
          ]
        }
      ]

```

So you maybe need HomeyScript to transform the number you initially get into a string, because `fan_speed` is a “dim” capability which **must return a number** , although flows handle **ids which must be strings**.

---

<div class="post-metadata">

**Author:** ![clindh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/clindh/32/60091_2.png) [@clindh](https://community.homey.app/u/clindh)\
**Post date:** [September 26, 2023, 10:18am UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/52 "2023-09-26T10:18:39Z")

</div>

Thanks, I see - so this is probably a question for the HomeyScript forum instead - how to call a card/action from HomeyScript passing in the parameters, instead of having it specified in the flow

---

<div class="post-metadata">

**Author:** ![Colin\_Osborne](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/colin_osborne/32/79809_2.png) [@Colin\_Osborne](https://community.homey.app/u/Colin_Osborne)\
**Post date:** [November 6, 2023, 6:30pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/53 "2023-11-06T18:30:16Z")

</div>

Thank you for adding this app for MELCloud.

I have successfully installed and connected the App with my heating system. I tried visualising all the available metrics in Homey web app “Insights” tab, but the only one that shows anything is “Wifi signal strength”.

There seem to be no data values for “Current fan speed”, “Fan speed”, “Target temperature”, or “Temperature”.

I then tried creating a flow to read and report the temperature field, but it showed a red exclamation error triangle and said:  
Invalid Token: homey:device:1af06477-39fb-4b23-8d17-c0a253f0ab5f|measure\_temperature

Is there something I need to do to enable further access and control?

My Homey system is:  
Model: Homey Pro (Early 2023)  
Version: 10.0.8

My heating system has the following:  
WIFI Interface - Mitsubishi MAC-567IF-E  
Controller - Mitsubishi Ecodan FTC6 Standalone Controller: PAC-IF072B-E  
Ecodan Model Number (Outside Unit): PUZ-HWM140VHA

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [November 6, 2023, 7:49pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/54 "2023-11-06T19:49:39Z")

</div>

Hi @Colin_Osborne, very strange, I will investigate… thanks for your feedback!

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [November 6, 2023, 8:53pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/55 "2023-11-06T20:53:50Z")

</div>

@Colin_Osborne,

On my side I’ve monitored for 1 hour: I have data for all the capabilities and everything seems to work fine.

Some thoughts:

- insights are not data retrieved from MELCloud but registered by Homey – consequence: if your Homey is off, insights will be empty, and if you remove a device or a whole app, the insights won’t be recovered after reinstalling

- some capabilities seem to be duplicated: some have data and others make the mobile app freeze and appear empty on the web app – insight display is not handled by the app but by Homey (the app just flags the capabilities which needs to appear under the insight tab), so it’s not under my control

- fan\_power: 0 = automatic mode is set (even if the inside units are off)

- fan\_power\_state: can be 0 if the target\_temperature is reached, in particular when the automatic mode is set

- temperature scales don’t start at 0 but at minimal temperature (i.e. 16 °C for air-to-air heat pumps), so that they can look empty

---

<div class="post-metadata">

**Author:** ![Colin\_Osborne](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/colin_osborne/32/79809_2.png) [@Colin\_Osborne](https://community.homey.app/u/Colin_Osborne)\
**Post date:** [November 6, 2023, 9:58pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/56 "2023-11-06T21:58:43Z")

</div>

Thanks for checking. Is there any diagnostic testing that I can do? I’m puzzled that one data field seems to be available but not others.

As I type this I wonder about the fact that presumably Wi-Fi signal strength comes from the Wi-Fi adaptor itself, but the other fields should come from deeper into the Mitsubishi system?

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [November 6, 2023, 10:31pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/57 "2023-11-06T22:31:39Z")

</div>

All values come from the MELCloud API.  
Do you have screenshots to share?

---

<div class="post-metadata">

**Author:** ![Colin\_Osborne](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/colin_osborne/32/79809_2.png) [@Colin\_Osborne](https://community.homey.app/u/Colin_Osborne)\
**Post date:** [November 11, 2023, 4:36pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/58 "2023-11-11T16:36:55Z")

</div>

After a separate discussion … Thank you Olivier for developing the MELCloud app, and thank you for your assistance with diagnosing my issues. It turned out that something was wrong with my initial app installation (no idea why), and it could see the WiFi signal strength parameter but nothing else. Anyway, having removed the device and the MELCloud Homey app, and then reinstalled … now it seems to be working correctly. Thanks again.

---

<div class="post-metadata">

**Author:** ![Christer\_Sjostrom](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/christer_sjostrom/32/628_2.png) [@Christer\_Sjostrom](https://community.homey.app/u/Christer_Sjostrom)\
**Post date:** [November 14, 2023, 4:36pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/59 "2023-11-14T16:36:36Z")

</div>

Since 12 a clock today (14 Nov 2023) MelCloud app stopp reading values and can’t set values. The MelCloud app from Mitsubishi can read and set values.

Have restarted Homey and restarted the Ecodan Air/Water heatpump but no success.  
’  
Any other with the same problem?

EDIT:

After a couple of reboots it starts working again.  
Problem solved.

---

<div class="post-metadata">

**Author:** ![OlivierZal](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/olivierzal/32/61843_2.png) [@OlivierZal](https://community.homey.app/u/OlivierZal)\
**Post date:** [November 14, 2023, 5:03pm UTC](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094/60 "2023-11-14T17:03:06Z")

</div>

Hi @Christer_Sjostrom, I’m glad it works again.

I didn’t experience myself the issue.

The last time it happened (working on MELCloud / not working on Homey), it was the MELCloud certificate which has expired and needed to be renewed.

Kind regards

[Previous page](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094.md?page=2)

[Next page](https://community.homey.app/t/app-pro-melcloud-classic-melcloud-home-melcloud-extension-take-control-of-your-heat-pump/73094.md?page=4)
