I can't help with Belchertown skin specific problems, but can offer some insight of the lightning_strike_count/None issue. Within WeeWX there is a subtle difference in meaning between an observation being 0 and None. Within loop packets and archive records the existence of a given field (irrespective of value) generally means that the relevant sensor is present and detected by the driver. If the value is None that is an indication that no data/invalid data was received from the sensor. If the value is 0 then data was received from the sensor and the value of that data is, well, 0. If a driver does not detect a given sensor the obs should be omitted from loop packets/archive records. In terms of the Ecowitt gateway driver the driver considers the lightning sensor to be present if the driver sees the lightning count address is the data received from the Ecowitt gateway device, so in your case the lightning sensor is being detected. The fact that the data is None indicates the driver could not decode the corresponding lightning count data. That should not occur.
So, troubleshooting. The fact you are plotting lightning data leads me to assume you do indeed have a WH57 lightning sensor linked to your Ecowitt gateway device? Do you see lightning data in the Ecowitt WSView Plus or WS View apps? Stop then restart WeeWX, let WeeWX run for at least two full archive periods and then post a log extract showing the full WeeWX startup and the reporting cycle for each archive period. Run WeeWX directly <http://weewx.com/docs/usersguide.htm#Running_directly>, this will show loop packet (LOOP:) and archive record (REC:) data on the console. Does lightning_strike_count appear in the loop packets and archive records, and what value do they show? Paste the console output here (text based post please, no an image based screen capture). Gary On Friday, 19 May 2023 at 12:22:18 UTC+10 [email protected] wrote: > Further to this my chart section looks like this... > > [[chart8]] > title = Lightning > time_length = today > aggregate_type = max > aggregate_interval = 3600 # 1 hour > gapsize = 3600 > type = column > > [[[lightning_strike_count]]] > name = Lightning > stacking = normal > > [[[lightning_distance]]] > name = Average Distance > stacking = normal > > Running the gw1000 drive is see that its returning > 'lightning_strike_count': 'None' rather than a zero, so that's what the > error is about. > > I have vague memories of there being some option or flag to set if this > kind of thing happened but I cant find it ! > > So... is there an incantation to change the "none" to 0 > > thanks > > Tim > > > On Thursday, 18 May 2023 at 22:29:02 UTC+10 Tim Tuck wrote: > >> Hi all, >> >> I've just upgraded my weewx instance to the latest Belchertown skin v >> 1.31 and I have this error in syslog... >> >> May 18 20:55:24 metoffice weewx[7013] INFO user.belchertown: Observation >> lightning_strike_count is using unit count that returns %d for >> StringFormat, rather than float point decimal format value - using 0 as >> rounding >> May 18 20:55:24 metoffice weewx[7013] message repeated 2 times: [ INFO >> user.belchertown: Observation lightning_strike_count is using unit count >> that returns %d for StringFormat, rather than float point decimal format >> value - using 0 as rounding] >> >> any help appreciated. >> >> thanks >> >> Tim >> >> >> -- 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/ebcab9d0-462a-4d7e-9fc5-96380915460bn%40googlegroups.com.
