On Thursday, June 11, 2020 at 5:19:24 PM UTC-7, gjr80 wrote: > > The thing to remember is that WeeWX tends to go quiet when a driver stops > feeding WeeWX, WeeWX will keep running but largely does nothing. Agree > there's not much to go on so far but o am not familiar with Weatherlink > Live and it's driver. > >> >> The driver he's running is a fork of one I wrote for a couple people who haven't reported any problems to date, hence my request for more info.
As background, 'my' driver queries a URL periodically, grabs the JSON, and constructs a packet for weewx to save. I have multiple users who have not reported any issues, FWIW. The driver is configurable for: - which URL to query - how often to query - how many times to try, with a configurable wait time, and a max retries setting - if it fails try-wait-try-wait-try-wait-try (etc) the hope was that it would logerr and raise the error to weewx - (and it was written for v3 weewx if that matters) The forked version seems to have added a couple elements and keeps track of rain. I don't know if the fork has bugs that mine doesn't have (or vice versa). But if it's failing routinely I would think the normal debugging would apply - run weewx in the foreground and see if it works stably there, etc. etc. etc. My driver is at https://github.com/vinceskahan/weewx-weatherlinklive-json/blob/master/bin/user/WeatherLinkLiveJSON.py if you want to see the code. It's based on something Matthew wrote, but of course any bugs should be pointed to me for my driver, and to the author of the fork if there are bugs in his/her fork. Hope this helps. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b048d99a-f2d7-4167-ac9a-8cd2bcbe2793o%40googlegroups.com.
