Viessmann Component

oischinger · December 12, 2021, 5:36pm

The empty input fields issue is being addressed with this PR:

github.com/home-assistant/core

Add vicare strings

home-assistant:dev ← oischinger:vicare_strings

opened 05:31PM - 12 Dec 21 UTC

oischinger

+50 -0

## Proposed change  ## Type of change  - [ ] Dependency upgrade - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [ ] New feature (which adds functionality to an existing integration) - [ ] Breaking change (fix/feature causing existing functionality to break) - [ ] Code quality improvements to existing code or addition of tests ## Additional information  - This PR fixes or closes issue: fixes #61561 - This PR is related to issue: - Link to documentation pull request: ## Checklist  - [x] The code change is tested and works locally. - [x] Local tests pass. **Your PR cannot be merged unless tests pass** - [x] There is no commented out code in this PR. - [x] I have followed the [development checklist][dev-checklist] - [x] The code has been formatted using Black (`black --fast homeassistant tests`) - [ ] Tests have been added to verify that the new code works. If user exposed functionality or configuration variables are added/changed: - [ ] Documentation added/updated for [www.home-assistant.io][docs-repository] If the code communicates with devices, web services, or third-party tools: - [x] The [manifest file][manifest-docs] has all fields filled out correctly. Updated and included derived files by running: `python3 -m script.hassfest`. - [x] New or updated dependencies have been added to `requirements_all.txt`. Updated by running `python3 -m script.gen_requirements_all`. - [x] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description. - [x] Untested files have been added to `.coveragerc`. The integration reached or maintains the following [Integration Quality Scale][quality-scale]:  - [ ] No score or internal - [ ] 🥈 Silver - [ ] 🥇 Gold - [ ] 🏆 Platinum  To help with the load of incoming pull requests: - [ ] I have reviewed two other [open pull requests][prs] in this repository. [prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone  [dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html [manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html [quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html [docs-repository]: https://github.com/home-assistant/home-assistant.io

Hopefully will end up in HA Core soon.

Alternatively you can install the custom component from GitHub - oischinger/ha_vicare: Home Assistant component for Viessmann Vitodata service to have working input fields right now.

sidlauskas · December 12, 2021, 6:11pm

that was a question to me or Tobias?

TobiasKneidl · December 12, 2021, 7:00pm

After update to 2021.12, did you remove the ViCare component from the YAML configuration file and reboot?

sidlauskas · December 12, 2021, 7:03pm

I did not update to 2021.12, I’m still on core-2021.11.5 and I’m trying to add ViCare integration for the first time.

oischinger · December 12, 2021, 7:36pm

@sidlauskas if you want to setup the component via UI you must have the latest home assistant version. The previous version only supported yaml configuration

alessandro.bardi · December 12, 2021, 8:03pm

Thanks for fix.
Unfortunately, i have this error:

Logger: homeassistant.config_entries
Source: components/vicare/__init__.py:134
First occurred: 21:02:26 (1 occurrences)
Last logged: 21:02:26

