Applied the sub-zero fix and updated it to https://etherpad.net/p/weewx_raspi
Yes, I only have 1 station currenlty but might at some point add a DHT22 or some DIY air quality sensors. Oct 29 11:58:58 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 11:59:01 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:00:01 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:01:01 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:01:04 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:02:04 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:03:04 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:03:07 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:04:08 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:05:08 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:05:10 ripapi weewx[22108]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:05:36 ripapi weewx[22384]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:07:06 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:08:07 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:09:07 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:09:09 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:10:09 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:11:09 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:11:11 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:12:12 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:13:12 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:13:14 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:14:14 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:14:17 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:15:17 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:16:18 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:16:20 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:17:20 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:18:20 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:18:23 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:19:23 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:20:23 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:20:26 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:21:26 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:22:26 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:22:29 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:23:30 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:24:30 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:24:33 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:25:33 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:26:33 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:26:36 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) Oct 29 12:27:36 ripapi weewx[22446]: ws3000: write: 7b 03 40 7d (len=4) looks like that it's a bit irregular. I changed the loop interval from 30-> 60 earlier today, but to me it looks like that some 'duplicates' are there. My weewx.conf visible at https://pastebin.com/gZvFUm5q -> Please propose changes, if needed. Archive interval now 2min for test purposes, can change that to 5min if useful. Also if record_generation needs to be changed to software, that's also OK. I haven't yet read very much what do these configs do.. And thanks for your help Olivier :) r maanantai 29. lokakuuta 2018 11.30.10 UTC+2 [email protected] kirjoitti: > > ok, this is weird. If the interval was already 30 seconds, I don't > understand why the driver was trying to fetch the data several times in a > short interval (as seen in your log). > > What's the output of: > grep "ws3000: write" <log file> > I would like to see how often the driver is fetching data. > > I have to admit that I can't remember how this is all supposed to work. My > setup is very different: I am using the ws3000DataService to fetch the > values from the WS-3000 only when I am writing a record to the database > (every 60 seconds). The data is then combined with what I get from my other > station. You could say that in my case, the WS-3000 is only a secondary > station, and therefore the loop_interval is not taken into account. > > In your case (I am assuming that you only have 1 station), it doesn't make > sense to use the ws3000DataService. But we need to figure out how weewx and > the driver are interacting with the station... > As far as I can tell, the driver is generating loop packets (using the > loop_interval). Then, I assume that when weewx is generating an archive > record something else must be happening, depending on the values of the > archive_interval and maybe record_generation (software or hardware). But I > don't know exactly how this is working, and what function weewx is calling > to fetch the data (is it calling genLoopPackets again?). I have the > feeling that the record generation might trigger an additional query to the > station, and if it turns out to be too close to a loop packet generation, > then we run into the current issue. > > Ideally, you would want to disable the loop packets completely if > possible, and just let weewx fetch the data when it needs to generate an > archive record. I don't know if this is possible though. But after quickly > looking at the documentation, I think that you may have to consider > switching record_generation to *software*. This might help to prevent the > problem, if weewx builds the record from previous loop packets rather than > be querying the station again. > > What is your archive_interval? > > -- 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.
