Vicare integration not exposing room thermostat as a metric

[rvrignaud]

The problem

I have a room thermostat connected to my Vitocal. The room temperature is properly displayed in the vitocal card (current temperature)

I can see the graph if I click on the history button

However I can't see that metric for in my statistics graph cards. Is there any way to retrieve that metric ? I don't know if this is related to https://github.com/home-assistant/core/pull/125243 ? Is that PR included in 2024.10.0 ?

What version of Home Assistant Core has the issue?

core-2024.10.0

What was the last working version of Home Assistant Core?

none

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Vicare

Link to integration documentation on our website

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

Diagnostics information

config_entry-vicare-02171e0ff74ab236df7b9ac332d68fca.json

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]

I don't know if this is related to https://github.com/home-assistant/core/pull/125243 ? Is that PR included in 2024.10.0 ?

No, that will only be in 2024.11.0. With that change in place, you will have dedicated sensor entities for your ZIGBEE room sensors. Is that what you have?

You should be able to access the value as an attribute of your climate entity.

[rvrignaud]

I have a Vitotrol 300-E. I do have that attribute:

Is there a way to use that attribute in a statistic graph ?

[rvrignaud]

When creating a statistic card, the entity climate.e3_vitocal_heating_2 where the current_temperature is located doesn't show up in the statistic field:

[CFenner]

Is there a way to use that attribute in a statistic graph ?

At least you can create a template sensor for the attribute and use that.

[rvrignaud]

Any pointer on how to do that ? Any way to surface that metric more natively ?

btw, thanks a lot for the hard work on that integration !

[CFenner]

Just go to the helpers tab under devices & service and create a new template and *template for a sensor.

Do you have the room sensor connected via zigbee? Then it should show up with the next release (welcome to test upfront).

[rvrignaud]

The template sensor did the trick. Thank you @CFenner .

I have a Vitotrol 300-E, do you know if the Room Sensor PR will make it work ? If not any specific feature request I can create, because right know it really not trivial to use.

Thank you

[CFenner]

Hm.. looks like it's a different sensor that does not provide the data, unfortunately.

[rvrignaud]

I don't understand. The data I'm looking for is already accessible in e3_vitocal_heating_2.current_temperature. I just want a way to be able use that without using the template sensor workaroud

[marcjay]

@rvrignaud The Statistics Graph Card is for graphing the state of entities, not individual attributes. The state of a climate entity is not the current temperature. There are other graphing cards available that are more flexible, e.g. apex-charts. Otherwise, the workaround provided is sensible, not sure why it's an issue to use it?

[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.