Hi, WeeWX is doing exactly what it should/has been told to do. Inside dewpoint is not provided by Davis VP2 hardware (have a look at the loop, loop2 and rev A/rev B archive records in the Davis Serial Communications Reference (about page 30 in https://www.davisnet.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf). StdWXCalculate has been told to 'prefer' gettting inside dewpoint from hardware. Since the hardware doesn't provide inside dewpoint weeWX calculates it instead (if it was set to hardware_only the weeWX would not calculate it) and adds it to loop packets and archive records. That explains why you are seeing inDewpoint.
As Vince said weeWX defaults to using the wview schema and the wview schema does not include inDewpoint, so weeWX does not save inDewpoint to the database (by default weeWX will save to the database any fields in an archive record that are also defined in the db schema you are using). In terms of reports, something like $current.inDewpoint will work because reports can use any field in the current archive record without having saved it to the database. However, any aggregates eg $day.inDewpoint.max used in a report or plotting inDewpoint will not work as these require inDewpoint to be saved to the database. There are a number of ways to add inDewpiunt to the database, you can extend the current schema (as Vince points out) or you could add a new database. The former will be easier. This link might help http://weewx.com/docs/customizing.htm#archive_database Hope this explains what is going on. Gary -- 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. For more options, visit https://groups.google.com/d/optout.
