Maybe worth mentioning I've been using weewx on Linux with Acurite 01036 for ~7years. This is a newer, more recent setup...
Acurite Atlas with an Access bridge: It's been sending data to myacurite.com (and wunderground) for some time now. However repeated attempts to get it working with weewx RTL/SDR, and more recently, Interceptor, have failed. I just completed a successful experiment with Acuparse. My setup was entirely defaults. I only: 1) changed Server Name on the Acurite Access device https://imgur.com/a/7hptaIr 2) provided Acuparse with the Access MAC/Device ID 3) provided Acuparse with Station ID / Sensor ID. I would prefer to use weewx with the Atlas. I've read through https://github.com/matthewwall/weewx-interceptor as well as a few posts via search however numerous attempts have been unsuccessful. Here the Access is hostname atlas.foobar.com (.98) and weewx (.99) is running on acuparse.foobar.com There is no firewall between them, full open access. Yes, acuparse is disabled for these tests. What I see when running weewx and tcpdump (atlas.foobar.com = 192.168.1.98). This tcpdump is done on weewx host acuparse.foobar.com (192.168.1.99). # tcpdump -i eth1 src 192.168.1.98 11:18:17.846452 IP atlas.foobar.com.5678 > acuparse.foobar.com.https: Flags [S], seq 3747456072, win 8192, options [mss 1460], length 0 11:18:17.846480 IP acuparse.foobar.com.https > atlas.foobar.com.5678: Flags [R.], seq 217488705, ack 2355357015, win 0, length 0 11:18:17.902067 IP atlas.foobar.com.5678 > acuparse.foobar.com.https: Flags [S], seq 3748847508, win 8192, options [mss 1460], length 0 11:18:17.902097 IP acuparse.foobar.com.https > atlas.foobar.com.5678: Flags [R.], seq 217488705, ack 2356748451, win 0, length 0 11:18:17.957792 IP atlas.foobar.com.5678 > acuparse.foobar.com.https: Flags [S], seq 3750240717, win 8192, options [mss 1460], length 0 11:18:17.957818 IP acuparse.foobar.com.https > atlas.foobar.com.5678: Flags [R.], seq 217488705, ack 2358141660, win 0, length 0 Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb' Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.manager: Starting backfill of daily summaries Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.manager: Daily summaries up to date Nov 18 11:17:03 acuparse weewx[68764] INFO weewx.engine: Starting main packet loop. Nov 18 11:17:13 acuparse weewx[68764] DEBUG user.interceptor: empty queue This tells me data is being sent from Access to weewx via port 443 but weewx isn't seeing it (IS THAT CORRECT?). weewx config is all defaults and interceptor is simply: [Interceptor] driver = user.interceptor device_type = acurite-bridge Also, this provides no output with port as 80 or 443: PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=listen --port=80 --debug Why does Interceptor doc not mention anything about 443/ssl/tls? Given the ease and success of Acuparse I was expecting to find an easier path to move this to weewx. Can you please let me know what is correct/incorrect about this setup and any good/bad assumptions I've made? I'd be happy to provide additional details! -- 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/14019777-9e46-4711-91cf-7b4340a0baa2n%40googlegroups.com.
