Woche der Wärmepumpe

Während der Woche der Wärmepumpe haben Sie bundesweit die Möglichkeit, die innovative Wärmepumpentechnologie näher kennenzulernen. Mit über 50 Informationsveranstaltungen beteiligt sich Viessmann Climate Solutions an der Aktionswoche und lädt Sie herzlich ein – vor Ort oder online – dabei zu sein.

Mehr erfahren →
Woche der Wärmepumpe
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

endpoint empty

From yesterday there is no data here.

Someone facing the same issue?

 

{
"feature": "heating.compressors.1.statistics",
"gatewayId": "-",
"deviceId": "0",
"timestamp": "2024-02-22T05:56:06.523Z",
"isEnabled": false,
"isReady": true,
"apiVersion": 1,
"uri": "https://api.viessmann.com/iot/v1/equipment/installations/1711821/gateways/7571381816709106/devices/0...",
"properties": {},
"commands": {}
},

9 ANTWORTEN 9

Indeed, same problem here. The compressor starts/hours variable is empty after the back-end update of last night.

Now the question is? 

WHY?

It will come back?

They need to stop to play around!!!

And same problem here after last night service break.

Viessmann - Please INFORM API CHANGES RIGHT AFTER SERVICE BREAKS 

I have the same problem. Viessmann modified the output, probably yesterday. Properties and commands follow now the URI statement and are not anymore at the beginning of the item. The compressor starts and run time (compressors.x.statistics, x=1 or 0 may be dependent on the system, 0 in my system) are not the only parameters which are not anymore enabled (isEnabled: false, was 'true' in former times). The following items are also disabled in my system for which I got data before: 

heating.compressors.0.heat.production.current

heating.compressors.0.power.consumption.current

heating.circuits.0.heating.curve (shift and slope for cooling)

heating.circuits.0.temperature

On my side heating.circuits.0.temperature is still available

 

{
"feature": "heating.circuits.0.temperature",
"gatewayId": "-",
"deviceId": "0",
"timestamp": "2024-02-22T05:56:06.523Z",
"isEnabled": true,
"isReady": true,
"apiVersion": 1,
"uri": "https://api.viessmann.com/iot/v1/equipment/installations/1711821/gateways/7571381816709106/devices/0...",
"properties": {
"value": {
"type": "number",
"value": 26.9,
"unit": "celsius"
}
},
"commands": {}
},

 

Same here (sorry for doubled posting) https://community.viessmann.de/t5/The-Viessmann-API/heating-compressors-0-statististics-Abfrage-funk...

Thanks @CHZ but I'm not sure if I want to take care of this sh*tty upgrades here.

It seems to work for me again 😊.

{"starts":{"type":"number","value":7644,"unit":""},"hours":{"type":"number","value":5520.9,"unit":"hour"}}

Except for the running state, but maybe that one was already not working for a while.

 

Edit: Also works with:

 

(int)$viessmannApi->isHeatingCompressorsActive();

(using https://github.com/thetrueavatar/Viessmann-Api/releases)

The data is back! 🤔

Yes, the heating.compressors. ... data are back since this morning. The heating.circuits.0. ... data I missed are still not back. Fortunately, these are not so important (cooling curve data).

@MichaelHanna: Great that the most important data are back. Why is it not possible to post messages about planned changes in the system? I always have to restart my data reading and do not look every day into my tool. It would also be great to post information about actual problems/errors on which Viessmann is working and when these problems are solved.

Regards,

Christian

Top-Lösungsautoren