Error setting up entry ViCare for vicare
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 313, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 98, 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 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 134, in setup_vicare_api
    hass.data[DOMAIN][entry.entry_id][VICARE_CIRCUITS] = hass.data[DOMAIN][
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareDevice.py", line 36, in circuits
    return list([self.getCircuit(x) for x in self.getAvailableCircuits()])
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareUtils.py", line 45, in feature_flag_wrapper
    return wrapper(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareUtils.py", line 38, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareDevice.py", line 265, in getAvailableCircuits
    return self.service.getProperty("heating.circuits")["properties"]["enabled"]["value"]
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareCachedService.py", line 24, in getProperty
    data = self.__get_or_update_cache()
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareCachedService.py", line 36, in __get_or_update_cache
    data = self.fetch_all_features()
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareService.py", line 56, in fetch_all_features
    return self.oauth_manager.get(url)
  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 502 and message "DEVICE_COMMUNICATION_ERROR". ViCare ErrorId: req-cb3b24c375d04e8285c6536671f00d66')

config failed!
Regards,

Alessandro

sidlauskas · December 12, 2021, 8:40pm

I managed to make it work. What is interesting about this integration that it doesn’t provide “current room temperature” entity.

adorobis · December 12, 2021, 8:58pm

Normally it does, in my case it is called: living_room_temperature
But for that you need to have the Vitotrol room regulator (e.g. Vitotrol 300 in my case) to have the room temperature.

TheJulianJES · December 12, 2021, 8:59pm

At some point today, “HTTP 500 Internal server error” started appearing in my logs (like every 30 minutes?). I restarted Home Assistant (2021.12.0) and now the entire integration failed to setup.

The ViCare app seems to work fine though. Does anybody have similar problems?

Edit: See below.

2021-12-12 21:54:25 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry ViCare for vicare
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 313, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 98, 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 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/vicare/__init__.py", line 134, in setup_vicare_api
    hass.data[DOMAIN][entry.entry_id][VICARE_CIRCUITS] = hass.data[DOMAIN][
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareDevice.py", line 36, in circuits
    return list([self.getCircuit(x) for x in self.getAvailableCircuits()])
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareUtils.py", line 45, in feature_flag_wrapper
    return wrapper(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareUtils.py", line 38, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareDevice.py", line 265, in getAvailableCircuits
    return self.service.getProperty("heating.circuits")["properties"]["enabled"]["value"]
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareCachedService.py", line 24, in getProperty
    data = self.__get_or_update_cache()
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareCachedService.py", line 36, in __get_or_update_cache
    data = self.fetch_all_features()
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareService.py", line 56, in fetch_all_features
    return self.oauth_manager.get(url)
  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-censored')

Edit: Seems to work after another restart now?
Edit 2:
Now getting this for the circulation pumps:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 487, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 691, in async_device_update
    raise exc
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/vicare/binary_sensor.py", line 196, in update
    self._state = self.entity_description.value_getter(self._api)
  File "/usr/src/homeassistant/homeassistant/components/vicare/binary_sensor.py", line 44, in <lambda>
    value_getter=lambda api: api.getCirculationPumpActive(),
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareUtils.py", line 45, in feature_flag_wrapper
    return wrapper(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareUtils.py", line 38, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareDevice.py", line 455, in getCirculationPumpActive
    status = self.service.getProperty(f"heating.circuits.{self.circuit}.circulation.pump")[
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareCachedService.py", line 24, in getProperty
    data = self.__get_or_update_cache()
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareCachedService.py", line 36, in __get_or_update_cache
    data = self.fetch_all_features()
  File "/usr/local/lib/python3.9/site-packages/PyViCare/PyViCareService.py", line 56, in fetch_all_features
    return self.oauth_manager.get(url)
  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-censored')

sidlauskas · December 12, 2021, 9:34pm

Yes, I have Vitotrol room regulator and I can see the room temperature in their application (Vicare), but not in this integration.

bronek1 · December 13, 2021, 1:32pm

For all Viessmann Vitodens-100W (or similar) users - I added gas and power consumption methods in oischinger version of ha-vicare in pull request in github. @oischinger could you check that and share to main home assistant vicare addon?

Daniel_Dyp_Jonasson · December 14, 2021, 1:17pm

I do very often get Error: (PyViCareCommandError(…), ‘Command failed with status code 502. Reason given was: COMMAND_NOT_FOUND’)
A reboot of HA can solve the issue sometimes. Many times a automation can run once and then fail with the same issue.

bronek1 · December 14, 2021, 8:47pm

Question is do you use the newest version of ViCare? Which Viessmann equipment / hardware you use?
Which version did you installed? Original from configuration.yaml or custom component from Oischinger (ha_vicare from github)?

Daniel_Dyp_Jonasson · December 15, 2021, 7:03am

I have a vitocal 222-S and a Vitoconnect. Uppgraded to latest version yesterday. Removed the old vicare-connection and added it manually through integrations.

moppes · December 16, 2021, 5:23pm

What should I do if adding the new ViCare integration says “Aborted”?
Before I used to have it set up via configuration.yaml. Now, after updating to 2021.12.02 (I was very looking forward to it) I liked to set it up again.

Feels somehow strange. How can I re-install the whole ViCare thing?

jelin23 · December 17, 2021, 7:45am

Hey, yesterday on the vicare app they displayed an info about serwer works, today on the app the info i have is (your viessmann cant connect to wifi) *in my router I see that it stays connected. Do you guys have same problem after the vicare app update?

adorobis · December 17, 2021, 8:02am

I have just updated the app and all works ok. In the past occasionally the vitoconnect module required restart (power cycle) to get it connected back to Viessmann servers.

mamoel · December 17, 2021, 8:10am

Same here. I cannot connect the Vitoconnect 100 Opto1 to my router anymore.

jelin23 · December 17, 2021, 8:14am

I use newest vitodens 100. I re configured the wifi in the boiler and on the end point vitodens says e-12 error which means ( server error)

jelin23 · December 17, 2021, 8:22am

I just received a message from V:

Hi, we have some issues with our cloud servers and are currently trying to fix the error. I will give you an information as soon as the problem is resolved.
Best regards, Chris