home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.81k stars 30.51k forks source link

no water Temperatur water_heater.vicare_water #96895

Closed gregorwolf1973 closed 9 months ago

gregorwolf1973 commented 1 year ago

The problem

I have vicare working sins many month. Lately I added a heat pump (Vitocal 250-SH HAWB-M-AC 252.B10) to my gas boiler (Vitodens 200 W). Vicare app is working fine.

I have all data but the water_heater.vicare_water shows no data. There is no water temperature, I can't turn on or off the heating etc. My heat pump is recognised as VScotHO1_200_11

Following information are available image

I have restartet several times and also reinstalled the vicare adon many times. Any one knows help?

What version of Home Assistant Core has the issue?

core-2023.6.3

What was the last working version of Home Assistant Core?

core-2023.6.3

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

vicare documentation vicare source

gregorwolf1973 commented 1 year ago

As you can see here, the "vicare water aktuelle Temperatur" and "vicare water Zieltemperatur" is missing. Why? image

gregorwolf1973 commented 1 year ago

vicare documentation vicare source

I have ready, but there is No Help to find according this issue

drozdzszymon commented 1 year ago

Similar problem: Vicare app is working fine.

Home Assistant 2023.8.3: E3_Vitodens_100_BHC_0421 image

TheSmartGerman commented 1 year ago

I also struggle with this. As far as I'm unterstood the problem. the vicare_water is no sensor. It's a heater type. I'm also not able to use it with a sensor card. if you open the entity and lock at the graph you have 2 values like: https://github.com/home-assistant/core/issues/96895#issuecomment-1647341990

How can I use this data in lovelace cards?

modem-man-gmx commented 1 year ago

the vicare_water is no sensor. It's a heater type. I'm also not able to use it with a sensor card. How can I use this data in lovelace cards?

Same question here. would like to use a large temperature gauge card to show up the current water temp, before we fill the bathtub. Everybody has the value as an attribute in water_heater.vicare_water object. But nobody telling me how to convert it to a temperature. :-(

Did YOU already found a way?

modem-man-gmx commented 1 year ago

I also struggle with this. I'm also not able to use it with a sensor card. > How can I use this data in lovelace cards?

Found the way in the meantime.

Step 1:

enter the 'climate.vicare_heating' here under Entities, then note all attribute of interest:

image

Step 2:

go to Helpers and add one of the "{} Template" type sensor (not binary!):

image

and fill the fields like here:

image

some working state templates for Vitodens Gas in 10/2023 are: ` {{ state_attr('water_heater.vicare_water', 'current_temperature') | replace('“', '') | float }}

{{ state_attr('climate.vicare_heating', 'room_temperature') | replace('“', '') | float }}

{{ state_attr('climate.vicare_heating', 'current_temperature') | replace('“', '') | float }}

{{ state_attr('climate.vicare_heating', 'temperature') | replace('“', '') | float }}

{{ state_attr('climate.vicare_heating', 'active_vicare_mode') }}

{{ state_attr('climate.vicare_heating', 'active_vicare_program') }}

{{ state_attr('climate.vicare_heating', 'hvac_action') }} `

Step 3:

This is usable f.i. this way:

image

image

Hope this helps...

TheSmartGerman commented 1 year ago

ok perfekt!

this helps a lot. I just had a workaround to see the graph:

grafik

grafik

issue-triage-workflows[bot] commented 9 months ago

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.