Viessmann Component

Tommmii · May 4, 2020, 10:27am

You seem to have several datapoints that are different from what I have in the Vicare app for Android.
Perhaps you could consider setting your language to english, it would certainly make comparisons much easier.

Jiri_Stransky · May 4, 2020, 10:37am

Yes, I probably have it a little different, but probably everyone will have it differently, depending on the type of boiler. This is also evident from the demo application, where it is also different and on the web interface there are several boilers in the demo and in each it is also a little different.
I tried to see if the language version could be changed and not. I would probably have to change the language for the whole phone, and that’s nonsense. But if you know how to change only the language for Vicare, then I’ll try.

Jiri_Stransky · May 4, 2020, 10:46am

To clarify, I will add what kind of automation I have for the boiler vitotronic 200 kw2
https://1url.cz/IzEzc

Jiri_Stransky · May 14, 2020, 2:38am

Friends, since I got the answers, I immersed myself in examining the code and found some bugs that cause the burner starts and burner hours to no longer be displayed after deleting the vicare folder from custom_components. At the same time, the burner status was never displayed.
I don’t know exactly what is modified in the code for the Home Assistant implementation, but something is different than in the version on Gitghub, because when loading files from Github, the burner starts and hours appear again.

If you also want to see the status of the burner, whether it is active or not, you need to add one line in climate.py to the following line 154:

’ self._attributes [“burner_active”] = self._api.getBurnerActive ()’

You can try, but all the values provided by PyVicare templates are now available

crazyfx1 · May 18, 2020, 12:04pm

Thats very easy to explain: The official integration and the integration in the github of oischinger are two different version states of the integration. Since it takes quite long to release new features in the official integration, you can try out features earlier by using the custom component.

In the end I would suggest to always use the official integration, otherwise you might miss out on new features

Ruud2702 · July 15, 2020, 7:09am

Hello @oischinger,
I noticed a few things in the current ha integration with german translation:

water_heater.vicare_water: the status is displayed as on and off. but it should be “An” and “Aus” as with the other entities
state_color: true for binary_sensor.vicare_burner_active, climate.vicare_heating, and water_heater.vicare_water doens’t work
there is no way to set a pure hot water operation. only permanently set heating to reduced temperature. but this will also deactivate domestic hot water.

Can you help?

Have a nice day

adorobis · July 16, 2020, 1:16pm

After installing the custom component I have the following entry in the log:

ClimateDevice is deprecated, modify ViCareClimate to extend ClimateEntity

what should I do about it? I don’t specify any config for those climate devices apart from the “vicare:” section

vicare:
  username: !secret vicare_username
  password: !secret vicare_password

adorobis · July 16, 2020, 1:20pm

I have another question to the vicare component. As we have summer now would be good to have a DHW mode available. When switching from off to Auto the heater actually switches to DHWandHeating mode, at the same time the ViCare app has this option available so it should also be available in the API. Am I missing something or it is not implemented yet?

crazyfx1 · July 16, 2020, 4:48pm

Delete the custom component from your folder and use the official version which is up-to-date.

adorobis · July 16, 2020, 6:44pm

OK, clear
Anyway the DHW mode is not available in the official version. Is this something that is in the plans?

gomble · September 1, 2020, 12:19pm

Same problem… cant use it like this in homeassistant

Tommmii · September 6, 2020, 4:01pm

anyone else not getting connection through the ViCare app?

najumiqbal · September 17, 2020, 4:26pm

Hi,

I am new to home assistance. I am running Home Assistant Core 0.115.0b12. I am trying to add Viessman Integration but have no clue where to start. If someone can help me step by step guide that would be much appreciated. I found this integration link on home assistance integration section but not sure what repo to add.

Please if someone can help me in the right direction.

Thanks,

n@j

Tommmii · September 17, 2020, 7:30pm

@najumiqbal This is literally all yo need to do :
https://www.home-assistant.io/integrations/vicare/#configuration

najumiqbal · September 18, 2020, 4:48pm

HI Tommmii,

Thanks for responding to my query. I have already added those bits under configuraiton.yaml. but I am not seeing any Viessman device.

Regards,

n@j

Tommmii · September 18, 2020, 7:27pm

in the HA web interface, go into Configuration (in side bar), then select Entities, then search for Vicare.
You should see a bunch of results, all were added by this ViCare integration.

najumiqbal · September 21, 2020, 11:47am

Thanks, @Tommmii . I finally got it working.

Jiri_Stransky · October 4, 2020, 10:07am

Hello. After a long time, I am writing again to see if anyone would know what can cause sporadic non-loading of the sensor in LOVELACE. I enclose 3 screens where you can see which sensor it is in LOVELACE, it is the Vicare temperature curve that both shows “not detected”, but it can be seen in the history of the sensor that it has been in order for some time. Then it can be seen that in the test the template shows normal values at any time.
So the question is, what causes the sensor to work normally in the template test, but LOVELACE does not always display it.
Thank you in advance for your comments.

Jiri_Stransky · October 7, 2020, 2:19pm

If anyone is interested in a solution. After restarting HA, the data from the sensors will not be read from VICARE and the template will no longer be loaded when the data from VICARE runs out. Entity sensor template needs to be reloaded. So far, I’m doing it manually, but it should be somehow automated.

stefanwi · October 13, 2020, 6:59am

Hi,

is anyone else experiencing an error in vicare since yesterday afternoon? HA log:

Logger: homeassistant.setup
Source: custom_components/vicare/__init__.py:84
First occurred: 6:38:48 (1 occurrences)
Last logged: 6:38:48

Error during setup of component vicare
Traceback (most recent call last):
  File "/srv/homeassistant_3.8/lib/python3.8/site-packages/homeassistant/setup.py", line 213, in _async_setup_component
    result = await task
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/homeassistant/.homeassistant/custom_components/vicare/__init__.py", line 84, in setup
    vicare_api = GazBoiler(conf[CONF_USERNAME], conf[CONF_PASSWORD], **params)
  File "/srv/homeassistant_3.8/lib/python3.8/site-packages/PyViCare/PyViCareDevice.py", line 48, in __init__
    self.service = ViCareCachedService(username, password, cacheDuration, token_file, circuit)
  File "/srv/homeassistant_3.8/lib/python3.8/site-packages/PyViCare/PyViCareCachedService.py", line 8, in __init__
    ViCareService.__init__(self, username, password, token_file, circuit)
  File "/srv/homeassistant_3.8/lib/python3.8/site-packages/PyViCare/PyViCareService.py", line 58, in __init__
    self._getInstallations()
  File "/srv/homeassistant_3.8/lib/python3.8/site-packages/PyViCare/PyViCareService.py", line 219, in _getInstallations
    self.id=self.installations["entities"][0]["properties"]["id"]
KeyError: 'entities'

Occuring since yesterday afternoon, ~ 5 pm

Regards,
Stefan