Melcloud Cannot Connet about core

[simonepittis]

I use HAOS

the Core works like Docker in the OS

Install addon Advanced SSH & Web Terminal with Protection mode is disabled

[simonepittis]

it's an other way :-)

you can use the HACS "Additional CA for Home Assistant" too, if you use HAOS

[mainmind83]

change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"

1. Install Advanced SSH: https://github.com/hassio-addons/addon-ssh
2. Config plugin with user and password of root
3. Open terminal web
4. Execute: docker exec -it homeassistant /bin/bash
5. Execute: vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py
6. Search on line 34: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"
   change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"
   Basic vi: press "esc" and write ":w" to save file
   Basic vi: press "esc" and write ":x" to exit vi
7. Restart OS

[AuroreVgn]

In France I’ve got an SSL certificat error since this morning (May 24th) and the last change of temperature sensor was yesterday (May 23rd) at 17h25 (Paris time).

The iPhone app is working as MELCloud on web browser.
The Android app is not working.

Does anyone know to accept the certificat manually or have any idea to bypass this SSL verification?

[simonepittis]

I made the "workaround" (advanced users)

open HA shell:
docker exec -it homeassistant /bin/bash
vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py

on line 34 you find this: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"

change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"

save and exit

HA core restart

Fix it ;-)

[simonepittis]

I made the "workaround" (advanced users)
open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py
on line 34 you find this: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"
change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"
save and exit
HA core restart
Fix it ;-)

Are we expecting any issues with future updates or would this just get overwritten back to original?

this is only a workaround, waiting the SSL fix. if you update the CORE you lose the fix

[Nightstalker81]

I made the "workaround" (advanced users)
open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py
on line 34 you find this: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"
change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"
save and exit
HA core restart
Fix it ;-)

Are we expecting any issues with future updates or would this just get overwritten back to original?

Not 100% sure but it should possibly be the later one: overwritten to original and would (if needed) be manually edited again.

[ilwalti]

I made the "workaround" (advanced users)

open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py

on line 34 you find this: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"

change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"

save and exit

HA core restart

Fix it ;-)

Unfortunately, it doesn't work for me... nor the app works. Only web access is OK.

BTW, the real syntax of row 34 is as follows:
f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True
and I've changed accordingly:
f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False
(there are no double quotes at the beginning/end of the row)
Just to avoid misunderstandings.

[bkleef]

I prefer to keep SSL verification enabled with: verify_ssl=True.

The intermediate certificate which is missing in the chain is:

• Sectigo RSA Organization Validation Secure Server CA
• Fingerprint SHA256: 72a34ac2b424aed3f6b0b04755b88cc027dccc806fddb22b4cd7c47773973ec0
• Pin SHA256: RkhWTcfJAQN/YxOR12VkPo+PhmIoSfWd/JVkg44einY=

Check it yourself with: https://www.ssllabs.com/ssltest/analyze.html?d=app.melcloud.com.

Download: https://support.sectigo.com/articles/Knowledge/Sectigo-Intermediate-Certificates

Content of the .crt file:

