Thanks Matthew, I understand now. I also did some reading of the 'customization' section in the wiki and it ties together nicely with what you have posted. So my next step is to setup the database, load all of my archive data and then update the driver to match the schema. Craig
On Wednesday, September 13, 2023 at 11:07:28 PM UTC+12 matthew wall wrote: > On Wednesday, September 13, 2023 at 6:51:17 AM UTC-4 [email protected] > wrote: > > Where can I find the list of observation types? > > > within the driver code, use names that match whatever the hardware uses. > then you can map those onto the weewx observation types when you generate a > LOOP or ARCHIVE dict. for example, the hardware documentation might use > 'inside_temperature', but the weewx equivalent is 'inTemp'. > > the weewx observation types are defined by the database schema. > 'wview_extended' is the default schema, but weewx also ships with the > legacy 'wview' and 'wview_small' schemas. > > https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py > > you can see what other drivers have done by browsing the 'Station data' > section for each driver in the hardware guide: > > http://weewx.com/docs/hardware.htm > > for power/solar/battery monitoring, or hardware that emits observations > that are not easily mapped to the weather-based schemas, it is typical to > ship a bespoke schema with the driver. > > > -- 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/ed0abb3f-cbdd-40ab-a890-de10b9f22d35n%40googlegroups.com.
