Climate Solutions Community

berroniko · ‎11.09.2024

Sometimes there is a significant difference between the "timestamp" and the dayValueReadAt of several weeks. In a past post this was seen as "temporary error". But recently I had the same behavior again. Do you have any idea, what might be going wrong? { "feature": "heating.gas.consumption.total", "gatewayId": "...", "deviceId": "0", "timestamp": "2024-08-24T22:35:32.900Z", "isEnabled": true, "isReady": true, "apiVersion": 1, "uri": "https://api.viessmann.com/iot/v1/equipment/installations/.../features/heating.gas.consumption.total", "properties": { ... }, "dayValueReadAt": { "type": "string", "value": "2024-07-15T18:27:03.838Z" }, "weekValueReadAt": { "type": "string", "value": "2024-08-18T22:34:15.007Z" }, "monthValueReadAt": { "type": "string", "value": "2024-07-31T22:30:39.302Z" }, "yearValueReadAt": { "type": "string", "value": "2024-07-15T18:27:04.975Z" } }, "commands": {} },

berroniko · ‎27.08.2024

Hi Michael, Recently I had the same discrepancy again (see below). Maybe you can track the source of the error this time? Best regards Niko { "feature": "heating.gas.consumption.total", "gatewayId": "...", "deviceId": "0", "timestamp": "2024-08-24T22:35:32.900Z", "isEnabled": true, "isReady": true, "apiVersion": 1, "uri": "https://api.viessmann.com/iot/v1/equipment/installations/.../features/heating.gas.consumption.total", "properties": { ... }, "dayValueReadAt": { "type": "string", "value": "2024-07-15T18:27:03.838Z" }, "weekValueReadAt": { "type": "string", "value": "2024-08-18T22:34:15.007Z" }, "monthValueReadAt": { "type": "string", "value": "2024-07-31T22:30:39.302Z" }, "yearValueReadAt": { "type": "string", "value": "2024-07-15T18:27:04.975Z" } }, "commands": {} },

berroniko · ‎07.01.2024

Thanks Michael! I checked my data and found the discrepancies only in the period between mid May and early October 23. Afterwards it's mostly the same day, sometimes one day difference. So it was a temporary error. To get my numbers right, I will then ignore "ValueReadAt" for this period and use "timestamp" instead. Best regards Niko

berroniko · ‎22.12.2023

Hi Michael, did you get any feedback from your IT colleagues?

berroniko · ‎11.12.2023

I noticed that sometimes there is a significant difference between the "timestamp" (which I understand as the moment the response was sent) and the dayValueReadAt (which I understand as the time the measurement was taken). In the following example the difference is a full month. There are other examples with less than a month, too. Do you have any idea what the reason could be? "dayValueReadAt": { "type": "string", "value": "2023-05-24T03:54:25.876Z" }, "weekValueReadAt": { "type": "string", "value": "2023-06-18T21:59:51.460Z" }, "monthValueReadAt": { "type": "string", "value": "2023-05-31T23:56:13.834Z" }, "yearValueReadAt": { "type": "string", "value": "2023-05-24T03:54:27.007Z" } }, "commands": {}, "apiVersion": 1, "uri": "https://api.viessmann.com/iot/v1/equipment/installations/18594/gateways/7571381629375109/devices/0/features/heating.gas.consumption.total", "gatewayId": "-", "feature": "heating.gas.consumption.total", "timestamp": "2023-06-24T20:01:19.054Z", "isEnabled": true, "isReady": true, "deviceId": "0" },

berroniko · ‎11.12.2023

Das liegt vermutlich an der Zeitzone. Die Antwort ist in "Zulu" bzw. UTC "2022-09-18T22:07:18.000Z" (erkennt man am Z am Ende). Wenn deine Anlage auf deutsche Sommerzeit (UTC+2h) eingestellt ist, war sie schon einen Tag weiter und deshalb beginnt die Liste unter properties.day.value mit einer 0 für den Verbrauch in der ersten 7min des Montages.

Climate Solutions Community

Deine Aktuellen Statistiken

(heating.gas.consumption.total) large difference b...

Re: (heating.gas.consumption.total) large differen...

Betreff: (heating.gas.consumption.total) large dif...

Re: (heating.gas.consumption.total) large differen...

(heating.gas.consumption.total) large difference b...

Betreff: Gasverbrauch in ViCare falsch!

Weitersurfen