I have just created a master branch and committed v1.00 to GitHub:
Please recycle the electrons that make up previous versions responsibly, per local laws.
The readme file explains the sensor_map feature and configuration. Without a proper sensor_map in weewx.conf, this driver will not log ANY data! The naming syntax was borrowed from Matthew Wall’s weewx-SDR driver. I enjoyed the hours that I spent writing the readme file to explain everything, and hope that you enjoy reading it just as much when setting up the new/final version.
Before you curse me out for the added complexity of the sensor_map feature, let me explain the rationale. I have an Air unit in my basement, logging the temperature/humidity into weewx as indoor sensors to watch the furnace for failure. I also have an Air located outdoors, logging temperature/humidity/barometer/lightning as outdoor sensors for weather purposes. Using the sensor_map feature, I can decide which sensor’s data gets stored in weewx…with granularity down to the individual sensor. In addition, I can choose to ignore certain sensors, like the lightning sensor in the basement. Not sold yet? Rumor has it that making a $7.95 Arduino NodeMCU or ESP8266 send UDP packets for things like water levels and soil moisture is a trivial thing, and it would probably take less than a dozen new lines of code in this driver to bring all kinds of additional sensors into weewx beyond what are available in the Air (and soon the Sky) today.
I have been running this driver in a test weewx instance as it was developed. Other than the socket timeout dump when my Hub was doing an upgrade (now handled properly), it has been running for a week in final form without any observed issues.
My usual disclaimer applies. I am not a programmer by trade, and did not sleep in a Holiday Inn Express last night. Please let me know via GitHub or here if you find any bugs. Also, if someone else can try installing it and let me know if it works for them, I’d be extremely grateful…