No problem, Rob. You can still test whether the driver is working by looking at your database. The values for all extra sensors should now be null.
On Mon, May 9, 2022 at 9:45 AM Rob Cranfill <[email protected]> wrote: > I have installed the new (May 6) driver and my system seems happy enough. > I'm not sure I'm a good test, as I had previously hacked skin.conf to > exclude the non-existent sensors (as opposed to letting the system > self-configure and ignore missing data, right?) and I am loath to put that > back. > > But I suppose the next software update (I'm still on WeeWX 4.7, Seasons > 4.6) I'll find out just how happy it is. > > But I'll bet it's fine. Thanks again for your work! > > On Sunday, May 8, 2022 at 2:26:52 PM UTC-7 Rob Cranfill wrote: > >> Thanks, I’ll pop the new code in, a take a look after a bit, and let ya >> know. >> >> On Sun, May 8, 2022 at 11:47 Tom Keffer <[email protected]> wrote: >> >>> Neither. The push to Weatherlink was just for troubleshooting. The log >>> files should look normal. >>> >>> On Sun, May 8, 2022 at 10:05 AM Rob Cranfill <[email protected]> wrote: >>> >>>> Tom, >>>> >>>> I'm glad to try out the new code, but I'm not sure what you'd like us >>>> to do - push data to Weatherlink again? Or just look for something in the >>>> log files? >>>> >>>> </rob> >>>> >>>> >>>> On Fri, May 6, 2022 at 10:24 AM Tom Keffer <[email protected]> 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. <[email protected]> >>>>> 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 [email protected] >>>>>> 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. <[email protected]> >>>>>>> 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 [email protected]. >>>>>>>> >>>>>>> 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 [email protected]. >>>>>> 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 a topic in the >>>>> Google Groups "weewx-user" group. >>>>> To unsubscribe from this topic, visit >>>>> https://groups.google.com/d/topic/weewx-user/BbOKMsyUUBo/unsubscribe. >>>>> To unsubscribe from this group and all its topics, send an email to >>>>> [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEA0%2BG9%2B1AXTtuRc1eqKGc3%3DXG1_bZvP-SmH%2BqNyz9NEPA%40mail.gmail.com >>>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEA0%2BG9%2B1AXTtuRc1eqKGc3%3DXG1_bZvP-SmH%2BqNyz9NEPA%40mail.gmail.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 [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/CAOVFAvrp1nXLy6gRCguj%2BV8YecZyXH8LcjV%2BDwX33Ev1wKmEXg%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/weewx-user/CAOVFAvrp1nXLy6gRCguj%2BV8YecZyXH8LcjV%2BDwX33Ev1wKmEXg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> -tk >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "weewx-user" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/weewx-user/BbOKMsyUUBo/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEDSnZrqgS%3D%3DGiUo0ddftdJ3rNfUPe3f11KwJ7ne%3Dq7ezQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEDSnZrqgS%3D%3DGiUo0ddftdJ3rNfUPe3f11KwJ7ne%3Dq7ezQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> </rob> >> > -- > 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/bf038f7b-d5fe-4aa1-89e4-4d803e80e3e7n%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/bf038f7b-d5fe-4aa1-89e4-4d803e80e3e7n%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEDM3qyhdb_d-pwo4iZ36RRtgsJ%2ByLDiTFf2zObW9BVJoQ%40mail.gmail.com.
