Alle Announcements-Beiträge

Lösung zu “PACKAGE_NOT_PAID_FOR”

CustomerCareChris — Fri, 22 May 2026 08:31:13 GMT

Liebe Viessmann-API Nutzer,

im Zusammenhang mit den Erfahrungen bei API-Antworten mit „PACKAGE_NOT_PAID_FOR“ wurde gestern ein Fix bereitgestellt, von dem wir ausgehen, dass er das aufgetretene Problem behebt.Vielen Dank, dass ihr das Thema mit unserer Developer-API an uns herangetragen habt.

Sollten weiterhin Probleme bestehen, wendet euch bitte an developer@viessmann-climatesolutions.com.

Bitte gebt dabei eure Gateway-Seriennummer oder die Installations-ID an, damit wir euch effektiv unterstützen können.

Euer Viessmann-API Team

Dear all,

In reference to experiences from API responses with “PACKAGE_NOT_PAID_FOR” a fix has been deployed yesterday which we believe should mitigate the issue experienced.
Thank you for bringing forward the issue with our Developer API.

If any issues persist, please reach out to developer@viessmann-climatesolutions.com.

Please include your gateway serial number or installation-ID, so we would be able to support effectively on your issue.

Your Viessmann-API Team

Betreff: Domain Change for the Viessmann API

CustomerCareMichael — Thu, 04 Sep 2025 13:35:39 GMT

Hi @jochensch44 , du müsstest natürlich auch in deinem genutzten Code schauen, dass bei den API-Aufrufen nur noch die neue Domain genutzt wird. Wenn du ein Plugin von Home Assistant, ioBroker oder ähnlichen verwendest, stelle sicher, dass dort die Anpassungen vorgenommen wurden, bzw. dass du auf die neueste Version updatest.

Gruß

Michael

Betreff: Domain Change for the Viessmann API

jochensch44 — Sun, 24 Aug 2025 18:23:51 GMT

Hallo @CustomerCareMichael, vielen Dank für die Rückmeldung. Wenn ich es richtig verstehe, füge ich beim API Key die neue URI hinzu (siehe Screenshot). Passt das dann so?

Vielen Dank und viele Grüße

Jochen

Betreff: Domain Change for the Viessmann API

CustomerCareMichael — Wed, 13 Aug 2025 05:45:43 GMT

Hallo @jochensch44 , eine neue Redirect URI kannst du im Dashboard Bereich des Developer Portals einstellen: https://app.developer.viessmann-climatesolutions.com/

Dort wird unter "Your clients" dein API Key angezeigt. Daneben befindet sich ein Knopf zum Editieren des API Keys, unter anderem lassen sich dort neue Redirect URIs einstellen.

Probier es einmal aus. Ich hoffe, es hilft dir weiter.

Gruß,

Michael

Betreff: Domain Change for the Viessmann API

jochensch44 — Sun, 27 Jul 2025 12:35:16 GMT

Hallo, bin ich der einzige der noch nicht gefunden hat wie ich das im ioBroker Adapter anpassen kann.

Vielen Dank für Eure Unterstützung.

Betreff: Domain Change for the Viessmann API

jochensch44 — Wed, 23 Jul 2025 19:05:14 GMT

Hallo,

ich nutze aktuell in iobroker den Adapter viessmannapi.0

Leider kann ich hier nirgendwo die neue API URI ändern.

Wie ist das vorgehen um auch weiterhin in iobroker auf meine Daten zugreifen zu können.

Vielen Dank!

Domain Change for the Viessmann API

CustomerCareMichael — Fri, 11 Jul 2025 05:55:23 GMT

As part of the continuous optimization and modernization of our services, we are currently in the process of switching our applications and websites to the new domain viessmann-climatesolutions.com. This change will also affect the domains for resources such as the Developer Portal and the API Documentation.

For your integrations, this requires the following technical updates:

1. API Endpoints:

The base URI for all API calls is changing. You need to update your code to use the new domain.
Old: https://api.viessmann.com/...
New: https://api.viessmann-climatesolutions.com/...

