[weewx-user] WeeWX is memory hungry

Hi, Ever since I've upgraded to 3.5.0 and beyond WeeWX is taking up a lot of memory. Way more then I'd hope it would be taking up. Any ideas why this is or how do reduce this ram usage? -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To

Re: [weewx-user] Releasing V3.7.0

On Monday, March 13, 2017 at 10:19:27 PM UTC-4, Robert Mantel wrote: > > Doesn't seem to be working for me. sudo apt-get upgrade says I'm on the > latest and I have 3.6.2, Maybe it hasn't propagated to all the mirrors? >> >> >> what's in your /etc/apt/sources.list.d/weewx.list? cat

Re: [weewx-user] Re: 3.7.0 with MySQL quitting with database error

Something did change. Previously, weewx used transaction isolation level "READ UNCOMMITTED." Now it uses "READ COMMITTED." But, according to the error message in your first post, both are limited to row-based logging, so I don't know why this change would suddenly cause the error. -tk On Sun,

Re: [weewx-user] #1 - Missing 20 days in monthly summary #2 - User guide error?

Yes. Starting with V3.0, there is no longer a separate "stats" database. Instead, the daily summaries are incorporated into the archive file itself. Try rebuilding the daily summaries and see if that causes the data to reappear. -tk On Mon, Mar 13, 2017 at 4:52 PM, John Canfield

Re: [weewx-user] #1 - Missing 20 days in monthly summary #2 - User guide error?

Ah-so. Thanks Tom. Any idea about the missing data? On Monday, March 13, 2017 at 4:27:21 PM UTC-5, Tom Keffer wrote: > > --rebuild-daily is the command used by later versions. Earlier versions > use --backfill-daily. > > -tk > > On Mon, Mar 13, 2017 at 1:26 PM, John Canfield

[weewx-user] Re: Lost rapidfire to Wunderground with 3.7.0

That fixed it. No errors on startup and I see Wunderground updating every few seconds as it did with 3.6.2. Thanks for the help. - Paul Mar 13 20:34:51 norge weewx[17569]: engine: Initializing weewx version 3.7.0 Mar 13 20:34:51 norge weewx[17569]: engine: Using Python 2.7.5 (default, Nov

Re: [weewx-user] Using MariaDB/MySQL with non-standard directories

Here's how I understand it: - If hostname is localhost, but no port is supplied: use sockets. - If hostname is localhost, but a port is supplied: use TCP/IP. In version 3.6.x, you were in situation #2. With version 3.7.x, you are in #1. -tk On Mon, Mar 13, 2017 at 3:58 PM, Theophanis

Re: [weewx-user] Using MariaDB/MySQL with non-standard directories

Hi Tom, Thank you for the follow up. Actually the standard MySQL/MariaDB way is to use sockets if the hostname is localhost. TCP/IP will only be used if the hostname is not localhost, or if an IP is provided. So basically it works now as expected (non standard dirs etc) but had to provide

[weewx-user] Re: no module named alarm

On Monday, March 13, 2017 at 6:13:17 AM UTC-7, gjr80 wrote: > Hi, > > Admittedly it was the 28th item in the change log included in the release > post > : > > Moved examples out of bin directory. Eliminated experimental

[weewx-user] Using MariaDB/MySQL with non-standard directories

Hello All, I have a mariadb on CEntOS 7.3 with non-standard datadir and socket. The configuration is implemented via drop in files. [root@tweety ~]# cat /etc/my.cnf.d/tweety.cnf [mysqld] datadir=/mnt/services/DBs/mysql socket=/mnt/services/DBs/mysql/mysql.sock [client]

[weewx-user] Re: Problem with djr80 windrose and weewx 3.7.0

Hi, Works perfect, thank you for your work. michael http://wetter-wien.bplaced.com Am Montag, 13. März 2017 14:06:07 UTC+1 schrieb gjr80: > > I have published v2.1.0 which fixes the above problem. It can be > downloaded here . > > Gary >

[weewx-user] #1 - Missing 20 days in monthly summary #2 - User guide error?

weewx v3.6.2 on the new Fitlet, weewx 3.0.1 on the old FIT #1: I've just brought up weewx on another Fitlet (CompuLab fanless) and have it running okay. Poking around I discovered I'm missing Feb 1 to Feb 20 in the monthly summary. I copied over the weewx.sdb from the old FIT to the new

[weewx-user] Re: Kindly clarify hand on the dependencies between archive_interval polling_interval & read_period:

you want this: set hardware's archive interval to 5 minutes (300 seconds) wee_device --set-interval=5 set weewx archive interval to match the hardware archive interval [StdArchive] archive_interval = 300 poll the hardware every 60 seconds [FineOffsetUSB] polling_interval = 60 m --

[weewx-user] Re: wee_extension: command not found: How do I run the wee_extension from bash session within a docker container.

On Monday, March 13, 2017 at 2:49:45 PM UTC-4, mr wrote: > > Based on the above Dockerfile, which rings and hoops do I need to jump > through in order to run the following command within a weewx container? > try specifying the full path to wee_extension. since you are installing to

[weewx-user] Re: Lost rapidfire to Wunderground with 3.7.0

I figured that. Did I do it? Or was it introduced from an update? Night -- 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.

[weewx-user] Kindly clarify hand on the dependencies between archive_interval polling_interval & read_period:

Hello, After reading through documentation and forum I am still confused. Since my cognitive style is "work by example" I will describe what I try to do and what I think should be done. My Fineoffset should read the met station every five minutes. Then every 30 minutes weewx should ask the

[weewx-user] wee_extension: command not found: How do I run the wee_extension from bash session within a docker container.

Greetings! I am running Weewx as a docker container using the following Dockerfile *FROM debian:jessie* *MAINTAINER Michael.C Ryan m...@iotimpactlabs.com* *#ENV VERSON=3.6.0* *ENV VERSION=3.7.0* *ENV HOME=/home/weewx* *RUN apt-get -y update && apt-get -y upgrade* *RUN apt-get install -y

Re: [weewx-user] Re: Lost rapidfire to Wunderground with 3.7.0

No. That's a typo. You want "False" (not "Falsee") -tk On Mon, Mar 13, 2017 at 10:39 AM, NightTripper wrote: > Is this the problem? > > Mar 13 12:24:52 burgus weewx[855]: engine: Loading service > weewx.restx.StdWunderground > Mar 13 12:24:52 burgus weewx[855]: engine:

[weewx-user] Re: Lost rapidfire to Wunderground with 3.7.0

Mar 13 12:24:52 burgus weewx[855]: Unknown boolean specifier: 'Falsee'. Night -- 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] Re: Lost rapidfire to Wunderground with 3.7.0

