Thema "Re: Betreff: OneTimeCharge leads to status 502 - what is behind that and how to fix it?" in The Viessmann API

OneTimeCharge leads to status 502 - what is behind that and how to fix it?

jborup — Sat, 07 Aug 2021 10:04:06 GMT

Hi community,

I was trying to do a oneTimeCharge() via a post but I get a 502 in return what do I do about that?

This is the POST request:

curl --location --request POST 'https://api.viessmann-platform.io/iot/v1/equipment/installations/1127/gateways/7555115512740109/devices/0/features/heating.dhw.oneTimeCharge/commands/activate' \
--header 'Authorization: Bearer XXXXXXXXXX' \
--header 'Content-Type: application/json' \
--data-raw '{}'

And this is the response:

{"viErrorId":"req-ca1f1d7c23bf4c5f95b0adb866beb636","statusCode":502,"errorType":"DEVICE_COMMUNICATION_ERROR","message":"DEVICE_COMMUNICATION_ERROR","extendedPayload":{"reason":"INTERNAL_SERVER_ERROR"}}

I especially like to know how to proceed on a reason:INTERNAL_SERVER_ERROR 😕

Any help greatly appriciated.

PS! I actually have a feeling that the viCare app is doing the same thing though it is not reporting the error, as in both cases the oneTimeCharge of the DHW-tank is not starting...

Betreff: OneTimeCharge leads to status 502 - what is behind that and how to fix it?

jborup — Sun, 08 Aug 2021 10:45:49 GMT

Still does not work, however I now get a 200 with

{

"data": {

"success": true,

"reason": "COMMAND_EXECUTION_SUCCESS"

}

I have not changed a thing so I am guessing it was an "outage" on the API gateway... ?

But the question is still relevant in the sense that the INTERNAL_SERVER_ERROR is that the API gateway error? Or communication to my device? or execution at my device? Some more information would be good in case of these kind of errors going forward. Would that be possible?

Betreff: OneTimeCharge leads to status 502 - what is behind that and how to fix it?

jborup — Mon, 09 Aug 2021 13:57:41 GMT

And now it is the 502 again.

{

"viErrorId": "req-cac6a423632c42afb1a880989e5e98bd",

"statusCode": 502,

"errorType": "DEVICE_COMMUNICATION_ERROR",

"message": "DEVICE_COMMUNICATION_ERROR",

"extendedPayload": {

"reason": "INTERNAL_SERVER_ERROR"

}

@CustomerCareMichael Is there anything you and the team could do and reveal to make this more obvious ? Secondly ofcourse more resilient, and working 🙂

Re: Betreff: OneTimeCharge leads to status 502 - what is behind that and how to fix it?

CustomerCareMichael — Thu, 12 Aug 2021 10:20:43 GMT

Hi @jborup ,

is the error 502 still existent? How often do you experience the error? In general, the internal server error is not related to your call or the function you are using.