Climate Solutions Community

MichaelHanna · ‎09.08.2021

Hi @joeH68 , First sorry you didn't hear anything from us so far – I was indeed in exchange with @jborup about this topic and I thought information exchanged will also reach this thread. Basically, I was first recommending switching off the system via the power switch, restarting the router and, if available, the powerline adapter and then putting the system back into operation. Sometimes certain data packets are not transmitted because the gateway, the router or the powerline adapter has "hung up". Let me know if this works for you. Also, could you provide a screenshot from ViCare and list here the list of feature names you are missing at the moment. You can check https://developer.viessmann.com/en/doc/iot/data-points to get the feature names. Best, Michael

MichaelHanna · ‎06.08.2021

Hi @andreas13 , Thank you for the information, we appreciate your feedback! I will have to forward this to our development teams to have a closer look. I will inform you as soon as I receive feedback on this. Best, Michael

MichaelHanna · ‎06.08.2021

Hello @nerixs , I replied to this issue in the thread you mentioned. For completeness, let me also add it here. We have checked with our development team and did testing on the mentioned issue, but could not find any bugs on the logic. After reaching limits, requests are not counted at all so they can’t lead to extending ban. If the issue still occurs on your side, please contact me directly via PM and provide us with steps for reproducing the issue, as well as your user id (login name) and your client id (API key) to remove the >24h ban. Best, Michael

MichaelHanna · ‎06.08.2021

Hallo @DMy , könntest du einen Screenshot von der Übersicht zum Gasverbrauch aus ViCare und aus dem Modul, das die API nutzt, zuschicken? Meines Wissens nach zeigt ViCare ebenfalls den Gasverbauch für Heizung, Warmwasser und Total an. Gruß, Michael

MichaelHanna · ‎04.08.2021

Hi @bz, du könntest mal versuchen, anstelle von "changeEndDate" den Command "schedule" auszuführen und "start" und "end" zu setzen (Datumsformat: YYYY-MM-DD): "commands": { "schedule": { "uri": "https://api.viessmann-platform.io/iot/v1/equipment/installations/{{installationID}}/gateways/{{gatewaySerial}}/devices/{{deviceID}}/features/heating.operating.programs.holiday/commands/schedule", "name": "schedule", "isExecutable": true, "params": { "start": { "type": "string", "required": true, "constraints": { "regEx": "^[\\d]{4}-[\\d]{2}-[\\d]{2}$" } }, "end": { "type": "string", "required": true, "constraints": { "regEx": "^[\\d]{4}-[\\d]{2}-[\\d]{2}$", "sameDayAllowed": false } } } }, },

MichaelHanna · ‎02.08.2021

Hallo @ceeage , um deine Daten via API abzurufen, musst du dich zunächst authentifizieren. Die Authentifizierung nutzt den sog. "OAuth" workflow. Hierbei ist die redirect_uri die Adresse, die bei der erfolgten Authentifizierung aufgerufen wird. Du kannst die redirect_uri frei wählen, sie muss aber in den Einstellungen deines API Keys und in deinem Befehl identisch sein. Für Testzwecke bietet es sich an, als redirect_uri "http://localhost:4200/" (ohne Anführungszeichen) zu verwenden. Bei der Nutzung der API über eine andere Applikation wird meist verlangt, eine bestimmte redirect_uri zu verwenden. Hast du schon in die Dokumentation auf dem Developer Portal reingeschaut? Dort haben wir eine Anleitung für die Authentifizierung: https://developer.viessmann.com/de/doc/authentication Ansonsten kann ich dir auch empfehlen, den Sample Code aus @nerixs Beitrag zu testen (Thanks nerixs!) Den ReCaptcha kannst du in den Einstellungen zum API Key aus- und einschalten (während des Erstellens oder beim nachträglichen editieren). Aus Sicherheitsgründen empfehlen wir, ReCaptcha einzuschalten, für die Automatisierung ist das Captcha allerdings abzuschalten. Gruß, Michael

MichaelHanna · ‎02.08.2021

