-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
Integration ViCare: selected source ist "heatpump" but comsumption is shown in "gas" ?? #102995
Comments
In #99468 (comment) some uses report about the same behavior. |
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. |
Hi, Hi, Hoffe es hilft.... |
As the sensors that were used for gas heatings are now used for heat pumps and others, I think it's nevertheless important to correct the naming. I opened a PR to do so. Feel free to verify & suggest changes. |
The problem
Hi,
I am not sure about if this is a real issue or just cosmetic, but whatever type of heating source I choose (auto/heatpump), the result is that the entities are shown as consumption of "gas"?? Maybe this can be fixed by changing from gas to energy in total, or the source type heatpump should trigger that the entities are named kWh instead of gas.
I know that I can rename them but this is realy the very last option I would expect.
I also know that the integration realized that it is an heatpump because of the compressor information.
The value of the data itself seems to be fine.
Thomas
What version of Home Assistant Core has the issue?
core-2023.10.5 and older versions
What was the last working version of Home Assistant Core?
never
What type of installation are you running?
Home Assistant OS
Integration causing the issue
integration: vicare
Link to integration documentation on our website
https://www.home-assistant.io/integrations/vicare
Diagnostics information
{
snip==>
"integration_manifest": {
"domain": "vicare",
"name": "Viessmann ViCare",
"codeowners": [],
"config_flow": true,
"dhcp": [
{
"macaddress": "B87424*"
}
],
"documentation": "https://www.home-assistant.io/integrations/vicare",
"iot_class": "cloud_polling",
"loggers": [
"PyViCare"
],
"requirements": [
"PyViCare==2.25.0"
],
"is_built_in": true
},
"data": {
"entry": {
"entry_id": "5d624eb05e2dcbb5eb40f615d7e8818b",
"version": 1,
"domain": "vicare",
"title": "ViCare",
"data": {
"username": "REDACTED",
"password": "REDACTED",
"client_id": "REDACTED",
"heating_type": "heatpump"
},
==> snap
Example YAML snippet
Thert is no vicare.yaml accept for the vicar token :-)
Anything in the logs that might be useful for us?
Additional information
The text was updated successfully, but these errors were encountered: