That's the one. I used to be a fan of setting things in skin.conf but these
days prefer to override in weewx.conf. The skin.conf increases the risk of
losing user chnages when upgrades occur. Especially the case with
extensions. weewx.conf is not immune to it (losing customisations) but no
Thanks for the replies. I mean the weewx generated 'standard report'.
I've also just seen that the 'weewx.conf' section for [StdReport]
[[StandardReport]] [[[Units]]] Groups has a 'group_pressure' entry
that is set for 'mbar' so I'll try setting that when I get home. (I assume
that this
Thanks Mark,
Adding the field in to the database and dropping the daily values has fixed
the problem. The feels like calculation that is part of the skin now works.
I have been meaning to get back to you on github about the multi channel
fix you posting for me(ratava). The code change for the
setting Group pressure to hPA in skin.conf should do the trick if you are
referring to the weewx generated pages - or you can force the unit change
in just one particular field in the template using the dot notation.
.
On Monday, 28 November 2016 05:32:38 UTC+2, gjr80 wrote:
> What do you mean
What do you mean by 'web output'? The values display on the weewx generated
index.html (for instance) or what is published to the likes of, say, WOW? :)
Gary
On Monday, 28 November 2016 13:26:44 UTC+10, vk3...@gmail.com wrote:
>
> I am running weewx 3.6.2 on a RPi using the standard report.
> I
Nothing special required to use WOW. I ditched it a few months ago for
other reasons. Might need to instrument your code to have a look at exactly
what is being posted.
Gary
On Monday, 28 November 2016 12:58:53 UTC+10, vk3...@gmail.com wrote:
>
> I'm using weewx 3.6.2 and it has been working
Hi Brent,
The issue you have is not one of units I suspect but rather appTemp is not
being stored in the database. By default weewx calculates appTemp and adds
it to the archive record and loop packets received from the weather station
(if it does not already exist - I don't know of any
I am running weewx 3.6.2 on a RPi using the standard report.
I can't find where to change the web output to show 'hPa' for the pressure
measurements, instead of 'mbar'. I've tried 'skin.conf' under
'group_pressure' and in 'units.py' (the definition of 'MetricUnits' and
'MetrixWXUnits' for
Thanks M..
That has sorted Weewx from crashing. I also did have the unrecoverable error
below but I have corrected that by comparing my config with weewx.conf.dist. I
found I had some old template tags from when I was messing with different
templates months ago. No idea why they would
Hi Everyone
I have a brand new weewx site built around the Responsive skin with the
interceptor driver collecting data from a Oregon Scientific setup. Weewx is
configure with the target_unit set to Metric and the database configured to
do so.
The site is working well (
I'm using weewx 3.6.2 and it has been working well on my RPi (even with my
custom driver).
I have recently started sending data to WOW and I've noticed that the wind
direction is always 'NNE' and that the wind speed (which is displayed in
knots on WOW) is always much higher than on the standard
I had the same problem. A bit of research shows that I needed to edit the
/etc/init.d/weewx file so that the
# Required-Start:
line contains '$network'.
This is converted by the tools that translate the SysVInit code to
'systemd' code to wait until the network is operational.
Susan
On
Cool, I will upgrade soon.
As for the hardware sending "less frequently", it looks more like it being
sent randomly, and not at any regular interval:
~~~
Nov 27 00:12:15 raspberrypi weewx[17396]: interceptor: MainThread: mapped
packet: {'barometer': 1006.0, 'usUnits': 17, 'dateTime':
At least it's giving you some warning! Usually they just quietly die.
-tk
On Sun, Nov 27, 2016 at 6:06 PM, Rob Cranfill wrote:
> I am indeed running on borrowed time - that is, on a good old-fashioned
> (and old) SD card. I've been waiting for it to die, any time now.
I am indeed running on borrowed time - that is, on a good old-fashioned
(and old) SD card. I've been waiting for it to die, any time now. Perhaps
this is it.
Thanks - I guess. ;-)
/rob
On Sunday, November 27, 2016 at 12:50:04 PM UTC-8, Tom Keffer wrote:
>
> The error message is cryptic, but
On Sunday, November 27, 2016 at 6:28:41 PM UTC-5, Sam Roza wrote:
>
> BTW, I find it interesting that you ask about readings. I'm at 220M. The
> data the equipment reports is never the same as the data that WU reports.
> For instance, the final reading above is 1012 from the station, but WU
>
So the TEE file, the weewx.log file, and WU table seem to jive. I'm just
not capturing baro data with regularity.
WU
site:
https://www.wunderground.com/personal-weather-station/dashboard?ID=KCASANJO594#history
TEE file:
~~~
mac=0004a369e0d6=c2=0=0=0=1809==1010=0=1=1
On Sunday, November 27, 2016 at 4:26:38 PM UTC-5, Sam Roza wrote:
>
> What does the POST for pressure look like? I'm trying to remember if is
> shows in mb or what?
>
> I'm getting wind data and thermo/hygro data, but can't tell if the
> pressure is buried in the thgr POST or not?
>
packets
THis is currently happening to my barometric pressure, so I'm actively
looking into it.
What does the POST for pressure look like? I'm trying to remember if is
shows in mb or what?
I'm getting wind data and thermo/hygro data, but can't tell if the pressure
is buried in the thgr POST or not?
Hi,
/etc/init.d/weewx
#! /bin/sh
# Author: Tom Keffer
# Startup script for Debian derivatives
#
# the skeleton script in debian 6 does not work properly in package scripts.
# the return/exit codes cause {pre|post}{inst|rm} to fail regardless of the
# script completion status.
The error message is cryptic, but what it means is that the pickle contents
are corrupted. What kind of storage are you using? The problem may be a
failing SD card.
-tk
On Sun, Nov 27, 2016 at 12:19 PM, Rob Cranfill
wrote:
> This is similar to some issues posted
david,
please post /etc/init.d/weewx and /etc/default/weewx
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
This is similar to some issues posted previously, but a) is not exactly the
same, and b) continues to bedevil me. So I humbly ask for any assistance
dealing with this issue. Which is, to post the log (with debug=1), thus:
pi@x10pi /etc/weewx $ tail -f /var/log/syslog | grep weewx
Nov 27
Gary, thanks for the help. Looks like that was the problem. Did the dump
and clear and it has been running for about 10 minutes. The index.html has
been updated and the data has uploaded to my PWS site.
I had read about the dump and clear functions but could not get them to
work because I
Hi,
I've done that but I am still getting this:-
Nov 27 19:49:55 localhost weewx[29712]: engine: Initializing weewx version 3.6.2
Nov 27 19:49:55 localhost weewx[29712]: engine: Using Python 2.7.6 (default,
Jun 22 2015, 17:58:13) #012[GCC 4.8.2]
Nov 27 19:49:56 localhost weewx[29712]: engine:
On Sunday, November 27, 2016 at 1:55:16 PM UTC-5, David Johns wrote:
>
> Hi,
>
> Ok. There is no such directory as etc/defaults on this version of ubuntu.
> So I have added the LD_LIBRARY_PATH to the weewx file in /etc/init.d/
>
> It still did not work starting weewx in the usual way (service
Hi,
Ok. There is no such directory as etc/defaults on this version of ubuntu. So I
have added the LD_LIBRARY_PATH to the weewx file in /etc/init.d/
It still did not work starting weewx in the usual way (service weewx start) and
threw up the original errors.
However, I tried the way you said
On Sun, Nov 27, 2016 at 10:40 AM, Andrew Milner wrote:
> .. or you could just say weewx does not support feather . and
> leave feather users to do their own thing if doing software archive
> record generation from loop packets does not solve the
.. or you could just say weewx does not support feather . and leave
feather users to do their own thing if doing software archive record
generation from loop packets does not solve the problem.
On Sunday, 27 November 2016 20:35:22 UTC+2, Tom Keffer wrote:
> I'm getting lost in
I'm getting lost in where we are.
Let me try another suggestion. If you do not or cannot implement GETTIME on
the feather, how about writing a new driver that inherits from the old
vantage driver, but overrides getTime() and setTime()?
It would look something like this (NOT TESTED):
*File
On Sunday, November 27, 2016 at 1:20:18 PM UTC-5, Sathish Kumar Duraisamy
wrote:
>
> Same question... has anyone installed on the OSX (EI Captain)
>
the macos instructions:
http://weewx.com/docs/macos.htm
were written while testing on 10.10.3 and 10.6.8
not sure what differences you'll
On Sunday, November 27, 2016 at 1:12:04 PM UTC-5, David Johns wrote:
>
> Hi,
>
> I tried those two lines didn't work and have thrown thias up:-
>
good! the LD_LIBRARY_PATH works. be sure to put
LD_LIBRARY_PATH=/opt/owfs/lib
into the file /etc/default/weewx
now you have a problem reading a
I just found set_time(). It has somthing todo with option --set-time. Is
this an option I can trigger via weewx.conf?
Thanks, Gustl
--
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
Same question... has anyone installed on the OSX (EI Captain)
On Monday, June 13, 2016 at 4:50:15 PM UTC+5:30, Arne Skaanes wrote:
>
> Seems like the description for OSX is a couple of years old.
> Anyone successfully installed it on OSX 10.11.x (El Capitan)
> Also seems like the
Am Sonntag, 27. November 2016 14:05:56 UTC+1 schrieb Tom Keffer:
>
> On Sun, Nov 27, 2016 at 3:53 AM, gustl319 > wrote:
>
>> I've done some code searching. Please tell me if I'm right:
>>
>>- on startup do_sync() is called
>>- in do_sync() is a call to getTime()
>>
Hi,
I tried those two lines didn't work and have thrown thias up:-
Nov 27 18:05:35 localhost weewx[27915]: engine: Initializing weewx version 3.6.2
Nov 27 18:05:35 localhost weewx[27915]: engine: Using Python 2.7.6 (default,
Jun 22 2015, 17:58:13) #012[GCC 4.8.2]
Nov 27 18:05:35 localhost
On Sunday, November 27, 2016 at 12:41:38 PM UTC-5, David Johns wrote:
>
> With regards to the rest, I don't understand where to put LD_LIBRARY_PATH
> and also the weewxd
>
first try these two lines at the command prompt:
export LD_LIBRARY_PATH=/opt/owfs/lib
weewxd /etc/weewx/weewx.conf
the
Hi
owfs was installed in /opt/owfs as I believe that is the default when it was
installed by compiling.
With regards to the rest, I don't understand where to put LD_LIBRARY_PATH and
also the weewxd
Weewx is being run as a service. ie sudo service weewx start
There is no RC script as far as
On Sunday, November 27, 2016 at 12:13:25 PM UTC-5, David Johns wrote:
> Nov 27 12:31:15 localhost weewx[23212]: File
>> "/usr/lib/python2.7/dist-packages/ow/*init*.py", line 33, in
>> Nov 27 12:31:15 localhost weewx[23212]: from ow import _OW
>> Nov 27 12:31:15 localhost weewx[23212]:
Hi,
My weewx has been running great for a couple of years on my ubuntu server
14.04LTS and so I thought it was time to update the owfs to 3.1p4 and weewx
to 3.6.2. The updates went fairly swimmingly but when I try and start
weewx, I get this mess in the syslog:-
Nov 27 12:31:15 localhost
On Saturday, November 26, 2016 at 8:53:24 AM UTC-5, WindnFog wrote:
>
> I have a USB camera pointed at my backyard. It takes a picture every 5
> minutes, one minute before weewx does it's calculations and uploads (i.e.
> picture at 04, weewx at 05 and so on.) It works fine now on a cron job
>
Hi Topher,
At this moment in time I am not using weewx-wd.
What I have done is to add this function to my weewx driver.
Which creates a clientraw_wx.txt to tme ramdisk I have on my pi3.
The #
On Sun, Nov 27, 2016 at 3:53 AM, gustl319 wrote:
> I've done some code searching. Please tell me if I'm right:
>
>- on startup do_sync() is called
>- in do_sync() is a call to getTime()
>- getTime() returns the GETTIME answer
>- if the difference to system
I've done some code searching. Please tell me if I'm right:
- on startup do_sync() is called
- in do_sync() is a call to getTime()
- getTime() returns the GETTIME answer
- if the difference to system time is greater than max_drift (5sec) then
a setTime() -> SETTIME sequence is
Andrew, Gary,
thanks a lot...
I will setup a clean 3.6.2 USB-Stick version for my Pi and then go for the
exchange of the data base.
I guess that will work... if not I give the other version(upgrading from
3.1. step by step)
You guys are awesome and fast...
Best for now
Frank
(And yes, I have
Am Sonntag, 27. November 2016 00:07:26 UTC+1 schrieb Tom Keffer:
>
> A dead battery shuts down the Vantage completely but, once replaced, weewx
> will immediately set it to the correct time.
>
I asume this is done by GETTIME / SETTIME combination. During my try I
never saw a SETTIME command. Is
Ken,
Looks like another corrupted logger, that's the second one over the last few
days. I would stop weewx and then use wee_device to dump the logger memory and
then clear the memory:
$ sudo /etc/init.d/weewx stop
$ ./wee_device --dump
You may see a lot of duplicate primary key messages in
If the db change was indeed 3.0.0 then you are, of course, spot on Gary (as
usual), and my belt and braces approach is indeed not necessary. I assumed
(always a dangerous thing to do) from the tenor implied by 'not
understanding' that it had been the db upgrade process that had not been
Now I am not trying to be argumentative this afternoon, but the change from
having a stats database to instead having daily summary tables happened in
v3.0.0. So if the Frank has a working copy of his database (its not clear
to me from his post) he should not need to rebuild anything. That
You should re-install 3.1 and make sure that installation is working
correctly - and then the upgrade to 3.6.2 should make the necessary
database changes for you as part of the upgrade - thus retaining all your
old data.
The archive format is unchanged (only the stats format/structure changed)
50 matches
Mail list logo