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. El martes, 17 de abril de 2018, 13:00:03 (UTC+2), Andrew Milner escribió: > > 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.... > > > > > On Tuesday, 17 April 2018 13:48:45 UTC+3, José-Manuel Anguita wrote: > >> 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ó: >>> >>> 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 >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
