Loxberry Vitoconnect

[challo]

Danke! Ich habs gemerged und die Token/Auth Endpoints auch gleich auf v3 aktualisiert. Bitte mal prüfen ob Release 1.1.2. jetzt funktioniert. Bei mir sieht es gut aus.

[Flanki]

Hallo,

ich habe gestern nach dem letzten Update von Viessmann in deren App festgestellt, dass die Endpoints nun anscheinend entfernt wurden, wodurch ich keine Installationdetails mehr erhalten habe.

challo: ich habe in Github einen schnellen Fix commited (mglw. muss man alle Endpoints überprüfen)

https://api.viessmann-climatesolutions.com/documentation/static/changelog-2025

[elextricmax]

Bei mir ist auch seit kurzem Schluss mit den Abfragen.
Im Log ist das ersichtlich:

INFO: LoxBerry Version 3.0.1.3 ( is_arch_aarch64.cfg is_hwmodel_raspberry_pi_4_400.cfg is_raspberry.cfg )

INFO: Viessmann Vitoconnect Version 1.1.1

INFO: Loglevel: 3

ERROR: Status GetData: 410

ERROR: Response {"viErrorId":"req-f90e02a86bb04bc990f3f98ee60e5931","statusCode":410,"errorType":"GONE","message":"This endpoint has been deprecated and is no longer available. Sunset date: 2025-11-17T12:00:00.000Z Replacement: Endpoint in /iot/v2/features/","extendedPayload":{"sunsetDate":"2025-11-17T12:00:00.000Z","replacement":"Endpoint in /iot/v2/features/"}}

ERROR: Unable to get installation details -exiting

Vielleicht kann daraus jemand Schlüsse ziehen, woran die Kommunikation mit der API scheitert.

Möglicherweise hat sich die URL für die Authorization geändert.

In der Datei /webfrontend/htmlauth/defines.php finden sich diese Definitionen:
define ("authorize_URL", "https://iam.viessmann-climatesolutions.com/idp/v2/authorize");
define ("token_url", "https://iam.viessmann-climatesolutions.com/idp/v2/token");

Inder Online Dokumenation von Viessmann steht das drinnen:
URI: https://iam.viessmann-climatesolutio...p/v3/authorize
URI: https://iam.viessmann-climatesolutions.com/idp/v3/token

[wiggo87]

Is there already a solution?

[mantal]

What is needed to be done so my LoxBerry will work again?

[Marco74]

This was a quick and dirty change to make things work again for me using v2 calls. This is definitely not a final solution.

The original code only used the v2 for the Viessmann_SetData, not for the Viessmann_GetData calls. And it seems the GetData v1 calls are now also depreciated.

And the original code has:

define ("apiURL", "https://api.viessmann-climatesolutions.com/iot/v1/equipment/");
define ("apiURLv2", "https://api.viessmann-climatesolutions.com/iot/v2/features/"); 

Those are 2 different endpoints for different things and not just a V1 and a V2 endpoint. I think the v1/v2 switch has to be implemented a bit differently.

[challo]

I dont't get your change. In defines.php you have apiURL and apiURLv2. You can select which you want to use in the web UI below the credentials.
You canged the apiURL and in vitoconnect.php you canged apiURL to apiURLv2. So your change in defines is not used!?

[Marco74]

I had the same issues yesterday where I got the installation info, but not any details. There was an error in the log about a deprecated call.

I edited 2 files and that solved the issue (of course until the current outage):
defines.php

define ("apiURL", https://api.viessmann-climatesolutions.com/iot/v1/equipment/"); 

Changed to:

define ("apiURL", https://api.viessmann-climatesolutions.com/iot/v2/equipment/"); 

vitoconnect.php

$installationDetailJson = Viessmann_GetData (apiURL."installations/".$Install->general->id."/gateways/".$Install->general->serial."/devices/0/features/" ); 

Changed to:

$installationDetailJson = Viessmann_GetData (apiURLv2."installations/".$Install->general->id."/gateways/".$Install->general->serial."/devices/0/features/" ); 

Not a thorough solution, but I managed to control my heatpump again.

[challo]

Ich denke wir müssen kurz mal abwarten. Der API URL Change sollte im Plugin schon drin sein.
Auf der Viessmann Developer Seite steht aktuell folgender Hinweis:

Outage
Our systems are currently experiencing major outages.
Therefore, requests in the Developer Portal cannot be processed.

Daher wird sich wahrscheinlich alles wieder ohne Änderung ergeben...

[VladokSK]

I have got the same issue from yesterday, I see only info about installation-ID, Serial, version, modelID, country etc.. but not info about temperatures, power, gas consumption.. :/

Loxberry : 3.0.1.3
Viessmann Vitoconnect vs. 1.1.1

[Wing_Stefan]

Hallo, bei mir geht seit ein paar Tagen die ViCare app nicht, also ladet nichts. Habe VitoConnect heute resetet neu ins Netz gehängt, Auf Loxberry hat seit ein paar Tagen keine Daten bekommen.
Habe die Info bekommen das die developer URL ausläuft und sich ändert ab 26.11 glaube ich stand dort: Viessmann Developer Portal | Viessmann Developer
Weiters auch gesehen das es eine neue Version gibt. Hier waren aber Errors drinnen:

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:47.865 [COLOR=red][B]ERROR:[/B][/COLOR] Error updating apt database - Error 100[/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:47.866 [COLOR=black][B]INFO:[/B] Updating YARN key...[/COLOR][/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:48.145 [COLOR=black][B]INFO:[/B] Updating NodeJS key...[/COLOR][/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:48.226 [COLOR=black][B]INFO:[/B] Changing Rasbian mirror to http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/[/COLOR][/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Get:1 http://debian.fhem.de/nightly InRelease [1481 B][/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Ign:2 https://deb.nodesource.com/node_18.x buster InRelease[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Get:3 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian bullseye InRelease [15.0 kB][/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Hit:4 https://dl.yarnpkg.com/debian stable InRelease[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Err:5 https://deb.nodesource.com/node_18.x buster Release[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate. Could not handshake: Error in the certificate verification. [IP: 104.20.45.190 443][/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Err:1 http://debian.fhem.de/nightly InRelease[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 64D7A7544B5E40B5[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]Reading package lists...[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]E: The repository 'https://deb.nodesource.com/node_18.x buster Release' no longer has a Release file.[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://debian.fhem.de/nightly InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 64D7A7544B5E40B5[/FONT][/COLOR][/SIZE]
[SIZE=13px][COLOR=#8080ff][FONT=monospace]E: Release file for http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/dists/bullseye/InRelease is not valid yet (invalid for another 8d 16h 54min 55s). Updates for this repository will not be applied.[/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.413 [COLOR=red][B]ERROR:[/B][/COLOR] Error updating apt database - Error 100[/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.414 [COLOR=black][B]INFO:[/B] Updating YARN key...[/COLOR][/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.529 [COLOR=black][B]INFO:[/B] Updating NodeJS key...[/COLOR][/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.611 [COLOR=black][B]INFO:[/B] Changing Rasbian mirror to http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian/[/COLOR][/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.622 [COLOR=red][B]ERROR:[/B][/COLOR] Error updating apt database. All servers give an error. Internet connection available? Giving up.[/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.665 [COLOR=green][B]OK:[/B][/COLOR] Apt cache cleaned successfully.[/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.666 [COLOR=red][B]WARNING:[/B][/COLOR] APT database could not be refreshed.[/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.666 [COLOR=black][B]INFO:[/B] Installing additional software packages.[/COLOR][/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.899 [COLOR=black][B]INFO:[/B] No process is locking apt or dpkg. Fine.[/COLOR][/FONT][/COLOR][/SIZE]

[SIZE=13px][COLOR=#000000][FONT=monospace]06:21:49.899 [COLOR=black][B]INFO:[/B] Installing apt packages php7.4-curl...[/COLOR][/FONT][/COLOR][/SIZE]
​

Schlimm?, Problem ist ich bekomme trotzdem keine Daten auch die Vicare app neu installiert und dort kann ich mich nicht anmelden, proxy error kommt als Fehler, ich habe keinen Proxy.

danke

[mantal]

I am getting the same error. It seems that Viessmann Developer Portal and API services are experiencing some technical issues. I can not access Viessmann Developer Portal using web browser neither.

[seppal97]

hab ich schon beides versucht

[challo]

Vielleicht loxberry und vitoconnect Mal Neustart

[seppal97]

Hallo, seit heute bekomme ich keine Werte mehr vom Loxberry von der Viessmann Wärmepumpe. Plugin Version 1.1.1
Bei den Query links and data kommen nur die Installationsdaten Allgemein, sonst bekomme ich keinen Wert.
In den Installationsdaten Details: sind keine Daten vorhanden.

Beim Log:
18.11.2025 13:13:36 TASK STARTED

Start Logging

INFO: LoxBerry Version 3.0.1.3 ( is_arch_aarch64.cfg is_hwmodel_raspberry_pi_5.cfg is_raspberry.cfg )

INFO: Viessmann Vitoconnect Version 1.0.0

INFO: Loglevel: 3

ERROR: JSON error, or JSON is empty: Error code 4 Syntax error

ERROR: JSON error, or JSON is empty: Error code 4 Syntax error

Processing finished

18.11.2025 13:13:36 TASK FINISHED

kann mir da jemand weiterhelfen?

Mfg Sebastian