Fix compatibility with aioaquarea 1.0.2+ (new authentication)

[maddandy]

markdown

Summary

This PR fixes the integration to work with the latest aioaquarea library (main branch) which includes the new Panasonic authentication mechanism.

Panasonic changed their authentication system in May 2025, breaking the existing integration. The aioaquarea library has been updated to support this new auth flow, but the API has some breaking changes that this PR addresses.

Changes

manifest.json

• Updated dependency to use aioaquarea from git main branch (includes auth fix)

init.py

• Removed include_long_id=True parameter from get_devices() call (no longer supported)
• Changed device.name to device.device_name
• Changed device.version to device.firmware_version

sensor.py

• Changed device.name to device.device_name (3 occurrences)

Related Issues

Fixes #139 (Aquarea Smart Cloud no more accessible via web - Integration isn't currently working)

Testing

• Tested login with Panasonic Comfort Cloud credentials
• Verified device discovery works
• Confirmed all sensors populate correctly (temperatures, consumption, etc.)
• Confirmed climate and water_heater entities work

Notes

Once aioaquarea publishes a new version to PyPI with the auth fix, the manifest.json should be updated to use a pinned version instead of the git reference.

[hoschiking]

do you think, the code will be update for this improvement?
the last version is from 04.2024 !!!
There i another wax to integrate this fix to the addon?
I am not able to control the HP :-(

[maddandy]

@hoschiking I m not the owner of that repository… you can update the code with my branch in your home assistant plugin folder. That’s what I did to validate my work.

[hoschiking]

Yes of course, but I'm not able to do this.
Could you write a small step by step instruction for integration your code?
I think, a last of people had the same problem. This would help us :-)
A file manager I already installed in ha.
File editing is not a problem for me.
But where is the coffee to change?

[hoschiking]

The changes in sensor.py and init.py I allready done.
init.py doesnt exist, only init.py (whit underlines in the filename), I hope you mean this file.
But:
Updated dependency to use aioaquarea from git main branch (includes auth fix)
What I have to do for this?
Thank you so much for your support

[maddandy]

@hoschiking I think the easy way it's to add a custom repository in HA

And click on "Add".

The "new" version sould be available in HACS

You will be able to add a new integration, like usual but select the "Patched" version

[hoschiking]

It works !!!! Thank you !!!! :-)
Have a nice weekend :-)

[pzdpro]

Hi!
is there any issue with loging here?
i use my login and pass in app and on the website https://accountglb.digital.panasonic.com/social and it works correctly while using phone network.
When i use local network an ios app connot sign in getting error "The request is blocked"
Using yours integration in HA it shows incorrect login or password.

is that mean that they blocked my local IP or something?

[maddandy]

@pzdpro , It's seems weird ...
from my side, the iOS app and the website are working, I tested with my local network and the mobile network.
I created a second account for HA , the "main" account is used for the iOS app and the second one for HA, did you tried that approach ?

[pzdpro]

I tried but still not working. It was working fine form few months and it stops while ago.

[A-Caesar-B]

I tried but still not working. It was working fine form few months and it stops while ago.

I can confirm it, no possible to connect from HA (error 403), changing my IP address on phone (over VPN), it started to work. After few hours, from mobile again with my regular IP public address, it worked again. Starting HA --> block error 403 again...

T.

[maddandy]

I think I found the root cause of the 403 errors and created a fix.

The Problem

The default polling intervals are way too aggressive:

• DEFAULT_SCAN_INTERVAL_SECONDS = 10 → 360 API calls/hour
• CONSUMPTION_REFRESH_INTERVAL = 1 minute

This triggers Panasonic's rate limiting/IP blocking very quickly, especially
after the May 2025 authentication changes.

Also, the Aquarea Smart Cloud API doesn't refresh data that frequently anyway,
so polling every 10 seconds is pointless and just hammers their servers.

My Fix

I forked the repo and changed the intervals to more reasonable values:

