Climate Solutions Community

Hallo @Bjoern77 ,   hast du es schon mit dem Feature heating.solar.power.production versucht? Das Feature gibt dir die Werte für Tag, Woche, Monat und Jahr zurück.   Gruß,   Michael ... Mehr anzeigen

Hallo @Prinz-ip ,   die Registrierung neuer Client IDs ist nicht ausgesetzt und du müsstest dir einen eigenen Client erstellen können. Bitte prüfe es nochmal, ggf. hilft es, wenn du dich vorab von deinem Viessmann Account aus- und wieder einloggst.   Gruß,   Michael ... Mehr anzeigen

Hi @DMy , @Linda1406,   Ich habe erfahren, dass im nächsten bzw. übernächsten Update der ViCare das hier beschriebene Thema behoben wird.   Es ist also in Arbeit 🙂   Gruß,   Michael ... Mehr anzeigen

Hallo @Linda1406 ,   wenn du das Feedback bereits über die Funktion in ViCare weitergegeben hast, dann wurde es bereits an die richtigen Teams weitergeleitet und sich darum gekümmert. Du brauchst hier also nichts weiter zu tun.   Ansonsten geht es in diesem Teil des Forums um die API (Application Programming Interface, also Programmierschnittstelle) von Viessmann. Falls du mehr Infos hierzu haben möchtest, kannst du gerne unser Developer Portal besuchen: https://developer.viessmann.com. Ansonsten stehen wir dir zu diesem Thema hier gerne zur Verfügung 🙂   Viele Grüße,   Michael ... Mehr anzeigen

@jborup , could you please check once more within ViCare and provide me the information about errors shown in the app? Are there errors which are not shown in the API? ... Mehr anzeigen

@nerixs ,   if you use the endpoint https://api.viessmann.com/iot/v1/events-history/events?gatewaySerial={{gatewaySerial}}&eventType=device-error, you will get a response similar to this:   {     "data": [         {             "eventType": "device-error",             "gatewaySerial": "{{gatewaySerial}}",             "body": {                 "errorCode": "05",                 "deviceId": "0",                 "modelId": "CU401B_S",                 "active": false,                 "equipmentType": "Boiler",                 "errorEventType": "Error",                 "errorDescription": "Fault EEV"             },             "createdAt": "2019-09-19T08:40:42.807Z",             "eventTimestamp": "2019-09-19T08:40:27.000Z",             "editedBy": "system",             "origin": null         },         {             "eventType": "device-error",             "gatewaySerial": "{{gatewaySerial}}",             "body": {                 "errorCode": "05",                 "deviceId": "0",                 "modelId": "CU401B_S",                 "active": true,                 "equipmentType": "Boiler",                 "errorEventType": "Error",                 "errorDescription": "Fault EEV"             },             "createdAt": "2019-09-19T08:40:15.038Z",             "eventTimestamp": "2019-09-19T08:39:59.000Z",             "editedBy": "system",             "origin": null         }     ],     "cursor": {         "next": ""     } }   Notice that I filtered the response by eventType = device-error to only receive specific events. You receive the errorCode and the attribute "active" determines an an active or not active error. As the same error (05) was first active and then changed to not active, this shows that the error has been solved.   For further infos please check the documentation: https://developer.viessmann.com/en/doc/events-mw-iot/v1 ... Mehr anzeigen

Hi @nerixs ,   we added new features to the list of features. You can find them in the feature overview list: https://developer.viessmann.com/en/doc/iot/data-points and the changelog: https://developer.viessmann.com/en/doc/changelog   Best,   Michael ... Mehr anzeigen

Hi @AndreasP ,   you already observed that we are currently working on restructuring some of our features. We added the recent feature updates now in the changelog https://developer.viessmann.com/en/doc/changelog and the feature overview: https://developer.viessmann.com/en/doc/iot/data-points   We are also working on providing relevant information in a timely manner.  ... Mehr anzeigen

Hello @SebHH ,   thanks for the patience and sharing your case!   We are still in the trial / initial stage with the public API. Therefore, individual systems, such as fuel cells, are not yet supported by this.   We do not plan to make all the features that were available before the public API available again in the same form and without a clear purpose. However, your list helps us identifying the need more precisely. I'm happy to take your request for additional features, even though for the time being, I cannot tell you if/how additional features will be made available.   @nerixs , for errors and other events, you can check our "Events" endpoint, which is documented here: https://developer.viessmann.com/en/doc/events-mw-iot/v1   Best regards,   Michael ... Mehr anzeigen

Hallo @badenweisser ,   danke für die Geduld und das Teilen deines Falls!   Mit der public API befinden wir uns noch im Trial- / Anfangsstadium. Daher werden zur Zeit einzelne Systeme, wie z.B. Brennstoffzelle, hierüber noch nicht untersützt.   Könntest du in Sachen Funktionen, die fehlen, noch genauer sein und die für dich relevanten Features spezifieren? Das würde helfen, den Bedarf genauer zu erkennen. Wir planen nicht, sämtliche Features, die vor der offiziellen API verfügbar waren, in gleicher Form und ohne klaren Verwendungszweck wieder bereit zu stellen.   Schöne Grüße,   Michael ... Mehr anzeigen

