core ViCare shows same device twice since upgrade to 2024.10

The problem

i have a Viessmann heating system which is integrated into HA via the ViCare Integration. This was working fine for over 1 year now but after the HA update to 2024.10 the integration shows 2 devices: the original one (which is used in all automations, dashboards,...) and the same device but with new ID. all entities from the "old" device are shown as "unavailable", the "new" device is working correctly. I am not able to delete one of the 2 devices. All my automations, dashboard views,... referring to the heating device are not working anymore since they are referring "unavailable" entities.

What version of Home Assistant Core has the issue?

2024.10.0

What was the last working version of Home Assistant Core?

2024.9.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Viessmann ViCare

Link to integration documentation on our website

https://www.home-assistant.io/integrations/vicare

Diagnostics information

config_entry-vicare-d5e6b42b2d1c5921b56341075c2fcc95.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

Oct 04 '24 11:10 filewalker1

Hey there @cfenner, mind taking a look at this issue as it has been labeled with an integration (vicare) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of vicare can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign vicare Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

vicare documentation vicare source _{^{(message by IssueLinks)}}

Oct 04 '24 11:10 home-assistant[bot]

Hey @filewalker1, can you share the logs, when the integration is loaded?

We migrated the entity and device IDs to prepare for the room sensors. Looks like this failed for you.. What kind of devices do you own?

Oct 04 '24 13:10 CFenner

Hi @CFenner, thanks for the quick response! i own a Vitodens 300 System (Gas Heater + Water Storage). How do i get the log files for you? i tried activating debug logging in the integration and restartet HA. This is what i got (deleted lines not related to vicare).

home-assistant_vicare_2024-10-04T14-07-12.611Z.log

Oct 04 '24 14:10 filewalker1

I see Device does not offer a 'device.serial' data point in the logs. Could be related to the TCU not being recognized as a gateway (fixed with https://github.com/openviess/PyViCare/pull/412).

Can you lookup the new and old entity / device IDs?

Oct 04 '24 14:10 CFenner

you mean the HA device IDs? The original (now not working device): 35c1dd5f82f5854bbe2070767ab04f36, the new one: 148ff0022c2e17db3877edb0bb81c47f

Oct 04 '24 14:10 filewalker1

@CFenner can i do something to help you or try something for you? Thanks for helping here :)

Oct 11 '24 08:10 filewalker1

the problem still persists in HA2024.11. I now have my heating system twice, the old device with the history but no new data and a new device with the new data. i am not able to delete the old device as the integration always reports two identical heating systems. Is there somethin i can do? Even if i swithc to the new device all my historical data is lost. is there a way to transfer the historical data to the new device?

Nov 23 '24 11:11 filewalker1

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Feb 21 '25 12:02 issue-triage-workflows[bot]

still open and not fixed

Feb 23 '25 11:02 filewalker1

any update on this? problem still persists on latest HA Version

Apr 25 '25 06:04 filewalker1

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Jul 25 '25 13:07 issue-triage-workflows[bot]

still an issue with latest HA version

Jul 25 '25 18:07 filewalker1

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Oct 23 '25 19:10 issue-triage-workflows[bot]