Re: [weewx-user] wunderfixer: OK with --test, fails when doing it for real

[David Hathaway]

Worked great!  Thanks ever so much!

Dave

On Wednesday, November 2, 2016 at 9:02:49 PM UTC-5, David Hathaway wrote:
>
> mwall and Gary,
>
> Yes, it is 3.6.0.  I'll go ahead and update.  I didn't realize there was a 
> 3.6.1 already. :-/
>
> I'll report back on success or failure.
>
> Dave
>
> On Wed, Nov 2, 2016 at 8:57 PM, gjr80  wrote:
>
>> Hi,
>>
>> What version of weewx are you running, 3.6.0? I am pretty sure this issue 
>> was fixed in 3.6.1. If you are on 3.6.0 you might want to try pulling down 
>> the current wunderfixer.py.
>>
>> Gary
>>
>> --
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/W2sBVQJmAQw/unsubscribe.
>> To unsubscribe from this group and all its topics, 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] wunderfixer: OK with --test, fails when doing it for real

[David Hathaway]

mwall and Gary,

Yes, it is 3.6.0.  I'll go ahead and update.  I didn't realize there was a
3.6.1 already. :-/

I'll report back on success or failure.

Dave

On Wed, Nov 2, 2016 at 8:57 PM, gjr80  wrote:

> Hi,
>
> What version of weewx are you running, 3.6.0? I am pretty sure this issue
> was fixed in 3.6.1. If you are on 3.6.0 you might want to try pulling down
> the current wunderfixer.py.
>
> Gary
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/W2sBVQJmAQw/unsubscribe.
> To unsubscribe from this group and all its topics, 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] wunderfixer: OK with --test, fails when doing it for real

[gjr80]

Hi,

What version of weewx are you running, 3.6.0? I am pretty sure this issue was 
fixed in 3.6.1. If you are on 3.6.0 you might want to try pulling down the 
current wunderfixer.py.

Gary

-- 
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: wunderfixer: OK with --test, fails when doing it for real

[mwall]

On Wednesday, November 2, 2016 at 9:51:47 PM UTC-4, David Hathaway wrote:

> What am I doing wrong?
>

hi dave,

the missing '_formats' is a bug in weewx 3.6.0 caused by changes i made

it has been fixed in weewx 3.6.1

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] wunderfixer: OK with --test, fails when doing it for real

[David Hathaway]

Xfinity crapped again, cutting my station off from the net.  I decided to 
try wunderfixer.

When run as

>> sudo wunderfixer -t

I get a lot of pseudo-published records, such as.

Using configuration file /etc/weewx/weewx.conf.
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
2016-11-02 00:00:00 CDT (1478062800); 30.014";  75.2F;  86%; 0.8 mph;  97 
deg; 2.0 mph gust;  70.7F; 0.00" rain; 0.00" daily rain  ... skipped.
2016-11-02 00:01:00 CDT (1478062860); 30.013";  75.2F;  86%; 0.2 mph;  97 
deg; 1.0 mph gust;  70.7F; 0.00" rain; 0.00" daily rain  ... skipped.

etc

However, run as 

>> sudo wunderfixer

I get:

Using configuration file /etc/weewx/weewx.conf.
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
2016-11-02 00:00:00 CDT (1478062800); 30.014";  75.2F;  86%; 0.8 mph;  97 
deg; 2.0 mph gust;  70.7F; 0.00" rain; 0.00" daily rain
Traceback (most recent call last):
  File "/usr/bin/wunderfixer", line 558, in 
main()
  File "/usr/bin/wunderfixer", line 276, in main
wunder.postData(record)
  File "/usr/bin/wunderfixer", line 387, in postData
for _key in weewx.restx.AmbientThread._formats:
AttributeError: type object 'AmbientThread' has no attribute '_formats'

What am I doing wrong?

Dave

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

Only thing I noticed is you are running it off the bridge device. I can't 
get any data off my bridge device. only eth0. I also see a stream similar 
to yours when its communicating with weatherunderground. Is it possible you 
didn't let it run long enough? Im assuming you let it run for a min or two 
and had the same results? 

