Climate Solutions Community

qdel · ‎27.02.2025

So, I have now improved logging. And it feels completely wrong. Note that I am in France (+1 tz). On the 25/02, at 14:16:06,502 : - array is: [ 9.2, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004, 33.8] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS CORRECT! I drop the first element of the array as I don't care about "today". Consumption on vicare of the 24/02 is of 10kWh, and previous day are fine also (albeit, roundings) On the 25/02 at 23:57:53,351: - array is: [19.6, 19, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS WRONG! (my final consumption for the 25/02 on vicare is 19.5Kwh. So we have 2 glitches: wrong dayValueReadAt, wrong number of elements) On the 25/02 at 23:59:54,196: - array is: [0, 19, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS WRONG ! (Same as before, with a 0 in front...) From this time the front value will improve according to the new day. This logic seems fine. But the dayValueReadAt stays as 2025-02-25T13:13:57.206Z ! On the 26/02 at 00:15:01: - array is: [0.2, 19.6, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS WRONG! (values look fine, but as the date is the wrong one, we will think it is the 24th which has a power of 19.6 while it is in fact the 9.9...) From this time the front value will improve according to the new day. This logic seems fine. But the dayValueReadAt stays as 2025-02-25T13:13:57.206Z ! Feels like we are having multiple issues: dayValueReadAt never changes, possible duplication of data in the list etc...

qdel · ‎26.02.2025

So, I have now improved logging. And it feels completely wrong. Not that I am in France (+1 tz). On the 25/02, at 14:16:06,502 : - array is: [ 9.2, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004, 33.8] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS CORRECT! I drop the first element of the array as I don't care about "today". Consumption on vicare of the 24/02 is of 10kWh, and previous day are fine also (albeit, roundings) On the 25/02 at 23:57:53,351: - array is: [19.6, 19, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS WRONG! (my final consumption for the 25/02 on vicare is 19.5Kwh. So we have 2 glitches: wrong dayValueReadAt, wrong number of elements) On the 25/02 at 23:59:54,196: - array is: [0, 19, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS WRONG ! (Same as before, with a 0 in front...) From this time the front value will improve according to the new day. This logic seems fine. But the dayValueReadAt stays as 2025-02-25T13:13:57.206Z ! On the 26/02 at 00:15:01: - array is: [0.2, 19.6, 9.9, 17.799999999999997, 11, 10, 15.7, 25.000000000000004] - dayValueReadAt: 2025-02-25T13:13:57.206Z THIS IS WRONG! (values look fine, but as the date is the wrong one, we will think it is the 24th which has a power of 19.6 while it is in fact the 9.9...) From this time the front value will improve according to the new day. This logic seems fine. But the dayValueReadAt stays as 2025-02-25T13:13:57.206Z ! [Story twist incoming, waiting for the data to come in. But actually the API is working perfectly fine between 14h30 and 23h50....]

qdel · ‎24.02.2025

Hello, When retrieving the API, data is either strange or not consistent. I will show for Total, but it is same on dhw and heating. I will concentrate on daily, just for limiting the explanation We are, today, the 24-02-2025. I receive this array of values: [0.3, 11, 10, 15.7, 25.000000000000004, 33.8, 32.6, 37.3]. DayValueReadAt is: 2025-02-22T14:41:51.317Z So, if we follow the idea: 0.3 = 22/02/2025, 11 the 21/02, 10 the 20/02, 15.7 the 19/02, 25 the 18/02 etc... But everything is shifted one day if we compare with ViCare: 0.3 = ???, 11 the 22/02, 10 the 21/02, 15.7 the 20/02, 25 the 19/02. I feels also that, at one point, I received correct positionning. Because I have, on my system a check for new data with what the API provides. And it is also checking consistency, it is this pass which tell me that the "newly received data" is invalid with what I already received ! I, sadly, had not enabled logging on this part of code. How can we fix it ?

qdel · ‎01.02.2024

Hi, First of all, I am French, I sadly do not speak German and I have some doubts on how google translate behaves. Well, sorry for that! Secondly, I have trouble creating the first authentication request: https://documentation.viessmann.com/static/authentication Here is my request: https://iam.viessmann.com/idp/v3/authorize?client_id=[client-iad-as-seen-in-developer-board]&redirect_uri=[valid-uri]&scope=IoT%20User%20offline_access&reponse_type=code&code_challenge_method=S256&code_challenge=[generated-with-python-pkce] The challenge is generated with: https://github.com/RomeoDespres/pkce Which seems to match the requirements for Viessmann API. But I am faced 99.99999% of the time by this page: Roughly translated by "System error, try again later". I managed to get the login page once. But my callback code was not created at this time. Is my request wrongly made? Is the API just down? Note that my account is not linked to any hardware at the moment. (Buying the house where I will install heat pump there, but code do not need to wait 😃 ) Is there a sandbox api ? Thanks for your help !

Climate Solutions Community

Deine Aktuellen Statistiken

Betreff: heating.power.consumption.{dhw,heating,to...

Betreff: heating.power.consumption.{dhw,heating,to...

heating.power.consumption.{dhw,heating,total} inva...

Login request fail with system error

Weitersurfen