Re: [weewx-user] Davis AirLink and PurpleAir

2020-09-23 Thread Andy 

I used these instruction  and 
now I have a sensor here 
. Used the 
SDS011 sensor for this one. Couple of the Plantower sensors on the way. This 
 and this 
.

Andy



On Tuesday, September 22, 2020 at 12:25:32 PM UTC-7 vince wrote:

> On Tuesday, September 22, 2020 at 11:05:10 AM UTC-7, John Kline wrote:
>
>> In my logs, I see that it is a redirect that fails.  It seems 
>> purpleair-38fe.lan cannot be resolved without an internet connection:
>>
>>
>>
> I have a local pihole box with a hosts file in it that is my LAN primary 
> resolver, so I added the alias there to make it resolve without needing 
> Internet access.
>
> Can't stop a determined network engineer with too many computers on the 
> LAN :-)
>
>

-- 
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/aff90d60-488d-4fac-8f01-e0e9ed262414n%40googlegroups.com.

Re: [weewx-user] Davis AirLink and PurpleAir

2020-09-22 Thread vince 
On Tuesday, September 22, 2020 at 11:05:10 AM UTC-7, John Kline wrote:

> In my logs, I see that it is a redirect that fails.  It seems 
> purpleair-38fe.lan cannot be resolved without an internet connection:
>
>
>
I have a local pihole box with a hosts file in it that is my LAN primary 
resolver, so I added the alias there to make it resolve without needing 
Internet access.

Can't stop a determined network engineer with too many computers on the LAN 
:-)

-- 
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/0c931015-9ddd-45f9-a5f4-a7fe20a16307o%40googlegroups.com.

Re: [weewx-user] Davis AirLink and PurpleAir

2020-09-22 Thread John Kline 
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(': 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.2

Re: [weewx-user] Davis AirLink and PurpleAir

2020-09-22 Thread vince 
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- 
where  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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d0a059c8-b926-4019-9e25-0b2876119bf9o%40googlegroups.com.

Re: [weewx-user] Davis AirLink and PurpleAir

2020-09-22 Thread Tom Keffer 
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.

(I'm looking at you, WeatherFlow.)

-tk

On Tue, Sep 22, 2020 at 7:08 AM John Kline  wrote:

> The PA sensors do not need an internet connection. Just query the local
> endpoint 'json'.
>
>
> In fact I do that.  Unplug your internet and try it.  It doesn’t work for
> me.
>
> On Sep 22, 2020, at 3:37 AM, Tom Keffer  wrote:
>
> 
> That's awesome! I haven't seen a comparison anywhere else.
>
> The PA sensors do not need an internet connection. Just query the local
> endpoint 'json'. For example, mine is at http://192.168.1.101/json
>
> -tk
>
> On Mon, Sep 21, 2020 at 9:03 PM jo...@johnkline.com 
> wrote:
>
>> I’ve been playing with the new Davis AirLink.  I have one WeeWX instance
>> running with it.
>>
>> Unlike the PurpleAir, which is slow answering requests and needs an
>> internet connection to respond, the AirLink is fast (the doc claims it can
>> respond to 3 queries per second) and presumably will still respond when the
>> internet is down.
>>
>> On the downside, unlike the performance of the PurpleAir, which is pretty
>> well understood (e.g., during these poor air quality days due to wood
>> smoke, the LRAPA correction can be used to have some confidence in the
>> numbers), I’m not aware of any studies with the AirLink.  As such, it’s
>> difficult to have any confidence in the AirLinks numbers.  Having said
>> that, I thought I would plot AirLink concentrations vs. PurpleAir (A and B
>> sensor) concentrations.
>>
>> At present, the AirLink is reporting similar PM2.5 to the PurpleAir (see
>> below).  It would be nice to know if the AirLink continued to closely track
>> PM2.5 at much higher concentrations.  I hope to not find out (it’s been
>> pretty good here in the SF Bay Area for the last few days), but I’ll reply
>> here with a graph if the concentrations get real bad again.
>>
>> 
>>
>>
>>
>>
>>
>> --
>> 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/b6efea69-df87-4b96-b366-bd8df2981a59n%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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEB9%3DZ-rcOPWf9F-q_Wx_hijmdfOTc0%3D%2BctTXUpZHyK%2B5w%40mail.gmail.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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/0F4D4571-6A61-44E6-9D26-858A87380026%40johnkline.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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECe9PhFigKr5w5%3DZOAAQG-qQ4ekmFa%2BWaB4KwYBr2UTqQ%40mail.gmail.com.

Re: [weewx-user] Davis AirLink and PurpleAir

2020-09-22 Thread John Kline 
> The PA sensors do not need an internet connection. Just query the local 
> endpoint 'json'.

In fact I do that.  Unplug your internet and try it.  It doesn’t work for me.

> On Sep 22, 2020, at 3:37 AM, Tom Keffer  wrote:
> 
> 
> That's awesome! I haven't seen a comparison anywhere else. 
> 
> The PA sensors do not need an internet connection. Just query the local 
> endpoint 'json'. For example, mine is at http://192.168.1.101/json
> 
> -tk
> 
>> On Mon, Sep 21, 2020 at 9:03 PM jo...@johnkline.com  
>> wrote:
>> I’ve been playing with the new Davis AirLink.  I have one WeeWX instance 
>> running with it.
>> 
>> Unlike the PurpleAir, which is slow answering requests and needs an internet 
>> connection to respond, the AirLink is fast (the doc claims it can respond to 
>> 3 queries per second) and presumably will still respond when the internet is 
>> down.
>> 
>> On the downside, unlike the performance of the PurpleAir, which is pretty 
>> well understood (e.g., during these poor air quality days due to wood smoke, 
>> the LRAPA correction can be used to have some confidence in the numbers), 
>> I’m not aware of any studies with the AirLink.  As such, it’s difficult to 
>> have any confidence in the AirLinks numbers.  Having said that, I thought I 
>> would plot AirLink concentrations vs. PurpleAir (A and B sensor) 
>> concentrations.
>> 
>> At present, the AirLink is reporting similar PM2.5 to the PurpleAir (see 
>> below).  It would be nice to know if the AirLink continued to closely track 
>> PM2.5 at much higher concentrations.  I hope to not find out (it’s been 
>> pretty good here in the SF Bay Area for the last few days), but I’ll reply 
>> here with a graph if the concentrations get real bad again.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> 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/b6efea69-df87-4b96-b366-bd8df2981a59n%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 weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEB9%3DZ-rcOPWf9F-q_Wx_hijmdfOTc0%3D%2BctTXUpZHyK%2B5w%40mail.gmail.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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0F4D4571-6A61-44E6-9D26-858A87380026%40johnkline.com.