Published v0.2.8 which should gracefully handle missing historical data
when calculating day max/mins.
Gary
On Monday, 27 February 2017 05:02:11 UTC+10, Bill Morrow wrote:
>
> Weewx was rejecting readings around minus 24% (yes, -24%) because they
> were outside my QC settings in StdQC of 0% to
On Sunday, February 26, 2017 at 11:37:49 PM UTC-5, David Lang wrote:
>
> I'm not completely sure this was the issue, the rain totals seem high
> normally,
> and I could have believed 3.5" of rain in the hour that it reported 34"
>
each tip is supposed to be 0.01 inches of rain. the acurite.py
On Sun, 26 Feb 2017, mwall wrote:
On Sunday, February 26, 2017 at 11:15:38 PM UTC-5, David Lang wrote:
It's been wet in Southern California recently, but weewx is reporting that
I've
had 66 inches of rain, which is completely unreasonable :-)
I'm using a AcuRite 02032C weather station and hav
On Sunday, February 26, 2017 at 11:15:38 PM UTC-5, David Lang wrote:
>
> It's been wet in Southern California recently, but weewx is reporting that
> I've
> had 66 inches of rain, which is completely unreasonable :-)
>
> I'm using a AcuRite 02032C weather station and have weewx 3.6.2 installed
It's been wet in Southern California recently, but weewx is reporting that I've
had 66 inches of rain, which is completely unreasonable :-)
I'm using a AcuRite 02032C weather station and have weewx 3.6.2 installed on my
Pi via the weewx apt repo.
What's the best way to fix this?
David Lang
I managed to change the xscale by modifying genplot.py directly. It works
well, and produces images that look like this:
http://sinkingsensation.com/dropbox/daywinddir2.png
But the method is ugly. I modified genplot.py, adding these lines to the
top of the _renderXAxes() function. I have a feelin
I'm trying to customize the xaxis of some of the images generated by
ImageGenerator. I'm making much larger images than stock (800 pixels
across), and once enlarged the X axis resolution isn't very good. It would
make much more sense to have hourly, or bi-hourly labels, without showing
minutes
Rob- thanks for the awesome work on your SFTP mod.
One issue the mod has is that it doesn't create directories on the remote
server if they don't exist. Easily fixed though. I'll upload my fix to
github, or email me off-list if you need it in the meantime.
The gist is:
Search for this section
I've been spending the last few days customizing weewx, which I installed
via apt-get. I was spending a fair amount of time jumping between
directories, and getting confused about file locations. I finally bit the
proverbial bullet and re-installed using setup.py so everything is
contained in /home
Station: WMR300
weewx v3.6.2
Since updated to v3.6.2, I have realised that windchill/heatindex data are
not available in my system.
In weewx.conf the default option for these data is prefer_harware so I
understand that even a station problem would not prevent these data to be
recorded.
I do no
Great!!!
--
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 was rejecting readings around minus 24% (yes, -24%) because they were
outside my QC settings in StdQC of 0% to 100%. It's a problem with the
humidity sensor when the humidity is extreme.
It did this for about a day, while we had a lot of fog and rain.
I widened out the QC limits
[StdQC]
I have had this problem in the past and have found that by adding ferrite
rings to the cable and also reducing the baud rate can help eliminate these
errors. Also, keeping the data cable routed away from sources of RF noise,
such as USB power adapters, the Davis power adapter and also wifi/blue
Could you give me some more details Bill. There is a bug in the code if that
error is being thrown, irrespective of what is going on with outHumidity. That
trace is telling me there is no outHumidty information for the entire day (to
10:26am) which seems odd. When you say weeWX is rejecting your
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
devices, but
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':
traHeatindex3': None, 'extraHeatindex2': None, 'extraHeatindex1': None,
'extraHeatindex7': None, 'extraHeatindex6': None, 'extraHeatindex5': None,
'extraHeatindex4': None, 'interval': 900.0, 'dateTime': 1488108360.0,
'windDir': 153.0, 'outTemp': 0.6001, 'windSpeed': 1.3,
'inHumidity': 2
hello B!
first figure out whether the 'holes' are just at wu or also in your local
database.
check the weewx log - you should see a log message whenever weewx is unable
to connect to wu. however, it is possible that there will be 'holes' in
the data at wu even though there are no warnings or
Hi,
I am using weewx with SDR to report the data from my OS WMR88 sensors to
WU. However, since I started using weewx, I have some "holes" in the data
that are sent to WU. As a consequence, when looking up the data from WU,
the station appears as not updated.
Is there a way to change the rest
It works for me, thank you Gary.
It has been essentially 100% humidity here for about a day, and my humidity
sensor is sending data that weewx rejects. I think that's the reason I am
getting this error:
Feb 26 10:26:08 weewx[22818]: rtgdthread: Traceback (most recent call
last):
Feb 26 1
On Sunday, February 26, 2017 at 7:59:12 AM UTC-5, Torbjørn Aasen wrote:
>
> I think I'm never going to get this to work.
>
you are very close!
please use wmr300.py v0.18rc5 instead of rc4:
sudo /etc/init.d/weewx stop
sudo wget -O wmr300-0.18rc5.py
https://raw.githubusercontent.com/weewx/weewx/
No, the charts can be easily rebuilt once the underlying data is there. The
issue (when going from 1 minute to 5 minutes) is converting the historical data
from a 1 minute basis to a 5 minute basis. Say you have five 1 minute readings
for outside temperature (outTemp) for 9:01, 9:02, 9:03, 9:04
The most recent version of meteotemplate as of today (11.0 passion fruit)
does't have the api function yet.
This will be available in version 12 which will be expected witin one or
two weeks.
On Sunday, 26 February 2017 03:25:00 UTC-3, Ruben Navarro Huedo wrote:
>
> A lot of thanks
> I installe
Thanks for the excellent explanation. I increased the report interval to 5
minutes.
I don't understand this though:
One final thing, if you start using 1 minute and decide later to move to 5
> minutes (or vice versa), there is no simple method to move between the two.
> It can be done but you wil
No real direct disadvantages, you will fill your database quicker than most,
but storage is cheap and it's nothing that the dbms used by weeWX can't handle.
CPU load is not necessarily an issue, unless you make it an issue. WeeWX spends
most of its time reading and storing loop data and doing ot
Thanks for that.
> As far as I knew the Vantage stations only support archive periods of 1,
5, 10, 15, 30, 60 and 120 minutes - 9 minutes sounds odd.
Indeed there's something strange going on, as when I changed the interval
using wee_device it said the interval was set to 30 minutes:
wee_device
Hi,
True, reports are run at the end of each archive period. FTP is really just
another report so by deduction FTP occurs (at best) every archive period.
As far as I knew the Vantage stations only support archive periods of 1, 5, 10,
15, 30, 60 and 120 minutes - 9 minutes sounds odd. No matter.
I've been working on setting up weewx for the last few days, and making
slow but sure progress. I want to make sure I understand this though:
> you can deduce that reports cannot be run more frequently than once at
the end of each archive period
With my hardware (Davis Vantage Pro2), the archi
28 matches
Mail list logo
