Während der Woche der Wärmepumpe haben Sie bundesweit die Möglichkeit, die innovative Wärmepumpentechnologie näher kennenzulernen. Mit über 50 Informationsveranstaltungen beteiligt sich Viessmann Climate Solutions an der Aktionswoche und lädt Sie herzlich ein – vor Ort oder online – dabei zu sein.
Mehr erfahren →Dear developer and smart home enthusiasts,
today, we want to contact you to talk with you about the recent activities that are taking place concerning the interface of the heating systems, also known as the Viessmann API. As most of you might have already received our Email in which we informed you about the upcoming changes concerning the use of the API, we would like to open this thread to continue the discussion openly and transparent with you and pick up on the discussions in this thread. Here is again a brief summary of the main points from our message:
> As Viessmann, it’s in our responsibility to provide our users with reliant and safe products, including features and services around those products
> We are impressed to see your interest in connecting and interacting with your heating system and that you found a solution for your specific use case without a description or support from our side
> However, 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
> What is even more important is that for these solutions, we as Viessmann currently cannot guarantee a safe and reliant operation of your heating system
This has the following steps that we have to take:
> In order to keep operation through our API safe and still give you the chance to interact with your system, we limit the use for all applications by setting a threshold for the requests. The limit is set for both a larger (e.g. daily) and a smaller (<15 mins) time scale. Reaching the limit will prevent you to execute any further requests with your account in the specific time frame. So please make sure to adapt the frequency of the requests of your current solution to avoid reaching the limitation.
> We are heavily working on providing a solution for all users that is 1) approved & safe to use, 2) properly explained and 3) gives you the functions and information you need for your specific use case. At the same time, this will also be moment when the solution is in place where we cannot allow any other ways of accessing our API. To make things clear: Your already built and currently used functions will still be able to use, it’s only that you will need a new API client provided through the Portal that can be self-managed by the user himself.
We also received a lot of questions via Mail and also in this forum, which we are going to answer for everyone individually. We also saw that the most common question among the responses was the demand for a local API. This is a reasonable request and we appreciate and take the demand very seriously. However, we will not able to provide you a solution for this in the near future. This feature (as all other features and requests by users) are permanently discussed and evaluated and brought together with all other strategic decisions that Viessmann is taking.
I again would like to encourage everyone to participate in the development and make sure to sign in here to get an early access to the Developer Portal. Also, we are hoping to have a constructive discussion here in this thread. We are really looking forward to work jointly together with you on ideas and co-create future solutions!
P.S.
As stated in the previous thread and in certain Emails we received, we are aware that some users might expect a communication in german from us, as Viessmann is of course a company with German heritage. However, since we are providing climate solutions all over the world and especially programming / APIs is natively described in english, there is no other option than communicating in english first. This has already been greatly explained by @thetrueavatar in the previous thread.
All the best!
Michael Hanna
Viessmann Developer Portal
EDIT:
In order to support you more on adjusting your current solutions according to the current limitation, here is how the threshold works:
We have a rate limit with sliding window. Whenever the first request arrives, we open a time window and count all request in that window. If the number of requests reach the limitation, we block all incoming user requests until the time window ends. Then, with the next user request, a new time window opens.
Currently, we have the following limits active:
120 calls for a time window of 10 minutes
1450 calls for a time window of 24 hours
Please take note that we are taking the right to adjust the limits if seen necessary. Information about adjustment of the threshold will be given with a reasonable amount of time in advance for all affected user.
EDIT2:
For all who experienced a ban after the limitation time frame with a few number of API requests: Our team fixed an issue with the limitation, which is taking effect since today and should solve this problem. We are still analyzing the behavior, but for now it looks ok.
Hi,
first I need to say, I fully understand this and what the most "nerds" forget, if you find a way to use an API, this don't mean you are legaly allowed to use it.
So I'm really thankful that Viessmann don't focus only on the non tech guys who use only the App. It is great that you planning an official API for the SmartHome users.
**bleep** all these good words, the big BUT. IoT system should be build in a way that you can easily scale the system and it should be no problem to add more servers to your IoT cluster. Why you don't spend the money till you are done with the developer API and provide us directly with a solution?
A good release schedule would be to implement the threshold **bleep** 2 months of the release of the new API. So everyone have time to move the programming over to the new API.
Perhaps you could remove the threshold again and add it **bleep** you released the new API.
Also something that would cool down the situation a little bit, would be to give us an ETA for the start of the BETA testing also for the official release. Already with the "working" beta, most of us could bring systems up and running again.
Also remove the english word A F T E R from your filter of the forum.
Hubert
How about fixing this thread also ? I can't see half of the message sometimes and it's quite difficult to understand why. Sometimes my response appears in the feed, sometimes as comment to others.. Pffou this is quite a mess to deal with...
@thetrueavatar
When clicking a notification in an email only the thread with comments is displayed. Above the box is a link "Gesamtes Thema betrachten" or "See full thread" or something similar. This will switch the view (although this is really quite a mess). When vieweing a single post or comment the reply will only end up in this subthread. When viewing the full thread and replying below it will end up as a new post.
@MichaelHanna
Indeed since the old api was designed to be discovered bit by bit with it's HateOAS approach my client was implemented in this way.Moreover feature were added/updated quite often and since I didn't had a full spec documentation I couldn't test most of the feature available. That's why I have started by a "one call per information" approach. However, I could switch to a kind of graphql approach where every user give as input the list of data they want and I will do only one call and parse it to provide the data asked.
I could indeed update my client as soon as I get my access back 😛
Hello Michael and all Viessmann Team,
@MichaelHanna schrieb:
> In order to keep operation through our API safe and still give you the chance to interact with your system, we limit the use for all applications by setting a threshold for the requests. The limit is set for both a larger (e.g. daily) and a smaller (<15 mins) time scale. Reaching the limit will prevent you to execute any further requests with your account in the specific time frame. So please make sure to adapt the frequency of the requests of your current solution to avoid reaching the limitation.
Could you please specify this a bit more clearly, what the limits are? I don't think it is very constructive if everyone tries to figure out this individually via try&error.Does 15 minutes mean, you only can have one request per 15 minutes, 96 per day? And if you do one automatic request every 15 minutes, you will not be able to use the "original" ViCare app any more, because you already used up all of your "quota"?
Question answered while I wrote this post, thank you!
@MichaelHanna schrieb:
At the same time, this will also be moment when the solution is in place where we cannot allow any other ways of accessing our API.
In order to allow a seemless handover for the users, it would be great if you can provide an overlap of at least one week, so everyone has the opportunity to implement the changes necessary without totally loosing the service in the mean time. (Not ultra viable for logging-only users like me, but for those who also remote-command their heating system.)
@MichaelHanna schrieb:
We also saw that the most common question among the responses was the demand for a local API. This is a reasonable request and we appreciate and take the demand very seriously. However, we will not able to provide you a solution for this in the near future. This feature (as all other features and requests by users) are permanently discussed and evaluated and brought together with all other strategic decisions that Viessmann is taking.
Could you give us a small hint, what are the big issue with a local API?
To make things clear: I would be totally satisfied if the local API only provides a READOUT of current STATE (all measured temperatures, modulation, pumps, current program active - preferrably also active settings like heat curve, set temperatures, but that's not so important) and for anything you want to SET on the heating system you would have to go over your servers.
People who have integrated it in their home automation may think different, as they also want to reduce dependency on cloud services. But I can imagine, that consolidating commands from two sources may be an issue. So this could be a second step somewhen in the future.
But giving a local access that only gives you information but does not allow to modify anything could be easier to implement. This would satisfy all users who do logging, and it takes off much traffic and server load on your side (what you will keep in any way with "just" a new, different API). It can be a totally simple interface, just every time you query data from the heating, put it out to the local interface as well.
Also if limited CPU power and/or memory in the VitoConnect is the issue, keep it simple. For example, make a telnet port that routinely outputs the data as it arrives. No need for compicated API server software.
Best regards,
an engineer that is also working on embedded systems and therefore know about those limitations.
Dear Viessmann,
This is a direct consequence of enforcing users to use cloud only solution. Clearly, you are completely unprepared for such solution. Allow developers and users access over LAN and problems will be solved!
This is crazy that in order to read temperature from the boiler 10 meters away I need to send data back and forth across the globe especially that both are on the same network.
Not only I am struggling with Vitodens 200-W B2HE problems that according to local Viessmann support are because of software bugs, now this. This is becoming a joke.
Looks like you are giving me no choice but consider steps to return the product or at least file complain to local government consumer centre.
Regards,
Lukasz
Hi Michael,
I have limited my requests to a frequency of 20 minutes. That is 1440/20=72 requests in 24 hrs. To me, I'm not brekaking the lilit. Nevertheless my Vicare app still doesn't work...
Kind regards
Johan
Hello,
two questions concerning the Developer Portal (Pre-)Registration.
Does the email address there need to match the credentials used for the server registration?
What is the intention about giving the postal address - oh I just see, this is not mandatory, so nevermind.