Suddenly yesterday my WMR200 stopped talking to Weewx.
It happened after multiple parsing errors when generating HTML-pages (yes -
my bad). I don't know if the engine gave up due to this or if the engine
shutdown is related to the WMR200-driver quitting..
according to the customisation guide
http://weewx.com/docs/customizing.htm#Using_multiple_bindings
I think the tag format is something like:
$niculskinLabels.conditions.aqi_pm2_5($data_binding='aqi_binding').current.aqi_pm2_5
On Sunday, 11 November 2018 09:14:35 UTC+2, jonathan koren wrote:
>
I have been using Weewx since version, well.. probably 2.someting.
On every upgrade I have selected to keep weewx.conf etc as there are
changes in them that I don't want to loose but now many versions later I
note that the weewx.conf on a brand new installation is quite different
from my old
the current versions of weewx will, when updating from one version to the
next, backup the old weewx.conf (by adding the date to the filename) and
update weewx.conf with any .conf changes which are necessary. This means
that you end up with the old weewx.conf backed up and weewx.conf will have
http://weewx.com/docs/usersguide.htm#StdCalibrate can do what you desire.
or set your altitude to 0!!
it is normal however for weather stations to report sea level pressure so
personally the 'correct' way to get pressure rather than barometer onto the
report pages generated by weewx is indeed
My WMR200 is presenting local airpressure ("pressure") on the display but
Weewx have default setting to present sea-lever pressure ("barmometer").
I don't find sea-level-pressure useful as it differs from what the WMR200
is showing. It is also more acurate.
Changing this requires editing
Em domingo, 11 de novembro de 2018 12:32:13 UTC-2, Jose Luiz Kotch escreveu:
>
> Hi All!
>
> I stopped using the other software because I had daily problem of
> restarting and sending data to cwop and wunderground
> and I thought that now with weewx everything is solved,
> but after a few days
Hi All!
I stopped using the other software because I had daily problem of
restarting and sending data to cwop and wunderground
and I thought that now with weewx everything is solved,
but after a few days of use everything stopped, below the log!
Nov 11 12:25:36 raspi-new weewx[6506]:
There seems to be a mismatch between a working system:
*root@RPi3B-Roses:/etc/weewx/skins/Standard# lsusbBus 001 Device 004: ID
0fde:ca01 Oregon Scientific WMRS200 weather stationBus 001 Device 005: ID
0951:1666 Kingston Technology DataTraveler G4Bus 001 Device 003: ID
0424:ec00 Standard
Another one !
root@raspi-new:~# wee_device --current
Using configuration file /etc/weewx/weewx.conf
Using FineOffsetUSB driver version 1.9 (weewx.drivers.fousb)
Traceback (most recent call last):
File "/usr/bin/wee_device", line 54, in
main()
File "/usr/bin/wee_device", line 51, in main
ov 11 06:48:21 raspi-new weewx[7760]: manager: Added record 2018-11-11
06:48:00 -02 (1541926080) to database 'weewx.sdb'
Nov 11 06:48:21 raspi-new weewx[7760]: manager: Added record 2018-11-11
06:48:00 -02 (1541926080) to daily summary in 'weewx.sdb'
Nov 11 06:48:22 raspi-new weewx[7760]: restx:
Thanks for the link. For some reason I couldn’t find it in the manual.
Just in case someone searches the archive, the correct line is:
$current($data_binding=‘aqi_binding’).aqi_pm2_5
On Sunday, November 11, 2018 at 1:07:48 AM UTC-8, Andrew Milner wrote:
>
> according to the customisation guide
I have set up a Stretch VM using the same locale and timezone settings as
you running a .deb weeWX install and I cannot reproduce the fault you are
experiencing. This really brings me back to the your database. I will
instrument one of the weeWX files with some extra logging so we can see
13 matches
Mail list logo
