Hi,
I appreciate you have come up with a solution to your question 3 but,
depending on your requirements, an alternative may be to create a fairly
basic report to create an ascii file to provide the data you want, then you
could simply do $cat filename from the command prompt to display the file
contents, or some program could easily read the file contents. WeeWX
generates reports at the end of each archive period so your report would
always be up-to-date with the latest observation data. For example, a
report template with something like:
$current.dateTime $current.outTemp $current.dewpoint $current.windSpeed
would create a file with contents something like:
12-Apr-2017 17:05 25.3C 12.1C 1.6 km/h
The power of using a template is that you have all of the weeWX
formatting/unit conversion options available (something not available via
SQLite3). Another example:
$current.dateTime.format("%d/%m/%y %H:%M"), $current.outTemp.degree_F.
nolabel, $current.dewpoint.nolabel, $current.windSpeed.mile_per_hour.nolabel
would create a file with contents something like:
12/04/17 17:05, 77.5, 12.1, 1.0
Note if you want comma separated fields put commas in the template, raw
data (without the rounding) can be dsplayed using .raw. You can read about
weeWX' tags, formatting and conversion options in the Customizing templates
<http://weewx.com/docs/customizing.htm#customizing_templates> section in
the Customization Guide.
As for question 1, there are a few steps involved. Broadly speaking:
1. You need to make sure that the data you want to plot is being saved in
the weeWX archive. A driver may well read data from all sensors on a
station but that does not (necessarily) mean that the data is saved to
archive. A simple test is if you can obtain the data you want via a query
on the archive table using SQLite3 (or mySQL) then the data is being saved
to archive and can be plotted. If not you will need to make some changes to
ensure the data is being saved to archive. You might find the Customizing
the database <http://weewx.com/docs/customizing.htm#archive_database>
section in the Customization Guide useful.
2. Once the data concerned is in the archive, you need to have weeWX create
the plots. This can be done by adding to/changing the plots being created
in an existing skin (eg Standard) or creating a new skin. If modifying the
existing Standard skin you would need to edit file skin.conf in the
skins/Standard directory, find the [ImageGenerator] stanza and add new or
edit existing plots; these are the stanzas that start with something like
[[[daybarometer]]]. For example:
[[[newplot]]]
[[[[obs1]]]]
[[[[obs2]]]]
would create an image file newplot.png that plots fields obs1 and obs2. The
weeWX image generator is covered in the Customizing images
<http://weewx.com/docs/customizing.htm#Customizing_images> section of the
Customization Guide.
3. Once you have the plots being generated you will want to display them.
You could display them on one of the Standard skin existing pages by
editing the respective template (eg skins/Standard/index.html.tmpl for
index.html). Locate the div where the plots are included, in this case it s
something like:
<div id="plots">
<img src="daytempdew.png" alt="temperatures" />
<img src="daytempchill.png" alt="heatchill" />
<img src="dayhumidity.png" alt="outside humidity" />
<img src="dayrain.png" alt="rain" />
<img src="daywind.png" alt="wind" />
<img src="daybarometer.png" alt="barometer"/>
<img src="daywinddir.png" alt="Hi Wind" />
<img src="dayinside.png" alt="Inside" />
<img src="daywindvec.png" alt="Wind Vector" />
#if $day.radiation.has_data
<img src="dayradiation.png" alt="Radiation" />
#end if
#if $day.UV.has_data
<img src="dayuv.png" alt="UV Index" />
#end if
#if $day.rxCheckPercent.has_data
<img src="dayrx.png" alt="day rx percent"/>
#end if
</div> <!-- End id "plots" -->
adding in
<img src="newplot.png" alt="new plot" />
would display the plot newplot that I used as an example at 2.
If you do modify the Standard skin I would keep a backup copy of the
modified files, weeWX will respect any changes you make to the Standard
skin, but if things do go astray at least the process of restoring your
chnages is much easier and quicker if you have a backup.
As for your question 2, I can't help you with your question but I would say
that if things go astray, and they do from time to time, the log is your
friend and it is invaluable in tracking down problems. If you are concerend
with disk space maybe just cut down the retention period for your logs. If
you search the forums you will find a few posts on the different approaches
that different folks have taken.
Hope this helps.
Gary
On Tuesday, 11 April 2017 00:34:09 UTC+10, [email protected] wrote:
>
> Hi,
> First of all: successfully running Weewx on Excito B3 (1.2 GHz ARMv5,
> ArchLinux), using RTL dongle and rtl-sdr plugin, CPU utilization with 3x
> Prologue sensor is 5-10% - thanks for great software!
>
> Now, 3 questions I couldn't find good answer for, I'm hoping someone can
> share their own setup.
>
> 1. The Prologue sensors are only giving temp & humidity, so I have 3x temp
> and 3x humidity. One pair is outside, one pair is bottom floor, one pair is
> top floor. Question: how can I modify the skin to show those 6 graphs only?
> (I assume I can't easily source stuff like barometric pressure from
> outside, not my sensors?)
>
> 2. Weewx is logging a lot, since it works I don't really have a reason to
> save it all - can someone share their journald config to output those logs
> to /dev/null? I don't know much about journald configuration.
>
> 3. Is there a way to get the last updates for all sensors from bash? Some
> sqlite query I can run? Would be useful for other scripts I want to run.
>
> Thanks in advance!
>
> Stan
>
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