2. Identity and Access Management (IAM):

The domain for our identity services will also be updated. This needs to be updated in your application to ensure authorization continues to function correctly.
Old: https://iam.viessmann.com
New: https://iam.viessmann-climatesolutions.com

3. API Response Body:

The uri value within the JSON response from the Features API (/iot/v2/features/...) will reflect the new viessmann-climatesolutions.com domain in the future.

The API endpoints under the new domain are already available, and we ask you to please use the new addresses with immediate effect. The old viessmann.com domain will be deactivated during Q4/2025, by the end of the year at the latest.

We understand that these changes may require adjustments to your existing code. To assist you in this process, we recommend referring to the API documentation.

Support Channels:

If you have any questions or require further assistance regarding these updates, please don't hesitate to reach out here in our forum or send an email to developer@viessmann-climatesolutions.com.

We appreciate your understanding and cooperation as we continue to improve the Viessmann API.

Important Update to Viessmann API (effective April 30, 2025)

CustomerCareMichael — Mon, 14 Apr 2025 08:33:31 GMT

Dear Viessmann Developer Portal users,

We are announcing two important upcoming changes to the Viessmann API. These updates, effective 30.04.2025, aim to improve the API's functionality, enhance consistency, and streamline the development process for our users.

1. IoT Feature Renaming and Standardization

This update introduces a breaking change to the Viessmann API's IoT features, primarily involving the renaming and standardization of several data point identifiers. These changes are necessary to improve platform consistency and align with ongoing updates. Existing integrations using the legacy feature names will cease to function correctly. Please note that some of these changes were previously announced in August 2024.

Impact:

This is a breaking change. Applications relying on the affected IoT feature names will require immediate updates to maintain functionality.
Affected device types: Buffer storage tank, Heating, Domestic hot water (DHW), Fuel cell, Heat pump, and Ventilation.

Reason for Change:

These changes are driven by platform updates aimed at enhancing consistency and standardization across our IoT features.

Detailed Changes:

The following IoT feature names have been updated:

Buffer storage tank:
- heating.buffer.charging.level.bottom → heating.bufferCylinder.charging.level.bottom
- heating.buffer.charging.level.middle → heating.bufferCylinder.charging.level.middle
- heating.buffer.charging.level.top → heating.bufferCylinder.charging.level.top
- heating.buffer.charging.level.total → heating.bufferCylinder.charging.level.total
- heating.buffer.sensors.temperature.main → heating.bufferCylinder.sensors.temperature.main
- heating.buffer.sensors.temperature.top → heating.bufferCylinder.sensors.temperature.top

Replace heating.buffer.* with heating.bufferCylinder.*

Heating:

heating.circuits.N.operating.programs.summerEco → heating.circuits.N.operating.programs.reducedEnergySaving
heating.co2.saving → heating.co2.saving.raw

Domestic hot water (DHW):
- heating.dhw.comfort → heating.dhw.operating.modes.comfort / .eco / .active
- heating.dhw.sensors.temperature.hotWaterStorage.bottom → heating.dhw.sensors.temperature.dhwCylinder.bottom
- heating.dhw.sensors.temperature.hotWaterStorage.midBottom → heating.dhw.sensors.temperature.dhwCylinder.midBottom
- heating.dhw.sensors.temperature.hotWaterStorage.middle → heating.dhw.sensors.temperature.dhwCylinder.middle
- heating.dhw.sensors.temperature.hotWaterStorage.top → heating.dhw.sensors.temperature.dhwCylinder.top
- heating.dhw.sensors.temperature.hotWaterStorage → heating.dhw.sensors.temperature.dhwCylinder

Replace *.hotWaterStorage.* with *.dhwCylinder.*

