Yes, I've read the guides back and forth a number of times, but it's funny in that these certain details, while there, aren't so obvious until they are pointed out. I should have this hooked up to weewx shortly. I can make loop records now that look right. Now, on to bolting this stuff into data generator and fire up weewx with the hacked up driver. Thx, Chris
On Thursday, February 16, 2017 at 7:45:13 PM UTC-8, mwall wrote: > > > > On Thursday, February 16, 2017 at 10:36:10 PM UTC-5, [email protected] > wrote: >> >> OK, I think I've got it. One more thing. Is there a point to including >> pairs where the value is zero, or is that assumed when the data gets rolled >> up for archive or plotting? >> Thx, Chris >>> >>> >>>> > chris, > > if the sensor returns a value of zero, then return zero. if the sensor is > broken, return a value of None. > > btw, you should return numeric values (integer or float) whenever > possible. it is ok for the driver to use string values internally in the > dict, but anything that is returned in a LOOP packet must be numeric. > > have you read the 'porting to new hardware' section of the customizing > guide? > > http://weewx.com/docs/customizing.htm#porting > > m >
