Climate Solutions Community

MichaelHanna · ‎08.07.2021

Hi @nerixs , Please find my answer to this topic in the related thread: https://www.viessmann-community.com/t5/The-Viessmann-API/Fehlende-Datenpunkte/m-p/180340#M20 @phildaub23 , the respond to your specific request you can find here: https://www.viessmann-community.com/t5/The-Viessmann-API/API-Datenpunkt-Solarthermie-Energieproduktion/m-p/180334#M19

MichaelHanna · ‎08.07.2021

Hello @andreas13, @JueBag , @AndreasP , with the availability of the Developer Portal, we simultaneously look at which features of the API we can make available and in what form. Our API offers various options for obtaining certain data points. The Developer Portal is ongoing development, you can always state your concrete feedback in the respective section in the developer forum area 🙂 Also, keep in mind that there is a difference between the offering and use of ViCare and the API. We are not planning to 1:1 all functionalities of ViCare through our API. @AndreasP , your list of features is quite exetensive. As they were only accessible through an unofficial / unauthorized way, we cannot offer the same functionality through the Developer Portal. What would be more interesting is a more concrete explanation of use cases that come with certain functionalities. To sum it up, the Developer Portal and the offering is in an ongoing development. My recommendation is to first consider the currently available features, however we are happy to take the requests (based on use cases) with us for further investigation. Best, Michael

MichaelHanna · ‎08.07.2021

Hallo @phildaub23 , Es freut mich zu hören, dass du auf den Developer Portal API client erfolgreichen umsteigen konntest. Mit dem Bereitstellen des Developer Portals schauen wir gleichzeitig, welche Features der API wir in welcher Form zur Verfügung stellen können. Unsere API bietet zu bestimmten Datenpunkten zudem auch verschiedene Möglichkeiten, diesen Datenpunkt zu erhalten. Wir sind also dran. Ich würde dir nochmal Bescheid geben, sobald ich hier genaueres sagen kann 🙂

MichaelHanna · ‎06.07.2021

Hallo @HartmutJ, danke für die Rückmeldung. Die Puffertemperatur wird aktuell leider noch nicht in der ViCare App angezeigt bzw. können nicht via API abgerufen werden. Es stehen allerdings für Solarthermieanlagen folgende Datenpunkte zur Verfügung: heating.solar.pumps.circuit - Shows the status of the solar pump heating.solar.sensors.temperature.collector - Shows Solar Collector temperature in °C heating.solar.sensors.temperature.dhw - Shows solar dhw (domestic hot water) temperature in °C

MichaelHanna · ‎05.07.2021

Hallo @HartmutJ, Welche Daten kannst Du genau via API aufrufen? Sind das bereits Daten bezogen auf das Heizsystem? generell gilt als Voraussetzung für die Nutzung der API, dass das System Vitoconnect-fähig ist. Die unterstützten Regelungen sind hier aufgeführt: https://www.viessmann.de/de/viessmann-apps/vitoconnect.html Um sicher zu gehen, kannst Du mir gerne die Seriennummer Deines Systems (gerne auch per PN) zuschicken. Nutzt Du für dein System bereits die ViCare App?

MichaelHanna · ‎05.07.2021

Hello @BrechtM, we recently added solar thermal features to the Developer Portal API clients: heating.solar.pumps.circuit - Shows the status of the solar pump heating.solar.sensors.temperature.collector - Shows Solar Collector temperature in °C heating.solar.sensors.temperature.dhw - Shows solar dhw (domestic hot water) temperature in °C The list of all available data points can be found in the chapter "Data Points" within the "IoT" section of the Developer Portal API Dokumentation: https://developer.viessmann.com/en/doc/iot/data-points

MichaelHanna · ‎05.07.2021

Hi @JueBag, could you please share the response that you receive from the request? In general, my first assumption is that the feature request is not accounting for the order of the features. To have a more robust implementation, I would recommend anaylsing feature names instead of the order of the features. However, I will check with the development teams to make sure, how the device features is ordered within the response.

MichaelHanna · ‎05.07.2021

Hallo @andreas13, mit der Abfrage machst Du alles richtig. Der Punkt an der Stelle ist, dass für den Installations Endpunkt keine Features zur Verfügung stehen 🙂 Wenn du Informationen zu Deiner Installation suchst, hast du mit https://api.viessmann.com/iot/v1/equipment/installations/{installationId} die Möglichkeit, die Infos abzurufen.

