[RELEASE] Unified Thermostat Driver - MELCloud, MELView, Kumo Cloud and more if you want

Oh, ok then.... :slight_smile: Let me see what I can manage in the next couple of weeks.

And thanks for your support, particularly in this feature.

1 Like

Sorry @tohm, but my time seems to be even more limited than normal lately. I can't honestly commit to any time when I might be able to look at this meaningfully. If the mood strikes me and I do, I will take that opportunity, but I would not count on that, unfortunately.

I installed a Mitsubishi heat pump a few weeks ago. Your driver has been great, but the Kumo Cloud service has been Really flakey. Every few days goes non responsive (http timeouts, or 503 server full) for hours (1-5 hrs) at a time. “Downdetector.com” shows them down for the same intervals. I’ve resorted to “repeat while” loops (10 minute retries) to get changes to take place.

Local control would be really nice and/or feedback in the device state that the catch{} after the try{} caught an error. I know you are busy and I’ve considered picking up your GitHub start on local control, but I’m reluctant to start debugging from a diverged branch. Willing to help any way I can.

1 Like

Thanks, and nice to hear you have found the drivers useful, cloud-platform issues aside.

That's a good decision to hold back on what is essentially a relatively stale version of the driver from my previous work on local control for Kumo units. I expect the vast majority of the changes in the meantime have been relating to the European (MELCloud) platform, but I can't say for certain without checking.

(warning... nerd-ish talk coming up... :slight_smile: )

My memory of where I was at is that I had cracked the hardest part of encrypting the comm's to the unit, it was just a case of expanding the list of commands that were covered by the differently formatted message needed when communicating locally. There may be one or two more complicated one's left, but I hope it will be relatively straight forward.

My next step (which I don't know when it may be, could be someone else's if they want it) will be to setup a new copy (branch) of the current driver and merge the local control changes I developed previously, deleting that old branch. Once the same local commands I implemented can be tested successfully in the merged copy, then I/we can complete implementation of the remaining commands.

That all sounds great, but may be some time away. If you are keen and able, you are welcome to go down a similar path I described above. If I get any time to spend on developing HE stuff, I'll try to direct it this way.

1 Like