Fuel cell:
- heating.fuelCell.operating.modes.active → fuelCell.operating.modes.active
- heating.fuelCell.operating.modes.chimneySweeperMode → fuelCell.operating.modes.chimneySweeperMode
- heating.fuelCell.operating.modes.ecological → fuelCell.operating.modes.ecological
- heating.fuelCell.operating.modes.economical → fuelCell.operating.modes.economical
- heating.fuelCell.operating.modes.energyControlled → fuelCell.operating.modes.energyControlled
- heating.fuelCell.operating.modes.heatControlled → fuelCell.operating.modes.heatControlled
- heating.fuelCell.operating.modes.holidayWithFuelCellOff → fuelCell.operating.modes.holidayWithFuelCellOff
- heating.fuelCell.operating.modes.holidayWithFuelCellOn → fuelCell.operating.modes.holidayWithFuelCellOn
- heating.fuelCell.operating.modes.maintenance → fuelCell.operating.modes.maintenance
- heating.fuelCell.operating.modes.party → fuelCell.operating.modes.party
- heating.fuelCell.operating.modes.standby → fuelCell.operating.modes.standby
- heating.fuelCell.operating.phase → fuelCell.operating.phase
- heating.fuelCell.power.production → fuelCell.power.production
- heating.fuelCell.sensors.temperature.return → fuelCell.sensors.temperature.return
- heating.fuelCell.sensors.temperature.supply → fuelCell.sensors.temperature.supply
- heating.fuelCell.statistics → fuelCell.statistics

Replace heating.fuelcell.* with fuelCell.*

Heat pump:
- heating.scop.dhw → heating.spf.dhw
- heating.scop.heating → heating.spf.heating
- heating.scop.total → heating.spf.total

Replace heating.scop.* with heating.spf.*

Ventilation:
- ventilation.operating.programs.comfort → ventilation.quickmodes.comfort
- ventilation.operating.programs.eco → ventilation.quickmodes.eco
- ventilation.operating.programs.forcedLevelFour → ventilation.quickmodes.forcedLevelFour
- ventilation.operating.programs.holiday → ventilation.quickmodes.holiday
- ventilation.operating.programs.levelFour → ventilation.levels.levelFour
- ventilation.operating.programs.levelOne → ventilation.levels.levelOne
- ventilation.operating.programs.levelThree → ventilation.levels.levelThree
- ventilation.operating.programs.levelTwo → ventilation.levels.levelTwo
- ventilation.operating.programs.silent → ventilation.quickmodes.silent

Replace ventilation.operating.programs.* with ventilation.operating.state / ventilation.quickmodes.* / ventilation.levels.*

2. API Endpoints Update

We are replacing several API endpoints with their current versions.

Affected Endpoints:

/iot/v1/equipment/installations/{installationId}/gateways/{gatewaySerial}/devices/{deviceId}/features will be replaced with /iot/v2/features/installations/{installationId}/gateways/{gatewaySerial}/devices/{deviceId}/features
/iot/v1/equipment/installations/{installationId}/gateways/{gatewaySerial}/features will be replaced with /iot/v2/features/installations/{installationId}/gateways/{gatewaySerial}/features
/iot/v1/equipment/installations/{installationId}/features will be replaced with /iot/v2/features/installations/{installationId}/features
/iot/v1/features will be replaced with /iot/v2/features

Important Notes:

The previous versions (/iot/v1/...) of the listed endpoints will be removed entirely on 30.04.2025. As a result, any existing integrations using these endpoints will cease to function.
The new endpoints (/iot/v2/...) function identically to their predecessors. There are no changes to the request parameters, response formats, or any other functional aspects.

Action Required (For Both Updates):

For IoT Feature Renaming: Update your API integrations to use the new feature names. The renamed IoT features are already available via the API for testing and implementation. Legacy names will be fully deprecated and removed after this date.
For API Endpoints Update: Update your integrations to use the new API endpoints (/iot/v2/...). The new endpoints are already available for use.

We understand that these changes may require adjustments to your existing code. To assist you in this process, we recommend referring to the API documentation.

Support Channels:

If you have any questions or require further assistance regarding these updates, please don't hesitate to reach out here in the forum or send an email to developer@viessmann.com.

All the best

Michael from the Viessmann Developer Portal Team

Important changes in the Viessmann API IoT features

CustomerCareMichael — Fri, 06 Sep 2024 12:44:33 GMT

We have an important update regarding the Viessmann API, specifically concerning a change to some of our IoT features.

Starting from 2024-09-15, we will be changing the IoT features for several device types and migrating to the new naming nomenclature. This change will require you to update your existing API integration to ensure uninterrupted access to the relevant data.

These are the changes for each device type

Buffer storage tank:

heating.buffer.charging.level.bottom → heating.bufferCylinder.charging.level.bottom
heating.buffer.charging.level.middle → heating.bufferCylinder.charging.level.middle
heating.buffer.charging.level.top → heating.bufferCylinder.charging.level.top
heating.buffer.charging.level.total → heating.bufferCylinder.charging.level.total
heating.buffer.sensors.temperature.main → heating.bufferCylinder.sensors.temperature.main
heating.buffer.sensors.temperature.top → heating.bufferCylinder.sensors.temperature.top

Heating:

heating.circuits.N.operating.programs.summerEco → heating.circuits.N.operating.programs.reducedEnergySaving
heating.co2.saving → heating.co2.saving.raw

Domestic hot water (DHW):

heating.dhw.comfort → heating.dhw.operating.modes.active
heating.dhw.sensors.temperature.hotWaterStorage.bottom → heating.dhw.sensors.temperature.dhwCylinder.bottom
heating.dhw.sensors.temperature.hotWaterStorage.midBottom → heating.dhw.sensors.temperature.dhwCylinder.midBottom
heating.dhw.sensors.temperature.hotWaterStorage.middle → heating.dhw.sensors.temperature.dhwCylinder.middle
heating.dhw.sensors.temperature.hotWaterStorage.top → heating.dhw.sensors.temperature.dhwCylinder.top
heating.dhw.sensors.temperature.hotWaterStorage → heating.dhw.sensors.temperature.dhwCylinder

Fuel cell:

heating.fuelCell.operating.modes.active → fuelCell.operating.modes.active
heating.fuelCell.operating.modes.chimneySweeperMode → fuelCell.operating.modes.chimneySweeperMode
heating.fuelCell.operating.modes.ecological → fuelCell.operating.modes.ecological
heating.fuelCell.operating.modes.economical → fuelCell.operating.modes.economical
heating.fuelCell.operating.modes.energyControlled → fuelCell.operating.modes.energyControlled
heating.fuelCell.operating.modes.heatControlled → fuelCell.operating.modes.heatControlled
heating.fuelCell.operating.modes.holidayWithFuelCellOff → fuelCell.operating.modes.holidayWithFuelCellOff
heating.fuelCell.operating.modes.holidayWithFuelCellOn → fuelCell.operating.modes.holidayWithFuelCellOn
heating.fuelCell.operating.modes.maintenance → fuelCell.operating.modes.maintenance
heating.fuelCell.operating.modes.party → fuelCell.operating.modes.party
heating.fuelCell.operating.modes.standby → fuelCell.operating.modes.standby
heating.fuelCell.operating.phase → fuelCell.operating.phase
heating.fuelCell.power.production → fuelCell.power.production
heating.fuelCell.sensors.temperature.return → fuelCell.sensors.temperature.return
heating.fuelCell.sensors.temperature.supply → fuelCell.sensors.temperature.supply
heating.fuelCell.statistics → fuelCell.statistics

Heat pump:

heating.scop.dhw → heating.spf.dhw
heating.scop.heating → heating.spf.heating
heating.scop.total → heating.spf.total

Ventilation:

ventilation.operating.programs.comfort → ventilation.quickmodes.comfort
ventilation.operating.programs.eco → ventilation.quickmodes.eco
ventilation.operating.programs.forcedLevelFour → ventilation.quickmodes.forcedLevelFour
ventilation.operating.programs.holiday → ventilation.quickmodes.holiday
ventilation.operating.programs.levelFour → ventilation.levels.levelFour
ventilation.operating.programs.levelOne → ventilation.levels.levelOne
ventilation.operating.programs.levelThree → ventilation.levels.levelThree
ventilation.operating.programs.levelTwo → ventilation.levels.levelTwo
ventilation.operating.programs.silent → ventilation.quickmodes.silent

Migration Date

Starting 2024-09-15: You must update your integration to utilize the new endpoints.

Action Required

To ensure, you will not get any problems in your applications, please check and if necessary update your code and integrate the new IoT features before 2024-09-15. The renamed IoT features are already available via API.

Our support team will be happy to help you with any problems during the migration process.

Thank you for your understanding towards the changes and have fun and success with our updated API.

Endkundenbetreuung

PeterEhrt — Wed, 24 Jul 2024 10:40:08 GMT

Ich hatte am 15.7. als Antwort auf eine Mail von Viessmann wegen fehlender Energieeinsparung an usermarketing@viessmann.com gesendet,
Weil keine Antwort kam habe ich diese heute (24.7.) nochmal gesendet an info@viessmann.com.
Es kam als Antwort, dass Viessmann eine dezentrale Abwicklung über regionale Niederlassungen hat.
Ich habe also in der Niederlassung für Mannheim angerufen, bin aber in der nordhessischen Zentrale gelandet. In der Zentrale sagte man mir, dass Viessmann keine Endkundenbetreuung macht.
Super, hätte ich dies vorher gewusst hätte ich einen anderen Heizungsanbieter gewählt!
Ich schreibe dies als Hinweis für andere potentielle Kunden die noch keine Bestellung ausgelöst haben.

Wir suchen Young Talents – Empfehle unser Ausbildungs- und duales Studienprogramm deinen Freunden und Bekannten weiter!

CustomerCareChris — Wed, 06 Mar 2024 14:09:05 GMT

Du kennst jemanden in deinem Umfeld, der sich für eine Ausbildung oder ein duales Studium interessiert und bisher noch keine passende Möglichkeit für sich entdeckt hat? Wir haben für diesen Sommer noch spannende Ausbildungs- und duale Studienplätze zu vergeben und freuen uns darauf, neue Young Talents für Viessmann Climate Solutions zu gewinnen. Hilf uns dabei, Aufmerksamkeit bei potenziellen Bewerberinnen und Bewerbern zu erwecken – dein Einsatz ist für unseren gemeinsamen Erfolg entscheidend. Deshalb möchten wir euch gerne motivieren, unser Angebot über freie Young-Talents-Plätze mit Freunden, Familie sowie Bekannten zu teilen und freuen uns über eure Unterstützung.

Für folgende Duale Studiengänge suchen wir weitere Young Talents:

Ingenieurwesen - Elektrotechnik
Wirtschaftsingenieurwesen - Elektrotechnik
Softwaretechnologie

Innovativ und praxisnah: Spannende Events und Weiterbildung
Wenn es um die Planung der eigenen Zukunft geht, ist die Wahl des richtigen Ausbildungs- oder dualen Studienplatzes sehr entscheidend. Unser Young Talents Programm legt mit spannenden Onboarding-Events, wie der bekannten Projektwoche zu Beginn, sowie vielfältigen Community-Events den Grundstein zur Stärkung des Zusammenhalts und der Bildung eines Netzwerks. Neben Prüfungsvorbereitungskursen bieten wir umfangreiche Weiterbildungsmöglichkeiten wie zum Beispiel Präsentationstrainings, Produktschulungen oder auch Themen über den Tellerrand hinaus, wie ein Fahrsicherheitstraining, an. Zudem ermöglichen wir sehr gerne Einsätze an den deutschlandweiten sowie globalen Viessmann Climate Solutions Standorten – für viele junge Talente ist dies das absolute Highlight in ihrer Ausbildung/ihrem dualen Studium.

Weitere Informationen findest du in unserem Young Talents Bereich auf der Viessmann Climate Solutions Karriereseite.

Important Announcement: Switching to New Endpoint for Viessmann API Events History

CustomerCareMichael — Fri, 26 May 2023 08:51:55 GMT

We have an important announcement regarding the Viessmann API, specifically concerning the events history endpoint. We are excited to inform you that we will be switching to a new endpoint to enhance the functionality and reliability of this feature.

