Any Netatmo cloud users working?

[Robert Brown]

I'm seeing a HTTP 400 error in the logs every time it retries. I've not been able to find anything beyond the basic setup. I've cut & pasted my keys into the conf file. Since my app activation is new, I wondered if there was a delay in making it live or if there is a URL out of wack somewhere. 

Any one else working that could shed some light on this? I'd like to move off of Meteoware before I add wind and rain since that setup doesn't report those items to wunderground.

[mwall]

On Monday, November 6, 2017 at 8:21:36 AM UTC-5, Robert Brown wrote:

I'm seeing a HTTP 400 error in the logs every time it retries. I've not been able to find anything beyond the basic setup. I've cut & pasted my keys into the conf file. Since my app activation is new, I wondered if there was a delay in making it live or if there is a URL out of wack somewhere. 

Any one else working that could shed some light on this? I'd like to move off of Meteoware before I add wind and rain since that setup doesn't report those items to wunderground.

are your netatmo connections working now?

my netatmo test station was working fine until around midnight US eastern time on 18oct2017.  then it started reporting:

netatmo-client: failed attempt 5 of 5 to get data: <urlopen error _ssl.c:489: The handshake operation timed out>

netatmo-client: failed to get data after 5 attempts

it seems to be working fine now.

m

 

[Robert Brown]

Thank you... I'll test it out later once my head fog clears. This rain in NE Texas is needed but AWFUL for thinking.  :)

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/ENdlg0jEP-U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robert Brown]

Sadly... failure.

Nov  8 12:36:16 nas weewx[26867]: restx: StationRegistry: Registration not requested.

Nov  8 12:36:16 nas weewx[26867]: restx: Wunderground: Posting not enabled.

Nov  8 12:36:16 nas weewx[26867]: restx: PWSweather: Posting not enabled.

Nov  8 12:36:16 nas weewx[26867]: restx: CWOP: Posting not enabled.

Nov  8 12:36:16 nas weewx[26867]: restx: WOW: Posting not enabled.

Nov  8 12:36:16 nas weewx[26867]: restx: AWEKAS: Posting not enabled.

Nov  8 12:36:16 nas weewx[26867]: engine: Starting up weewx version 3.7.1

Nov  8 12:36:16 nas weewx[26867]: engine: Starting main packet loop.

Nov  8 12:36:16 nas weewx[26867]: netatmo: netatmo-client: failed attempt 1 of 5 to get data: HTTP Error 400:

Nov  8 12:36:27 nas weewx[26867]: netatmo: netatmo-client: failed attempt 2 of 5 to get data: HTTP Error 400:

Nov  8 12:36:38 nas weewx[26867]: netatmo: netatmo-client: failed attempt 3 of 5 to get data: HTTP Error 400:

Nov  8 12:36:48 nas weewx[26867]: netatmo: netatmo-client: failed attempt 4 of 5 to get data: HTTP Error 400:

[mwall]

...

Nov  8 12:36:48 nas weewx[26867]: netatmo: netatmo-client: failed attempt 4 of 5 to get data: HTTP Error 400:

please set debug=1, restart weewx, then post the log from when you start weewx until after 15 minutes or so

before posting, be sure to check the log output for any keys or passwords

m

[Robert Brown]

Thank you... I completely ignored that when I read, sorry.  The driver is accessing: https://api.netatmo.net/oauth2/token. According to docs, it should be using: https://api.netatmo.com/oauth2/token. So the domain has changed since the driver was created.

ref: https://dev.netatmo.com/resources/technical/samplessdks/codesamples#getstationsdata

[Robert Brown]

Any howtos on updating the python script to use the correct URL and then recompiling?

[mwall]

On Saturday, November 11, 2017 at 2:02:20 PM UTC-5, Robert Brown wrote:

Any howtos on updating the python script to use the correct URL and then recompiling?

1) stop weewx 

2) modify netatmo.py change this (around line 269):

    NETATMO_URL = 'https://api.netatmo.net'

to this:

    NETATMO_URL = 'https://api.netatmo.com'

3) start weewx

however, i'm pretty sure that the .com/.net url is not the problem.  it looks like netatmo.net redirects to netatmo.com

when you have debug=1, what do you see for the url, data, and header that are sent to netatmo's servers?

m

[Robert Brown]

Yes, that's what made me look up the api reference. 

--

[Robert Brown]

And I get no redirect from here.

[mwall]

On Saturday, November 11, 2017 at 4:23:22 PM UTC-5, Robert Brown wrote:

Yes, that's what made me look up the api reference. 

so does it work when you use .com instead of .net?

please post the log when debug=1

if the netatmo server is not lying to you, then a response of 400 means that the request was not structured or formatted correctly.  the url, data, and header lines from the log will tell us exactly what weewx posted.

m

[José-Manuel Anguita]

It doesn't work

[José-Manuel Anguita]

I think that I've found the problem.

You should edit /etc/weewx/weewx.conf manually and add the four Netatmo parameters to this file. 

The problem appears to be that sudo wee_config --reconfigure doesn't setup the driver right.

This worked for me.

El domingo, 12 de noviembre de 2017, 0:26:14 (UTC+1), mwall escribió:

[Andrew Milner]

It may be helpful to others if you could tell us exactly what sudo wee_config --reconfigure does not do correctly, and what you had to then manually edit in weewx.conf to make weewx work correctly....

[José-Manuel Anguita]

I've been testing with other systems and I can confirm you that, at least in Debian, the sudo wee_config --reconfigure doesn't modify the netatmo part of /etc/weewx/weewx.conf.

The problem is solved if you edit /etc/weewx/weewx.conf manually and at the end of file, you add the four parameters for netatmo driver.