You're probably right in that it looks as though the guide assumes apache2
is installed first, before the deb install - although there then appear to
be some linguistic issues with present tense used when maybe it should
be future!! I don't use apache2 either - preferring lighttpd on my rpi.
gt; apache2 according to this guide.
> The correct sequence is to install apache2 first and add weewx later?
> On Wednesday, July 27, 2016 at 11:19:59 AM UTC+2, Andrew Milner wrote:
>> You're probably right in that it looks as though the guide assumes
>> apache2 is
NEW_LOOP_PACKET is the data from the hardware - and depending on the
hardware may be either for all the sensors or just some - different
hardware works in different ways. NEW_ARCHIVE_RECORD will be the average
data values for all sensors received during the archive period (often 5
RPi power supply??
On Sunday, 14 August 2016 03:58:06 UTC+3, Peter Ten Eyck wrote:
> Davis Vantage Vue connect via serial -> USB to Raspberry Pi.
> Now getting:
> Aug 13 20:52:02 weewx weewx: Starting weewx weather system: weewx.
> Aug 13 20:52:02
I just decided to do a fresh install on a new rpi3 with hdd and whilst
following the user guide ran into a few issues.
It seems that the user guide and wiki have been 'tweeked' for .deb package
installs, rendering it a little harder to determine what is needed for a
setup.py install. I think
Thanks Matthew for the clarification (and for doing the update).
On Saturday, 6 August 2016 13:28:19 UTC+3, mwall wrote:
> wiki has been updated.
> you can symlink or copy. which you choose depends on how you like to
> manage your system(s).
You received this message
On Friday, 3 February 2017 20:12:24 UTC+2, Den S wrote:
> From the utilities / weewx_import / importing from Weather Underground /
> To perform a dry run enter the following command:
> wee_import --import-config=/var/tmp/wu.conf --date="2016/01/20
I have been considering having an old RPi outdoors connected to my WH2080
for the sole purpose of extracting the data from the station and would like
to get the loop data so read into another instance of weewx via Wi-Fi
running on another RPi indoors - also on the same local network. Thye
!! At the moment this
is blocking progress and further thoughts on the concept!!!
On Wednesday, 8 February 2017 16:29:35 UTC+2, mwall wrote:
> On Tuesday, February 7, 2017 at 11:14:25 AM UTC-5, Andrew Milner wrote:
>> I have been considering having an old RPi outdoors connect
That's a bit harsh Vince - many people use a webcam to supply weather
images for use on their weewx generated webpages . and the webcam
capture may have to co-exist with the weewx weather station capture and
subsequent data processing. Certainly some time ago I found that my
what more do you want to know?? It is either running or not running
On Monday, 6 February 2017 18:23:43 UTC+2, Jiří Sachl wrote:
> Raspberry Pi 3, Raspian Jessie, system upgrade, weewx 3.6.2
> root@weewx:~# service weewx status
>> [ ok ] Status of weewx weather system: running.
Clay - since weewx configuration changes do not usually require a database
to be dropped and recreated empty can you clarify what reconfiguration
changes you had made and what the logs showed?
On Sunday, 5 February 2017 22:26:35 UTC+2, Clay Jackson wrote:
> Problem solved! Turns out that
> *From:* weewx...@googlegroups.com [mailto:
> weewx...@googlegroups.com ] *On Behalf Of *Andrew Milner
> *Sent:* Sunday, February 5, 2017 8:12 PM
> *To:* weewx-user <weewx...@googlegroups.com >
> *Subject:* Re: [weewx-user] Re: SDR/RTL Process stop
Just comment it out of the image generator section of
skins/Standard/skin.conf to stop the plotg being created and comment out
the references to the appropriate plot in the plot division towards the end
of the templates. You may even be able to use the same method as for the
tabular (see how
I couldn't see any inconsistency in the documentation either - just in your
'example' in the post.
On Friday, 3 February 2017 16:35:47 UTC+2, gjr80 wrote:
> Yes, dates are separated by - not /, I should not have rushed my reply as
> I was going out the door.
> I had a quick
How about posting
1) the logfile
2) the output from running wee_debug
On Friday, 3 February 2017 17:53:58 UTC+2, Jiří Sachl wrote:
> after reboot
>> root@weewx:~# /etc/init.d/weewx status
>> [ ok ] Status of weewx weather system: running.
>> nothing more
> I was truly
What is the theory behind the changes, and how do the changes impact the
various measurements and differ from the original??
On Saturday, 21 January 2017 14:11:30 UTC+2, Darryn Capes-Davis wrote:
> Hi All,
> I have modified the SqtQC service so it can do spike detection. I am after
03:38:08 UTC+1 schrieb Andrew Milner:
>> It may help us if you told us what exactly you are trying to do. To copy
>> data from one database to another - which would be the result of reading
>> data from a MySQL-db does not require a weewx driver. If the data is
It may help us if you told us what exactly you are trying to do. To copy
data from one database to another - which would be the result of reading
data from a MySQL-db does not require a weewx driver. If the data is
already in a db you should not need to parse the data. Are you, for
You can probably get 'odd' things happening if the station emits partial
packets - depending on whether software or hardware is set as being
preferred or specified. If set for hardware preferred, but it is missing,
weewx will supply a value (but ignore correction) - but if present it will
Could the differences you 'observe' be caused by physical factors such as
mounting position above the ground, terrain around sensor, one station in
shade one exposed to sun, not all fan aspirated etc etc?? a strong sun can
really heat up some kinds of soil and vegetation which is then radiated
Can you be more specific? How frequently are the archive records being
saved? Ids the issue with the creation of the html pages, the .png image
files, the ftp of the data to a remote site, or in the browser viewing the
what exactly hap[pens every hour, and/or every 5
ause of the radiated heat from the flat roof. It got much better
> when I moved it to the current location.
> There is a picture of the installation here at:
> On Tuesday, January 24, 2017 a
I suspect the format should be either 2010-21-01 from looking at the csv
example in the weewx documentation - or - 21-01-2010. I'd wait for an
expert to reply though!!
On Friday, 27 January 2017 13:49:50 UTC+2, Thomas Olausson wrote:
> I'm trying to import old archve data from
Have you tried setting raw_datetimeformat in the conf file to match what
The default is %Y-%m-%d and you need %d-%m-%y
On Friday, 27 January 2017 14:46:55 UTC+2, Andrew Milner wrote:
> I suspect the format should be either 2010-21-01 from looking at the csv
> example in the
One thing I noticed when looking at the cumulus file was that the decimal
separator seemed to be ',' rather than '.', as well as the '-' instead of
'/'. Perhaps there should be formatting options in the cumulus file for
dates like the csv - and what about the numeric decimal formats -
y, 27 January 2017 23:49:43 UTC+10, Andrew Milner wrote:
>> One thing I noticed when looking at the cumulus file was that the decimal
>> separator seemed to be ',' rather than '.', as well as the '-' instead of
>> '/'. Perhaps there should be formatting
It IS based on the archive period. If you want to update every 10 minutes
then you need to:
a) stop weewx
b) edit weewx.conf and change archive_interval (in SECONDS) in the
c) either use wee_device --set_interval to change the archive interval in
the wh1080 to match or set
> On Sun, Jan 29, 2017 at 3:36 AM, Andrew Milner <andrew.s...@gmail.com
> > wrote:
>> It IS based on the archive period. If you want to update every 10
>> minutes then you need to:
>> a) stop weewx
>> b) edit weewx.conf and change archive_inte
Being the usual pedantic soul that I am ... so Tom's 'not true' which
implied my post on archive intervals was not true is also not strictly
true. The FTP report timing IS based on the archive timing, but may be
DEFERRED to run LESS frequently by setting a report_timing option if so
Can you provide copies of
1. Existing (old) weewx.conf
2. New (Modified) weewx.conf (with change to bindings)
3. Modification made to fileparse.py (to extend the schema)
On Sunday, 29 January 2017 04:56:22 UTC+2, Robert Mantel wrote:
> Ok, so there is no soc.py because I thought that extending
1. Weewx appeared to install correctly
2. Weewx started to run as a daemon as expected
3. Weewx attempted to read records from your wmr300 station - but I do not
understand the from n/a message
Your log that you show on the video does not begin at the start of weewx -
the log for 5 minutes
Matthew - since you have provided a new driver for Torbjorn to use should I
leave this thread for you to resolve now?? It looks to me as though
everything is basically working as it should.
On Wednesday, 22 February 2017 14:13:42 UTC+2, mwall wrote:
> On Tuesday, February 21, 2017 at
gt; where high wind speeds often cause significant property damage and even
> loss of life.
> 2) Rapidly changing gauges quickly demonstrate to website visitors that
> they are in fact watching near-real-time data.
> On Monday, February 20, 2017 at 10:23
I would prefer to ask the questions - why am I providing 3 second updates?
What practical value do 3 second updates have for most users?? What is the
On Monday, 20 February 2017 19:33:27 UTC+2, tempus wrote:
> This is merely a suggestion for consideration.
> Space characters are
How much bigger are the actual tipper buckets though??
On Saturday, 18 February 2017 12:01:43 UTC+2, Geni wrote:
> The rain sensor on the WH1080 has got a new bigger heated funnel for the
> rain sensor.
> The area is 3.655 times bigger than the original, where and how do I enter
> this in
So since the rain gauge just outputs a tip count, and one tip corresponds
to .3mm or .01" when used with the standard funnel, if the collection area
is 3.655 times greater isn't it just a question of using the calibrate
section of weewx.conf to say rain = rain / 3.655??
On Saturday, 18
What does your database contain in the outTempBatteryStatus field? If it
contains varying values then you just need to add the plots of
outTempBatteryStatus to your skin to get your graph.
On Thursday, 23 February 2017 21:21:18 UTC+2, Jerry Simonowits wrote:
> Thanks much. All of the code I
21 09:26:11 raspberrypi weewx: wmr300: read failed: max retries
> (5) exceeded
> Feb 21 09:26:11 raspberrypi weewx: wmr300: Release interface failed:
> could not release intf 0: Invalid argument
> Feb 21 09:26:11 raspberrypi weewx: engine: Caught WeeWxIOError: read
rrypi dhcpcd: wlan0: fe80::222:7ff:fe4a:ebca
> router available
> Feb 21 07:39:40 raspberrypi dhcpcd: wlan0: DHCPv6 REPLY: No Addresses
> Feb 21 07:41:40 raspberrypi dhcpcd: wlan0: DHCPv6 REPLY: No Addresses
> Feb 21 07:41:40 raspberrypi rsyslo
> router available
> Feb 21 08:23:20 raspberrypi rsyslogd-2007: action 'action 17' suspended,
> next retry is Tue Feb 21 08:24:50 2017 [try http://www.rsyslog.com/e/2007
> Feb 21 08:23:25 raspberrypi dhcpcd: wlan0: fe80::222:7ff:fe4a:ebca
> router av
Have you connected the weather station to the Pi?? The log is saying that
weewx cannot find the weather station plugged into the USB.
If you want to run weewx without a weather station connected to the RPi you
must select 'simulator' as the station type.
If you select a station type of WMR300
> IOError: Config file not found: "/home/pi/weewx.conf".
> pi@raspberrypi:~ $
> 2017-02-21 7:46 GMT+01:00 Andrew Milner <andrew.s...@gmail.com
>> Have you connected the weather station to the Pi?? The log is saying
or to run directly, not as a daemon, try
sudo weewxd /etc/weewx/weewx.conf
On Tuesday, 21 February 2017 08:54:41 UTC+2, Andrew Milner wrote:
> 1. what were you trying to do with the command which you posted?
> 2. how did you install weewx? If you used the deb install th
D|o make sure that you are, as matthew said, comparing apples with apples.
What is the time interval in use on the weather smart system, and what is
the archive interval in the console itself? I still do not see how you
managed to obtain records for the same time period into two different
On Sunday, 12 February 2017 08:09:56 UTC+2, Paolo Benvenuto wrote:
> Hi! I registered on openweathermap, I got a key, but I cannot realize how
> can I get a station_id in order to put it in weewx.con as explained in
in the following examples:
On Sunday, 12 February 2017 13:06:51 UTC+2, Paolo Benvenuto wrote:
> Il giorno domenica 12 febbraio 2017 07:23:56 UTC+1, Andrew
move the driver to the bin/user directory if the reference is user.wh23xx,
or with the other drivers in bin/weewx/drivers and use the reference
weewx.drivers or change the reference to just wh23xx (without the user.
On Sunday, 12 February 2017 10:57:59 UTC+2, Thom Rogers wrote:
On Sunday, 12 February 2017 20:25:12 UTC+2, ge...@embarqmail.com wrote:
> Thanks.. off and running setup
> what driver do I need for Davis ?
> On Sunday, February 12, 2017 at 10:05:23 AM UTC-8, Tom Keffer wrote:
>> Did you install the
Both should work
On Tuesday, 14 February 2017 18:27:57 UTC+2, wysiwyg wrote:
> Hello !
> I just discovered this nice SQL command suggested in this discussion:
> *UPDATE archive SET barometer=barometer+xxx WHERE dateTime < YYY;*
> I'm interested in this to correct an other parameter with
Please provide more details on exactly what did not work, at what time(s).
The log appears to show the images (graphs) being generated correctly.
Did you try and force a refresh of the relevant page(s) in your web
browser? I find I quite often have to hit the 'reload' button to make
what format are you actually using?? I think that %a and %A should be
capitalised by default when used in strftime strings.
On Friday, 17 February 2017 13:15:33 UTC+2, Ruben Navarro Huedo wrote:
> I have been reading customization guide but i don't find how i could do
I suspect the images are being generated into the wrong directory. Can you
either post your weewx.conf or the output from running wee_debug
On Wednesday, 18 January 2017 14:59:46 UTC+2, gjr80 wrote:
> Perhaps there is a language barrier but when I first read this thread this
> morning I
See 'running weewx' in the user guide.
On Thursday, 19 January 2017 14:52:42 UTC+2, Kevin Bosworth wrote:
> How do I run it normally and not as a daemon?
> Sent from Yahoo Mail on Android
> On Thu, Jan 19, 2017 at 4:40 AM, Thomas Keffer
> Things to
If you brouse to /var/www/html/weewx/index.html on your local machine do
you see the correct page AND correct images??
If you browse to /etc/weewx/public_html/index.html on your local machine do
you see the correct page and correct images??
Can you give the output from ls -l *.png in
If you are asking for some help providing more details of the issues will
What specific problems do you have with the charts??
If the issues are just with some of the charts then the output from
wee_debug and the log from startup of weewx until after two or three
Since the log clearly shows an error is being detected by cheetah posting
the output from wee_debug would help as you have something incorrect in
either weewx.conf or skin.conf
On Tuesday, 17 January 2017 20:04:01 UTC+2, alean...@hotmail.com wrote:
Install an RTC, lighttpd, phpmyadmin, SQLite or MySQL, samba, php,
logrotate, - that's about it I think.
On Tuesday, 17 January 2017 05:10:16 UTC+2, Marc Aubry wrote:
> on all my headless rpi, I do install vncserver and Screen for ease of
> remote acess.
> On Monday, January 16, 2017
wrong log for the current situation!!
On Tuesday, 17 January 2017 06:33:46 UTC+2, Marc Aubry wrote:
> Yes i did.
> Wait and see
> So far so good
> On Tuesday, January 17, 2017 at 10:38:36 AM UTC+7, Andrew Milner wrote:
>> Yes, that's what I was
. so maybe i
> forgot to restart weewx after the modif.
> sorry about that.
> for now the system is running since last reboot and i wont change the
> genrator tonight to check if it has any influence.
> thanks for your help.
> On Tuesday, January 17, 201
screen and vncserver.
> the power supply is a branded 3A USB power supply and i did try with other
> power supply.
> i did change the file /home/weewx/user/forrecat.py nd the /etc/
> i did change the /etc/rsyslog.conf as suggested
> On Tuesday, January 1
f you have permission problems when moving or copying files use sudo in
front of the command - for examplesudo mv filea fileb instead of mv
On Wednesday, 18 January 2017 16:28:22 UTC+2, alean...@hotmail.com wrote:
> Thanks to all for the support. Could anyone to explain me
t's is not a clean solution but it should work.
> I would prefer to find a cleanest way to do it.
> Thanks again for your help.
> On Wednesday, January 18, 2017 at 12:20:09 AM UTC+7, Andrew Milner wrote:
>> . or the cables or the physical
My initial reaction is that this would become an incredibly time consuming
calculation without having a additional daily night and day tables holding
max and min like the existing daily tables, and have an associated
service updating them. Thinking aloud perhaps the same can be achieved by
I'd start by having a look at what is inside forecast_table.inc and then
see if you can achieve the desired effect by 'tweaking' the css definitions
of the styles used.
I am guessing that in the css file h1 is defined as being centred - which
is why they work ok.
On Saturday, 20 August 2016
Perhaps you could attach the revised version of the snippet after your
editing in case you have mis-edited or mis-positioned the changes in some
way, which would make it easier to relate what you say happens with the
actual template code which is being executed.
On Sunday, 21 August 2016
See http://weewx.com/docs/usersguide.htm#StdWXCalculate from the user
On Sunday, 21 August 2016 11:31:30 UTC+3, GBW wrote:
> As beginner, I am running weewx on a raspi 3 (setup.py) connected to a
> german TFA Nexus (TE923 clone). Weewx is running fine apart from ocassional
If you have said windchill and/or heat index are hardware generated then:
a) According to WMR300 manual the wmr300 only calculates (and so only
provides) heat index when temp is > 80F and humidity > 40%
b) I do not know how/when windchill is calculated by wmr300 - manual says
it is based on
It is of course quite right and proper that there is not always a heat
index or windchill value - and in fact you can never have both
On Monday, 27 February 2017 14:10:30 UTC+2, Andrew Milner wrote:
> If you have said windchill and/or heat index are hardware genera
I am baffled by WU. I have a 5 minute archive and 5 min upload to WU. A
few months ago I set up a cron task to fill in holes twice a day - and
without fail it uploads 60-70 records each time. It appears that WU
prefers 10 or 15 minute intervals rather than 5 when left to its own
so it is working fine again
On Sunday, 26 February 2017 18:33:43 UTC+2, Torbjørn Aasen wrote:
> traHeatindex3': None, 'extraHeatindex2': None, 'extraHeatindex1': None,
> 'extraHeatindex7': None, 'extraHeatindex6': None, 'extraHeatindex5': None,
> 'extraHeatindex4': None, 'interval':
weewx pre-requisites says what is needed - when using setup.py at least.
On Tuesday, 28 February 2017 14:12:40 UTC+2, Eric Gammeter wrote:
> OK- sounds good on your station setup. I've been tinkering with my Rpi
> for some time now and finally decided to use
Does the wm300 show values for windchill and heat index? weewx software
generated values require temp < 50F and wind > 5mph for windchill and >80F
and humidity > 40% for heatindex otherwise will default to the same
as outdoor temperature.
On Sunday, 26 February 2017 22:01:41 UTC+2, Miguel
> It's a little more fun now that something seems to work
> [image: Innebygd bilde 1]
> [image: Innebygd bilde 2]
> 2017-02-26 17:54 GMT+01:00 Andrew Milner <andrew.s...@gmail.com
>> so it is working fine again
or the wrong version of wee_import or something?
was trying to import from wunder with the command:
sudo ./wee_import --wunder --calc-missing --dry-run --station=ILIMASSO5
On Wednesday, 31 August 2016 11:50:20 UTC+3, Andrew Milner wrote:
> Well I never knew that!!! I use the
Stop weewx running.
Do you still get the message?? If you do then clearly this has nothing to
do with weewx - and the best way of debugging the issue will then be to
forget about weewx until you have solved the basic Ubuntu installation!!!
Disable the startup daemon so weewx won't start when
have you tried, in wxcalculate section, setting
pressure = prefer hardware . or hardware
altimeter = prefer hardware .or software
barometer = prefer hardware ..or software
does not look right to have all three set to software, since at least one
of them should
a picture of the database.
> Op maandag 5 september 2016 03:51:31 UTC+2 schreef Andrew Milner:
>> I'm sorry Jan - but just asking questions without giving full details of
>> precisely what you did, and without attaching the log files makes it very
> On Monday, September 5, 2016 at 8:13:11 PM UTC+10, Andrew Milner wrote:
>> have you tried changing the aggregate interval ??
> Yup, I set it to 30 days
> aggregate_interval = 2592000
You received this message because you are subscribe
id-Weatherboard for UV, InfraRed and radiation.
> This board has also presure, altitude, humidity and temp sensors.
> Hoogtemeter (altitude) is data from the Odroid-Weatherboard.
> From 16.00 hour I started with the weatherboard. after I changed the
> weewx.conf file.
have you tried changing the aggregate interval ??
On Monday, 5 September 2016 12:21:06 UTC+3, John Smith wrote:
> I'm relatively new to weewx and have successfully imported data from a
> previous weather station, and so I have 9 years or so of data and I'd like
> to have ten year graphs.
Vince - the pressure/barometer comes from the console on the 1080, and I
believe FO changed their radio protocol at some stage so it is very
possible for old and new to be incompatible. The values were in the LOOP
records I saw from the log that was posted.
On Saturday, 3 September 2016
I found similar things Liz when I imported 2yrs of data from WU - and found
that many of the negative values were a result of either -- or values
in the WU data. I initially did a quick QC by looking for negative winds,
humidity and barometer, humidity > 100, barometer > 1300, barometer <
t is in the master branch awaiting
> release is still coded as 3.5.0.
> On Thursday, 1 September 2016 12:51:01 UTC+10, Andrew Milner wrote:
>> Sorry, did not understand - do you mean that you need to make changes to
>> wee_import to us
have you tried the smartphone/mobile pages??
On Friday, 2 September 2016 06:45:04 UTC+3, ppmax wrote:
> and never mind. That was easy...I just created a text-only template.
> Thank again,
> On Thursday, September 1, 2016 at 9:19:21 PM UTC-6, ppmax wrote:
don't now what was the cause of this.
> Op zaterdag 3 september 2016 17:42:11 UTC+2 schreef Andrew Milner:
>> Vince - the pressure/barometer comes from the console on the 1080, and I
>> believe FO changed their radio protocol at some stage so it is very
estions my site.
> you did
> Op zondag 4 september 2016 08:10:16 UTC+2 schreef Andrew Milner:
>> Are you saying that when the barometer was missing from the database it
>> was also missing from the weather station console screen, but after
>> deleting s
Or you can force a .conf reload with a hup
You can tell a running instance of weewx to reread its configuration file
by sending it the HUP signal. First run ps to find out the Process ID (PID)
number of the instance, then send it the HUP signal:
ps -a # Note the PID of the
A couple of questions - a) where/how are the WU API key and station ID
specified when retrieving history data from WU? b) Is it possible to
specify start and stop dates and times for the importing from WU via
On Wednesday, 31 August 2016 07:32:30 UTC+3, gjr80 wrote:
Well I never knew that!!! I use the api to get temperatures for another
project - and I guess the only difference is in the format of the returned
On Wednesday, 31 August 2016 11:29:17 UTC+3, gjr80 wrote:
>> a) where/how are the WU API key and station ID specified when retrieving
Is there a utility that will backfill the weewx database (preferably MySQL)
using data retrieved from WU via the WU API - or does anyone have a
recommended approach to achieve this and also generate the derived columns?
You received this message because you are subscribed to the Google
check the wiki
On Monday, 12 September 2016 13:22:01 UTC+3, zkab wrote:
> Some people have very cool skins in the examples of weewx documentation.
> Is there away to download skins or do I have to contact the person who
> made them ?
> If I have to contact them, due to copyright issues, how
The Fine Offset default archive interval is, I think, 30 minutes. If you
have changed nothing and have told weewx to use hardware records then the
updates will be every 30 minutes. You can change the interval by using
wee-util - most people set to 5 minutes I think (300 seconds). You should
Andy - first of all you need to separate in your mind the database and the
outputs from weewx. You have specified a database in US units, so data
will be stored in the database in US units - regardless of how it is output
to either webpages, wunderground or anywhere else!!
Since the database
Rebooting the Pi won't solve all FO1080 lockups though!
What kind of things go 'awry' on your RPi - I've not had (touch wood) any
weewx RPi issues in a few years, and usually only get one FO usb lockup a
year - which usually necessitates completely resetting the FO1080 - removal
What do you have in the examples directory then??
According to the user guide:
- on a deb installation it should be at
/usr/share/weewx/examples I think
On Thursday, 15 September 2016 13:04:39 UTC+3, zkab wrote:
> I have Davis
Looks to me as though the system is still getting started long after it
tried to run weewx and failed to start the driver. Have you tried starting
the system and then starting weewx off the command line rather than as a
daemon? If that works then you need to fiddle around with the start up
Weewx uploads according to the archive interval.
On Sunday, 11 September 2016 08:06:31 UTC+3, vince wrote:
> On Saturday, September 10, 2016 at 10:03:59 PM UTC-7, Cliff Wylie wrote:
>> I need to change how often weewx uploads to the web, can anyone point me
>> to where this implemented.
If you are trying to solve FO lockups by reading the external sensors
directly via a radio receiver of some kind, where do you get the pressure
from?? This comes from the FO console on a FO station, and not from the
On Saturday, 24 September 2016 05:26:25 UTC+3,
5 minute archive usually works just fine.
On Wednesday, 5 October 2016 19:55:02 UTC+3, Double J Entertainment wrote:
> Okay when I get home from work I am gonna turn off rapid updates and then
> configure the archival times down if needed but I will do the adjustments
> slowly to find a good
1 - 100 of 1098 matches
Mail list logo