I’m not sure if this is the right place to ask, but how would I integrate two circuits from ViCare?
I can change which one I use with the circuit: 0 or circuit: 1, but I think I’m unable to add both of them at the same time.
Does anybody know, if that’s already possible?
Thanks!
(Put this in a new thread as a question: Viessmann ViCare integration: Multiple circuits possible?)
Also not sure if this is the right place - I´ve successfully set up vicare however I am missing some entities as visible in the lovelace example (https://github.com/oischinger/ha_vicare/blob/38af017444475130b141dd846c5fc51f8b94a492/doc/lovelace_example.jpg):
The only one´s that I got are
climate.vicare_heating
and
water_heater.vicare_water
and for those there´s only current and target temperature.
What I am missing therefore is for example outside temp, kWh consumption, etc.
Did I miss anything? I´ve also copied the contents of the vicare directory to /config/custom_components/vicare
Thanks in advance & regards,
Marcel
Most of the sensors are now attributes of the climate and water_heater components. You can still create individual sensors if you want. See my blog post here:
“Making use of template sensors and the Home Assistant Vicare integration” https://link.medium.com/h3hohRn7t2
Note that consumption is currently not available. We weren’t able to get it accepted upstream. It needs to be done as a sensor and since Viessmann provides the data in a non-continous way (e.g. consumption / month) it’s not really easy to do it right.
First of all, thanks for the Vicare integration!
I have some problems setting the water heater target temp for my heat pump. Calling the water heater service with set_temperature gives no errors, and using lovelace the numbers change from red (unsaved?) to black, but the target temp for the water heater never actually changes. It does show the correct current water temp, target temp (that i can change in the vicare app), and the on/off-status is switched when changing modes in the climate component.
Does anyone else have this problem or any ideas on how to troubleshoot?
What lovelace type is the temperature?
I’m using thermostat but I can’t switch between eco and comfort?
Same issue here. Attributes are getting updated properly but I can’t change the preset_mode neither to Eco nor to Comfort. It does not work neither from the lovelace thermostat component nor by calling the service set_preset_mode directly from developer tools. There is no message in the log that would explain what’s the problem. Another issue is that the burner status is always Inactive even when it is actually On. Other attributes seem to have correct data.
Today’s Vicare outage brought up an issue with this component.
Home Assistant takes ages to restart & throws errors because the Vicare component can’t reach the Viessmann servers.
Any way to handle this properly ?
Well since the Viessmann servers aren’t overly reliable anyway, but also because your internet connection could fail we didn’t introduce any strategy when the integration should give up fetching data.
What could be done is reducing the number of requests (i.e. not fetching every single attribute but instead fetching all the data with a single API call).
Unfortunately this would result in quite some rework of the PyVicare library.
Local access FTW … 
hello oischinger,
did you read the future request to display a second circuit?
regards
@Ruud2702 I guess it shouldn’t be so hard but I have no ways to test it. Would you volunteer to install a custom component and try it out?
Today I got an email from Viessmann API development with a survey how they can improve their api. There were also 2 questions about a price for api usage.
Looks like the have traffic problems. Let’s see what will come in terms of monetarisation.
an evaluation has shown that you have used the web interface to Viessmann IoT Services very frequently in recent days.
On the one hand, we are delighted to know you are taking a closer look at our products and solutions. Especially since you have (apparently) found a solution for your specific use case without a description or our support from our side.
On the other hand, it challenges us checking and channelling the method and frequency of requests to our IoT Services in order to keep those stable and available for all our users.
We are aware that the demand for APIs to our technologies for integration into other solutions and third-party systems is increasing. We do not want to close our eyes to this. On the contrary! With a project called “Viessmann Developer Portal” we intend to open ourselves up and release a documentation of the interface to you.
Therefore we would like to get in contact with you, get to know each other and understand your use case in order to learn from you!
If you are interested to support us, on further development on the API and to explore new possibilities, we are very happy if you take part in our short survey! The link to the survey can be found
Always keep reminding them that local access really should be offered to us (the already paying customer).
@oischinger: I added two new properties to the heatpump device (https://github.com/somm15/PyViCare/pull/20) and it’s already available in latest PyViCare package. Can we get those 2 attributes (getSupplyTemperaturePrimaryCircuit and getReturnTemperaturePrimaryCircuit) also in the Home Assistant Integration? Maybe you can add these when doing some changes otherwise I would do a pull request to the Viessmann integration.
This! If the VitoConnect 100 could have a local API i would be so happy! I guess i triggered Viessmann with my poor automation, it pushed a new operating mode to their servers every 2min. Worked fine for about two months, but then just stopped. Changing mode works fine from the app, and changing other settings work fine from HA, it seems their servers block some of the requests from my HA.
Local is the way, i don’t need any Viessmann servers to drop my requests with no feedback and no way for me to fix it. I installed OpenV on a rpi and can now do what i need locally.