Past that I have no more ideas :( sorry...
B

On Wednesday, November 2, 2016 at 5:06:51 PM UTC-7, Pat Hayes wrote:
>
> Looks like yours minus the good stuff.
>
> [root@weewx ~]# tcpdump -A -n -p -l -i bridge0 -s0 -W tcp dst port 80 | 
> stdbuf -oL strings -n8 | stdbuf -oL grep "&"
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on bridge0, link-type EN10MB (Ethernet), capture size 65535 bytes
> E..4l.@.1..+b..7...*...P.&9.R...
> E..(l.@.1..6b..7...*...P.&...v.PP...3.
> E...l.@.1...b..7...*...P.&...v.PP...{4..GET / HTTP/1.0
> E..4l.@.1..(b..7...*...P.&...v.P.{.
> E..4l.@.1..'b..7...*...P.&...v"8...
> E..4l.@.1..&b..7...*...P.&...v'
> E..4l.@.1..%b..7...*...P.&...v.l..-..C.
> E..4l.@.1..$b..7...*...P.&...v.l..-..?.
> E..(..@.1.Y.b..7...*...P.&..P.
> E..(..@.1.Y.b..7...*...P.&..P.
> E..(..@.1.Y.b..7...*...P.&..P.
> E..(..@.1.Y.b..7...*...P.&..P.
> E..(..@.1.Y.b..7...*...P.&..P.
> E.@.5.&.F,4*...PX~4..;...*.
> E&@.5...F,4*...P..-..X.R.$.
> E..4.&@.5.+.F,4*...PX~6M.<.w...
> f.6.&,.[.
> f.6.&,...
> f.6.&-.5.
> ^C62 packets captured
> 62 packets received by filter
> 0 packets dropped by kernel
>
>
>
>
> On Wednesday, November 2, 2016 at 7:38:41 PM UTC-4, Brad Tucker wrote:
>>
>> what does you output look like on tcpdump w/o the perl script? mine 
>> always looked strange but it worked... Also don't do it off the bridge but 
>> use eth0 or your main ethernet to the router.
>> sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | stdbuf -oL 
>> strings -n8 | stdbuf -oL grep "&"
>>
>> output always looks strange but it works well with the perl script:
>> pi@weather:~ $ sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | 
>> stdbuf -oL strings -n8 | stdbuf -oL grep "&"
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
>> E..xfd..d.=.4}.P.. B...cP...D...GET 
>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>> E..Qfe..d.=.4}.P.. 
>> cPg..&id=24C86E06B15C&mt=tower&sensor=00012694
>> 4}.P.. cP...OD..&humidity=53&tempf=73.0
>> E..Lfg..d.=.4}.P.. 
>> cP|..&baromin=29.31&battery=normal&rssi=3
>> E..xfs..d...4~.P..0jP...GET 
>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>>
>> E..Qft..d...4~.P..0jP...UH..&id=24C86E06B15C&mt=tower&sensor=8384
>> E..?fu..d...4~.P..1jP$..&humidity=37&tempf=82.3
>>
>> E..Lfv..d...4~.P..1/...jP..._c..&baromin=29.31&battery=normal&rssi=2
>> E..xf...d.^.46._...P/...P...3...GET 
>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>>
>> E..Rf...d.^.46._...P/..LP5..&id=24C86E06B15C&mt=5N1x38&sensor=2179
>> E..Cf...d.^.46._...P/..vP6..&windspeedmph=3&humidity=15
>> E..3f...d.^.46._...P/...P...Rg..&tempf=78.4
>>
>> E..Lf...d.^.46._...P/...P...&baromin=29.31&battery=normal&rssi=3
>>
>> GLUCK!
>> B
>>
>>
>> On Wednesday, November 2, 2016 at 4:30:08 PM UTC-7, Pat Hayes wrote:
>>>
>>> With just the tcpflow command, it shows this.
>>>
>>> [root@weewx ~]# tcpflow -C -0 -s tcp dst port 80
>>> tcpflow: listening on bridge0
>>> GET 
>>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x38&sensor=2701&windspeedmph=0&humidity=86&tempf=58.8&baromin=30.34&battery=normal&rssi=3
>>>  
>>> HTTP/1.1
>>> Host: hubapi.myacurite.com
>>> User-Agent: Hub/224
>>> Connection: close
>>>
>>> GET 
>>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
>>>  
>>> HTTP/1.1
>>> Host: hubapi.myacurite.com
>>> User-Agent: Hub/224
>>> Connection: close
>>>
>>> GET 
>>> /weatherstation/updateweatherstation.php?ID=KNJNEWJE4&PASSWORD=pat6854&dateutc=now&action=updateraw&realtime=1&rtfreq=36&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
>>>  
>>> HTTP/1.1
>>> Host: rtupdate.wunderground.com
>>> Connection: close
>>>
>>>
>>>
>>> Brad, I tryed your combination, but nothing gets sent to weewx and 
>>> nothing gets shown in console either.
>>>
>>>

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

[Thomas Keffer]

Close.

For a simple report like this, you want "ToDate" generation (as opposed to
summaries by month or year, like the NOAA reports). So, you need to tuck
your addition under [[ToDate]] and add one more set of brackets. It will
look like:

[[ToDate]]

... (other templates)

[[[temp.txt]]]
# Report that makes current outTemp available to other program
encoding = strict_ascii
template = temp.txt.tmpl

-tk

On Wed, Nov 2, 2016 at 4:04 PM, Jim W.  wrote:

> Tom and Andrew,
> I have created a new template called temp.txt.tmpl in the
> etc/weewx/skins/Standard directory. It's only content is: $current.outTemp
>
> In the skin.conf file under [CheetahGenerator] I added:
>
>[[temp.txt]]
> # Report that makes current outTemp available to other program
> encoding = strict_ascii
> template = temp.txt.tmpl
>
> Am I on the right track? Thanks for your patience!
>
>
>
>
>
> On Monday, October 31, 2016 at 9:23:13 AM UTC-4, Jim W. wrote:
>>
>> THANKS ALL... now i'm heading in the right direction!!!
>>
>>
>>
>> On Sunday, October 30, 2016 at 9:31:54 PM UTC-4, Tom Keffer wrote:
>>>
>>> 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+...@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.
>

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

[Pat Hayes]

Looks like yours minus the good stuff.

[root@weewx ~]# tcpdump -A -n -p -l -i bridge0 -s0 -W tcp dst port 80 | 
stdbuf -oL strings -n8 | stdbuf -oL grep "&"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bridge0, link-type EN10MB (Ethernet), capture size 65535 bytes
E..4l.@.1..+b..7...*...P.&9.R...
E..(l.@.1..6b..7...*...P.&...v.PP...3.
E...l.@.1...b..7...*...P.&...v.PP...{4..GET / HTTP/1.0
E..4l.@.1..(b..7...*...P.&...v.P.{.
E..4l.@.1..'b..7...*...P.&...v"8...
E..4l.@.1..&b..7...*...P.&...v'
E..4l.@.1..%b..7...*...P.&...v.l..-..C.
E..4l.@.1..$b..7...*...P.&...v.l..-..?.
E..(..@.1.Y.b..7...*...P.&..P.
E..(..@.1.Y.b..7...*...P.&..P.
E..(..@.1.Y.b..7...*...P.&..P.
E..(..@.1.Y.b..7...*...P.&..P.
E..(..@.1.Y.b..7...*...P.&..P.
E.@.5.&.F,4*...PX~4..;...*.
E&@.5...F,4*...P..-..X.R.$.
E..4.&@.5.+.F,4*...PX~6M.<.w...
f.6.&,.[.
f.6.&,...
f.6.&-.5.
^C62 packets captured
62 packets received by filter
0 packets dropped by kernel




On Wednesday, November 2, 2016 at 7:38:41 PM UTC-4, Brad Tucker wrote:
>
> what does you output look like on tcpdump w/o the perl script? mine always 
> looked strange but it worked... Also don't do it off the bridge but use 
> eth0 or your main ethernet to the router.
> sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | stdbuf -oL 
> strings -n8 | stdbuf -oL grep "&"
>
> output always looks strange but it works well with the perl script:
> pi@weather:~ $ sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | 
> stdbuf -oL strings -n8 | stdbuf -oL grep "&"
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
> E..xfd..d.=.4}.P.. B...cP...D...GET 
> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
> E..Qfe..d.=.4}.P.. 
> cPg..&id=24C86E06B15C&mt=tower&sensor=00012694
> 4}.P.. cP...OD..&humidity=53&tempf=73.0
> E..Lfg..d.=.4}.P.. 
> cP|..&baromin=29.31&battery=normal&rssi=3
> E..xfs..d...4~.P..0jP...GET 
> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>
> E..Qft..d...4~.P..0jP...UH..&id=24C86E06B15C&mt=tower&sensor=8384
> E..?fu..d...4~.P..1jP$..&humidity=37&tempf=82.3
>
> E..Lfv..d...4~.P..1/...jP..._c..&baromin=29.31&battery=normal&rssi=2
> E..xf...d.^.46._...P/...P...3...GET 
> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
>
> E..Rf...d.^.46._...P/..LP5..&id=24C86E06B15C&mt=5N1x38&sensor=2179
> E..Cf...d.^.46._...P/..vP6..&windspeedmph=3&humidity=15
> E..3f...d.^.46._...P/...P...Rg..&tempf=78.4
>
> E..Lf...d.^.46._...P/...P...&baromin=29.31&battery=normal&rssi=3
>
> GLUCK!
> B
>
>
> On Wednesday, November 2, 2016 at 4:30:08 PM UTC-7, Pat Hayes wrote:
>>
>> With just the tcpflow command, it shows this.
>>
>> [root@weewx ~]# tcpflow -C -0 -s tcp dst port 80
>> tcpflow: listening on bridge0
>> GET 
>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x38&sensor=2701&windspeedmph=0&humidity=86&tempf=58.8&baromin=30.34&battery=normal&rssi=3
>>  
>> HTTP/1.1
>> Host: hubapi.myacurite.com
>> User-Agent: Hub/224
>> Connection: close
>>
>> GET 
>> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
>>  
>> HTTP/1.1
>> Host: hubapi.myacurite.com
>> User-Agent: Hub/224
>> Connection: close
>>
>> GET 
>> /weatherstation/updateweatherstation.php?ID=KNJNEWJE4&PASSWORD=pat6854&dateutc=now&action=updateraw&realtime=1&rtfreq=36&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
>>  
>> HTTP/1.1
>> Host: rtupdate.wunderground.com
>> Connection: close
>>
>>
>>
>> Brad, I tryed your combination, but nothing gets sent to weewx and 
>> nothing gets shown in console either.
>>
>> [root@weewx ~]# tcpdump -A -n -p -l -i bridge0 -s0 -W tcp dst port 80 | 
>> stdbuf -oL strings -n8 | stdbuf -oL grep "&" | ./acurite-lwp.pl
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on bridge0, link-type EN10MB (Ethernet), capture size 65535 
>> bytes
>> ^C42 packets captured
>> 42 packets received by filter
>> 0 packets dropped by kernel
>>
>>
>>
>>
>> On Wednesday, November 2, 2016 at 7:17:42 PM UTC-4, mwall wrote:
>>>
>>> On Wednesday, November 2, 2016 at 6:53:13 PM UTC-4, Pat Hayes wrote:

 I've been following this 

[weewx-user] Re: Interceptor using bridge new Accurate firmware

[Brad Tucker]

what does you output look like on tcpdump w/o the perl script? mine always 
looked strange but it worked... Also don't do it off the bridge but use 
eth0 or your main ethernet to the router.
sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | stdbuf -oL 
strings -n8 | stdbuf -oL grep "&"

output always looks strange but it works well with the perl script:
pi@weather:~ $ sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | 
stdbuf -oL strings -n8 | stdbuf -oL grep "&"
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
E..xfd..d.=.4}.P.. B...cP...D...GET 
/weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
E..Qfe..d.=.4}.P.. 
cPg..&id=24C86E06B15C&mt=tower&sensor=00012694
4}.P.. cP...OD..&humidity=53&tempf=73.0
E..Lfg..d.=.4}.P.. cP|..&baromin=29.31&battery=normal&rssi=3
E..xfs..d...4~.P..0jP...GET 
/weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
E..Qft..d...4~.P..0jP...UH..&id=24C86E06B15C&mt=tower&sensor=8384
E..?fu..d...4~.P..1jP$..&humidity=37&tempf=82.3
E..Lfv..d...4~.P..1/...jP..._c..&baromin=29.31&battery=normal&rssi=2
E..xf...d.^.46._...P/...P...3...GET 
/weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1
E..Rf...d.^.46._...P/..LP5..&id=24C86E06B15C&mt=5N1x38&sensor=2179
E..Cf...d.^.46._...P/..vP6..&windspeedmph=3&humidity=15
E..3f...d.^.46._...P/...P...Rg..&tempf=78.4
E..Lf...d.^.46._...P/...P...&baromin=29.31&battery=normal&rssi=3

GLUCK!
B


On Wednesday, November 2, 2016 at 4:30:08 PM UTC-7, Pat Hayes wrote:
>
> With just the tcpflow command, it shows this.
>
> [root@weewx ~]# tcpflow -C -0 -s tcp dst port 80
> tcpflow: listening on bridge0
> GET 
> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x38&sensor=2701&windspeedmph=0&humidity=86&tempf=58.8&baromin=30.34&battery=normal&rssi=3
>  
> HTTP/1.1
> Host: hubapi.myacurite.com
> User-Agent: Hub/224
> Connection: close
>
> GET 
> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
>  
> HTTP/1.1
> Host: hubapi.myacurite.com
> User-Agent: Hub/224
> Connection: close
>
> GET 
> /weatherstation/updateweatherstation.php?ID=KNJNEWJE4&PASSWORD=pat6854&dateutc=now&action=updateraw&realtime=1&rtfreq=36&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
>  
> HTTP/1.1
> Host: rtupdate.wunderground.com
> Connection: close
>
>
>
> Brad, I tryed your combination, but nothing gets sent to weewx and nothing 
> gets shown in console either.
>
> [root@weewx ~]# tcpdump -A -n -p -l -i bridge0 -s0 -W tcp dst port 80 | 
> stdbuf -oL strings -n8 | stdbuf -oL grep "&" | ./acurite-lwp.pl
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on bridge0, link-type EN10MB (Ethernet), capture size 65535 bytes
> ^C42 packets captured
> 42 packets received by filter
> 0 packets dropped by kernel
>
>
>
>
> On Wednesday, November 2, 2016 at 7:17:42 PM UTC-4, mwall wrote:
>>
>> On Wednesday, November 2, 2016 at 6:53:13 PM UTC-4, Pat Hayes wrote:
>>>
>>> I've been following this thread thanks to Brad letting me know of it. It 
>>> seems I ran into a snag. It seems the interceptor driver doesn't like the 
>>> input. 
>>>
>>
>> pat,
>>
>> it looks like your tcpflow/acurite-lwp.pl combination is butchering the 
>> string that it is posting to the interceptor.
>>
>> what do you see when you just do the tcpflow command?
>>
>> 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

[Pat Hayes]

With just the tcpflow command, it shows this.

[root@weewx ~]# tcpflow -C -0 -s tcp dst port 80
tcpflow: listening on bridge0
GET 
/weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x38&sensor=2701&windspeedmph=0&humidity=86&tempf=58.8&baromin=30.34&battery=normal&rssi=3
 
HTTP/1.1
Host: hubapi.myacurite.com
User-Agent: Hub/224
Connection: close

GET 
/weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
 
HTTP/1.1
Host: hubapi.myacurite.com
User-Agent: Hub/224
Connection: close

GET 
/weatherstation/updateweatherstation.php?ID=KNJNEWJE4&PASSWORD=pat6854&dateutc=now&action=updateraw&realtime=1&rtfreq=36&id=24C86E08150D&mt=5N1x31&sensor=2701&windspeedmph=0&winddir=158&rainin=0.00&dailyrainin=0.00&humidity=86&tempf=58.8&dewptf=54&baromin=30.34&battery=normal&rssi=3
 
HTTP/1.1
Host: rtupdate.wunderground.com
Connection: close



Brad, I tryed your combination, but nothing gets sent to weewx and nothing 
gets shown in console either.

[root@weewx ~]# tcpdump -A -n -p -l -i bridge0 -s0 -W tcp dst port 80 | 
stdbuf -oL strings -n8 | stdbuf -oL grep "&" | ./acurite-lwp.pl
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bridge0, link-type EN10MB (Ethernet), capture size 65535 bytes
^C42 packets captured
42 packets received by filter
0 packets dropped by kernel




On Wednesday, November 2, 2016 at 7:17:42 PM UTC-4, mwall wrote:
>
> On Wednesday, November 2, 2016 at 6:53:13 PM UTC-4, Pat Hayes wrote:
>>
>> I've been following this thread thanks to Brad letting me know of it. It 
>> seems I ran into a snag. It seems the interceptor driver doesn't like the 
>> input. 
>>
>
> pat,
>
> it looks like your tcpflow/acurite-lwp.pl combination is butchering the 
> string that it is posting to the interceptor.
>
> what do you see when you just do the tcpflow command?
>
> 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

[mwall]

On Wednesday, November 2, 2016 at 6:53:13 PM UTC-4, Pat Hayes wrote:
>
> I've been following this thread thanks to Brad letting me know of it. It 
> seems I ran into a snag. It seems the interceptor driver doesn't like the 
> input. 
>

pat,

it looks like your tcpflow/acurite-lwp.pl combination is butchering the 
string that it is posting to the interceptor.

what do you see when you just do the tcpflow command?

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: locale.Error: unsupported locale setting

[John Masters]

After some more reading i rebooted the pi and the command succeeded.
Regards
John
P.s. i will delete this post 

On Wednesday, November 2, 2016 at 8:43:24 PM UTC, John Masters wrote:
>
> Hi Folks, me again in trouble!
>
> I have worked through the wee_import procedure and imported 3 years of old 
> data successfully.  Many thanks for that excellent utility. I have been 
> able to make new graphs showing it.
> I found some extreme rain data in year 2008/2009, which i remember was 
> down to over excited spiders in the rain gauge who i evicted, and removed 
> said data using TK's "cleaning up old 'bad' data recipe on the wiki.
>
> When i came to drop the daily summaries however i get an error:
>
> root@pikodi:/home/weewx/bin# ./wee_database weewx.conf --drop-daily
> Traceback (most recent call last):
>   File "./wee_database", line 15, in 
> import user.extensions  #@UnusedImport
>   File "/home/weewx/bin/user/extensions.py", line 18, in 
> locale.setlocale(locale.LC_ALL, '')
>   File "/usr/lib/python2.7/locale.py", line 579, in setlocale
> return _setlocale(category, locale)
> locale.Error: unsupported locale setting
>
>
> john@pikodi:/home/weewx/bin $ locale -a
> C
> C.UTF-8
> en_GB.utf8
> POSIX
>
> john@pikodi:/home/weewx/bin $ echo $LANG
> en_GB.UTF-8
>
> What foolishness have i been up to this time, and how can i fix it?
> Cheers
> John
>
>
>

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

[Jim W.]

Tom and Andrew,
I have created a new template called temp.txt.tmpl in the 
etc/weewx/skins/Standard directory. It's only content is: $current.outTemp

In the skin.conf file under [CheetahGenerator] I added:

   [[temp.txt]]
# Report that makes current outTemp available to other program
encoding = strict_ascii
template = temp.txt.tmpl

Am I on the right track? Thanks for your patience!





On Monday, October 31, 2016 at 9:23:13 AM UTC-4, Jim W. wrote:
>
> THANKS ALL... now i'm heading in the right direction!!!
>
>  
>
> On Sunday, October 30, 2016 at 9:31:54 PM UTC-4, Tom Keffer wrote:
>>
>> 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+...@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: Interceptor using bridge new Accurate firmware

[Pat Hayes]

> Hello everyone!
>

I've been following this thread thanks to Brad letting me know of it. It 
seems I ran into a snag. It seems the interceptor driver doesn't like the 
input. 

syslog

Nov  2 18:48:22 weewx weewx[20752]: interceptor: MainThread: parse failed 
for dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x31&sensor
=2701&windspeedmph=0&winddir=68&rainin=0.00&dailyrainin=0.00&humidity=83
&tempf=60.0&dewptf=55&baromin=30.34&battery=normal&rssi=3 
HTTP/1.1#015&windspeedmph=0&winddir=68&rainin=0.00&dailyrainin=0.00&humidity=83&tempf=60.0&dewptf=55&baromin=30.34&battery=normal&rssi=3
 
HTTP/1.1#015&humidity=83&tempf=60.0&dewptf=55&baromin=30.34&battery=normal&rssi=3
 
HTTP/1.1#015&baromin=30.34&battery=normal&rssi=3 HTTP/1.1#015: invalid 
literal for float(): 3 HTTP/1.1

Command I'm using.

tcpflow -C -0 -s tcp dst port 80 | ./acurite-lwp.pl

Debian 8 with the latest tcpflow 1.4.6

Thanks for any pointers.

Pat


-- 
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] start problems

[Glenn McKechnie]

First thought is to open two terminals.
In the first one run
*sudo tail -f /var/log/syslog*
In the second run your start commands. Additionally, make sure you run*
sudo /etc/init.d/weewx stop* first, or use* restart / reload *instead

*.*

run* sudo /etc/init.d/weewx status *or* sudo service weewx status*
immediately after and you will be given a short log extract, a status
report of that daemon

You can add -x to the top of */etc/init.d/weewx* - ie #!/bin/sh -x to get
some feedback - whether it's helpful or not is probably debatable. Make
sure you* run systemctl daemon-reload *anytime you edit an init.d config
file.

Second thought - have you changed from a deb to a setup.py install
recently? ie:- is it the correct init.d script for your installation?





Cheers
 Glenn

rorpi - read only raspberry pi + weewx: now with scripts



On 3 November 2016 at 09:27, J.L. Blom  wrote:

> I have since a few weeks an annoying problem. I cannot start weewx anymore
> with the startup script, only by starting manual.
> So sudo service weewx start doesn't work but sudo /home/weewx/bin/weewxd
> /home/weewx/weewx.conf works.
> sudo service weewx start doesn't give an error but does not start weewx
> sudo /etc/init.d/weewx start gives:
>  "[ ok ] Starting weewx (via systemctl): weewx.service" doesn't start
> weewx either.
> I have no clue how to test where something goes wrong except by putting
> echo lines in the startup script but maybe matt or thomas know what is
> causing this problem and know how to solve it.
> I'm running weewx v 3.5.0 (still not upgraded to 3.6.0) on a raspberrypi 2
> (as my odriod-C2 crashed mysteriously).
> Joep
>
>

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

I too would love to use tcpflow but had problems with it as well. Ive been 
using tcpdump in the meantime...
sudo tcpdump -A -n -p -l -i eth0 -s0 -W tcp dst port 80 | stdbuf -oL 
strings -n8 | stdbuf -oL grep "&" | ./acurite-lwp2.pl

Gluck,
Brad

On Wednesday, November 2, 2016 at 3:53:13 PM UTC-7, Pat Hayes wrote:
>
>
> Hello everyone!
>>
>
> I've been following this thread thanks to Brad letting me know of it. It 
> seems I ran into a snag. It seems the interceptor driver doesn't like the 
> input. 
>
> syslog
>
> Nov  2 18:48:22 weewx weewx[20752]: interceptor: MainThread: parse failed 
> for dateutc=now&action=updateraw&realtime=1&id=24C86E08150D&mt=5N1x31&
> sensor=2701&windspeedmph=0&winddir=68&rainin=0.00&dailyrainin=0.00&
> humidity=83&tempf=60.0&dewptf=55&baromin=30.34&battery=normal&rssi=3 HTTP/
> 1.1#015&windspeedmph=0&winddir=68&rainin=0.00&dailyrainin=0.00&humidity=83&tempf=60.0&dewptf=55&baromin=30.34&battery=normal&rssi=3
>  
> HTTP/1.1#015&humidity=83&tempf=60.0&dewptf=55&baromin=30.34&battery=normal&rssi=3
>  
> HTTP/1.1#015&baromin=30.34&battery=normal&rssi=3 HTTP/1.1#015: invalid 
> literal for float(): 3 HTTP/1.1
>
> Command I'm using.
>
> tcpflow -C -0 -s tcp dst port 80 | ./acurite-lwp.pl
>
> Debian 8 with the latest tcpflow 1.4.6
>
> Thanks for any pointers.
>
> Pat
>
>
>

-- 
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] start problems

[J.L. Blom]

I have since a few weeks an annoying problem. I cannot start weewx 
anymore with the startup script, only by starting manual.
So sudo service weewx start doesn't work but sudo /home/weewx/bin/weewxd 
/home/weewx/weewx.conf works.
sudo service weewx start doesn't give an error but does not start weewx 
sudo /etc/init.d/weewx start gives:
 "[ ok ] Starting weewx (via systemctl): weewx.service" doesn't start 
weewx either.
I have no clue how to test where something goes wrong except by putting 
echo lines in the startup script but maybe matt or thomas know what is 
causing this problem and know how to solve it.
I'm running weewx v 3.5.0 (still not upgraded to 3.6.0) on a raspberrypi 
2 (as my odriod-C2 crashed mysteriously).

Joep

--
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] locale.Error: unsupported locale setting

[John Masters]

Hi Folks, me again in trouble!

I have worked through the wee_import procedure and imported 3 years of old 
data successfully.  Many thanks for that excellent utility. I have been 
able to make new graphs showing it.
I found some extreme rain data in year 2008/2009, which i remember was down 
to over excited spiders in the rain gauge who i evicted, and removed said 
data using TK's "cleaning up old 'bad' data recipe on the wiki.

When i came to drop the daily summaries however i get an error:

root@pikodi:/home/weewx/bin# ./wee_database weewx.conf --drop-daily
Traceback (most recent call last):
  File "./wee_database", line 15, in 
import user.extensions  #@UnusedImport
  File "/home/weewx/bin/user/extensions.py", line 18, in 
locale.setlocale(locale.LC_ALL, '')
  File "/usr/lib/python2.7/locale.py", line 579, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting


john@pikodi:/home/weewx/bin $ locale -a
C
C.UTF-8
en_GB.utf8
POSIX

john@pikodi:/home/weewx/bin $ echo $LANG
en_GB.UTF-8

What foolishness have i been up to this time, and how can i fix it?
Cheers
John


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

[Pat Hayes]

Thanks for remembering me! I saw your thread and I'm in the process of 
reinstalling the VM with weewx on it right now. I will try your findings 
and report back.

Pat

On Wednesday, November 2, 2016 at 11:03:53 AM UTC-4, Brad Tucker wrote:
>
> You might want to take a look at this post. I have it working with a 
> recently updated Interceptor along with a perl script. Details and script 
> are in the post:
>
> https://groups.google.com/forum/#!topic/weewx-user/9JJmM2V2u3U
> Interceptor using bridge new Accurate firmware
>
> Enjoy,
> B
>
> On Monday, October 31, 2016 at 6:28:12 AM UTC-7, Pat Hayes wrote:
>>
>> Hey Brad,
>>
>> I ended up doing it a hack way, imo. I just setup a cron job to run every 
>> minute with that code in it. For some reason though, weewx wasn't picking 
>> up barometer readings. Still have to mess with it some.
>>
>

-- 
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: No data from station

[mwall]

On Tuesday, November 1, 2016 at 4:49:24 PM UTC-4, Alberto Sánchez wrote:
>
> I have had the same problem and I have solve it with the same solution. 
> Using 3.5.0 wmr 300 driver.


alberto, roland, and others,

please try the latest wmr300 driver (0.15rc1).  it uses the usb 
initialization logic from 0.10, but it has the pressure/barometer and wind 
direction fixex that came later.

https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/wmr300.py

it turns out that the wmr300 stations do not default to spewing data to the 
usb - the driver must invoke an interruptWrite periodically to keep the 
data flowing.

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

[Brad Tucker]

You might want to take a look at this post. I have it working with a 
recently updated Interceptor along with a perl script. Details and script 
are in the post:

https://groups.google.com/forum/#!topic/weewx-user/9JJmM2V2u3U
Interceptor using bridge new Accurate firmware

Enjoy,
B

On Monday, October 31, 2016 at 6:28:12 AM UTC-7, Pat Hayes wrote:
>
> Hey Brad,
>
> I ended up doing it a hack way, imo. I just setup a cron job to run every 
> minute with that code in it. For some reason though, weewx wasn't picking 
> up barometer readings. Still have to mess with it some.
>

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