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.
