[weewx-user] Re: sdr.py

[Brad Tucker]

Fantastic. Thanks!
Brad

On Sunday, October 30, 2016 at 8:56:04 AM UTC-7, Brad Tucker wrote:
>
> Trying to install weewx. I have installed rtlsdr rtl433 along with weewx.
>
> I have tested rtf-433 by issuing rtl-433 -G and get lots of data passed 
> back.
>
> Once I try and use the actual sdr.py driver directly using the command:
> sudo PYTHONPATH=bin python bin/user/sdr.py
>
> I get this:
> Traceback (most recent call last):
>   File "bin/user/sdr.py", line 699, in 
> [--path=PATH] [--ld_library_path=LD_LIBRARY_PATH]""" % DEFAULT_CMD
> ValueError: unsupported format character 'p' (0x70) at index 1
>
> Not quite sure where to go from here. Seems maybe I need to call a path 
> out to the driver.
>
> I have tried things like this:
> export PATH=/usr/local/bin:${PATH}
>
> export LD_LIBRARY_PATH=/usr/local/lib
>
>
> from the shell and then issuing the command. Im a bit of a newbie here so any 
> help would be greatly appreciated.
>
>
> Thanks,
>
> Brad
>
>

-- 
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: sdr.py

[mwall]

On Sunday, October 30, 2016 at 11:56:04 AM UTC-4, Brad Tucker wrote:
>
> Once I try and use the actual sdr.py driver directly using the command:
> sudo PYTHONPATH=bin python bin/user/sdr.py
>
> I get this:
> Traceback (most recent call last):
>   File "bin/user/sdr.py", line 699, in 
> [--path=PATH] [--ld_library_path=LD_LIBRARY_PATH]""" % DEFAULT_CMD
> ValueError: unsupported format character 'p' (0x70) at index 1
>
> Not quite sure where to go from here. Seems maybe I need to call a path 
> out to the driver.
>

sorry about that.  fixed at cc7984d.  please pull then try again.

 

> I have tried things like this:
> export PATH=/usr/local/bin:${PATH}
>
> export LD_LIBRARY_PATH=/usr/local/lib
>
>
> from the shell and then issuing the command. Im a bit of a newbie here so any 
> help would be greatly appreciated.
>
>
you can either configure the environment before running python/weewx:

export LD_LIBRARY_PATH=/usr/local/lib
export PATH=/usr/local/bin:${PATH}
PYTHONPATH=bin python bin/user/sdr.py

or you can specify PATH and LD_LIBRARY_PATH as options to the sdr driver 
and it will pre-load the environment with those variables before it invokes 
the rtl_433 command.  for example:

[SDR]
path = /usr/loca/bin
ld_library_path = /usr/local/lib
cmd = rtl_433 -G

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: Interceptor using bridge new Accurate firmware

[Radar]

it puts it on one line
i had to download version 1.4.4 its not yet in fedora rpm so had to compile 
from source
i'm looking for the script i used when i was playing with interceptor 
driver can't remember it's name or where i left it :)

On Sunday, October 30, 2016 at 10:59:23 PM UTC-5, Brad Tucker wrote:
>
> If only it was that easy. I'm not a coder and I haven't touched perl in a 
> good 20years... on your tcpflow you have -0 in the syntax. My version on 
> the pi doesn't understand -0. What should the -0 do?
>
> Thanks,
> B
>

-- 
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: Interceptor using bridge new Accurate firmware

[Brad Tucker]

If only it was that easy. I'm not a coder and I haven't touched perl in a good 
20years... on your tcpflow you have -0 in the syntax. My version on the pi 
doesn't understand -0. What should the -0 do?

Thanks,
B

-- 
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: Interceptor Driver Acurite Bridge

[Brad Tucker]

Any luck with this? I'm having a similar issue. I too am having the nc issue.

Thanks,
Brad

-- 
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: Interceptor using bridge new Accurate firmware

[Radar]

the perl script is not part of weewx i made it long time ago
i don't have it for download (it's real messy) it does a little more than 
just feed weewx it prints to the console too
you should be able to write one to suit you
don't know about nc

On Sunday, October 30, 2016 at 10:31:53 PM UTC-5, Brad Tucker wrote:
>
> Thanks for the reply Radar. Is your perlscript available for download or 
> is it currently part of the weewx pacakage and I'm missing it?
>
> I'll give tcpflow a shot as well.
>
> Any idea why nc only stays alive for a short period?
>
> Thanks!
> Brad
>
>

-- 
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: Interceptor using bridge new Accurate firmware

[Brad Tucker]

Thanks for the reply Radar. Is your perlscript available for download or is it 
currently part of the weewx pacakage and I'm missing it?

I'll give tcpflow a shot as well.

Any idea why nc only stays alive for a short period?

Thanks!
Brad

-- 
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: Interceptor using bridge new Accurate firmware

[Radar]

i use a perl script to put the obs on one line then feed it to weewx

if you have tcpflow 1.4.4 you can try
tcpflow -C -p -0 -i eth0


On Sunday, October 30, 2016 at 10:01:59 PM UTC-5, Brad Tucker wrote:
>
> I have setup a bridge running raspberry pi. It is connected as follows:
>
> Acurite Bridge -> RaspberyPi WeeWX Bridge -> Internet Connection
>
> It is passing packets through the bridge. The bridge has been updating 
> myaccurite & weather underground for hours and all is well with it.
>
> I am having problems passing the sniffed data to the weewx driver. I have 
> picked together what I think is a decent script but its not parsing 
> properly.
> sudo tcpdump -A -n -p -l -i eth0 -s0 -w - tcp dst port 80 | stdbuf -oL 
> strings -n8
>
> output:
> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
> 262144 bytes
> GET 
> /weatherstation/updateweatherstation?dateutc=now=updateraw=1R
> =24C86E06B15C=tower=00012694R
> =65=72.8R
> =29.35=normal=3R
>  HTTP/1.1
> hubapi.myacurite.com
> User-Agent: Hub/224R
> Connection: close
> GET 
> /weatherstation/updateweatherstation?dateutc=now=updateraw=1]
> =24C86E06B15C=5N1x31=2179]
> =0=270]
> =0.00=0.20=96=57.2=56]
> =29.35=normal=3]
>  HTTP/1.1
> hubapi.myacurite.com
> User-Agent: Hub/224]
> Connection: closeGET 
> /weatherstation/updateweatherstation.php?ID=KCATHOUS110=password=now=updateraw=1^
> =36^
> =24C86E06B15C=5N1x31=2179^
> =0=270^
> =0.00=0.20=96=57.2=56^
> =29.35=normal=3^
>  HTTP/1.1
> rtupdate.wunderground.com^
> Connection: close
> GET 
> /weatherstation/updateweatherstation?dateutc=now=updateraw=1b
> =24C86E06B15C=tower=8384b
> =48=81.4b
> =29.35=normal=3b
>  HTTP/1.1
> hubapi.myacurite.com
> User-Agent: Hub/224b
> Connection: close
> GET 
> /weatherstation/updateweatherstation?dateutc=now=updateraw=1c
> =24C86E06B15C=tower=00012694c
> =65=72.8c
> =29.35=normal=3c
>  HTTP/1.1
> hubapi.myacurite.com
> User-Agent: Hub/224c
> Connection: close
> GET 
> /weatherstation/updateweatherstation?dateutc=now=updateraw=1{
> =24C86E06B15C=5N1x38=2179{
> =0=96{
> =56.9{
> =29.35=normal=3{
>  HTTP/1.1
> hubapi.myacurite.com{
> User-Agent: Hub/224{
> Connection: close
>
> when I run the following through netcat like this:
> sudo tcpdump -A -n -p -l -i eth0 -s0 -w - tcp dst port 80 | stdbuf -oL 
> strings -n8 | nc 192.168.1.22 8080
> the process only stays alive for seconds and I get this:
> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
> 262144 bytes
> 19 packets captured
> 19 packets received by filter
> 0 packets dropped by kernel
>
> and syslog reports this:
> Oct 30 19:58:57 weather weewx[781]: interceptor: MainThread: empty queue
> Oct 30 19:59:07 weather weewx[781]: interceptor: MainThread: empty queue
> Oct 30 19:59:17 weather weewx[781]: interceptor: MainThread: empty queue
> Oct 30 19:59:27 weather weewx[781]: interceptor: MainThread: empty queue
> Oct 30 19:59:37 weather weewx[781]: interceptor: MainThread: empty queue
>
> After spending the better part of a day with this Im out of ideas.
>
> Please Help!
> Brad
>
>

-- 
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] Steel Series gauges - cant alter chart popup size

[erbenton07]

I am using the SteelSeries gauges in weewx 3.4.0 (I know, I need to upgrade 
weewx and i will shortly)
In weewx/skins/ss/skin.conf I changed the image height and width and 
restarted weewx but don't see any chart popup size changes. Altering the 
colors of x and y axis labels works ok but the image size is ignored.
[ImageGenerator]
image_width = 1080
image_height = 294
#image_width = 720
#image_height = 196
What I am doing wrong?
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] Interceptor using bridge new Accurate firmware

[Brad Tucker]

I have setup a bridge running raspberry pi. It is connected as follows:

Acurite Bridge -> RaspberyPi WeeWX Bridge -> Internet Connection

It is passing packets through the bridge. The bridge has been updating 
myaccurite & weather underground for hours and all is well with it.

I am having problems passing the sniffed data to the weewx driver. I have 
picked together what I think is a decent script but its not parsing 
properly.
sudo tcpdump -A -n -p -l -i eth0 -s0 -w - tcp dst port 80 | stdbuf -oL 
strings -n8

output:
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
262144 bytes
GET 
/weatherstation/updateweatherstation?dateutc=now=updateraw=1R
=24C86E06B15C=tower=00012694R
=65=72.8R
=29.35=normal=3R
 HTTP/1.1
hubapi.myacurite.com
User-Agent: Hub/224R
Connection: close
GET 
/weatherstation/updateweatherstation?dateutc=now=updateraw=1]
=24C86E06B15C=5N1x31=2179]
=0=270]
=0.00=0.20=96=57.2=56]
=29.35=normal=3]
 HTTP/1.1
hubapi.myacurite.com
User-Agent: Hub/224]
Connection: closeGET 
/weatherstation/updateweatherstation.php?ID=KCATHOUS110=password=now=updateraw=1^
=36^
=24C86E06B15C=5N1x31=2179^
=0=270^
=0.00=0.20=96=57.2=56^
=29.35=normal=3^
 HTTP/1.1
rtupdate.wunderground.com^
Connection: close
GET 
/weatherstation/updateweatherstation?dateutc=now=updateraw=1b
=24C86E06B15C=tower=8384b
=48=81.4b
=29.35=normal=3b
 HTTP/1.1
hubapi.myacurite.com
User-Agent: Hub/224b
Connection: close
GET 
/weatherstation/updateweatherstation?dateutc=now=updateraw=1c
=24C86E06B15C=tower=00012694c
=65=72.8c
=29.35=normal=3c
 HTTP/1.1
hubapi.myacurite.com
User-Agent: Hub/224c
Connection: close
GET 
/weatherstation/updateweatherstation?dateutc=now=updateraw=1{
=24C86E06B15C=5N1x38=2179{
=0=96{
=56.9{
=29.35=normal=3{
 HTTP/1.1
hubapi.myacurite.com{
User-Agent: Hub/224{
Connection: close

when I run the following through netcat like this:
sudo tcpdump -A -n -p -l -i eth0 -s0 -w - tcp dst port 80 | stdbuf -oL 
strings -n8 | nc 192.168.1.22 8080
the process only stays alive for seconds and I get this:
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
262144 bytes
19 packets captured
19 packets received by filter
0 packets dropped by kernel

and syslog reports this:
Oct 30 19:58:57 weather weewx[781]: interceptor: MainThread: empty queue
Oct 30 19:59:07 weather weewx[781]: interceptor: MainThread: empty queue
Oct 30 19:59:17 weather weewx[781]: interceptor: MainThread: empty queue
Oct 30 19:59:27 weather weewx[781]: interceptor: MainThread: empty queue
Oct 30 19:59:37 weather weewx[781]: interceptor: MainThread: empty queue

After spending the better part of a day with this Im out of ideas.

Please Help!
Brad

-- 
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] Noob question... where to find the actual data (temp) within weewx?

[Thomas Keffer]

Jim,

Did you check the Customizing Guide ?
It has an abundance of information about how to access the data. As Andrew
suggests, the easiest is to specify that the report generator create
another (tiny) file, with just a single tag $current.outTemp. On every
reporting cycle the tag will be replaced with the current temperature.

-tk

On Sat, Oct 29, 2016 at 1:50 PM, Jim W.  wrote:

> I have very little Linux (or other programming) experience...  Decades ago
> I did a little Visual Basic programming but that is a dim memory. I have
> managed (with the generous help of this forum) to setup and run weewx on a
> Rpi3b. WS2080 WU and Motion sending images to WU.
>
> My next project is to add overlays of temperature and wind speed and
> direction to the images I'm sending to WU. Most of it I have figured out
> but what I don't know is where to find the actual data (temp) within 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+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.

Re: [weewx-user] Re: Davis Vantage Pro2 and WU - best settings

[Thomas Keffer]

Hello, Jacek,

You said you have soil temperature and humidity sensors, but it appears
that you actually have soil and *leaf temperature* sensors. That is, you
have values for soilTemp1 and leafTemp1, but nothing for soilMoist1.

Or, perhaps the sensors are plugged into the wrong probe slot? You should
check.

The WeatherUnderground PWS protocol
 does not
recognize leaf temperature, so that would explainwhy you are not seeing
anything.

-tk

On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński  wrote:

> some logs
> REC:2016-10-30 17:30:00 CET (1477845000) altimeter: 30.2914897657,
> appTemp: 42.5550178172, barometer: 30.332, cloudbase: 2354.14897393,
> consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint: 38.9625445147,
> ET: 0.0, extraHumid1: None, extraHumid2: None, extraTemp1: None,
> extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 46.1,
> highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1,
> inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5,
> leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None,
> lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1,
> pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0,
> rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3:
> None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: None,
> soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.1,
> windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58,
> windSpeed: 2.0
> LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter: 30.2924734796,
> appTemp: 42.4369596271, barometer: 30.333, cloudbase: 2353.42091128,
> consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 0.0, dayRain: 0.0,
> dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0,
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0,
> extraAlarm8: 0, extraHumid1: None, extraHumid2: None, extraHumid3: None,
> extraHumid4: None, extraHumid5: None, extraHumid6: None, extraHumid7: None,
> extraTemp1: None, extraTemp2: None, extraTemp3: None, extraTemp4: None,
> extraTemp5: None, extraTemp6: None, extraTemp7: None, forecastIcon: 8,
> forecastRule: 1, heatindex: 46.0, humidex: 46.0, inDewpoint: 54.6182787763,
> inHumidity: 49.0, insideAlarm: 0, inTemp: 75.1, leafTemp1: 45.0, leafTemp2:
> None, leafTemp3: None, leafTemp4: None, leafWet1: None, leafWet2: None,
> leafWet3: None, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain:
> 2.960629922, outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0,
> outTemp: 46.0, pressure: 29.5100730398, radiation: None, rain: 0.0,
> rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0,
> soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: None, soilMoist2: None,
> soilMoist3: None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None,
> soilTemp3: None, soilTemp4: None, stormRain: 0.0, stormStart: None,
> sunrise: 1477802580, sunset: 1477837860, txBatteryStatus: 0, usUnits: 1,
> UV: None, windchill: 46.0, windDir: 32.0, windGust: 2.0, windGustDir: 32.0,
> windSpeed: 2.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 12.3
>
> so both loop and rec have soilTemp1 value of 45.0.
>
> and here other log
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting up weewx
> version 3.5.0
> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
> console successful
> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Clock error is 2.61
> seconds (positive is fast)
> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Getting archive packets
> since 2016-10-30 17:30:00 CET (1477845000)
> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
> console successful
> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Retrieving 0 page(s);
> starting index= 0
> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting main packet
> loop.
> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
> console successful
> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Requesting 200 LOOP
> packets.
> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
> console successful
> Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: Getting archive packets
> since 2016-10-30 17:30:00 CET (1477845000)
> Oct 30 17:35:15 raspberrypi rsyslogd-2007: action 'action 17' suspended,
> next retry is Sun Oct 30 17:36:45 2016 [try http://www.rsyslog.com/e/2007
> ]
> Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: gentle wake up of
> console successful
> Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: Retrieving 1 page(s);
> starting index= 3
> Oct 30 17:35:16 raspberrypi weewx[10216]: manager: added record 2016-10-30
> 17:35:00 CET (1477845300) to database 'weewx.sdb'
> Oct 30 17:35:16 raspberrypi weewx[10216]: manager: added record 2016-10-30
> 17:35:00 CET 

[weewx-user] Adding/Removing Values to MQTT extension

[jmltech]

I'm using Matthew Wall's nice MQTT extension for weewx.  Where can I 
specify which weewx variables to add to the MQTT stream, and remove some 
others that are not needed for my purpose?  I thought it would be a skin, 
but didn't find anything.
Thanks
Joe

-- 
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: Noob question... where to find the actual data (temp) within weewx?

[Andrew Milner]

1) If you have another program wanting the temperature you can read it from 
the archive table in the database 
or
2) Create a template called temp.txt.tmpl containing $current.outTemp - 
and have cheetah create a file called temp.txt every archive interval which 
you can then read into your other program.
or
3) Create a service, bound to loop records, to extract the outTemp from the 
loop record and create a text file every loop record


On Sunday, 30 October 2016 23:29:29 UTC+2, Jim W. wrote:

> Ok... Maybe if I ask the question in a more clear form... Can someone 
> explain how I can pass the current outdoor temp to a variable so I can us 
> it in another program?
>
>
>
>
> On Saturday, October 29, 2016 at 4:50:59 PM UTC-4, Jim W. wrote:
>>
>> I have very little Linux (or other programming) experience...  Decades 
>> ago I did a little Visual Basic programming but that is a dim memory. I 
>> have managed (with the generous help of this forum) to setup and run weewx 
>> on a Rpi3b. WS2080 WU and Motion sending images to WU.
>>
>> My next project is to add overlays of temperature and wind speed and 
>> direction to the images I'm sending to WU. Most of it I have figured out 
>> but what I don't know is where to find the actual data (temp) within 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Noob question... where to find the actual data (temp) within weewx?

[Jim W.]

Ok... Maybe if I ask the question in a more clear form... Can someone 
explain how I can pass the current outdoor temp to a variable so I can us 
it in another program?




On Saturday, October 29, 2016 at 4:50:59 PM UTC-4, Jim W. wrote:
>
> I have very little Linux (or other programming) experience...  Decades ago 
> I did a little Visual Basic programming but that is a dim memory. I have 
> managed (with the generous help of this forum) to setup and run weewx on a 
> Rpi3b. WS2080 WU and Motion sending images to WU.
>
> My next project is to add overlays of temperature and wind speed and 
> direction to the images I'm sending to WU. Most of it I have figured out 
> but what I don't know is where to find the actual data (temp) within 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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Attempting to use a Pete Bros. Ultimeter2100 on a RPi3 with a serial to usb converter

[Ralph Underwood]

I'll second that, great support from users and developers!  

This is the third weewx station I have cobbled together - one with a 
wireless Oregon Scientific, one with one-wire, and now this one with Pete 
Bros. - Plus two more carefully monitoring my basement as I test and 
experiment. The Rpi price makes all of this possible, just skip a couple of 
Starbucks visits and you can buy a computer.  I now know just enough Linux 
to get things going and it is fun learning.

The wireless station looses connectivity too often. That station is located 
near I-90 and I suspect that there is some powerful interference from the 
truckers radios as well as some nearby state radios. Just a suspicion, 
everything worked fine when it was twenty feet away in my workshop, but in 
the field not so much. So I wanted a wired system for my new system to be 
installed at my vacation home. With the demise of Hobby Boards; I was 
looking for an alternative to one-wire. I still plan on adding some 
one-wire sensors to this installation as I have a bundle of temperature 
probes.

Thanks again to all of the supportive users.

On Saturday, October 29, 2016 at 2:13:06 PM UTC-7, Steve2Q wrote:
>
> Ralph..good to see another Peet Bros user (not many of us here). I am not 
> a programmer, but have learned some very basic Linux to tweak my install. 
> One of the things I like about Weewx is all of the support. Tom, mwall, and 
> many others always help out,and have developed drivers for stations that 
> are not very common like ours. Mine is also a 2100.
> Welcome to Weewx. 
> Steve   N2QLQ 
>

-- 
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] How to use humidex, apparent temperature, evapotranspiration, cloud base and maximum solar radiation?

[herve FRELAT]

Thank you very very  much
All seems ok now.

H.frelat

-- 
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: Davis Vantage Pro2 and WU - best settings

[Jacek Skowroński]

some logs
REC:2016-10-30 17:30:00 CET (1477845000) altimeter: 30.2914897657, 
appTemp: 42.5550178172, barometer: 30.332, cloudbase: 2354.14897393, 
consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint: 38.9625445147, 
ET: 0.0, extraHumid1: None, extraHumid2: None, extraTemp1: None, 
extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 46.1, 
highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1, 
inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5, 
leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None, 
lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1, 
pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0, 
rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3: 
None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: None, 
soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.1, 
windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58, 
windSpeed: 2.0
LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter: 30.2924734796, 
appTemp: 42.4369596271, barometer: 30.333, cloudbase: 2353.42091128, 
consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 0.0, dayRain: 0.0, 
dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
extraAlarm8: 0, extraHumid1: None, extraHumid2: None, extraHumid3: None, 
extraHumid4: None, extraHumid5: None, extraHumid6: None, extraHumid7: None, 
extraTemp1: None, extraTemp2: None, extraTemp3: None, extraTemp4: None, 
extraTemp5: None, extraTemp6: None, extraTemp7: None, forecastIcon: 8, 
forecastRule: 1, heatindex: 46.0, humidex: 46.0, inDewpoint: 54.6182787763, 
inHumidity: 49.0, insideAlarm: 0, inTemp: 75.1, leafTemp1: 45.0, leafTemp2: 
None, leafTemp3: None, leafTemp4: None, leafWet1: None, leafWet2: None, 
leafWet3: None, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 
2.960629922, outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0, 
outTemp: 46.0, pressure: 29.5100730398, radiation: None, rain: 0.0, 
rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: None, soilMoist2: None, 
soilMoist3: None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, 
soilTemp3: None, soilTemp4: None, stormRain: 0.0, stormStart: None, 
sunrise: 1477802580, sunset: 1477837860, txBatteryStatus: 0, usUnits: 1, 
UV: None, windchill: 46.0, windDir: 32.0, windGust: 2.0, windGustDir: 32.0, 
windSpeed: 2.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 12.3

so both loop and rec have soilTemp1 value of 45.0.

and here other log
pi@raspberrypi:~ $ tail -f /var/log/syslog
Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting up weewx version 
3.5.0
Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
console successful
Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Clock error is 2.61 
seconds (positive is fast)
Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Getting archive packets 
since 2016-10-30 17:30:00 CET (1477845000)
Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
console successful
Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Retrieving 0 page(s); 
starting index= 0
Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting main packet loop.
Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
console successful
Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Requesting 200 LOOP 
packets.
Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
console successful
Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: Getting archive packets 
since 2016-10-30 17:30:00 CET (1477845000)
Oct 30 17:35:15 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Sun Oct 30 17:36:45 2016 [try http://www.rsyslog.com/e/2007 ]
Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: gentle wake up of 
console successful
Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: Retrieving 1 page(s); 
starting index= 3
Oct 30 17:35:16 raspberrypi weewx[10216]: manager: added record 2016-10-30 
17:35:00 CET (1477845300) to database 'weewx.sdb'
Oct 30 17:35:16 raspberrypi weewx[10216]: manager: added record 2016-10-30 
17:35:00 CET (1477845300) to daily summary in 'weewx.sdb'
Oct 30 17:35:16 raspberrypi weewx[10216]: vantage: DMPAFT complete: page 
timestamp 2016-10-21 21:10:00 CEST (1477077000) less than final timestamp 
2016-10-30 17:35:00 CET (1477845300)
Oct 30 17:35:16 raspberrypi weewx[10216]: vantage: Catch up complete.
Oct 30 17:35:16 raspberrypi weewx[10216]: reportengine: Running reports for 
latest time in the database.
Oct 30 17:35:16 raspberrypi weewx[10216]: vantage: Requesting 200 LOOP 
packets.
Oct 30 17:35:16 raspberrypi weewx[10216]: reportengine: Running report 
StandardReport
Oct 30 17:35:16 raspberrypi weewx[10216]: reportengine: Found configuration 
file 

[weewx-user] sdr.py

[Brad Tucker]

Trying to install weewx. I have installed rtlsdr rtl433 along with weewx.

I have tested rtf-433 by issuing rtl-433 -G and get lots of data passed 
back.

Once I try and use the actual sdr.py driver directly using the command:
sudo PYTHONPATH=bin python bin/user/sdr.py

I get this:
Traceback (most recent call last):
  File "bin/user/sdr.py", line 699, in 
[--path=PATH] [--ld_library_path=LD_LIBRARY_PATH]""" % DEFAULT_CMD
ValueError: unsupported format character 'p' (0x70) at index 1

Not quite sure where to go from here. Seems maybe I need to call a path out 
to the driver.

I have tried things like this:
export PATH=/usr/local/bin:${PATH}

export LD_LIBRARY_PATH=/usr/local/lib


from the shell and then issuing the command. Im a bit of a newbie here so any 
help would be greatly appreciated.


Thanks,

Brad

-- 
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: Davis Vantage Pro2 and WU - best settings

[Thomas Keffer]

It would not surprise me that the WU is not archiving soil temperature and
moisture. They are not very common and I doubt they would want to dedicate
columns in their database schema to them.

I have an extra temperature sensor ('extraTemp1'), which the WU reports as
"soil moisture." I don't know why. It also does not show up in the archive.

-tk

On Sun, Oct 30, 2016 at 1:02 AM, Jacek Skowroński  wrote:

> I had changed the probe slot for 1, and now I have
> soilTemp1: 46.0,
>
> but on the WU page something is strange. I get C close to the soil temp,
> but there is no value.
> https://www.wunderground.com/personal-weather-station/
> dashboard?ID=IWOJEWDZ56#history
>
> On Saturday, October 29, 2016 at 9:49:27 PM UTC+2, Jacek Skowroński wrote:
>
>> Hi,
>> I have Davis Vatange pro2 with external leaf_soil module located on ID=2.
>> So according to help I did such an command
>>
>> wee_device --set-transmitter-type=2,8,1,1
>>
>>
>> So if I understood it correctly I would have temperature and humidity of
>> soil on the external temp1 and external hum1.
>> How to get those data to WU?
>>
>> Just now on my station we do not see temp and humidity of the soil.
>> https://www.wunderground.com/personal-weather-station/dashbo
>> ard?ID=IWOJEWDZ56
>>
>> Next topic is best timings for sending data, is it possible to get data
>> in RealTime?
>> In general Davis has archival for 5min (300sec) so it sends data every
>> 5minute.
>> I had tried rapid fire, but it sends data every 2.5 sec but data changes
>> every 5minute so it's a little bit crazy.
>>
>> Is there anybody using Davis Vantage pro2 and WU and could share your
>> config?
>>
>> Thanks in advance
>> BR
>> Jacek
>>
> --
> 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] Re: Please can I have my bug back?

[mwall]

On Sunday, October 30, 2016 at 4:47:57 AM UTC-4, Macha wrote:
>
> In fact, the original "lockouts" weren't coincident with weewx's reporting 
> and seemed pretty random (and infrequent). I still suspect that the whole 
> issue had something to do with the fact that this "original" machine stores 
> "/" on my NFS and consequently Ethernet traffic is high.
>

all evidence (from 5+ years of dealing with these stations) points to a 
hardware problem with the fine offset hardware and/or firmware design, not 
a software problem on the computer.

the usb comm failures you were experiencing are not due to the cpu load of 
the pi or weewx's ability to process - they are due to the 
voltage/current/power on the usb.

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: Davis Vantage Pro2 and WU - best settings

[Andrew Milner]

Tom expressed doubts as to whether WU displayed soil temps on rapid fire - 
and you appear to be using rapid fire.  Have you tried uploading normal 
archive records instead of rapid firing??

Did you run with debug set, as Tom suggested, and confirm that the REC and 
LOOP contain the soil temperature??


On Sunday, 30 October 2016 10:02:55 UTC+2, Jacek Skowroński wrote:

> I had changed the probe slot for 1, and now I have
> soilTemp1: 46.0,
>
> but on the WU page something is strange. I get C close to the soil temp, 
> but there is no value.
>
> https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56#history
>
> On Saturday, October 29, 2016 at 9:49:27 PM UTC+2, Jacek Skowroński wrote:
>>
>> Hi,
>> I have Davis Vatange pro2 with external leaf_soil module located on ID=2.
>> So according to help I did such an command
>>
>> wee_device --set-transmitter-type=2,8,1,1
>>
>>
>> So if I understood it correctly I would have temperature and humidity of 
>> soil on the external temp1 and external hum1.
>> How to get those data to WU?
>>
>> Just now on my station we do not see temp and humidity of the soil.
>>
>> https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56
>>
>> Next topic is best timings for sending data, is it possible to get data 
>> in RealTime?
>> In general Davis has archival for 5min (300sec) so it sends data every 
>> 5minute.
>> I had tried rapid fire, but it sends data every 2.5 sec but data changes 
>> every 5minute so it's a little bit crazy.
>>
>> Is there anybody using Davis Vantage pro2 and WU and could share your 
>> config?
>>
>> Thanks in advance
>> BR
>> Jacek 
>>
>

-- 
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] Convert 60 seconds to 5 minute database

[stefano siega]

Someone can help me to do the correct select statement from database to mediate 
5 entries to one and preserve max and min loop values?

Many 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: Please can I have my bug back?

[Macha]

No I didn't. In fact I didn't play around with nice levels etc.

The "original" RPi is a Pi 2 (more by accident than intention, but it 
should have enough "welly") - it now runs just weewx and a single camera 
and its CPU utilisation is very low. 

In fact, the original "lockouts" weren't coincident with weewx's reporting 
and seemed pretty random (and infrequent). I still suspect that the whole 
issue had something to do with the fact that this "original" machine stores 
"/" on my NFS and consequently Ethernet traffic is high.

Cheers

PS: The RPi now running 3 cameras, several Adafruit sensors and audio 
streaming has had a traumatic history. It is a "Model B+ and was originally 
housed outdoors in a weatherproof clear plastic case. Unfortunately, this 
case wasn't as rugged as hoped and about 12 months ago - after it had 
crashed and following a few days of high wind and heavy rain - I found the 
RPi lying in the grass, soaking wet and covered in a kind of powdery grey 
gunk. I cleaned it up (toothbrush + alcohol + compressed air) and it then 
worked fine agin. The only lasting damage being the failure of the 
spring/clip thing that holds the SD card in place - this is now secured by 
a plastic cable tie. The original SD card was completely fried.

On Sunday, October 30, 2016 at 8:53:44 AM UTC+1, Andrew Milner wrote:
>
> when you had cams and weewx on one machine did you have turbo mode 
> enabled?  It would have needed it I expect.
>
> weewx will have failed because the camera were hogging resources - you 
> could have tried raising the priority.  weewx will trundle along at very 
> low cpu usage UNTIL it generates reports and plots - then it will need very 
> high resources.
>
>
>
> On Sunday, 30 October 2016 09:42:12 UTC+2, Macha wrote:
>
>> OK, status report on my "lockout" with weewx and my FOUSB station.
>>
>> I moved 2 webcams from the RPi running weewx onto a different machine 
>> (another RPi, I have quite a few).
>>
>> Result? No weewx lockouts for nearly 10 days. I'm not sure if this passes 
>> the "5 sigma" test, but it's certainly a record uptime.
>>
>> Still a few puzzlements - on the previous setup, it was always weewx 
>> (well Python I suppose) that "failed", the webcams (run with mjpg-streamer) 
>> were always rock-solid. On the new setup, the RPi which now has the "moved" 
>> webcams is quite busy - it runs the 2 new cameras, plus an RPi camera (all 
>> driven with mjpg-streamer) and also icecast2+darkice (monitoring bird 
>> tweets, etc.) - CPU utilisation is around 35%.  This machine never fails.
>>
>> The previous RPi is now chuffing along at <1% 
>>
>> Anyway, thanks again for the advice and comments ...
>>
>>

-- 
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: Please can I have my bug back?

[Andrew Milner]

when you had cams and weewx on one machine did you have turbo mode 
enabled?  It would have needed it I expect.

weewx will have failed because the camera were hogging resources - you 
could have tried raising the priority.  weewx will trundle along at very 
low cpu usage UNTIL it generates reports and plots - then it will need very 
high resources.



On Sunday, 30 October 2016 09:42:12 UTC+2, Macha wrote:

> OK, status report on my "lockout" with weewx and my FOUSB station.
>
> I moved 2 webcams from the RPi running weewx onto a different machine 
> (another RPi, I have quite a few).
>
> Result? No weewx lockouts for nearly 10 days. I'm not sure if this passes 
> the "5 sigma" test, but it's certainly a record uptime.
>
> Still a few puzzlements - on the previous setup, it was always weewx (well 
> Python I suppose) that "failed", the webcams (run with mjpg-streamer) were 
> always rock-solid. On the new setup, the RPi which now has the "moved" 
> webcams is quite busy - it runs the 2 new cameras, plus an RPi camera (all 
> driven with mjpg-streamer) and also icecast2+darkice (monitoring bird 
> tweets, etc.) - CPU utilisation is around 35%.  This machine never fails.
>
> The previous RPi is now chuffing along at <1% 
>
> Anyway, thanks again for the advice and comments ...
>
>

-- 
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: Please can I have my bug back?

[Macha]

OK, status report on my "lockout" with weewx and my FOUSB station.

I moved 2 webcams from the RPi running weewx onto a different machine (another 
RPi, I have quite a few).

Result? No weewx lockouts for nearly 10 days. I'm not sure if this passes the 
"5 sigma" test, but it's certainly a record uptime.

Still a few puzzlements - on the previous setup, it was always weewx (well 
Python I suppose) that "failed", the webcams (run with mjpg-streamer) were 
always rock-solid. On the new setup, the RPi which now has the "moved" webcams 
is quite busy - it runs the 2 new cameras, plus an RPi camera (all driven with 
mjpg-streamer) and also icecast2+darkice (monitoring bird tweets, etc.) - CPU 
utilisation is around 35%.  This machine never fails.

The previous RPi is now chuffing along at <1% 

Anyway, thanks again for the advice and comments ...

-- 
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.