is this still an issue for you? new update is in approval.
Hi,
Since the update adding support for the frost protection mode the app sets the new target temperature to 16 degrees on both my CZ25 heat pumps. When I manually change back to a desired level, it still reverts back within approximately 60 seconds.
I’ve (reasonably) isolated the issue to the Homey app rather than the official Comfort cloud app or other sources such as schedules or the remote controls.
The only thing I haven’t done is to re-install the app in Homey.
I will send a diagnostics report just after this. 5d3c77cb-5d28-47f6-b016-c2bd9e925a5c
Let me know if I can do anything else for you to help.
Thanks for a great app so far! @Johnny_Espesete
Best regards
Rikard
Hello
i am sorry for this, i found a bug that have been fixed and published. The app should update shortly on your homey and fix the issue.
Unfortunately, the air conditioner is still unreachable even after the update. I can add it successfully, and it works for about 5 minutes. After that, I receive an error message and I can no longer control it.
I can see the air conditioner’s energy consumption in the power tab, but I am unable to control the device.
Follow up on previous.
It did not fix my issue. Now one of them revert to 16 degrees and the other one to 17. The common denominator is they both move to exactly 2 degrees below the current measured room temperature. Maybe coincidence.
While you might look into a fix, I’ll need to disable the app so we’re not freezing. 
Thanks.
/Rikard
Disable the app until further notice, dont freeze to death because of the stupid app 
I will check the code, i must be missing something somewhere. !
Send me a diagnostic report and i will check!
Thanks, here you go:
07616c2b-8f23-4227-b784-0835c44b3dcd
The log you sent shows the app restarting a few times, but doesn’t quite catch the moment the temperature actually dropped to 16°C. Could you help me with two things?
- Did you (or the Homey app) restart or toggle the Panasonic app off/on around the time this happened — for example while troubleshooting, or a Homey reboot? I noticed the app restarted 3 times in a short window, and that timing might be connected to the bug.
- Next time it happens, could you wait 2–3 minutes and then send a fresh diagnostics report (rather than right away)? That gives the app time to log a couple of normal update cycles, which will show me exactly what values it received right before and after the temperature changed — that’s the key piece I’m missing.
Also, just to narrow things down: was Frost Protection mode active or had it been used recently on this device?
-
Yes, I toggled several times including restarting.
-
Will do, report number below. I observed that as soon as I enabled the app, it instantly set the temperature to 16 on the “verkstad” device and 17 on the “energy center” device. I have not changed any settings at all during this test run. Finally I will disable it again due to risk of frostbite.
cfb3cbfc-8e80-4f53-9d75-37830cf7b2a6
Regarding Frost protection mode: No, I have never used it on any of the two devices. In this case only “Cool” mode for both.
Thanks for the detailed feedback — that “it happens instantly on enable, no settings touched” detail is really valuable, and it rules out the theory I was chasing before (this isn’t the Frost Protection issue, since you’ve confirmed you’ve never used that mode).
I haven’t been able to pin down the exact cause yet, because the app wasn’t logging enough detail to see what’s actually happening at the moment the temperature changes. I’ve just released v2.1.26, which adds more detailed logging — it doesn’t change any behavior, it just lets me see exactly what the app receives from Panasonic and what (if anything) it sends back.
Could you please:
- Update to v2.1.26 (should arrive automatically, or check under Apps).
- Next time you enable the app and see it jump to 16/17°C again, wait a minute or two, then send a fresh diagnostics report the same way as before.
With the new logging, that report should tell us whether the temperature change is coming from the app or if it’s already like that when we read the device’s status — which is the key thing I’m missing right now.
Really appreciate your patience and the clear reports so far — this is exactly the kind of detail that helps track these things down.
Hi again.
I really appreciate the fast feedback loops and your great attention to this. It’s fun to hopefully be able to help.
I’ve followed your steps and here’s the report:
332ca5db-61f6-45f0-adcb-b8e5f3c03184
Good news — I found the actual cause, and it’s not a bug in the app itself. Looking at the detailed logs from your last report, I can see exactly what happens:
- The app starts and reads the correct temperature (22°C and 20.5°C).
- A few seconds later, something sends a command telling the app to change the temperature to your indoor temperature minus 2°C (that’s why it became 18°C and 16°C — matching your room temperature at the time, not a fixed number).
The important part: this command isn’t coming from the Panasonic Comfort Cloud app’s own logic — it’s an external command arriving right when the device becomes available again. That points to either:
- A Homey Flow on your system that reacts to this device becoming available (or the app starting) and sets the temperature based on the room temperature — possibly an old “frost guard” flow you or someone else set up a while back, maybe before this app had its own built-in Frost Protection feature.
- Homey’s own Zone/Energy heating settings — under Homey Energy → Heating, or your Zone settings, there can be an automatic eco/comfort temperature tied to this device.
Could you check the following in the Homey app?
- Flows → search for any flow that mentions this device (Luftvärmepump / Verkstad LVP) and involves “temperature” — especially anything triggered by the device/app “becoming available” or “starting.”
- Zones / Homey Energy → Heating → check if either device’s zone has an automatic eco or comfort temperature configured.
If you find a flow like this, that’s very likely the culprit — the timing (a few seconds after the app starts) lines up exactly.
Thanks again, this diagnostic report was exactly what I needed to crack it!
Hi Johnny,
I’m unable to add my Panasonic heat pump using Panasonic Comfort Cloud v2.1.27.
After entering my Panasonic email address and password, the login fails with:
No code in redirect: /mf?state=…
I have verified the following:
– The same email/password works when logging into the official Panasonic Comfort Cloud app on another phone.
– My Panasonic ID/email login and Sign in with Apple are linked to the same Panasonic account.
– The heat pump is visible and works normally in the official Comfort Cloud app.
– The Homey error occurs both from the Homey iOS app and when adding the device through Homey Web on a computer.
I have generated a Homey diagnostics report. I can provide the diagnostic report code if needed.
Could this be related to the OAuth/redirect handling in the current version? Panasonic appears to redirect back with state, but Homey reports that no code was present.
You may be onto something with the OAuth/redirect question. Here’s what I found looking at the code: our app logs into Panasonic by directly simulating the login requests a browser would make (no actual browser window), which works fine for accounts with a plain email+password login. However, I noticed Panasonic officially supports linking Apple/Google sign-in to a Panasonic ID — and I suspect that when an account has that link, Panasonic’s login service inserts an extra “confirm/merge account” step that requires a real interactive browser to complete. That’s likely the /mf?state=… page you’re seeing — it’s not the normal callback URL our app expects, so it never gets the authorization code.
I want to be upfront that I can’t confirm this 100% yet, but it fits the evidence well, and a proper fix (using a real embedded browser during setup) would be a fairly large change I don’t want to make without being more sure first.
Would you be willing to try this as a test:
- Temporarily unlink Apple Sign-In from your Panasonic account (via Panasonic’s website/account settings, not the Homey app).
- Try pairing again in Homey using just your email and password.
- If that works, you can likely re-link Apple Sign-In afterward — the Homey pairing only needs the plain credentials once, and the app stores its own login session rather than reusing Apple’s.
If this fixes it, that confirms the theory and gives me a solid lead for a proper fix down the line. If you’d rather not unlink it, let me know and I’ll look for other options.
Hi,
Sorry delayed response but my Homey had some connection issues that I had to resolve before I could make another test.
I disconnected Apple login and then it worked!
Br, Caroline
Skickat från Outlook för iOS
great! i’m glad to hear that 
Hi @Johnny_Espesete,
I’m having an issue with your Panasonic Comfort Cloud app on Homey Pro.
My setup:
Homey app: Panasonic Comfort Cloud v2.1.30
Indoor AC unit: Panasonic S-6071PF
WLAN adapter: Panasonic CZ-CAPWFC2 (Commercial AC WLAN Adapter)
Device name in Panasonic Comfort Cloud: Medhils
The air conditioner works correctly in the official Panasonic Comfort Cloud app. I can turn it on/off, change the target temperature and control it normally.
Homey successfully connects to my Panasonic Comfort Cloud account and also discovers the unit during pairing. I can select it and add it to Homey without any error.
However, immediately after adding it, the device is shown as “Unavailable”.
I have also restarted the Panasonic Comfort Cloud Homey app, but the device remains unavailable.
Diagnostics report ID:
b3a51983-2b0e-473d-b30c-006862864053
Could you please have a look at the diagnostic report?
Thank you very much for your help !!
Hi! I will look into your diagnostic report!
Between 11:23 and 12:21 there were a couple of failed login attempts (incorrect username/password), which is expected — the app applies a short cooldown after repeated auth failures so it doesn’t hammer Panasonic’s servers.
After 12:21 the login itself succeeded, but for about 7 hours after that, Panasonic’s cloud API reported no devices on the account when the app asked for your device list. That’s not something the app controls — it means your indoor unit wasn’t yet visible to your account on Panasonic’s side at that point (this can happen right after adding/re-adding a unit in the official Comfort Cloud app, or if it needs a bit of time to propagate).
At 19:10 your device (“Medhils”) showed up and paired successfully, and in the two app restarts logged after that, it initialised without any errors. So based on this log, it looks like the “unavailable” state you saw was during that earlier window before Panasonic’s cloud had registered the unit — and it should be working now.
Could you confirm whether it’s still showing unavailable currently? If so, could you send a fresh diagnostic report from right now — that’ll show me the live polling behavior rather than the pairing history.
