Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot access hot water temperature #84875

Closed
philipp-kuttner opened this issue Dec 30, 2022 · 14 comments
Closed

Cannot access hot water temperature #84875

philipp-kuttner opened this issue Dec 30, 2022 · 14 comments

Comments

@philipp-kuttner
Copy link

The problem

I‘m unable to get the value of the water temperature.
The entity water_heater.vicare_water delivers the state AND the value, but I cannot access only the value.

What version of Home Assistant Core has the issue?

core-2022.11.5

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

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?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @oischinger, 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 Change the title of 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.

(message by CodeOwnersMention)


vicare documentation
vicare source
(message by IssueLinks)

@oischinger
Copy link
Contributor

This should be fixed with #84720
can you please check with 2023.01 (yet to be released as stable)

@philipp-kuttner
Copy link
Author

philipp-kuttner commented Feb 6, 2023

Hi @oischinger.
I updated today to 2023.2.2, but I cannot access to this data.
Do you have any other tips for a solution?

P.S.
I used this entity:
water_heater.vicare_water
But this entity only returns for example "on", not the water temperature.

@rolandsteinmeyer
Copy link

rolandsteinmeyer commented Feb 19, 2023

I have this in water_heater.vicare_water_0 attributes:

min_temp: 10
max_temp: 60
current_temperature: 48.3
temperature: null
target_temp_high: null
target_temp_low: null
friendly_name: ViCare Water 0
supported_features: 1

current_temperature is ok. target temperature should be in attribute "temperature" but is "null". I can sucessfully set new target temperature with service "water_heater.set_temperature". It just doesn't show in "temperature".
I am not sure, but I think this has worked a few days before. Viessmann may have changed something in the API, there was a service downtimes some days ago.

@oischinger
Copy link
Contributor

@philipp-kuttner
You would need to create a template sensor to have a dedicated attribute for the water temp. See https://www.home-assistant.io/integrations/template/

Concerning what @rolandsteinmeyer mentioned: There's currently an issue on PyVicare which was used to report a breaking change: openviess/PyViCare#285
But so far I wasn't aware that the water temperature attribute is affected by this.

@rolandsteinmeyer you can upload the diagnostic data then we can check

@rolandsteinmeyer
Copy link

temperature is back today in water_heater. I had some 'EXPIRED TOKEN' errors in the log, it might have sorted itsself out in subsequent requests. Log attached.

PyViCare.PyViCareUtils.PyViCareInternalServerError: (PyViCareInternalServerError(...), 'Request failed with status code 502 and message "INTERNAL_SERVER_ERROR".
vicare-ha.log

@gras55
Copy link

gras55 commented Mar 20, 2023

Am still not able to turn on DHW on the E3 platform

@garagenlager
Copy link

garagenlager commented Apr 3, 2023

Hi, is this issue still pending?
I´m trying to use the water temperature as a separate sensor, but my template sensors returns the numeric value with question marks.
code:

  • name: 'Brauchwassertemperatur'
    unit_of_measurement: '°C'
    device_class: temperature
    state: “{{ state_attr('water_heater.vicare_water', 'current_temperature') }}”

Result: “51.6”
This non-numeric value cannot be used as statistical data.
Tested the same with the climate.vicare_heating and current temperature: The temperature is also returned as string value with question tags.

@ja-m
Copy link

ja-m commented Apr 9, 2023

@garagenlager Thanks for your code. This helps me a lot. And I fix the problem with the string value.
state: "{{ state_attr('water_heater.vicare_water_1', 'current_temperature') | replace('“', '') | float }}"

@garagenlager
Copy link

@ja-m Thanks for your help. Nevertheless, I´m still getting the string value back as result with question tags. The replace order is not executed for some strange reason. It seems that the question tags around the expression "{{....}} cause the problem. If I delete these, the yaml file is not acceted due to syntax error.

@garagenlager
Copy link

Hi, just to present the working solution now:

  • name: "Brauchwassertemperatur"
    unique_id: "Brauchwassertemperatur"
    unit_of_measurement: °C
    device_class: temperature
    state_class: measurement
    state: "{{ state_attr('water_heater.vicare_water', 'current_temperature') }}"

It seems that the sate class measurement was missing.

@issue-triage-workflows
Copy link

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.

@garagenlager
Copy link

problem solved

@philipp-kuttner
Copy link
Author

Solved, thanks!

@github-actions github-actions bot locked and limited conversation to collaborators Aug 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants