Update problem when changes are made directly in MELCloud

[ericl780]

First, thanks for your work on this — it works great. I just wanted to flag a problem: when I change a setting in MELCloud from my iPhone, Home Assistant doesn't sync, which breaks some of my scripts. For instance, if I turn the AC off from the iPhone and then try to restart it from HA, HA still thinks the unit is on and won't turn it on, since it never registered that I'd switched it off from the iPhone.

[andrew-blake]

Hi @ericl780, what you're seeing is a known limitation worth explaining.

The MELCloud API doesn't push state changes to us, so the integration has to poll for them. We deliberately keep that to once every 60 seconds to avoid hammering Mitsubishi's servers with requests. If the integration were too aggressive, they could rate-limit or block it entirely, which would affect all users.

As part of that, before sending a command, the integration checks whether the device is already in the requested state and skips the API call if so. If HA's view is stale and it still thinks the unit is on because it hasn't polled since your iPhone change, it skips the command entirely.

If you make a change in the MELCloud app, waiting around 60 seconds before trying to control the same thing from HA will let the poll fire first and sort it out.

Fixing this properly would need real-time push updates from Mitsubishi's servers, which is a significant architectural change and not something on the near-term roadmap.

Out of interest, is there a reason you use the MELCloud app rather than the HA companion app on your phone? Just curious whether there's a specific workflow we should think about.

[ericl780]

Today I'm migrating my Fibaro HC3 to HA, but all my heating/AC management is handled on the HC3, which controls HA via API. So I check whether everything is working properly by looking at the MELCloud app on my iPhone, and I readjust to run the tests. Of course, use of the MELCloud app will be dropped as soon as possible. Thanks very much for your reply.

[ericl780]

Hello,
I'm writing to ask for your help, please.
When I use HA (Home Assistant) to control my 6 split units, at first glance there's no problem, but when I control HA through the Fibaro HC3, I run into issues with the MELCloud server, which at first glance seems to freeze on the commands sent to the split. Let me explain:
I send this kind of command to HA for an update: self:setClim("living_room", "on", 24, "cooling")
So a systematic update of on/off, heating/cooling, temperature.
This works two or three times and then freezes the MELCloud server for sending commands (EVEN WITH THE MELCLOUD APP — no longer possible to send any commands). To get it going again, I cut the power to the split and turn it back on, which is a complete reset of the wifi card, and that doesn't work every time.
Last night, two splits were completely frozen. I left it overnight and this morning it's working again. I'm thinking there's some kind of incident reset on the MELCloud server.
Question: When you receive the On/Off status, heating type, and temperature in a single command, how is that processed before being sent to MELCloud?
I wouldn't presume to blame your program, but might it be possible that, in my very particular case, the MELCloud server receives a string of commands it can't interpret and then completely blocks communication afterward?
It's true that I'm going to migrate everything over to HA, but the whole house is still managed at this level by the HC3, and the program takes into account a lot of parameters, including the sensors that are still under Fibaro.
I'm in debug mode :=) — I'm continuing to investigate and I'm fully at your disposal. Like everyone, I'm capable of making a big mistake and overlooking something.
The wifi network is fine, no ping loss, around -50 dB on average for 2.4 GHz reception.
Here, in case it helps, is a copy of my QA that controls my HA.
With my thanks,

