Page 2 of 7

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 21 Nov 2018, 16:26
by andy333
The error is back there. No dashboard_data is delivered. Guys, what are you doing!!? :cry:

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 21 Nov 2018, 16:42
by skuske
Yes, same here. Problem is back.

Netatmo: what the heck are you doing there?

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 21 Nov 2018, 16:49
by remember
Good afternoon,

Again? I thought I was the only one!

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 21 Nov 2018, 17:07
by andy333
And fixed again...

Seems to me as if they are testing. Guys, ever heard of a "sandbox" for testing? Please only touch the api results as soon as you are finished testing.

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 21 Nov 2018, 17:10
by skuske
It works again, but these states are totally unacceptable. I would appreciate it if netatmo once commented on the causes of these constant server problems, because even the lack of communication regarding the causes of these almost daily problems is also completely unacceptable.

@netatmo: do we have to expect that those daily issue continue, and: what exactly are the causes?

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 21 Nov 2018, 18:06
by fleproust91
No, the bug is not fixed !!! new problem today. 2 days. I am tired ! my house is controlled by the temperatures. when will the problems stop?

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 22 Nov 2018, 18:41
by fleproust
Inaccessible again. But what does Netatmo do

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 22 Nov 2018, 19:28
by remember
Again? is that neither explanations give ... neither app, nor portal, nothing!
Fantastic!

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 22 Nov 2018, 19:56
by _Jens_
It is really ridiculous :oops:

If anyone from Netatmo is interested ... if we could run our own Netatmo server, the problems would be gone. :?

Re: SERIOUS ISSUE with /api/getstationsdata

Posted: 22 Nov 2018, 20:10
by nesys
The issue here is from 6.21 PM CET, and still unsolved (now is 8.10 PM CET)