Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

Intall 0.6 version now... and same problem. My installation is wit APT



Aug 31 08:25:17 meteomontaos weewx[14817]: reportengine: Found 
configuration file /etc/weewx/skins/Belchertown/skin.conf for report 
Belchertown
Aug 31 08:25:18 meteomontaos weewx[14817]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.belchertown.getData', 'user.belchertown.getForecast', 
'user.belchertown.getEarthquake', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear']
Aug 31 08:25:18 meteomontaos weewx[14817]: manager: Daily summary version 
is 2.0
Aug 31 08:25:18 meteomontaos weewx[14817]: Belchertown Extension: version 
0.6
Aug 31 08:25:25 meteomontaos wee_reports[16397]: reportengine: Caught 
unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
Aug 31 08:25:25 meteomontaos wee_reports[16397]:   start time 
(1514674800) is greater than stop time (1420066800)
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   Traceback (most 
recent call last):
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   obj.start()
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   self.run()
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   ngen = 
self.generate(gen_dict[section_name], self.gen_ts)
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   default_binding)
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 1350, in 
get_extension_list
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   (time_start_vt, 
time_stop_vt, outTemp_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts, 
timespan.stop), 'outTemp', 'max', 86400)
Aug 31 08:25:26 meteomontaos wee_reports[16397]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 315, in __new__
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   raise 
ValueError("start time (%d) is greater than stop time (%d)" % (args[0], 
args[1]))
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   ValueError: start 
time (1514674800) is greater than stop time (1420066800)
Aug 31 08:25:26 meteomontaos wee_reports[16397]:   Generator terminated




Greetings.

El jueves, 30 de agosto de 2018, 20:14:47 (UTC+2), Pat escribió:
>
> Juan, how did you install weewx? APT/YUM or setup.py?
>
> On Thursday, August 30, 2018 at 2:27:32 AM UTC-4, Juan Antonio Mosquera 
> wrote:
>>
>> Hi, my steps>
>>
>> pi@meteomontaos:~ $ sudo vim /etc/weewx/weewx.conf
>> pi@meteomontaos:~ $ sudo wee_extension --install 
>> weewx-belchertown-0.5.tar.gz
>> Request to install 'weewx-belchertown-0.5.tar.gz'
>> Extracting from tar archive weewx-belchertown-0.5.tar.gz
>> Saving installer file to /usr/share/weewx/user/installer/Belchertown
>> Saved configuration dictionary. Backup copy at 
>> /etc/weewx/weewx.conf.20180830075700
>> Finished installing extension 'weewx-belchertown-0.5.tar.gz'
>> pi@meteomontaos:~ $ sudo wee_extension --list
>> Extension NameVersion   Description
>> Belchertown   0.1   A clean modern skin with real time streaming 
>> updates and interactive charts. Modeled after BelchertownWeather.com
>> csv   0.5   Emit loop or archive data in CSV format.
>> pi@meteomontaos:~ $ sudo vim /etc/weewx/weewx.conf
>> pi@meteomontaos:~ $ sudo service weewx stop
>> pi@meteomontaos:~ $ sudo service weewx start
>> pi@meteomontaos:~ $ sudo journalctl -f
>>
>>
>> Change your .py 

Re: [weewx-user] Avoid bad data with StdQC

[gjr80]

Ok, given the most recent anomaly is from 2016 I guess we can give it the 
benefit of the doubt for now. Would be more concerned if it was happening here 
and now. Probably not worth the effort of trying to track down what went wrong, 
hard  enough keeping on top of current issues, let alone old ones :)


Gary

-- 
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: weewx_wd

[gjr80]

Hallo Kalli,

Es tut mir leid, dass ich dich fast vergessen habe.

Ich denke, das, was Sie sehen, ist nur eine weitere Wunderground-Anomalie. 
Die aktuelle Beschreibung der WeeWX-WD wird direkt von der Wunderground API 
übernommen. Wenn du die Wunderground-Bedingungen sagst, meinst du die 
Beschreibung, wenn du deine Station auf wunderground.com betrachtest? Wenn 
ich zum Beispiel meine Station auf wunderground.com betrachte, sehe ich das 
Wort "Sunny", aber wenn ich die Wunderground-API abfrage, bekomme ich das 
Wort "clear" (Sie können überprüfen, was Sie von der Wunderground-API 
erhalten Einfügen der folgenden URL in Ihren Browser - 
http://api.wunderground.com/api/xxx/conditions/pws:1/q/pws:Z.json
 
- ersetzen Sie einfach xxx mit Ihrem API-Schlüssel und Z 
mit Ihrem PWS identifiziert eq IQUEENSL999: Die resultierende Seite sollte 
etwa halb unten einen Eintrag "weather" haben, dass der Eintragstext (zu 
übersetzender Text) der von WeeWX-WD verwendete Text ist.

Wenn Sie das sehen, ist nicht viel zu tun. Die einzige Möglichkeit, dass 
beide zustimmen, wäre, dass WeeWX-WD die wunderground.com-Informationen 
scrappt, das ist nicht etwas, was ich tun will, es ist fragil und nicht 
wirklich geduldet.

I am sorry again for almost forgetting you.

I think that what you are seeing is just another Wunderground anomaly. The 
WeeWX-WD current conditions description is taken directly from the 
Wunderground API. When you say the Wunderground conditions do you mean the 
description when you look at your station on wunderground.com? For example, 
when I look at my station on wunderground.com right now I see the word 
'Sunny', but when I query the Wunderground API I get the word 'clear'(You 
can check what you are getting from the Wunderground API by pasting the 
following URL into your browser - 
http://api.wunderground.com/api/xxx/conditions/pws:1/q/pws:Z.json
 
- just replace xxx with your API key and Z with your PWS 
identified eq IQUEENSL999. The resulting page should have an entry 
'weather' about half way down, that entries text (subject to translation) 
is the text that WeeWX-WD uses)

If this is what you are seeing then there is not too much to be done. The 
only way make them both agree would be for WeeWX-WD to screen scrape the 
wunderground.com information, that is not something I want to do, its 
fragile and not really condoned.


Gruß

Gary

On Saturday, 25 August 2018 16:18:10 UTC+10, Kalli wrote:
>
> Hallo Gary
> ich muss dich nochmal stören.
>
> die Aktuelle Condition mit Wunderground und WD stimmen nicht Überein.
> Wunderground zeigt = Partly Cloudy   und WD zeigt = cloudy
> da kann doch was nicht stimmen, Wunderground ist richtig.
> kannst du da nochmal drüber schauen..
>
> cu. Kalli
>

-- 
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: Switchdoc Grove hardware support?

[gjr80]

Hi,

I am not aware of any explicit support for Grove hardware from Switchdoc 
but there have been a number of posts regarding getting information from 
GrovePi (is that the same ?) into WeeWX. I know one fellow had a GrovePi 
driver that seemed to mostly work but needed some fine tuning, but he 
seemed to go quiet after a while. I suggest you search the weewx-user group 
for GrovePi, there are quite a few threads. I suspect that you will 
ultimately need to develop some of the software yourself, but then since 
you are building your own weather station perhaps that is not such a leap 
for you :) There are plenty of helpful folks here and putting together a 
driver is pretty simple, especially if you have control over what and how 
the station is emitting. You might also want to have a look at the 
Customization Guide, especially the Porting to new hardware 
 section and probably the 
Introduction  as well.

Gary

On Tuesday, 28 August 2018 09:21:35 UTC+10, Gunnar H. Valdimarsson wrote:
>
> I have hardware from switchdoc.com and did make weather station but want 
> to change to Weewx, the interface is much better.
> Have you made support for Grove hardware from Switchdoc?
>
> I am using 
>
>- Interface board 
>
> https://shop.switchdoc.com/collections/grove/products/the-weather-board-w-grove-interface-board-for-weather-instruments-for-raspberry-pi-arduino
>- WeatherRack - Anemometer/Wind /Rain 
>
> https://shop.switchdoc.com/collections/sensors/products/weatherrack-anemometer-wind-rain-for-weatherpiarduino-weatherplus-raspberry-pi-arduino
>- 4 Channel 16 Bit Analog to Digital Converter 
>
> https://shop.switchdoc.com/collections/i2c/products/grove-4-channel-16-bit-analog-to-digital-converter
>-  AM2315 - Encased I2C Temperature/Humidity 
>
> https://shop.switchdoc.com/collections/weather/products/grove-am2315-encased-i2c-temperature-humidity-sensor-for-raspberry-pi-arduino
>
>
> Gunnar H.
> Iceland
>

-- 
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: after raspbian and weewx updates, weewx is still collecting data but stopped publishing to CWOP and Wunderground

[gjr80]

Tom,

At least it is apparent from the log why the CWOP posts are failing, but 
what is the underlying cause is another matter. By default CWOP posts the 
relevant data from the archive record every 10 minutes; however, when the 
data is to be posted it's age is checked and it's considered as stale if it 
is older than 60 seconds. If you look at the log extract you provided you 
can see the 11:20:00 archive record was generated and saved to database at 
11:21:33:

Aug 29 11:21:33 raspberrypi2 weewx[26138]: manager: Added record 2018-08-29 
11:20:00 EDT (1535556000) to database 'weewx.sdb' 
Aug 29 11:21:33 raspberrypi2 weewx[26138]: manager: Added record 2018-08-29 
11:20:00 EDT (1535556000) to daily summary in 'weewx.sdb'

WeeWX attempted to post the 11:20:00 data to CWOP at 11:21:33 but by that 
time the archive record data was 93 seconds old (11:21:33 - 11:20:00) and 
hence it was skipped:

Aug 29 11:21:33 raspberrypi2 weewx[26138]: restx: CWOP: record 2018-08-29 11
:20:00 EDT (1535556000) is stale (93 > 60).

I assume this is the case on each archive record and that is why no CWOP 
records are being posted. However, the underlying reason is another matter. 
I have never used the interceptor driver but it seems odd that the 11:20:00 
record is saved to database at 11:21:33, I would expect that to happen 
about 1 minute earlier, usually within a few seconds of the archive record 
timestamp; perhaps this is a peculiarity of the interceptor driver. Perhaps 
someone knowledgeable on the interceptor driver and your station can 
comment.

In the meantime you get things working by explicitly setting the stale 
config option for CWOP posts. To do this edit weewx.conf and locate the 
[[CWOP]] stanza under [StdRESTful], add in a line stale = 120. You should 
end up with something like:


