After Update to 2024.1.3 some Entities are not available any longer

[Friedi1970]

The problem

After I updated (yesterday) from core-2024.1.2 to core-2024.1.3 some of the ViCare entities are not available any longer. Even a reload doesn't help.
The following entities are not available:

• binary_sensor.vicare_burner_active
• sensor.vicare_burner_modulation
• sensor.vicare_burner_hours
• sensor.vicare_burner_starts
• sensor.vicare_boiler_temperature

Before everything worked well.

What version of Home Assistant Core has the issue?

core-2024.1.3

What was the last working version of Home Assistant Core?

core-2024.1.2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Viessmann ViCare

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Unfortunately not :(

Additional information

No response

[home-assistant]

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)}}

[CFenner]

Please note that there is a mayor api outage which is unfortunately not propagated in the ha integration.

[petervandersman]

Good morning,
Exact same problem here :(
Hope this can be resolved soon as I’m actively using the observations to remotely estimate the gas consumption and then (manually for now) optimize the operational settings.
Kind regards, Peter

[WolfgangSauer]

Same for me. Issue started after upgrading to 2024.1.3. But a rollback to 2024.1.2 has not helped. I also tried to activate the integration on a second HA instance -> same issue. Seems like a Viessmann problem.

Wolfgang

[petione]

I also confirm

[Ukey89]

After delete all information still won't work, and now can't finde my device.

[CFenner]

Did you also remove the .storage/vicare.token file?

We can also continue the discussion on Discord.

[Jordan87]

I tried to delete /config/.storage/vicare_token.save file but same issue still after update to 2024.1.3 (this file is missing each time i stop ViCare integration)

[Friedi1970]

I tried to delete /config/.storage/vicare_token.save file but same issue still after update to 2024.1.3 (this file is missing each time i stop ViCare integration)

Forget this! It isn't the integration but the Viessmann API. Mind the answer of CFenner: #107940 (comment)

[CFenner]

See #107847 (comment) for issue root cause and workaround.

[WolfgangSauer]

It's working now. Big thanks!

[Ukey89]

How did You delete config/.storage/vicare_token.save? Im new in HA

[WolfgangSauer]

I did not delete the file but used the command which @CFenner published two lines above this entry. Change to the /config directory with the "cd /config" command prior running the above command.

[ggliniak]

How did You delete config/.storage/vicare_token.save? Im new in HA

Normally this file gets automatically purged when deinstalling the integration.
If you really need or want to purge it, because it is a zombie file, install the "Terminal & SSH" Add-On and do:

[core-ssh ~]$ rm config/.storage/vicare_token.save

And yes, to run the workaround mentioned in #107847 (comment) you need to change first from root directory into /config in your Terminal.

[Friedi1970]

See #107847 (comment) for issue root cause and workaround.

Thanks @CFenner for the workaround 🙏 It works well for me!

[CFenner]

Feel free to share feedback on the PR if you have issues.

[Ukey89]

Thx, works well!

[pisolofin]

Feel free to share feedback on the PR if you have issues.

Thanks :)

[gt026328]

Hi;
with the update of HA to version 2024.1.6 I thought that the missing device bug is solved?
I'm still facing this issue after updating. Have I missed any "new setting" topics? or do I have to delete my integration an begin from scratch again? Or is this still open?
appreciate for calrification
Thanks
Tom

[gt026328]

[Friedi1970]

Well, it seems that the updates haven‘t been approved.
Btw. did you read anything about Vicare within the change log of the current HA version? I didn’t 🤷‍♂️

[gt026328]

Well, it seems that the updates haven‘t been approved. Btw. did you read anything about Vicare within the change log of the current HA version? I didn’t 🤷‍♂️

Well, in the Release Notes of 2024.1.6 I found this line
Fix entity naming for heatpump heatings in ViCare (@CFenner - #109013)
I did not check the Issue #109013 . From the wording my guess was that this will fix the unavailable of sensors

[CFenner]

With #106477 the Gateways Heatbox 1 & 2 aka Vitoconnect Opto1 & 2 are ignored by the integration, though the real heating device should be used instead. Can you confirm that you have issues with this gateway or is there another gateway that has this issues?

[Mercury0802]

Hello,
on my integration, the correct heatdevice is used. But even after updating to 2024.1.6, i'm also still missing some entities.
In my case, a heat pump, its compressor status, running time and buffer temperature. In the earlier integration they were named sensor.cu401b_g_compressor_hours, sensor.cu401b_g_compressor_starts sensor.cu401b_g_buffer_main_temperature and sensor.cu401b_g_buffer_top_temperature

These entities are not that important to me, but if you have a toggling heat pump they are very useful to start an analysis of the problem.
Would be great to get them again :)

best regards

[gt026328]

With #106477 the Gateways Heatbox 1 & 2 aka Vitoconnect Opto1 & 2 are ignored by the integration, though the real heating device should be used instead. Can you confirm that you have issues with this gateway or is there another gateway that has this issues?

Well I'm connecting to my gas heating box via a OPTP2. There is nothing in between. Heating box - Opto2 - Internet.

[gt026328]

With #106477 the Gateways Heatbox 1 & 2 aka Vitoconnect Opto1 & 2 are ignored by the integration, though the real heating device should be used instead. Can you confirm that you have issues with this gateway or is there another gateway that has this issues?

Well I'm connecting to my gas heating box via a OPTP2. There is nothing in between. Heating box - Opto2 - Internet.

Hey, thanks very, very much. With the update of HA to Version 2024.02 your Bug fixing have brought back the missing Entities. Al is working fine now
Again thank you very much
Cheers
Tom

[Mercury0802]

Same here :) Thanks!

[CFenner]

@home-assistant close