I turned my AC on to check, and it started fine, then a few minutes later showed up with:
I don’t have any automations running at present, just using the Homey app to manually control it. The manufacturer’s Panasonic Comfort Cloud app (Android) is still working fine (same login). I only have 1 AC using the Homey app. This is exactly the time it stopped working:
Diag report:
d1b7c6dc-b5f5-4e2c-9057-fa25bf6d08f6
could you send me a diagnose rapport? by email. Just use the Send diagnose rapport from the homey app
I published a fix now, 2.1.12, update and see if that helped?
I have installed and testet your app, it worked fine to install the app and it got connected and could read out the values, but then it only shows “Could not reach Panasonic Comfort Cloud” and it will not respond or work at all.
I have sent you a log:
5c5d1c4c-9f5e-4245-a73a-9ba8047af390
Thnx Johnny.
I Have removed the Panasonic app, restarted Homey, added the Panasonic app (2.1.12),
added the devices, they are recognised again, I updated the Flows again.
Try to report back tommorow mornig.
1 strange thing, 1 airco looks enabled (both windows webapp and android-app),
but in reality it is off, even after restarting the Panasonic app.
Kind regards Dj.
P.S. off and on switchen in the android app solved the problem.
2.1.13 should fix this problem. In review awaiting approval.
2.1.12 has me working again. Thanks Johnny:
The app works with the aquarea heat pump?
Just an observation, my AC doesn’t have a motorised Left/Right direction, just Up/Down. I now have an Auto Swing Left/Right button in the app that automatically turns to on, and on the next page, Swing Left/Right capability shows and is showing set to 2 -Left.. I can change this setting to any position (obviously this doesn’t change anything at the AC), but the Auto Swing Left/Right button remains activated. Is the app able to test if the model supports L/R and hide these settings if it doesn’t? Report b7f2954d-8470-4ed8-9ab7-60cdfcb937c7
Another couple of observations: The background colour isn’t changing to orange in heat mode anymore (just remains black - I have it displayed in Dark mode), but still changes to Blue in Cool mode. This issue fixes itself when I switch to Light Mode, then back to Dark mode.
Also, my unit has Eco Mode. Can this be supported in the app?
Aquera is an air to water system with its own drivers. Will not work
Goodmorning Johnny,
In my case with the airco units, everything works now,
so now the Flap goes in the right direction, Thanks a lot. 
Kind regards, Dj.
Neat! Thanks for your fast response and implementation!"
Hi,
Thank you for your hard work on the Pansonic Comfort Cloud app!
I’m currently using a custom dashboard (my own) to control my Homey devices, and I noticed that functions like “Dry Mode”, “Fan Only Mode”, and “Auto Swing Up/Down” are missing from the main Thermostat widget. I see that they are implemented as separate buttons/toggles on another tab in the Homey app as you said.
However, because they are implemented as custom boolean capabilities (separate switches) rather than standard enumeration values, third-party dashboards and integrations (like Apple HomeKit or Google Home) cannot automatically detect and map them to their standard AC interfaces.
Would it be possible to include these options in the standard Homey capability enumerations?
For instance, adding Dry and Fan as selectable values inside the standard thermostat_mode capability.
Adding auto (or up_down/left_right) inside the standard swing_mode capability instead of having them as separate buttons.
Using the standardized enumerations would make the app fully integrated and seamless with external dashboards and smart home hubs.
Thanks again for a great app!
That is solid feedback! Ill see what i can do for you
Thanks @Johnny_Espesete - I am loving this new app - especially how quickly it activates the Aircon. Just another thought for your consideration - I have logic running on my Homey Pro that needs to detect a change of Aircon mode, so that any change made to the mode from outside the Homey environment is detected and the Homey logic reset accordingly. Currently you have a Thermostat Mode Changed trigger, but as this requires a mode to be selected in the card, I need to stack four different cards to detect a mode change has occurred. Would it be possible to rename the current card to “Thermostat Mode Changed to …” and add a new card for “Thermostat Mode Changed” that would trigger on any change of mode? Alternatively the existing card could have an “any” option added, so it would trigger on any change.
2.1.14 is in review with you request implemented. Could you test and see if this is something that would work for you?
dry and fan_only → thermostat_mode
This is doable. Homey lets you override a standard capability’s values in app.json, and many AC apps (Daikin, Mitsubishi, etc.) do exactly this — they add dry and
fan_only as extra enum values. The code change is clean: remove the two boolean capabilities, fold their logic into the thermostat_mode listener, and update the mode
mapping tables.
The catch is HomeKit and Google Home. Both platforms only recognize off/auto/heat/cool from thermostat_mode — they can’t map dry or fan_only to anything in their AC
interfaces. So this helps custom dashboards (they can read the enum directly), but won’t give HomeKit/Google Home any extra benefit.
The other concern is migration: existing users have flows built on the panasonic_dry and panasonic_fan_only boolean capabilities. Removing them breaks those flows
silently. We’d need to keep the booleans around or give a clear deprecation notice.
Auto swing → standard swing capability
Homey doesn’t have a standard swing_mode capability (that’s a Home Assistant concept). There’s nothing to standardize to on the Homey side, so this part of the request
can’t really be fulfilled in a meaningful way.
My biggest concern is breaking something since there are now almost 200 users on this app. This was only meant to be a single user-project = me
