Yes, I read something about Rapidfire not working with Acurite sensors until 3.7 is released. I decided to stay with the stable release, although third beta looks promising.
I am showing a strong signal from the station to the display whenever I look, so, if it drops out on occasion, I'm not confident in getting that fixed. I think it could be handled, though, if I could get weewx to recognize that it doesn't have good data and not upload it to other services. I'd rather have a missing entry than a bad one. I have turned on the debugging, and every thing is being logged, including every file it sends via ftp. As additional info, here's the MySQL row for the time in question. It's getting the inside temperature from the display, so it appears to be getting something. It didn't get the indoor humidity, but I guess it never does. rxCheckPercent is 0, and it was 87.5 in the previous row, but it's usually 100 (and has been 100 in the almost two hours since the event). Thanks again for looking at it. This isn't a huge deal; it's more of a suggestion about how an archive interval without valid data is handled. # dateTime, usUnits, interval, barometer, pressure, altimeter, inTemp, outTemp, inHumidity, outHumidity, windSpeed, windDir, windGust, windGustDir, rainRate, rain, dewpoint, windchill, heatindex, ET, radiation, UV, extraTemp1, extraTemp2, extraTemp3, soilTemp1, soilTemp2, soilTemp3, soilTemp4, leafTemp1, leafTemp2, extraHumid1, extraHumid2, soilMoist1, soilMoist2, soilMoist3, soilMoist4, leafWet1, leafWet2, rxCheckPercent, txBatteryStatus, consBatteryVoltage, hail, hailRate, heatingTemp, heatingVoltage, supplyVoltage, referenceVoltage, windBatteryStatus, rainBatteryStatus, outTempBatteryStatus, inTempBatteryStatus '1487707200', '1', '5', NULL, '29.34394857875', '29.8745177625901', '78.98', NULL, NULL, NULL, NULL, NULL, NULL, NULL, '0', '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL , NULL, NULL, NULL, NULL, NULL, NULL, '0', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL On Sunday, March 5, 2017 at 4:31:35 PM UTC-5, mwall wrote: > > craig, > > you should only get an empty record if there are no loop packets for an > entire archive interval. if that happens, that means you're getting a loss > of signal for 5 minutes at a time. > > watch the database to see if there is a pattern to the empty records, then > see if you can correlate local radio interference to those times. > > the acurite hardware sends partial packets. as you have seen, wu > rapidfire does not handle partial packets properly. > > m > -- 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]. For more options, visit https://groups.google.com/d/optout.
