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):
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):
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
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:
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':
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
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
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:
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
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:
10 matches
Mail list logo