Hi davids1 ,    you are right the response contains the the URL "https://api.viessmann-platform.io". So this is not the issue as I first expected.   There has not been any migration to new servers or similar recently. The only thing that happened is that an old API client has been disabled. The API itself, as well as all accounts, are still the same as before. So there should be no need to delete your API client and especially there is no need to delete your account.   Are the values for the available in your ViCare app? Could you provide me your GatewaySerial (via DM if you like) so we can have a closer look? ... Mehr anzeigen

@jborup, concerning the error messages, you can check our "Events" endpoint, which is documented here: https://developer.viessmann.com/en/doc/events-mw-iot/v1   If you want to know when your system is on dhw only and when it is on dhw and heating, you can use the operating mode features:   heating.circuits.N.operating.modes.active - Shows current active operating mode on the device and provides command to change it.   I do not think that for this, information about valves will be necessary. ... Mehr anzeigen

Thanks for the information! That was also my assumption: "Heizkreis 1" being the default name for the heating circuit, which corresponds to an empty value for the name property of the heating circuit feature. ... Mehr anzeigen

@andreas13 there have been some adjustments made that might have also impacted your issue. Happy to hear that it works for you now 🙂 ... Mehr anzeigen

Hi @nerixs ,   Thanks for the feedback. We will have a look at the consumption features. ... Mehr anzeigen

Hi @JensDorfmueller ,   for errors and other events, you can check our "Events" endpoint, which is documented here: https://developer.viessmann.com/en/doc/events-mw-iot/v1 ... Mehr anzeigen

Hi @andreas13 ,   Could you provide a screenshot of ViCare and the name that is shown there? ... Mehr anzeigen

Hi @MK176 ,   This forum is open for all topics around the API and developing, although our goal is to also encourage discussions that go beyond feature requests 🙂   As stated in the other threads, I'm happy to take your request for additional features, even though for the time being, I cannot tell you if/how additional features will be made available.   With the public API, we are at the beginning and start to build up the service for our users. Our plan is to enhance our offering, also in terms of features that are provided. ... Mehr anzeigen

Hi @bvdp ,   Thank you for your request! We are always happy about finding out more about your and other user's use cases with our API.   Unfortunately, I cannot give you an answer about if/how additional features like the one you mentioned will be available.    With the public API, we are at the beginning and start to build up the service for our users. Our plan is to enhance our offering, also in terms of features that are provided. ... Mehr anzeigen

Hi @Davids ,   Thank you for your feedback and the request!   With the public API, we are at the beginning and start to build up the service for our users. Our plan is to enhance our offering, also in terms of features that are provided.   To better understand your use case, could you specify how this features helps you in monitoring your system's performance?   Best,   Michael ... Mehr anzeigen

Hi @davids1 ,   both features heating.circuits.N.temperature and heating.circuits.N.sensors.temperature.supply are still be available.   From the response you posted I can see you are using "https://api.viessmann-platform.io/". Please use "https://api.viessmann.com/" and try to call both features. ... Mehr anzeigen

Hi @jborup ,   the key "materialNumber" identifies the product you are looking for. The materialNumber is equal to the first 7 digits of your boiler serial number.   You can identify your boiler serial number with the endpoint https://api.viessmann.com/iot/v1/equipment/installations?includeGateways=true and searching for "boilerSerial".   Best,   Michael ... Mehr anzeigen

Hi @jborup,   Thanks for the further explanations! It seems your installation is configured in a special (or at least not in the default) way. Maybe it makes sense to check the installation in general to make sure this is not the cause for any other issues? For other / general topics, you can also use other sections in this forum 🙂   Concerning the error messages, you can check our "Events" endpoint, which is documented here: https://developer.viessmann.com/en/doc/events-mw-iot/v1   It should also provide information about errors. Let me know if this also covers the E0 error for you. ... Mehr anzeigen

Hallo @sun_nerd ,   danke für das Teilen der Infos zu deiner Lösung!   Mit der public API befinden wir uns noch im Trial- / Anfangsstadium. Daher werden zur Zeit einzelne Systeme, wie z.B. PV-Systeme und Batteriespeicher, hierüber noch nicht untersützt.   Könntest du in Sachen Funktionen, die fehlen, noch genauer sein und die für dich relevanten Features spezifieren? Das würde helfen, den Bedarf genauer zu erkennen. Wir planen nicht, sämtliche Features, die vor der offiziellen API verfügbar waren, in gleicher Form und ohne klaren Verwendungszweck wieder bereit zu stellen.   Schöne Grüße,   Michael ... Mehr anzeigen

Hi @davids1 ,   there was a change in the heting.power.consumption feature, which made it unavailable. We are working on bringing back the feature to the public API.   Please also make sure to follow the advice of @BrechtM and have a look at the available features listed here: https://developer.viessmann.com/en/doc/iot/data-points ... Mehr anzeigen

Hi @TigerVI90 ,   have you tried changing the schedule through ViCare, does this work?   For testing, please try other modes in your request, e.g. intensive or reduced. ... Mehr anzeigen

@DMy @Linda1406 ,   für Probleme, die direkt in der ViCare App vorkommen, könnt ihr gerne die Feedback Funktion in der App nutzen. Das macht die Klärung einfacher und leitet das Problem dirket an die richtigen Team weiter.   Sollte es hier ebenfalls Probleme in der API geben, könnt ihr diese hier gerne ergänzen.   Gruß,   Michael ... Mehr anzeigen

Hi @jborup ,   is the error 502 still existent? How often do you experience the error? In general, the internal server error is not related to your call or the function you are using. ... Mehr anzeigen