Viessmann Component

I’m also struggling a bit to install this.

I created the custom_components folder in my config directory.
There is mentioned a vicare.py file, where do I get that ?
It’s not in the zip file I downloaded from https://github.com/oischinger/ha_vicare
Should I use a file from https://github.com/somm15/PyViCare and just rename the file ?

I got it working :slight_smile:
Didn’t know Home Assistant would download PyVicare it self.

I get these errors.

Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity.py", line 220, in async_update_ha_state
await self.async_device_update()
  File "/usr/src/app/homeassistant/helpers/entity.py", line 379, in async_device_update
await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/vicare/climate.py", line 95, in update
_room_temperature = self._api.getRoomTemperature()
  File "/config/deps/lib/python3.7/site-packages/PyViCare/PyViCare.py", line 338, in getRoomTemperature
return self.getProperty("heating.circuits." + str(self.circuit) + ".sensors.temperature.room")["properties"]["value"]["value"]
  File "/config/deps/lib/python3.7/site-packages/PyViCare/PyViCare.py", line 212, in getProperty
j=self.__get(url)
  File "/config/deps/lib/python3.7/site-packages/PyViCare/PyViCare.py", line 145, in __get
r=self.oauth.get(url).json()
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 546, in get
return self.request('GET', url, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests_oauthlib/oauth2_session.py", line 425, in request
headers=headers, data=data, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

Seems you resolved your installation problems except for that error.

Does the custom component deliver proper data despite that error?
These ConnectionErrors are unfortunately happening due to various network or server reasons but most the next update usually succeeds.

By the way: I updated the custom component to word with Home Assistant 0.92.

Regards, Hans

Yes it deliver proper data, but it’s a short time it works.
Maybe scan time is too short (using default value).

Have to restart HA before it works again.

The exception is not the reason it sops working. The issue most likely relates to token renewal. See https://github.com/somm15/PyViCare/issues/10

Hi,

any possibility to have the climate component activate the dhw instead of the dhwAndHeating? I mean any option to make this configurable? Like during summer I would only like dhw to be active and dhwAndHeating only when it’s cold…

Thanks!

I have a Vitocal 333 G heat pump and the Vitoconnect 100.
In the Vitoguide web there is the following information below of which I only see the outside temperature in Home Assistant with the Vicare integration.

Is there a way to monitor these other attributes as well?

Regards, Christer

System

Compressor
OFF

Hours run
9824

No. of starts
36420

Outside
15.9°C

Return flow
30.2°C

1 Like

I have updated from 0.93.2 to 0.96.2 and suddenly vicare component is not working.
Even when I try to validate configuration, I got

" Configuration invalid 
Platform not found: climate.vicare"

Any thoughts?

Yeah, the default HASS climate component has been reworked, so the Viessmann component needs to be updated as well. I have been wanting to do an ‘official’ home assistant integration for some time, but I’ve been having some medical issues. I’ll see if I can make some time this week to update the custom component to a working state, but I can’t make any guarantees…

1 Like

A configuration value could do that I guess. I’ll look into it.
The components is broken since the last home assistant update. I’ll try to fix it asap.

Did you check the sensors created by the custom component?
Some things like outside temperature should already be there.
Since I don’t have the same heater I don’t know what to look for.
You could try to look for it yourself by digging through the parameters in the API. e.g. run this to get the gas consumption on your home assistant python venv:

python -c "from PyViCare import ViCareSession; t=ViCareSession('[USERNAME](mailto: USERNAME)','','/tmp/vicare_token.save'); print(t.getProperty('heating.gas.consumption.heating')['properties']['month']['value'][0])"

I started to work on HA 0.96 compatibility and created an initial PR:
https://github.com/oischinger/ha_vicare/pull/19

The concept of Climate devices in HA has changed quite a bit, see this HA PR: https://github.com/home-assistant/home-assistant/pull/23899/files
It might be more compatible with the ViCare API than before now.

My PR is however far from complete and mostly untested. I guess it’ll take some time to finish it.

1 Like

Have you noticed that there is a new Version for ViCare (0.1.0 https://github.com/somm15/PyViCare ) released, which also supports heat pumps? When doing your adjustments, it might make sense to also incorporate this new version / changes as well?

Any update on the “96” version?

Please watch the PR https://github.com/oischinger/ha_vicare/pull/19

I’m planning to merge it soon.

@michelde I guess we’ll make a separate PR for the new API after the Climate 1.0 migration

The PR is now merged. Vicare component on master branch is now compatible with HA 0.96+.

The handling of the different modes and programs has now changed quite a bit:
Basically the three hvac modes off, heat and auto now map to the Viessmann modes ForcedReduced, ForcedNormal and DHWandHeating.

The presets eco and comfort are a 1:1 mapping to the respective Viessmann programs.

After the update I cant get in lovelace the entity

climate.vicare_heating

It should still be there. do you see some ViCare related errors on the log?