New app Panasonic Comfort Cloud

Apps
,
81

Thanks Johnny. I will ask Robert if Homekitty could also trigger onoff when changing thermostat mode. If not, I will implement your workaround.

Regards

Dennis

82

Thanks. Just set up the flows. Unfortunately it doesnā€™t workto turn the AC on via HomeKit. The thermostat mode is changed as I can see (blue dot behind temp on the tile of the device). But it doesnā€™t turn on. Activating the flow in the homey app turns it on fine though. But turning it off works via HomeKit and homey app. Strange. Maybe thatā€™s the change you implemented to change the mode to off when the AC is turned off?

83

After looking into it more, the Homey flow approach unfortunately doesnā€™t work reliably when the trigger comes from an external bridge like HomeKitty ā€” Homey only fires those flow triggers
for changes initiated within Homey itself, which is why it worked when you activated it manually but not from HomeKit.

So I went ahead and made the change in the app after all. Version 2.1.18 is out ā€” changing the thermostat mode to cool/heat/auto will now automatically turn the device on as well. No flows
needed, it just works.

Sorry for the detour!

84

Sounds great. Thank you so much! Will test it tomorrow :flexed_biceps:t2:

85

Hi, Iā€™ve got a new homey pro, a Panasonic airconditioning connected to the comfort cloud and app working. Checked username password several times. Still when trying to add my airco I cannot get passed the authorization. Wrong username. Removed app, restarted homey, reinstalled, same issue. What am I doing wrong here? Thanks, Bert

86

Just below the credential fields there is a sign in button, have you tried that?

87

Yeah, at least 20 times. This morning I added my phone number to my Comfort Cloud account (you try anything) and, ā€¦ IT WORKED! Got through authentication. Thanks for your work and response.

88

I had the app installed with 3 units. But since some weeks they stopped working (message: could not reach panasonic cloud). Today I uninstalled the app and reinstalled the comfort cloud app in homey pro. Now, when adding new units I need the authenticate, but when entering email and password, clicking the sign in button it says ā€˜No redirect from authorizeā€™.

89

Strange..could you try to send me a diagnostic report from the homey app?

90

This is de code for the diagnostic report: 29c46238-c45d-4a1b-ba9f-4b55c494624b

91

Great. Have you tested your account on the official panasonic app?

92

Yes. I can login when on cellular. But when Iā€™m on local WiFi it looks like Iā€™m blocked out by Panasonic, since I will only get that messsge then. And the homey is in my local network so it seems itā€™s blocked by ip.

I checked the login attempts in my Panasonic account, and it show login attempts, for every minute for a long period. It stopped at 18-6 (thatā€™s also when the integration stopped working).

So it looks like the homey-integration tried to login every minute for a longer period and therefore Panasonic blocked my local ip. Are you familiar with this issue? I already reached out to Panasonic support for whitelisting my ip, but there seems to be something wrong with the integration.

93

Thank you for this app. I am currently using a Home Assistant integration to control my heat pumps and I am looking forward to move my code to your app. While doing the migration, I have noticed the following issues.

Using the developer tools web site, when I inspect a device created by your app, the domain of the capability ā€˜panasonic_swing_udā€™ goes from 0 to 4 instead of 0 to 5.

I have 2 outside compressors, one working with only one internal unit and the other with 2. The 1 compressor - 1 internal units combo works fine with your app. However with the outside compressor with 2 internal units:

  • The energy is over estimated. It seems that the energy consumed by the outside compressor is getting added to both internal units.
  • The 2 internal units randomly keep switching from reachable to unreachable (I havenā€™t figure out a pattern). Everything is working fine in Home Assistant and in the Panasonic app. Looking in my router software, the connections are fine and data is being received and sent. I have try deleting the app, rebooting Homey and reinstalling the app and heat pumps, but it doesnā€™t fix the problem. Let me know if you need more information to fix this

Next is a feature request, It would great is you could support the Eco mode of the newer heat pumps.

Thanks again.

94

What happened: When sign-in fails repeatedly for an account, older versions of the app would retry the full login every single minute (matching the poll interval). Panasonicā€™s servers see that as abusive traffic and respond by temporarily blocking the source IP. Thatā€™s why itā€™s network-specific for you: your phone on cellular uses a different IP and still works, while your home WiFi (same network as your Homey) is the IP that got blocked.

