Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Faulty setup of multiple heat pumps #292

Open
Guzz-T opened this issue Nov 1, 2024 · 7 comments · May be fixed by #301
Open

Faulty setup of multiple heat pumps #292

Guzz-T opened this issue Nov 1, 2024 · 7 comments · May be fixed by #301
Labels
help wanted Extra attention is needed question Further information is requested wontfix This will not be worked on

Comments

@Guzz-T
Copy link

Guzz-T commented Nov 1, 2024

The setup of several heat pumps found is not yet working properly. The devices per hub are created incorrectly and the entities are not assigned correctly. The entities of the two heat pumps are assigned to the same device.

Environment:
Home-Assistant 2024.10.4
Luxtronik 2024.10.5-Beta
Heatpump 1 (Master): xxx-0512
Heatpump 2 (Slave): xxx-013

image

Heatpump 1 Devices:
image

Heatpump 2 Devices:
image

Heatpump 1 WP-Device:
image

@BenPru
Copy link
Owner

BenPru commented Nov 15, 2024

Please provide a diag file. See documentation howto do this.
Please have a look at the entity ids. They should contain the serial number of the hp. If not and the ids are only .luxtronik2_ your installation is broken and you have to remove the devices and re create them.
BUT VERY IMPORTANT: You will lose your sensor history and all links to them (dashboards, scripts, automations and so on)!

@BenPru BenPru added help wanted Extra attention is needed question Further information is requested wontfix This will not be worked on labels Nov 15, 2024
@Guzz-T
Copy link
Author

Guzz-T commented Nov 16, 2024

The entities are OK. however, both the .luxtronik2_xxx_0512 and the .luxtronik2_xxx_013 entities are displayed under the same device.

[Update]:
It is not possible for me to download diagnostic data. Neither with “edge”, “safari” nor with “brave”.
With other integrations the download is possible without any problems.

Have found and solved the problem.

@BenPru
Copy link
Owner

BenPru commented Nov 16, 2024

@Guzz-T Strange...
Please have a look into the two file .storage/core.config_entries and .storage/core.device_registry.
Check the luxtronik ids are correct linked. If not you can backup the files, shutdown ha and correct it manually.
Alternative attach the files in the issue.

@Guzz-T
Copy link
Author

Guzz-T commented Nov 16, 2024

Here are the (shortened) files:

core.config_entries.json
core.device_registry.json
core.entry_registry.json

@Guzz-T
Copy link
Author

Guzz-T commented Nov 16, 2024

I assume:

  • core.config_entries is correct
  • in core.device_registry:
    • config_entries should only contain one entry
    • in xxx_013_heating primary_config_entry is wrong
  • in core.entry_registry:
    • in luxtronik_xxx_013_outdoor_temperature device_id is wrong

Please note that I have tried the setup several times and each time it did not work properly.

[Update]:
It seems that the manual changes in the files are overwritten again by HA

@Guzz-T
Copy link
Author

Guzz-T commented Nov 16, 2024

I have now managed to create the diag files:
config_entry-luxtronik2-01JBFDSPEZEJB9ZMNGZBBZA0VQ.json
config_entry-luxtronik2-01JBFDD1J31QPAYDNZ1SJMGKNR.json

Please note that i am using the latest version of Bouni/python-luxtronik commit ceed16e5486e689e06fe88f3e908cdcc21f37dfe. However, I think that this has no influence on the setup of the HA components.

@Guzz-T
Copy link
Author

Guzz-T commented Nov 16, 2024

Here is the debug protocol of the setup:
debug_protocol.txt

I guess:

[Update]
With the changes mentioned, it seems to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants