Lightning Strike issues

[dave.sp...@gmail.com]

Good morning all, I am having a small issue with the lightning strikes. I have an Acurite 7-n-1 sensors. On the weewx web page the lightning strikes are not correct. Here is what the web page is showing:

 

 

 

 

 

When I tail the logs, here is just the part on lightning:  'lightning_distance': 7, 'lightning_strike_count': 296

 

Weewx.conf:

 

[SDR]

    # This section is for the software-defined radio driver.

 

    # The driver to use

    driver = user.sdr

    log_unknown_sensors = True

    log_unmapped_sensors = True

    cmd = sudo rtl_433 -M utc -F json

 

    [[sensor_map]]

        outTemp = temperature.0010.AcuriteAtlasPacket

        outHumidity = humidity.0010.AcuriteAtlasPacket

        windSpeed = wind_speed.0010.AcuriteAtlasPacket

        windDir = wind_dir.0010.AcuriteAtlasPacket

        UV = uv.0010.AcuriteAtlasPacket

        rain_total = rain_total.0010.AcuriteAtlasPacket

        radiation = lux.0010.AcuriteAtlasPacket

        outTempBatteryStatus = battery.0010.AcuriteAtlasPacket

        lightning_distance = strike_distance.0010.AcuriteAtlasPacket

        lightning_strike_count = strike_count.0010.AcuriteAtlasPacket

        luminosity = lux.0010.AcuriteAtlasPacket

 

    [[deltas]]

        rain = rain_total

 

 

Hardware:

Weewx version 4.8.0

Running SDR

 

Any help in getting the lightning info would be great.

Thanks

Dave

[vince]

"Is not correct" isn't much to go on. What are you expecting to see ?

See https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem

I don't know about your station in particular, but WeatherFlow stations frequently can show thousands of bogus lightning strikes due to the inexpensive sensor that vendor uses.  Fix there is to rotate the sensor 90 degrees which amazingly does work in quieting down erroneous strike readings.  Acurite has a web page on your station at https://support.acurite.com/hc/en-us/articles/360045278273-AcuRite-Atlas-7-in-1-Inaccurate-Lightning if that helps any.

[an oldman]

the atlas and lightning sensors have a running count for strikes

i have a atlas and lightning sensor and i use this in weewx.conf

under sdr in sensor map

[SDR]

    [[sensors_map]]

        strike_total = strike_count.494.AcuriteAtlasPacket

        lightning_distance = strike_distance.494.AcuriteAtlasPacket

    [[deltas]]

        lightning_strike_count = strike_total

then add accumulators section to weewx.conf

[Accumulator]

    [[lightning_distance]]

        extractor = last

then in stdcalibrate

[StdCalibrate]

    [[Corrections]]

        lightning_distance = lightning_distance if lightning_strike_count > 0 else None

hope this helps

[dave.sp...@gmail.com]

My acurite sensor is reporting correct lightning data. In the loop data I see 'lightning_distance': 7, 'lightning_strike_count': 296, but on the web page it is saying that strikes are 9768 and the hourly total of approx. 280000+. How do I get it to where it shows that current data instead of erroneous values?

 

 

 

I would except to see strikes by at 7

 

Also how do I get a graft to see the distance? I am running the default seasons 4.8.0 skin

 

Thanks

Dave

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/07aa5e30-cafe-456c-a4a7-3dcb55fa460bn%40googlegroups.com.

[an oldman]

the graph have to add to skin.conf this is what i added

[DisplayOptions]

    # Some observations display a sum rather than min/max values
    obs_type_sum = rain, ET, lightning_strike_count

    # This list determines which plots will be shown, as well as the order in
    # which they will be displayed.  The names refer to the plots defined in
    # the ImageGenerator section, without any time span prefix.  For example,
    # the name 'wind' refers to 'daywind', 'weekwind', 'monthwind', and
    # 'yearwind'.

    plot_groups = lightning

[ImageGenerator]

    [[[daylightning]]]
            yscale = None, None, 1
            plot_type = bar
            [[[[lightning_strike_count]]]]
                aggregate_type = sum
                aggregate_interval = hour
                label = Lightning Strike (hourly total)

[gjr80]

The reason you are seeing such large lightning strike numbers reported by WeeWX is that your station reports a cumulative lightning strike count, but WeeWX requires a per-period count. As posted earlier, the solution is to tell the SDR driver the lightning_strike_count field is a delta that is derived from the cumulative strike count. This is done via the highlighted lines below that were included in the earlier post:

[SDR]

    [[sensors_map]]

        strike_total = strike_count.494.AcuriteAtlasPacket

        lightning_distance = strike_distance.494.AcuriteAtlasPacket

    [[deltas]]

        lightning_strike_count = strike_total

Have you included similar lines? Did you restart WeeWX after making the changes? Also note that unless you deleted the old cumulative data from WeeWX it will likely take an hour for the effects of any old cumulative data to disappear from last hour total.

Gary

[dave.sp...@gmail.com]

Thank you Gary, That seems to have done the trick.

 

Thanks

Dave

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/8ddac774-6eab-4bad-820b-46341af2bd35n%40googlegroups.com.