Loxberry Vitoconnect

[challo]

reinstalling the plugin should be enough.
Normaly you don't need to trigger manual update. Try to setup cronjob every 5min and check if correct data is sent over mqtt or udp.
Is your data visible when using page "Query links and data"

[tomiou]

I tried reinstalling the plugin. Should I try reinstalling the Loxberry OS? That installation is about 3 years old....

[challo]

That's strange, maybe try to reinstall the plugin

[tomiou]

I switched the log level to debug.
In the log I see data loaded from the API from my device. I think it is loaded correctly.
But on the link http://10.254.254.9/admin/plugins/Vi...action=summary I still see the response #!/usr/bin/php

[challo]

no more log information? Did you set logging to "debug" ?

[tomiou]

Yes, more times... I have FW Loxberry 3.0.1.2... I get the response: *#!/usr/bin/php*

[challo]

Did you restart l9xberry?

[tomiou]

Hello community.
I updated to version 1.1.1 and read data it stopped working.

I have errors in the log:
ERROR: Status GetData: 500
ERROR: Response
ERROR: Unable to get installation details -exiting

I have the correct name, password and TOKEN.

Can you please advise me what I can do?
I'm desperate.....

Thank you

[beekaydottv]

Vielen herzlichen Dank!

[Denon2002]

Hallo challo,

vielen Dank. Habe die Version 1.1.1 installiert und funktioniert.
Danke

[MarkusCosi]

großartig, vielen Dank dafür!

[challo]

Die URLs sind mit dem neuen Release des Plugins angepasst:
Update kommt über das automatische Update des Loxberry.

https://github.com/challo2018/LoxBerry-Plugin-Vitoconnect/releases/tag/v1.1.1

[challo]

Das sollte nur eine kleine Änderung der URL in der defines.php sein. Ich ändere hier mal die URL's und schaue ob alles noch läuft.

[Olinist]

Hi, ich habe hierzu ein Ticket beim Ersteller auf GitHub geöffnet: https://github.com/challo2018/LoxBer...nect/issues/16

Gruß Oli

[Denon2002]

Hallo Gemeinde,

sieht sich jemand im Stande das Plugin entsprechend anzupassen und zu veröffentlichen ?
Ich glaube es geht nur um die Anpassung der URL der API, welche sich ändern soll.

Wäre super nett.

Domain Change for the Viessmann API Dear Developer Portal user, 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.