Netatmo offline?

Add-ons Bindings
1

Does someone else see connection errors with Netatmo?

image

2017-08-10 21:03:14.491 [ERROR] [netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : OAuthProblemException{error=‘unsupported_response_type’, description=‘Invalid response! Response body is not application/json encoded’, uri=‘null’, state=‘null’, scope=‘null’, redirectUri=‘null’, responseStatus=0, parameters={}}

The problem started for me a few days ago…

Michael

2

I’ve got the same error since today with my netatmo binding… ;-(
michael

3

Same here.
Changed the API key yesterday and it started working again, but a day later offline again.

4

Hi @cweitkamp @RolandS

You both are working/using the Netatmo-Binding, right? Do you see the same error? For me the API is still offline today :frowning:

–> https://github.com/openhab/openhab2-addons/issues/2541

5

yes, I see the same error message (#2541). ;-(

6

I have the same issue since yesterday.

7

Since several days I also have found some Netatmo errors in the openhab log:

“2017-08-09 13:43:30.756 [ERROR] [netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : 403 Forbidden”

or

“2017-08-10 13:40:33.313 [ERROR] [netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : Verbindungsaufbau abgelehnt (Connection refused)”

or
"2017-08-10 16:01:09.934 [ERROR] [netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : 503 Service Temporarily Unavailable"

I use the current unstable 2.2.0 snapshot build in all three installatios. Nur sure, if the problems occured since i switched from stable 2.1

8

I’ve got still the stable release netatmo-binding 2.1.0 installed.

9

I’m using 2.1 and have the same error messages in my log.

Yesterday I’ve rebooted the device and it started to work again for about a day or so. :frowning:

10

Same here. Running Openhab 2.0.

11

Hi all,

yes I have the same problems. Since yesterday afternoon my log shows plenty of those messages.

2017-08-11 10:27:31.239 [ERROR] [netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : 503 Service Temporarily Unavailable

The days before I got a lot of messages like this - which only occurs for a while.

2017-08-10 13:50:29.442 [ERROR] [netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : 403 Forbidden

2017-08-10 15:46:11.930 [ERROR] [netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : Verbindungsaufbau abgelehnt
12

There is problem with the Netatmo servers, see here.

13

Hej all - Netatmo confirmed this morning, that their API server is offline.

Blockquote
Postby Brieuc_Netatmo » Fri Aug 11, 2017 9:14 am
Hi all,
Our servers are indeed currently facing some trouble.
We are focused on solving this issue as soon as possible.
Thank you for your patience and your understanding.

This message comes from the netatmo Forum. http://forum.netatmo.com/viewtopic.php?f=7&t=8749&p=44232#p44232

Lets hope, that they have their servers running soon again. There were allready outages last weekend and the week over… no good sign for the reliability of the netatmo system at the moment.

14

I think the Netatmo API is accessible again. But not very stable. I got some errors in the the log every few update cycles. Does anybody feeling the same?

15

Yes same for me

16

Yes, the same here.

17

Got the same. At least it’s back. Hope it will be better in future.

18

HI,
i’m on the netatmo:2.2.0.201711040020 version - and i am not sure weather it is about the used snapshot or netatmo api - so can so please tell me if the 2.1 is working - and its more about the snapshot?

23:33:32.675 [DEBUG] [.netatmo.handler.NetatmoBridgeHandler] - An error occurred while calling station API : 400 Bad Request
retrofit.RetrofitError: 400 Bad Request
	at retrofit.RetrofitError.httpError(RetrofitError.java:40) ~[225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at retrofit.RestAdapter$RestHandler.invokeRequest(RestAdapter.java:388) [225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at retrofit.RestAdapter$RestHandler.invoke(RestAdapter.java:240) [225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at com.sun.proxy.$Proxy144.getstationsdata(Unknown Source) [225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at org.openhab.binding.netatmo.handler.NetatmoBridgeHandler.getStationsDataBody(NetatmoBridgeHandler.java:153) [225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at org.openhab.binding.netatmo.internal.station.NAMainHandler.updateReadings(NAMainHandler.java:42) [225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at org.openhab.binding.netatmo.handler.NetatmoDeviceHandler.updateChannels(NetatmoDeviceHandler.java:92) [225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at org.openhab.binding.netatmo.handler.NetatmoDeviceHandler$1.run(NetatmoDeviceHandler.java:64) [225:org.openhab.binding.netatmo:2.2.0.201711040020]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
	at java.lang.Thread.run(Thread.java:748) [?:?]```