Open x4N70pHyLL opened 1 week ago
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!
(message by CodeOwnersMention)
vicare documentation vicare source (message by IssueLinks)
Maya the same issue I have reported here a few minutes before: https://github.com/home-assistant/core/issues/130271
I have The Same Problem :/
I had the same issue, and then I tried to reload the integration and now all sensors are gone and I get an error in the log:
Logger: homeassistant.config_entries
Quelle: config_entries.py:635
Erstmals aufgetreten: 16:23:27 (1 Vorkommnisse)
Zuletzt protokolliert: 16:23:27
Error setting up entry ViCare for vicare
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/requests/models.py", line 974, in json
return complexjson.loads(self.text, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/simplejson/__init__.py", line 514, in loads
return _default_decoder.decode(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/simplejson/decoder.py", line 386, in decode
obj, end = self.raw_decode(s)
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/simplejson/decoder.py", line 416, in raw_decode
return self.scan_once(s, idx=_w(s, idx).end())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 635, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 48, in async_setup_entry
await hass.async_add_executor_job(setup_vicare_api, hass, entry)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 80, in setup_vicare_api
vicare_api = vicare_login(hass, entry.data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 69, in vicare_login
vicare_api.initWithCredentials(
File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCare.py", line 25, in initWithCredentials
self.initWithExternalOAuth(ViCareOAuthManager(
File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCare.py", line 30, in initWithExternalOAuth
self.__loadInstallations()
File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCare.py", line 41, in __loadInstallations
installations = self.oauth_manager.get(
^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/PyViCare/PyViCareAbstractOAuthManager.py", line 38, in get
response = self.__oauth.get(f"{API_BASE_URL}{url}", timeout=31).json()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/requests/models.py", line 978, in json
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
The app also doesn't work for me currently. So I'm guessing it might also be a Viessmann issue?
Edit: This issue seems to be fixed now and was probably independent.
Now that the the general integration works again, but I still don't get the energy values. This the log with debug logging enabled, maybe it helps someone?:
I have the same problem since the first of November: { "apiVersion": 1, "commands": {}, "deviceId": "0", "feature": "heating.power.consumption.heating", "gatewayId": "################", "isEnabled": true, "isReady": true, "properties": { "day": { "type": "array", "unit": "kilowattHour", "value": [ 0.2, 3.6, 3, 3.1, 15.9, 4.1, 3.8, 3.6 ] }, "dayValueReadAt": { "type": "string", "value": "2024-10-31T22:58:23.426Z" }, "month": { "type": "array", "unit": "kilowattHour", "value": [ 0.2, 163.5, 25.5, 0, 0, 0, 31.2, 23.9, 81.2, 0, 0, 0, 0 ] }, "monthValueReadAt": { "type": "string", "value": "2024-10-31T16:14:25.469Z" }, "week": { "type": "array", "unit": "kilowattHour", "value": [ 25.8, 40.6, 29.500000000000004, 36 ] }, "weekValueReadAt": { "type": "string", "value": "2024-10-31T22:58:23.426Z" }, "year": { "type": "array", "unit": "kilowattHour", "value": [ 408.20000000000005, 0 ] }, "yearValueReadAt": { "type": "string", "value": "2024-10-31T22:58:23.426Z" } }, "timestamp": "2024-11-10T17:10:50.828Z", "uri": "https://api.viessmann.com/iot/v1/features/installations/#######/gateways/################/devices/0/features/heating.power.consumption.heating" },
Very interesting that the point in time when the data stopped working seems to be very different for many people. For me the sensors worked until yesterday.
I actually upgraded to 2024.11.1 yesterday at 14:00, but the sensors still updated after, it only stopped working today.
I actually upgraded to 2024.11.1 yesterday at 14:00, but the sensors still updated after, it only stopped working today.
at midnight? For me it was like that. After updating it was updating till midnight, regularly the heat pump starts only at 4am with heating so I don't know about the timeframe midnight to 4am, but I suppose it stopped at next midnight after updating to 2024.11
Same here. I am running latest version of HAOS Core 2024.11.1 Supervisor 2024.11.2 Operating System 13.2
I can see data for all entities except for daily energy consumption for these entities: sensor.e3_tcu10_x07_dhw_energy_consumption_today sensor.e3_tcu10_x07_heating_energy_consumption_today
They were working up until a few days ago.
Rob
I have the same problem again after the 06.11.2024. For me it is the second time that this happens. No change after Update or restart of server. The last value registered appears all day as daily consumption.
Same here. I am running latest version of HAOS Core 2024.11.1 Supervisor 2024.11.2 Operating System 13.2
I can see data for all entities except for daily energy consumption for these entities: sensor.e3_tcu10_x07_dhw_energy_consumption_today sensor.e3_tcu10_x07_heating_energy_consumption_today
They were working up until a few days ago.
Rob
@SwiftRR I assume the other are showing data as they have not had a cyclic reset yet. Or are you really seeing values being changed/increased in these sensors?
In response to @x4N70pHyLL on 11th November and my comment from 10th November
I assume the other are showing data as they have not had a cyclic reset yet. Or are you really seeing values being changed/increased in these sensors?
I have checked back at all my entities.
So I am in a similar position to others. The integration appears to be broken.
Rob
Same Problem here. No data for Powerconsumption.
Already tryed to delete the integration and set it up again with a new Clienid from the developer portal. But nothing changes.
Hello, I have tried out a few things. I keep getting data when I restart the communication module of my heat pump. After restarting the module, it takes a few minutes and data appears again in Home Assistant. However, the problem is that I have to do this again every day. In my case, no data is transferred after midnight. Is this a Home Assistant problem or could it be Viessmann's fault? I have uploaded two screenshots here showing where you can restart the communication module in the Viessmann app.
That worked for me as well, so it seems I got the current values for today since midnight (not only the change after restarting the communication module).
What could be the problem? Is the error in Home Assistant or is the error directly at Viessmann in the cloud?
Restarting the communication module worked as well for me...Let's see if the data disappear tomorrow. Thx for the hint.
same here, all consumption data is stucked at 0 the last 2 days. never had such issues anytime before Nov 9th.
you have to restart the communication module every day since November 9 to continue receiving the data. This means that I will have to restart the module on my heat pump tomorrow morning to get the data again. The problem does not go away by restarting the communication module once.
I started to see these problems as well, but before I even updated Home Assistant to the November release. I actually went downstairs since two days to restart the complete central heating device. Glad to see that there is an easier way. As the timing doesn't match for me, I am convinced it is an Viessmann screw-up. Something else I noticed at the same time is, that my two circuits have been named back in the Vicare app to "Heizkreis 1" and "Heizkreis 2" (or whatever name it was...). At the central heating device downstairs, they where still using the chosen name. I couldn't rename them in the app, so I had to do this at the device, by adding something behind "Bodenheizung" and then removing it again. This fixed this problem for me. And even the option to rename them in the app re-appeared again.
'Same problem with my headpump - nothing changed (either Version of Com-Module nor HA) - just stopped to get data at the exact same point in time (06.11.)
Did someone try to logout the communication module? And reconnect it?
I started to see these problems as well, but before I even updated Home Assistant to the November release. I actually went downstairs since two days to restart the complete central heating device. Glad to see that there is an easier way. As the timing doesn't match for me, I am convinced it is an Viessmann screw-up. Something else I noticed at the same time is, that my two circuits have been named back in the Vicare app to "Heizkreis 1" and "Heizkreis 2" (or whatever name it was...). At the central heating device downstairs, they where still using the chosen name. I couldn't rename them in the app, so I had to do this at the device, by adding something behind "Bodenheizung" and then removing it again. This fixed this problem for me. And even the option to rename them in the app re-appeared again.
Hey,
did this fix the problem permanently? Or does the energy consumption fall back to 0 after a day again?
I started to see these problems as well, but before I even updated Home Assistant to the November release. I actually went downstairs since two days to restart the complete central heating device. Glad to see that there is an easier way. As the timing doesn't match for me, I am convinced it is an Viessmann screw-up. Something else I noticed at the same time is, that my two circuits have been named back in the Vicare app to "Heizkreis 1" and "Heizkreis 2" (or whatever name it was...). At the central heating device downstairs, they where still using the chosen name. I couldn't rename them in the app, so I had to do this at the device, by adding something behind "Bodenheizung" and then removing it again. This fixed this problem for me. And even the option to rename them in the app re-appeared again.
Hey,
did this fix the problem permanently? Or does the energy consumption fall back to 0 after a day again?
Only the name change seems to be fixed. The electricity data was missing this morning again and I fixed by recycling the communication module.
Restarting the communication module does not solve the problem permanently. The problem returns the next day.
Same here. Data disappears today again.
Same here, restart of com module helped again. However, maybe Vissmann changed something, but in their app the values are there. Daily as well. That means we'll have to look at the HomeAssistant / Integration side I guess.
Any insights, @CFenner ?
Is this limited to heat pumps?
I think the heat pump uses the summary endpoint and all others another one. No idea why..
let me check as i have a heat pump and a gaz boiler connected; for sure the heat pump is affected, restarting the module help until midnight, then 0 again.
Today my Energy Consumption actually stopped updating at circa. 1:00 and the compressor was still running after that:
I also checked the Viessmann API with the official Postman collection and it actually has the same problem (also in the summary features), while the official App shows the correct data:
{
"feature": "heating.power.consumption.total",
"gatewayId": "xxxx",
"deviceId": "0",
"timestamp": "..............................",
"isEnabled": true,
"isReady": true,
"apiVersion": 1,
"uri": "https://api.viessmann.com/iot/v2/features/installations/xxxxx/gateways/xxxxxx/devices/0/features/heating.power.consumption.total",
"properties": {
"day": {
"type": "array",
"value": [
1.5,
30.3,
.............
],
"unit": "kilowattHour"
},
"week": {
.............
So this is not a problem with the home-assistant integration but with the API from Viessmann.
let me check as i have a heat pump and a gaz boiler connected; for sure the heat pump is affected, restarting the module help until midnight, then 0 again.
the gaz boiler statistics are working well , so only heat pump data affected
@CFenner do you think, a fix can be done on HA?
@benniju
So this is not a problem with the home-assistant integration but with the API from Viessmann.
So the state, that the value is no longer updated, you can see in plain API as well? Then this is an issue with Viessmann.
https://community.viessmann.de/t5/The-Viessmann-API/API-liefert-Verbrauchswerte-nicht-mehr/td-p/445412 https://community.viessmann.de/t5/The-Viessmann-API/API-Power-Consumption-empty/td-p/481779 https://community.viessmann.de/t5/The-Viessmann-API/API-Power-Consumption/td-p/484586
Same issue, I can read the values in the Vissmann app on my phone, but after newest HA version, no energy consumption are updated after 2 AM I can restart my router, and wait for a few hours, and then the complete consumption will get updated in one bar, and after that the hourly consumption will show up... until 2 am the next day
Same here ,does a roll back to a previous version of ha fixed it?
same here...
Did I get this correct, that it's not related to the HA version, so 2024.10.x also does not work, right? So it's Viessmann related?
not really, it happened with the new release 2024.11.x , works well with 2024.10.x so it's most likely HA/plugin related ;-)
I wasn't on the new version when it started for me. So, it is an API issue at Viessmann and not your integration. Thanks for it btw!
My end I could confirm with raw API calls using curl
that I get the same results. So clearly a Viessman issue, not a plugin one.
I restart the "Kommunikationsmodul" every day now, to get informations. So this is a Workaround. I could imagine that reset the "Kommunikationsmodul" with the Button "Kommunikationsmodul abmelden" and setup the vicare App again, could help, because its a Viessmann issuse and i assume they destroyed the integration/communication with already registered Heatpumps. Maybe with a certificate update, who knows. But if i do it, i will lose my consumption data in the ViCare App.
So did someone try it?
Thanks for the update How do you restart the communication module, via the app manually which is so boring or via a script in home assistant?, if so could you share the way to do it?
On 22 Nov 2024, at 11:08, geekblog-dev @.***> wrote:
I restart the "Kommunikationsmodul" every day now to get informations. So this is a Workaround. I could imagine that reset the "Kommunikationsmodul" with the Button "Kommunikationsmodul abmelden" an than setup the vicare App again could help because its a Viessmann issuse and i assume they destroyed the integration/communication with already registered Heatpumps. Maybe with a certificate update, who knows. But if i do it, i will lose my consumption data in the ViCare App.
So did someone try it?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/130273#issuecomment-2493389325, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARGUMYDA2WXWRMQ646J2EAD2B37AXAVCNFSM6AAAAABRP6HWCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTGM4DSMZSGU. You are receiving this because you commented.
Thanks
On 22 Nov 2024, at 09:47, thestonewell @.***> wrote:
My end I could confirm with raw API calls using curl that I get the same results. So clearly a Viessman issue, not a plugin one.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/130273#issuecomment-2493209352, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARGUMYD2FPY7F3VRSBE4EE32B3VR5AVCNFSM6AAAAABRP6HWCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTGIYDSMZVGI. You are receiving this because you commented.
Just via the ViCare APP. Because i hope for a fix this year and its not bothering me enough at this point.
My end I could confirm with raw API calls using
curl
that I get the same results. So clearly a Viessman issue, not a plugin one.
@thestonewell: Could you please verify if your device has two consumption endpoints and both are affected?
summary | non-summary |
---|---|
heating.power.consumption.total |
|
heating.power.consumption.summary.dhw |
heating.power.consumption.dhw |
heating.power.consumption.summary.heating |
heating.power.consumption.heating |
heating.power.consumption.cooling |
The heat pumps (in the library) currently use the summary
data points while other heating devices use the non-summary
data point (no idea what the difference is an why it is done that way (legacy)).
Could you please verify if your device has two consumption endpoints and both are affected?
When I checked it a while ago, both endpoints were showing the same incorrect value. I can't check it again today, because I have already restarted the Kommunikationsmodul. Now both of the endpoints are also showing the same correct values with the correct day being the first element in the non-summary array.
If anyone wants to test the API themselves, you can use the postman collection linked at the bottom of this page: https://documentation.viessmann.com/static/getting-started . You can create a (temporary) bearer token in the dev portal (Generate Access Token). The request I am using, which returns all the endpoints in one respone, is under IoT/Features/Installation gateway device features and its URL is https://api.viessmann.com/iot/v2/features/installations/{{installationID}}/gateways/{{gatewaySerial}}/devices/{{deviceId}}/features . So you need to find the installationID, gatewaySerial and deviceId with the other requests under IoT/Equipment.
The problem
Since 2024.11.0 (in 2024.11.1 as well) my ViCare Integration does not show energy consumption anymore. It is not working for both heating and DHW and it affects all the sensors (daily, weekly, etc.). The old values are there (daily at 0 as it was reset already), weekly/monthly/yearly have their last values but are not increasing since 2 days.
Additionally I noticed that for overall consumption (there was - I think - daily/weekly/monthly/yearly) there is only the daily consumption sensor remaining, the others are gone.
Also for the new cooling energy consumption sensor I noticed that there is no weekly consumption, only daily/monthly/yearly which seems inconsistent to the rest.
To sum it sup . let me know if I should open different issues for the topics, they seem related to me so I put the together in one issue for now:
What version of Home Assistant Core has the issue?
core-2024.11.0
What was the last working version of Home Assistant Core?
core-2023.10
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
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response