Would anyone happen to know if it’d be possible to build something like GitHub - rospogrigio/localtuya: local handling for Tuya devices but to communicate locally with our Mitsubishi device using Wifi? I’ve been successfully using localtuya, it’s awesome. I wonder how hard that’d be to replicate for this use case. Prob not easy but does anyone have an idea?
I’m guessing it may be “unpossible” as apparently the wifi device checks for Mitsubishi certificates… So if we try to man in the middle we’ll just get an error with the certificates I guess…
I had the same issue after upgrading today. I disabled the integration, waited until I could log in from my App again, then enabled the Integration and it worked normally.
Well, all i can say is that i wish i swapped to local (esphome) earlier. Having external temperature sensor is light years better when we’re talking about heating with climate (can’t say about cooling yet…). Temperature is as I set it on my climate and it’s way more stable than with original (built-in) one.
You can use Google Translate (right mouse) it should work and explain itself.
PS: My file is not made to be used as a package, I am not familiar with packaging.
I just found out the code to get it working and hope that the Melcloud integration on HACS could take advantage of that to integrate the extra sensors of a ASHP.
The integrations is like this:
In Configuration. yaml
sensor: !include melcloud.yaml
Your melcloud.yaml has to be changed for login/password/device ID and building ID.
Hope this helps.
Walter
Hello Vilppuvuorinen,
I’m not familiar with coding in a way that allowed me to understand your GitHub post completely.
From what I gather, you’ve created a method to combine information into a single sensor with multiple attributes, similar to my “heat_pump_API” sensor.
You suggest that this sensor could later be split into individual sensors using the attributes and templating (like your “melcloud.yaml” file), but you prefer not to take that approach.
This approach could potentially provide a Melcloud integration for key variables and an additional interface through templating for more specific sensors like frequency, daily usage, and additional zone temperatures.
Is my understanding of your method correct?
Thank you for all the work you’ve done so far; it’s beyond my current expertise!
Apologies if this has been mentioned somewhere but could not see it.
I recently got an ASHP and consequently added the ‘melcloud’ integration in to home assistant. Looks good so far apart from getting blocked has HA is sending too many api calls.
How do I change the default polling time that HA or rather the itegration uses? I could not find the corresponding yaml files in HA but I am a newbie.
On one post I saw that the default may be 5 mins and changing it to 6 mins resolves the issue but I feel it most e polling more that once every 5 mins to get blocked by melcloud? Not sure.
Having wrestled with Melcloud API based control in various different forms over the last year, which worked pretty well for a while, I finally gave up when they started throttling all the API based traffic recently, and built a local MQTT based control unit, based on:
I wish I had made the jump earlier - it’s like going from a clumsy 1960s Lada to a 2024 BMW.
Massive thanks to Richard Broker for creating this amazing project. Shame that one man can create such a polished interface that works beautifully, whereas an enormous multinational corporation fails miserably to provide any sort of decent control.
I thought I’d post my experience in case it helps someone else. If you’re happy to do some soldering and a bit of wiring it’s a relatively straight forward project. I used the schematic posted by Dan_Nichols in the above link with an ESP32 WROOM-32 board. On my board the 5v in pin is labelled VIN. Flashed it using Arduino IDE (chose ESP32 Dev Module as board type, although I think it worked with ESP32-WROOM-DA-Module too). After a few hiccups due to libraries, dependencies and Python packages it installed fine. Once rebooted it broadcast the WiFi network as outlined in Richard Broker’s Github repository, and followed the config instructions. I first mocked it all up using a 5v power supply from a butchered USB cable, to avoid constantly plugging/unplugging the CN105 plug and damaging it. Once connected to the heat pump I had to switch the PIN numbers to get Rx and Tx the right way round. The WiFi range seems fairly reasonable for the board I chose, despite not having an external antenna. It’s been pretty stable for the last few days. The web browser based config is excellent. All the MQTT sensors are populated automatically in HA from the Python package and that part was seamless. It exposes more sensors/controls than I ever managed using the Melcloud API and works beautifully.
All in all very happy, and massive thanks again to Richard Broker
This change got merged into the latest home assistant, version 2024.3.1 I think, so if you upgrade you shouldn’t have to do anything else. But where the files are depends on your installation. For me it’s in /home/homeassistant/data/homeassistant/custom_components/melcloud but you might find it in /usr/src/homeassistant/homeassistant/components/melcloud (but note that changes you make in supervised/container installations will be overwritten.
Seems like MELCloud has stopped updating used energy. At least mine has been now “flat lining” since 16.04.2024 22:10 EEST. All other values are still coming in from MELCloud. So I assume that there is some problem in the MELCloud end.
This is affecting at least FT25 and RW25 air-to-air heat pumps at the moment.
I have tried making a support ticket with Mitsubishi, which is no easy task. When I finally did, I got a person dumber than soup, not even reading my troubleshooting findings. Which includes me saying that the wifi-module 3 LED’s points to server issues, and that the LAN IP from the module is visible on my router, and can be pinged.
But writes: If you have changed the router or password for the router recently the MELcloud interface will need to be re-paired. Once successfully paired the app will connect and start communicating. See attached advanced pairing guide.
MAN… oh and the guide he attaches is for a newer wifi module that supports local wifi network for connecting to router. Mine is the older version, only supporting WPS.
One can only hope, someone with a bit more knowledge gets it fixed!. If they even know it’s down.
Hmm I have strange behaviour: some values are updated but some aren’t. For example OutdoorTemperature is “alive” but TankWaterTemperature is stuck. And most of other temps are stuck as well.
The MelCloud App is not showing the right Water Tank Temperature either, and is also stuck on some other values, so let’s hope is something temporary going on on their end, and not the integration.