Thanks for both of those bits of info Andrew. I'll try the change in
[[StdArchive]] tomorrow (here) and see how that goes

Colin

On Tue, 30 Oct 2018, 21:57 Andrew Milner, <[email protected]>
wrote:

> re vantage driver - Tom is the man
>
>
>
> On Tuesday, 30 October 2018 10:56:25 UTC+2, Andrew Milner wrote:
>>
>> If you set software record creation in weewx [[StdArchive]] section of
>> weewx.conf then the hardware archive record will not be used and weewx will
>> generate the archive records from the LOOP packets - so if only the LOOP
>> packets are supplied weewx should generate the REC packets itself.
>>
>> .
>>
>> On Tuesday, 30 October 2018 09:33:01 UTC+2, Colin Larsen wrote:
>>>
>>> The Arduino, yes it has RTC - the Rpi no. It is syncing to my own
>>> stratum 1 time source though, is that usually enough accuracy? I have a
>>> spare RTC module so I'll do that mod to dump the hwclock
>>>
>>> There has been a problem with the Arduino software regarding RTC that
>>> has just been corrected today - that was part of yesterdays frustration, so
>>> hopefully that's out of the way.
>>>
>>> The Arduino software writer is asking if the REC data can be ignored and
>>> just the LOOP data used, apparently some issue with not being able to
>>> expunge that record from memory. I'm not sure who to contact regards the
>>> vantage driver though.
>>>
>>> On Tue, Oct 30, 2018 at 7:23 PM Andrew Milner <[email protected]>
>>> wrote:
>>>
>>>> one further point …. caused by the enormous time difference in one of
>>>> your logs - do you have an RTC on the rpi and on the Arduino which is doing
>>>> the emulation?  weewx will throw wobblies and be rather unpredictable if it
>>>> starts before it has a correct time set and/or there is a large time
>>>> difference between station and weewx.  the fake hwclock by itself is not
>>>> sufficient.  weewx tries to hold off until it has what it thinks is the
>>>> right time - but does not always get it right.  rtc is the way to go for
>>>> guaranteed success and disable all references to the fake hwclock.
>>>>
>>>>
>>>> On Tuesday, 30 October 2018 05:57:59 UTC+2, Colin Larsen wrote:
>>>>>
>>>>> Unfortunately I don't know either :) I've handed the info to the
>>>>> developer to try and sort it out. I'll pass that on too though in case
>>>>> you're right.
>>>>>
>>>>> Thanks again
>>>>>
>>>>> On Tue, 30 Oct 2018, 16:12 Andrew Milner, <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> I am a little baffled in that the REC looks more like what I would
>>>>>> expect for a LOOP and the LOOP looks more like what I would expect for a
>>>>>> REC in that the REC only contains barometer whilst the LOOP contains
>>>>>> altimeter, barometer and pressure values and without checking in fine
>>>>>> detail it looks as though there are more fields in the LOOP than there 
>>>>>> are
>>>>>> in the REC.  Maybe this is what is expected, maybe not - only you know!!
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tuesday, 30 October 2018 01:25:57 UTC+2, Colin Larsen wrote:
>>>>>>>
>>>>>>> Andrew,
>>>>>>>
>>>>>>> Thanks once agin for that nudge in the right direction! By running
>>>>>>> Weewx from the command line I was able to catch the faulty data and 
>>>>>>> send it
>>>>>>> on to the developer of the hardware. I'm extremely grateful for the 
>>>>>>> advice.
>>>>>>> As you'll see below the first REC packets have the wrong date, the LOOP
>>>>>>> packets are fine. This is obviously the issue that Weewx is rightly
>>>>>>> complaining about.
>>>>>>>
>>>>>>> REC:    2019-09-11 12:05:00 NZST (1568160300) appTemp:
>>>>>>> 23.7946336801, barometer: 996.241532442, cloudbase: 1192.83426336,
>>>>>>> consBatteryVoltage: None, dateTime: 1568160300, dewpoint: 13.2578694156,
>>>>>>> ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, 
>>>>>>> forecastRule:
>>>>>>> 193, heatindex: 22.7777777778, highRadiation: 8.0, highUV: 0.0, humidex:
>>>>>>> 25.7175378458, inDewpoint: 12.5050008741, inHumidity: 48.0, inTemp:
>>>>>>> 24.2222222222, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 
>>>>>>> 0.0,
>>>>>>> leafWet2: 0.0, maxSolarRad: 677.517690702, outHumidity: 55.0, outTemp:
>>>>>>> 22.7777777778, radiation: 5.0, rain: 0.0, rainRate: 0.0, rxCheckPercent:
>>>>>>> 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0,
>>>>>>> soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0,
>>>>>>> txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 22.7777777778,
>>>>>>> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, 
>>>>>>> windSpeed:
>>>>>>> 0.0
>>>>>>>
>>>>>>> REC:    2019-09-11 12:10:00 NZST (1568160600) appTemp:
>>>>>>> 23.9395702779, barometer: 996.106076916, cloudbase: 1193.82866351,
>>>>>>> consBatteryVoltage: None, dateTime: 1568160600, dewpoint: 13.3610055859,
>>>>>>> ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, 
>>>>>>> forecastRule:
>>>>>>> 193, heatindex: 22.8888888889, highRadiation: 6.0, highUV: 0.0, humidex:
>>>>>>> 25.8866899091, inDewpoint: 12.3022086734, inHumidity: 48.0, inTemp: 
>>>>>>> 24.0,
>>>>>>> interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 
>>>>>>> 0.0,
>>>>>>> maxSolarRad: 678.470118882, outHumidity: 55.0, outTemp: 22.8888888889,
>>>>>>> radiation: 6.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, 
>>>>>>> soilMoist1:
>>>>>>> 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0,
>>>>>>> soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None,
>>>>>>> usUnits: 16, UV: 0.0, windchill: 22.8888888889, windDir: None, windGust:
>>>>>>> 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0
>>>>>>>
>>>>>>> REC:    2019-09-11 12:15:00 NZST (1568160900) appTemp:
>>>>>>> 23.8477397072, barometer: 996.139940797, cloudbase: 1228.9199514,
>>>>>>> consBatteryVoltage: None, dateTime: 1568160900, dewpoint: 13.0795786931,
>>>>>>> ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, 
>>>>>>> forecastRule:
>>>>>>> 193, heatindex: 22.8888888889, highRadiation: 9.0, highUV: 0.0, humidex:
>>>>>>> 25.7291442751, inDewpoint: 11.9820744371, inHumidity: 47.0, inTemp: 
>>>>>>> 24.0,
>>>>>>> interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 
>>>>>>> 0.0,
>>>>>>> maxSolarRad: 678.963138624, outHumidity: 54.0, outTemp: 22.8888888889,
>>>>>>> radiation: 9.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, 
>>>>>>> soilMoist1:
>>>>>>> 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0,
>>>>>>> soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None,
>>>>>>> usUnits: 16, UV: 0.0, windchill: 22.8888888889, windDir: None, windGust:
>>>>>>> 0.0, windGustDir: None, windrun: 0.0, windSpeed: 0.0
>>>>>>>
>>>>>>> REC:    2019-09-11 12:20:00 NZST (1568161200) appTemp:
>>>>>>> 25.0073116388, barometer: 996.207668561, cloudbase: 1348.87628346,
>>>>>>> consBatteryVoltage: None, dateTime: 1568161200, dewpoint: 13.22865792, 
>>>>>>> ET:
>>>>>>> 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, forecastRule: 
>>>>>>> 193,
>>>>>>> heatindex: 24.0, highRadiation: 17.0, highUV: 0.0, humidex: 
>>>>>>> 26.9233851327,
>>>>>>> inDewpoint: 12.2008068001, inHumidity: 48.0, inTemp: 23.8888888889,
>>>>>>> interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 0.0, leafWet2: 
>>>>>>> 0.0,
>>>>>>> maxSolarRad: 678.996340225, outHumidity: 51.0, outTemp: 24.0, radiation:
>>>>>>> 10.0, rain: 0.0, rainRate: 0.0, rxCheckPercent: 0.0, soilMoist1: 0.0,
>>>>>>> soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0,
>>>>>>> soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0, txBatteryStatus: None,
>>>>>>> usUnits: 16, UV: 0.0, windchill: 24.0, windDir: None, windGust: 0.0,
>>>>>>> windGustDir: None, windrun: 0.0, windSpeed: 0.0
>>>>>>>
>>>>>>> REC:    2019-09-11 12:25:00 NZST (1568161500) appTemp:
>>>>>>> 25.1971216855, barometer: 995.97062139, cloudbase: 1389.00049386,
>>>>>>> consBatteryVoltage: None, dateTime: 1568161500, dewpoint: 13.1290899619,
>>>>>>> ET: 0.0, extraTemp1: 0.0, extraTemp2: 0.0, extraTemp3: 0.0, 
>>>>>>> forecastRule:
>>>>>>> 193, heatindex: 24.2222222222, highRadiation: 12.0, highUV: 0.0, 
>>>>>>> humidex:
>>>>>>> 27.090004937, inDewpoint: 12.0486967731, inHumidity: 48.0, inTemp:
>>>>>>> 23.7222222222, interval: 5, leafTemp1: 0.0, leafTemp2: 0.0, leafWet1: 
>>>>>>> 0.0,
>>>>>>> leafWet2: 0.0, maxSolarRad: 678.570029189, outHumidity: 50.0, outTemp:
>>>>>>> 24.2222222222, radiation: 9.0, rain: 0.0, rainRate: 0.0, rxCheckPercent:
>>>>>>> 0.0, soilMoist1: 0.0, soilMoist2: 0.0, soilMoist3: 0.0, soilMoist4: 0.0,
>>>>>>> soilTemp1: 0.0, soilTemp2: 0.0, soilTemp3: 0.0, soilTemp4: 0.0,
>>>>>>> txBatteryStatus: None, usUnits: 16, UV: 0.0, windchill: 24.2222222222,
>>>>>>> windDir: None, windGust: 0.0, windGustDir: None, windrun: 0.0, 
>>>>>>> windSpeed:
>>>>>>> 0.0
>>>>>>>
>>>>>>> LOOP:   2018-10-30 12:13:45 NZDT (1540854825) altimeter:
>>>>>>> 998.675752833, appTemp: 19.2627703232, barometer: 998.984506851, 
>>>>>>> cloudbase:
>>>>>>> 1093.61384033, consBatteryVoltage: 0.0, dateTime: 1540854825, dayET: 
>>>>>>> 0.0,
>>>>>>> dayRain: 0.0, dewpoint: 10.3869357368, extraAlarm1: 0, extraAlarm2: 0,
>>>>>>> extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0,
>>>>>>> extraAlarm7: 0, extraAlarm8: 0, extraTemp1: 0.0, extraTemp2: 0.0,
>>>>>>> extraTemp3: 0.0, extraTemp4: 0.0, extraTemp5: 0.0, extraTemp6: 0.0,
>>>>>>> extraTemp7: 0.0, forecastIcon: 0, forecastRule: 0, heatindex:
>>>>>>> 19.1111111111, humidex: 20.5701568672, inDewpoint: 9.63329898111,
>>>>>>> inHumidity: 52.0, insideAlarm: 0, inTemp: 19.7777777778, leafTemp1: 0.0,
>>>>>>> leafTemp2: 0.0, leafTemp3: 0.0, leafTemp4: 0.0, leafWet1: 0.0, leafWet2:
>>>>>>> 0.0, leafWet3: 0.0, leafWet4: 0.0, maxSolarRad: 930.93994079, monthET: 
>>>>>>> 0.0,
>>>>>>> monthRain: 0.0, outHumidity: 57.0, outsideAlarm1: 0, outsideAlarm2: 0,
>>>>>>> outTemp: 19.1111111111, pressure: 998.288070605, radiation: 0.0, rain:
>>>>>>> None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0,
>>>>>>> soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: 0.0, soilMoist2: 0.0,
>>>>>>> soilMoist3: 0.0, soilMoist4: 0.0, soilTemp1: 0.0, soilTemp2: 0.0,
>>>>>>> soilTemp3: 0.0, soilTemp4: 0.0, stormRain: 0.0, stormStart: 943873200,
>>>>>>> sunrise: 1540810800, sunset: 1540810800, trendIcon: -1, 
>>>>>>> txBatteryStatus: 1,
>>>>>>> usUnits: 16, UV: 0.0, windchill: 19.1111111111, windDir: None, windGust:
>>>>>>> 0.0, windGustDir: None, windSpeed: 0.0, windSpeed10: 0.0, yearET: 0.0,
>>>>>>> yearRain: 0.0
>>>>>>>
>>>>>>> On Monday, 29 October 2018 23:02:39 UTC+13, Colin Larsen wrote:
>>>>>>>>
>>>>>>>> Hi Andrew
>>>>>>>>
>>>>>>>> Thanks for reply and help, you may just have given me the
>>>>>>>> information I need to debug this issue.
>>>>>>>>
>>>>>>>> Yes I do indeed realise that Thomas is 'Mr Weewx' and yes I love
>>>>>>>> this application too, that's why I went down the Weewx path. I looked 
>>>>>>>> at
>>>>>>>> the amount of support folks were given when they struck hiccups and 
>>>>>>>> went
>>>>>>>> 'wow' this is definitely what I'm looking for.
>>>>>>>>
>>>>>>>> So I meant absolutely no disrespect in my reply, perhaps it was
>>>>>>>> tinged with a days debug frustration.
>>>>>>>>
>>>>>>>> I think what you've said about running Weewx from the command line
>>>>>>>> is exactly what I needed to know. The more information I can get for 
>>>>>>>> the
>>>>>>>> WeatherDuino folk the faster they can fix any problem, so any logs etc 
>>>>>>>> from
>>>>>>>> the Vantage driver will be a huge help.
>>>>>>>>
>>>>>>>> I had already gone back to the vanilla Weewx, in fact I may do a
>>>>>>>> complete rebuild tomorrow to see if that helps. At the moment I just 
>>>>>>>> want
>>>>>>>> to get good data flowing then I can move onto the glossy stuff.
>>>>>>>>
>>>>>>>> Many thanks again Andrew, hopefully Thomas hasn't written me off
>>>>>>>> just yet!
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>> Colin
>>>>>>>>
>>>>>>>> On Mon, 29 Oct 2018, 22:22 Andrew Milner, <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Colin
>>>>>>>>> FYI Thomas IS mr weewx - it is HIS creation and HIS design.  If
>>>>>>>>> you are going to continue with weewx you'd be well advised to listen 
>>>>>>>>> to
>>>>>>>>> what Thomas says!!!!
>>>>>>>>>
>>>>>>>>> Have you tried setting the debug options to gain further
>>>>>>>>> information??
>>>>>>>>>
>>>>>>>>> The simulator does not use any hardware, does not obtain
>>>>>>>>> timestamps from anywhere other than the host machine - this could be 
>>>>>>>>> why a
>>>>>>>>> new db with simulator works.  The vantage driver has many years of
>>>>>>>>> successful operation with Davis hardware - whilst your Davis lookalike
>>>>>>>>> appears to generate archive types and timestamps which would not come 
>>>>>>>>> from
>>>>>>>>> a real Davis device.
>>>>>>>>>
>>>>>>>>> Have you run from the command line rather than as a background
>>>>>>>>> daemon?? This then gives Loop and Rec data as received - see the 
>>>>>>>>> weewx user
>>>>>>>>> documentation for more information.
>>>>>>>>>
>>>>>>>>> Since the hardware appears to be 'under development' I would
>>>>>>>>> recommend using only the standard weewx software - as downloaded from 
>>>>>>>>> weewx
>>>>>>>>> repository, using the standard skin (not Belchertown) until such time 
>>>>>>>>> as
>>>>>>>>> you have got everything working correctly - and then, and only then, 
>>>>>>>>> start
>>>>>>>>> to use other skins.  The standard weewx uses much less cpu processing 
>>>>>>>>> power
>>>>>>>>> than some of the other skins such as forecasts, Belchertown etc.  
>>>>>>>>> Slowly
>>>>>>>>> but surely is the best way to sort out new hardware and software - 
>>>>>>>>> and you
>>>>>>>>> would appear to have both involved here!!
>>>>>>>>>
>>>>>>>>> weewx is great, it is very stable, and it just works straight out
>>>>>>>>> of the box.  It rarely has bugs and very rarely has issues even.  It 
>>>>>>>>> is
>>>>>>>>> flexible, versatile, adaptable, extendable - how many more adjectives 
>>>>>>>>> do
>>>>>>>>> you need??!!  However - whilst the standard weewx is well proven the 
>>>>>>>>> same
>>>>>>>>> is not necessarily true for user supplied add-ons and enhancements.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Monday, 29 October 2018 06:05:45 UTC+2, Colin Larsen wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Thomas
>>>>>>>>>>
>>>>>>>>>> While I may agree with you that it's a station hardware problem I
>>>>>>>>>> do find that a particularly unhelpful statement.
>>>>>>>>>>
>>>>>>>>>> When you say "clearly" where do you see that in my information
>>>>>>>>>> and what could I pass to them to help debug the issue please? Is 
>>>>>>>>>> there a
>>>>>>>>>> way to capture the information being sent to Weewx via the driver?
>>>>>>>>>>
>>>>>>>>>> Interestingly if I create a new Weewx db file, start weewx with
>>>>>>>>>> simulator and then swap to the vantage driver it seems to work ok.
>>>>>>>>>>
>>>>>>>>>> I went the Weewx route because I saw that the help from the
>>>>>>>>>> developers and users was fantastic. Unfortunately your blanket and 
>>>>>>>>>> somewhat
>>>>>>>>>> unhelpful statement dims that a little. I hope this isn't starting 
>>>>>>>>>> to shape
>>>>>>>>>> up as 'he said, she said' problem
>>>>>>>>>>
>>>>>>>>>> I really like this software so hopefully there is a solution here
>>>>>>>>>> somewhere :)
>>>>>>>>>>
>>>>>>>>>> Cheers
>>>>>>>>>> Colin
>>>>>>>>>>
>>>>>>>>>> On Monday, 29 October 2018 14:57:48 UTC+13, Thomas Keffer wrote:
>>>>>>>>>>>
>>>>>>>>>>> Why don't you ask the WeatherDuino people about this? Clearly,
>>>>>>>>>>> your instrument is emitting some strange timestamps and archive 
>>>>>>>>>>> types...
>>>>>>>>>>>
>>>>>>>>>>> -tk
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Oct 28, 2018 at 6:43 PM Colin Larsen <
>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> I wonder if the Pi I'm using is a little cranky now - so many
>>>>>>>>>>>> confusing problems popping up.
>>>>>>>>>>>>
>>>>>>>>>>>> Just saw this one in the log - another time anomaly though -
>>>>>>>>>>>> 27392398.74 seconds fast ????
>>>>>>>>>>>>
>>>>>>>>>>>> Oct 29 14:37:01 raspberrypi weewx[10296]: engine: Starting up
>>>>>>>>>>>> weewx version 3.8.2
>>>>>>>>>>>>
>>>>>>>>>>>> Oct 29 14:37:01 raspberrypi weewx[10296]: engine: Clock error
>>>>>>>>>>>> is 27392398.74 seconds (positive is fast)
>>>>>>>>>>>>
>>>>>>>>>>>> Oct 29 14:37:02 raspberrypi weewx[10296]: vantage: Clock set to
>>>>>>>>>>>> 2018-10-29 14:37:02 NZDT (1540777022)
>>>>>>>>>>>>
>>>>>>>>>>>> Oct 29 14:37:02 raspberrypi weewx[10296]: manager: Unable to
>>>>>>>>>>>> add record 2018-10-29 14:35:00 NZDT (1540776900) to database 
>>>>>>>>>>>> 'weewx.sdb':
>>>>>>>>>>>> UNIQUE constraint failed: archive.dateTime
>>>>>>>>>>>>
>>>>>>>>>>>> Oct 29 14:37:02 raspberrypi weewx[10296]: engine: Internal
>>>>>>>>>>>> error detected. Catchup abandoned
>>>>>>>>>>>>
>>>>>>>>>>>> Oct 29 14:37:02 raspberrypi weewx[10296]: **** Unknown archive
>>>>>>>>>>>> type = 0x7a
>>>>>>>>>>>>
>>>>>>>>>>>> Oct 29 14:37:02 raspberrypi weewx[10296]: engine: Starting main
>>>>>>>>>>>> packet loop.
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> 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.
>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>> --
>>>>>> 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.
>>>>>>
>>>>> --
>>>> 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.
>>>>
>>> --
> 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.
>

-- 
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.

Reply via email to