Starting from July 1, 2023, we will be deprecating the current endpoint for events history and migrating to a new endpoint that offers improved performance and additional capabilities. This change will require you to update your existing API integration to ensure uninterrupted access to the events history data.

Here are the key details you need to know:

New Endpoint: /iot/v2/events-history/installations/{id}/events

Deprecated Endpoint: /iot/v1/events-history/events

Migration Timeline:

July 1, 2023: The deprecated endpoint (/iot/v1/events-history/events) will be deactivated.
Starting July 1, 2023: You must update your integration to utilize the new endpoint (/iot/v2/events-history/installations/{id}/events) for retrieving events history.

Benefits of the New Endpoint:

The new events history endpoint offers the following advantages:

Improved performance: The new endpoint has been optimized for faster response times, ensuring a more seamless experience when fetching events history.
Enhanced filtering options: You can now leverage additional filtering parameters to narrow down your event queries based on specific criteria, allowing for more targeted and efficient data retrieval. The installation ID {id} is now part of the Endpoint URL.
Future-ready architecture: The new endpoint has been built on a modern and scalable infrastructure, ensuring its reliability and longevity for your application needs.

Action Required:

To ensure a smooth transition, we kindly request you to update your code and integrate the new events history endpoint (/iot/v2/events-history/installations/{id}/events) before July 1, 2023. This will ensure uninterrupted access to events history data for your applications.

Please refer to our updated API documentation, which will provide detailed information on how to migrate to the new endpoint, including any changes in request parameters or response formats.

Should you encounter any issues or require assistance during the migration process, please don't hesitate to reach out to our support team. We are here to help and ensure a seamless transition for your applications.

Betreff: Important adjustment in IoT features: Split heating circuits and domestic hot water

CustomerCareMichael — Tue, 17 Jan 2023 14:06:07 GMT

Hi, thanks for reaching out. The change was announced in November here as well as in the Changelog and the emailing that was sent out in December as well, forwarding to the news article in the Developer Portal.

For the new type of heating systems (type = E3), the operating modes of the heating circuit and of the domestic hot water (DHW) were split. To see/change the operating mode of the DHW, you now need to use the features heating.dhw.operating.modes.*. For example to check the currently active operating mode of the DHW, you now use heating.dhw.operating.modes.active. The new features for the DHW operating modes are

heating.dhw.operating.modes.active
heating.dhw.operating.modes.balanced
heating.dhw.operating.modes.comfort
heating.dhw.operating.modes.eco
heating.dhw.operating.modes.off

For further communication and if anything is not working, please use the other areas of the Developer area of this forum. Thanks for your understanding!

Best regards,

Michael

Betreff: Important adjustment in IoT features: Split heating circuits and domestic hot water

ArrowX — Mon, 16 Jan 2023 16:51:47 GMT

My home automation is also not working after the rollout of this breaking change in the API.

@CustomerCareMichael : Can you give an example on how to set the operating modes "dhw" and "dhwAndHeating" with the new API?

Betreff: Important adjustment in IoT features: Split heating circuits and domestic hot water

Lala_OK — Sun, 15 Jan 2023 09:13:22 GMT

What the hell is really going on?

Was zum Teufel ist wirklich los?

Betreff: Important adjustment in IoT features: Split heating circuits and domestic hot water

Reinhard4 — Sat, 14 Jan 2023 20:37:55 GMT

As of yesterday, or the day before, Home Assistant did no longer report the actual hot water temperatur.

The problem was in the are of "water_heater.vicare_water", showing the value Unknown.

I upgraded to HA 2023.1.4 today and the problem disappeared.

-Reinhard

Betreff: Important adjustment in IoT features: Split heating circuits and domestic hot water

BrechtM — Sat, 14 Jan 2023 16:00:15 GMT

Hi, is it possible this change has been implemented yesterday? It was not listed on the changelog but something seems to have changed.

I am having issues controlling my vitodens burner as I used to, as do other people controlling their boiler using home automation.

