So it should still work, we just need to adapt the API usage restrictions. According to polling entity integration documentation there should be a parameter scan_interval used. I’ve just checked and it is not implemented for this integration. Would it be possible to add it or where in the code could this be introduced?
I lost access on both HA and phone. Got a reset and could configure the app with a new email address. The one used esrlier with HA seems to be blocked.
I guess the new one will get blocked as well as you’ll reach the API use limits. So the key question is how to change the polling interval for vicare integration so we don’t exceed the limits.
The funny thing is, that the iOS app is still working while Android app shows connection problems…
So we now have some data on the limits published on the forum LINK
Currently, we have two limits active:
120 calls for a time window of 10 minutes
1450 calls for a time window of 24 hours
We see these limitations reasonable, also based on your great explanation concerning cloud based services. So thank you for that!
Also, we decided against HATEOAS as it is deprecated and will sooner or later be switched off.
So indeed it looks reasonable to me. How can we now implement it in the integration?
I have pushed this commit to the custom component:
665b2aa
This sets the update interval to 15 minutes. Worked for me within the last 8 hours but not yet 24 hours.
This fix will make it into the upcoming 0.107.
I guess something like this will have to be the hotfix for the Home Assistant integration. For an optimal solution we have to work on PyVicare to be able to fetch more than a single parameter via one HTTP GET.
So do we think accounts have been (perma-)banned due to exceeding API limits?
Both my Android app & the HA integration are dead, in the HA recorder I’m seeing a short period of activity, then it stops for the rest of the day.
Tha Android app never seems to function.
For now, there seems to be little choice but to disable the Vicare: integration ? This way, at least the app will(?) function correctly…I hope?
I disabled the HA Integration atm and recieved this e-mail from Viessmann development:
thank you for your response and your understanding!
Exceeding the limitation of API requests prevents you to execute any further requests with your account, which also affects the use of the ViCare app. You are still allowed to use the app and it should be working again within the next 24 hours.
In the meantime, please make sure to adapt the frequency of requests of your current API solution to avoid reaching the limitation. Usually, increasing to a frequency of 5 minutes per request should currently be ok.
I got a similar mail from Viessmann.
I disabled the HA integration yesterday and the App came back today.
0.107 is out now and as I read there is a scan_interval parameter.
Any details on this?
It’s only a quick fix: scan interval is now hardcoded to 15 minutes.
Further work is needed for lower scan intervals.
1 Like
Looks good so far, thank you!
Oh, I guess I was to fast. My Viessmann account has been locked again.
I upgraded to 0.107. Is there anything else which I have to configure?
My current setup in configuration.yaml looks like this:
vicare:
username: schwarze....
password: !secret vicare_pwd
heating_type: 'gas'
In the log I see the following:
Logger: ViCare
Source: custom_components/vicare/water_heater.py:80
First occurred: 1:17:04 PM (1 occurrences)
Last logged: 1:17:04 PM
Token expired, renewing
no there is nothing else to configure.
Just upgrade to 0.107 or higher. (and wait 15minutes after the reboot for data to arrive in the vicare integration)
Hello. Will display options expand?
- For example, an outdoor temperature sensor
- a water temperature sensor in the heater
- number of burner starts
- number of burner hours
- Fuel consumption (if possible)
Thanks for your work.
@oischinger I’m still experiencing the ban, it seems to be irregular.
Can I edit something somewhere to further increase the delay ?
Hi @Tommmii,
I guess I’ll make it configurable but I’m also still trying to figure out the exact numbers of api accesses for a ban. Unfortunately if a user opens the Vicare app a couple of API calls more are made and you’re banned again 
Regarding your question.
Please see this commit:
https://github.com/oischinger/ha_vicare/commit/665b2aabd58d4c8c0efd05db4e633e8301b58806
This is the line of code you need to adapt. It’s 900seconds currently. Note that both components: water_heater and climate are making api calls.
Do you have multiple circuits configured? That would also increase the amount if api calls.
I figured that opening the app would also count against their api-counter, thanks for confirming that though.
Yes, I’ve also configured the water_heater component, I guess I will remove that for now - until the dust settles.
There is just the single circuit for me.
So I probably have a blocked account, or I do not know, but since yesterday when I installed the add-on to HA so today after one HA restart Viessmann data in HA has not appeared in the application and VICARE reports that my smartphone can not connect to the server. I didn’t get any email. where can be the error?
I still have a question. Couldn’t the whole be overhauled and circumvent the Viessmann API? To collect all data optolink which would be connected to esp8266 and send everything to HA? On the Internet I saw a solution with dual optolink and one part went to Viessmann servers and the other to a PC where the data was processed. There is information on github.
Hello,
what can i do now? 
Dear {{ insert first_name 'default=default' }} {{ insert last_name 'default=default' }},
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 to check and channel the method and frequency of requests to our IoT Services in order to keep those stable and available for all our users.
That’s why we have now taken the decision to limit access to our API. From the coming week on, a threshold will become active that prevents from unauthorized use of the API. This will affect all third-party solutions, which can thereby no longer be used.
We are aware that the demand for APIs to our technologies for integration into other solutions and third-party systems is increasing. To provide you with an opportunity for this, we will launch a portal in the next two months for all developers to get access to our API. With the Viessmann Developer Portal, we intend to open ourselves up, release a documentation of the interface and co-develop new solutions together with you. In addition, we are planning to provide you with useful information around our heating systems you need for your development and to offer you a first-level support concerning our APIs.
As one of the users who is already working with our API, we would like to invite you to an early access to the Developer Portal. If you are interested, please fill out this short form. The access to the pre-version of the Portal will be sent to you within the next weeks.
We hope you understand the decision that we have to take. If you are interested to support us, on further development on the API and to explore new possibilities, we are very happy to welcome you to our Developer Portal soon!
In the meantime in case you have any questions, feel free to contact us under [email protected].
Thank you for your understanding.