Hi,
i updated HA today to 2022.5 form i guess 2022.4.
No i lost some entities of my vicare integration.
I don’t get any information about burner modulation or burner starts
Does anybody know what happend?
Hi,
i updated HA today to 2022.5 form i guess 2022.4.
No i lost some entities of my vicare integration.
I don’t get any information about burner modulation or burner starts
Does anybody know what happend?
It has nothing to do with the update. I’m on 2022.5 since release and it worked until 08:32 this morning (CET). Now the most important sensors are unavailable:
I just checked out this python lib:
looks like they fixed something today that meets the problem stated above
Viessmann changes the API a lot. I’ve never seen an API with so many breaking changes in such a short time.
It’s also fixed in HA Core now.
The next minor update should resolve the issues
hi, I can’t config the vicar component, the is the error, someone can help mi? I use ha supervised on proxmox
Logger: aiohttp.server
Source: components/vicare/init.py:55
First occurred: 11:06:26 (1 occurrences)
Last logged: 11:06:26
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py”, line 435, in _handle_request
resp = await request_handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py”, line 504, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py”, line 117, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 60, in security_filter_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/forwarded.py”, line 100, in forwarded_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 28, in request_context_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 79, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 236, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 136, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/config/config_entries.py”, line 177, in post
return await super().post(request, flow_id)
File “/usr/src/homeassistant/homeassistant/components/http/data_validator.py”, line 62, in wrapper
result = await method(view, request, *args, **kwargs)
File “/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py”, line 109, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 277, in async_configure
result = await self._async_handle_step(
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 359, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File “/usr/src/homeassistant/homeassistant/components/vicare/config_flow.py”, line 53, in async_step_user
await self.hass.async_add_executor_job(
File “/usr/local/lib/python3.10/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 55, in vicare_login
vicare_api.initWithCredentials(
File “/usr/local/lib/python3.10/site-packages/PyViCare/PyViCare.py”, line 26, in initWithCredentials
self.initWithExternalOAuth(ViCareOAuthManager(
File “/usr/local/lib/python3.10/site-packages/PyViCare/PyViCareOAuthManager.py”, line 30, in init
oauth_session = self.__restore_oauth_session_from_token(token_file)
File “/usr/local/lib/python3.10/site-packages/PyViCare/PyViCareOAuthManager.py”, line 34, in __restore_oauth_session_from_token
existing_token = self.__deserialize_token(token_file)
File “/usr/local/lib/python3.10/site-packages/PyViCare/PyViCareOAuthManager.py”, line 135, in __deserialize_token
s_token = pickle.load(binary_file)
EOFError: Ran out of input
I am gering the same error.
Just from one day to another, without any Updates/changes from my side
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht
Logger: homeassistant.config_entries
Source: custom_components/vicare/init.py:55
Integration: Viessmann ViCare
First occurred: 09:36:26 (1 occurrences)
Last logged: 09:36:26
Error setting up entry ViCare for vicare
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 339, in async_setup
result = await component.async_setup_entry(hass, self)
File “/config/custom_components/vicare/init.py”, line 44, in async_setup_entry
await hass.async_add_executor_job(setup_vicare_api, hass, entry)
File “/usr/local/lib/python3.9/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/vicare/init.py”, line 66, in setup_vicare_api
vicare_api = vicare_login(hass, entry.data)
File “/config/custom_components/vicare/init.py”, line 55, in vicare_login
vicare_api.initWithCredentials(
File “/usr/local/lib/python3.9/site-packages/PyViCare/PyViCare.py”, line 26, in initWithCredentials
self.initWithExternalOAuth(ViCareOAuthManager(
File “/usr/local/lib/python3.9/site-packages/PyViCare/PyViCare.py”, line 31, in initWithExternalOAuth
self.__loadInstallations()
File “/usr/local/lib/python3.9/site-packages/PyViCare/PyViCare.py”, line 43, in __loadInstallations
installations = self.oauth_manager.get(
File “/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareAbstractOAuthManager.py”, line 41, in get
self.__handle_server_error(response)
File “/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareAbstractOAuthManager.py”, line 60, in __handle_server_error
raise PyViCareInternalServerError(response)
PyViCare.PyViCareUtils.PyViCareInternalServerError: (PyViCareInternalServerError(…), ‘Request failed with status code 500 and message “Internal server error”. ViCare ErrorId: req-fb0164176fe24bb0a9935616b2d02a84’)
Same error here.
PyViCare.PyViCareUtils.PyViCareInternalServerError: (PyViCareInternalServerError(…), ‘Request failed with status code 500 and message “Internal server error”. ViCare ErrorId: req-f6edd62a96d447a697f4f2c3baf4c7c4’)
This seems to be a server issue recently introduced by Viessmann. Interestingly it doesn’t happen for everyone.
I have two instances of Home Assistant, 2022.8.x
PyViCare.PyViCareUtils.PyViCareInternalServerError: (PyViCareInternalServerError(…), ‘Request failed with status code 500 and message “Internal server error”
I wonder if the architecture difference is a good debugging direction.
As probably many of us in these days i got a new price from my supplier for gas. So i thought its a good idea to add the price to the energy dashboard to see real time costs.
But unfortunately is the price for gas provided in kwh and in HA its measured in m3.
Whats is the easiest way to add the price now? Is it necessary to recalculate kwh to m3?
Entgegen des Titles ist es recht trivial für die hier nötige Genauigkeit, kWh Preis mal 10 als m3 Preis eingegeben
Is there anything new to this problem?
I am using HA inside a Docker container on my Synology Diskstation 220+.
Current HA version is 2022.8.5. The problem exists since 7.8.
Maybe this will help to narrow down the problem.
I would be grateful for any help.
As a workaround please see https://github.com/home-assistant/core/issues/77050#issuecomment-1221565264
Hello to all. I’m quite new to HA and at the moment I’m trying to integrate my Viessman Vitocaldens 222-F with this component. Everything work as a charm, but my device is identified by the PyViCare library as “HeatPump”. The device identifier is “CU401B_S” however this is not an Heat Pump but an Hybrid generator used for both Heating and Hot Water.
I made some test using PyViCare library on a python CLI and I’m able to access all the relevant data (compressor, burner and various temperature). I will open an issue to PyViCare to have my model correctly assigned. However i wonder how I can force the device type inside the Viessman Component in HA.
Here an extract of “download diagnostic”, as you can see the heating type is “auto”.
"entry": {
"entry_id": "e5285b6427d56d1d59a640f75a3eadf8",
"version": 1,
"domain": "vicare",
"title": "Vicare",
"data": {
"username": "**REDACTED**",
"password": "**REDACTED**",
"client_id": "**REDACTED**",
"heating_type": "auto"
},
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"unique_id": null,
"disabled_by": null
},
Regards,
Federico
Thanks! I didn’t think about that possibility.
Federico
Hi everybody, digging around i found this site Announcements | Viessmann. It seems that Viessman is announcing here their changing in the API. Hope this can help… even if I understand that the most interested are the guys that are developing PyViCare.
Federico