On Thursday, June 20, 2019 at 11:20:52 AM UTC-4, BillLaRiv wrote: > > I am new to this forum so be gentle. I purchased an Acurite Atlas with > Access hub thinking I would easily connect up to Weewx using dns changes on > my lan. I quickly found out "Not so fast my friend". I made my changes in > dns and ran tcpdump listening on port 80 on the weewx server (Pi). No > traffic. hrmm. So I bounced around and finally did tcpdump on port 443. > There it was, s sa a to myacurite.com on port 443. Access Hub is the new > white cylinder running firmware 224. I have yet to see data get entered in > weewx on my local network. Any ideas would be greatly appreciated. >
are you successfully sending data to weather underground? if so, then you must *sniff* traffic bound for port 80. if not, then you must configure the access to send data to weather underground, configure dns spoofing so that the computer running weewx receives the http connections bound for wu, then *listen* for traffic on port 80. to diagnose, run the interceptor driver directly, and use the --debug option if you need more info. (details are in the interceptor readme - or ask here if you're not sure) you cannot do anything with encrypted traffic unless you figure out how to decrypt it. if you do that, please let us know - lots of people would like to know how to do that! it would be nice if we could decode the traffic to the acurite servers, since that contains all sensor data, not just the limited set of sensor data sent to wu. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/3452c265-e849-4211-94a7-5f722226eddb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