[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = XXX obfuscated by wee_debug XXX

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
passcode = "removed"
post_interval = 600
server_list = rotate.aprs.net:14580, rotate.aprs.net:14580
stale = 120

Save weewx.conf then restart WeeWX. Monitor your log and hopefully you will 
see CWOP data being posted. Once you are happy you can set debug=0 again 
(and restart WeeWX) to cut down on your log entries.

Gary


On Thursday, 30 August 2018 01:58:47 UTC+10, Boston Tom wrote:
>
> Thank you Gary.  I have attached the weewx conf file and debug log.
>
> Please note that I have set-up an RPI as a wireless access point and am 
> directing the weather station to send data to this WAP.  I then sniff the 
> data off the WAP and process it through weewx.  This set-up has been 
> working for over a year now, but my weather system hardware failed and the 
> company sent me new hardware (Lacrosse).  Ever since the new hardware, it 
> won't upload to CWOP.  It does upload to PWSWeather, so I know the data is 
> being sniffed and processed.  Any help on this matter is much appreciated.  
> Thank you!
>
> Tom
>
> On Tuesday, August 28, 2018 at 8:14:15 PM UTC-4, gjr80 wrote:
>>
>> Hi,
>>
>> We need to have a good look at the log to see what is going on here. Can 
>> I get you to edit weewx.conf, set debug = 1 (line 11), save weewx.conf 
>> then restart WeeWX. Let WeeWX run for say 15 minutes then post an extract 
>> from your log from when you restarted WeeWX through until the 15 minutes 
>> elapsed. Posting your sanitised weewx.conf would also help, probably 
>> easiest done by running wee_debug 
>>  and posting its 
>> output. Just make sure you check the wee_debug output for any sensitive 
>> info, wee_debug is pretty good at obfuscating sensitive info but it is 
>> not perfect.
>>
>> Gary
>>
>> On Wednesday, 29 August 2018 01:49:42 UTC+10, Boston Tom wrote:
>>>
>>> I have a similar problem.  restx says it is going to post to CWOP and 
>>> PWSWeather, but is only posting to PWSWeather (see below)
>>>
>>> I'm not very good at finding things in Linux, so if you could please 
>>> help me find where I can check my Pi for DNS name resolution, I would like 
>>> to make sure it is showing the correct servers.
>>>
>>> Thank you!
>>>
>>>
>>>
>>> Aug 28 11:27:04 raspberrypi2 weewx[3754]: engine: Using binding 
>>> 'wx_binding' to database 'weewx.sdb'
>>> Aug 28 11:27:04 raspberrypi2 weewx[3754]: manager: Starting backfill of 
>>> daily summaries
>>> Aug 28 11:27:04 raspberrypi2 weewx[3754]: restx: StationRegistry: 
>>> Registration not requested.
>>> Aug 28 11:27:04 raspberrypi2 weewx[3754]: restx: Wunderground: Posting 
>>> not enabled.
>>> Aug 28 11:27:04 raspberrypi2 weewx[3754]: restx: PWSWeather: Data for 
>>> station KC1ELF will be posted
>>> Aug 28 

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[John Clark]

/*The files are in /etc/weewx/*/

/*Next I did a reinstall (just in case)*/

john@OptiPlex ~ $ sudo wee_extension --install weewx-belchertown-0.6.tar.gz
[sudo] password for john:
Request to install 'weewx-belchertown-0.6.tar.gz'
Extracting from tar archive weewx-belchertown-0.6.tar.gz
Saving installer file to /usr/share/weewx/user/installer/Belchertown
Saved configuration dictionary. Backup copy at 
/etc/weewx/weewx.conf.20180830204818

Finished installing extension 'weewx-belchertown-0.6.tar.gz'
john@OptiPlex ~ $

/*then I restarted weewx and got the syslog*/

john@OptiPlex ~ $ sudo /etc/init.d/weewx restart
[sudo] password for john:
 * Restarting weewx weather system weewx . [ OK ]
john@OptiPlex ~ $ tail -f /var/log/syslog

/*and clipped out two report cycles starting at*/

Aug 30 21:50:19 OptiPlex weewx[28835]: Belchertown Extension: version 0.6
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: PWSWeather: Published 
record 2018-08-30 21:50:00 CDT (1535683800)
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: Wunderground-PWS: 
Published record 2018-08-30 21:50:00 CDT (1535683800)
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: StationRegistry: Published 
record 2018-08-30 21:50:00 CDT (1535683800)
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: CWOP: Connected to server 
cwop.aprs.net:14580
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: CWOP: Published record 
2018-08-30 21:50:00 CDT (1535683800)
Aug 30 21:50:20 OptiPlex weewx[28835]: restx: WeatherCloud: Published 
record 2018-08-30 21:50:00 CDT (1535683800)
Aug 30 21:50:24 OptiPlex weewx[28835]: cheetahgenerator: Generated 16 
files for report StandardReport in 4.83 seconds
Aug 30 21:50:24 OptiPlex weewx[28835]: copygenerator: copied 22 files to 
/var/www/html/weewx
Aug 30 21:50:24 OptiPlex weewx[28835]: reportengine: Running report 
Belchertown


/*The rest is the attached file, for message brevity. Also, although 
today's graphs show up on weather.w0avq.org they don't show up on 
localhost/weewx.


*/
On 8/30/2018 3:05 PM, Pat wrote:
Something doesn't seem right. I do not see the version number in this 
log, so I don't think you have 0.6 installed.


You should see something like this in your logs if you are on 0.6

|
Aug3014:20:17weewxlab weewx[14442]:BelchertownExtension:version 0.6
|

Are your files in /home/weewx?

If so, you need to run this command because your wee_extension is in a 
different location.


|
sudo /home/weewx/bin/wee_extension --install weewx-belchertown-0.6.tar.gz
|


You should see some information come back confirming the install is 
successful.


Restart weewx, and look for the logs which indicate "Belchertown 
Extension: version 0.6". Then I'll know you're on the right version.






--
*/John Clark /*

--
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.
Aug 30 21:50:19 OptiPlex weewx[28835]: Belchertown Extension: version 0.6 
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: PWSWeather: Published record 
2018-08-30 21:50:00 CDT (1535683800) 
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: Wunderground-PWS: Published 
record 2018-08-30 21:50:00 CDT (1535683800) 
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: StationRegistry: Published record 
2018-08-30 21:50:00 CDT (1535683800) 
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: CWOP: Connected to server 
cwop.aprs.net:14580 
Aug 30 21:50:19 OptiPlex weewx[28835]: restx: CWOP: Published record 2018-08-30 
21:50:00 CDT (1535683800) 
Aug 30 21:50:20 OptiPlex weewx[28835]: restx: WeatherCloud: Published record 
2018-08-30 21:50:00 CDT (1535683800) 
Aug 30 21:50:24 OptiPlex weewx[28835]: cheetahgenerator: Generated 16 files for 
report StandardReport in 4.83 seconds 
Aug 30 21:50:24 OptiPlex weewx[28835]: copygenerator: copied 22 files to 
/var/www/html/weewx 
Aug 30 21:50:24 OptiPlex weewx[28835]: reportengine: Running report Belchertown 
Aug 30 21:50:24 OptiPlex weewx[28835]: reportengine: Found configuration file 
/etc/weewx/skins/Belchertown/skin.conf for report Belchertown 
Aug 30 21:50:24 OptiPlex weewx[28835]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.belchertown.getData', 'user.belchertown.getForecast', 
'user.belchertown.getEarthquake', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear'] 
Aug 30 21:50:24 OptiPlex weewx[28835]: manager: Daily summary version is 2.0 
Aug 30 21:50:24 OptiPlex weewx[28835]: reportengine: Caught unrecoverable 
exception in generator weewx.cheeta

Re: [weewx-user] Dewpoint does not get reported to Wunderground under rapid fire

[Thomas Keffer]

If WeeWX is not reporting dewpoint in the Rapidfire post, then dewpoint
must not be in the LOOP packet. Or, at least, not often enough to show up
on the WU.

Try running WeeWX directly from the command line
, and watch what
variables have a value in the LOOP packet. The LOOP packets are marked with
the label "LOOP." Records are marked with a label "REC".

-tk

On Thu, Aug 30, 2018 at 2:05 PM  wrote:

> Hi All I am running WEEWX 3.8.2 under ubuntu installed via apt-get from
> the repository.  I have a WMR-918 weather station and under the normal
> setup of wunderground it works fine.  Everything gets updated.  I wanted to
> try rapid fire updates and everything seems to work except dewpoint.  I set
> debug to 2 and this is the packet it is sending to wunderground.  I am not
> sure why dewpoint is missing.
>
>
> http://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw&ID=KMANORTH221&PASSWORD=XXX&softwaretype=weewx-3.8.2&realtime=1&baromin=29.619&humidity=055&dateutc=2018-08-30%2017%3A42%3A14&rtfreq=2.5&dailyrainin=0.00&tempf=82.8&windspeedmph=0.0&windgustmph=0.0&rainin=0.00
>
>
> This isn't a big deal I'll just leave rapidfire off, but maybe it is a bug
> somewhere?  I understand that this weather station sends partial packets
> but after reading several post it seems like there is a cache mode that
> should send out cached data to make the rapid fire data complete.
>
>
>
> --
> 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.
>

-- 
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.

Re: [weewx-user] How to read the total amount of rain for a given day from the database

[Thomas Keffer]

Yes, archive_day_rain holds the calendar day rain in the local time.

The key dateTime in the main archive (table "archive") is in UTC.

-tk

On Thu, Aug 30, 2018 at 1:40 PM Valley  wrote:

> Indeed I am using METRIC, and interval of 300 (5 minutes). I was not aware
> of that the stored unit is cm! Then I get very close to 25.8 but still not
> exactly the same!
> Unfortunately I have no idea how Netatmo calculates daily rainfall, it
> justs reports it. Of course I could use Netamo's API to retrieve the values
> from the Netatmo server (it is impossible to gain access to the local
> receiver, everything has to go via the Netatmo server). However I thought
> reading the weewx database was a quicker way for me than digging into
> Netatmo's coding examples. Netatmo has an example, returning all modules
> data from the last 30 days, and among other things I get:
>
> 27 August:
>
> sum_rain: 25.8 mm
>
> So, if I look at table archive_day_rain, field "sum" has a unit of cm.
> What about the "unit" of date and time, are we talking UTC or local time?
> If I look at the record that has the value closest to 25.8 (25.654) the
> dateTime is 1535320800 which corresponds to 2018-08-27 00:00:00, so I guess
> the date and time are in local values?
>
> When it comes to "daily" rain we have another complicating factor: In
> official reporting "daily" is NOT the calendar day (00-24). To be more
> precise: Officially, the total amount of rain of the 27th of Aug should
> actually have been measured starting 27th of Aug at 08:00, and ending on
> the 28th (!) of Aug 08:00. This is for Sweden (DST, in winter it is 07:00
> instead).
>
> This led me to query "archive" with "select 10*sum(rain) as rain_mm from
> archive where (dateTime >= UNIX_TIMESTAMP('2018-08-27 08:00:00')) and
> (dateTime <= UNIX_TIMESTAMP('2018-08-28 08:00:00')). Result  25.86 which
> indeed is closer to Netatmo's own value of 25.8!
> Querying "archive" with the calendar day "select 10*sum(rain) as rain_mm
> from archive where (dateTime >= UNIX_TIMESTAMP('2018-08-27 00:00:00')) and
> (dateTime <= UNIX_TIMESTAMP('2018-08-27 23:59:59')) results in the same
> value as archive_day_rain, namely 25,65.
>
> This means that table "archive_day_rain" is a calendar day? For all other
> parameters (pressure, wind etc) this is the same as in official reporting
> but in my opinion "archive_day_rain should be calculated between DAY
> 06:00:00 (UTC) and DAY+1 06:00:00 (UTC).
>
> /Valley
>
>
> On Thursday, August 30, 2018 at 2:42:36 AM UTC+2, Thomas Keffer wrote:
>>
>> First of all, I suspect you are using a database with a unit system of
>> METRIC, which measures in centimeters (not millimeters).
>>
>> As for the difference between 25.654 and 25.8, there can be several
>> explanations. Here's one example: say you are using a 5 minute archive
>> interval. For WeeWX, the first archive interval of the day is timestamped
>> 0005. It measures the rain that fell between  and 0005. However, many
>> weather services include the measurement timestamped .
>>
>> To get any more specific, we would need more information, such as exactly
>> what unit system you are using, and how the Netatmo app is calculating
>> daily rainfall.
>>
>> -tk
>>
>>
>> On Wed, Aug 29, 2018 at 2:23 PM Valley  wrote:
>>
>>> I use weewx with a Netatmo rain gauge. It works well but I cannot figure
>>> out how the total amount of daily rain is calculated.
>>>
>>> Since Python is too hard for me to learn, I use php coding to query the
>>> database.
>>>
>>> The other day we got 25.8 mm of rain. A figure reported by my Netatmo
>>> app on the iPhone and on the Netatmo web page. Also very close to what I
>>> could read on an old fashioned measuring glass in the garden. So the figure
>>> 25.8 mm is definitely ok.
>>>
>>> The graph in weewx also shows 25.8 (hard to read exactly, but somewhere
>>> between 25 and 26) (see image). Now: If I look at the
>>> table archive_day_rain for that specific day it says sum=2.5654 (also
>>> wsum=2.5654). How is 2.5654 becoming 25.8? Difference between sum and wsum?
>>>
>>> I also queried the archive table with sum(rain) for all records for that
>>> date. As a result I got 2.5654, the same as in the sum column in table
>>> archive_day_rain.
>>>
>>> So the question is: How is the original data from Netatmo actually
>>> stored, and how is it that the graph shows me the correct amount?
>>>
>>> Very puzzling for me!
>>>
>>> /Valley
>>>
>>> Here is a picture of the graph
>>>
>>> [image: raingraph.png]
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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: migrate an sql DB to another machine?

[vince]

On Thursday, August 30, 2018 at 2:15:25 PM UTC-7, Eric Gammeter wrote:
>
> Thanks all-  I think I misread/misunderstood the size of the original sdb 
> file-  I thought it was big enough to contain all the archived data for the 
> year-  I expected it to have all the 2018 data- but it didn't turn out that 
> way.  End of this story.  /Eric
>
>
>
Unless your disk filled on the old system, it should have just grown as 
needed.  There's nothing pre-allocated re: size of a sqlite3 db
 

-- 
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: migrate an sql DB to another machine?

[Eric Gammeter]

Thanks all-  I think I misread/misunderstood the size of the original sdb 
file-  I thought it was big enough to contain all the archived data for the 
year-  I expected it to have all the 2018 data- but it didn't turn out that 
way.  End of this story.  /Eric

On Tuesday, August 28, 2018 at 11:31:27 AM UTC-4, Eric Gammeter wrote:
>
> Hi-  
>
> I have been running weewx 3.8.2-1 for a year on my main debian PC-  It ran 
> SQL and created a weewx.sdb file (32kb).  Now I would like to migrate 
> that database file onto a RaspberryPi PC and operate weewx on the Rpi...My 
> question is this:  Is there a way to migrate my weewx.sdb file into the RPi 
> weewx application?  
> Many thanks- /E
>

-- 
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] Dewpoint does not get reported to Wunderground under rapid fire

[mattr100]

Hi All I am running WEEWX 3.8.2 under ubuntu installed via apt-get from the 
repository.  I have a WMR-918 weather station and under the normal setup of 
wunderground it works fine.  Everything gets updated.  I wanted to try 
rapid fire updates and everything seems to work except dewpoint.  I set 
debug to 2 and this is the packet it is sending to wunderground.  I am not 
sure why dewpoint is missing.

http://rtupdate.wunderground.com/weatherstation/updateweatherstation.php?action=updateraw&ID=KMANORTH221&PASSWORD=XXX&softwaretype=weewx-3.8.2&realtime=1&baromin=29.619&humidity=055&dateutc=2018-08-30%2017%3A42%3A14&rtfreq=2.5&dailyrainin=0.00&tempf=82.8&windspeedmph=0.0&windgustmph=0.0&rainin=0.00


This isn't a big deal I'll just leave rapidfire off, but maybe it is a bug 
somewhere?  I understand that this weather station sends partial packets 
but after reading several post it seems like there is a cache mode that 
should send out cached data to make the rapid fire data complete.



-- 
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.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Juan Antonio Mosquera]

apt

El jue., 30 ago. 2018 20:14, Pat  escribió:

> Juan, how did you install weewx? APT/YUM or setup.py?
>
> On Thursday, August 30, 2018 at 2:27:32 AM UTC-4, Juan Antonio Mosquera
> wrote:
>>
>> Hi, my steps>
>>
>> pi@meteomontaos:~ $ sudo vim /etc/weewx/weewx.conf
>> pi@meteomontaos:~ $ sudo wee_extension --install
>> weewx-belchertown-0.5.tar.gz
>> Request to install 'weewx-belchertown-0.5.tar.gz'
>> Extracting from tar archive weewx-belchertown-0.5.tar.gz
>> Saving installer file to /usr/share/weewx/user/installer/Belchertown
>> Saved configuration dictionary. Backup copy at
>> /etc/weewx/weewx.conf.20180830075700
>> Finished installing extension 'weewx-belchertown-0.5.tar.gz'
>> pi@meteomontaos:~ $ sudo wee_extension --list
>> Extension NameVersion   Description
>> Belchertown   0.1   A clean modern skin with real time streaming
>> updates and interactive charts. Modeled after BelchertownWeather.com
>> csv   0.5   Emit loop or archive data in CSV format.
>> pi@meteomontaos:~ $ sudo vim /etc/weewx/weewx.conf
>> pi@meteomontaos:~ $ sudo service weewx stop
>> pi@meteomontaos:~ $ sudo service weewx start
>> pi@meteomontaos:~ $ sudo journalctl -f
>>
>>
>> Change your .py and result>
>>
>>
>> Aug 30 08:25:41 meteomontaos weewx[11275]: reportengine: Caught
>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   start time (1514674800)
>> is greater than stop time (1420066800)
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   Traceback (most recent
>> call last):
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   obj.start()
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   self.run()
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   ngen =
>> self.generate(gen_dict[section_name], self.gen_ts)
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   ngen +=
>> self.generate(section[subsection], gen_ts)
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   ngen +=
>> self.generate(section[subsection], gen_ts)
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   default_binding)
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   searchList +=
>> obj.get_extension_list(timespan, db_lookup)
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 1350, in
>> get_extension_list
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   (time_start_vt,
>> time_stop_vt, outTemp_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts,
>> timespan.stop), 'outTemp', 'max', 86400)
>> Aug 30 08:25:41 meteomontaos weewx[11275]: File
>> "/usr/share/weewx/weeutil/weeutil.py", line 315, in __new__
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   raise
>> ValueError("start time (%d) is greater than stop time (%d)" % (args[0],
>> args[1]))
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   ValueError: start time
>> (1514674800) is greater than stop time (1420066800)
>> Aug 30 08:25:41 meteomontaos weewx[11275]:   Generator terminated
>>
>>
>>
>> El miércoles, 29 de agosto de 2018, 17:42:41 (UTC+2), Pat escribió:
>>>
>>> So you get that error with 0.5? Or you re-install and it is OK now?
>>>
>>> On Wednesday, August 29, 2018 at 11:32:36 AM UTC-4, Juan Antonio
>>> Mosquera wrote:

 I installed 0.5 version... and weewx 3.8.2 running in Raspberry Pi B+.
 And now... I uninstalled your extension. When extension running OK I
 install it.

 El miércoles, 29 de agosto de 2018, 17:24:27 (UTC+2), Pat escribió:
>
> Juan, which version did you install? This particular error should
> have been resolved in 0.5
> . Please
> upgrade to that version.
>
>
> On Wednesday, August 29, 2018 at 11:16:52 AM UTC-4, Juan Antonio
> Mosquera wrote:
>>
>> My result is:
>>
>>
>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: reportengine: Caught
>> unrecoverable exception in generator 
>> weewx.cheetahgenerator.CheetahGenerator
>

Re: [weewx-user] How to read the total amount of rain for a given day from the database

[Valley]

Indeed I am using METRIC, and interval of 300 (5 minutes). I was not aware 
of that the stored unit is cm! Then I get very close to 25.8 but still not 
exactly the same!
Unfortunately I have no idea how Netatmo calculates daily rainfall, it 
justs reports it. Of course I could use Netamo's API to retrieve the values 
from the Netatmo server (it is impossible to gain access to the local 
receiver, everything has to go via the Netatmo server). However I thought 
reading the weewx database was a quicker way for me than digging into 
Netatmo's coding examples. Netatmo has an example, returning all modules 
data from the last 30 days, and among other things I get: 

27 August: 

sum_rain: 25.8 mm

So, if I look at table archive_day_rain, field "sum" has a unit of cm. 
What about the "unit" of date and time, are we talking UTC or local time? 
If I look at the record that has the value closest to 25.8 (25.654) the 
dateTime is 1535320800 which corresponds to 2018-08-27 00:00:00, so I guess 
the date and time are in local values?

When it comes to "daily" rain we have another complicating factor: In 
official reporting "daily" is NOT the calendar day (00-24). To be more 
precise: Officially, the total amount of rain of the 27th of Aug should 
actually have been measured starting 27th of Aug at 08:00, and ending on 
the 28th (!) of Aug 08:00. This is for Sweden (DST, in winter it is 07:00 
instead). 

This led me to query "archive" with "select 10*sum(rain) as rain_mm from 
archive where (dateTime >= UNIX_TIMESTAMP('2018-08-27 08:00:00')) and 
(dateTime <= UNIX_TIMESTAMP('2018-08-28 08:00:00')). Result  25.86 which 
indeed is closer to Netatmo's own value of 25.8!
Querying "archive" with the calendar day "select 10*sum(rain) as rain_mm 
from archive where (dateTime >= UNIX_TIMESTAMP('2018-08-27 00:00:00')) and 
(dateTime <= UNIX_TIMESTAMP('2018-08-27 23:59:59')) results in the same 
value as archive_day_rain, namely 25,65. 

This means that table "archive_day_rain" is a calendar day? For all other 
parameters (pressure, wind etc) this is the same as in official reporting 
but in my opinion "archive_day_rain should be calculated between DAY 
06:00:00 (UTC) and DAY+1 06:00:00 (UTC).

/Valley


On Thursday, August 30, 2018 at 2:42:36 AM UTC+2, Thomas Keffer wrote:
>
> First of all, I suspect you are using a database with a unit system of 
> METRIC, which measures in centimeters (not millimeters).
>
> As for the difference between 25.654 and 25.8, there can be several 
> explanations. Here's one example: say you are using a 5 minute archive 
> interval. For WeeWX, the first archive interval of the day is timestamped 
> 0005. It measures the rain that fell between  and 0005. However, many 
> weather services include the measurement timestamped . 
>
> To get any more specific, we would need more information, such as exactly 
> what unit system you are using, and how the Netatmo app is calculating 
> daily rainfall.
>
> -tk
>
>
> On Wed, Aug 29, 2018 at 2:23 PM Valley > 
> wrote:
>
>> I use weewx with a Netatmo rain gauge. It works well but I cannot figure 
>> out how the total amount of daily rain is calculated.
>>
>> Since Python is too hard for me to learn, I use php coding to query the 
>> database.
>>
>> The other day we got 25.8 mm of rain. A figure reported by my Netatmo app 
>> on the iPhone and on the Netatmo web page. Also very close to what I could 
>> read on an old fashioned measuring glass in the garden. So the figure 25.8 
>> mm is definitely ok.
>>
>> The graph in weewx also shows 25.8 (hard to read exactly, but somewhere 
>> between 25 and 26) (see image). Now: If I look at the 
>> table archive_day_rain for that specific day it says sum=2.5654 (also 
>> wsum=2.5654). How is 2.5654 becoming 25.8? Difference between sum and wsum?
>>
>> I also queried the archive table with sum(rain) for all records for that 
>> date. As a result I got 2.5654, the same as in the sum column in table 
>> archive_day_rain.
>>
>> So the question is: How is the original data from Netatmo actually 
>> stored, and how is it that the graph shows me the correct amount?
>>
>> Very puzzling for me!
>>
>> /Valley
>>
>> Here is a picture of the graph
>>
>> [image: raingraph.png]
>>
>> -- 
>> 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+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

Something doesn't seem right. I do not see the version number in this log, 
so I don't think you have 0.6 installed. 

You should see something like this in your logs if you are on 0.6

Aug 30 14:20:17 weewxlab weewx[14442]: Belchertown Extension: version 0.6

Are your files in /home/weewx? 

If so, you need to run this command because your wee_extension is in a 
different location. 

sudo /home/weewx/bin/wee_extension --install weewx-belchertown-0.6.tar.gz


You should see some information come back confirming the install is 
successful. 

Restart weewx, and look for the logs which indicate "Belchertown Extension: 
version 0.6". Then I'll know you're on the right version. 



On Thursday, August 30, 2018 at 3:58:54 PM UTC-4, John Clark wrote:
>
> *As per instructions, I did (copy/paste the commands)*
>
> Quick install:
> wget 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.6.tar.gz
> Then run
> sudo wee_extension --install weewx-belchertown-0.6.tar.gz
>
>
> *in Belchertown/skin.conf, the pertinent lines are *forecast_enabled 
> = 0
> darksky_secret_key = "wouldn't you like to know"
>  earthquake_enabled = 0
>
>
>
> * and in weewx.conf I have * [[[Extras]]]
> forecast_enabled = 1
> darksky_secret_key = "not gonna tell you here either"
> earthquake_enabled = 1
>
> * then I tried both restarting and stop/restarting weewx. The time is 
> corrected on the graphs but there is still no forecast or earthquake info 
> displayed. The pertinent syslog info is* 
>
> Aug 30 14:35:08 OptiPlex weewx[23053]: acurite: next read in 18 seconds
> Aug 30 14:35:26 OptiPlex weewx[23053]: acurite: Found station at bus=002 
> device=011
> Aug 30 14:35:26 OptiPlex weewx[23053]: manager: Added record 2018-08-30 
> 14:35:00 CDT (1535657700) to database 'weewx.sdb'
> Aug 30 14:35:26 OptiPlex weewx[23053]: manager: Added record 2018-08-30 
> 14:35:00 CDT (1535657700) to daily summary in 'weewx.sdb'
> Aug 30 14:35:26 OptiPlex weewx[23053]: restx: StationRegistry: wait 
> interval (2400 < 604800) has not passed for record 2018-08-30 14:35:00 CDT 
> (1535657700)
> Aug 30 14:35:26 OptiPlex weewx[23053]: reportengine: Running reports for 
> latest time in the database.
> Aug 30 14:35:27 OptiPlex weewx[23053]: reportengine: Running report 
> StandardReport
> Aug 30 14:35:27 OptiPlex weewx[23053]: acurite: Found station at bus=002 
> device=011
> Aug 30 14:35:27 OptiPlex weewx[23053]: reportengine: Found configuration 
> file /etc/weewx/skins/Belchertown/skin.conf for report StandardReport
> Aug 30 14:35:27 OptiPlex weewx[23053]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.belchertown.getData', 'user.belchertown.getForecast', 
> 'user.belchertown.getEarthquake', 
> 'user.belchertown_highchartsSearchX.highchartsDay', 
> 'user.belchertown_highchartsSearchX.highchartsWeek', 
> 'user.belchertown_highchartsSearchX.highchartsMonth', 
> 'user.belchertown_highchartsSearchX.highchartsYear']
> Aug 30 14:35:27 OptiPlex weewx[23053]: acurite: next read in 18 seconds
> Aug 30 14:35:27 OptiPlex weewx[23053]: manager: Daily summary version is 
> 2.0
> Aug 30 14:35:27 OptiPlex weewx[23053]: restx: CWOP: Connected to server 
> cwop.aprs.net:14580
> Aug 30 14:35:27 OptiPlex weewx[23053]: restx: CWOP: Published record 
> 2018-08-30 14:35:00 CDT (1535657700)
> Aug 30 14:35:27 OptiPlex weewx[23053]: restx: PWSWeather: Published record 
> 2018-08-30 14:35:00 CDT (1535657700)
> Aug 30 14:35:27 OptiPlex weewx[23053]: restx: Wunderground-PWS: Published 
> record 2018-08-30 14:35:00 CDT (1535657700)
> Aug 30 14:35:29 OptiPlex weewx[23053]: restx: WeatherCloud: Published 
> record 2018-08-30 14:35:00 CDT (1535657700)
> Aug 30 14:35:31 OptiPlex weewx[23053]: cheetahgenerator: Generated 16 
> files for report StandardReport in 4.44 seconds
> Aug 30 14:35:31 OptiPlex weewx[23053]: copygenerator: copied 1 files to 
> /var/www/html/weewx
> Aug 30 14:35:31 OptiPlex weewx[23053]: reportengine: Running report 
> Belchertown
> Aug 30 14:35:31 OptiPlex weewx[23053]: reportengine: Found configuration 
> file /etc/weewx/skins/Belchertown/skin.conf for report Belchertown
> Aug 30 14:35:31 OptiPlex weewx[23053]: cheetahgenerator: using search list 
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
> 'user.belchertown.getData', 'user.belchertown.getForecast', 
> 'user.belchertown.getEarthquake', 
> 'user.belchertown_highchartsSearchX.highchartsDay', 
> 'user.belchertown_highchartsSearchX.highchartsWeek', 
> 'user.belchertown_highchartsSearchX.highchartsMonth', 
> 'user.belchertown_highchartsSearchX.highchartsYear']
> Aug 30 14:35:31 Opt

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[John Clark]

/*As per instructions, I did (copy/paste the commands)*/

    Quick install:
    wget 
https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.6.tar.gz

    Then run
    sudo wee_extension --install weewx-belchertown-0.6.tar.gz

/*in Belchertown/skin.conf, the pertinent lines are

*/    forecast_enabled = 0
    darksky_secret_key = "wouldn't you like to know"
 earthquake_enabled = 0/*

and in weewx.conf I have

*/ [[[Extras]]]
    forecast_enabled = 1
    darksky_secret_key = "not gonna tell you here either"
    earthquake_enabled = 1/*

then I tried both restarting and stop/restarting weewx. The time is 
corrected on the graphs but there is still no forecast or earthquake 
info displayed. The pertinent syslog info is*/


Aug 30 14:35:08 OptiPlex weewx[23053]: acurite: next read in 18 seconds
Aug 30 14:35:26 OptiPlex weewx[23053]: acurite: Found station at bus=002 
device=011
Aug 30 14:35:26 OptiPlex weewx[23053]: manager: Added record 2018-08-30 
14:35:00 CDT (1535657700) to database 'weewx.sdb'
Aug 30 14:35:26 OptiPlex weewx[23053]: manager: Added record 2018-08-30 
14:35:00 CDT (1535657700) to daily summary in 'weewx.sdb'
Aug 30 14:35:26 OptiPlex weewx[23053]: restx: StationRegistry: wait 
interval (2400 < 604800) has not passed for record 2018-08-30 14:35:00 
CDT (1535657700)
Aug 30 14:35:26 OptiPlex weewx[23053]: reportengine: Running reports for 
latest time in the database.
Aug 30 14:35:27 OptiPlex weewx[23053]: reportengine: Running report 
StandardReport
Aug 30 14:35:27 OptiPlex weewx[23053]: acurite: Found station at bus=002 
device=011
Aug 30 14:35:27 OptiPlex weewx[23053]: reportengine: Found configuration 
file /etc/weewx/skins/Belchertown/skin.conf for report StandardReport
Aug 30 14:35:27 OptiPlex weewx[23053]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'user.belchertown.getData', 
'user.belchertown.getForecast', 'user.belchertown.getEarthquake', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear']

Aug 30 14:35:27 OptiPlex weewx[23053]: acurite: next read in 18 seconds
Aug 30 14:35:27 OptiPlex weewx[23053]: manager: Daily summary version is 2.0
Aug 30 14:35:27 OptiPlex weewx[23053]: restx: CWOP: Connected to server 
cwop.aprs.net:14580
Aug 30 14:35:27 OptiPlex weewx[23053]: restx: CWOP: Published record 
2018-08-30 14:35:00 CDT (1535657700)
Aug 30 14:35:27 OptiPlex weewx[23053]: restx: PWSWeather: Published 
record 2018-08-30 14:35:00 CDT (1535657700)
Aug 30 14:35:27 OptiPlex weewx[23053]: restx: Wunderground-PWS: 
Published record 2018-08-30 14:35:00 CDT (1535657700)
Aug 30 14:35:29 OptiPlex weewx[23053]: restx: WeatherCloud: Published 
record 2018-08-30 14:35:00 CDT (1535657700)
Aug 30 14:35:31 OptiPlex weewx[23053]: cheetahgenerator: Generated 16 
files for report StandardReport in 4.44 seconds
Aug 30 14:35:31 OptiPlex weewx[23053]: copygenerator: copied 1 files to 
/var/www/html/weewx
Aug 30 14:35:31 OptiPlex weewx[23053]: reportengine: Running report 
Belchertown
Aug 30 14:35:31 OptiPlex weewx[23053]: reportengine: Found configuration 
file /etc/weewx/skins/Belchertown/skin.conf for report Belchertown
Aug 30 14:35:31 OptiPlex weewx[23053]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 'user.belchertown.getData', 
'user.belchertown.getForecast', 'user.belchertown.getEarthquake', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear']

Aug 30 14:35:31 OptiPlex weewx[23053]: manager: Daily summary version is 2.0
Aug 30 14:35:35 OptiPlex weewx[23053]: cheetahgenerator: Generated 16 
files for report Belchertown in 3.97 seconds
Aug 30 14:35:35 OptiPlex weewx[23053]: copygenerator: copied 1 files to 
/var/www/html/weewx/belchertown

Aug 30 14:35:35 OptiPlex weewx[23053]: reportengine: Running report FTP
Aug 30 14:35:35 OptiPlex weewx[23053]: reportengine: Found configuration 
file /etc/weewx/skins/Ftp/skin.conf for report FTP
Aug 30 14:35:35 OptiPlex weewx[23053]: ftpupload: Attempting connection 
to ftp.w0avq.org

Aug 30 14:35:36 OptiPlex weewx[23053]: ftpupload: Connected to ftp.w0avq.org
Aug 30 14:35:37 OptiPlex weewx[23053]: ftpupload: Uploaded file 
/weather/style.css
Aug 30 14:35:37 OptiPlex weewx[23053]: ftpupload: Uploaded file 
/weather/index.html
Aug 30 14:35:37 OptiPlex weewx[23053]: ftpupload: Uploaded file 
/weather/graphs/index.html
Aug 3

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Pat O'Brien]

Yes I added a version number which shows up in the log when the skin report
is generated.

I was able to fix a couple of items you were asking for. Hope they are good
to go now.

On Thu, Aug 30, 2018, 2:43 PM David Hathaway 
wrote:

> Pat,
>
> I am installing now to https://hathaway.house/weewx/belchertown/
>
> Is there a way to determine the running version?
>
> Dave
>
>
> On Thu, Aug 30, 2018 at 1:15 PM Pat  wrote:
>
>> Version 0.6 is out which fixes a lot of items.
>>
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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: migrate an sql DB to another machine?

[vince]

On Thursday, August 30, 2018 at 11:40:18 AM UTC-7, Eric Gammeter wrote:
>
>
> Thank you Vince-  I get the following reply:
> bash: syntax error near unexpected token `|
>
>
oops - put the semi-colon inside the quotes before the close quote...

echo "select datetime(dateTime,'unixepoch','localtime'),dateTime from 
archive where dateTime > 1535574000 and dateTime < 153558 limit 10;" | 
sqlite3 weewx.sdb
 

>
> On Tuesday, August 28, 2018 at 11:31:27 AM UTC-4, Eric Gammeter wrote:
>>
>> Hi-  
>>
>> I have been running weewx 3.8.2-1 for a year on my main debian PC-  It 
>> ran SQL and created a weewx.sdb file (32kb).  Now I would like to 
>> migrate that database file onto a RaspberryPi PC and operate weewx on the 
>> Rpi...My question is this:  Is there a way to migrate my weewx.sdb file 
>> into the RPi weewx application?  
>> Many thanks- /E
>>
>

-- 
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.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[David Hathaway]

Pat,

I am installing now to https://hathaway.house/weewx/belchertown/

Is there a way to determine the running version?

Dave


On Thu, Aug 30, 2018 at 1:15 PM Pat  wrote:

> Version 0.6 is out which fixes a lot of items.
>
> https://github.com/poblabs/weewx-belchertown/releases
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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: migrate an sql DB to another machine?

[Eric Gammeter]

Thank you Vince-  I get the following reply:
bash: syntax error near unexpected token `|


On Tuesday, August 28, 2018 at 11:31:27 AM UTC-4, Eric Gammeter wrote:
>
> Hi-  
>
> I have been running weewx 3.8.2-1 for a year on my main debian PC-  It ran 
> SQL and created a weewx.sdb file (32kb).  Now I would like to migrate 
> that database file onto a RaspberryPi PC and operate weewx on the Rpi...My 
> question is this:  Is there a way to migrate my weewx.sdb file into the RPi 
> weewx application?  
> Many thanks- /E
>

-- 
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.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

Version 0.6 is out which fixes a lot of items. 

https://github.com/poblabs/weewx-belchertown/releases

-- 
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.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

Juan, how did you install weewx? APT/YUM or setup.py?

On Thursday, August 30, 2018 at 2:27:32 AM UTC-4, Juan Antonio Mosquera 
wrote:
>
> Hi, my steps>
>
> pi@meteomontaos:~ $ sudo vim /etc/weewx/weewx.conf
> pi@meteomontaos:~ $ sudo wee_extension --install 
> weewx-belchertown-0.5.tar.gz
> Request to install 'weewx-belchertown-0.5.tar.gz'
> Extracting from tar archive weewx-belchertown-0.5.tar.gz
> Saving installer file to /usr/share/weewx/user/installer/Belchertown
> Saved configuration dictionary. Backup copy at 
> /etc/weewx/weewx.conf.20180830075700
> Finished installing extension 'weewx-belchertown-0.5.tar.gz'
> pi@meteomontaos:~ $ sudo wee_extension --list
> Extension NameVersion   Description
> Belchertown   0.1   A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> csv   0.5   Emit loop or archive data in CSV format.
> pi@meteomontaos:~ $ sudo vim /etc/weewx/weewx.conf
> pi@meteomontaos:~ $ sudo service weewx stop
> pi@meteomontaos:~ $ sudo service weewx start
> pi@meteomontaos:~ $ sudo journalctl -f
>
>
> Change your .py and result>
>
>
> Aug 30 08:25:41 meteomontaos weewx[11275]: reportengine: Caught 
> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
> Aug 30 08:25:41 meteomontaos weewx[11275]:   start time (1514674800) 
> is greater than stop time (1420066800)
> Aug 30 08:25:41 meteomontaos weewx[11275]:   Traceback (most recent 
> call last):
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> Aug 30 08:25:41 meteomontaos weewx[11275]:   obj.start()
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> Aug 30 08:25:41 meteomontaos weewx[11275]:   self.run()
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
> Aug 30 08:25:41 meteomontaos weewx[11275]:   ngen = 
> self.generate(gen_dict[section_name], self.gen_ts)
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> Aug 30 08:25:41 meteomontaos weewx[11275]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> Aug 30 08:25:41 meteomontaos weewx[11275]:   ngen += 
> self.generate(section[subsection], gen_ts)
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
> Aug 30 08:25:41 meteomontaos weewx[11275]:   default_binding)
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
> Aug 30 08:25:41 meteomontaos weewx[11275]:   searchList += 
> obj.get_extension_list(timespan, db_lookup)
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 1350, in 
> get_extension_list
> Aug 30 08:25:41 meteomontaos weewx[11275]:   (time_start_vt, 
> time_stop_vt, outTemp_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts, 
> timespan.stop), 'outTemp', 'max', 86400)
> Aug 30 08:25:41 meteomontaos weewx[11275]: File 
> "/usr/share/weewx/weeutil/weeutil.py", line 315, in __new__
> Aug 30 08:25:41 meteomontaos weewx[11275]:   raise 
> ValueError("start time (%d) is greater than stop time (%d)" % (args[0], 
> args[1]))
> Aug 30 08:25:41 meteomontaos weewx[11275]:   ValueError: start time 
> (1514674800) is greater than stop time (1420066800)
> Aug 30 08:25:41 meteomontaos weewx[11275]:   Generator terminated
>
>
>
> El miércoles, 29 de agosto de 2018, 17:42:41 (UTC+2), Pat escribió:
>>
>> So you get that error with 0.5? Or you re-install and it is OK now?
>>
>> On Wednesday, August 29, 2018 at 11:32:36 AM UTC-4, Juan Antonio Mosquera 
>> wrote:
>>>
>>> I installed 0.5 version... and weewx 3.8.2 running in Raspberry Pi B+. 
>>> And now... I uninstalled your extension. When extension running OK I 
>>> install it.
>>>
>>> El miércoles, 29 de agosto de 2018, 17:24:27 (UTC+2), Pat escribió:

 Juan, which version did you install? This particular error should have 
 been resolved in 0.5 
 . Please 
 upgrade to that version.


 On Wednesday, August 29, 2018 at 11:16:52 AM UTC-4, Juan Antonio 
 Mosquera wrote:
