Hum... that post truncated: Trying again
Mar 30 09:12:14 homepi systemd[1]: Starting LSB: weewx weather system...
Mar 30 09:12:15 homepi weewx[30778]: engine: Initializing weewx version
3.7.1
Mar 30 09:12:15 homepi weewx[30778]: engine: Using Python 2.7.9 (default,
Sep 17 2016, 20:26:04) #012[GC
Glenn,
To understand why things are like they are you need a bit of history. When Tom
first developed weeWX he used the wview schema, I suspect this is why hail and
hailRate are in the schema. It's not much point having a field in the schema if
you don't have the units to support it, hence you
Hi Gary,
Thanks for your considered reply.
It does help, in that it gives some assurance that I'm not, altogether,
losing it. If it's not in there that's fine and that explains why I
couldn't find any references to it in the docs, or in the groups. I'll
appropriate both those columns for my gauge
Thanks Matt...
I made the suggested change but still get essentially the same error:
Mar 30 21:57:59 raspberrypi weewx[7145]: File
"/usr/share/weewx/user/swb.py", line 52, in
Mar 30 21:57:59 raspberrypi weewx[7145]:
weewx.accum.extract_dict['grid_energy'] = weewx.accum
On Thursday, 30 March 2017 20:58:43 UTC+10, Glenn McKechnie wrote:
>
> The conversion rate between the rain vs hail values is an odd one. I
> initially thought it was a straight conversion between Metric and Imperial
> but it's a factor of 70 (and at times 60) which I can't relate to anything;
On Thursday, March 30, 2017 at 7:33:27 AM UTC-4, Andrew Potter wrote:
>
> Thanks Matt...
> I made the suggested change but still get essentially the same error:
>
> Mar 30 21:57:59 raspberrypi weewx[7145]: File
> "/usr/share/weewx/user/swb.py", line 52, in
> Mar 30 21:57:59 raspberryp
andrew,
comment line 52, then add this to your weewx configuration file:
[Accumulator]
[[grid_energy]]
extractor = sum
tom, did i get that right?
m
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and
I know I can't pass for Tom but yes that's right, I am using an identical
stanza with my non-swb inverter under 3.7.1.
Gary
On Thursday, 30 March 2017 21:43:13 UTC+10, mwall wrote:
>
> andrew,
>
> comment line 52, then add this to your weewx configuration file:
>
> [Accumulator]
> [[grid_ene
it looks like cheetahgenerator is defaulting to wx_binding instead of using
kl_binding.
please post your weewx.conf and your kl/skin.conf (remove/obfuscate any
passwords before posting)
the log you posted smells funny. for some reason it shows the startup
sequence twice. normally that would
That was indeed it. I added yet another tweak to the user/extensions.py
here.
weewx.accum.extract_dict['hail'] = weewx.accum.Accum.sum_extract
weewx.accum.extract_dict['hailRate'] = weewx.accum.Accum.sum_extract
donned the trusty headlamp, and went and tipped the buckets...
Viola, the last two l
I think the posting of the log went strange - looks like I copied more than
I expected. Sorry!
Attached conf files. I've not edited the skin conf at all.
F.
pi@homepi:/etc/weewx $ cat weewx.conf
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer
# See the file LICENSE.txt for yo
fraser,
in the file /usr/share/weewx/weewx/cheetahgenerator.py, make these two
changes.
1) change line 480 from this:
try:
archive = self.generator.db_binder.get_manager()
except (KeyError, weewx.UnknownBinding):
pass
to this:
try:
a
>
>
>
> comment line 52, then add this to your weewx configuration file:
>
> [Accumulator]
> [[grid_energy]]
> extractor = sum
>
> tom, did i get that right?
>
>
Yes, I think that's correct, but no one has every actually used this
before! :-)
-tk
--
You received this message because
On Friday, March 24, 2017 at 1:00:38 PM UTC-4, Alec Bennett wrote:
>
> Just wanted to correct this, which after some research I think is wrong:
>
> > Doing some research, it looks like the key to plotting curves in PIL is
> Bezier Curves.
>
> Ater some trial and error I don't think those curves ar
burt,
please try the attached netatmo-0.10rc1.py
move aside your existing netatmo.py and put this one in its place, then
restart weewx
it should do the right scaling for every type of rain reported by the
netatmo stations (Rain, sum_rain_14, sum_rain_1)
m
--
You received this message becaus
At first glance, it looks accurate as it measured about .001 and it is what
I expected in that 5-10 min window (It's raining steady but not a
downpour/TS). But I need to dump the accumulation I already have and rerun
from zero to know for sure. I will watch this and try to test this
afternoon
gjr80 - mwall
Thank you all very much.. This is exactly the bridge I needed.. based on
this I totally understand the documentation now.
I am getting this now..
Traceback (most recent call last):
File "/usr/bin/weewxd", line 64, in
weewx.engine.main(options, args)
File "/usr/share/weew
Added "Import time" and boom we are collecting data..
now the next fun part..
The sensor outputs hectopascals so to convert that in the driver is going
to be fun.
hectopascals = pascals / 100
baro = 0.02952998751*hectopascals
On Thursday, March 30, 2017 at 1:05:58 PM UTC-5, Tommy Denton wrot
Thanks for the explanation.
No, I do not have a SummaryByDay subsection in my skin.conf; I haven't yet
gotten around to implementing a -MM-DD template. That is next on my
To-Do list.
On Wed, Mar 22, 2017 at 7:41 PM, Thomas Keffer wrote:
> Do you have a [[SummaryByDay]] subsection in your s
On Thursday, March 30, 2017 at 2:42:15 PM UTC-4, Tommy Denton wrote:
>
> The sensor outputs hectopascals so to convert that in the driver is going
> to be fun.
>
> hectopascals = pascals / 100
> baro = 0.02952998751*hectopascals
>
>>
>>>
you probably want this:
import weewx.units
...
packet['pres
btw, you'll probably want to slow down the data collection a bit. put a
sleep in the data collection loop like this:
while True:
try:
packet = dict()
...
except IOError, e:
syslog.syslog(...)
time.sleep(10) # wait 10 seconds before getting next set of data
ot
Fantastic! Index.html generated!
(I've not seen any data arrive in influxdb yet though - is there anything I
need to configure to make that so?)
F.
On 30 March 2017 at 14:42, mwall wrote:
> fraser,
>
> in the file /usr/share/weewx/weewx/cheetahgenerator.py, make these two
> changes.
>
> 1) ch
I have more reading to do on the weewx.units but I am fully up and running..
Thank you for all your help!
On Thursday, March 30, 2017 at 2:10:45 PM UTC-5, mwall wrote:
>
> btw, you'll probably want to slow down the data collection a bit. put a
> sleep in the data collection loop like this:
>
>
Forgive me for being stupid, but this is all new to me.
It's the last step, getting the data to weewx, that I'm fuzzy on. Do you
import the csv file with wee_import?
I am going to play with reading my Acurite (and other) wireless sensors
using SDR, which means I can eliminate their display sys
Never mind. I've got it. If I'm going to be using the SDR driver for
everything but this one sensor, I should create a service that runs in the
data_services period that binds to weewx.NEW_ARCHIVE_RECORD . That way I
don't have to write anything to disk .
Now I just need to learn Python. Th
So, is there a workaround that I can put in place?
Regards,
Christopher
On Wednesday, 29 March 2017 00:58:27 UTC+11, Christopher McAvaney wrote:
>
> Yes, I did notice that wview.py in the schemas subdirectory - now a
> weewx.py in the schemas directory
> $ pwd
> /usr/share/weewx
> $ ls schemas/
26 matches
Mail list logo
