.1.19: -s -d
Thanks again,
Brad
On Saturday, November 12, 2016 at 10:24:33 PM UTC-8, mwall wrote:
>
>
>
> On Sunday, November 13, 2016 at 12:55:46 AM UTC-5, Brad Tucker wrote:
>>
>> Hello Matt,
>>
>> I starting thinking about the time stamp on the log I jus
ber 13, 2016 at 12:55:46 AM UTC-5, Brad Tucker wrote:
>>
>> Hello Matt,
>>
>> I starting thinking about the time stamp on the log I just sent, and that
>> was right around the time I typed in the IP address to find the boot
>> version and firmware vers
:
>
> On Sat, 12 Nov 2016 21:55:45 -0800 (PST)
> Brad Tucker > wrote:
>
> > Hello Matt,
> >
> > I starting thinking about the time stamp on the log I just sent, and
> > that was right around the time I typed in the IP address to find the
> > boot versi
, 2016 at 9:42:56 PM UTC-8, Brad Tucker wrote:
>
> Hey Matt,
>
> I had the interceptor crash this morning. I have attached the current logs.
>
> Thanks,
> Brad
>
>
> Nov 12 06:52:37 weather weewx[725]: interceptor: MainThread: raw data:
> dateutc=now&action=up
Hey Matt,
I had the interceptor crash this morning. I have attached the current logs.
Thanks,
Brad
Nov 12 06:52:37 weather weewx[725]: interceptor: MainThread: raw data:
dateutc=now&action=updateraw&realtime=1&id=24C86E06B15C&mt=5N1x38&sensor=2179&windspeedmph=1&humidity=43&tempf=58.8&baro
I think the 104 boot version means it is older hardware just updated. I have
seen people with a much later boot version. Not positive on the details though.
Good luck.
B
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this
Hello Radar,
I see you and Matt are already trouble shooting your problems but to answer
your question, I believe I am using a new hub. I only bought the unit weeks
ago. With that said here is what the bridge reports.
Boot firmware version : 104
Application version : 224
Hope this helps,
Brad
Still going strong! Thanks Matt!
B
On Tuesday, November 8, 2016 at 7:12:45 AM UTC-8, Brad Tucker wrote:
>
> It's been running for 24 hours :)
> I'll let it go for a few more days and let you know my findings.
>
> Thanks Matt!
> B
>
--
You received this message be
It's been running for 24 hours :)
I'll let it go for a few more days and let you know my findings.
Thanks Matt!
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
It has been loaded. Ill report back in the morning if all goes well.
Thanks Matt,
Brad
On Monday, November 7, 2016 at 7:57:39 AM UTC-8, mwall wrote:
>
>
>
> On Monday, November 7, 2016 at 12:08:35 AM UTC-5, Brad Tucker wrote:
>>
>> Good Evening Matt,
>>
>> I
Good Evening Matt,
I thought tcpflow would go forever but forever happened to only be 12 hours
;) After running for a very long time everything crashed. Ive been keeping
a mindful eye on it so I caught it pretty early... Attached is a syslog.
Let me know if you see anything I should look for. T
Great. I was thinking to add it to the initd startup but I like the idea of
adding if it to the weewx initd instead. Thanks for the thoughts.
Thanks,
Brad
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop re
1478451000) to database 'weewx.sdb'
Nov 6 08:50:17 weather weewx[20110]: manager: added record 2016-11-06
08:50:00 PST (1478451000) to daily summary in 'weewx.sdb'
Nov 6 08:50:18 weather weewx[20110]: reportengine: Running reports for
latest time in the database.
Nov 6 08:50:
4:47:09 AM UTC-8, mwall wrote:
>
>
>
> On Sunday, November 6, 2016 at 2:32:46 AM UTC-5, Brad Tucker wrote:
>>
>> Decided to turn off the FTP skin and see if it changed anything. I still
>> got the crash and here is the syslog:
>>
>>
> tcpdump is pick
Decided to turn off the FTP skin and see if it changed anything. I still
got the crash and here is the syslog:
Nov 6 00:28:32 weather weewx[19819]: interceptor: ServerThread: POST:
dateutc=now&action=updateraw&realtime=1&id=24C86E06B15C&mt=tower&sensor=00012694&humidity=51&tempf=70.6&baromin=29
Hello Matt!
I think I have some good news. After I did the clean install tcpdump worked
exactly as it had before. However this time I tried to give tcpflow a shot.
It has a great output and then once I run it through your perl script it
looks really pretty and all on one line. It will run for a
t every thing on one line
>>
>> On Wednesday, November 2, 2016 at 7:21:17 PM UTC-5, Brad Tucker wrote:
>>>
>>> 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 stre
:06:39 PM UTC-4, Brad Tucker wrote:
>>
>> Hey Matt,
>>
>> This is in syslog when the tcpdump chokes...
>>
>> Nov 5 18:58:55 weather weewx[2574]: interceptor: MainThread: parse
>> failed for
>> dateutc=now&action=updateraw&realtime=1&a
eTime':
pkt['dateTime'], 'usUnits': pkt['usUnits']}
Nov 5 18:58:56 weather weewx[2574]: KeyError: 'dateTime'
Nov 5 18:58:56 weather weewx[2574]: Exiting.
to get going again, I have to restart weewx completely...
sudo service weewx restart
-Bra
18:45:35 weather weewx[2331]: interceptor: MainThread: ignored
parameter rainin=0.00
Nov 5 18:45:35 weather weewx[2331]: interceptor: MainThread: parse failed
for
dateutc=now&action=updateraw&realtime=1>&id=24C86E06B15C&mt=5N1x31&sensor=2179>&windspeedmph=0&
This appears to work I'm vpn'ed in from my phone and doing it at dinner
while with the family. I'm getting dirty looks from the wife ;) I'll let it run
and send you some logs as soon as I get home. I did notice some small errors
but I see things parsing! Thanks for your help and your patienc
sudo tcpdump -Anpl -s0 -w - -i eth0 dst port 80 | stdbuf -oL
strings -n5 | ./combine-lines.pl | xargs -n 1 curl http://192.168.1.7:8080
-s -d
tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size
262144 bytes
syslog
Nov 5 17:02:36 weather weewx[769]: interceptor: MainThread: e
p;sensor=00012694
&humidity=45&tempf=71.5
&baromin=29.29&battery=normal&rssi=3
HTTP/1.1
hubapi.myacurite.com
User-Agent: Hub/224
Connection: close
^C58 packets captured
58 packets received by filter
0 packets dropped by kernel
>
>
>
> On Saturday, Novemb
06B15C&mt=tower&sensor=00012694&humidity=45&tempf=71.2&baromin=29.29&battery=normal&rssi=3hubapi.myacurite.com
dateutc=now&action=updateraw&realtime=1&id=24C86E06B15C&mt=tower&sensor=8384&humidity=30&tempf=79.8&baromin=29.29&battery
Here is the dump.txt
On Saturday, November 5, 2016 at 4:23:22 PM UTC-7, mwall wrote:
>
> On Saturday, November 5, 2016 at 6:47:45 PM UTC-4, Brad Tucker wrote:
>>
>> this is looking yummy :)
>>
>>>
>>>
> getting close. i don't know where the spur
0&PASSWORD=ofsglckk&dateutc=now&action=updateraw&realtime=1&rtfreq=36&id=24C86E06B15C&mt=5N1x31&sensor=2179&windspeedmph=1&winddir=90&rainin=0.00&dailyrainin=0.20&humidity=37&tempf=78.8&dewptf=51&baromin=29.28&battery=normal&r
ssi=3�UX\#GG&�8vB$�n�E9odVQ��46�_1P�p{�M�!P���
HTTP/1.1
Host: �UX�*__&�8vB$�n�EQodV8��46�_1P�p{�M�!P��hubapi.myacurite.com
User-Agent: Hub/224�UXMM&�8vB$�n�E?o dVI��46�_1P�p|M�!P�Cn
Connection: close
^C44 packets captured
44 packets received by filter
0 packets dropped by kernel
�UX�*
hese options is used more than once on the
same command line, the data pieces specified will be merged together with a
separating &-symbol. Thus, using '-d name=daniel -d
skill=lousy' would generate a post chunk that looks like
'name=daniel&skill=lousy'.
line;
$obs_line = $obs_line . $newline;
$newline = '';
}
if ($build == 2) {
$build = 0;
print "$obs_line\n";
$req->content("$obs_line");
$res = $ua->request($req);
$obs_line = 'dateutc=now&action=updateraw&realtime=1';
if ( $res->is_success ) {
pr
;:
0, 'rainfall.2179.24C86E06B15C': 0.0, 'dateTime.2179.24C86E06B15C':
1478312343, 'bridge_id.2179.24C86E06B15C': '24C86E06B15C',
'barometer.2179.24C86E06B15C': 29.34, 'dateTime': 1478312343,
'windspeed.2179.24C
Yes, that is correct. I have installed the latest off GitHub.
DRIVER_NAME = 'Interceptor'
DRIVER_VERSION = '0.14'
On Saturday, November 5, 2016 at 9:55:47 AM UTC-7, mwall wrote:
>
> On Saturday, November 5, 2016 at 12:46:27 PM UTC-4, Brad Tucker wrote:
>>
>&
or: MainThread: ignored
parameter realtime=1
Nov 5 09:19:09 weather weewx[4699]: interceptor: MainThread: ignored
parameter action=updateraw
Nov 5 09:19:09 weather weewx[4699]: interceptor: MainThread: raw packet:
{'humidity.8384.24C86E06B15C': 35.0, 'dateTime.8384.24C
eedmph=0&winddir=113&rainin=0.00&dailyrainin=0.55&humidity=50&tempf=59.2&dewptf=41&baromin=29.35&battery=normal&rssi=3
HTTP/1.1
Host: rtupdate.wunderground.com
Connection: close
On Friday, November 4, 2016 at 9:45:30 PM UTC-7, Brad Tucker wrote:
>
> M
00&dailyrainin=0.55&humidity=50&tempf=59.2&dewptf=41&baromin=29.35&battery=normal&rssi=3
HTTP/1.1
Host: rtupdate.wunderground.com
Connection: close
On Friday, November 4, 2016 at 9:26:05 PM UTC-7, mwall wrote:
>
> On Friday, November 4, 2016 at 10:42:37 PM UTC-4, Bra
r help,
Brad
On Friday, November 4, 2016 at 9:26:05 PM UTC-7, mwall wrote:
>
> On Friday, November 4, 2016 at 10:42:37 PM UTC-4, Brad Tucker wrote:
>>
>> For some reason Rain is not being logged to the system w/ the interceptor
>> model. I accidentally tripped the rain s
For some reason Rain is not being logged to the system w/ the interceptor
model. I accidentally tripped the rain señor while working on the unit
today, and the acurite display is reporting .55 inches however my plots
show 0 as do the stats. I took a look at the database to make sure nothing
is
itted from your Acurite.
>
> -tk
>
>
> On Thu, Nov 3, 2016 at 11:59 AM, Brad Tucker > wrote:
>
>> outTemp, windchill & heatindex are all registering the same temp. on my
>> system. Anyone have any ideas on where to look? When I look at the
>> myAcurite
outTemp, windchill & heatindex are all registering the same temp. on my
system. Anyone have any ideas on where to look? When I look at the
myAcurite web display they are al different but for some reason whew is
reporting them all the same. I thought maybe the value where just drawing
on top of
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.&-.
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 "&"
out
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,
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, Octo
mid2 = humidity.00008384.*
On Tuesday, November 1, 2016 at 5:39:10 AM UTC-7, mwall wrote:
>
>
>
> On Tuesday, November 1, 2016 at 2:08:14 AM UTC-4, Brad Tucker wrote:
>>
>> Thanks for the help Mwall.
>> For some reason it is still not mapping the barometer. i
; On Monday, October 31, 2016 at 3:47:51 PM UTC-5, Brad Tucker wrote:
>>
>> Radar,
>>
>> Thanks again for script and all the help. I ran my tcpdump through your
>> script and it actually logs data!!! I have added some of the logs so you
>> can see. One thing
'windspeed.2179.24C86E06B15C': 2.0, 'humidity.2179.24C86E06B15C':
69.0, 'usUnits': 1}
Oct 31 23:01:14 weather weewx[2895]: interceptor: MainThread: *mapped
packet: {'outHumidity': 69.0, 'rain': 0.0, 'dateTime': 1477980075,
'
Fantastic. Thanks Mwall! Not sure Ill get to this tonight, being halloween
and all, but Ill def tackle it late night or tomorrow sometime. Thanks for
the info. Also thanks for the nice drivers. I played around with the SDR
driver and had a blast. Im a ham operator so playing with computers, and
Monday, October 31, 2016 at 2:45:59 PM UTC-7, mwall wrote:
>
> On Monday, October 31, 2016 at 4:47:51 PM UTC-4, Brad Tucker wrote:
>
>> I also have 2 Tower Sensors attached so I included logs for this incase
>> one of them is conflicting...
>>
>
> brad,
>
&g
Thanks for the reply mwall. Good to hear its working as expected and that I
can change it if I like.
Thanks!
Brad
On Monday, October 31, 2016 at 2:28:35 PM UTC-7, mwall wrote:
>
> On Monday, October 31, 2016 at 4:47:51 PM UTC-4, Brad Tucker wrote:
>>
>> 3. Why do
Radar,
Thanks again for script and all the help. I ran my tcpdump through your
script and it actually logs data!!! I have added some of the logs so you
can see. One thing Ive noticed is it doesn't log barometric pressure. Not
sure why. I did see that after getting processed by the perl script i
Radar wrote:
>>
>> here is the one i used to play with interceptor driver
>>
>> On Sunday, October 30, 2016 at 11:09:01 PM UTC-5, Brad Tucker wrote:
>>>
>>> Ha! Of course the most important part ;) I have 1.44 but I'll dig for
>>> the s
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
Ha! Of course the most important part ;) I have 1.44 but I'll dig for the
source and see what I can find.
Thanks for the 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,
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
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...@
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 t
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 problem
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
57 matches
Mail list logo