@nerixs , Thanks a lot for sharing a sample code to support others getting started and doing their first API call! Much appreciated!

MichaelHanna · ‎02.08.2021

Hi @prior_philip & @phildaub23 , We have checked with our development team and did testing on the mentioned issue, but could not find any bugs on the logic. After reaching limits, requests are not counted at all so they can’t lead to extending ban. If the issue still occurs on your side, please contact me directly via PM and provide us with steps for reproducing the issue, as well as your user id (login name) and your client id (API key) to remove the >24h ban. Best, Michael

MichaelHanna · ‎15.07.2021

Update: The old API key is now disabled. For further using the API, please go on the Developer Portal to use you own personal API key.

MichaelHanna · ‎15.07.2021

Hallo @phildaub23, das Feature heating.solar.power.production samt einiger anderer Features sind nun in der Basic Version der API verfügbar. Weitere Infos dazu findest du in unserem Changelog: https://developer.viessmann.com/de/doc/changelog Das ist besonders, um den Nutzern einen möglichst nahtlosen Übergang vom alten API client hin zum Developer Portal mit persönlichem API client zu ermöglichen.

MichaelHanna · ‎15.07.2021

Hi @thetrueavatar, referring to your initial post in this thread, we recently added some features that were missing to the basic version of the API. The information we just shared on the Change Log within the Documentation: https://developer.viessmann.com/de/doc/changelog This is especially to provide you with a smooth transition switching from the old API client to the Developer Portal with your own personal API keys. Best, Michael

MichaelHanna · ‎15.07.2021

Hi @nerixs , as already mentioned in my other post, we recently added some features that were missing to the basic version of the API. The information we just shared on the Change Log within the Documentation: https://developer.viessmann.com/de/doc/changelog This is especially to provide you with a smooth transition switching from the old API client to the Developer Portal with your own personal API keys. Best, Michael

MichaelHanna · ‎15.07.2021

Hi @AndreasP @nerixs , we recently added some features that were missing to the basic version of the API. The information we just shared on the Change Log within the Documentation: https://developer.viessmann.com/de/doc/changelog This is especially to provide you with a smooth transition switching from the old API client to the Developer Portal with your own personal API keys.

MichaelHanna · ‎14.07.2021

@upset I appreciate your feedback! That was not the intention with the formulation of "unauthorized". But I like your formulation and will consider it 🙂

MichaelHanna · ‎14.07.2021

@bvdp glad to hear that. You're welcome 🙂

MichaelHanna · ‎14.07.2021

Hi @nerixs @upset , about the "missing" data points compared to the old / unauthorized client, we are happy to receive your feedback and are currently working on a solution to support you on your requests. I hope you and the other developers / API enthusiasts can have a bit more patience. However, pressuring with using on local processing solutions is what I believe not the right approach. We are aware that there are other solutions available that work directly via the communication buses. But please be aware that is not supported by us, whereas with the API, we want to provide an authorized, supported and secure way of system integration. So, let's work together on a great developer and API experience 🙂

MichaelHanna · ‎14.07.2021

Hi @bvdp , You need to have the same Redirect URI also in settings of the API client. Otherwise you will get an error. Please check your Redirect URI within your client to match with the one you are using to obtain the access token. Best, Michael

MichaelHanna · ‎14.07.2021

Hi @bvdp, here is a short explanation about Redirect URIs: Redirect URIs are used to redirect the user to your application after successful login at our site has been performed. The URI must be a callback URI to your application. Usually only one URI is required but you may setup more than one, for example, if you have multiple environments with differing base URL. Basically, it depends on your application what the Redirect URI should be. Within the examples given in the documentation, the Redirect URI "http://localhost:4200/" is used, which basically is a link to your local environment. If you just want to obtain the access token, you can follow the steps within example in the documentation and use the same Redirect URI. Hope this helps.

MichaelHanna · ‎14.07.2021

