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] <javascript:>> 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/a3960248-7e70-4752-90b0-a3655e21559f%40googlegroups.com.
