Vicare Integration: Feature not supported

[asun777]

The problem

With my installed Home Assistant Core I get now messages from ViCare Integration Feature not supported home-assistant_vicare_2024-09-23T13-16-04.927Z.log

What version of Home Assistant Core has the issue?

2024.9.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ViCare

Link to integration documentation on our website

No response

Diagnostics information

home-assistant_vicare_2024-09-23T13-16-04.927Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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]

Hi @asun777, can you share your diagnostic information?

I can see in the log, that you have a Gateway E3_TCU10_x07 and a VitoCharge. It that correct/all?

Also I see that once HA tries to create entities for a device Gateway and once for a device HeatingDevice. You should set the device type in the config to auto.

When looking at the ViCare library, it seems that *VitoCharge could either be mapped to a FuelCell heating device or a ElectricalEnergySystem. What is the device you own?

Did it work for you in the past as expected?

[asun777]

Hello Christopher

Sorry for late answer I was on holidays

I have the following Components

VitoCharge VX3 8.0 A Communication Module / Gateway is integrated.

It is a ElectricalEnergySystem (Photovoltaic with Battery).

It worked good in the past after an upgrade to a new HA Version it stopped working.

Attached you will find the log regarding ViCare

How do I set the devece type in the config to auto.

---

From: Christopher Fenner @.> Sent: Monday, September 23, 2024 21:29 To: home-assistant/core @.> Cc: asun777 @.>; Mention @.> Subject: Re: [home-assistant/core] Vicare Integration: Feature not supported (Issue #126547)

Hi @asun777https://github.com/asun777, can you share your diagnostic information?

I can see in the log, that you have a Gateway E3_TCU10_x07 and a VitoCharge. It that correct/all?

Also I see that once HA tries to create entities for a device Gateway and once for a device HeatingDevice. You should set the device type in the config to auto.

When looking at the ViCare library, it seems that *VitoCharge could either be mapped to a FuelCell heating device or a ElectricalEnergySystem. What is the device you own?

Did it work for you in the past as expected?

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/126547#issuecomment-2369183997, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6EPJSPMIUH4GSSY6SX44TDZYBTZHAVCNFSM6AAAAABOWC5DKSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRZGE4DGOJZG4. You are receiving this because you were mentioned.

[issue-triage-workflows[bot]]

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.