Panasonic Aquarea Heat Pump integration

cjaliaga · September 17, 2022, 4:53pm

Sorry @XiteKnight I missed your message. Correct, this is the repo link

I’ll try to get the repo on the default HACS list so there’s not even need of adding the repo URL to find the integration. I was waiting on having the logos added before doing that but since that’s taking a lot to get reviewed, I may do it now.

cjaliaga · September 17, 2022, 5:00pm

Hi,

Thanks a lot @muppeth. I’m with you and I try to remove external clouds as much as possible. There’s a project where you can build your own device that replaces the Panasonic device to connect to their cloud and use it locally: GitHub - Egyras/HeishaMon: Panasonic Aquarea air-water H and J series protocol decrypt

However, I decided to not go via this path for my heat pump and use the Panasonic server. These devices are expensive and for the time being I prefer to have Panasonic as a control plane for all the commands. That said, I’d also like to have direct control without their cloud, maybe I’ll try that path in the future.

kommis · September 18, 2022, 7:35am

Hello Carlos,

Thanks for your Integration! It works fine!
Do you know the service cloud? There are much more Informations. It would be very nice if you are able to set up also an Integration for the Service cloud. Then you have all data from the heatpump or aircondition!

An important value are:

return temperature
flow temperature
operating mode
etc.

Link: https://aquarea-service.panasonic.com/

Best regards and thanks again for your excellent Integration!
Dominik

Mavo · September 18, 2022, 9:23am

Hi Carlos, thanks for the great integration, when I run this integration, i get in Home assistant log following error:

Is there something I missed?

Marian

cjaliaga · September 18, 2022, 9:34pm

Thanks @kommis!

Yes I’ve looked at the service account and I have to say that API is a pain in the *** to say something

That said, the main goal of the integration is to work as much as possible with aquarea smart as it’s what most people uses, the service one is for installers, even if we can register ourselves as installers (as we both have done ).

We can study the possibilities in the future, either with a complementary integration or trying to extend this one in a way that makes sense.

Most or these values can be obtained with aquarea smart, however, as you said, some of them are things that, from my investigations, I only found possible using the service account: like the pump flow or the possibility of fully restarting the device when there’s an error

cjaliaga · September 18, 2022, 9:36pm

Hello @Mavo,

I think this is the last type of zone sensor (Thermistor) that I’m missing on the integration. Let me add it and publish a new version of the integration that supports it.

I’ll write you when it’s published so you can test it out and let me know if everything works as expected for you.

Thanks!
Carlos

cjaliaga · September 18, 2022, 11:30pm

@Mavo Release v0.1.6 · cjaliaga/home-assistant-aquarea · GitHub is published and should appear shortly on HACS.

Please let me know if everything works as expected with your configuration.

Thanks!
Carlos

kommis · September 19, 2022, 7:37am

Thanks for your answer. I think you need the return temperature and flow temperature for your house temperature. Because you need to know how warm/cold is your temperature.

Is that possible from the smart cloud? Because I dont see this attributes in the smart cloud. I see only the flow temperature.

best regards

Mavo · September 19, 2022, 6:33pm

Great job Carlos, new version is working. Thank you for quick response and new version!

I have another issue with this integration. I have heat pump with 2 zones:

1.st is named as ‘podlahovka’ (= floor heating)
2nd is ‘radiator’

In home assistant I see only entity ID climate.majco_podlahovka, second zone is missing (look at next post).

I don’t know if it’s related with this error in HA log:

Logger: homeassistant.components.climate
Source: helpers/entity_platform.py:520
Integration: Klimatizácia (documentation, issues)
First occurred: 20:14:26 (2 occurrences)
Last logged: 20:20:26

Platform aquarea does not generate unique IDs. ID None_heatpump already exists - ignoring climate.majco_podlahovka

What do you think?

Marian

Mavo · September 19, 2022, 6:36pm

I can’t add more than 1 image in one post, this is what I see under integration:

cjaliaga · September 20, 2022, 4:41pm

Thanks a lot @Mavo, we couldn’t test the integration with 2 zones yet. This is really helpful!

Could you please do me a favor and open an issue on the GitHub repo Sign in to GitHub · GitHub with all these details? I’ll track it there and work on it as soon as possible.

Mavo · September 20, 2022, 6:11pm

Sure, no problem, already opened
Thanks

Krasimir_Stanev · September 20, 2022, 7:16pm

Thanks a lot Carlos,

After waiting for so long I have tested the integration and it worked. Finally I can almost ditch the crappy panasonic app and use HA, great job!

If I have to set priorities in the further development for this will be:

Energy sensors - Heating, cooling and tank consumption, heating, cooling and tank generation and heating, cooling and tank COP
Direct control without cloud
3 . Second zone support
Buffer tank sensor and 3 way vavle position
Backup electrical heater amd sterilization status
Hydrobox inlet and outler temperature
All other sensors

I have the bellow setup, if anything has to be tested let me know!

Greay job!

Krasimir_Stanev · September 20, 2022, 7:30pm

2 things that I noticed -

The tank temperature statistics shows the set temperature’s graph instead of the current temperature. This is why the graph stays always on 53 which makes no sense.
On the thermostat card in the modes you have Heat/Cool which is confusing and should be called Auto as it is in the Aquarea.

cjaliaga · September 20, 2022, 8:22pm

Thanks!

I think I’ve found the problem. There’s an issue in the entity unique_id generation in the integration. This ID is an internal Home Assistant id, is not the one that we normally use, like light.kitchen. I’ll fix that in the new release. These are the good news.

Now with the possible bad news. The unique id will be now properly defined. However, the consequence of that is for home assistant they will be new entities. This is something that needs to be done to fix this issue and to avoid other issues in the future.

Here we have 2 possibilities:

I’m able to migrate the unique_ids, which will mean few to none visible changes.
I’m not able to migrate the unique_ids, so it will generate the right ids on startup and if the integration was already installed, new entities will appear.

Let’s see an example of option 2:

climate.mydevice_myzone is already created
a new entity will appear with climate.mydevice_myzone_2.
climate.mydevice_myzone will need to be manually deleted
climate.mydevice_myzone_2 should be renamed back to climate.mydevice_myzone

I don’t like the consequences of possibility 2 and I do apologize for that. I’ll see what I can do here. I’ll let you know.

shajek · September 21, 2022, 8:32am

For option 2, is only onetime thing, right ?
Then for me, is no problem, integration is 0.16 version

If we delete integration and then re-add it will correctly create unique ids

cjaliaga · September 21, 2022, 3:32pm

Yes, it would be a onetime thing, just the first time you update to something > 0.1.6. Deleting and recreating would do exactly that, yes.

Being honest, doing it that way saves me some time that I can spend on adding more features (and unfortunately time is limited)

Mavo · September 21, 2022, 4:20pm

I agree with @shajek, recreation integration is absolute not a problem
@cjaliaga, you really don’t need to waste your time finding solution for this IMHO

cjaliaga · September 21, 2022, 5:04pm

I’ll do it this way then. I’ll add a breaking change message on the change log

cjaliaga · September 24, 2022, 11:14pm

I published v0.2.0 with the breaking change and support for multiple zones. @Mavo please let me know when you have time of checking it if everything works as expected for you.

Thanks!