Thanks for the input! My impression was that I was attempting to perform 
the latter by updating my pihole's /etc/hosts file. I added records to 
resolve both `time.windows.com` and `rtupdate.wunderground.com` to the ip 
running weewx (those domains are the domains regularly being requested by 
the WS-2902A, according to pihole).

Is there a better way to to do this?

That being said, I like the idea of Ecowitt GW1000 - I'll have to explore 
that route, as well. Thanks again!

On Thursday, January 23, 2020 at 10:20:32 AM UTC-6, galfert wrote:
>
> You need to do one of two things...
>
> - put the WS-2902A console behind the WeeWx system so that it can see the 
> WU packets and actually intercept them. This is done by creating a separate 
> network hotspot for the WS-2902A to connect to. 
>
> - or you need d to do DNS poisoning so that the WS-2902A sends the data to 
> the WeeWx system instead of to WU servers. The WS-2902A will think it is 
> sending data to WU but the DNS resolution will be changed so that it 
> resolves to the WeeWx system's IP address instead.
>
> Yet another alternative is to forget using the WS-2902A console and 
> instead use the Ecowitt GW1000 to pick up your sensors and then the GW1000 
> can be configured to send the data to the WeeWx system using its 
> "Customized" server settings. This is an option that the WS-2902A console 
> device does not have hence is a reason adding the GW1000 is appealing. The 
> other benefit to using the GW1000 is that you'll be able to add more 
> sensors that the WS-2902A can't pick up (extra temp/hum, soil moisture, 
> lightning, PM2.5, and more). You can then use the GW1000 with Ecowitt.net 
> protocol instead of WU protocol to send these extra sensors to WeeWx.
>
>

-- 
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/8ffd0e40-4a01-47ef-8fc4-3549da81cd25%40googlegroups.com.

Reply via email to