A couple of points that might help: - for an observation to be recorded in the database two fundamental conditions must be met:
1. the field/observation concerned must exist in the archive records generated by WeeWX (this can be checked by running WeeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly> and observing the loop packets (LOOP: lines) and archive records (REC: lines) that appear on the console 2. the field/observation must appear in the database archive table schema, for a default clean install this will be the wview_extended schema <https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py>, if you are upgrading a old installation or have previously modified your schema your schema may be different - as a rule of thumb drivers do not modify the database schema, programatically it could be done but I would suggest that it would add significant complexity to a driver and its operation would be fraught with danger, off the top of my head I cannot think of a single driver that modifies the database schema - I would recommend against trying to read through the driver to understand the fields used by the driver, the Ecowitt gateway driver uses a complex series of mappings to produce its output to WeeWX. The wiki contains a comprehensive table of available fields <https://github.com/gjr80/weewx-gw1000/wiki/Field-map#tabulated-default-field-map> showing the default field mapping that should more than suffice. The Ecowitt gateway driver wiki is publicly editable, if there is a shortfall or incorrect information feel free to make appropriate changes. -- 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/22536b30-3f4a-4710-9629-44c8fe258b14n%40googlegroups.com.