Is this the problem? Mar 13 12:24:52 burgus weewx[855]: engine: Loading service weewx.restx.StdWunderground Mar 13 12:24:52 burgus weewx[855]: engine: Caught unrecoverable exception in engine: Mar 13 12:24:52 burgus weewx[855]: Unknown boolean specifier: 'Falsee'. Mar 13 12:24:52

[weewx-user] Re: FineOffsetUSB problem after update 3.7.0 debian repository

This error: ViolatedPrecondition: lastUpdate(2017-03-13 10:05:00 CET (1489395900)) > lastRecord(2017-03-13 09:58:01 CET (1489395481)) solved with: wee_database weewx.conf --drop-daily from: https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data and wee_database weewx.conf

Re: [weewx-user] Re: Lost rapidfire to Wunderground with 3.7.0

Definitely a problem. We should have a solution soon. -tk On Mon, Mar 13, 2017 at 7:51 AM, Mauro De Lauretis < mauro.delaure...@gmail.com> wrote: > > > I have the same problem after uploading to 3.7.0 version > > > Il giorno lunedì 13 marzo 2017 15:12:38 UTC+1, WindnFog ha scritto: > >> Good

[weewx-user] Re: Lost rapidfire to Wunderground with 3.7.0

I have the same problem after uploading to 3.7.0 version Il giorno lunedì 13 marzo 2017 15:12:38 UTC+1, WindnFog ha scritto: > > Good day, gentlemen, > > I just upgraded to 3.7.0. It is working well with the exception of > rapidfire to Wunderground. It works with Wunderground using the

[weewx-user] Lost rapidfire to Wunderground with 3.7.0

Good day, gentlemen, I just upgraded to 3.7.0. It is working well with the exception of rapidfire to Wunderground. It works with Wunderground using the station/password, just seems to kill the Wunderground-RF thread on start up: Mar 13 10:08:43 norge weewx[3814]: engine: Initializing

[weewx-user] Re: FineOffsetUSB problem after update 3.7.0 debian repository

LOG: Mar 13 14:22:09 raspberrypi weewx[20949]: engine: Initializing weewx version 3.7.0 Mar 13 14:22:09 raspberrypi weewx[20949]: engine: Using Python 2.7.9 (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2] Mar 13 14:22:09 raspberrypi weewx[20949]: engine: Platform

