Hello Wes, It seems you're missing some basic information on writing a driver. Be sure to review the docs at http://www.weewx.com/docs/customizing.htm#porting (same link Tom just sent). Scroll down to the *Implement a Driver* section, then look for the *Required Keys* table. You need to always include the usUnits field where you specify the units for the LOOP packet. So if your hardware temperature for outTemp natively returns in celcius, then you need to set usUnit to METRIC or METRICWX depending on what other observations are also included.
Note that there's no requirement to have all observations in each LOOP packet. You can return LOOP packets based on the frequency of the observations, usUnit type or other logical grouping. Hope this helps, -Bill On Wednesday, June 3, 2020 at 2:04:47 PM UTC-4, Wes Witt wrote: > > thanks to both of you for the responses. > > it seems that any of the database fields can be included in loop packets > -- perfect. > > @tom my weather station is a custom design so i have written my own driver > that emits loop packets. my question about expected values in the loop > packets can be rephrased more specifically. for outtemp packet values it > seems that this is expected to be fahrenheit -- is this documented > somewhere or can i configure this field to be fahrenheitor celcius?? > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/8e9d67af-c144-44c1-a122-302c50683f8f%40googlegroups.com.
