[weewx-user] Re: weewx stopped for no apparent reason

OK, I've just taken a look into the 5 minutes thing. Forget my point from above, the 5 minutes correspond to the 300 second archive interval. I was able to confirm this by changing the interval. Michael Schantl schrieb am Freitag, 18. Juni 2021 um 15:41:57 UTC+2: > OK, will push a new

[weewx-user] Re: weewx stopped for no apparent reason

OK, will push a new release shortly with the change you suggested. Did everything work in the last few days? On the topic of the regular messages, is there any other device or process talking to the WLL. I've noticed that the WLL's HTTP server can act weird when there are too many connections in

[weewx-user] Re: weewx stopped for no apparent reason

Hi JRJ, thank you for the extensive debugging. I've just pushed a new dev release . Yeah, you're right with the missing timeout. I had assumed the requests library honors the socket timeout configured global

[weewx-user] Re: weewx stopped for no apparent reason

@JRJ: So, you're saying that WeeWX stopped generating reports but data still was recorded in the database, correct? If yes, it seems unlikely that it's a driver issue and more on the weewx engine's side. cub...@gmail.com schrieb am Mittwoch, 9. Juni 2021 um 20:22:01 UTC+2: > @chris: yes, indee

[weewx-user] Re: weewx stopped for no apparent reason

Nah, the logging level change doesn't matter, I've published a dev release a few days ago making exactly that change. I'd suggest you to try the new driver version anyway since I also made some changes regarding the HTTP interaction with the WLL. You should also enable debug logging so we get a

[weewx-user] Re: weewx stopped for no apparent reason

Hi, I'm the author of that WLL driver. Yes, the UDP broadcasts come from the WeatherLink Live. The driver should continue to 'tickle' the WLL even if any packets should have been missed, so that shouldn't be an issue. Were there no errors in the log? Your log dump looks absolutely normal. - Mi

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

Yes, a new db needs to be created. You could also configure a second db manually, let WeeWX populate the schema and then transfer all data using wee_database --transfer But the effort is mostly the same either way, so it's easier to just follow the documentation. -- You received this message

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

> > should the pi and weatherlink live be on the same subnetwork, because i > dont get data > Yes, to receive the live 2.5 second push updates (wind, rain) both devices must be on the same subnet. They work using UDP broadcasts. The "complete" data set (HTTP) doesn't technically require it, th

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

Hi Chris, I guess you followed the documentation for installing on a Pi? http://www.weewx.com/docs/debian.htm In that case first uninstall WeeWX {should keep configuration}: sudo apt remove weewx Also keep in mind that the WLL driver uses the Python *requests* library. Install it using:

Re: [weewx-user] Problem with extension install (SyntaxError: Non-ASCII character)

As far as I can see, you are using Python 2 or this problem occurs only with this version. However, the plugin is unfortunately only compatible with Python 3, as it also uses some other Py 3-only features. regards, Michael grua...@gmail.com schrieb am Freitag, 19. Februar 2021 um 19:31:26 UTC+1: