Re: [weewx-user] Re: randomly stops adding data

This is done already for catchup at startup time. See engine.py “Reject any records with a timestamp in the future.” It uses the current time and allows archive_delay seconds for clock drift. > On Sep 14, 2020, at 6:54 PM, vince wrote: > >  >> On Monday, September 14, 2020 at 5:03:23 PM

[weewx-user] Re: randomly stops adding data

On Monday, September 14, 2020 at 5:03:23 PM UTC-7, YB322 wrote: > > It is clearly something with the station itself, but not sure why it is > randomly throwing a time in the future, think it is some kind of bug in the > latest firmware as I have now seen a couple of other posts with the same >

[weewx-user] Weewx Doesn't Go Past "Started LSB: weewx weather system"

I started weewx using SDR with an Acurite Atlas. I can see data when I use the sdr.py driver directly, but when I start weewx, this is as far as it goes in the syslog: Sep 14 21:09:36 raspberrypi weewx[2374]: Starting weewx weather system: weewx. Sep 14 21:09:36 raspberrypi systemd[1]: Started

Re: [weewx-user] Starting a clean weewx.sdb file

You didn't set debug=1, but that looks normal. The earliest record in your Vantage logger appears to be 2020-09-14 22:05:00 NZST. You can double check by using the wee_device utility, using the --logger-summary option and a file name. Make sure you stop weewx first. *wee_device

Re: [weewx-user] stopping writes of clearly bad timestamp to weewx.sdb

