Cool. This is part of why we pay extra for Davis !!! What about the extra sensors VP2 folks also see ? (that fortunately aren't in the extended schema by default so we get lucky there)
Does the VP2 weewx.conf stanza need an extra_sensors include/exclude list or the like perhaps ? On Friday, May 6, 2022 at 10:24:15 AM UTC-7 Tom Keffer wrote: > Huge thumbs up to Bruce at Davis, who didn't let the ball drop. > > While we all know that VantageVues do not support extra sensors, what we > did not know is that the corresponding field values in the logger's archive > records are 'undefined', not null. So, you may get random values for Vues. > > The fix is a simple matter of skipping over any extra sensors when > decoding for a Vue. > > Please try the attached driver. > > While this is not documented in their API, they are way ahead of other > vendors in that they publish an API at all. The vast majority of vendors do > not, leaving us to reverse engineer them. > > Let me know how the new version works. > > -tk > > On Sun, Feb 27, 2022 at 11:47 AM Jeff A. D. <jadav...@gmail.com> wrote: > >> Makes some sense. But I also wonder about ET values always being '0' >> when I have no solar sensors. That does make it into the archive data and >> the database, though I don't use it in any reports, so I guess it really >> doesn't matter, though I wouldn't think it's accurate. (I'm assuming '0" >> means no evaporation and isn't the same as 'null'.) I don't recall if that >> has been brought up. >> >> On Sunday, February 27, 2022 at 4:34:17 AM UTC-7 tke...@gmail.com wrote: >> >>> I think the way to interpret "alarm" values of zero is no alarm at all. >>> So, zero values are probably normal. >>> >>> However, it is not normal to have leafWet4 when there is no sensor. >>> >>> On Sat, Feb 26, 2022 at 8:22 PM Jeff A. D. <jadav...@gmail.com> wrote: >>> >>>> Just as a matter of interest, I went back even further and looked at my >>>> original Vantage Pro (not 2) with firmware "REV B MAR 30 2004". >>>> >>>> I'm seeing the soilLeafAlarms but not leafWet in the LOOP data. >>>> >>>> I don't push to Weatherlink or publish online at all, I just use WeeWX >>>> to download the archive data from the logger and produce reports >>>> (particularly NOAA) to keep my own historical records locally. Works >>>> great >>>> for me. >>>> >>>> Manufacture code: B30407A83A >>>> >>>> LOOP: 2022-02-26 21:14:24 MST (1645935264) 'altimeter': >>>> '30.257678000000002', 'appTemp': '-6.179805913900935', 'barometer': >>>> '30.257678000000002', 'cloudbase': '1571.5926270879713', >>>> 'consBatteryVoltage': '4.75', 'dateTime': '1645935264', 'dayET': '0.0', >>>> 'dayRain': '0.0', 'dewpoint': '-4.9150075591870745', 'ET': 'None', >>>> 'extraAlarm1': '0', 'extraAlarm2': '0', 'extraAlarm3': '0', 'extraAlarm4': >>>> '0', 'extraAlarm5': '0', 'extraAlarm6': '0', 'extraAlarm7': '0', >>>> 'extraAlarm8': '0', 'extraTemp1': '43.0', 'forecastIcon': '8', >>>> 'forecastRule': '1', 'heatindex': '2.0', 'humidex': '1.9999999999999964', >>>> 'inDewpoint': '27.247736039588684', 'inHumidity': '24.0', 'insideAlarm': >>>> '0', 'inTemp': '64.9', 'maxSolarRad': 'None', 'monthET': '0.0', >>>> 'monthRain': '0.0', 'outHumidity': '72.0', 'outsideAlarm1': '0', >>>> 'outsideAlarm2': '0', 'outTemp': '2.0', 'pressure': '23.188788492606', >>>> 'rain': '0.0', 'rainAlarm': '0', 'rainRate': '0.0', '*soilLeafAlarm1': >>>> '0', 'soilLeafAlarm2': '0', 'soilLeafAlarm3': '0', 'soilLeafAlarm4': '0',* >>>> 'stormRain': '0.0', 'sunrise': '1645883880', 'sunset': '1645923900', >>>> 'txBatteryStatus': '0', 'usUnits': '1', 'windchill': '2.0', 'windDir': >>>> '162.0', 'windGust': '3.0', 'windGustDir': '162.0', 'windrun': 'None', >>>> 'windSpeed': '3.0', 'windSpeed10': '2.0', 'yearET': '0.0', 'yearRain': >>>> '0.0' >>>> >>>> On Saturday, February 26, 2022 at 1:41:32 PM UTC-7 vince wrote: >>>> >>>>> On Saturday, February 26, 2022 at 12:01:07 PM UTC-8 Tom Keffer wrote: >>>>> >>>>>> Now that you mention it, I see much the same thing on my vintage VP2. >>>>>> >>>>> However, the archive records are fine. If you use hardware record >>>>>> generation (the default), then the values should not get into the >>>>>> database >>>>>> at all. >>>>>> >>>>>> So, Tom & VInce, I suspect this is a different issue, if it's an >>>>>> issue at all. >>>>>> >>>>> >>>>> Think it's a different issue. The extra leafWet4 and soilLeafAlarm1-4 >>>>> items we see on VP2 aren't even in the extended schema so we might just >>>>> be >>>>> getting lucky there. Given my firmware is over 13 years old, whatever's >>>>> going on has been there for a long time.... >>>>> >>>>> -- >>>> 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/f601b966-0862-4400-930b-f8e3cb073281n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/f601b966-0862-4400-930b-f8e3cb073281n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> 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/6268d78e-bc66-4d79-b9d2-189d080eb674n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/6268d78e-bc66-4d79-b9d2-189d080eb674n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/24abd4fc-bfcf-49cc-b305-2fe4fea257abn%40googlegroups.com.
