API response Internal Server Error, code 500 when calling “getmeasure” with a scale of 3 hours
When I call “getmeasure”, I get a systematic Internal Server Error code 500 when I use the “3hours” scale.
The problem has been reproduced for several users, for the “read_station”, “read_homecoach” and “read_thermostat” scopes.
The problem affects all types of measure.
I have no problem retrieving the measurement history on all the other available scales.
Is there any change in the use of this scale?
Thank you in advance for your response.
Comments
4 comments
Hello,
Indeed I reproduce the problem on my side. I'm pretty sure it's linked to the arrival of the new DIN module to measure solar energy production
I asked the developers if it's a regression or a wanted change. I'll tell you once I know more
Have a good day,
Leslie - Community Manager
Hello Leslie,
Thank you for your feedback.
I look forward to hearing from you and hope that this is not a wanted change.
Have a nice day,
Hello Leslie,
Can we have an update on the problem, which is still ongoing 11 days after I reported it?
Over the last few days I've been seeing a record number of “code 500, internal error” on all types of “gethomecoachsdata, getstationdata, getmeasure, homestatus, etc...” calls to the api without any further communication from you.
I'm sure you'll agree that it's very difficult to make progress on development and maintain user satisfaction under these conditions.
Best regards,
I am getting code 500, internal error lots of times every day.
Really not stable system. Not relaiable for controlling anything in a Smart Home.
Please sign in to leave a comment.