DEFAULT_SCAN_INTERVAL_SECONDS = 120 # 2 minutes instead of 10 seconds
CONSUMPTION_REFRESH_INTERVAL = 2 # 2 minutes instead of 1 minute

This reduces API calls from 360/hour to 30/hour (12x reduction).

How to Install

1. Remove the old integration first:
   • Go to Settings → Devices & Services → Aquarea
   • Click the 3 dots → Delete
   • Restart Home Assistant
2. Install my fork via HACS:
   • HACS → Integrations → 3 dots menu → Custom repositories
   • Add: https://github.com/maddandy/home-assistant-aquarea
   • Category: Integration
   • Download and restart Home Assistant
3. Add the integration back with your credentials

Important: Use a Separate Account!

Create a second Panasonic account for Home Assistant. Don't use the same
account as your iOS/Android Aquarea app.
Why? If you use the same account on multiple devices/IPs with different polling
patterns, Panasonic may flag it as suspicious activity and block you faster.
To create a second account:

• Go to Aquarea Smart Cloud website
• Register a new account with a different email
• In the app, invite this new account to your device (share access)
• Use this secondary account in Home Assistant

---

Let me know if this helps resolve the 403 errors!

[pzdpro]

Still not working for me.
I checked few options:

Mobile phone, HA APP, local wifi: i get info "already_in_progress"
Mobile phone, HA APP, Mobile network: i get info "already_in_progress"
Mobile phone, web browser, local wifi: i get info "already_in_progress"
Windows, web browser, local network: i get info "already_in_progress"
Windows, HA APP, mobile network: i get info "invalid user or password"
Windows, HA APP, local network: i get info "invalid user or password"

I dont use original comfort cloud app. I just logged in and logout yesterday just to try is it work (it works fine). Should i create a new account anyway even if i used it only for HA in the past?

[maddandy]

I guess it's not mandatory in your case... the purpose it's to avoid multiple connection for the same user but with ip and/or different device . I guess there is a threshold in their side with that criteria.

What do you means with "Mobile phone, HA APP, local wifi or mobile network", Home Assistant is connected into your network with his own connection (wifi or rj45), the plugin used the physical connection where home assistant is installed (docker, linux, dedicated box, and so on ... not your mobile. Your mobile is just a client to the Home Assistant.

[pzdpro]

I just tried different options an i supossed that will not changed anything if i use mobile network or home wifi.
Yes. The system is installed and running as VM on my own server and this has his own LAN Card and direct connection via RJ45 to the home router.

[lczarnec693]

I just tried different options an i supossed that will not changed anything if i use mobile network or home wifi. Yes. The system is installed and running as VM on my own server and this has his own LAN Card and direct connection via RJ45 to the home router.

I have same issue...

[Marcjulcar]

Hi,
I'm trying to add the (patched" repository but doesn't seem to work. It says that already exists in the store but I only see the "normal" version, not the "(Patched)" or "(Fork)" one... What should I do?

Thanks a lot!

[maddandy]

Hi, I'm trying to add the (patched" repository but doesn't seem to work. It says that already exists in the store but I only see the "normal" version, not the "(Patched)" or "(Fork)" one... What should I do?

Thanks a lot!

did you tried to restart home assistant ? what do you see in the HACS ?

[Marcjulcar]

Now it appeared! Matter of waiting some time I guess.
However, now it says "Failed to setup" after adding the integration and signin in, and i don't see how to check the logs...

[maddandy]

Now it appeared! Matter of waiting some time I guess. However, now it says "Failed to setup" after adding the integration and signin in, and i don't see how to check the logs...

You can check your logs here : https://my.home-assistant.io/redirect/logs/

[sebastianciupinski]

@maddandy - please enable issues in your fork, now it is not possible to raise issues there

[devboyz089]

x-app-version should be bumped to 4.0.0 (it was 3.1.1 for me before, new app version came out and the integration couldn't start (401)).
after the version bump, its working