Viessmann Component

Sophokles · August 19, 2021, 4:42pm

for me, the two sensors “Vicare Burner Hours” “Vicare Burner Starts” and “Vicare Burner modulation” are important, nut not available any more. As I thought thy might not be provided by Viessmann yet, I Wrote to Viessmann and asked them to provide them again in their API. Viessmann answered, that they are already provided. Any idea why they arent available? Are they available in other users integrations? Here is the answer from Viessmann:

Hallo xxx,

mit der neuen API stellen wir weiterhin die wichtigsten Funktionen bereit, die für Privatanwender im Bereich Smart Home relevant sind. Dazu gehört auch die Modulation Brenners. In der API Dokumentation haben wir eine Sektion, die die verfügbaren Datenpunkte auflistet: https://developer.viessmann.com/en/doc/iot/data-points. Die Funktion, die Sie benötigen ist “heating.burners.N.modulation”

Falls der Datenpunkt über Home Assistant nicht verfügbar sein sollte, kann dies unter Umständen an der Implementierung liegen. Daher wäre mein Vorschlag, dies nochmal bei Home Assistant in Erfahrung zu bringen.

Ansonsten können Sie auch gerne unser Forum besuchen: Developer Portal | Viessmann

Freundliche Grüße,

XXXXXXXXXXXXX

crazyfx1 · August 19, 2021, 5:45pm

Every heating system is different so please specify the name of your heating system.

Tommmii · August 19, 2021, 7:28pm

on my 222W those are indeed present.

hteske · August 19, 2021, 8:38pm

Interesting, Burner Hours and Burner Starts are visible to me. I‘m lacking the other information as posted above…

Sophokles · August 23, 2021, 4:01pm

I have A Vitodens 300-W connected by a Vitoconnect 100 Opto 2. These are my configuration lines:

# Viessmann Vicare
vicare:
  username: xxxxx
  password: xxxxx
  client_id: xxxxx
  heating_type: gas
  circuit: 1

With this configuration, Vicare supply temperature is available, but the three sensors mentioned above are not. If I delete this line, Vicare supply temperature becomes unavaillable, but the three others (e.g. burner modulation) become available. I would like to see all four …
This seems to be a bit odd for me and it wasn’t the case with the old integration. I only have one heating circuit so I think the circuit line should not be neccesary in the configuration, but without it the circuit sensors are not shown.

Sophokles · August 23, 2021, 4:16pm

Sorry, the line I deleted 7 added was the line circuit: 1

Sophokles · August 23, 2021, 8:30pm

Different question: is it possible to make the sensor infomration of the solar heating system of the 300-w available? I think theyare supported by the viessmann API.

hteske · August 24, 2021, 7:34am

Hi Sophokles,

I experimented with adding circuit: 1. I see the same behaviour:

ViCare Heating and ViCare Supply Temperature are available,

but Burner Hours, Burner modulation and Burner Starts are now missing too.

Does anyone have an idea what we could change or is this maybe a big in the integration?

Regards
Holger

ursus_polaris · August 25, 2021, 11:12am

I recently added the Viessmann-Integration through API and even I did everything correctly, I also got connection errors. I believe the Developer Portal of Viesmmann runs a cron-job at night to activate the API-Keys with a delay. Either way: The next day my integration worked without any changes. (I saw this behavior before with other API-portals, that’s why I tried it out).

So my advice, if it doesn’t work: Wait a day.

My (working) config is:

vicare:
  username: "[email protected]"
  password: "xxxxxxxxx"
  client_id: cb2exxxxxxxxxxxxxxxxxxxxxxxxx
  name: Heatpump
  heating_type: heatpump

oischinger · August 25, 2021, 12:16pm

Hey @hteske I have a PR ongoing to allow configuration of the component via the UI and automatic discovery of all circuit ids:

unfortunately I find too little time to finish it but you could help me verifying that it works for multiple circuits. My system has only a single circuit.

adorobis · August 25, 2021, 6:14pm

Interestingly the water_heater entity does not look the same anymore:

Previously it was showing the set temperature and provided controls to set it, now only the current temp is visible.

Tommmii · August 25, 2021, 7:29pm

yea, it turns out to be a known thing and fixed in PiVicare…but not (yet?) in the HA Vicare integration.

hteske · August 27, 2021, 9:00am

I’m happy to help. Can you give me a little hint on how I can get your version up and running?

oischinger · August 28, 2021, 7:10pm

You need to check out the branch “config_flow” GitHub - oischinger/ha_vicare at config_flow and than copy the vicare directory from your workarea to /config/custom_components/vicare (in case you are using Home Assistant OS). This will replace the official integration by that custom one.
Then remove all config entries for vicare from your yaml. After a restart Home Assistant should notify you that it discovered a Viessmann Vicare device on your network and ask you to set it up via the integrations page. You should see a dialog like this:

Once set up you should see entities for all circuits on your system. Would be great if you could send me a screenshot of all entities discovered for vicare.

TheJulianJES · August 28, 2021, 7:26pm

I haven’t tried the new config_flow branch yet, but how does it handle multiple heating circuits?
Will it support two circuits at once for example?

Also, thanks for your work!

oischinger · August 28, 2021, 7:43pm

Yes it autodiscovers the circuits and creates the sensors multiple times if required

hteske · August 30, 2021, 1:22pm

So, I added your branch to the custom_components directory and restarted HA like you wrote. Unfortunately, the integration is not detected. I also tried finding it manually, but it didn’t show up under “Integrations”.

I use HACS, so the custom_components directory also contains the HACS components, don’t know if that causes trouble?

ddokupil · August 30, 2021, 1:27pm

Should I be able to add a Viessmann integration manually? I suppose it should be looking for vitoconnect on my network, which is connected and available and has MAC B87424* but for some reason isn’t listed anywhere in HASS and I can’t force it to rediscover it, nor add an integration manually (not present on list of available integrations - see image below). As for a custom integration I’m pretty sure it’s in right place as I’m getting Error during setup of component vicare preceded by This error originated from a custom integration. if I uncomment my old vicare setup in configuration.yaml. Any idea?

oischinger · August 30, 2021, 7:01pm

@ddokupil and @hteske
do you see some exception in the log?
You should be seeing it in the list of integration unless of course it crashes on load.

By the way, I updated the branch to use the latest version of PyVicare.

ddokupil · August 31, 2021, 8:47am

Works fine already. Turned out to be my router causing problems. After fixing that it automatically detected vitoconnect, however I have no idea why I could’t see vicare integration on the list before…