A huge thanks to @Johnny_Espesete - I’ve missed this app!
My specific use is to guard my summerhouse, and start the heatpump if temperatures gets below a certain threshold.
Also I’d like to ensure that the tenants isn the house uses the nanoe-X function, so I’d like to force-enable this.
Would it be possible to add the nanoe-X enable/disable function to the flows?
Frost/temperature guarding for your summerhouse is already possible today — create a flow with “Outdoor (or Indoor) Temperature drops below X” as the trigger and “Turn on”/“Set thermostat mode” as the action, no update needed.
Nanoe force enable/disable is now added as a flow action card (“Set Nanoe Mode”) in the next release (v2.1.31) — you’ll be able to force it on for your tenants regardless of what they set locally.
Thank you very much for the kind words! And an awesome donation! Its great that this little app is of good use for so many people! it started as a little personal project and things have escalated
There is actually 1000+ users on this thing so any changes needs to be carefully tested so i don’t brake the flows or the app itself for so many people!
I noticed one annoyance and was wondering if you had an idea. The available temperature range when creating an action seems to be affected by the heat pump’s current mode. This means that if it’s in frost protection mode then I can’t select a temperature over 15C. Similarly if it’s in heat mode then I can’t select lower temperatures.
Maybe you could just allow the temperature selection to be in the widest possible range?
I looked into this. The temperature range follows the mode because the app only has one range for the target temperature, and Homey’s built-in “Set target temperature” card uses it as well as the slider. The app can’t give the flow card its own wider range.
I considered just allowing the full range all the time. I decided against it for now, because it could let flows send temperatures the unit doesn’t accept in other modes (for example below 16 °C in Cool). I can’t test that properly without risking other users’ flows.
For now you can work around it like this:
To set a temperature above 15 °C, turn Frost Protection off first.
Use the app’s own Frost Protection action card to switch it on and off in your flows.
I’ll keep it in mind for a future version if I find a safe way to do it.
update the app to 2.1.33 and send me a new diagnose report. I have added more error logging to pinpoint the problem. I think maybe Panasonic have made changes to their API.
To talk to Panasonic’s servers, this app identifies itself as the official Panasonic Comfort Cloud phone app, including a version number. Panasonic’s servers started rejecting the version number the app was sending, and answered with code 4106: “New version app has been published”. Your credentials, Homey and the app were fine. The failure came after the login had already succeeded.
What’s fixed in v2.1.34
The app now sends a version number that Panasonic’s servers accept. It takes the number from the official Android app’s listing, because the iOS number was ahead of what the servers support.
If Panasonic rejects a version, the app automatically tries known-good ones, so a future mismatch should fix itself.
Sign-in failures now log Panasonic’s actual response, which makes future problems easier to diagnose.
I’m having an authentication issue with Panasonic Comfort Cloud v2.1.34 in Homey.
The error is: OAuth step 3 failed: 400 invalid username
The username is definitely valid. I logged completely out of the official Panasonic Comfort Cloud app and successfully logged back in through Panasonic’s authglb.digital.panasonic.com login using the same Panasonic ID email address and password. My phone number is also registered and SMS verified.
Restarting Homey did not help. The Panasonic unit is working normally in the official Comfort Cloud app.
Could this be related to Panasonic’s current OAuth/authentication flow? Is there a workaround or newer/test version I could try?
Update: I managed to solve the problem by adding the Panasonic device through my.homey.app on my PC. Using exactly the same Panasonic ID and password that gave OAuth step 3 failed: 400 invalid username in the Homey iOS app, authentication succeeded from the Web App.
The heat pump is now connected and working correctly from Homey, including on/off and status feedback.
This therefore seems to be related to the authentication flow from the iOS Homey app rather than the Panasonic credentials.