Well, at least Vince has seen this behavior when the internet is down; but has
a workaround.
I have tried it with dns names:
purple-air.amarillo.johnkline.com
purple-air-indoor.amarillo.johnkline.com
Both of these resolve without internet calls via my local dns servers.
I have also tried it with the corresponding IP addresses.
In all cases, I get no response when I lose my internet connection.
When I look at packet capture, I see it chatting with amazon’s servers. See
packet capture below. Although this doesn’t necessarily mean it won’t respond
without being able to chat with those servers.
In my logs, I see that it is a redirect that fails. It seems
purpleair-38fe.lan cannot be resolved without an internet connection:
Aug 13 01:35:23 ella purple-proxy[560]:
HTTPConnectionPool(host='purple-air-38fe.lan', port=80): Max retries exceeded
with url: /redirect (Caused by
NewConnectionError('<urllib3.connection.HTTPConnection object at
0x7f1f0779a9b0>: Failed to establish a new connection: [Errno -3] Temporary
failure in name resolution')): Retrying request.
This has been annoying. WeeWX and everything associated with it continue to
run happily without an internet connection–except the purple airs.
10:35:18.286754 IP 54.186.213.21.443 > 192.168.168.197.59220: tcp 69
10:35:18.286768 IP 54.186.213.21.443 > 192.168.168.197.59220: tcp 0
10:35:18.288759 IP 192.168.168.197.59220 > 54.186.213.21.443: tcp 0
10:36:09.171449 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 0
10:36:09.188699 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.190451 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 0
10:36:09.193986 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 98
10:36:09.224137 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.249017 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 1430
10:36:09.249233 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 1127
10:36:09.253882 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 0
10:36:09.369752 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 267
10:36:09.402907 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.404920 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 75
10:36:09.426878 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.450973 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 75
10:36:09.458057 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 229
10:36:09.474423 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 565
10:36:09.490082 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 565
10:36:09.496904 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.497845 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.506197 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 565
10:36:09.515096 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 357
10:36:09.515230 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 53
10:36:09.532567 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.533653 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.542607 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.542620 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.630763 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 293
10:36:09.634332 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 0
10:36:09.940649 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 0
10:36:09.940782 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:09.957889 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.976918 IP 142.250.68.83.443 > 192.168.168.197.54978: tcp 0
10:36:09.978360 IP 192.168.168.197.54978 > 142.250.68.83.443: tcp 0
10:36:10.011673 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 0
10:36:10.014025 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:10.017342 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 99
10:36:10.097479 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 0
10:36:10.098132 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 1460
10:36:10.098451 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 1460
10:36:10.098780 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 1275
10:36:10.101829 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:10.102725 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:10.113491 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:10.228904 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 267
10:36:10.350375 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 0
10:36:10.352205 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 91
10:36:10.429587 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 0
10:36:10.429838 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 91
10:36:10.440405 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 245
10:36:10.554365 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 709
10:36:10.559906 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:11.340712 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:11.341133 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:11.423391 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 0
10:36:11.423615 IP 54.210.227.170.443 > 192.168.168.197.50712: tcp 0
10:36:11.425221 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:11.425905 IP 192.168.168.197.50712 > 54.210.227.170.443: tcp 0
10:36:11.434655 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 99
10:36:11.521890 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 0
10:36:11.522318 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 1460
10:36:11.522467 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 1460
10:36:11.522586 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 1275
10:36:11.525821 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:11.532375 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:11.542972 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:11.657044 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 267
10:36:11.786345 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 0
10:36:11.788272 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 91
10:36:11.865904 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 0
10:36:11.866149 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 91
10:36:11.876097 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 261
10:36:12.006307 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 709
10:36:12.006736 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 69
10:36:12.008570 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:12.012728 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:12.722424 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:12.722770 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 0
10:36:12.799833 IP 54.210.227.170.443 > 192.168.168.197.52666: tcp 0
10:36:12.800053 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 0
10:36:12.801704 IP 192.168.168.197.52666 > 54.210.227.170.443: tcp 0
10:36:12.802389 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 0
10:36:12.805823 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 99
10:36:12.891171 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 0
10:36:12.891816 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 1460
10:36:12.892137 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 1460
10:36:12.892407 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 1275
10:36:12.894455 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 0
10:36:12.907127 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 0
10:36:12.921945 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 0
10:36:13.021514 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 267
10:36:13.142410 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 0
10:36:13.144378 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 91
10:36:13.213169 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 0
10:36:13.213182 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 91
10:36:13.223062 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 245
10:36:13.342325 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 0
10:36:13.346481 IP 54.210.227.170.443 > 192.168.168.197.49639: tcp 709
10:36:13.352301 IP 192.168.168.197.49639 > 54.210.227.170.443: tcp 0
> On Sep 22, 2020, at 9:23 AM, vince <[email protected]> wrote:
>
>
>> On Tuesday, September 22, 2020 at 8:08:02 AM UTC-7, Tom Keffer wrote:
>> Just tried it, and it worked for me. It would a truly dumb design that
>> depended on an internet connection to respond to a local query.
>>
>>
>
> One thing I did find experimentally is that if you use hostnames, don't use
> 'purpleair'. Use their desired hostname which seems to be purpleair-NNNN
> where NNNN is the last few characters of the MAC address. In my case it
> would be purpleair-d32a
>
> If you use the longer hostname, the box responds if your Internet is down.
> Odd but I found it true here.
> --
> 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/d0a059c8-b926-4019-9e25-0b2876119bf9o%40googlegroups.com.
--
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/4140E4F2-4D75-4D84-94B1-911BA5FA2F62%40johnkline.com.
