[weewx-user] Re: syslog message
Thanks for the response... Yes I'm using record_generation=software... On Thursday, September 8, 2016 at 9:33:31 PM UTC-4, mwall wrote: > > > > On Thursday, September 8, 2016 at 8:40:31 PM UTC-4, Jim W. wrote: >> >> I have been getting this message in my syslog:weewx[753]: fousb: avoid >> 5.89486002922 with debug set to 1. Any ideas? >> Thanks all! >> >> > that is part of the fousb driver debugging output - the 'avoid' measure is > used when figuring out when the hardware will write to memory. > > are you using record_generation=hardware? > > for a fine offset station you'll have better luck with > record_generation=software > > see the 'use correct settings' in this document: > > https://github.com/weewx/weewx/wiki/FineOffset%20USB%20lockup > -- 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-user] Re: syslog message
Thank you Sir! On Thursday, September 8, 2016 at 8:40:31 PM UTC-4, Jim W. wrote: > > I have been getting this message in my syslog:weewx[753]: fousb: avoid > 5.89486002922 with debug set to 1. Any ideas? > Thanks all! > > -- 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-user] Re: syslog message
On Thursday, September 8, 2016 at 8:40:31 PM UTC-4, Jim W. wrote: > > I have been getting this message in my syslog:weewx[753]: fousb: avoid > 5.89486002922 with debug set to 1. Any ideas? > Thanks all! > > that is part of the fousb driver debugging output - the 'avoid' measure is used when figuring out when the hardware will write to memory. are you using record_generation=hardware? for a fine offset station you'll have better luck with record_generation=software see the 'use correct settings' in this document: https://github.com/weewx/weewx/wiki/FineOffset%20USB%20lockup -- 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-user] syslog message
I have been getting this message in my syslog:weewx[753]: fousb: avoid 5.89486002922 with debug set to 1. Any ideas? Thanks all! -- 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-user] WU loses station icon?
About once a day weather underground loses my icon? The blue shaded circle remains but the icon with temperature in the circle goes missing. The actual rapid fire update *stays current* but somehow the position disappears? After an hour or so EVERYTHING disappears (because is not getting position information?!?) A few hours later all is back. WTH? Thanks for any insight... -- 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-user] AS3935 Lightning detector and database creation not working
I have installed the AS3935 service, configured the extensions.py and the
wview.py schema. I found that I needed to modify wview.py in order to get
the extensions to work for some reason.
At this time I have the lightning archive configured as a separate archive.
So far there has been no archive created so I must have something wrong.
For a time I had it archiving to weewx.sdb but was getting an error about
units. At some point I would like to just have one database.
The log file, even with debug on shows nothing untoward. I have attached my
weewx.conf, extensions.py and wview.py. Hopefully someone can see what is
wrong.
Lightning detection doesn't seem to work properly yet but if a database
isn't created I will never see it.
Steve
--
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.
#
#Copyright (c) 2009-2015 Tom Keffer
#
#See the file LICENSE.txt for your full rights.
#
"""The wview schema, which is also used by weewx."""
# =
# This is a list containing the default schema of the archive database. It is
# identical to what is used by wview. It is only used for initialization ---
# afterwards, the schema is obtained dynamically from the database. Although a
# type may be listed here, it may not necessarily be supported by your weather
# station hardware.
#
# You may trim this list of any unused types if you wish, but it will not
# result in saving as much space as you may think --- most of the space is
# taken up by the primary key indexes (type "dateTime").
# =
schema = [('dateTime', 'INTEGER NOT NULL UNIQUE PRIMARY KEY'),
('usUnits', 'INTEGER NOT NULL'),
('interval', 'INTEGER NOT NULL'),
('barometer','REAL'),
('pressure', 'REAL'),
('altimeter','REAL'),
('inTemp', 'REAL'),
('outTemp', 'REAL'),
('inHumidity', 'REAL'),
('outHumidity', 'REAL'),
('windSpeed','REAL'),
('windDir', 'REAL'),
('windGust', 'REAL'),
('windGustDir', 'REAL'),
('rainRate', 'REAL'),
('rain', 'REAL'),
('dewpoint', 'REAL'),
('windchill','REAL'),
('heatindex','REAL'),
('ET', 'REAL'),
('radiation','REAL'),
('UV', 'REAL'),
('extraTemp1', 'REAL'),
('extraTemp2', 'REAL'),
('extraTemp3', 'REAL'),
('soilTemp1','REAL'),
('soilTemp2','REAL'),
('soilTemp3','REAL'),
('soilTemp4','REAL'),
('leafTemp1','REAL'),
('leafTemp2','REAL'),
('extraHumid1', 'REAL'),
('extraHumid2', 'REAL'),
('soilMoist1', 'REAL'),
('soilMoist2', 'REAL'),
('soilMoist3', 'REAL'),
('soilMoist4', 'REAL'),
('leafWet1', 'REAL'),
('leafWet2', 'REAL'),
('rxCheckPercent', 'REAL'),
('txBatteryStatus', 'REAL'),
('consBatteryVoltage', 'REAL'),
('hail', 'REAL'),
('hailRate', 'REAL'),
('heatingTemp', 'REAL'),
('heatingVoltage', 'REAL'),
('supplyVoltage','REAL'),
('referenceVoltage', 'REAL'),
('windBatteryStatus','REAL'),
('rainBatteryStatus','REAL'),
('outTempBatteryStatus', 'REAL'),
('inTempBatteryStatus', 'REAL'),
('lightning_strikes','REAL'),
('lightning','REAL')]
#
#Copyright (c) 2009-2015 Tom Keffer
#
#See the file LICENSE.txt for your full rights.
#
"""User extensions module
This module is imported from the main executable, so anything put here will be
executed before anything else happens. This makes it a good place to put user
extensions.
"""
import locale
# This will use the locale specified by the environment variable 'LANG'
# Other options are possible. See:
# http://docs.python.org/2/library/locale.html#locale.setlocale
locale.setlocale(locale.LC_ALL, '')
# extend the default schema to include lightning
import weewx.units
weewx.units.USUnits['group_distance'] = 'mile'
weewx.units.MetricUnits['group_d
[weewx-user] Re: Driver SDR
On Thursday, September 8, 2016 at 6:41:23 PM UTC-4, Marco Tibaldi wrote: > > it's works! >> > only the time is ahead by 2 hours exactly . ?!? > check the times in the output when you run rtl_433 directly check the timezone setting on the pi the driver gets the timestamps from rtl_433 -- 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-user] Re: Driver SDR
> > it's works! > only the time is ahead by 2 hours exactly . ?!? i have made this mods on weewx.conf for lacrosse sensor: [SDR] # This section is for the software-defined radio driver. # The driver to use driver = user.sdr cmd = /usr/local/bin/rtl_433 [[sensor_map]] wind_gust.9:34.LaCrossePacket = windGust Rainfall.9:34.LaCrossePacket = rain wind_speed.9:34.LaCrossePacket = windSpeed wind_dir.9:34.LaCrossePacket = windDir humidity.9:34.LaCrossePacket = outHumidity temperature.9:34.LaCrossePacket = outTemp and this is the result in web page !! yeah! Current Conditions Outside Temperature 25,2°C Wind Chill 25,2°C Heat Index 25,2°C Dewpoint 14,9°C Humidity 53% Barometer N/A Barometer Trend (3 hours) N/A Wind 0,0 m/s from N/A (N/A) Rain Rate 0,0 mm/hr Inside Temperature N/A any idea for the time? the raspberry time is correct. -- 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-user] Re: Driver SDR
On Thursday, September 8, 2016 at 5:56:42 PM UTC-4, Marco Tibaldi wrote:
>
> Sep 8 23:38:35 SDR weewx[1034]: sdr: MainThread: lines=[]
> Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread: lines=['2016-09-08
> 23:38:41 :\tLaCrosse WS \t:\t9 \t:\t34\n', '\tTemperature:\t 25.3 C\n']
> Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread: ts=1473377921
> payload=LaCrosse WS #011:#0119 #011:#01134
> Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread:
> pkt={'temperature.9:34.LaCrossePacket': 25.3, 'usUnits': 17, 'dateTime':
> 1473377921}
> Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread:
> packet={'temperature.9:34.LaCrossePacket': 25.3, 'usUnits': 17, 'dateTime':
> 1473377921}
>
your sensor cluster is emitting :9 and :34
what kind of hardware are you running on? the driver is getting some of
the rtl_433 output, but some of the output is getting split up. rtl_433
spits out lines of data without a standard format. so the driver has to
guess to figure out where output from one sensor ends and output from
another begins. this is complicated by the fact that it is done
asynchronously - there is one thread that runs the rtl_433 binary and
captures its output, while the weewx main thread waits on a queue for the
output lines.
this is how to debug things. at the lowest level you run rtl_433 directly:
sudo rtl_433
that will spit out data from sensors as the sdr hardware receives them.
next up is to run the driver directly:
PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/sdr.py
that will spit out the data with all recognized data tagged with
identifiers ready for mapping to database fields. it also flags any sensor
output that is not recognized by the driver.
finally, you can run weewxd directly:
sudo weewxd weewx.conf
that will spit out the data mapped to the database fields in 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 options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Driver SDR
i show the log.
> you mean this?
>
Sep 8 23:38:35 SDR weewx[1034]: sdr: MainThread: lines=[]
Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread: lines=['2016-09-08
23:38:41 :\tLaCrosse WS \t:\t9 \t:\t34\n', '\tTemperature:\t 25.3 C\n']
Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread: ts=1473377921
payload=LaCrosse WS #011:#0119 #011:#01134
Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread:
pkt={'temperature.9:34.LaCrossePacket': 25.3, 'usUnits': 17, 'dateTime':
1473377921}
Sep 8 23:38:41 SDR weewx[1034]: sdr: MainThread:
packet={'temperature.9:34.LaCrossePacket': 25.3, 'usUnits': 17, 'dateTime':
1473377921}
Sep 8 23:38:41 SDR weewx[1034]: reportengine: Running reports for latest
time in the database.
Sep 8 23:38:41 SDR weewx[1034]: reportengine: Running report StandardReport
Sep 8 23:38:41 SDR weewx[1034]: reportengine: Found configuration file
/etc/weewx/skins/Standard/skin.conf for report StandardReport
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: lines=['\tHumidity:\t
52\n']
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: ts=None payload=None
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: unhandled message format:
ts=None payload=None
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: lines=['2016-09-08
23:38:42 :\tLaCrosse WS \t:\t9 \t:\t34\n', '\tWind speed:\t 0.0 m/s\n',
'\tDirection:\t 247.500\n']
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: ts=1473377922
payload=LaCrosse WS #011:#0119 #011:#01134
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread:
pkt={'wind_speed.9:34.LaCrossePacket': 0.0, 'wind_dir.9:34.LaCrossePacket':
247.5, 'usUnits': 17, 'dateTime': 1473377922}
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread:
packet={'wind_speed.9:34.LaCrossePacket': 0.0,
'wind_dir.9:34.LaCrossePacket': 247.5, 'usUnits': 17, 'dateTime':
1473377922}
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: lines=['\tTemperature:\t
25.3 C\n']
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: ts=None payload=None
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: unhandled message format:
ts=None payload=None
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: lines=['2016-09-08
23:38:42 :\tLaCrosse WS \t:\t9 \t:\t34\n', '\tHumidity:\t 52\n']
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread: ts=1473377922
payload=LaCrosse WS #011:#0119 #011:#01134
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread:
pkt={'humidity.9:34.LaCrossePacket': 52, 'usUnits': 17, 'dateTime':
1473377922}
Sep 8 23:38:42 SDR weewx[1034]: sdr: MainThread:
packet={'humidity.9:34.LaCrossePacket': 52, 'usUnits': 17, 'dateTime':
1473377922}
Sep 8 23:38:49 SDR weewx[1034]: cheetahgenerator: Generated 14 files for
report StandardReport in 7.09 seconds
Sep 8 23:38:52 SDR weewx[1034]: sdr: MainThread: lines=['\tWind speed:\t
0.0 m/s\n', '\tDirection:\t 247.500\n']
Sep 8 23:38:52 SDR weewx[1034]: sdr: MainThread: ts=None payload=None
Sep 8 23:38:52 SDR weewx[1034]: sdr: MainThread: unhandled message format:
ts=None payload=None
Sep 8 23:38:53 SDR weewx[1034]: genimages: Generated 24 images for
StandardReport in 3.92 seconds
Sep 8 23:38:53 SDR weewx[1034]: reportengine: copied 9 files to
/var/www/weewx
Sep 8 23:38:53 SDR weewx[1034]: reportengine: Running report FTP
--
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.
Re: [weewx-user] Raspberry PI using WH1080WS with extra DHT22 sensor
Great, Tom thanks for your help. I will give it a shot. -- 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-user] Re: Te923 driver is not starting anymore.
On Thursday, September 8, 2016 at 5:47:49 PM UTC-4, Andy Harrold wrote: > > I'm needing to update the te923 driver to the latest version 0.18 > Where is this file located so I can update it ? > I have the latest version from > https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/te923.py > How do I instal it? (Newbie on Raspbian!) > Thanks > assuming a setup.py installation, it looks something like this: 1) stop weewx sudo /etc/init.d/weewx stop 2) move the old driver aside sudo mv /home/weewx/bin/weewx/drivers/te923.py /home/weewx/bin/weewx/drivers/te923-0.17.py 3) put the new driver in place sudo cp ~/Downloads/te923.py /home/weewx/bin/weewx/drivers/te923.py 4) start weewx sudo /etc/init.d/weewx start -- 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-user] Re: Driver SDR
On Thursday, September 8, 2016 at 5:22:35 PM UTC-4, Marco Tibaldi wrote: > > thanks for the reply, i'm testing on la-cross ws2350, > have you a trace for this meteo station sensor? > this is the output i have for lacrosse ws23xx: # 2016-09-08 00:43:52 :LaCrosse WS :9 :202 # Temperature: 21.0 C # 2016-09-08 00:43:53 :LaCrosse WS :9 :202 # Humidity: 92 # 2016-09-08 00:43:53 :LaCrosse WS :9 :202 # Wind speed: 0.0 m/s # Direction: 67.500 if you get something else, please post it. in particular, i would be interested to see what values you get after the 'LaCrosse WS' string - the :9 and :202 in the example above. 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 options, visit https://groups.google.com/d/optout.
[weewx-user] Re: Te923 driver is not starting anymore.
I'm needing to update the te923 driver to the latest version 0.18
Where is this file located so I can update it ?
I have the latest version
from https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/te923.py
How do I instal it? (Newbie on Raspbian!)
Thanks
On Tuesday, 15 March 2016 09:35:51 UTC, Joep L. Blom wrote:
>
> From the start of the new driver I have had problems with it. I begin
> however, to get the suspicion that something in the TFA Nexus has gone
> but I'm not sure as the console display is strictly normal.
> However, yesterday (localtime) morning the program stopped suddenly
> receiving packets .
> This the excerpt of the log:
> _
> Mar 15 06:35:30 kangoo weewx[2420]: reportengine: ftp'd 49 files in 6.67
> seconds
> Mar 15 06:40:21 kangoo weewx[2420]: manager: added record 2016-03-15
> 06:40:00 CET (1458020400) to database 'weewx.sdb'
> Mar 15 06:40:21 kangoo weewx[2420]: manager: added record 2016-03-15
> 06:40:00 CET (1458020400) to daily summary in 'weewx.sdb'
> Mar 15 06:40:23 kangoo weewx[2420]: te923: Failed attempt 1 of 5 to read
> data: Timeout after 0 bytes
> Mar 15 06:40:24 kangoo weewx[2420]: cheetahgenerator: Generated 14 files
> for report StandardReport in 2.15 seconds
> Mar 15 06:40:25 kangoo weewx[2420]: genimages: Generated 12 images for
> StandardReport in 1.11 seconds
> Mar 15 06:40:25 kangoo weewx[2420]: reportengine: copied 0 files to
> /home/weewx/public_html
> Mar 15 06:40:26 kangoo weewx[2420]: GaugeGenerator: windDir has no
> reading (None)
> Mar 15 06:40:26 kangoo weewx[2420]: GaugeGenerator: windRose has no
> reading (None)
> Mar 15 06:40:27 kangoo weewx[2420]: GaugeGenerator: Generated 7 images
> for HTMLPages in 1.68 seconds
> Mar 15 06:40:27 kangoo weewx[2420]: historygenerator.pyc: Generated 5
> tables in 0.12 seconds
> Mar 15 06:40:27 kangoo weewx[2420]: te923: Failed attempt 2 of 5 to read
> data: Timeout after 15 bytes
> Mar 15 06:40:29 kangoo weewx[2420]: cheetahgenerator: Generated 10 files
> for report HTMLPages in 1.62 seconds
> Mar 15 06:40:29 kangoo weewx[2420]: reportengine: copied 0 files to
> /home/weewx/public_html/Bootstrap
> Mar 15 06:40:29 kangoo weewx[2420]: genimages: Generated 6 images for
> SmallImages in 0.90 seconds
> Mar 15 06:40:31 kangoo weewx[2420]: te923: Failed attempt 3 of 5 to read
> data: Timeout after 14 bytes
> Mar 15 06:40:35 kangoo weewx[2420]: te923: Failed attempt 4 of 5 to read
> data: Timeout after 14 bytes
> Mar 15 06:40:36 kangoo weewx[2420]: reportengine: ftp'd 49 files in 6.65
> seconds
> Mar 15 06:40:40 kangoo weewx[2420]: te923: Failed attempt 5 of 5 to read
> data: Timeout after 14 bytes
> Mar 15 06:40:43 kangoo weewx[2420]: engine: Shutting down StdReport thread
> Mar 15 06:40:43 kangoo weewx[2420]: engine: Caught WeeWxIOError: Read
> failed after 5 tries
> Mar 15 06:40:43 kangoo weewx[2420]: Waiting 60 seconds then
> retrying...
> Mar 15 06:41:43 kangoo weewx[2420]: engine: retrying...
> Mar 15 06:41:43 kangoo weewx[2420]: engine: Using configuration file
> /home/weewx/weewx.conf
> Mar 15 06:41:43 kangoo weewx[2420]: engine: Loading station type TE923
> (weewx.drivers.te923)
> Mar 15 06:41:43 kangoo weewx[2420]: te923: driver version is 0.17
> Mar 15 06:41:43 kangoo weewx[2420]: te923: polling interval is 10
> Mar 15 06:41:43 kangoo weewx[2420]: te923: observation map is {'bat_1':
> 'outBatteryStatus', 'bat_3': 'extraBatteryStatus2', 'bat_2':
> 'extraBatteryStatus1', 'bat_5': 'extraBatteryStatus4', 'bat_4':
> 'extraBatteryStatus3', 'bat_wind': 'windBatteryStatus', 't_in':
> 'inTemp', 'link_rain': 'rainLinkStatus', 't_5': 'extraTemp4', 'h_in':
> 'inHumidity', 'h_4': 'extraHumid3', 'h_5': 'extraHumid4', 'h_2':
> 'extraHumid1', 'h_3': 'extraHumid3', 'h_1': 'outHumidity', 't_2':
> 'extraTemp1', 'link_2': 'extraLinkStatus1', 'link_uv': 'uvLinkStatus',
> 'link_wind': 'windLinkStatus', 'uv': 'UV', 'bat_uv': 'uvBatteryStatus',
> 'link_5': 'extraLinkStatus4', 'bat_rain': 'rainBatteryStatus', 'link_3':
> 'extraLinkStatus2', 't_3': 'extraTemp2', 'link_1': 'outLinkStatus',
> 't_1': 'outTemp', 't_4': 'extraTemp3', 'link_4': 'extraLinkStatus3'}
> Mar 15 06:41:43 kangoo weewx[2420]: te923: Found device on USB bus=001
> device=005
> Mar 15 06:41:43 kangoo weewx[2420]: te923: read: wrong number of bytes:
> 35 != 34
> Mar 15 06:41:43 kangoo weewx[2420]: te923: Failed attempt 1 of 5 to read
> data: Bad header byte: 03 != 5a
> Mar 15 06:41:47 kangoo weewx[2420]: te923: Failed attempt 2 of 5 to read
> data: Timeout after 7 bytes
> Mar 15 06:41:52 kangoo weewx[2420]: te923: Failed attempt 3 of 5 to read
> data: Timeout after 14 bytes
> Mar 15 06:41:56 kangoo weewx[2420]: te923: Failed attempt 4 of 5 to read
> data: Timeout after 14 bytes
> Mar 15 06:42:00 kangoo weewx[2420]: te923: Failed attempt 5 of 5 to read
> data: Timeout after 14 bytes
> Mar 15 06:42:03 kangoo weewx[2420]: engine: Unable to
Re: [weewx-user] Raspberry PI using WH1080WS with extra DHT22 sensor
The engine in weewx uses a pipeline architecture. The services are processed in order, with the results of one service given to the next in line. The data_services are fairly early in the pipe, but after the driver. So, if you substitute a new value of outHumidity in place of whatever was already in the loop packet, it will be treated as if it came off the driver. Your service will look something like this (NOT TESTED): class AddHumidity(StdService): """Service to add outHumidity""" def __init__(self, engine, config_dict): # Initialize my base class: super(AddHumidity, self).__init__(engine, config_dict) self.bind(weewx.NEW_LOOP_PACKET, self.new_loop_packet) def new_loop_packet(self, event): """Substitute value of outHumidity""" humidity = myFunctionToGetHumidity() event.packet['outHumidity'] = humidity Note that the function myFunctionToGetHumidity() is expected to supply the new humidity value. It is important that it not block too long because it is sitting in the main engine thread. Everything stops while the engine waits for the new humidity value. -tk On Thu, Sep 8, 2016 at 2:31 PM, Thomas Culver wrote: > I am successfully running weewx on a Raspberry Pi 3 using a Fine Onset > wh1080 weather station. I have noticed over time that the humidity reading > from the wh1080 is not accurate, therefore I installed a dht22 sensor and > connected it the Rasperry Pi via the gpio interface. I have modified a > service , "data_services = user.dht22.DHT22Service" to read and store the > data in the archive table at extraTemp1 and extraHumid1. Since the > humidify sensor is bad on my wh1080, i would like to write the humidify > data, from the dht22, to outHumidity. That way I will not need to customize > any reports to use the correct humidify column from the archive table. I > know how to write the outHumidify in my data_services routine, but i expect > it will be overwritten when weewx reads from the wh1080. I would expect > that I need to modify the fousb driver, can someone point me to the > correct code, or documentation, that would explain the change. I am not a > python programmer. An "Old IBM 360 Assembler programmer" appreciates the > help. Thanks. > > -- > 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. > -- 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-user] Raspberry PI using WH1080WS with extra DHT22 sensor
I am successfully running weewx on a Raspberry Pi 3 using a Fine Onset wh1080 weather station. I have noticed over time that the humidity reading from the wh1080 is not accurate, therefore I installed a dht22 sensor and connected it the Rasperry Pi via the gpio interface. I have modified a service , "data_services = user.dht22.DHT22Service" to read and store the data in the archive table at extraTemp1 and extraHumid1. Since the humidify sensor is bad on my wh1080, i would like to write the humidify data, from the dht22, to outHumidity. That way I will not need to customize any reports to use the correct humidify column from the archive table. I know how to write the outHumidify in my data_services routine, but i expect it will be overwritten when weewx reads from the wh1080. I would expect that I need to modify the fousb driver, can someone point me to the correct code, or documentation, that would explain the change. I am not a python programmer. An "Old IBM 360 Assembler programmer" appreciates the help. Thanks. -- 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-user] Re: Driver SDR
thanks for the reply, i'm testing on la-cross ws2350, have you a trace for this meteo station sensor? thanks a lot Matt ! M. Il giorno giovedì 8 settembre 2016 21:20:58 UTC+2, Marco Tibaldi ha scritto: > > > Good evening everyone, I'm ' trying to use the SDR driver of Matt Wall > changed today. the weewx web page updates to display the correct date and > time , but do not get any value in the conditions . > > this is an exctract of the log: > > Sep 8 21:07:00 SDR weewx[1034]: cheetahgenerator: Generated 14 files for > report StandardReport in 2.80 seconds Sep 8 21:07:04 SDR weewx[1034]: > genimages: Generated 24 images for StandardReport in 3.85 seconds Sep 8 > 21:07:04 SDR weewx[1034]: reportengine: copied 0 files to /var/www/weewx > Sep 8 21:09:06 SDR weewx[1034]: manager: unable to add record 2016-09-08 > 23:05:00 CEST (1473368700) to database 'weewx.sdb': UNIQUE constraint > failed: archive.dateTime Sep 8 21:09:06 SDR weewx[1034]: manager: unable to > add record 2016-09-08 23:05:00 CEST (1473368700) to database 'weewx.sdb': > UNIQUE constraint failed: archive.dateTime Sep 8 21:09:07 SDR weewx[1034]: > manager: unable to add record 2016-09-08 23:05:00 CEST (1473368700) to > database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime Sep 8 > 21:09:08 SDR weewx[1034]: cheetahgenerator: Generated 14 files for report > StandardReport in 2.56 seconds Sep 8 21:09:12 SDR weewx[1034]: genimages: > Generated 24 images for StandardReport in 3.88 seconds Sep 8 21:09:12 SDR > weewx[1034]: reportengine: copied 0 files to /var/www/weewx > > Any idea? > > > > > -- 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-user] Re: Driver SDR
On Thursday, September 8, 2016 at 3:20:58 PM UTC-4, Marco Tibaldi wrote: > > > Good evening everyone, I'm ' trying to use the SDR driver of Matt Wall > changed today. the weewx web page updates to display the correct date and > time , but do not get any value in the conditions . > you need to define a sensor map in the [SDR] stanza in weewx.conf (you should also do another pull). for example, if you want to capture data from a fine offset instrument cluster, do something like this: [SDR] driver = user.sdr [[sensor_map]] wind_gust.0026.FOWH1080Packet = windGust battery.0026.FOWH1080Packet = outBatteryStatus total_rain.0026.FOWH1080Packet = rain wind_speed.0026.FOWH1080Packet = windSpeed wind_dir.0026.FOWH1080Packet = windDir humidity.0026.FOWH1080Packet = outHumidity temperature.0026.FOWH1080Packet = outTemp if you have some acurite sensors, do something like this: [SDR] driver = user.sdr [[sensor_map]] wind_dir.0BFA.Acurite5n1Packet = windDir wind_speed.0BFA.Acurite5n1Packet = windSpeed temperature.0BFA.Acurite5n1Packet = outTemp humidity.0BFA.Acurite5n1Packet = outHumidity temperature.24A4.AcuriteTowerPacket = inTemp humidity.24A4.AcuriteTowerPacket = inHumidity the left-hand side is a tuple with observation_name.sensor_id.packet_type you can use * as wildcard for any part of the tuple. details and examples in the readme.txt to see what your sdr is reporting, first run the driver directly like this: PYTHONPATH=/home/weewx/bin python /home/weewx/bin/user/sdr.py or set debug=1 in weewx.conf and look at all of the raw output from all the sensors that your sdr can detect. 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 options, visit https://groups.google.com/d/optout.
[weewx-user] Driver SDR
Good evening everyone, I'm ' trying to use the SDR driver of Matt Wall changed today. the weewx web page updates to display the correct date and time , but do not get any value in the conditions . this is an exctract of the log: Sep 8 21:07:00 SDR weewx[1034]: cheetahgenerator: Generated 14 files for report StandardReport in 2.80 seconds Sep 8 21:07:04 SDR weewx[1034]: genimages: Generated 24 images for StandardReport in 3.85 seconds Sep 8 21:07:04 SDR weewx[1034]: reportengine: copied 0 files to /var/www/weewx Sep 8 21:09:06 SDR weewx[1034]: manager: unable to add record 2016-09-08 23:05:00 CEST (1473368700) to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime Sep 8 21:09:06 SDR weewx[1034]: manager: unable to add record 2016-09-08 23:05:00 CEST (1473368700) to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime Sep 8 21:09:07 SDR weewx[1034]: manager: unable to add record 2016-09-08 23:05:00 CEST (1473368700) to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime Sep 8 21:09:08 SDR weewx[1034]: cheetahgenerator: Generated 14 files for report StandardReport in 2.56 seconds Sep 8 21:09:12 SDR weewx[1034]: genimages: Generated 24 images for StandardReport in 3.88 seconds Sep 8 21:09:12 SDR weewx[1034]: reportengine: copied 0 files to /var/www/weewx Any idea? -- 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.
Re: [weewx-user] BASIC question regarding config file
Yep! That's it. THANKS! I installed it using the DEB package. Later I was warned away from it but I had already got it running so I never re-installed it via the setup.py On Thursday, September 8, 2016 at 10:40:35 AM UTC-4, Macha wrote: > > I think it depends on the way you installed it. With my Pi, it shows it > running as a python task. I always do .. > > ps aux | grep wee > > .. and it shows the command launching weewx, something like ... > > root 4193 13.9 5.4 78352 48232 ?Sl Sep06 398:00 python > ./bin/weewxd weewx.conf > > I use it in a Cron job to reboot the Pi on the odd occasion I get a USB > lockup and weewx bombs out. Weewx is launched from a @reboot script. > > > > > On Thursday, September 8, 2016 at 2:00:31 PM UTC+2, Jim W. wrote: >> >> This is what I get with the ps -a command. For some reason the weewx >> process does not show up? >> >> pi@WXraspberrypi:/ $ ps -a >> PID TTY TIME CMD >> 933 tty1 00:00:00 bash >> 3310 pts/200:00:00 ps >> 20632 pts/000:00:00 sudo >> 20636 pts/000:00:00 tail >> >> On Thursday, September 8, 2016 at 12:12:48 AM UTC-4, Andrew Milner wrote: >>> >>> Or you can force a .conf reload with a hup >>> " >>> >>> You can tell a running instance of weewx to reread its configuration >>> file by sending it the HUP signal. First run ps to find out the Process >>> ID (PID) number of the instance, then send it the HUP signal: >>> >>> ps -a # Note the PID of the weewxd processkill -HUP *pid* # Send >>> it a HUP signal >>> >>> Note that this *only* rereads the configuration file. It will not >>> reload any code. >>> " >>> >>> >>> On Thursday, 8 September 2016 06:16:25 UTC+3, Dave Webb wrote: >>> You need to stop and restart weewx for it to pick up the changes in weewx.conf Dave-KB1PVH Sent from my Galaxy S7 On Sep 7, 2016 11:15 PM, "Jim W." wrote: > Does the config file get read once during start up or is it poled > continuously? If I make a change in the config file do I have to stop and > start weewx? > Thanks! > > -- > 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+...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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.
Re: [weewx-user] BASIC question regarding config file
I think it depends on the way you installed it. With my Pi, it shows it running as a python task. I always do .. ps aux | grep wee .. and it shows the command launching weewx, something like ... root 4193 13.9 5.4 78352 48232 ?Sl Sep06 398:00 python ./bin/weewxd weewx.conf I use it in a Cron job to reboot the Pi on the odd occasion I get a USB lockup and weewx bombs out. Weewx is launched from a @reboot script. On Thursday, September 8, 2016 at 2:00:31 PM UTC+2, Jim W. wrote: > > This is what I get with the ps -a command. For some reason the weewx > process does not show up? > > pi@WXraspberrypi:/ $ ps -a > PID TTY TIME CMD > 933 tty1 00:00:00 bash > 3310 pts/200:00:00 ps > 20632 pts/000:00:00 sudo > 20636 pts/000:00:00 tail > > On Thursday, September 8, 2016 at 12:12:48 AM UTC-4, Andrew Milner wrote: >> >> Or you can force a .conf reload with a hup >> " >> >> You can tell a running instance of weewx to reread its configuration >> file by sending it the HUP signal. First run ps to find out the Process >> ID (PID) number of the instance, then send it the HUP signal: >> >> ps -a # Note the PID of the weewxd processkill -HUP *pid* # Send >> it a HUP signal >> >> Note that this *only* rereads the configuration file. It will not reload >> any code. >> " >> >> >> On Thursday, 8 September 2016 06:16:25 UTC+3, Dave Webb wrote: >> >>> You need to stop and restart weewx for it to pick up the changes in >>> weewx.conf >>> >>> Dave-KB1PVH >>> >>> Sent from my Galaxy S7 >>> >>> On Sep 7, 2016 11:15 PM, "Jim W." wrote: >>> Does the config file get read once during start up or is it poled continuously? If I make a change in the config file do I have to stop and start weewx? Thanks! -- 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+...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. >>> -- 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.
Re: [weewx-user] BASIC question regarding config file
This is what I get with the ps -a command. For some reason the weewx process does not show up? pi@WXraspberrypi:/ $ ps -a PID TTY TIME CMD 933 tty1 00:00:00 bash 3310 pts/200:00:00 ps 20632 pts/000:00:00 sudo 20636 pts/000:00:00 tail On Thursday, September 8, 2016 at 12:12:48 AM UTC-4, Andrew Milner wrote: > > Or you can force a .conf reload with a hup > " > > You can tell a running instance of weewx to reread its configuration file > by sending it the HUP signal. First run ps to find out the Process ID > (PID) number of the instance, then send it the HUP signal: > > ps -a # Note the PID of the weewxd processkill -HUP *pid* # Send it > a HUP signal > > Note that this *only* rereads the configuration file. It will not reload > any code. > " > > > On Thursday, 8 September 2016 06:16:25 UTC+3, Dave Webb wrote: > >> You need to stop and restart weewx for it to pick up the changes in >> weewx.conf >> >> Dave-KB1PVH >> >> Sent from my Galaxy S7 >> >> On Sep 7, 2016 11:15 PM, "Jim W." wrote: >> >>> Does the config file get read once during start up or is it poled >>> continuously? If I make a change in the config file do I have to stop and >>> start weewx? >>> Thanks! >>> >>> -- >>> 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+...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- 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.
Re: [weewx-user] BASIC question regarding config file
THANK YOU! On Wednesday, September 7, 2016 at 11:16:25 PM UTC-4, Dave Webb wrote: > > You need to stop and restart weewx for it to pick up the changes in > weewx.conf > > Dave-KB1PVH > > Sent from my Galaxy S7 > > On Sep 7, 2016 11:15 PM, "Jim W." > > wrote: > >> Does the config file get read once during start up or is it poled >> continuously? If I make a change in the config file do I have to stop and >> start weewx? >> Thanks! >> >> -- >> 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+...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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-user] Re: 404 Not Found
I made following changes: /etc/weewx/weewx.conf HTML_ROOT = /var/www/html/weewx /etc/weewx/apache/conf.d/weewx.conf Alias /weewx /var/www/html/weewx Options FollowSymlinks AllowOverride None # for apache 2.2 Order allow,deny Allow from all # for apache 2.4 # Require all granted then restarted weewx and apache ... Bingo ... it works Thanks for your professional support ... -- 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-user] Re: Regenerate reports after making changes in the weewx.sdb database.
Thanks Gary. Greetings Guus. -- 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-user] Re: Regenerate reports after making changes in the weewx.sdb database.
Hi, The yearly reports come from the daily summaries, so you will need to drop them and then rebuild them. Refer to Dropping and rebuilding the daily summaries in the Customization Guide. Once you have done this delete the offending reports and they will be regenerated on the next report cycle. Gary On Thursday, 8 September 2016 18:31:12 UTC+10, Guus Rameckers wrote: > > I'm using weewx on a RasPI hooked up to a WMR200. > Everything work's fine. > > Recently I had to make some adjustments to the rain gauge. > After making these adjustments the database (weewx.sdb) was partly filled > with incorrect (rain)data. > I changed the wrong data in the database. > > However in the (yearly) report the wrong data is presented. > This is not the case with the graphics. > > Is there a way to regenerate the reports after making changes in the > database? > > Greetings Guus. > -- 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-user] Regenerate reports after making changes in the weewx.sdb database.
I'm using weewx on a RasPI hooked up to a WMR200. Everything work's fine. Recently I had to make some adjustments to the rain gauge. After making these adjustments the database (weewx.sdb) was partly filled with incorrect (rain)data. I changed the wrong data in the database. However in the (yearly) report the wrong data is presented. This is not the case with the graphics. Is there a way to regenerate the reports after making changes in the database? Greetings Guus. -- 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.
Re: [weewx-user] Re: 404 Not Found
as said, forget about the database etc, that's likely already been configured for you during the install. Personally I have always got on better with lighttpd than apache. But that's your decision, In weewx.conf there should be the config relating to where it's saving the web html files. Once you know this, have a look and see if there where it says. You then need to config apache to serve that folder. Must be a ton of info on the net on how to config apache, use google. Obviously apache (or lighttpd) is a completely separate program from weewx, And weewx is unaware of the web server (apache or whatever) and does not care about it. Chris -- 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.
