[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
The problem of Atlas not sending data to WU might be that All data been channeled/DNS hijack to weewx, creating a loop (and similar case happened to me, when using DD-WRT DNSmasq). Use the following strategy and have weewx to feed WU. In case of DNS hijack through router (DD-WRT or similar): Do not use DNSmasq for hijack, but Firewall along with IPtables iptables -t nat -A PREROUTING -s [AcessIP] -p tcp --dport 80 -j DNAT --to-destination [weewxIP]:80 iptables -t nat -A POSTROUTING -j MASQUERADE Best, Xant -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/694178c4-8caf-468c-a49d-ce880d47c99e%40googlegroups.com.
Re: [weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
The problem of Atlas not sending data to WU might be that All data been
channeled/DNS hijack to weewx, creating a loop (and similar case happened to
me, when using DD-WRT DNSmasq). Use the following strategy and have weewx to
feed WU.
In case of DNS hijack through router (DD-WRT or similar):
Do not use DNSmasq for hijack, but Firewall along with IPtables
iptables -t nat -A PREROUTING -s [AcessIP] -p tcp --dport 80 -j DNAT
--to-destination [weewxIP]:80 iptables -t nat -A POSTROUTING -j MASQUERADE
Best,
Xant
On July 31, 2019 at 10:08 AM, Ray Pfaff (ray.pf...@gmail.com) wrote:
I also have the Access and am using sniff to feed data to weewx. I think some
of the rain parameters get initialized the first time you get rain and the
other errors can be ignored. Mine works fine other than a _very_ annoying
problem wherein the Access just decides that it won't send any data to
WeatherUnderground at all. This is confirmed by doing a tcpdump and seeing
nothing coming out of the Access.
On Tuesday, July 30, 2019 at 3:41:05 PM UTC-4, Xant wrote:
Ok... I may have figured-out as the following:
1) 'rain' sensors in Acurite Atlas as acquired by Interceptor driver
identifiers: {}
raw data:
ID=KNYCLIFT14==myAcuRite=now=updateraw=1=35=30.05=0=78=75.1=3=291=4=55=67.8=0.06=0.06
raw packet: {'wind_speed': 3.0, 'barometer': 30.05, 'wind_gust': 4.0,
'dewpoint': 67.8, 'humidity_out': 78.0, 'uv': 0.0, 'rain': None, 'dateTime':
1564448985, 'temperature_out': 75.1, 'wind_dir': 291.0, 'rain_total': 0.06,
'wind_gust_dir': 55.0, 'usUnits': 1}
mapped packet: {'barometer': 30.05, 'dewpoint': 67.8, 'outHumidity': 78.0,
'UV': 0.0, 'rain': None, 'dateTime': 1564448985, 'windDir': 291.0, 'outTemp':
75.1, 'windSpeed': 3.0, 'windGust': 4.0, 'usUnits': 1, 'windGustDir': 55.0}
That is "dailyrainin", "rainin", "rain", "rain_total". Not exactly clear which
one is what, but may have info overlap.
2) "rainin" in Interceptor driver
Previous postings mention "rainin" error and not recognized, which was puzzling
some as "rainin" at Interceptor.py listed as 'IGNORED_LABELS'.
That gave a hint from Developers that "rainin" might be overlap info, and
should be ignored.
While "rainin" in IGNORED_LABELS section, was still generating error... and the
reason is the IGNORED_LABELS shows twice in Interceptor.py (one with "rainin",
the other without "rainin").
IGNORED_LABELS = ['realtime', 'rtfreq', 'action', 'ID', 'PASSWORD', 'dateutc',
'softwaretype']
IGNORED_LABELS = ['rainin', 'dewptf', 'realtime', 'rtfreq', 'action', 'ID',
'PASSWORD', 'dateutc', 'updateraw', 'sensor', 'mt', 'id', 'probe', 'check',
'water']
Once 'rainin' is added to the first IGNORED_LABEL instance, the msg error is
gone, while still may provide the correct Rain data correlation.
Best,
Xant
--
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/Po5gvYKpWB0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/15b3a1de-036d-4d8c-8d31-5c0c2ca6e219%40googlegroups.com
(
https://groups.google.com/d/msgid/weewx-user/15b3a1de-036d-4d8c-8d31-5c0c2ca6e219%40googlegroups.com?utm_medium=email_source=footer
).
[image: ]
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/f9b9b1c0-a6a0-49fd-b9c8-51fdeefdf38f%40missiveapp.com.
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
I also have the Access and am using sniff to feed data to weewx. I think
some of the rain parameters get initialized the first time you get rain and
the other errors can be ignored. Mine works fine other than a _very_
annoying problem wherein the Access just decides that it won't send any
data to WeatherUnderground at all. This is confirmed by doing a tcpdump
and seeing nothing coming out of the Access.
On Tuesday, July 30, 2019 at 3:41:05 PM UTC-4, Xant wrote:
>
>
> Ok... I may have figured-out as the following:
>
>
> 1) '*rain*' sensors in Acurite Atlas as acquired by Interceptor driver
>
> identifiers: {}
> raw data: ID=KNYCLIFT14=&
>
> softwaretype=myAcuRite=now=updateraw=1=35=30.05=0=78=75.1=3=291=4=55=67.8&
> *dailyrainin*=0.06&*rainin*=0.06
> raw packet: {'wind_speed': 3.0, 'barometer': 30.05, 'wind_gust': 4.0,
> 'dewpoint': 67.8, 'humidity_out': 78.0, 'uv': 0.0, '*rain*': None,
> 'dateTime': 1564448985, 'temperature_out': 75.1, 'wind_dir': 291.0, '
> *rain_total*': 0.06, 'wind_gust_dir': 55.0, 'usUnits': 1}
> mapped packet: {'barometer': 30.05, 'dewpoint': 67.8, 'outHumidity': 78.0,
> 'UV': 0.0, '*rain*': None, 'dateTime': 1564448985, 'windDir': 291.0,
> 'outTemp': 75.1, 'windSpeed': 3.0, 'windGust': 4.0, 'usUnits': 1,
> 'windGustDir': 55.0}
>
> That is "dailyrainin", "rainin", "rain", "rain_total". Not exactly clear
> which one is what, but may have info overlap.
>
> 2) "rainin" in Interceptor driver
> Previous postings mention "rainin" error and not recognized, which was
> puzzling some as "rainin" at Interceptor.py listed as 'IGNORED_LABELS'.
>
> That gave a hint from Developers that "rainin" might be overlap info, and
> should be ignored.
> While "rainin" in IGNORED_LABELS section, was still generating error...
> and the reason is the IGNORED_LABELS shows twice in Interceptor.py (one
> with "rainin", the other without "rainin").
>
> IGNORED_LABELS = ['realtime', 'rtfreq', 'action', 'ID',
> 'PASSWORD', 'dateutc', 'softwaretype']
>
> IGNORED_LABELS = ['rainin', 'dewptf', 'realtime', 'rtfreq',
> 'action', 'ID', 'PASSWORD', 'dateutc', 'updateraw', 'sensor', 'mt', 'id',
> 'probe', 'check', 'water']
>
> Once 'rainin' is added to the first IGNORED_LABEL instance, the msg error
> is gone, while still may provide the correct Rain data correlation.
>
> Best,
> Xant
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/15b3a1de-036d-4d8c-8d31-5c0c2ca6e219%40googlegroups.com.
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
Ok... I may have figured-out as the following:
1) '*rain*' sensors in Acurite Atlas as acquired by Interceptor driver
identifiers: {}
raw data: ID=KNYCLIFT14=&
softwaretype=myAcuRite=now=updateraw=1=35=30.05=0=78=75.1=3=291=4=55=67.8&
*dailyrainin*=0.06&*rainin*=0.06
raw packet: {'wind_speed': 3.0, 'barometer': 30.05, 'wind_gust': 4.0,
'dewpoint': 67.8, 'humidity_out': 78.0, 'uv': 0.0, '*rain*': None,
'dateTime': 1564448985, 'temperature_out': 75.1, 'wind_dir': 291.0, '
*rain_total*': 0.06, 'wind_gust_dir': 55.0, 'usUnits': 1}
mapped packet: {'barometer': 30.05, 'dewpoint': 67.8, 'outHumidity': 78.0,
'UV': 0.0, '*rain*': None, 'dateTime': 1564448985, 'windDir': 291.0,
'outTemp': 75.1, 'windSpeed': 3.0, 'windGust': 4.0, 'usUnits': 1,
'windGustDir': 55.0}
That is "dailyrainin", "rainin", "rain", "rain_total". Not exactly clear
which one is what, but may have info overlap.
2) "rainin" in Interceptor driver
Previous postings mention "rainin" error and not recognized, which was
puzzling some as "rainin" at Interceptor.py listed as 'IGNORED_LABELS'.
That gave a hint from Developers that "rainin" might be overlap info, and
should be ignored.
While "rainin" in IGNORED_LABELS section, was still generating error... and
the reason is the IGNORED_LABELS shows twice in Interceptor.py (one with
"rainin", the other without "rainin").
IGNORED_LABELS = ['realtime', 'rtfreq', 'action', 'ID', 'PASSWORD',
'dateutc', 'softwaretype']
IGNORED_LABELS = ['rainin', 'dewptf', 'realtime', 'rtfreq',
'action', 'ID', 'PASSWORD', 'dateutc', 'updateraw', 'sensor', 'mt', 'id',
'probe', 'check', 'water']
Once 'rainin' is added to the first IGNORED_LABEL instance, the msg error
is gone, while still may provide the correct Rain data correlation.
Best,
Xant
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/a542e366-3ef6-4532-a13e-83cc1fc04c1c%40googlegroups.com.
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
Chris
As I also have an Acurite Atlas, and "rainin" error as well, wondering if
you figured out the many variations of 'rain' (?!)
My identifiers:
identifiers: {}
raw data:
ID=KNYCLIFT14==myAcuRite=now=updateraw=1=35=30.05=0=78=75.1=3=291=4=55=67.8=0.06=0.06
raw packet: {'wind_speed': 3.0, 'barometer': 30.05, 'wind_gust': 4.0,
'dewpoint': 67.8, 'humidity_out': 78.0, 'uv': 0.0, 'rain': None,
'dateTime': 1564448985, 'temperature_out': 75.1, 'wind_dir': 291.0,
'rain_total': 0.06, 'wind_gust_dir': 55.0, 'usUnits': 1}
mapped packet: {'barometer': 30.05, 'dewpoint': 67.8, 'outHumidity': 78.0,
'UV': 0.0, 'rain': None, 'dateTime': 1564448985, 'windDir': 291.0,
'outTemp': 75.1, 'windSpeed': 3.0, 'windGust': 4.0, 'usUnits': 1,
'windGustDir': 55.0}
As the above, there is 'rainin', 'rain' (twice) and 'total_rain'.
Thanks,
Xant
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/e213bd81-4c39-4d69-ba12-fc9ac501c31a%40googlegroups.com.
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
One more thing, I looked back at my syslog once more after posting the
below and see three lines and thought I would post them for completeness in
case they help sort the rain issue out.
Jul 24 22:19:20 Weewx2 weewx[20428]: interceptor: MainThread: unrecognized
parameter rainin=0.00
Jul 24 22:19:20 Weewx2 weewx[20428]: interceptor: MainThread: skipping rain
measurement of 0.0: no last rain
Jul 24 22:19:23 Weewx2 weewx[20428]: interceptor: MainThread: unrecognized
parameter rainin=0.00
On Wednesday, July 24, 2019 at 7:14:40 PM UTC-6, Chris McLeod wrote:
>
> Hello,
>
> I just got my new Atlas set up and having not done my research found that
> getting it to work with SDR isn't a solved solution as yet (if I am missing
> something please tell me) so I decided to go the interceptor route. I have
> the Access setup up and sending, have the pfSense resolver routing it to my
> ubuntu box and I can see the data both with tcpdump and with interceptor.py
> running in debug mode. I have made two attempts at a [[sensor_map]] (one
> off of tcpdump and one off of interceptor.py in debug mode) but I am still
> not getting anything but an eroneous rain measurement into the database. I
> am guessing its the sensor_map that is borked but since I don't know for
> sure I will be putting much more data here in case someone can assist.
>
> Thanks in advance,
>
> Chris
>
> weewx 3.9.2 installed from apt repository for Ubuntu 18.04 LTS
>
> *tcpdump on Ubuntu box:*
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
> 17:01:03.669281 IP W550-0A43C9.little-to-no.org.3132 >
> rtupdate.wunderground.com.http: Flags [P.], seq 1:440, ack 1, win 8192,
> length 439: HTTP: GET
> /weatherstation/updateweatherstation.php?ID=@@@=*=myAcuRite=now=updateraw=1=35=30.13=1=19=92.6=2=53=3=90=44.3=0.00=0.00
>
> HTTP/1.1
>
> From this I built the following sensor_map
>
> [[sensor_map]]
> barometer = baromin
> UV = UV
> outHumidity = humidity
> outTemp = tempf
> windSpeed = windspeedmph
> windDir = winddir
> windGust = windgustmph
> windGustDir= windgustdir
> dewpoint = dewptf
> rain = rainin
>
> but got nothing but the humidity on to the index.html
>
> *interceptory.py in manually with device type acurite-bridge*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen
> --port=80
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
>
> *interceptor.py in manual mode with device type observer (found old post
> where someone mentioned they got it going with observer)*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen
> --port=80
> identifiers: {}
>
> *Interceptor.py debug output w/accurite-bridge setting*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen
> --port=80 --bug
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
> raw data:
> ID=KCOTHORN74=YdrxbW2U=myAcuRite=now=updateraw=1=35=30.20=1=53=74.7=8=34=16=37=56.4=0.08=0.00
> raw packet: {'winddir..': 34.0, 'dateTime': 1564016918, 'usUnits..': 1,
> 'pressure..': 30.2, 'temperature..': 74.7, 'dateTime..': 1564016918,
> 'windspeed..': 8.0, 'rainfall..': None, 'usUnits': 1, 'humidity..': 53.0}
> mapped packet: {'pressure': 30.2, 'usUnits': 1, 'dateTime': 1564016918}
>
> As you can see the items here are named quite a bit differently than in
> just the raw HTTP GET so I generated a new sensor_map
>
> [[sensor_map]]
> barometer = pressure
> outHumidity = humidity
> outTemp = temperature
> windSpeed = windspeed
> windDir = winddir
> dewpoint = dewptf
> rain = rainfall
> UV = UV
>
> And now I have lost the barometric pressure.
>
> So as you can see the data is getting sent from my access to wunderground,
> redirected by pfSense to my Ubuntu box. I had hoped that would be the hard
> part and getting it into the db would be easier but I am obviously doing
> something wrong. Any assistance appreciated. I will respond quicky for asks
> for any missing infomration.
>
>
>
>
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/58fac131-2a28-4ef9-9326-b16933979370%40googlegroups.com.
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
Hello,
Sorry for the wasted post, I have this sorted (for the most part).
Apparently I was a bit overdone getting the networking sorted and didn't
read the fine manual provided for interceptor so I missed there was a
wu-client device. Once that was set things work much, much better. The only
error I am getting in syslog is:
Jul 24 22:21:08 Weewx2 weewx[20428]: interceptor: MainThread: unrecognized
parameter *rainin=0.00*
I removed the sensor_map so I guess this is part of interceptor.py? Below
is representative of what I get when running interceptor.py in debug mode:
:~$ sudo PYTHONPATH=/usr/share/weewx python
/usr/share/weewx/user/interceptor.py --device=wu-client --mode=listen
--port=80 --debug
identifiers: {}
raw data:
ID=@@@==myAcuRite=now=updateraw=1=35=30.26=0=42=76.6=4=195=7=0=51.8&
*dailyrainin=0.00*&*rainin=0.00*
raw packet: {'wind_speed': 4.0, 'barometer': 30.26, 'wind_gust': 7.0,
'dewpoint': 51.8, 'humidity_out': 42.0, 'uv': 0.0, 'rain': None,
'dateTime':1564028339, 'temperature_out': 76.6, 'wind_dir': 195.0,
'rain_total': 0.0, 'wind_gust_dir': 0.0, 'usUnits': 1}
mapped packet: {'barometer': 30.26, 'dewpoint': 51.8, 'outHumidity': 42.0,
'UV': 0.0, *'rain': None*, 'dateTime': 1564028339, 'windDir': 195.0,
'outemp': 76.6, 'windSpeed': 4.0, 'windGust': 7.0, 'usUnits': 1,
'windGustDir': 0.0}
I see that I am getting dailyrain from the wu data and it is likely getting
mapped to rain, would it be better to map rainin to rain and let weewx
calculate my daily rain? Any assistance on this appreciated as rain
measurement is one of my primary wants from this setup.
Thanks,
Chris
On Wednesday, July 24, 2019 at 7:14:40 PM UTC-6, Chris McLeod wrote:
>
> Hello,
>
> I just got my new Atlas set up and having not done my research found that
> getting it to work with SDR isn't a solved solution as yet (if I am missing
> something please tell me) so I decided to go the interceptor route. I have
> the Access setup up and sending, have the pfSense resolver routing it to my
> ubuntu box and I can see the data both with tcpdump and with interceptor.py
> running in debug mode. I have made two attempts at a [[sensor_map]] (one
> off of tcpdump and one off of interceptor.py in debug mode) but I am still
> not getting anything but an eroneous rain measurement into the database. I
> am guessing its the sensor_map that is borked but since I don't know for
> sure I will be putting much more data here in case someone can assist.
>
> Thanks in advance,
>
> Chris
>
> weewx 3.9.2 installed from apt repository for Ubuntu 18.04 LTS
>
> *tcpdump on Ubuntu box:*
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
> 17:01:03.669281 IP W550-0A43C9.little-to-no.org.3132 >
> rtupdate.wunderground.com.http: Flags [P.], seq 1:440, ack 1, win 8192,
> length 439: HTTP: GET
> /weatherstation/updateweatherstation.php?ID=@@@=*=myAcuRite=now=updateraw=1=35=30.13=1=19=92.6=2=53=3=90=44.3=0.00=0.00
>
> HTTP/1.1
>
> From this I built the following sensor_map
>
> [[sensor_map]]
> barometer = baromin
> UV = UV
> outHumidity = humidity
> outTemp = tempf
> windSpeed = windspeedmph
> windDir = winddir
> windGust = windgustmph
> windGustDir= windgustdir
> dewpoint = dewptf
> rain = rainin
>
> but got nothing but the humidity on to the index.html
>
> *interceptory.py in manually with device type acurite-bridge*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen
> --port=80
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
>
> *interceptor.py in manual mode with device type observer (found old post
> where someone mentioned they got it going with observer)*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen
> --port=80
> identifiers: {}
>
> *Interceptor.py debug output w/accurite-bridge setting*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen
> --port=80 --bug
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
> raw data:
> ID=KCOTHORN74=YdrxbW2U=myAcuRite=now=updateraw=1=35=30.20=1=53=74.7=8=34=16=37=56.4=0.08=0.00
> raw packet: {'winddir..': 34.0, 'dateTime': 1564016918, 'usUnits..': 1,
> 'pressure..': 30.2, 'temperature..': 74.7, 'dateTime..': 1564016918,
> 'windspeed..': 8.0, 'rainfall..': None, 'usUnits': 1, 'humidity..': 53.0}
> mapped packet: {'pressure': 30.2, 'usUnits': 1, 'dateTime': 1564016918}
>
> As you can see the items here are named quite a bit differently than in
> just the raw HTTP GET so I generated a new sensor_map
>
> [[sensor_map]]
> barometer = pressure
> outHumidity = humidity
> outTemp = temperature
>
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
As always, too many hours already trying to make WeeWX on RasperryPi to connect to Acurite Access, at no result (1st try normal installation; 2nd try driver standalone; etc). Acurite Access has a Static DHCP through DD-WRT router. The following command, returns no result: PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=sniff --iface=eth0 --filter="src 192.168.1.135 and dst port 80" Understand there might be other 'strong' approaches (DNS hijack, direct eth0 connection, etc). Please, advice whats "next" and usually works for WeeWX Interceptor and Acurite Access. After much plus hours, I was able to DNS hijack "atlasapi.myacurite.com" (this is the "new" API/myacurite.com address) to RaspberryPi/WeeWX IP address through DD-WRT DNSmasq/DNS Forwarding... still, no luck and stuck. The above, was a posted of mine in the GitHub Interceptor blog, which Matthew was kind to reply and respond as the following (so ALL Acurite Access users to be aware): *weewx does work with the access, but the access must send data in wu format. configure the access to send wu data. ideally you would configure it to send to the computer running weewx (use dns hijacking for this). then configure interceptor to listen (not sniff), and it will simply receive the wu data.* *if you prefer to send to wu, then you must configure the interceptor to sniff the traffic (not listen).* *please post on the weewx user group for further help on this.* *i am sorry there is not yet a guide specifically for intercepter and access* Thanks Matthew for continue support and response. Some progress! (more to come) DD-WRT can do DNS forwarding as the following: Upload data to WU consider "https://weatherstation.wunderground.com/weatherstation; (ref: https://projects.raspberrypi.org/en/projects/uploading-weather-data-to-weather-underground/4) In DD-WRT: Setup>Forced DNS Redirection [On] Services>ServicesTab>DNSmasq>Additional DNSmasq Options address=/website/forwardIP , or in this case address=wunderground/Y.Y.Y.Y In RaspberryPi: PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py --device=wu-client --mode=listen --port=80 Finally some data packages. Now, trying with WeeWX and identifiers. Best, ZX -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/5993451e-d755-4db3-ae6c-b5d6e0837512%40googlegroups.com.
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
On Wednesday, July 24, 2019 at 9:14:40 PM UTC-4, Chris McLeod wrote:
>
> Hello,
>
> I just got my new Atlas set up and having not done my research found that
> getting it to work with SDR isn't a solved solution as yet (if I am missing
> something please tell me) so I decided to go the interceptor route. I have
> the Access setup up and sending, have the pfSense resolver routing it to my
> ubuntu box and I can see the data both with tcpdump and with interceptor.py
> running in debug mode. I have made two attempts at a [[sensor_map]] (one
> off of tcpdump and one off of interceptor.py in debug mode) but I am still
> not getting anything but an eroneous rain measurement into the database. I
> am guessing its the sensor_map that is borked but since I don't know for
> sure I will be putting much more data here in case someone can assist.
>
> Thanks in advance,
>
> Chris
>
> weewx 3.9.2 installed from apt repository for Ubuntu 18.04 LTS
>
> *tcpdump on Ubuntu box:*
>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
> 17:01:03.669281 IP W550-0A43C9.little-to-no.org.3132 >
> rtupdate.wunderground.com.http: Flags [P.], seq 1:440, ack 1, win 8192,
> length 439: HTTP: GET
> /weatherstation/updateweatherstation.php?ID=@@@=*=myAcuRite=now=updateraw=1=35=30.13=1=19=92.6=2=53=3=90=44.3=0.00=0.00
>
> HTTP/1.1
>
> From this I built the following sensor_map
>
> [[sensor_map]]
> barometer = baromin
> UV = UV
> outHumidity = humidity
> outTemp = tempf
> windSpeed = windspeedmph
> windDir = winddir
> windGust = windgustmph
> windGustDir= windgustdir
> dewpoint = dewptf
> rain = rainin
>
> but got nothing but the humidity on to the index.html
>
> *interceptory.py in manually with device type acurite-bridge*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen
> --port=80
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
>
> *interceptor.py in manual mode with device type observer (found old post
> where someone mentioned they got it going with observer)*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=observer --mode=listen
> --port=80
> identifiers: {}
>
> *Interceptor.py debug output w/accurite-bridge setting*
>
> cmcleod@Weewx2:~$ sudo PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen
> --port=80 --bug
> identifiers: {'bridge_id': None, 'sensor_type': None, 'sensor_id': None}
> raw data:
> ID=KCOTHORN74=YdrxbW2U=myAcuRite=now=updateraw=1=35=30.20=1=53=74.7=8=34=16=37=56.4=0.08=0.00
> raw packet: {'winddir..': 34.0, 'dateTime': 1564016918, 'usUnits..': 1,
> 'pressure..': 30.2, 'temperature..': 74.7, 'dateTime..': 1564016918,
> 'windspeed..': 8.0, 'rainfall..': None, 'usUnits': 1, 'humidity..': 53.0}
> mapped packet: {'pressure': 30.2, 'usUnits': 1, 'dateTime': 1564016918}
>
> As you can see the items here are named quite a bit differently than in
> just the raw HTTP GET so I generated a new sensor_map
>
> [[sensor_map]]
> barometer = pressure
> outHumidity = humidity
> outTemp = temperature
> windSpeed = windspeed
> windDir = winddir
> dewpoint = dewptf
> rain = rainfall
> UV = UV
>
> And now I have lost the barometric pressure.
>
> So as you can see the data is getting sent from my access to wunderground,
> redirected by pfSense to my Ubuntu box. I had hoped that would be the hard
> part and getting it into the db would be easier but I am obviously doing
> something wrong. Any assistance appreciated. I will respond quicky for asks
> for any missing infomration.
>
>
>
>
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/4cb8264a-5d4a-4a21-a0f6-29c1f3bf1faa%40googlegroups.com.
[weewx-user] Re: Acurite Atlas/Access with interceptor and wunderground
As always, too many hours already trying to make WeeWX on RasperryPi to connect to Acurite Access, at no result (1st try normal installation; 2nd try driver standalone; etc). Acurite Access has a Static DHCP through DD-WRT router. The following command, returns no result: PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=sniff --iface=eth0 --filter="src 192.168.1.135 and dst port 80" Understand there might be other 'strong' approaches (DNS hijack, direct eth0 connection, etc). Please, advice whats "next" and usually works for WeeWX Interceptor and Acurite Access. After much plus hours, I was able to DNS hijack "atlasapi.myacurite.com" (this is the "new" API/myacurite.com address) to RaspberryPi/WeeWX IP address through DD-WRT DNSmasq/DNS Forwarding... still, no luck and stuck. The above, was a posted of mine in the GitHub Interceptor blog, which Matthew was kind to reply and respond as the following (so ALL Acurite Access users to be aware): *weewx does work with the access, but the access must send data in wu format. configure the access to send wu data. ideally you would configure it to send to the computer running weewx (use dns hijacking for this). then configure interceptor to listen (not sniff), and it will simply receive the wu data.* *if you prefer to send to wu, then you must configure the interceptor to sniff the traffic (not listen).* *please post on the weewx user group for further help on this.* *i am sorry there is not yet a guide specifically for intercepter and access* Thanks Matthew for continue support and response. If you place the Access IP in web-browser, it provides basic info and current Acurite server, which for the Atlas current server seems to be "atlasapi.myacurite.com". In my router with DD-WRT I was able to DNS forward "atlastapi.myacurite.com" to RaspberryPi/WeeWX IP. Is this the same approach for UW through DNS hijacking? If so, what UW domain for DNS forward? Thanks, ZX -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9c4d1218-1949-4b75-993d-a17768676578%40googlegroups.com.