>
> My result is:
>
>
> Aug 29 17:16:28 meteomontaos wee_reports[4760]: reportengine: Caught 
> unrecoverable exception in generator 
> weewx.cheetahgenerator.CheetahGenerator
> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   start time 
> (1514674800) is greater than stop time (14200668

Re: [weewx-user] Re: Last weewx with WMR-300. Datalogger?

[Ruben Navarro Huedo]

All is very stable again with 3.8.0



El jueves, 30 de agosto de 2018, 12:50:56 (UTC+2), Ruben Navarro Huedo 
escribió:
>
> Tested with 4.4.50 and same problem.
> After some hours weewx stops receiving data.
>
> Returning to weewx 3.8.0
>
> El jueves, 30 de agosto de 2018, 9:22:16 (UTC+2), Juan Antonio Mosquera 
> escribió:
>>
>> Now it seems that it works well ... I do not understand it.
>>
>> O xov., 30/08/2018 ás 09:18, Alberto Sánchez () 
>> escribiu:
>>
>>> I have the same problem with weewx 3.7.1 and the last driver of WMR300. 
>>> My datalogger is not full but weewx doesn't collect the data from it.
>>>
>>> Thanks.
>>>
>>> El miércoles, 29 de agosto de 2018, 19:42:53 (UTC+2), Ruben Navarro 
>>> Huedo escribió:

 I have around the same problem with a WMR180.
 Using kernel 4.4.50 -> All is very stable
 With 4.9.* -> Raspi locks after some hours.


 El miércoles, 29 de agosto de 2018, 17:45:01 (UTC+2), Juan Antonio 
 Mosquera escribió:
>
> Same problem today after restart weewx... its rare... 
>
> If force with wee_reports works fine.
>
> A lot of messages.-...
>
> Aug 29 17:41:46 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
> Aug 29 17:42:06 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
> Aug 29 17:42:27 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
> Aug 29 17:42:47 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
> Aug 29 17:43:08 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
> Aug 29 17:43:28 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
> Aug 29 17:43:49 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
> Aug 29 17:44:09 meteomontaos weewx[7851]: wmr300: dump history is 
> disabled
>
>
> And datalogger not full (21%)
>
> Thanks.
>
> El martes, 28 de agosto de 2018, 17:43:59 (UTC+2), Ruben Navarro Huedo 
> escribió:
>>
>> Hello:
>> Using last weewx (3.8.2) with WMR-300?
>> I think it is not getting data from the datalogger.
>> When weewx is down and after started then all the data when weewx is 
>> down is lost.
>>
>> Have a look at image.
>>
>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/weewx-user/bLanm5XbNVk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> weewx-user+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> -- 
>> http://www.juanantoniomosquera.com
>>
>

-- 
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: weewx, Interceptor, WS-2902A, Skipping Data and Parse Errors

[G Hammer]

Hopefully the error with the AW data can be corrected and perhaps the 
option to select AW or WU data.


On Friday, July 6, 2018 at 8:38:43 PM UTC-4, mwall wrote:
>
>
>
> On Friday, July 6, 2018 at 5:01:07 PM UTC-4, G Hammer wrote:
>>
>> I installed the latest version available on GitHub, but still get the 
>> error/ignored on the AW data. I looked at interceptor.py on GitHub and it 
>> shows version 0.39
>> DRIVER_VERSION = '0.39'
>> DRIVER_NAME = 'Interceptor'
>>
>> Again, not a huge deal as it does not affect the reporting.
>>
>
> sorry about that.  i forgot to bump the version in interceptor.py.  it is 
> now 0.40, and has been tagged.
>
> could you post the log messages about ignored data or parse failures?
>
> i should probably add an option to recognize only aw data or wu data, not 
> both...
>
> 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.

Re: [weewx-user] How to read the total amount of rain for a given day from the database

[Tony Locicero]

⁣Sent from BlueMail ​

On Aug 29, 2018, 8:42 PM, at 8:42 PM, Thomas Keffer  wrote:
>First of all, I suspect you are using a database with a unit system of
>METRIC, which measures in centimeters (not millimeters).
>
>As for the difference between 25.654 and 25.8, there can be several
>explanations. Here's one example: say you are using a 5 minute archive
>interval. For WeeWX, the first archive interval of the day is
>timestamped
>0005. It measures the rain that fell between  and 0005. However,
>many
>weather services include the measurement timestamped .
>
>To get any more specific, we would need more information, such as
>exactly
>what unit system you are using, and how the Netatmo app is calculating
>daily rainfall.
>
>-tk
>
>
>On Wed, Aug 29, 2018 at 2:23 PM Valley  wrote:
>
>> I use weewx with a Netatmo rain gauge. It works well but I cannot
>figure
>> out how the total amount of daily rain is calculated.
>>
>> Since Python is too hard for me to learn, I use php coding to query
>the
>> database.
>>
>> The other day we got 25.8 mm of rain. A figure reported by my Netatmo
>app
>> on the iPhone and on the Netatmo web page. Also very close to what I
>could
>> read on an old fashioned measuring glass in the garden. So the figure
>25.8
>> mm is definitely ok.
>>
>> The graph in weewx also shows 25.8 (hard to read exactly, but
>somewhere
>> between 25 and 26) (see image). Now: If I look at the
>> table archive_day_rain for that specific day it says sum=2.5654 (also
>> wsum=2.5654). How is 2.5654 becoming 25.8? Difference between sum and
>wsum?
>>
>> I also queried the archive table with sum(rain) for all records for
>that
>> date. As a result I got 2.5654, the same as in the sum column in
>table
>> archive_day_rain.
>>
>> So the question is: How is the original data from Netatmo actually
>stored,
>> and how is it that the graph shows me the correct amount?
>>
>> Very puzzling for me!
>>
>> /Valley
>>
>> Here is a picture of the graph
>>
>> [image: raingraph.png]
>>
>> --
>> 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.
>>
>
>-- 
>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.

-- 
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.

Re: [weewx-user] Re: Last weewx with WMR-300. Datalogger?

[Ruben Navarro Huedo]

Tested with 4.4.50 and same problem.
After some hours weewx stops receiving data.

Returning to weewx 3.8.0

El jueves, 30 de agosto de 2018, 9:22:16 (UTC+2), Juan Antonio Mosquera 
escribió:
>
> Now it seems that it works well ... I do not understand it.
>
> O xov., 30/08/2018 ás 09:18, Alberto Sánchez ( >) escribiu:
>
>> I have the same problem with weewx 3.7.1 and the last driver of WMR300. 
>> My datalogger is not full but weewx doesn't collect the data from it.
>>
>> Thanks.
>>
>> El miércoles, 29 de agosto de 2018, 19:42:53 (UTC+2), Ruben Navarro Huedo 
>> escribió:
>>>
>>> I have around the same problem with a WMR180.
>>> Using kernel 4.4.50 -> All is very stable
>>> With 4.9.* -> Raspi locks after some hours.
>>>
>>>
>>> El miércoles, 29 de agosto de 2018, 17:45:01 (UTC+2), Juan Antonio 
>>> Mosquera escribió:

 Same problem today after restart weewx... its rare... 

 If force with wee_reports works fine.

 A lot of messages.-...

 Aug 29 17:41:46 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled
 Aug 29 17:42:06 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled
 Aug 29 17:42:27 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled
 Aug 29 17:42:47 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled
 Aug 29 17:43:08 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled
 Aug 29 17:43:28 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled
 Aug 29 17:43:49 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled
 Aug 29 17:44:09 meteomontaos weewx[7851]: wmr300: dump history is 
 disabled


 And datalogger not full (21%)

 Thanks.

 El martes, 28 de agosto de 2018, 17:43:59 (UTC+2), Ruben Navarro Huedo 
 escribió:
>
> Hello:
> Using last weewx (3.8.2) with WMR-300?
> I think it is not getting data from the datalogger.
> When weewx is down and after started then all the data when weewx is 
> down is lost.
>
> Have a look at image.
>
> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/bLanm5XbNVk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> http://www.juanantoniomosquera.com
>

-- 
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: TE923 failed attempt read data after some time

[Pavel Kocanda]

I tried to change the usb power and it seems it is better. Now it works 
without ending.
mwall thanks for your suggestion.

-- 
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.

Re: [weewx-user] Re: Last weewx with WMR-300. Datalogger?

[Juan Antonio Mosquera]

Now it seems that it works well ... I do not understand it.

O xov., 30/08/2018 ás 09:18, Alberto Sánchez () escribiu:

> I have the same problem with weewx 3.7.1 and the last driver of WMR300. My
> datalogger is not full but weewx doesn't collect the data from it.
>
> Thanks.
>
> El miércoles, 29 de agosto de 2018, 19:42:53 (UTC+2), Ruben Navarro Huedo
> escribió:
>>
>> I have around the same problem with a WMR180.
>> Using kernel 4.4.50 -> All is very stable
>> With 4.9.* -> Raspi locks after some hours.
>>
>>
>> El miércoles, 29 de agosto de 2018, 17:45:01 (UTC+2), Juan Antonio
>> Mosquera escribió:
>>>
>>> Same problem today after restart weewx... its rare...
>>>
>>> If force with wee_reports works fine.
>>>
>>> A lot of messages.-...
>>>
>>> Aug 29 17:41:46 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>> Aug 29 17:42:06 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>> Aug 29 17:42:27 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>> Aug 29 17:42:47 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>> Aug 29 17:43:08 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>> Aug 29 17:43:28 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>> Aug 29 17:43:49 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>> Aug 29 17:44:09 meteomontaos weewx[7851]: wmr300: dump history is
>>> disabled
>>>
>>>
>>> And datalogger not full (21%)
>>>
>>> Thanks.
>>>
>>> El martes, 28 de agosto de 2018, 17:43:59 (UTC+2), Ruben Navarro Huedo
>>> escribió:

 Hello:
 Using last weewx (3.8.2) with WMR-300?
 I think it is not getting data from the datalogger.
 When weewx is down and after started then all the data when weewx is
 down is lost.

 Have a look at image.

 --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/bLanm5XbNVk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
http://www.juanantoniomosquera.com

-- 
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: Last weewx with WMR-300. Datalogger?

[Alberto Sánchez]

I have the same problem with weewx 3.7.1 and the last driver of WMR300. My 
datalogger is not full but weewx doesn't collect the data from it.

Thanks.

El miércoles, 29 de agosto de 2018, 19:42:53 (UTC+2), Ruben Navarro Huedo 
escribió:
>
> I have around the same problem with a WMR180.
> Using kernel 4.4.50 -> All is very stable
> With 4.9.* -> Raspi locks after some hours.
>
>
> El miércoles, 29 de agosto de 2018, 17:45:01 (UTC+2), Juan Antonio 
> Mosquera escribió:
>>
>> Same problem today after restart weewx... its rare... 
>>
>> If force with wee_reports works fine.
>>
>> A lot of messages.-...
>>
>> Aug 29 17:41:46 meteomontaos weewx[7851]: wmr300: dump history is disabled
>> Aug 29 17:42:06 meteomontaos weewx[7851]: wmr300: dump history is disabled
>> Aug 29 17:42:27 meteomontaos weewx[7851]: wmr300: dump history is disabled
>> Aug 29 17:42:47 meteomontaos weewx[7851]: wmr300: dump history is disabled
>> Aug 29 17:43:08 meteomontaos weewx[7851]: wmr300: dump history is disabled
>> Aug 29 17:43:28 meteomontaos weewx[7851]: wmr300: dump history is disabled
>> Aug 29 17:43:49 meteomontaos weewx[7851]: wmr300: dump history is disabled
>> Aug 29 17:44:09 meteomontaos weewx[7851]: wmr300: dump history is disabled
>>
>>
>> And datalogger not full (21%)
>>
>> Thanks.
>>
>> El martes, 28 de agosto de 2018, 17:43:59 (UTC+2), Ruben Navarro Huedo 
>> escribió:
>>>
>>> Hello:
>>> Using last weewx (3.8.2) with WMR-300?
>>> I think it is not getting data from the datalogger.
>>> When weewx is down and after started then all the data when weewx is 
>>> down is lost.
>>>
>>> Have a look at image.
>>>
>>>

-- 
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.