Viessmann Component

Jiri_Stransky · April 6, 2020, 2:11pm

I used the same code he wrote a week ago.
I have oil heater, so it is chosen generic

# Viessmann
vicare:
  username: !secret vicare_email
  password: !secret vicare_password
  heating_type: generic
  scan_interval: 120
#
water_heater:
  platform: vicare
#
sensor:
  - platform: template
    sensors:
      vicare_outside_temperature:
          friendly_name: "Vicare outside"
          unit_of_measurement: '°C'
          value_template: "{{ state_attr('climate.vicare_heating', 'outside_temperature') }}"
      vicare_desired_temperature:
          friendly_name: "Vicare target"
          unit_of_measurement: '°C'
          value_template: "{{ state_attr('climate.vicare_heating', 'temperature') }}"
      vicare_heatcurve_target_temperature:
        friendly_name: "Vicare heatcurve target "
        unit_of_measurement: '°C'
        value_template: "{{ state_attr('climate.vicare_heating', 'temperature') + state_attr('climate.vicare_heating', 'heating_curve_shift') - state_attr('climate.vicare_heating', 'heating_curve_slope') * (state_attr('climate.vicare_heating', 'outside_temperature') - state_attr('climate.vicare_heating', 'temperature')) * (1.4347 + 0.021 * (state_attr('climate.vicare_heating', 'outside_temperature') - state_attr('climate.vicare_heating', 'temperature')) + 247.9 * 0.000001 * (state_attr('climate.vicare_heating', 'outside_temperature') - state_attr('climate.vicare_heating', 'temperature')) * (state_attr('climate.vicare_heating', 'outside_temperature') - state_attr('climate.vicare_heating', 'temperature'))) }}"
      metno_outside_temperature:
        friendly_name: "Met.no outside"
        unit_of_measurement: '°C'
        value_template: "{{ state_attr('weather.home', 'temperature') }}"

Tommmii · April 6, 2020, 4:04pm

In the Template editor, what is the output of :
{{ state_attr('climate.vicare_heating', 'current_temperature') }}

?

Jiri_Stransky · April 6, 2020, 4:50pm

I do not know exactly how to work in the template editor, but after opening it is all already filled. Is it right? Or what exactly should I do?

Jiri_Stransky · April 6, 2020, 4:52pm

Jpsy · April 6, 2020, 7:13pm

After you copied the template code to the left pane the result of the template interpretation should appear in the right pane. That is the part that you should publish here.

Tommmii · April 6, 2020, 7:26pm

so {{ state_attr('climate.vicare_heating', 'current_temperature') }} = 0 , but Vicare app shows something other than 0 ???
I’m lost - this makes no sense, they are the same data.

Jiri_Stransky · April 6, 2020, 8:44pm

I don’t understand either, but if it helps as I see it in Vicare. Maybe there is a bug in the app at Viessmann. I don’t know where to get that temperature, whether from circuit1 or from the boiler. The boiler has a temperature, but the circuit is not. The temperature for circuit 1 should be taken directly from the boiler.

Jiri_Stransky · April 7, 2020, 11:18am

Hello, directly from vitogiude website it looks like this. At the same time, I will ask whether it will be possible to incorporate red marked items into HA.

Tommmii · April 7, 2020, 2:36pm

Have you tried reading {{ state_attr(‘climate.vicare_heating’, ‘current_temperature’) }}
while the boiler is On ?
Perhaps there’s some bug somewhere that doesn’t give the right value for boilertemp when burner is Off ?
I dunno…just thinking out loud.

Blindside · April 7, 2020, 5:39pm

Hi all,

I just installed HA a few hours ago. By trying to integrate my Viessmann system, I found this thread. Since the official integration is quite barebones, I downloaded all the files from the github repository.

I created the “custom_components/vicare” subfolder in the configuration folder an pasted all the filed there. After restarting HA, I find the following line in the log:

2020-04-07 19:32:30 ERROR (SyncWorker_3) [homeassistant.loader] Error parsing manifest.json file at /config/custom_components/vicare/manifest.json: Expecting value: line 7 column 1 (char 6)

What am I doing wrong?

Edit: As an additional question: Do I need to add code to the configuration file for this to work properly?

Edit 2: Do I need to remove the standard Viesmann integration somehow? Currently, I only have my Username and Password in the config file.

crazyfx1 · April 7, 2020, 6:40pm

Which home-assistant version do you use?

Blindside · April 7, 2020, 6:55pm

HassOS 3.12 according to the dashboard. I have downloaded the image from the website this afternoon.

Jiri_Stransky · April 7, 2020, 7:15pm

The result is always the same. I think that the 0 is taken from the circuit, where it is also 0 and it will be a mistake at Viessmann that for the heating system on my boiler does not take the boiler temperature into the circuit, because he does not have a sensor for circuit 1. It only has a sensor for circuit 2, which when connected, the boiler automatically programmed to have two circuits and the output temperature then I see circuit 2, but which physically does not exist.

Tommmii · April 7, 2020, 7:38pm

You need the same config as documented for the “regular” (non custom_component) integration. There’s plenty of examples posted in this thread.

No.

Blindside · April 7, 2020, 7:47pm

This is the code that I currently have in the config file:

  # Viessmann
vicare:
  username: yyyyyyy
  password: yyyyyyy
  heating_type: generic
#
water_heater:
  platform: vicare
#
sensor:
  - platform: template
    sensors:
      vicare_outside_temperature:
          friendly_name: "Vicare outside"
          unit_of_measurement: '°C'
          value_template: "{{ state_attr('climate.vicare_heating', 'outside_temperature') }}"

But I still get this error in the log file

2020-04-07 21:44:29 ERROR (SyncWorker_0) [homeassistant.loader] Error parsing manifest.json file at /config/custom_components/vicare/manifest.json: Expecting value: line 7 column 1 (char 6)

Edit: After I deleted the custom components folder, deleted everything I added to the configuration file and re-entered the standard Viessmann information, I am now not even getting the water temperature.

I would like to see in HASS

Warm water temperature (worked after new installation, not anymore)
Outside temperature from the Viessmann sensor

I am not able to set it up, since I always receive the mentioned error message in the log file if I copy the files from github.

crazyfx1 · April 8, 2020, 5:54am

Seems like the custom component is not working on your system for some reason. I would suggest to wait for the new home assistant version which should be out in the next weeks. Then you’ll have the current version of the integration officially.

Tommmii · April 8, 2020, 7:49am

how are you copying the files into the custom_components folder ?

Blindside · April 8, 2020, 9:01am

Seems like the custom component is not working on your system for some reason. I would suggest to wait for the new home assistant version which should be out in the next weeks. Then you’ll have the current version of the integration officially.

Allright, then I will wait. Will my code above correctly read out water temp and outside temp or is there an error in the code as well?

how are you copying the files into the custom_components folder ?

I installed the official Samba share and I am seeing the Pi in the Windows Explorer and simply copy the files in the destination folder. I anything wrong with that?

Tommmii · April 8, 2020, 9:20am

Sometimes the error you get is related to a wrong/bad download of the files from Github.
Just Google "home assistant" "Expecting value: line 7 column 1 (char 6)"

Did you actually download the zip archive, then extract it, then copy the vicare folder into HA ?
Compare the contents of your vicare folder to this post (#199) in this thread : Viessmann Component

Your config looks OK, but I wouldn’t configure the integration until you have the integration installed.

Blindside · April 8, 2020, 12:00pm

Wow thank you, redownloading and unzipping directly into the config folder actually did the trick!

I can now see outside and water temp as I wanted.

Do I have to delete these files and to config entries when this component becomes part of the next update?