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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/6d13107e-b74b-4c74-a2f4-adb042610e62%40googlegroups.com.
