I solved my own issue!  :-D  Putting the following line in your Weewx.conf 
file seems to do the trick!

[[Corrections]]
        strike_distance = strike_distance if Lightning_Strikes > 0 else None



On Saturday, April 25, 2020 at 4:29:09 PM UTC-4, Chris Morris wrote:
>
> Thats just it, Gary...LOL  I don't remember...I am still very much a 
> newbie.  :-D  I have followed instructions as best I can, and have even 
> figured out a few things on my own, but I have only been using WeeWX since 
> January (I started building my station in December though).  I know enough 
> about programming to fill a thimble halfway.  LOL
>
> That said, I *tremendously* appreciate the help of everyone on these 
> forums....this has proven to be a really cool and rewarding hobby to pick 
> up!  Thanks to everyone!
>
> On Saturday, April 25, 2020 at 4:21:22 PM UTC-4, gjr80 wrote:
>>
>> Remember the WeeWX approach to data from a driver for a given sensor is:
>>
>>    - a value of 0 should be emitted for a field when the source sensor 
>>    provides a reading of 0
>>    - a python None should be emitted for a field where the source sensor 
>>    is present but not emitting data or the data is considered 'bad' by the 
>>    driver
>>    - a field should be omitted if the source sensor is not present
>>    
>> Gary
>>
>> On Sunday, 26 April 2020 02:31:29 UTC+10, Greg Troxel wrote:
>>>
>>> Chris Morris <[email protected]> writes: 
>>>
>>> > So, lemme take a stab at explaining in a somewhat Boolean way... 
>>> > 
>>> > If strike_count_total_current = strike_count_total_last, then set 
>>> > strike_distance = 0, else strike_distance = INTEGER (actual value 
>>> > reported by Atlas or 6045). 
>>>
>>> Really if the current/last counts are equal, strike_distance should be 
>>> omitted, or it should be set to some sort of nil or undefined value. 
>>> It is not actually 0 either. 
>>>
>>> Then, the bits output by the acurite for distance, are not actually km 
>>> or miles.  They are some complicated re-encoding of the encoding from 
>>> the detector chip that is partly but not quite understood.   See the 
>>> rtl433 list archives for more information.    If you are saying that 
>>> weewx records the value sent by the acurite, that's fine. 
>>>
>>

-- 
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/8e77d8b5-ab07-45ef-9ed8-8b0c820bf6fa%40googlegroups.com.

Reply via email to