My HC3 QA (sorry comment in French, But I think you will understand
-- ============================================================
-- QuickApp HC3 : commande des thermostats Home Assistant
-- (Mitsubishi / MELCloud)
-- ============================================================
-- Variables QuickApp à créer (onglet "Variables") :
-- ha_url = http://192.168.1.37:8123
-- ha_token = <ton token longue durée HA, sur une seule ligne>
-- ============================================================
-- COMMANDES À ENVOYER (xxx= ID de ce QuickApp) :
-- fibaro.call(650, "setClim", "salon", "froid", 24) -- froid à 24°C
-- fibaro.call(650, "setClim", "salon", "chaud", 21) -- chaud à 21°C
-- fibaro.call(650, "setClim", "salon", "auto", 22) -- auto à 22°C
-- fibaro.call(650, "setClim", "salon", "on", 21) -- on (mode défaut)
-- fibaro.call(650, "setClim", "salon", "on", 24, "froid") -- on en froid à 24°C
-- fibaro.call(650, "setClim", "salon", "off") -- éteint
-- fibaro.call(650, "offClim", "salon") -- éteint (raccourci)
-- fibaro.call(650, "setFan", "salon", "auto") -- ventilateur auto
-- fibaro.call(650, "setFan", "salon", "moyen") -- ventilateur moyen
-- fibaro.call(650, "setFan", "salon", "max") -- ventilateur max
-- ============================================================

-- Correspondance pièce -> entity_id climate de Home Assistant
-- Récupère les entity_id exacts dans HA :
-- Outils de développement -> États -> filtre "climate."
local THERMOSTATS = {
salon = "climate.preteur_melcloudhome_7be9_89f9_climate",
amis = "climate.melcloudhome_9d8d_xxxx_climate",
chambre = "climate.melcloudhome_25d8_xxxx_climate",
cuisine = "climate.melcloudhome_944d_xxxx_climate",
bureau = "climate.melcloudhome_9d63_xxxx_climate",
couture = "climate.melcloudhome_2d3a_xxxx_climate",
}

-- Mode utilisé pour un simple "on" (sans précision chaud/froid)
local MODE_ON = "heat"

-- Correspondance commande "humaine" -> mode HVAC de HA
-- Mitsubishi : l'auto s'appelle "heat_cool" (pas "auto")
local MODES = {
on = MODE_ON,
chaud = "heat",
froid = "cool",
auto = "heat_cool",
off = "off",
}

-- Correspondance puissance "humaine" -> fan_mode de HA
-- /!\ Les valeurs de droite doivent correspondre EXACTEMENT à l'attribut
-- "fan_modes" de ton unité (voir GET /api/states/... en bas de fichier).
local FAN_MODES = {
auto = "auto",
min = "one",
faible = "two",
moyen = "three",
fort = "four",
max = "five",
}

function QuickApp:onInit()
self:debug("QuickApp HA Thermostat démarré")
self.haUrl = self:getVariable("ha_url")
self.haToken = self:getVariable("ha_token")
self.http = net.HTTPClient({timeout = 5000})

-- Test au démarrage (à commenter ensuite) :
-- self:setClim("salon", "on", 21, "froid")
-- self:setFan("salon", "auto")

end

---

-- Fonction interne : appel de service HA avec callback optionnel
-- onDone : fonction appelée après un succès (pour enchaîner)

---

function QuickApp:_callService(service, payload, label, onDone)
local url = self.haUrl .. "/api/services/climate/" .. service
self.http:request(url, {
options = {
method = "POST",
headers = {
["Authorization"] = "Bearer " .. self.haToken,
["Content-Type"] = "application/json",
},
data = json.encode(payload),
},
success = function(resp)
if resp.status == 200 or resp.status == 201 then
self:debug("OK : " .. label)
if onDone then onDone() end -- on enchaîne ici
else
self:error("Erreur HA (" .. label .. "), status=" ..
tostring(resp.status) .. " body=" .. tostring(resp.data))
end
end,
error = function(err)
self:error("Échec requête HA (" .. label .. ") : " .. tostring(err))
end,
})
end

---

-- Commande principale : mode (on/off/chaud/froid/auto) + température
-- piece : "salon", "amis", "chambre"...
-- commande : "on", "off", "chaud", "froid" ou "auto"
-- temperature : nombre (ignoré si OFF)
-- sens : (optionnel) "chaud" ou "froid", utilisé seulement
-- quand commande == "on" pour préciser le mode

-- Le mode est envoyé en PREMIER ; la température n'est envoyée
-- qu'APRES confirmation du mode (évite le télescopage MELCloud).

-- Exemples :
-- self:setClim("salon", "on", 21) -> allume (mode défaut) à 21°C
-- self:setClim("salon", "on", 24, "froid") -> allume en FROID à 24°C
-- self:setClim("salon", "chaud", 21) -> chaud à 21°C (forme directe)
-- self:setClim("salon", "froid", 24) -> froid à 24°C (forme directe)
-- self:setClim("salon", "off") -> éteint

---

function QuickApp:setClim(piece, commande, temperature, sens)
local entityId = THERMOSTATS[piece]
if not entityId then
self:error("Pièce inconnue : " .. tostring(piece))
return
end

commande = tostring(commande):lower()
local hvacMode = MODES[commande]
if not hvacMode then
    self:error("Commande inconnue : " .. tostring(commande) ..
               " (attendu on / off / chaud / froid / auto)")
    return
end

-- Si "on" + sens précisé, le sens prime
if commande == "on" and sens ~= nil then
    local sensMode = MODES[tostring(sens):lower()]
    if sensMode then
        hvacMode = sensMode
    else
        self:error("Sens inconnu : " .. tostring(sens) ..
                   " (attendu chaud ou froid) - mode par défaut utilisé")
    end
end

-- 1) On applique le mode, et SEULEMENT après son succès on règle la température
self:_callService("set_hvac_mode",
    { entity_id = entityId, hvac_mode = hvacMode },
    piece .. " mode=" .. hvacMode,
    function()
        -- callback exécuté après confirmation du mode
        if hvacMode ~= "off" and temperature ~= nil then
            self:_callService("set_temperature",
                { entity_id = entityId, temperature = temperature },
                piece .. " -> " .. tostring(temperature) .. "°C")
        end
    end)