-----BEGIN CERTIFICATE-----
MIIGGTCCBAGgAwIBAgIQE31TnKp8MamkM3AZaIR6jTANBgkqhkiG9w0BAQwFADCB
iDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCk5ldyBKZXJzZXkxFDASBgNVBAcTC0pl
cnNleSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxLjAsBgNV
BAMTJVVTRVJUcnVzdCBSU0EgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNMTgx
MTAyMDAwMDAwWhcNMzAxMjMxMjM1OTU5WjCBlTELMAkGA1UEBhMCR0IxGzAZBgNV
BAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEYMBYGA1UE
ChMPU2VjdGlnbyBMaW1pdGVkMT0wOwYDVQQDEzRTZWN0aWdvIFJTQSBPcmdhbml6
YXRpb24gVmFsaWRhdGlvbiBTZWN1cmUgU2VydmVyIENBMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEAnJMCRkVKUkiS/FeN+S3qU76zLNXYqKXsW2kDwB0Q
9lkz3v4HSKjojHpnSvH1jcM3ZtAykffEnQRgxLVK4oOLp64m1F06XvjRFnG7ir1x
on3IzqJgJLBSoDpFUd54k2xiYPHkVpy3O/c8Vdjf1XoxfDV/ElFw4Sy+BKzL+k/h
fGVqwECn2XylY4QZ4ffK76q06Fha2ZnjJt+OErK43DOyNtoUHZZYQkBuCyKFHFEi
rsTIBkVtkuZntxkj5Ng2a4XQf8dS48+wdQHgibSov4o2TqPgbOuEQc6lL0giE5dQ
YkUeCaXMn2xXcEAG2yDoG9bzk4unMp63RBUJ16/9fAEc2wIDAQABo4IBbjCCAWow
HwYDVR0jBBgwFoAUU3m/WqorSs9UgOHYm8Cd8rIDZsswHQYDVR0OBBYEFBfZ1iUn
Z/kxwklD2TA2RIxsqU/rMA4GA1UdDwEB/wQEAwIBhjASBgNVHRMBAf8ECDAGAQH/
AgEAMB0GA1UdJQQWMBQGCCsGAQUFBwMBBggrBgEFBQcDAjAbBgNVHSAEFDASMAYG
BFUdIAAwCAYGZ4EMAQICMFAGA1UdHwRJMEcwRaBDoEGGP2h0dHA6Ly9jcmwudXNl
cnRydXN0LmNvbS9VU0VSVHJ1c3RSU0FDZXJ0aWZpY2F0aW9uQXV0aG9yaXR5LmNy
bDB2BggrBgEFBQcBAQRqMGgwPwYIKwYBBQUHMAKGM2h0dHA6Ly9jcnQudXNlcnRy
dXN0LmNvbS9VU0VSVHJ1c3RSU0FBZGRUcnVzdENBLmNydDAlBggrBgEFBQcwAYYZ
aHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG9w0BAQwFAAOCAgEAThNA
lsnD5m5bwOO69Bfhrgkfyb/LDCUW8nNTs3Yat6tIBtbNAHwgRUNFbBZaGxNh10m6
pAKkrOjOzi3JKnSj3N6uq9BoNviRrzwB93fVC8+Xq+uH5xWo+jBaYXEgscBDxLmP
bYox6xU2JPti1Qucj+lmveZhUZeTth2HvbC1bP6mESkGYTQxMD0gJ3NR0N6Fg9N3
OSBGltqnxloWJ4Wyz04PToxcvr44APhL+XJ71PJ616IphdAEutNCLFGIUi7RPSRn
R+xVzBv0yjTqJsHe3cQhifa6ezIejpZehEU4z4CqN2mLYBd0FUiRnG3wTqN3yhsc
SPr5z0noX0+FCuKPkBurcEya67emP7SsXaRfz+bYipaQ908mgWB2XQ8kd5GzKjGf
FlqyXYwcKapInI5v03hAcNt37N3j0VcFcC3mSZiIBYRiBXBWdoY5TtMibx3+bfEO
s2LEPMvAhblhHrrhFYBZlAyuBbuMf1a+HNJav5fyakywxnB2sJCNwQs2uRHY1ihc
6k/+JLcYCpsM0MF8XPtpvcyiTcaQvKZN8rG61ppnW5YCUtCC+cQKXA0o4D/I+pWV
idWkvklsQLI+qGu41SWyxP7x09fn1txDAXYw+zuLXfdKiXyaNb78yvBXAfCNP6CH
MntHWpdLgtJmwsQt6j8k9Kf5qLnjatkYYaA7jBU=
-----END CERTIFICATE-----

With Docker you can add the intermediate certificate like:

-v $(pwd)/SectigoRSAOrganizationValidationSecureServerCA.crt:/etc/ssl/certs/SectigoRSAOrganizationValidationSecureServerCA.crt

[vekexasia]

it's an other way :-)

you can use the HACS "Additional CA for Home Assistant" too, if you use HAOS

Ive tried adding the sectigo crt and reload ha but no luck for me

[simonepittis]

try:

docker container cp /config/additional_ca/SectigoRSAOrganizationValidationSecureServerCA.crt homeassistant:/etc/ssl/certs/SectigoRSAOrganizationValidationSecureServerCA.crt

the other way if you have the HAOS

[simonepittis]

open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py

here comes the error cannot open binary file

1. docker exec -it homeassistant /bin/bash
2. vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py

two diff commands :-)

[simonepittis]

[eismarkt]

ok, i have change it , but it dosn´t work

[osulivanDE]

I could just reload the integration and now my Aircon is avaliable again.

[Klorins]

Yes, seems like its fixed in Melcloud`s end now. Works again here without any changes applied.

[simonepittis]

yes. cert fixed :-)

[simonepittis]

we will see next year :-D

[Nightstalker81]

to avoid this issue in the future... what is the best way right not to control mitsubishi aircon locally? despite of this issue repeating yearly melcloud is for me soooo slow.

If you meant what the best way to control the aircon locally is: I would suggest checking if the WIFI module in your aircon has a CN105 connector.
Just search for "ESP CN105". There are a lot of gateways out there you can easily build and install instead of the default WIFI module.
Some examples are:
https://github.com/geoffdavis/esphome-mitsubishiheatpump
https://github.com/dzungpv/mitsubishi2MQTT

In fact I will try and replace one of the modules myself and see whether that works nice.
If so, all other modules will also be replaced.

[mlauhalu]

Same issue here. Suddenly stopped working and trying to add the integration from scratch gets the cannot_connect error.

[jonare77]

Same here. I get a certificate verification error. Strange because Melcloud app works. Are they using diffrent certificates?

[home-assistant]

melcloud documentation
melcloud source

[eagle-phoenix]

Same here. Certificate verification error.

[elogreb]

Same here...PC app is working. Android app same as here

[eismarkt]

Same here

[MikeVanMelle]

Browser app working, mobile and HA can't connect.

[lovekull76]

My app has stopped working as well :/

[guihom83]

Same here but also Android app failed at login

and app.melcloud.com IS not stable

[emma201101]

App still works. Only Problems with HA interattion

[thephantom]

same here :(

[GMTheDoctor]

Same here, waiting for a solution :(

[Misxs]

same here

[philippebaque]

same here too.

web is working, but 'app' or 'ha' failed (certificats issue).

the certificate is working on web but not with 'app' or 'ha' ?

[OlivierZal]

It's an intermediate certificate issue:

Server certificate
subject=C=GB, ST=Hertfordshire, O=Mitsubishi Electric Europe B.V., CN=*.melcloud.com
issuer=C=GB, ST=Greater Manchester, L=Salford, O=Sectigo Limited, CN=Sectigo RSA Organization Validation Secure Server CA
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA
Server Temp Key: ECDH, prime256v1, 256 bits
---
SSL handshake has read 3491 bytes and written 450 bytes
Verification error: unable to verify the first certificate

[simonepittis]

the SSL certificate chain is not complete. unfortunately it happens every year when they renew the certificate.

https://www.sslshopper.com/ssl-checker.html?hostname=app.melcloud.com

there are only two solutions:

1. wait for them to change the certificate by installing the correct one
2. install the Intermediate certificate in HA... but I haven't found the correct procedure yet

[AuroreVgn]

1. Yep. Typical IT every year stuff 😅
2. If you find it, I can try it, if you need some help.

[Nightstalker81]

I made the "workaround" (advanced users)

open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py

on line 34 you find this: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"

change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"

save and exit

HA core restart

Fix it ;-)

Which unfortunately only works for Docker installations, right?
AFAIK with HAOS there is no such option or does anymore know of a workaround for HAOS?

[Pave87]

I made the "workaround" (advanced users)

open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py

on line 34 you find this: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"

change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"

save and exit

HA core restart

Fix it ;-)

Are we expecting any issues with future updates or would this just get overwritten back to original?

[hillell]

#92905 (comment)

[eismarkt]

i became an error cannot execute binary file

[simonepittis]

i became an error cannot execute binary file

where?

[eismarkt]

open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py

here comes the error cannot open binary file

[route66por]

Same error here

[Nightstalker81]

Just stumbled upon this... shouldn't it be possible to just copy the certificate to the shared folder "ssl" (if the Samba Share Addon is used)?
As I understand it that should be used custom certificates, shouldn't it?

[AuroreVgn]

I made the "workaround" (advanced users)
open HA shell: docker exec -it homeassistant /bin/bash vi /usr/local/lib/python3.12/site-packages/pymelcloud/client.py
on line 34 you find this: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True"
change to: "f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False"
save and exit
HA core restart
Fix it ;-)

Unfortunately, it doesn't work for me... nor the app works. Only web access is OK.

BTW, the real syntax of row 34 is as follows: f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True and I've changed accordingly: f"{BASE_URL}/Login/ClientLogin", json=body, raise_for_status=True, verify_ssl=False (there are no double quotes at the beginning/end of the row) Just to avoid misunderstandings.

Same for me, I have edited the file, reboot and still doesn't work.

[ilwalti]

After some time it worked on HA... at least for me. But still no joy with the phone app...

[AuroreVgn]

After some time it worked on HA... at least for me. But still no joy with the phone app...

I will wait.

[simonepittis]

After some time it worked on HA... at least for me. But still no joy with the phone app...

After some time it worked on HA... at least for me. But still no joy with the phone app...

I can't fix the app :-)

try to install the certificate in you mobile phone...

[eismarkt]

can you give me the command to write in the document.
because it is open but i can change anything in it

[AuroreVgn]

can you give me the command to write in the document. because it is open but i can change anything in it

You have to press "i". Once edited press "Esc" then ":wq"

[ilwalti]

After some time it worked on HA... at least for me. But still no joy with the phone app...

After some time it worked on HA... at least for me. But still no joy with the phone app...

I can't fix the app :-)

try to install the certificate in you mobile phone...
Nope. I think that Mitsubishi have to fix their own mistakes... Phone app is an official piece of the suite!

[AuroreVgn]

ok, i have change it , but it dosn´t work

Same here and still nothing.

I've tried the certificate method but it still doesn't work.
Did I have to delete the following links, I have in /etc/ssl/certs :

9046744a.0 -> ca-cert-Sectigo_Public_Server_Authentication_Root_R46.pem
ca-cert-IdenTrust_Public_Sector_Root_CA_1.pem -> /usr/share/ca-certificates/mozilla/IdenTrust_Public_Sector_Root_CA_1.crt
ca-cert-Sectigo_Public_Server_Authentication_Root_E46.pem -> /usr/share/ca-certificates/mozilla/Sectigo_Public_Server_Authentication_Root_E46.crt
ca-cert-Sectigo_Public_Server_Authentication_Root_R46.pem -> /usr/share/ca-certificates/mozilla/Sectigo_Public_Server_Authentication_Root_R46.crt
da0cfd1d.0 -> ca-cert-Sectigo_Public_Server_Authentication_Root_E46.pem

[margielm]

to avoid this issue in the future... what is the best way right not to control mitsubishi aircon locally? despite of this issue repeating yearly melcloud is for me soooo slow.

[margielm]

to avoid this issue in the future... what is the best way right not to control mitsubishi aircon locally? despite of this issue repeating yearly melcloud is for me soooo slow.

If you meant what the best way to control the aircon locally is

Yes sorry, i wanted to say "right now" Because i saw some projects but one of them was not updated for the last 4 years. thank you for the list of links. i will check it out.

[Nightstalker81]

No worries mate. I think I will try the ESPHome version, because of native integration into Home Assistant first.

[cedricdelecole]

Can you please confirm if this is the same problem I have because I am not sure I need to open a new issue :

On my side I have 2 cooling units. If I control them via HA, everything is ok (I can start the units and stop them. Units are controlled and melcloud interface is also "updated" accordingly ... BUT
If I control the units either via the remote control or via the Melcloud Mitsubishi app, the units are also controlled but HA is not updated accordingly

So it looks like communication is ok from HA towards Mitsubishi, but NOT from Mitsubishi towards HA

Is that the issue you have a and describe above, because I am really no ure ;-(

Many Thanks !

[Nightstalker81]

Can you please confirm if this is the same problem I have because I am not sure I need to open a new issue :

On my side I have 2 cooling units. If I control them via HA, everything is ok (I can start the units and stop them. Units are controlled and melcloud interface is also "updated" accordingly ... BUT If I control the units either via the remote control or via the Melcloud Mitsubishi app, the units are also controlled but HA is not updated accordingly

So it looks like communication is ok from HA towards Mitsubishi, but NOT from Mitsubishi towards HA

Is that the issue you have a and describe above, because I am really no ure ;-(

Many Thanks !

It is not directly the same issue.
The original issue had to do with a certificate change in the MEL cloud.
Your issue is related to the fact that the MEL cloud responds VERY slowly to local changes.

If you do not use HA at all, but just the MEL cloud (and their app) and e.g. a default IR remote control of the climate, the changes done by the IR remote do not show up in the MEL cloud until some time has passed (for me it was between 10-20 minutes!!!) or you do an active update of the MEL cloud app, thus forcing the app to reread the status of the climate.
I don’t know how in 2024 Mitsubishi thinks, that this is a good design, but that’s how it is.

If you want nearly instant updates in HA when you change the climate settings via an external system (e.g. the IR or MEL cloud), you need to stick to a DIY system, that works only locally.
See my post regarding CN105 above: #117997 (comment)

[cedricdelecole]

Can you please confirm if this is the same problem I have because I am not sure I need to open a new issue :
On my side I have 2 cooling units. If I control them via HA, everything is ok (I can start the units and stop them. Units are controlled and melcloud interface is also "updated" accordingly ... BUT If I control the units either via the remote control or via the Melcloud Mitsubishi app, the units are also controlled but HA is not updated accordingly
So it looks like communication is ok from HA towards Mitsubishi, but NOT from Mitsubishi towards HA
Is that the issue you have a and describe above, because I am really no ure ;-(
Many Thanks !

It is not directly the same issue. The original issue had to do with a certificate change in the MEL cloud. Your issue is related to the fact that the MEL cloud responds VERY slowly to local changes.

If you do not use HA at all, but just the MEL cloud (and their app) and e.g. a default IR remote control of the climate, the changes done by the IR remote do not show up in the MEL cloud until some time has passed (for me it was between 10-20 minutes!!!) or you do an active update of the MEL cloud app, thus forcing the app to reread the status of the climate. I don’t know how in 2024 Mitsubishi thinks, that this is a good design, but that’s how it is.

If you want nearly instant updates in HA when you change the climate settings via an external system (e.g. the IR or MEL cloud), you need to stick to a DIY system, that works only locally. See my post regarding CN105 above: #117997 (comment)

@Nightstalker81 ... it is not that slow from HA to Mitsubishi as when I start the unit from the HA, it takes 3 seconds for the command to come to Mitsubishi, and the Melcloud is also updated very quickly (few seconds) !!
So again, from HA towards Mitsubishi, only a few seconds .... but issue is from Mitsubishi (local remote or Melcloud) towards HA doesn't seem to update HA at all ...

P.S. How Can I check the current version of the Melcloud integration ? And the version installed on my Home assistant ? I would like to make sure I have the latest one but can't find any version anywhere ;-(

[Nightstalker81]

Can you please confirm if this is the same problem I have because I am not sure I need to open a new issue :
On my side I have 2 cooling units. If I control them via HA, everything is ok (I can start the units and stop them. Units are controlled and melcloud interface is also "updated" accordingly ... BUT If I control the units either via the remote control or via the Melcloud Mitsubishi app, the units are also controlled but HA is not updated accordingly
So it looks like communication is ok from HA towards Mitsubishi, but NOT from Mitsubishi towards HA
Is that the issue you have a and describe above, because I am really no ure ;-(
Many Thanks !

It is not directly the same issue. The original issue had to do with a certificate change in the MEL cloud. Your issue is related to the fact that the MEL cloud responds VERY slowly to local changes.
If you do not use HA at all, but just the MEL cloud (and their app) and e.g. a default IR remote control of the climate, the changes done by the IR remote do not show up in the MEL cloud until some time has passed (for me it was between 10-20 minutes!!!) or you do an active update of the MEL cloud app, thus forcing the app to reread the status of the climate. I don’t know how in 2024 Mitsubishi thinks, that this is a good design, but that’s how it is.
If you want nearly instant updates in HA when you change the climate settings via an external system (e.g. the IR or MEL cloud), you need to stick to a DIY system, that works only locally. See my post regarding CN105 above: #117997 (comment)

@Nightstalker81 ... it is not that slow from HA to Mitsubishi as when I start the unit from the HA, it takes 3 seconds for the command to come to Mitsubishi, and the Melcloud is also updated very quickly (few seconds) !! So again, from HA towards Mitsubishi, only a few seconds .... but issue is from Mitsubishi (local remote or Melcloud) towards HA doesn't seem to update HA at all ...

P.S. How Can I check the current version of the Melcloud integration ? And the version installed on my Home assistant ? I would like to make sure I have the latest one but can't find any version anywhere ;-(

Yes exactly.
As I said: the problem is the implementation of the MEL cloud itself.

If you are updating your AC from within HA you actually are using the MEL cloud connection.
So the flow is: HA triggers an update and sends the command to MEL cloud and the MEL cloud connects to the AC and sends the command down.

However if you are the other way around, i.e. not updating via the MEL cloud (either directly in their own app or indirectly, e.g. using the HA integration), the update of the AC state in the MEL cloud takes > 10 minutes, if you do not force it yourself (doing a refresh in the MEL cloud or their app).

So your problem is not related to the HA integration, but rather to the implementation Mitsubishi did with their MEL cloud.

This is exactly why I disconnected my ACs from MEL cloud and went the „Local control“ option.
No benefit from using the MEL cloud IMHO.

[cedricdelecole]

mmm acording me it was working perfectly in the past (last year when I started with HA ....).
I am confused with the MELcloud and the "app" ... for me was the same.

Bottom line if I update from the Mitsubishi APP or the remote control, the APP is updated but command is never sent back to HA.
How can we be sure that it is not an issue in HA not being able to receive the data from Mitsubishi ???

[Nightstalker81]

mmm acording me it was working perfectly in the past (last year when I started with HA ....). I am confused with the MELcloud and the "app" ... for me was the same.

Bottom line if I update from the Mitsubishi APP or the remote control, the APP is updated but command is never sent back to HA. How can we be sure that it is not an issue in HA not being able to receive the data from Mitsubishi ???

Your problem then is possibly related to the fact that the integration is of type „Cloud polling“ which means, that updates are never actively pushed to the integration.
You have at least the delay of the polling Intervall of the integration to the MEL cloud.
Since (I assume) Mitsubishi did not provide a mechanism for pushing this info down (at least they do not use this in their own apps as well), there is no way the HA integration can show updates near real time.

[cedricdelecole]

but you are telling me then the Mitsubishi Melcloud integration is then not able (anymore) to receive data from Mitsubishi themselves, if operation is done within their APP or the remote control ????