MichaelHanna · ‎05.07.2021

We are happy to announce that a dedicated Viessmann Community area for developers is now available. In this area, you will find new announcements and information around our API. You will also be able to post your questions and exchange with other developers around the API. To get started using the API, visit our Developer Portal under developer.viessmann.com or have a look at the post: https://www.viessmann-community.com/t5/Announcements/Das-Viessmann-Developer-Portal-ist-jetzt-verfuegbar/td-p/173369 We look forward to great exchanges and co-creation among all developers!

MichaelHanna · ‎22.06.2021

Hi @JueBag, your token has not been used by the browser I assume. Calling https://api.viessmann.com/service-documents/v3/ does not need any token in order to call the service. This is why your browser received the correct response. If you for example call https://api.viessmann.com/iot/v1/equipment/installations/ within your browser, you will get an error 401 "UNAUTHORIZED"; "NO TOKEN AVAILABLE", because you need an access token to call this service. Hope this helps. Best, Michael

MichaelHanna · ‎21.06.2021

Hi @JueBag , Thanks for your suggestion concerning the documentation. We will check how we can have clearer overview for the user, which scopes are available beforehand. Once you requested a refresh token, it will stay the same so that you can use it to obtain an access token. However, when requesting another refresh token, it will be new one that you will get. My suggestion is creating a refresh token once and then only performing step 2 in the authorization flow: https://developer.viessmann.com/en/doc/authentication Please do not get confused with the versioning within the API calls (URLs). There is no new API that is released after July 15th. What we are doing is that we are disabling an API key that is currently being by a lot of users. Instead, our intention is that everyone is obtaining their own personal API key through the Developer Portal. The versioning you are seeing is related to the services behind the API call and can be different for each service. You find the version of a service at the top of each page in the documentation, see the attachment image for installation features. I hope this answers your questions. Best, Michael

MichaelHanna · ‎21.06.2021

Hi @JueBag , within the second step (Authorization code exchange), have you set the parameter within the header? -H "Content-Type: application/x-www-form-urlencoded" Also, make sure to send a POST request. The expiration time of the token is in seconds. However, you can create a refresh token, which helps you obtaining a new access token much easier, as you do not need to do step 1 (Authorization request) anymore. You find the explanation for the refresh token here: https://developer.viessmann.com/en/doc/authentication (Refreshing an access token) Hope this helps. If you have further questions, let me know. Best, Michael

MichaelHanna · ‎17.06.2021

Hallo @asblass, vielen Dank für den Hinweis! Mittlerweile sollte das Problem mit dem Scrollen auf dem Developer Portal nicht mehr vorhanden sein. Falls Du doch noch irgendwelche Probleme mit dem Developer Portal erfahren solltest, kannst du diese auch gerne direkt an developer@viessmann.com weitergeben. Schöne Grüße, Michael

MichaelHanna · ‎19.03.2020

Thank you for explaining @Croydon 🙂 This behavior is valid for any active threshold, respectively.

MichaelHanna · ‎19.03.2020

@JueBag our team fixed an issue with the limitation, which is taking effect since today. We are still analyzing the behavior, but for now it looks ok. Please note that unregistering is not necessary!! And do not only reduce the calling rate, please also check the sum of your requests in the limitation time period. I will also add this in my initial post. @thetrueavatar @Croydon @adorobis Best, Michael

MichaelHanna · ‎18.03.2020

@thetrueavatar once this is approved I am happy to do this 🙂 But again, don't let your number of API calls exceed the limitation. There is not much we can do for you in this case.

MichaelHanna · ‎18.03.2020

@thetrueavatar your assumption from above (calls counted based on "credentials") is not correct. There was indeed an issue within the limitation, which I expect we will be having fixed tomorrow. However, I cannot say whether this is causing the problem for your implementation or not. So please make sure that your number of API calls are not exceeding the limitation once this is fixed. Best, Michael

MichaelHanna · ‎18.03.2020

@Tommmi unauthorized means that we are not able to guarantee a safe and responsible use of your applications since there is no official API provided by us. But as I say we are working on it change this.

MichaelHanna · ‎18.03.2020

