Page 5 of 7

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 24 Nov 2018, 15:34
by skuske
Yes, we can constantly reproduce that. I do not know if it is limited to the rain gauge, though. But: if the rain gauge (or maybe any other module, too) does not submit data for a longer period of time (maybe for the last 24 hours), then dashboard_data does not exist in the returned JSON for /api/getstationsdata.

@netatmo: can you confirm that? Actually it worked before the original problems of this thread started last week. That means that you must have changed something that causes dashboard_data not to be returned in such scenarios. You should do some sandbox testing before you make such drastic changes to your API.

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 26 Nov 2018, 14:31
by Céline
Hello,

Dashboard_data should be returned in getstationdata response if the device is reachable.
If the device is not reachable, for instance, battery is empty or wifi is off, dashboard_data won't be returned.

To get the older values, you can use getmeasure endpoint.

Céline

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 26 Nov 2018, 14:38
by skuske
Céline wrote: Dashboard_data should be returned in getstationdata response if the device is reachable.
If the device is not reachable, for instance, battery is empty or wifi is off, dashboard_data won't be returned.
OK, the docs don't say that, and actually it worked different before last week. It is not a good approach if you make the returned values dependent on certain (undocumented) conditions. In such cases, at least the key Dashboard_data should be present, but then empty. Otherwise you break the whole system if one expects the dashboard_data key to exist.

Dashboard_data was always returned before the last week, even under the seemingly new exclusion criteria. It's not just us who noticed that...

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 26 Nov 2018, 14:45
by skuske
To make a long story short:

To make the whole system safe, the key 'dashboard_data' should always exist, but in the cases described, it should then be empty, and not simply not exist. Otherwise, the documentation should clearly indicate that the key 'dashboard_data' does not exist under certain conditions.

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 26 Nov 2018, 15:56
by Céline
Hi skuske,

In our actual API, the logic is to not return a field if it is empty. That is why the key is missing in the unreachability case.

I've just updated the documentation and it now informs about the field not being returned when the device is unreachable.

Céline

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 29 Nov 2018, 07:49
by fleproust
Down again

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 30 Nov 2018, 09:26
by fleproust
Down again since 1 hour
no update since 8am this morning. the same on the netatmo website...

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 03 Dec 2018, 18:58
by Céline
Hi fleproust,

Are you sure your station is reachable ?

dashboard_data is not returned when the device is unreachable.

Céline

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 03 Dec 2018, 18:59
by fleproust
It’s ok Now. But 3 hours off last day

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 16 Dec 2018, 13:11
by _Jens_
15.12. -> 4 times the dashboard_data was missing
Every day seems to be the the same … :-/