end

---

-- Commande SPÉCIALE : puissance du ventilateur
-- piece : "salon", "amis", "chambre"...
-- puissance : "auto", "min", "faible", "moyen", "fort", "max"
-- (selon la table FAN_MODES ci-dessus)

-- Indépendante de setClim : ne touche ni au mode ni à la température.

-- Exemples :
-- self:setFan("salon", "auto")
-- self:setFan("couture", "max")
-- fibaro.call(650, "setFan", "salon", "moyen")

---

function QuickApp:setFan(piece, puissance)
local entityId = THERMOSTATS[piece]
if not entityId then
self:error("Pièce inconnue : " .. tostring(piece))
return
end

puissance = tostring(puissance):lower()
local fanMode = FAN_MODES[puissance]
if not fanMode then
    self:error("Puissance inconnue : " .. tostring(puissance) ..
               " (attendu auto / min / faible / moyen / fort / max)")
    return
end

self:_callService("set_fan_mode",
    { entity_id = entityId, fan_mode = fanMode },
    piece .. " ventilateur=" .. fanMode)

end

---

-- Raccourci dédié : éteindre une pièce
-- self:offClim("salon")

---

function QuickApp:offClim(piece)
self:setClim(piece, "off")
end

[andrew-blake]

Hi @ericl780, thanks for the detailed report and the code — very helpful.

The key clue is that the MELCloud app also stops responding. That rules out anything specific to the HA integration and points to something happening at the MELCloud server or device level that we can't see from our side.

The integration has built-in protections to avoid overloading the MELCloud API — request pacing, rate limiting, and deduplication to skip redundant calls. These are designed to keep us in good standing with Mitsubishi's servers. Those protections are still active when HC3 drives HA via the REST API, but they can't reduce the call volume below what HC3 is generating.

Each setClim in your QuickApp makes two HA service calls (set_hvac_mode then set_temperature), each of which becomes a MELCloud API call. Across 6 rooms that's 12 MELCloud calls per automation run, spaced 0.5s apart by our request pacer — so around 6 seconds of sustained API traffic each time. Run that a few times in quick succession while testing and the cumulative volume may be enough to trigger a server-side rate limit, which would explain why even the MELCloud app stops responding.

Once your migration is complete and HC3 is out of the picture, this will likely go away — HA's own automations would consolidate those into fewer calls and the volume stays well within normal limits.

If you want to see exactly what the integration is sending during a freeze, enabling debug logging would show the API calls and timing from our side:

logger:
  logs:
    custom_components.melcloudhome: debug

[ericl780]

I'm letting some time pass in order to check everything and get back to you with information if there's a problem.