So there are two separate things going on:

  1. The IP block is on Panasonicā€™s side ā€” nothing in Homey can clear it. Reaching out to Panasonic support to unblock/whitelist your IP (which youā€™ve already done :+1:) is the right move. In many cases it also clears on its own after a while.

  2. The app shouldnā€™t have hammered the login in the first place ā€” thatā€™s a bug, and itā€™s now fixed.

The fix (v2.1.20):

  • The app now backs off when sign-in fails (waiting progressively longer) instead of retrying every minute, so it can never trigger this block again.
  • Sessions are now renewed via token refresh and remembered across restarts, so it needs to do a full sign-in far less often.

Itā€™s on its way through the app store now.

What Iā€™d suggest on your end:

  1. Wait until Panasonic has lifted the block on your home IP (test by trying the official Panasonic Comfort Cloud app while on home WiFi ā€” once that works, the block is gone).

  2. Update the Homey app to 2.1.20 once itā€™s live.

  3. Re-add/re-pair the device and re-enter your credentials, just to be sure the stored login is current. A persistent sign-in failure is usually caused by a changed password (or a 2FA/account prompt) on the Panasonic account ā€” if your password was changed at any point, the old one stored in Homey would have been what kept failing. Worth double-checking that.

Let me know how it goes once your IP is unblocked and youā€™re on 2.1.20

95
  1. Swing Up/Down range (0ā€“4 vs 0ā€“5)

This is most likely expected rather than a bug. Up/Down has 5 physical vane positions (Top, Close-to-Top, Middle, Close-to-Bottom, Bottom), so the capability exposes values 0ā€“4. Left/Right has more positions (up to ā€œWideā€), which is why it goes higher. One difference from the Home Assistant integration: this app exposes the auto/swing state as a separate toggle (Auto Swing Up/Down) rather than as a value inside the position list, so the position enum has one fewer entry than you may be used to.

That said ā€” if your unit actually reports an airSwingUD value of 5 at some position, then Iā€™m missing it and should add it. Could you check in the developer tools what raw airSwingUD value the unit reports for the position that looks missing? If itā€™s a real 5, itā€™s a quick fix.

  1. Energy over-estimated on the 2-indoor-unit compressor

Youā€™ve diagnosed this correctly. On a multi-split, Panasonic meters the outdoor compressor and reports that same consumption against each indoor unitā€™s device ID. The app reads energy per device, so two indoor units each report the full outdoor figure ā€” which is why it looks doubled.

Thereā€™s no per-indoor breakdown available from the Panasonic API, so I canā€™t split it cleanly. The possible workaround is to use the group/topology info to detect indoor units that share an outdoor unit and only attribute the energy once. Iā€™d like to look into that ā€” if you can paste the group structure from the developer tools (the device list grouping), thatā€™ll help me design it.

  1. Indoor units flapping between reachable and unreachable

This one was a real bug on my side, and itā€™s now fixed in v2.1.21. The app was marking a device ā€œunavailableā€ after a single failed poll. On accounts with several indoor units there are more requests per minute, so a brief blip or a transient rate-limit from Panasonic would instantly flip a unit offline, then the next poll would bring it back ā€” exactly the flapping you saw, and why everything looked fine in Home Assistant and the Panasonic app. The app now tolerates short outages (a few consecutive misses, or a few minutes) before reporting unavailable. Please update to 2.1.21 and let me know if the flapping stops.

  1. Eco mode on newer units

Happy to look at adding this. I just need to know which parameter your unit uses for it, since it varies by model. Could you paste the raw ā€œparametersā€ JSON for one of the newer units from the developer tools ā€” ideally one capture with Eco on and one with it off? That lets me identify the exact field and add a proper toggle/flow card for it.

96

Since this weekā€™s update, the device has been offline. Even after removing it and adding it again, the device remains unavailable.

97

Please send diagnostic report

fre. 26. juni 2026, 09:19 skrev Jesse Bakker <notifications@athom.discoursemail.com>:

98

I created and submitted a diagnostic report: 9d8b7064-69fd-4308-84f9-1f3bd8680c5b