Climate Solutions Community

I'm using the (new) API for a couple of days now with such a request: "https://api.viessmann.com/iot/v1/equipment/installations/"+ installationID +"/gateways/" +gatewaySerial + "/devices/0/features?regex=heating.(sensors.temperature.outside%7Cdhw.(oneTimeCharge%7Csensors.temperature.hotWaterStorage%7Cpumps.circulation))%7Cventilation.operating.programs.active"   Why does the order of data entries in the return change? ( That happened this morning July 2nd between 03:00 and 11:00  UTC +2). The sequence in the returned string was and still is not inline with the request, also the number of data entries is 5 instead of 4. ... Mehr anzeigen

I'm trying to send a command via the API, for example I want to activate the feature "oneTimeCharge". I tried to send such POST request:   https://api.viessmann-platform.io/iot/v1/equipment/installations/My-Installation_ID/gateways/My-Gateway_Serial/devices/0/features/heating.dhw.oneTimeCharge/commands/activate    Sending the above with a valid  Bearer Token does return:   {     "viErrorId": "req-06063841ce214195b3fa08643a51cd60",     "statusCode": 422,     "errorType": "VALIDATION_ERROR",     "message": "VALIDATION_ERROR",     "validationErrors": [         {             "path": [                 "commandBody"             ],             "type": "any.invalid",             "message": "invalid value, most likely wrong format"         }     ],     "extendedPayload": {         "commandBody": "EMPTY_MODEL"     } }   or with the header Content-Type="application/x-www-form-urlencoded" {     "viErrorId": "req-25befbaad52e473c921fe9a0e8439be7",     "statusCode": 500,     "errorType": "INTERNAL_ERROR",     "message": "Internal server error" }     Where is my mistake? ... Mehr anzeigen

After getting my API-Token (and refreshing it) I stumbled on the following questions:   -Since the number of API-Calls are limited the use a single call for each requested value is not the intended way, how shall we concentate multiple requests in one API-Call? An example of such a request on the Portal would help users to create such calls, which in turn would reduce the load on your server.   -Currently I am using  getHeatingBurnerStatistics("hours") and getHeatingBurnerStatistics("starts"), however both are not listed on the Developer Portal (Tab IOT). Are these the ones that are no longes accesible in the new API. ... Mehr anzeigen

With the help of @MichaelHanna I was able to get my first API token. Thanks for that!   Now I do have some follow up questions:   Refresh Token: I noticed that the Refresh Token stays the same. Is that true for all the time? Regarding the documentation for refreshing a token I do suggest to use the scope  IoT%20User%20offline_access in Step 1 as well, that way the step of refreshing the API Token is done more easily.   Usage of API calls: In the Section IOT you show examples on how to get InstallationID etc. Those examples are using https://api.viessmann.com/iot/v1 will that remain possible after July 15th? I guess not, otherwise, we would not need an AccessToken. Only in the section Service documents a Version 3 is stated. Doing a request on those just returns. {     "startedAt": "2021-06-18T12:24:21.567Z",     "version": "3.4.0" } How should one get a document with that?           ... Mehr anzeigen

I am observing problems getting the access token as described in the developer portal.   Intitially I am trying to get the token manually by http requests in order to understand the procedure, the final goal is to implement the whole procedure into openHAB using rules and later maybe a complete binding (i.e. create a standard interface from openHAB to the Viessmann API useable for others as well).   My current problem/question:   I managed to get past Step 1 and received a code using the posted http request like: https://iam.viessmann.com/idp/v2/authorize?client_id=my_oauth_client_id&redirect_uri=http://localhost:4200/&response_type=code&code_challenge=my_code_challenge&scope=IoT%20User  (my_oauth_client and my_code_challenge are replaced with my actual values). Using the received code I posted: https://iam.viessmann.com/idp/v2/token?client_id=my_oauth_client&redirect_uri=http://localhost:4200/&code_verifier=my_code_challenge&code=my_received_code I used the same string for My_code_challenge in both cases (in my understanding without setting code_challenge_method this should be correct). From such I always get: {"error":"invalid-authorization-request"}   What am I doing wrong? I tried to send the second request as fast as possible (at least within a minute). Am I to slow? The developer portal showed only a cURL example for the second request, is my selfmade https string wrong? .... As a follow up question, the to be received API token has a setting of "expires_in": 3600  Is that seconds or minutes? ... Mehr anzeigen