It might be best to not write an archive record less than or equal to the largest dateTime value in the archive table. Sure, there may be an erroneous later row, but that is an issue that should be addressed anyway (rather than ignored). WeeWX already gets the latest at startup (in order to

Re: [weewx-user] Starting a clean weewx.sdb file

Is it something to do with the PID?? the file /var/run/weewx.pid seem to be there when weewx is running and hold a number such as 4738, but disappears when you stop weewx On Tuesday, 15 September 2020 at 12:54:28 UTC+12 John Blanchard wrote: > > > Sep 15 12:40:33 weewx-reynolds weewx[4734]

Re: [weewx-user] Re: And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

This is a excerpt from the extra_sensors_service script - == # Get DHT22 data def get_DHT22(self, event): humidity, temperature = DHT.read_retry(DHT.DHT22, self.DHT22_PIN) temperature = temperature * 9.0/5.0 + 32 if humidity is not None:

Re: [weewx-user] Starting a clean weewx.sdb file

Is it something to bdo with the PID?? the file /var/run/weewx.pid seem to be there when weewx is running, but disappears when you stop weewx On Tuesday, 15 September 2020 at 12:54:28 UTC+12 John Blanchard wrote: > > > Sep 15 12:40:33 weewx-reynolds weewx[4734] INFO __main__: PID file is >

Re: [weewx-user] Starting a clean weewx.sdb file

Sep 15 12:40:33 weewx-reynolds weewx[4734] INFO __main__: PID file is /var/run/weewx.pid Sep 15 12:40:33 weewx-reynolds weewx[4722]: Starting weewx weather system: weewx. Sep 15 12:40:33 weewx-reynolds systemd[1]: Started LSB: weewx weather system. Sep 15 12:40:33 weewx-reynolds weewx[4738]

Re: [weewx-user] Re: And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

Can someone enlighten me on the following that I see in the syslog. the length is either 21 or 51. *Sep 14 16:42:10 raspberrypi weewx[1032] INFO weewx.drivers.ws1: Failed attempt 2 of 5 to get readings: Unexpected buffer length 51* Thanks Michael H Grossie mhgros...@sbcglobal.net On Mon, Sep

[weewx-user] Re: randomly stops adding data

After a few weeks of success the problem appears to have resurfaced. I have done some extra research, the weather station is randomly throwing records with a date in the future. See below: A correct log (UTC 19:58 - 05:58 local time): Sep 15 05:59:08 raspberrypi weewx[15243] DEBUG

[weewx-user] stopping writes of clearly bad timestamp to weewx.sdb

Over in the WeatherFlow forums a guy had an interesting problem where occasionally he has timestamps in his weewx.sdb of 300 or so (ie, 12:05AM 1/1/1970 GMT). My 'guess' is his host took a reboot and weewx fired up before the host had accurate date+time. Is there an easy way to block writes

Re: [weewx-user] Re: And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

Thanks Tom, Vince I apologize - I will look at something to catch the "none" temperature values. Michael H Grossie mhgros...@sbcglobal.net On Mon, Sep 14, 2020 at 4:57 PM Tom Keffer wrote: > On Mon, Sep 14, 2020 at 2:34 PM Michael Grossie > wrote: > >> Vince, thanks for responding. I

Re: [weewx-user] Starting a clean weewx.sdb file

If it's still doing it, we will need to see a log. Set debug=1, restart weewx, post the log through the first reporting cycle. On Mon, Sep 14, 2020 at 2:06 PM John Blanchard wrote: > The file deleted was /var/lib/weewx/weewx.sdb. > > Sep 15 09:03:42 weewx-reynolds weewx[1991] INFO

Re: [weewx-user] Re: And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

On Mon, Sep 14, 2020 at 2:34 PM Michael Grossie wrote: > Vince, thanks for responding. I would consider that if the system had > not been running for almost 10 days prior, without an issue. > Sometimes the temperature is valid, occasionally it is None. One must always be vigilant to the

Re: [weewx-user] Re: And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

I just checked the syslog again. The polling of the DHT_22 (extra_sensors_service) appears to be occurring about every second. I do see an "unexpected buffer length" when it tries to poll WS1. See below. ===syslog (September 14, 2020 4:40P CDT *Sep 14 16:42:00

Re: [weewx-user] Re: And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

Vince, thanks for responding. I would consider that if the system had not been running for almost 10 days prior, without an issue. The error that you mentioned appears to have occurred because of the "engine" shutting down. Also that same code has been running flawless for the last four hours.

Re: [weewx-user] Starting a clean weewx.sdb file

The file deleted was /var/lib/weewx/weewx.sdb. Sep 15 09:03:42 weewx-reynolds weewx[1991] INFO weewx.manager: Starting backfill of daily summaries Sep 15 09:03:42 weewx-reynolds weewx[1991] INFO weewx.manager: Added record 2020-09-15 08:15:00 NZST (1600114500) to database 'weewx.sdb' Sep 15

Re: [weewx-user] Starting a clean weewx.sdb file

What was the path of the weewx.sdb file that you deleted? It should be /var/lib/weewx/weewx.sdb. You did not include a log, but I assume that weewxd is using that file, and not one at /home/weewx/archive/weewx.sdb. On Mon, Sep 14, 2020 at 1:28 PM John Blanchard wrote: > > I'm running Weewx

Re: UPDATE---Re: [weewx-user] HTTP Error 401: Unauthorized

So, the conclusion is that it's normal WU flakiness, plus an unpublished API change? On Mon, Sep 14, 2020 at 1:31 PM Ken Waters wrote: > I finally got it working. It *does* work by using the key. I still get > reject notices but then periodically I get one that shows it published and > now I

UPDATE---Re: [weewx-user] HTTP Error 401: Unauthorized

I finally got it working. It *does* work by using the key. I still get reject notices but then periodically I get one that shows it published and now I do get the "green light" when I log into the site. Here are my log entries showing before and then after it started sending: Sep 14 12:23:32

Re: [weewx-user] HTTP Error 401: Unauthorized

I am uploading to Wunderground without using single or double quotes on my station name and password. Only that way I could get it to work. Op maandag 14 september 2020 om 21:34:26 UTC+2 schreef tke...@gmail.com: > One last thing to try, although it's a long shot. Set debug=2. This will > log

[weewx-user] Starting a clean weewx.sdb file

I'm running Weewx 4.11 on Debian 10 (Buster) with a Vantage Vue station. I want erase all historic data from my computer and rebuild from the memory of the weather station. (I know there is a few months of data held in its memory) This is the process followed to date:- - stop weewx - delete

[weewx-user] Re: And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

On Monday, September 14, 2020 at 12:19:07 PM UTC-7, Michael Grossie wrote: > > * File "/home/weewx/bin/user/extra_sensors_service.py", line 26, in > load_data* > *self.get_DHT22(event)* > * File "/home/weewx/bin/user/extra_sensors_service.py", line 36, in > get_DHT22* > *temperature =

Re: [weewx-user] HTTP Error 401: Unauthorized

One last thing to try, although it's a long shot. Set debug=2. This will log extra debugging information, including the URL used to post to the WU. It will also obfuscate your password, so it won't help there, but at least we can see if the URL is well formed. But, I doubt it will reveal

Re: [weewx-user] HTTP Error 401: Unauthorized

I tried it with both of them and still got rejected. Ken On Mon, Sep 14, 2020 at 4:02 AM Tom Keffer wrote: > Pablo: as per Ken's suggestion, straighten out your station ID > > Both: The WU has taken the station ID plus user password in the past, and > that's what my station is using right now.

[weewx-user] And then it quit working - (Raspberry Pi/WS1/extra_sensors_service)

Good afternoon, After nearly 10 days of trouble free operation the system suddenly crashed. It occurred about 6:35PM CDT. This morning I found this on the screen; = *REC:2020-09-13 18:35:00 CDT (1600040100) altimeter: 27.32372623531874, appTemp:

Re: [weewx-user] Weewx changing from python2 to 3 errors

Python 2 and Python 3 keep separate libraries. What this means is that if something is installed for Python 2, it will not be available for Python 3. You must re-install for Python 3. If you review the install instructions for

[weewx-user] Re: Acurite Atlas Using sdr.py - No Output

Problem solved. Discovered the antenna connection was not good. On Sunday, September 13, 2020 at 9:18:29 PM UTC-4 wxwatching wrote: > > Thanks for the links. I went through the process of completely > reinstalling OS on the PI and following the instructions at >

[weewx-user] Weewx changing from python2 to 3 errors

I get the following error after changing from python 2 to 3. I'm using Weewx 4.1.1 I thought it may have been MQTT so I installed the latest version from https://github.com/weewx/weewx/wiki/mqtt Sep 14 13:05:23 raspberrypi weewx[12183] CRITICAL __main__: Caught unrecoverable exception: Sep

Re: [weewx-user] HTTP Error 401: Unauthorized

no, actually I deleted everything and tried again that is why they are different. but the id and password match. :) On Sun, Sep 13, 2020 at 9:44 PM Ken Waters wrote: > Hi Pablo, > > I just noticed your conf file shows station ID: KCASANJO1246 whereas your > WUnderground devices shows

Re: [weewx-user] Re: Belchertown Skin 1.2 (finally) released!

Pat; thanks for the info and for pointing me to the relevant information. I was able to get those links up and running again. as far as the N/A values being displayed... I haven't seen them since the first day, just after upgrading to 1.2

[weewx-user] Re: Timeline for python 2.7

Sorry for the delay in responding, Tom. You fellows were a great help in trying to resolve this some time ago. I tried everything you suggested, but it was like playing whack-a-mole. The problem is not with weewx, but a combination with my O/S needing a fresh install, my index.html.tmpl file

Re: [weewx-user] HTTP Error 401: Unauthorized

Pablo: as per Ken's suggestion, straighten out your station ID Both: The WU has taken the station ID plus user password in the past, and that's what my station is using right now. But, now I see in the upload protocol notes