You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For many specific error situations both post_measurements and get_sensor_data throw a too generic exception: An error occurred communicating with the API...
This is not helpful for debugging. For example when a wrong unit (of measurement) is sent, it could indicate this, or when an invalid date (string) for start or duration is sent this could be mentioned in the exception (pref. with the "erroneous" data).
Also, when the sensor_id is invalid (0) this general message shows..
The text was updated successfully, but these errors were encountered:
The FlexMeasures server should be sending back more informative messages than that. It looks like those are getting swallowed here. Could you try setting the logging level to debug and see if the more informative errors appear in your logs?
For many specific error situations both post_measurements and get_sensor_data throw a too generic exception:
An error occurred communicating with the API...
This is not helpful for debugging. For example when a wrong unit (of measurement) is sent, it could indicate this, or when an invalid date (string) for start or duration is sent this could be mentioned in the exception (pref. with the "erroneous" data).
Also, when the sensor_id is invalid (0) this general message shows..
The text was updated successfully, but these errors were encountered: