Re: [weewx-user] Re: Weewx 3.9.2 and WMR200 crash: Non-positive value for record field 'interval': 0
Hi, I am testing the new driver for almost 2 weeks now, and I am still getting frequent crashes, so this is not the solution to this problem. On Tuesday, September 24, 2019 at 7:58:09 AM UTC+2, Björn Torkelsson wrote: > > Hi Thomas, > > I have the same problem as Patrick. Though I had no luck with the new > driver version you suggested him to try with. I get: > > Sep 24 07:13:57 ripslinger weewx[17315]: engine: Starting up weewx version > 3.9.2 > Sep 24 07:13:59 ripslinger weewx[17315]: wmr200: MainThread: I > genStartup() Delaying archive packet processing until live packet received > Sep 24 07:13:59 ripslinger weewx[17315]: wmr200: MainThread: I Time drift > between host and console in seconds:-361 > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I > genStartup() Still receiving archive packets cnt:0 len:1 > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Using pc > time adjusting archive record time by -361 sec 2019-09-21 13:08:00 CEST > (1569064080) => 2019-09-21 13:01:59 CEST (1569063719) > Sep 24 07:14:00 ripslinger weewx[17315]: engine: Main loop exiting. > Shutting engine down. > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: Thread-2: I USB polling > device thread exiting > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I USB polling > thread expired > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: Thread-1: I Watchdog > received shutdown > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: Thread-1: I Watchdog > thread exiting > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Watchdog > thread expired > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Received > packet count live:1 archive:1 control:1 > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Received > bytes:600 sent bytes:40 > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Packet > archive queue len:0 live queue len:1 > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: W Exiting > with packets still in live queue cnt:1 > Sep 24 07:14:00 ripslinger weewx[17315]: wmr200: MainThread: I Driver > gracefully exiting > Sep 24 07:14:00 ripslinger weewx[17315]: engine: Caught unrecoverable > exception in engine: > Sep 24 07:14:00 ripslinger weewx[17315]: 'WMR200' object has no > attribute 'wmr200' > Sep 24 07:14:00 ripslinger weewx[17315]: Traceback (most recent > call last): > Sep 24 07:14:00 ripslinger weewx[17315]: File > "/usr/share/weewx/weewx/engine.py", line 894, in main > Sep 24 07:14:00 ripslinger weewx[17315]: engine.run() > Sep 24 07:14:00 ripslinger weewx[17315]: File > "/usr/share/weewx/weewx/engine.py", line 160, in run > Sep 24 07:14:00 ripslinger weewx[17315]: > self.dispatchEvent(weewx.Event(weewx.STARTUP)) > Sep 24 07:14:00 ripslinger weewx[17315]: File > "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent > Sep 24 07:14:00 ripslinger weewx[17315]: callback(event) > Sep 24 07:14:00 ripslinger weewx[17315]: File > "/usr/share/weewx/weewx/engine.py", line 520, in startup > Sep 24 07:14:00 ripslinger weewx[17315]: > self._catchup(self.engine.console.genStartupRecords) > Sep 24 07:14:00 ripslinger weewx[17315]: File > "/usr/share/weewx/weewx/engine.py", line 632, in _catchup > Sep 24 07:14:00 ripslinger weewx[17315]: for record in > generator(lastgood_ts): > Sep 24 07:14:00 ripslinger weewx[17315]: File > "/usr/share/weewx/weewx/drivers/wmr200.py", line 1940, in genStartupRecords > Sep 24 07:14:00 ripslinger weewx[17315]: > timestamp_packet_previous += self.wmr200.time_drift > Sep 24 07:14:00 ripslinger weewx[17315]: AttributeError: > 'WMR200' object has no attribute 'wmr200' > Sep 24 07:14:00 ripslinger weewx[17315]: Exiting. > > Den torsdag 12 september 2019 kl. 14:40:52 UTC+2 skrev Thomas Keffer: >> >> Hello, Patrick >> >> Can you try this version >> <https://raw.githubusercontent.com/cmanton/weewx/47800a0a622b7931898faf5aa6b254cac943557a/bin/weewx/drivers/wmr200.py> >> >> of the driver? >> >> On Tue, Sep 10, 2019 at 9:43 PM Patrick J wrote: >> >>> Hi, >>> >>> Last night, weewx crashed again, exactly the same scenario. Any help >>> would be greatly appreciated. >>> >>> -- >>> 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,
Re: [weewx-user] Re: Weewx 3.9.2 and WMR200 crash: Non-positive value for record field 'interval': 0
Hi Thomas, Thank you for the updated driver. I just installed it, and will monitor this closely. Can I also draw your attention to the second bug I described in my initial post? It was about live packets being queued but never processed while the archive records were retrieved from the station. This one seems to be on the engine side rather than the driver. Regards, P. On Thursday, September 12, 2019 at 2:40:52 PM UTC+2, Thomas Keffer wrote: > > Hello, Patrick > > Can you try this version > <https://raw.githubusercontent.com/cmanton/weewx/47800a0a622b7931898faf5aa6b254cac943557a/bin/weewx/drivers/wmr200.py> > > of the driver? > > On Tue, Sep 10, 2019 at 9:43 PM Patrick J > wrote: > >> Hi, >> >> Last night, weewx crashed again, exactly the same scenario. Any help >> would be greatly appreciated. >> >> -- >> 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...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/f6b0c669-5b12-48c8-bd7b-f3abc5c6b5b3%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/f6b0c669-5b12-48c8-bd7b-f3abc5c6b5b3%40googlegroups.com?utm_medium=email_source=footer> >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f2cc7519-b59f-4513-bb02-c75bd6e1953e%40googlegroups.com.
[weewx-user] Re: Weewx 3.9.2 and WMR200 crash: Non-positive value for record field 'interval': 0
Hi, Last night, weewx crashed again, exactly the same scenario. Any help would be greatly appreciated. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f6b0c669-5b12-48c8-bd7b-f3abc5c6b5b3%40googlegroups.com.
[weewx-user] WMR200: rain is always zero
Hi, I connected a RaspBerry PI to my WMR200 weather station. I am using the latest version of weewx, with version 3.3.4 of driver for WMR200. I let the system run for a couple of weeks, and noticed that the field rain in the archive table is always at 0 or null, even though we had a lot of rain. But the field rainRate has different values. As per the user guide, I ran weewx directly to see the packets that come out of the station, and here is the outcome: pi@raspberrypi:/usr/share/weewx $ sudo weewxd /etc/weewx/weewx.conf REC:2018-04-27 16:10:54 UTC (1524845454) altimeter: 29.5299875, appTemp: 63.3209288277, barometer: 29.5608564278, cloudbase: 7892.47484776, dateTime: 1524845454.0, dewpoint: 36.7002569534, ET: None, forecastIcon: 1, heatindex: None, hourRain: 0.0, humidex: 68.54, inDewpoint: 46.1216028652, inHeatindex: None, inHumidity: 43, inTemp: 69.62, interval: 1, maxSolarRad: None, outHumidity: 31, outTemp: 68.54, pressure: 28.880327775, rain: 0.0, rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: None, windDir: 292.5, windGust: 5.59235462985, windrun: 33.7987000882, windSpeed: 4.25018951868 REC:2018-04-27 16:11:54 UTC (1524845514) altimeter: 29.5299875, appTemp: 63.7582794974, barometer: 29.5610911259, cloudbase: 7704.13634321, dateTime: 1524845514.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: None, windDir: 202.5, windGust: 4.25018951868, windrun: 33.8695365802, windSpeed: 3.35541277791 REC:2018-04-27 16:12:54 UTC (1524845574) altimeter: 29.5299875, appTemp: 63.0022794974, barometer: 29.5610911259, cloudbase: 7704.13634321, dateTime: 1524845574.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: None, windDir: 157.5, windGust: None, windGustDir: None, windrun: 33.9254601265, windSpeed: 4.69757788907 REC:2018-04-27 16:13:54 UTC (1524845634) altimeter: 29.5299875, appTemp: 63.2542794974, barometer: 29.5610911259, cloudbase: 7704.13634321, dateTime: 1524845634.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: None, windDir: 202.5, windGust: 5.81604881504, windrun: 34.0037530913, windSpeed: 4.25018951868 REC:2018-04-27 16:14:54 UTC (1524845694) altimeter: 29.5299875, appTemp: 62.4982794974, barometer: 29.5610911259, cloudbase: 7704.13634321, dateTime: 1524845694.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: None, windDir: 202.5, windGust: None, windGustDir: None, windrun: 34.0745895833, windSpeed: 5.59235462985 REC:2018-04-27 16:15:54 UTC (1524845754) altimeter: 29.5299875, appTemp: 62.6242794974, barometer: 29.5610911259, cloudbase: 7704.13634321, dateTime: 1524845754.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: None, windDir: 202.5, windGust: 6.7108282, windrun: 34.1677954938, windSpeed: 5.36866044465 REC:2018-04-27 16:16:54 UTC (1524845814) altimeter: 29.5299875, appTemp: 62.6242794974, barometer: 29.5610911259, cloudbase: 7704.13634321, dateTime: 1524845814.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: None, windDir: 202.5, windGust: 6.7108282, windrun: 34.2572731679, windSpeed: 5.36866044465 REC:2018-04-27
[weewx-user] Re: Oregon WMR200 initial load issues
Hi, I just tried the new driver you attached, and it is working much better, as the archive records are now stored in the database :-) However, there is still an issue, as you can see in this log extract: Apr 27 07:23:31 raspiMeteo weewx[4406]: wmr200: MainThread: I Time drift between host and console in seconds:32 Apr 27 07:24:03 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:0 len:1 Apr 27 07:24:03 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time adjusting archive record time by 32 sec 2017-04-27 09:18:00 CEST (1493277480) => 2017-04-27 09:18:32 CEST (1493277512) Apr 27 07:24:03 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:18:32 CEST (1493277512) to database 'weewx.sdb' Apr 27 07:24:04 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:18:32 CEST (1493277512) to daily summary in 'weewx.sdb' Apr 27 07:24:06 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:1 len:1 Apr 27 07:24:06 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time adjusting archive record time by 32 sec 2017-04-27 09:19:00 CEST (1493277540) => 2017-04-27 09:19:32 CEST (1493277572) Apr 27 07:24:06 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:19:32 CEST (1493277572) to database 'weewx.sdb' Apr 27 07:24:06 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:19:32 CEST (1493277572) to daily summary in 'weewx.sdb' Apr 27 07:24:08 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:2 len:1 Apr 27 07:24:08 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time adjusting archive record time by 32 sec 2017-04-27 09:20:00 CEST (1493277600) => 2017-04-27 09:20:32 CEST (1493277632) Apr 27 07:24:08 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:20:32 CEST (1493277632) to database 'weewx.sdb' Apr 27 07:24:08 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:20:32 CEST (1493277632) to daily summary in 'weewx.sdb' Apr 27 07:24:11 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:3 len:1 Apr 27 07:24:11 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time adjusting archive record time by 32 sec 2017-04-27 09:21:00 CEST (1493277660) => 2017-04-27 09:21:32 CEST (1493277692) Apr 27 07:24:11 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:21:32 CEST (1493277692) to database 'weewx.sdb' Apr 27 07:24:12 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:21:32 CEST (1493277692) to daily summary in 'weewx.sdb' Apr 27 07:24:13 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:4 len:1 Apr 27 07:24:13 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time adjusting archive record time by 32 sec 2017-04-27 09:22:00 CEST (1493277720) => 2017-04-27 09:22:32 CEST (1493277752) Apr 27 07:24:13 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:22:32 CEST (1493277752) to database 'weewx.sdb' Apr 27 07:24:13 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:22:32 CEST (1493277752) to daily summary in 'weewx.sdb' Apr 27 07:24:15 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:5 len:1 Apr 27 07:24:15 raspiMeteo weewx[4406]: wmr200: MainThread: I Using pc time adjusting archive record time by 32 sec 2017-04-27 09:23:00 CEST (1493277780) => 2017-04-27 09:23:32 CEST (1493277812) Apr 27 07:24:15 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:23:32 CEST (1493277812) to database 'weewx.sdb' Apr 27 07:24:15 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:23:32 CEST (1493277812) to daily summary in 'weewx.sdb' Apr 27 07:26:16 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() phase exiting since looks like all archive packets have been retrieved after 120 sec cnt:6 Apr 27 07:26:16 raspiMeteo rsyslogd-2007: action 'action 17' suspended, next retry is Thu Apr 27 07:27:46 2017 [try http://www.rsyslog.com/e/2007 ] Apr 27 07:26:16 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Yielded 6 packets in 300 sec between these dates 2017-04-27 09:18:32 CEST (1493277512) ==> 2017-04-27 09:23:32 CEST (1493277812) Apr 27 07:26:16 raspiMeteo weewx[4406]: wmr200: MainThread: I genStartup() Average packets per minute:1.20 Apr 27 07:26:16 raspiMeteo weewx[4406]: engine: Starting main packet loop. Apr 27 07:27:16 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:27:00 CEST (1493278020) to database 'weewx.sdb' Apr 27 07:27:16 raspiMeteo weewx[4406]: manager: Added record 2017-04-27 09:27:00 CEST (1493278020) to daily summary in 'weewx.sdb' Apr 27 07:27:46 raspiMeteo weewx[4406]: cheetahgenerator: Generated 14 files for report StandardReport in 28.25 seconds Apr 27 07:27:46 raspiMeteo rsyslogd-2007: action 'action 17' suspended, next retry is Thu Apr 27
[weewx-user] Re: Oregon WMR200 initial load issues
Some news: as mentioned in my previous post, I decided to reinstall WeeWX with the Debian package. But this didn't change anything to my issue, archive records are rejected because of this NOT NULL constraint on archive.interval. I decided to clear the data log on the WMR200. I first stopped WeeWX, cleared the log, and restarted the service. One archive record, generated between the clear and the restart was then rejected, but then WeeWX started on process the live records, and these ones finally made their way into the database! This is a step forward, but I still wanted to see what happened if WeeWX was not catching the records on the fly. So I stopped the service for 15 minutes, and then restarted it. Unfortunately, the archive records recorded during this period were also rejected: Apr 26 12:28:51 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:7 len:1 Apr 26 12:28:51 raspiMeteo weewx[2490]: wmr200: MainThread: I Using pc time adjusting archive record time by 14 sec 2017-04-26 14:26:00 CEST (1493209560) => 2017-04-26 14:26:14 CEST (1493209574) Apr 26 12:28:51 raspiMeteo weewx[2490]: manager: Unable to add record 2017-04-26 14:26:14 CEST (1493209574) to database 'weewx.sdb': NOT NULL constraint failed: archive.interval Apr 26 12:28:54 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() Still receiving archive packets cnt:8 len:1 Apr 26 12:28:54 raspiMeteo weewx[2490]: wmr200: MainThread: I Using pc time adjusting archive record time by 14 sec 2017-04-26 14:27:00 CEST (1493209620) => 2017-04-26 14:27:14 CEST (1493209634) Apr 26 12:28:54 raspiMeteo weewx[2490]: manager: Unable to add record 2017-04-26 14:27:14 CEST (1493209634) to database 'weewx.sdb': NOT NULL constraint failed: archive.interval Apr 26 12:30:55 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() phase exiting since looks like all archive packets have been retrieved after 120 sec cnt:9 Apr 26 12:30:55 raspiMeteo rsyslogd-2007: action 'action 17' suspended, next retry is Wed Apr 26 12:32:25 2017 [try http://www.rsyslog.com/e/2007 ] Apr 26 12:30:55 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() Yielded 9 packets in 480 sec between these dates 2017-04-26 14:19:14 CEST (1493209154) ==> 2017-04-26 14:27:14 CEST (1493209634) Apr 26 12:30:55 raspiMeteo weewx[2490]: wmr200: MainThread: I genStartup() Average packets per minute:1.125000 Apr 26 12:30:55 raspiMeteo weewx[2490]: engine: Starting main packet loop. Apr 26 12:31:19 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 14:31:00 CEST (1493209860) to database 'weewx.sdb' Apr 26 12:31:19 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 14:31:00 CEST (1493209860) to daily summary in 'weewx.sdb' Apr 26 12:31:49 raspiMeteo weewx[2490]: cheetahgenerator: Generated 14 files for report StandardReport in 28.43 seconds Apr 26 12:31:54 raspiMeteo weewx[2490]: imagegenerator: Generated 12 images for StandardReport in 4.01 seconds Apr 26 12:31:54 raspiMeteo weewx[2490]: copygenerator: copied 9 files to /var/www/html/weewx Apr 26 12:32:15 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 14:32:00 CEST (1493209920) to database 'weewx.sdb' Apr 26 12:32:15 raspiMeteo weewx[2490]: manager: Added record 2017-04-26 14:32:00 CEST (1493209920) to daily summary in 'weewx.sdb' Apr 26 12:32:26 raspiMeteo weewx[2490]: cheetahgenerator: Generated 14 files for report StandardReport in 8.97 seconds So there is still an issue... And in addition, some records were lost, the ones from 14:28, 14:29 and 14:30. I would really appreciate if someone could help. Patrick -- 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.
[weewx-user] Re: Oregon WMR200 initial load issues
I just checked, and NTP is configured on the pi: ntpq> pe remote refid st t when poll reach delay offset jitter == +bb8.dousse.eu 212.83.179.156 3 u 905 1024 377 21.599 -1.943 4.789 -62-210-28-176.r 84.255.209.794 u 812 1024 377 17.188 -1.550 8.901 *mica.ad-notam.n 131.188.3.2202 u 92 1024 375 70.345 22.372 21.989 +194.177.34.116 163.172.61.210 3 u 917 1024 373 19.044 -1.883 9.531 This explains why the "date" command displays the correct time. The fake hw clock is still running on the pi, but as I didn't so far run weewx as a service, but rather launched it manually, NTP has done its job before weewx starts processing archive records, so this should not be an issue. I installed weewx with the "setup.py" method. As I don't know what else to try, I will fully uninstall it and try the debian package method... Patrick -- 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.
[weewx-user] Re: Oregon WMR200 initial load issues
My pi does not have a real clock. I did not remove the fake hardware clock, nor did I configure NTP, as I thought it was already included in Raspbian. Indeed, when I type "date" on the Linux command prompt, the current exact date is returned. But I will in any case check these points. The database is in fact empty. I installed sqlite on the pi, I have zero records in the archive table. Weewx rejects systematically all the history records that come from the weather station... Patrick On Wednesday, April 26, 2017 at 7:28:50 AM UTC+2, mwall wrote: > > On Tuesday, April 25, 2017 at 8:38:50 AM UTC-4, Patrick J wrote: >> >> After a while, there is no more output from weewx, but in the log I can >> see this type of lines: "wmr200: MainThread: I genStartup() Discarding >> received archive record exceeding archive interval cnt:10 threshold:604800 >> timestamp:2017-04-22 11:07:27 UTC (1492859247)". >> >> It seems that it has now reached the records corresponding to my usage, >> but it is discarding them... What should I do to get things right? >> > > does your pi have a real clock on it? (you would have to have added it > one - they do not come with a clock) > > did you remove the fake hardware clock software? > > is the pi configured to use ntp? > > your weewx database is probably full of data with wonky timestamps. you > can start over by doing this: > > 1) stop weewx > sudo /etc/init.d/weewx stop > > 2) move the database aside > sudo mv /home/weewx/archive/weewx.sdb /home/weewx/archive/weewx.sdb.bak > > 3) start weewx > sudo /etc/init.d/weewx start > > it could take awhile to read all of the records from the wmr200 logger, so > be patient and watch the log. > > 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.
[weewx-user] Re: Oregon WMR200 initial load issues
It may be useful to list what is in the beginning of the log (debug = 1):
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Initializing weewx version
3.7.1
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Using Python 2.7.9 (default,
Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Platform
Linux-4.4.50+-armv6l-with-debian-8.0
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Locale is 'en_GB.UTF-8'
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Using configuration file
/home/weewx/weewx.conf
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: debug is 1
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Initializing engine
Apr 25 15:37:15 raspiMeteo weewx[906]: engine: Loading station type WMR200
(weewx.drivers.wmr200)
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I driver version
is 3.3.1
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I sensor map is
{'outTempBatteryStatus': 'battery_status_out', 'outHumidity': 'humidity_1',
'rainRate': 'rain_rate', 'heatindex4': 'heatindex_5', 'rainTotal':
'rain_total', 'rainBatteryStatus': 'battery_status_rain', 'heatindex6':
'heatindex_7', 'extraTemp5': 'temperature_6', 'uvFault': 'uv_fault',
'extraTemp2': 'temperature_3', 'heatindex': 'heatindex_1', 'extraTemp3':
'temperature_4', 'rain24': 'rain_24', 'inHeatindex': 'heatindex_0',
'inTemp': 'temperature_0', 'extraTemp1': 'temperature_2', 'hourRain':
'rain_hour', 'windFault': 'wind_fault', 'windchill': 'windchill',
'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7':
'temperature_8', 'rain': 'rain', 'forecastIcon': 'forecast_icon',
'pressure': 'pressure', 'extraHumid4': 'humidity_5', 'extraHumid5':
'humidity_6', 'extraHumid2': 'humidity_3', 'extraHumid3': 'humidity_4',
'extraHumid1': 'humidity_2', 'extraTemp6': 'temperature_7', 'heatindex5':
'heatindex_6', 'extraTemp4': 'temperature_5', 'heatindex7': 'heatindex_8',
'altimeter': 'altimeter', 'heatindex1': 'heatindex_2', 'heatindex2':
'heatindex_3', 'heatindex3': 'heatindex_4', 'extraHumid6': 'humidity_7',
'extraHumid7': 'humidity_8', 'windBatteryStatus': 'battery_status_wind',
'UV': 'uv', 'rainFault': 'rain_fault', 'windDir': 'wind_dir', 'outTemp':
'temperature_1', 'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0',
'outTempFault': 'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus':
'battery_status_uv'}
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I Created
watchdog thread to poke for live data every 30 seconds
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I Created USB
polling thread to read block on device
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: MainThread: I Reset console
device
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: Thread-2: I USB polling
device thread for live data launched
Apr 25 15:37:15 raspiMeteo weewx[906]: wmr200: Thread-2: I USB polling
device thread signaled to start
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D Configuration
setup
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D Log sensor
faults: True
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D Using PC
Time: True
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D Erase
archive data: False
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D Archive
interval: 300
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: MainThread: D Archive
threshold: 604800
Apr 25 15:37:16 raspiMeteo weewx[906]: wmr200: Thread-1: I Started watchdog
thread live data
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service
weewx.engine.StdTimeSynch
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service
weewx.engine.StdTimeSynch
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service
weewx.engine.StdConvert
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: StdConvert target unit is 0x1
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service
weewx.engine.StdConvert
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service
weewx.engine.StdCalibrate
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service
weewx.engine.StdCalibrate
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service
weewx.engine.StdQC
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Finished loading service
weewx.engine.StdQC
Apr 25 15:37:16 raspiMeteo weewx[906]: engine: Loading service
weewx.wxservices.StdWXCalculate
Apr 25 15:37:16 raspiMeteo weewx[906]: wxcalculate: The following values
will be calculated: barometer=prefer_hardware, windchill=hardware,
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=hardware,
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware,
humidex=prefer_hardware, pressure=prefer_hardware,
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
cloudbase=prefer_hardware
Apr 25 15:37:16 raspiMeteo weewx[906]: wxcalculate: The following
algorithms will be used for calculations: altimeter=aaNOAA,
[weewx-user] Oregon WMR200 initial load issues
Hi, I just installed the latest version of weewx on a Raspberry pi, with the setup.py method. Then I connected my Oregon WMR200 weather station via USB, and launched weewx with the command "sudo weewxd weewx.conf" The program started to retrieve data from the weather station, but: - It reads one record per second at the best, sometimes several seconds between records. - The records do not correspond to periods on which the station was on, I see records from "2007-01-01" and "2016-07-20", while I bought the station a few days ago. - I see in the log error messages like "manager: Unable to add record 2016-07-20 16:01:27 UTC (1469030487) to database 'weewx.sdb': NOT NULL constraint failed: archive.interval" After a while, there is no more output from weewx, but in the log I can see this type of lines: "wmr200: MainThread: I genStartup() Discarding received archive record exceeding archive interval cnt:10 threshold:604800 timestamp:2017-04-22 11:07:27 UTC (1492859247)". It seems that it has now reached the records corresponding to my usage, but it is discarding them... What should I do to get things right? Patrick -- 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.