Hi, the URL you are referring to is deprecated. For getting information on your installation, please use the URL https://api.viessmann.com/iot/v1/equipment/installations We refer to this endpoint within the overview for the IoT section: https://developer.viessmann.com/en/doc/iot/overview This endpoint should provide you with all relevant information on your installation, especially the installation ID. You can also optionally add the query parameter ?includeGateways=true, to receive information about the gateway and device within the same call.

MichaelHanna · ‎14.07.2021

Hello, could you share an example of what you are trying to call using the token obtained by your own key (for which you are receiving an error)? In general, if you want to for example request the features of your device with your own key, this should work using the call curl -X GET https://api.viessmann.com/iot/v1/equipment/installations/{{installationId}}/gateways/{{gatewaySerial}}/devices/{{deviceId}}/features Best, Michael

MichaelHanna · ‎14.07.2021

@thetrueavatar your second assumption is correct. The API key you are currently using within your pugin will be disabled. So every user will need their own personal key, which can be obtained via the Developer Portal. I assume there is a difference in the authentication compared to the old key. The authentication is described here: https://developer.viessmann.com/en/doc/authentication. However, the API itself is still the same as before, except for current availability of certain feature, as explained before. Let me know if you have further questions! Best, Michael

MichaelHanna · ‎14.07.2021

Hi @thetrueavatar , I'm happy to hear you are working on integrating the new API! The heating curve feature is currently not available via the basic version of the API. But similar to the other threads about "missing" data points compared to the old / unauthorized client, we are happy to receive your feedback and are currently working on a solution to support you on your requests. I hope you and the other developers / API enthusiasts can have a bit more patience. Concerning setting data for e.g. programs or modes, there shouldn't be any changes. Please try it out in the way you are used to and let me know if there are any problems. Best, Michael

MichaelHanna · ‎12.07.2021

In order to keep our API stable into the future we must therefore shut down access to any old API keys that were not obtained through the Viessmann Developer Portal. On July 15th 2021, the access to old API keys will no longer be possible. The Developer Portal offers great benefits for both Developers and End-users: Easy to create an account and generate a new API key Continued access to heating system data for development of new applications Full documentation around our API to help you get started First-level support to answer any queries you may have And more to come! What must you do? If you are using an old API client, which you have not created through the Developer Portal and you are a: Developer Check your plugin to assure that it is working with the authorization flow, described here: https://developer.viessmann.com/en/doc/authentication. Every user will need their own API key to access their device. This means sharing one API key will not be possible anymore and users will need to have their own API key for continued access to data. Some data points that were accessible through the old API client will not be accessible through the new API client. Make sure to check the list of features provided in the documentation: https://developer.viessmann.com/en/doc/iot/data-points End user If you are using a 3rd party application to connect to your heating device, you need to go on the Developer Portal to create your own API key. This will be your personal key, which you need to access your device. We are pleased there has been so much demand for use of our API. We want to invite you to continue to develop your applications, so please carefully follow the instructions included here.

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.

Climate Solutions Community

Deine Aktuellen Statistiken

Re: Betreff: Missing data point heating.burners.0....

Re: Betreff: Wrong type in heating.power.consumpti...

Re: Time window problem when banning.

Re: Daten Energiebilanz zu Gasverbrauch

Re: Hilfe bei Change End Date heating.operating.pr...

Re: Betreff: API Abfragen - Ersteinrichtung - ich ...

Re: To help get started.

Betreff: Q&A Viessmann API

Betreff: Viessmann APIs - important information

Re: API Datenpunkt Solarthermie Energieproduktion

Re: Betreff: Endpoint missing and writing method n...

Re: Betreff: Missing access points.

Re: Betreff: Fehlende Datenpunkte

Re: Betreff: Missing access points.

Re: Redirect URIs

Re: Betreff: Missing access points.

Re: Redirect URIs

Re: Redirect URIs

Re: Betreff: Endpoint missing and writing method n...

Re: Betreff: Endpoint missing and writing method n...

Re: Betreff: Endpoint missing and writing method n...

Re: Endpoint missing and writing method not quiet ...

Viessmann APIs - important information

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.

Weitersurfen