Problem mit 2 Hub Instanzen

[dajupp]

Hallo,
ich möchte 2 Heizungen anbinden. Ich kann auch die zweite Heizung normal hinzufügen, benennen etc. Alles funktioniert.

wenn ich mit 2 Hubs konfiguriert einen Neustart von HA mache werden die Entitäten von beiden Hubs unter einem Hub "vermischt". Problem ist das dann nur noch die Entitäten der zuletzt hinzugefügten Instanz funktionieren.
Ich weiß nicht wie ich das Problem genauer beschreiben soll. Hier ein Screenshot nach einem HA Neustart.

[rhammen]

Please go to the hub, press the 3 dots, and choose Download diagnostics.
Post the file in this thread.

[dajupp]

See attached files below

config_entry-luxtronik2-01KGJFN3PM04EGAV0BYXD0BH7C.json
config_entry-luxtronik2-01KGC7XQ7QGKJJK7G7GZ84GASC.json

[fallingcats]

Can confirm, I've got the same problem. Even worse, sometimes an entity for one device receives a stray value from the other (which look like outliers in in an otherwise smooth temperature graph for example).

[rhammen]

Can you try to manually install fix-2-hubs-mixup-issue
ALternatively: you only need to replace the current coordinator.py file with this one
NOTE:
Please make a backup-first,
then update the coordinator,py file,
then delete the existing luxtronik2 devices. (Important: Using the changed file without deleting the old devices will likely result in the old devices remaining present under the hubs, so you likely will want to avoid that..... !)
Then restart.

Let me know if that solves the issue or not.

[fallingcats]

Wow, that was quick!

The fix looks good to me so far (even kept entity_id stable preserving history, which is nice). I'll report back if I encounter any related issues.

What I did notice is auto discovery doesn't happen anymore (at all?). Not good, but certainly better than the old one that forcefully discovered and enabled everything only seconds after they were manually deleted. Discovery should probably go through home assistant's normal mechanism for presenting auto discovered devices.

[dajupp]

Looks great, everything is still working after a Home Assistant restart.

[fallingcats]

I'm sorry to say, the mixing up of values between equivalent entities of different heat pumps still happens:

It's not only operation hours, those are just the easiest to demonstrate the issue.
Should I open different issue for that?

[rhammen]

I'm sorry to say, the mixing up of values between equivalent entities of different heat pumps still happens:

It's not only operation hours, those are just the easiest to demonstrate the issue. Should I open different issue for that?

It is fine to keep discussion in this issue.
Did you maybe change any settings on the heatpump from within HA just before these mix-ups occurred?

[rhammen]

Wow, that was quick!

The fix looks good to me so far (even kept entity_id stable preserving history, which is nice). I'll report back if I encounter any related issues.

What I did notice is auto discovery doesn't happen anymore (at all?). Not good, but certainly better than the old one that forcefully discovered and enabled everything only seconds after they were manually deleted. Discovery should probably go through home assistant's normal mechanism for presenting auto discovered devices.

Thanks, also to @dajupp, for confirming the fix works!
The challenge is that if I integrate the fix as is, it will create new devices for all users, without removing the old ones... :-(
I need to see if I can find a solution for that...

[fallingcats]

It is fine to keep discussion in this issue. Did you maybe change any settings on the heatpump from within HA just before these mix-ups occurred?

I enabled/disabled a couple off different entities related to the heatpumps, but I doubt that's the only reason, because this has happened multiple times a day (and at night too). Usually it's coincided with a heat pump starting or just running, when many entities are getting updated at once. This time it happened exactly when the one marked (MSW 10) was starting up for Heating.

Some kind of race condition probably?