[weewx-user] Re: CSV extension writing bad data

Can't comment on what changed on your install from 3.5.0 to 3.9.2. The only WeeWX code that could affect the csv output would be the AcuRite driver, and I see there have been no changes to this driver since the 3.5.0 release that could account for the changed behaviour. Perhaps you are using a

[weewx-user] Re: CSV extension writing bad data

It's probably not too bad to fork the extension and add the CachedValues method as seen in the restx extension (read: copy/paste). Once tested and working this should satisfy option 3. Other important information found f

[weewx-user] Re: CSV extension writing bad data

On Tuesday, October 15, 2019 at 11:39:03 PM UTC-7, gjr80 wrote: > > Hi, > > The problem you are experiencing is due an incompatibility between your > station emitting what is known as partial loop packets (ie not all obs are > included in all loop packets) and the mode in which you are operating

[weewx-user] Re: CSV extension writing bad data

Hi, The problem you are experiencing is due an incompatibility between your station emitting what is known as partial loop packets (ie not all obs are included in all loop packets) and the mode in which you are operating the csv extension. You are running the CSV extension such that it emits l

[weewx-user] Re: CSV extension writing bad data

Yes, I installed a standard report and that is accurate. At this point, I am tempted to run weewx inside of Perl and process LOOP statements directly. :) However, the point of all this is to get the information inside of a nagios monitor. I tried the graphite back end but that didn't seem to wo

[weewx-user] Re: CSV extension writing bad data

You're right. Not much here. What are your other skins (like Standard or Seasons) showing? Do they seem accurate? On Tuesday, October 15, 2019 at 1:50:48 PM UTC-4, Dave wrote: > > > > On Tuesday, October 15, 2019 at 9:39:42 AM UTC-7, Pat wrote: >> >> I saw the debug, but didn't see any actual hel

[weewx-user] Re: CSV extension writing bad data

On Tuesday, October 15, 2019 at 9:39:42 AM UTC-7, Pat wrote: > > I saw the debug, but didn't see any actual helpful debug output. That's > why I asked for a syslog. Oct 15 08:09:55 myserver weewx[18438]: engine: Debug is 1 Oct 15 08:09:55 myserver weewx[18438]: engine: Initializing engine Oct

[weewx-user] Re: CSV extension writing bad data

Answered my own question. The debug shows it's 0.10 which looks like it's the latest available . Sort of running out of options on why yours is acting differently than mine. Hopefully syslog has a clue or two. On Tuesday, October 15, 2019 at 12:39:42

[weewx-user] Re: CSV extension writing bad data

I saw the debug, but didn't see any actual helpful debug output. That's why I asked for a syslog. Also, I am assuming you're on the latest CSV extension version, but I shouldn't assume anything. Are you on the latest CSV extension version? -- You received this message because you are subscrib

[weewx-user] Re: CSV extension writing bad data

You'll note that debug is set to 1 in the weewx.conf I posted. So I have a parsing program that monitors the CSV file. Here's output from manual weewx: LOOP: 2019-10-15 08:09:56 PDT (1571152196) altimeter: 29.9926902844, channel: None, dateTime: 1571152196, inTemp: 77.0, maxSolarRad: None, ou

[weewx-user] Re: CSV extension writing bad data

I've never played with this extension, but I just installed it and copied your weewx.conf [CSV] settings. It appears to be working fine for me on 3.9.2 - my outTemp field is correct (see below). It's 49F outside and that's what's in the CSV. Is there anything in your syslog that would point to