Hi Gary,

Thanks a lot for that detailed reply. That cleared up several things for me.


On Monday, April 8, 2019 at 10:14:51 PM UTC-5, gjr80 wrote:
>
> Hi,
>
> Simple answer to your question re a list of sensors is 'any sensor for 
> which there is a WeeWX driver', bit of a circular answer and probably not 
> much help if you are setting out to write a driver. Slightly different 
> answer regarding units. WeeWX natively supports observations in a bunch of 
> units. Probably the most readable 'list' of supported units is at the Units 
> appendix <http://weewx.com/docs/customizing.htm#units> to the Customization 
> Guide <http://weewx.com/docs/customizing.htm>. If you are intending to 
> write a driver you will be diving into some python code so you might want 
> to have a look at the file bin/weewx/units.py 
> <https://github.com/weewx/weewx/blob/master/bin/weewx/units.py>, there 
> you will find most of the classes and methods used in by the WeeWX system.
>
> One of the strengths of WeeWX is the ability to extend its capabilities. 
> In terms of units it is a simple matter to extend the WeeWX unit system to 
> support additional units, for example I have extended WeeWX to support 
> various additional units associated with my solar PV system. If you need to 
> go down this path have a read of Customizing units and unit groups 
> <http://weewx.com/docs/customizing.htm#customizing_units> in the 
> Customization Guide. One key point to remember in dealing with units is 
> when you are adding an obs to an existing record/packet make sure the units 
> of the obs you are adding is consistent with the units used in that 
> record/packet. Frequently we see services and drivers that don't do any 
> unit checking and whilst they might work for a given user with given 
> hardware in a given country, the service/driver will frequently fail when 
> used with different hardware or in a different country (eg temperature obs 
> in F are added to a record/packet where temperatures are in C).
>
> And of course, if you are writing as driver make sure you read the Porting 
> to new hardware section <http://weewx.com/docs/customizing.htm#porting>, 
> again in the Customization Guide.
>
> Gary
>
> On Monday, 8 April 2019 10:45:23 UTC+10, Andrew B wrote:
>>
>> Hi All,
>>
>> I'm looking at making a driver for Lufft hardware over the next month or 
>> so. I can't seem to find a complete list of sensors that WeeWx supports and 
>> what unit each sensor expects the data to be.
>>
>> Can someone point me in the right direction?
>>
>

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to