@thetrueavatar I appreciate your passion on this topic. However, right now we do not see any reason for suspending the limitation. As I already said, I forwarded all your issues and we see what we can do on our side. @Tommmi, @ravanimi @adorobis your and all other responses and issues are taken seriously and we are looking closely to everything you provide us. We are trying our best to support you with your issues you are currently experiencing. However, please take into account that this limitation is a reasonable measure, but this measure also aims to still give you the opportunity to use your applications, which are not authorized in any way by us and since we have not yet officially allowed using our API, we are not responsible for the experience with your applications. That's just to be honest. So please understand that we are working on is to provide everyone the opportunity to get official access to our API, since we are more than happy to co-create new solutions together with you. Best, Michael

MichaelHanna · ‎18.03.2020

@Croydon @thetrueavatar thank you for the explanation. This helps us in investigating the issue. We will check with our developer and keep you updated here. Best, Michael

MichaelHanna · ‎18.03.2020

Hi @Tommmi, thank you for your response. Accounts have not been perma-banned. After the limitation time frame has passed, you should be able to execute requests again with your account. We will also have a look at the threshold implementation, since this issue has been stated by different users now. We will give you more information about it in this thread. Hope this helps. Best, Michael

MichaelHanna · ‎17.03.2020

@thetrueavatar @Croydon could you list which calls are being made by your code and how often? Then we can check and see if it makes sense. We will also have a look at the threshold implementation and give you more information here. (@ravanimi also for your notice)

MichaelHanna · ‎17.03.2020

Hi @johandb, reaching the limit will prevent you to execute any further requests with your account in that time. Changing the frequency of calls will help in not reaching the limit, but you need to wait until the time frame is over to be able to perform requests again. Best, Michael

MichaelHanna · ‎17.03.2020

Dear @JueBag, I'm not sure what you mean by "in one go". In general, every request is counted.

MichaelHanna · ‎17.03.2020

Hi @didy, concerning the the first part of your response I added a short description about how the current threshold is defined in the very first post of this thread. Also, I hope you understand I cannot go in details about the local API. This was also not my intention by opening this thread. At the same time, your opinion and suggestions of course help us in developing new solutions for the future. With the Developer Portal, we intend to give everyone the opportunity to co-create new solutions in a way that is reliable and sustainable. So, we hope to hear more suggestions from you in the future and appreciate it a lot! Best regards, Michael

MichaelHanna · ‎17.03.2020

Thank you @Croydon for giving the explanation 🙂

MichaelHanna · ‎17.03.2020

@thetrueavatar I'm happy to provide you and all other user more concrete information on how the current restriction 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 request until the time window ends. Then, with the next user request, a new time window opens. 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.

MichaelHanna · ‎17.03.2020

Hi @schueli86, thank you for your response! Your connection will be back as soon as the time limit stated above is reached. Just make sure to adapt the frequency of the requests of your current solution to avoid reaching the limitation. I'm for happy to hear that you are interest in the Developer Portal. You can find the link for registration here: https://forms.gle/kMpJ1i573absQWHn6

MichaelHanna · ‎17.03.2020

@ravanimi thank you for the response. One thing we definitely want to pursue with the Developer Portal is the opportunity to co-create new solutions with our users who are already very passionate in building own solutions for their use cases. That's why the Developer Portal is aiming to provide everything that is needed to enable this. We are always happy to hear from your suggestions, as this helps us in providing a better service. However, we also have to check with the possibilities we have. Best regards, Michael

MichaelHanna · ‎16.03.2020

Thank you @phildaub23 for bringing it on the point! And sorry for any misleading information that the previous mail had caused. Looking forward to co-develop! Best, Michael

Climate Solutions Community

Deine Aktuellen Statistiken

Re: Betreff: Missing access points.

Re: Betreff: Fehlende Datenpunkte

Re: Betreff: API Datenpunkt Solarthermie Energiepr...

Re: Betreff: Viessmann API und VITOLIGNIO 300C

Betreff: Viessmann API und VITOLIGNIO 300C

Betreff: API: solar information available in vicar...

Betreff: Returns from an API request change order.

Betreff: API "Installation features" liefert leere...

Welcome to the Viessmann Developer Community area!

Betreff: API usage questions

Betreff: API usage questions

Betreff: Problems getting the access token

Betreff: Das Viessmann Developer Portal ist jetzt ...

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Betreff: Q&A Viessmann API

Weitersurfen