I’ve replied to your logs by email: both MELCloud APIs answer that your credentials are not the right ones, I need more to be able to troubleshoot since you’re the only one who reported such an issue (it works well for myself with both APIs).
I have currently uninstalled the app. Deleted the devices and account on the old Melcloud.
Starting from scratch on the now new Home app and adding devices.
When that works, I’ll try the Homey app again…
Let me know. Just be aware that the auth part is just a layer of the official apps, so it wouldn’t make sense if works on the ones and not on the others…
Logging in with Home account works, but if I want to do any changes/Configure, I only have the classic option, and I cant change any configurations. Also there are no communications with the devices added.
Once the MELCloud Home is authenticated, it’s expected that only the Classic one is proposed: it will disappear only in case of successful authentication.
“Devices don’t communicate”: can you be more specific – including screenshots and concrete examples?
Once the MELCloud Home is authenticated, it’s expected that only the Classic one is proposed: it will disappear only in case of successful authentication.
First login with Home = OK. Then in the configure meny, I have to login with the Classic, so it does not disappear.
Communication issues;
I can’t turn it on/off. Can’t change temp. Can’t change state Cooling / Heating.
But this seems to be more an Mitsubishi issue, than your app, so I’ve reached out to their support.
I’ll get back when they have fixed their issues Thanks so far
I have 4 airco’s and a ecodan heatpump, installed february this year. I’m running the home app. I’ve bin trying to set up these devices in Homey without succes. I’ve installed the app en configered my acount in settings under ‘home’. When I try to add devices, it says: no new devices found. I’ve tried different kind of troubleshooting without succes. Any suggestions?
Hi @Gerjanshoe, sorry I missed the notification of your message. Ecodan working with MELCloud Home is in progress… quick question, do you have a one or two-zone device?
Thank you for your great job. As I completed my heatpumps install I had to move to Melcloud Home and migrated all my olds heatpump air-to-air. I run Homey Pro 2016-2019, removed the legacy Melcloud app and reinstall the latest after firmware upgrade needed. Unfortunately the login to Melcloud Home failed. I go to App parameters then long loader, then a popup “Loading failed”. I tried to compile your latest dev version Main branch, and it works I’m able to login… Hope it can help.
Does the application is ok for homey energy? can we have an overview of the kwh used on energy sheet? the Energy data from melcloud are well push into your application?
Hi @RedhaB, it’s implemented for the MELCloud Classic, in progress for MELCloud Home, but the data is very poor: no real time, only data refreshed every 2 hours.
I am following up on the end of our PM and GIT conversation about Holiday Mode. I have done a bunch of experimentation with the flow cards for Holiday Mode. When I set HM using the then flow card this is what happens:
Holiday mode settings are modified (visible in Homey app settings and in Melcloud native app Holiday Mode settings too).
Both start date and time and end date and time are set. The end date and time is correctly calculated from the number of days specified.
If you set HM with days = 0 HM is correctly cancelled
That’s all great, except… that the start time is set to hh:mm at the very moment you set it - unless you are very lucky and hit the flow card at exactly hh:mm:00 the unit never switches into Holiday Mode because hh:mm:00 has already gone past (the flow card executes at hh:mm:15, for example)
I don’t think this is a fault in your homey app - as you suggested in your response to my original question, all you are doing is pinging the Melcloud API. It seems to be a fault in the API itself.
I also played around with the Homey App Settings to establish Holiday Mode. These work perfectly. Whatever settings you put in the Homey App for Holiday Mode are immediately reflected in the Melcloud app. Assuming you set the start time for some time in the future, Holiday Mode kicks in and all is well.
I do want to be able to control Holiday Mode from Homey Flows. I suggest a workaround is to provide a flowcard (or several) that work by directly updating the app settings rather than by calling the API. Flowcards might be:
Then Set Holiday mode between <start date><start time> and <end date><end time> in <zone>
Then Cancel Holiday Mode in <zone> [cancels holiday mode in that zone to toggles on the on/off]
And If Holiday Mode in <zone> is enabled [the existing card seems to work for this]
When Holiday Mode Starts in <zone> [don’t know if this is possible]
When Holiday Mode Ends in <zone> [ditto]
From my experience there is no problem setting Homey App Settings from the app code, so I see no reason why this should not work.