[weewx-user] Re: FineOffsetUSB problem after update 3.7.0 debian repository

Hi, Version running were 3.6.2. worked fine!. I cant downgrade with sudo apt-get install weewx-3.6.2 Dont find package. Thanks... El lunes, 13 de marzo de 2017, 14:15:14 (UTC+1), mwall escribió: > > juan, > > please post the log from the time weewx started up. > > what version were you

[weewx-user] Re: FineOffsetUSB problem after update 3.7.0 debian repository

juan, please post the log from the time weewx started up. what version were you running before you upgraded? before you do anything else, you should save a copy of the database /var/lib/weewx/weewx.sdb, and your configuration /etc/weewx/weewx.conf. to downgrade using apt-get: sudo apt-get

[weewx-user] Re: no module named alarm

Hi, Admittedly it was the 28th item in the change log included in the release post : Moved examples out of bin directory. Eliminated experimental directory. Reinforce the use of user directory, eliminate use of examples

[weewx-user] Re: Problem with djr80 windrose and weewx 3.7.0

I have published v2.1.0 which fixes the above problem. It can be downloaded here . Gary On Monday, 13 March 2017 18:13:59 UTC+10, Michael Nepp wrote: > > hi, > > thank you > -- You received this message because you are subscribed to the

[weewx-user] Re: no module named alarm

I copied the alarm.py module to /bin/user and it works fine. I guess the examples dir is no longer included in the paths that modules could be loaded from... On Monday, March 13, 2017 at 8:29:43 AM UTC-4, Constantine Samaklis wrote: > > Hi, > > One of the included examples for a "custom"

[weewx-user] no module named alarm

Hi, One of the included examples for a "custom" service is alarm.py included in the examples directory. I just upgraded from 3.5 to 3.7 and I started getting the following error: Mar 13 08:10:44 raspberrypi weewx[18326]: engine = engine_class(config_dict) Mar 13 08:10:44

[weewx-user] Weather Underground intermittently showing "--" for "Pressure" with Acurite and Rapidfire enabled in 3.7.0.

The data in the MySQL archive (now that it's working) show good values for Pressure, but Weather Underground shows gaps of up to an hour with "pressure" of "--" in both graph and table. I noticed it when I got up this morning and saw that as the current data. This is not a deal breaker, since

[weewx-user] Re: RTC vs NTP on Raspberry Pi 3

I am using a RPi 3 and an RTC. As noted, it's not for accuracy; it's for what happens when you reboot it, in the brief period between the time weewx starts and ntp sets the clock. The clock was cheap and only took a few minutes to set up. On Sunday, March 12, 2017 at 4:38:54 PM UTC-4,

[weewx-user] RTC vs NTP on Raspberry Pi 3

I use an RTC on my Pi's (Pi 2and Pi 3) see the weewx wiki and elsewhere for procedures, the weewx wiki has a specific procedure for the Pi3 Neville -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop

[weewx-user] Re: Problem with djr80 windrose and weewx 3.7.0

hi, thank you -- 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

[weewx-user] Re: Problem with djr80 windrose and weewx 3.7.0

hi, thank you Am Montag, 13. März 2017 09:02:54 UTC+1 schrieb gjr80: > > Hi, > > A change to the weeWX report engine in 3.7.0 has caused the problem. > Interestingly, my 3.7.0 install which is running an earlier verison of the > stacked windrose generator is unaffected. I will fix the current

[weewx-user] Re: Problem with djr80 windrose and weewx 3.7.0

Hi, A change to the weeWX report engine in 3.7.0 has caused the problem. Interestingly, my 3.7.0 install which is running an earlier verison of the stacked windrose generator is unaffected. I will fix the current version of the stacked windrose tonight and post here when the updated version is

[weewx-user] Problem with djr80 windrose and weewx 3.7.0

hi, i get this error with gjr80's windrose 2.0.2 and weewx3.7.0 is it a fault from me or need the windrose a update? with weewx 3.6.2 it works perfekt. Mär 13 08:20:40 Wetter-Server weewx[13275]: reportengine: Unable to >> instantiate generator >>

Re: [weewx-user] Re: Barometer calculation

Thanks for confirmation! Does this formula has a name or source? The more I read, the more it seems complex to understand how to calculate barometer from pressure :-) I mean there are many models/algorithm more or less complex I think also that whatever the formula we talk about 0.0x mbar