i'm leaning toward a generic weewx-wu driver that captures (sniff or listen) tcp/ip packets that are wu protocol (http GET). that driver would work with acurite bridge, fine offset observer, and any other hardware that sends directly to weather underground.
there is already a working implementation in the weewx-interceptor driver. we would push the generic tcp/ip components into the weewx 'driver' module, then distribute a simple weewx-wu driver. the weewx-sdr driver would be much simpler if it only had to recognize the json output. i'm happy to make that change sooner than later, and push the pressure for consistency and versioning down onto the rtl_433 development. that could also facilitate the use of sdr dongle for capturing davis signals, not just 433Mhz signals. but i still don't have a clear vision of the "one json-speaking driver to rule them all" is it a weewx-json driver that accepts any json input? then that driver has plugins/modules/api to feed it via tcp/ip (e.g., for the weatherflow broadcasts) or pipe (e.g., for rtl_433 or rtldavis)? or do we just push the json-handling stuff into a simple class or two in the weewx drivers module. then implement weewx-weatherflow driver that listens for udp broadcasts (using tcp/ip components in weewx.drivers) and handles them (using json components in weewx.drivers). and we implement weewx-sdr that is just a simplification of the current weewx-sdr. or something else?