Important adjustment in IoT features: Split heating circuits and domestic hot water

CustomerCareMichael — Thu, 24 Nov 2022 08:38:23 GMT

In our API we have coupled heating circuits (HC) and domestic hot water (DHW) support closely together to keep the backwards compatibility between Legacy devices and devices based on our Viessmann One Base control platform, also called E3. Viessmann One Base provides the HCs and DHW as independent systems with a chance to access HC- and DHW-features as independent features.

What is being adjusted?

The planned adjustments brings the following changes to our IoT features:

adjust heating.circuits.N.operating.modes.* by removing existent DHW dependencies
remove heating.circuits.N.operating.modes.dhw* operating modes
adjust heating.circuits.N.operating.modes.active to only show the following states for the “value” property: auto, heating, cooling, heatingCooling or testMode

The DHW operating can in future be requested through the following new features:

introduce heating.dhw.operating.modes.off >> Shows whether the DHW is off
adjust heating.dhw.operating.modes.active >> Shows the current DHW operating mode with the possible states for the “value” property: balanced, comfort, eco, off

This change only affects our Viessmann One Base (E3) control platform (wifi integrated devices). For legacy devices, i.e. using a Vitoconnect, there are no changes. However, this also means, depending on the device, requesting and changing the DHW operating mode differs.

How to find out which device (legacy / One Base) is used?

To find which device you have, you can use the following request to check the devices of your installation: curl -X GET https://api.viessmann.com/iot/v1/equipment/installations/{{installationID}}/gateways/{{gatewaySerial}}/devices/

In the response, you find the list of devices, containing information about the type of device:

{
    "data": [
        {
            "gatewaySerial": {{gatewaySerial}},
            "id": {{deviceId}},
            "boilerSerial": {{boilerSerial}},
            "boilerSerialEditor": "DeviceCommunication",
            "bmuSerial": null,
            "bmuSerialEditor": null,
            "createdAt": "2020-11-16T07:06:56.267Z",
            "editedAt": "2022-10-27T11:16:06.670Z",
            "modelId": "E3_Vitodens_300_0421",
            "status": "Online",
            "deviceType": "heating",
            "roles": [
                "capability:backup;0002_HMU_VD3",
                "type:E3",
                "type:boiler",
                "type:product;Vitodens_300"
            ]
        },
    ]
}

The “roles” parameter lists the different types the device is assigned to. Here, you will find either the type:E3 or type:legacy. This information then tells you how to check the DHW operating modes.

When will this change take effect?

The adjustments will go live January 2023 (exact date will be added as soon as possible). From this date, you can only request the DHW operating mode for E3 using the described new way.

Electrifying changes to the Developer Portal

CustomerCareMichael — Thu, 17 Nov 2022 13:45:44 GMT

Whether it is our leading heat pumps, photovoltaics or battery storage, we at Viessmann are responding to our customers’ demands for more sustainable solutions. Naturally, we wish to extend the possibilities of these products to users of our Developer Portal.

Let’s get electrical

In addition to the Advanced package we now introduce a new “Electric” package.

It is a set of features that allows you to see how much electricity you are generating and where it is going. Gain full visibility over what your photovoltaic system is producing, how much is stored in your Vitocharge VX3 and how much you are sending back to the grid.

Pricing for every budget

In terms of pricing, we have made a few important changes that increase your options and flexibility:

You can now choose either
an annual subscription or a monthly plan for both the Advanced and the Electric package
For the Advanced package the annual subscription is charged on a monthly basis at just €11,98 per month, which is a savings of 40% compared to the monthly plan
The Electric package is priced at just €4.99 per month for an annual subscription or €7.98 when paying month-by-month

Learn more about our new features and pricing today.

Scheduled maintenance 11/16/2022

CustomerCareMichael — Mon, 14 Nov 2022 07:41:59 GMT

There is planned maintenance work on the Viessmann servers on 11/16/2022, 09:00PM to 10:00PM CET. During this time there may be a limitation of API functionality. This maintenance has no effect on your Viessmann heating system. It serves to improve our servers and thus also the API.