Re: [weewx-development] Re: V4.6.0 beta 3

OK, nothing of consequence in weewx.conf. You can run the vantage driver directly and have it output loop packets direct to the console, this takes WeeWX out of the equation. You can run the vantage driver directly by: 1. stopping WeeWX 2. running the following command: $ PYTHONPATH=/usr/share/

Re: [weewx-development] Re: V4.6.0 beta 3

No I forgot it, attached here. I was looking on github weewx, but I'm not finding the drivers directory. So I went looking at the vantage.py source /usr/share/weewx/weewx/drivers/vantage.py. Python is not my strong suit. So I wondered if 'leafWet1': lambda p, k: float(p[k]) if p[k

Re: [weewx-development] Re: V4.6.0 beta 3

Unfortunately I don’t see any wee_debug output attached? I’d suggest we find the source and fix the problem at source. The driver is most likely the culprit but when you are displaying LOOP packets on the console you are not looking at the data straight out of the driver, rather you are looking

Re: [weewx-development] Re: V4.6.0 beta 3

I'm not sure the wee_debug will help, but I attached it. So, yes, the data is coming in from the driver in a LOOP packet for sensors that don't exist and getting put into the database. The problem is down at the driver. So there are no configuration options on the driver to force values to

Re: [weewx-development] Re: V4.6.0 beta 3

Always, just after I hit send...here is a LOOP packet with data for sensors that don't exist on the Vantage Vue. I can see now then since the skin change to show if data is there, this will be displayed. But here is another LOOP packet snippet. leafTemp1: -90.0, leafTemp2: -81.0, leafWet1: 0,

Re: [weewx-development] Re: V4.6.0 beta 3

Bill, The (one) change from b2 to b3 is that Seasons will now display whatever data it can find in any of the extended schema files in your database. Previously, Seasons displayed a fixed subset of the extended schema. b3/b4 Seasons is not creating the bogus data, it is merely displaying it -

Re: [weewx-development] Re: V4.6.0 beta 3

## Version: 4.6.0b4 I ponder wee_debug. This is a change between beta2 and beta3, I didn't make any adjustments to weewx.conf, just the upgrade. I observed apt remove weewx left things behind, I can see it leaving things that have been modified but not if the same code matches the file in the

Re: [weewx-development] Re: V4.6.0 beta 3

and if I can read your mind, here is a LOOP packet. # The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both loop_request = 1 LOOP: 2021-10-12 21:01:21 PDT (1634097681) altimeter: 30.08348929681147, appTemp: 40.85484139638294, barometer: 30.103, cloudbase: 8025.41285667107

Re: [weewx-development] Re: V4.6.0 beta 3

On more thing, re Seasons template versioning. Tom has started versioning the Seasons template so if you have a look in skins/Seasons/index.html.tmpl you should find a version number in the first few lines, eg: ## Copyright 2009-2018 Tom Keffer, Matthew Wall ## Distributed under terms of GPLv3.

Re: [weewx-development] Re: V4.6.0 beta 3

First step in looking for the culprit is some config info. Running wee_debug and posting the output would be good. Just remember if posting wee_debug output to check it for sensitive info first (eg user names, passwords, API keys etc), wee_

Re: [weewx-development] Re: V4.6.0 beta 3

I also set a limit in weewx.conf for leafTemp1. leafTemp1 = 0, 0, degree_F Oct 12 19:00:14 weewx weewx[25634] WARNING weewx.qc: 2021-10-12 18:55:00 PDT (1634090100) Archive value 'leafTemp1' -26.0 outside limits (0.0, 0.0) Suggesting again, something is putting incorrect data into weewx.sdb fo

Re: [weewx-development] Re: V4.6.0 beta 3

The first time I did it, I just did a apt install python3-weewx_4.6.0b3-1_all.deb. I've not noticed a change log or I don't recall any instructions for upgrading from 4.5.1 to 4.6.0.beta1. So when I downgraded I did a apt remove weewx, then installed beta2. Just now I did an install to get t

Re: [weewx-development] Re: V4.6.0 beta 3

Bill, another question. Normally, when you upgrade between versions, the installer does not touch your skins. Are you running your old pre V4.6 Seasons skin? Or, the V4.6 skin? On Tue, Oct 12, 2021 at 2:27 PM Bill Richter wrote: > Yes, I was thinking that based on the changes and the new value f

Re: [weewx-development] Re: V4.6.0 beta 3

Yes, I was thinking that based on the changes and the new value for checking data first. Just not clear why the database has values, unexpected. I'll set the values to NULL for the sensors that don't exist but have data in the database. I feel lucky so, I'll try beta3 again. On Tuesday, Oct

Re: [weewx-development] Re: V4.6.0 beta 3

Beta 3 uses the presence of data in the database to decide whether or not to produce a plot and/or include the data in the left-hand column. On Tue, Oct 12, 2021 at 11:46 AM Bill Richter wrote: > By "Lots of new readings", do you mean in the templates? Or, plots? > > I mean new readings, leaf* a

Re: [weewx-development] Re: V4.6.0 beta 3

By "Lots of new readings", do you mean in the templates? Or, plots? I mean new readings, leaf* and soil* in the left hand summary high/low. I didn't think to check the database values (sqlite), since nothing shows up in beta2 and I have nothing writing to those things like soilMoist1. But

Re: [weewx-development] Re: V4.6.0 beta 3

The beta looks good on my Ecowitt setup with inside gateway/sensor, outside sensor, 3 outside sensors, and one soil sensor. I do see blank wind+rain graphs and a zero for rain rate in the data table that probably shouldn't be there, considering that I have no such sensors, but it did automagic

Re: [weewx-development] Re: V4.6.0 beta 3

Couple other questions: are the values in your database for soil* and leaf* null? Or, zero? Have you used those database columns for something else? On Tue, Oct 12, 2021 at 5:22 AM Tom Keffer wrote: > Thanks, Bill. > > The transmitter value was fixed in commit 378cd18 >

Re: [weewx-development] Re: V4.6.0 beta 3

Thanks, Bill. The transmitter value was fixed in commit 378cd18 . By "Lots of new readings", do you mean in the templates? Or, plots? Sorry for the trouble! On Mon, Oct 11, 2021 at 8:49 PM Bill Richter wrote: > I