You will find them here in units.py <https://github.com/weewx/weewx/blob/master/bin/weewx/units.py#L85>. WeeWX takes care of those fields that are in the default schema <https://github.com/weewx/weewx/blob/master/bin/schemas/wview_extended.py>, anything else needs the user to take care of it. WeeWX allows you to access fields in the current archive record (accessed through the $current tag) that have not been saved to your database. If you want to access aggregates (eg $day.xxxx.max) then the obs concerned (xxxx) must be in your database schema and xxxx saved to your database. I was likely wrong in my previous post, extraTemp8 and soilMoist5 are likely not in your schema/archive, the interceptor driver will have added extraTemp8 and soilMoist5 to loop packets and this will have caused WeeWX to include them in the archive record but they will were likely not saved to your archive. So $current.extraTemp8 will work but I expect $day.extraTemp8.max will not.
If you want to add extraTemp8 and soilMoist5 to your database so that you can view the aggregates you will need to refer to the section Adding a new type to the database <http://weewx.com/docs/customizing.htm#add_archive_type> in the Customization Guide. Gary On Thursday, 14 May 2020 11:34:37 UTC+10, John Hill wrote: > > Bingo. > > I never would have figured that out on my own. Thanks Gary, > > Just out of curiosity, where are all the other group associations stored > (from import weewx.units)? I'm curious why/how extraTemp8 wasn't set to be > the same as extraTemp1-7. > -- 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/77845003-8d79-4bd8-bd43-94742e06e201%40googlegroups.com.
