Could someone please point me towards the energy recovery ventilator that is compatible with MELCloud and Homey? The ERV below “supported devices” looks like the Mitsubishi VL-50SR2-E, but according to my retailer the VL-50 can’t be integrated with the Mitsubishi Electric Wi-Fi Interface.
Hi,
The app does support ERV devices, provided that they could be connected to Wi-Fi modules, and then could be controlled via a MELCloud account.
Kind regards
Hi @OlivierZal,
On my Uwano 7000 remote I have a button named “Circulator”. Is there any way to get this mode/function selected via flow card? I suspect it is not included in the MelCloud API.
It is really nice to use the “Circulator” function during winter when heating by wood in my living room fireplace, but would like to get it “automated”…
Brgds
Jan K.
Hi @Yankie, a good lead to know if it’s available via MELCloud API is: is there a button to activate this mode on the official MELCloud app?
Hi @OlivierZal , no there is not, unfortunately. But the “preset buttons #1, 2 & 3” is there. I can’t see that they are available in your app via flow card. I could store the “Circulator” as a preset condition and trigger that if available. Possible you can make those cards?
Brgds
Do you mean that presets on MELCloud app are the same than on the remote control? Would be interesting since the ones work with Wi-Fi while the others works with IR.
Hi @OlivierZal, no they are only in the app, not on the remote. But any setting you do with remote and then save current settings in the app as one of the preset buttons you will then get that “setting” on the heating pump. At least that was what the guy installing the heating pump told me.
I thought since they are in the MELCloud app they should also be in the API, but I might be wrong.
I think it’s true but that only the values available in the API are captured, since this API cannot be aware of the others, and most of all cannot read or control them.
Hey!
Came here to say I have issues logging in, similar to the HA issue here: MELCloud first registration fail · Issue #134113 · home-assistant/core · GitHub
As I comment there also, my guess is that the Homey app needs to be adapted for the new Melcloud Home API and App, to fully work going forward. The new app was created in Nov 2024, and on the swedish website they clearly state that they plan to migrate all existing users to that new service during 2025. So some new installations having issues now, but there will be more people possibly later this year.
Source (in swedish): MELCloud Wi-Fi-app | Mitsubishi Electric
Hi @Sigurdur_Birgisson, the authentification for the classic MELCloud app and the MELCloud Home app is completely different (different APIs). My app can work only with the classic MELCloud account.
Unfortunately, today it’s technically not possible to port the old app to the new app: the new APIs are different and partially public (I remind that I’m not a paid Homey or MELCloud developer, just a guy doing it in his free time…), and as for today don’t over all the classic MELCloud features and data.
If such a migration happens, that would mean that my app will be deprecated.
Hi Olivier, I am using your MELCloud app now for a couple of years with pleasure. I have a split system with 4 units in each bedroom. We basically only use one of the bedrooms at the moment, so we also only have one of the 4 split units on (the rest is turned off). I recently investing in an Athom Energy Dongle, but I now notice that all 4 units are always in the top energy consumers. When I examine the energy usage I also see that the other 3 units seem to have a similar power usage but then smaller then the one on our bedroom:
I saw in an earlier post that someone else had a similar problem, but you answered this in private, so I am wondering if this is a known issue and if there is anything I can do in the advanced settings to remove this mixture of power usage?
Hi @rstroot,
First of all, unfortunately the data comes straight forward from the MELCloud API, so no bug from the app… BUT here’s what you need to know about MELCloud Energy API:
- Not real time
- Updated only every 1 hour, without more details under a 1-hour range
- Low-precision values, specially for power since it’s deduced from a 2-hour energy range
- Data is given per external unit, not per internal unit – that’s why you see the same value for all your devices: that’s the external unit value divided by 4…
Conclusion: the API is bad, and values are not reliable.
I put them because maybe they provide some info and because people requested me to add them, but that’s also why I allow users to disable this data from device settings.
I hope my explanations help you understand your data inconsistencies…
Kind regards
