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 NULL or 0. Assuming either value is valid, I didn't look at the source, forcing the field to NULL should prevent display.
So I guess what you'd suggest is: stop weewxd. set the leafWet1 to NULL run wee_reports check the web page to see if leafWet1 is gone. On Tuesday, October 12, 2021 at 9:37:36 PM UTC-7 gjr80 wrote: > 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 - > something else is creating the bogus data. That could be any of a myriad of > sources; the driver, a core WeeWX service or some third party service. It > is impossible to say what the source could be without knowing how WeeWX is > configured, ie what driver, what services etc are loaded and how are they > configured. That is what weewx.conf/wee_debug will tell us. > > Since you seem to have installed the deb package you should be able to run > wee_debug by simply typing: > > $ wee_debug —info > > to display the wee_debug output on the console. You can add the —output > option to redirect the output to a file if you wish. Alternatively, if you > are not comfortable using wee_debug you can just take copy of your > weewx.conf, sanitise it by obliterating any sensitive info (user names, > passwords, API keys etc) and post the sanitised file. > > Gary > > On Wednesday, 13 October 2021 at 14:19:25 UTC+10 bill.g...@gmail.com > wrote: > >> ## 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 deb archive. So, I'm perplexed as well that on install the Seasons >> files were not restored. I copies them from git to get them back in place >> and confirm the are the most recent dev versions. >> >> So the code change to the Seasons skin seems to be working, but I'm a bit >> stuck now on tracing why data is being loaded into weewx.sdb from a value >> that is not output by Vantage. IE in the LOOP packet leafWet1 = 0. >> >> I'd expect the test to be showvalue if not NULL or 0. >> >> Since I set the values to NULL and the LOOP packet is saying 0 and >> that's what's being put into weewx.sdb, I'm not expecting the label or >> graph to be generated via if $year.leafWet1.has_data or >> $year.leafWet2.has_data. >> >> sqlite> select leafWet1 from archive where leafWet1 IS NOT NULL; >> 0.0 >> 0.0 >> 0.0 >> 0.0 >> sqlite> >> >> So I struggle here, >> 1. LOOP data shows 0, but the label and graph is displayed. >> 2. LOOP data for other values doesn't appear to exist yet it's in the >> database now. >> 3. Just to eliminate database issues, I've set leafWet2 and leafWet2 to >> NULL so the graph and label shouldn't print. >> 4. but this is new behavior from beta2 to beta3. >> >> My brain hurts. >> >> On Tuesday, October 12, 2021 at 8:01:20 PM UTC-7 gjr80 wrote: >> >>> 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. See LICENSE.txt for your rights. >>> ## Version: 4.6.0b4 >>> #errorCatcher Echo >>> >>> Gary >>> >>> >>> On Wednesday, 13 October 2021 at 12:15:35 UTC+10 bill.g...@gmail.com >>> wrote: >>> >>>> 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 >>>> for certain fields that have no real sensor. >>>> >>>> So to make sure I had the new Seasons skins, I apt remove weewx, then >>>> apt install python3-weewx_4.6.0b3-1_all.deb >>>> weewx# ls -l >>>> total 16 >>>> drwxr-xr-x 2 root root 4096 Oct 12 18:54 font >>>> drwxr-xr-x 2 root root 4096 Oct 12 18:54 lang >>>> drwxr-xr-x 2 root root 4096 Oct 12 18:54 NOAA >>>> -rw-r--r-- 1 root root 2732 Oct 12 18:52 sensors.inc >>>> >>>> >>>> >>>> On Tuesday, October 12, 2021 at 5:35:22 PM UTC-7 Bill Richter wrote: >>>> >>>>> >>>>> 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 to beta3 and added the battery patch. >>>>> That >>>>> patch fixes the battery reading. >>>>> >>>>> First, >>>>> sqlite> update archive set leafWet2=NULL; >>>>> sqlite> select leafWet2 from archive where leafWet2 IS NOT NULL; >>>>> sqlite> >>>>> >>>>> (time passes, at least 5M) >>>>> >>>>> sqlite> select leafWet2 from archive where leafWet2 IS NOT NULL; >>>>> 8.0 >>>>> sqlite> >>>>> >>>>> And now I have data in leafWet2! >>>>> >>>>> On Tuesday, October 12, 2021 at 4:04:06 PM UTC-7 Tom Keffer wrote: >>>>> >>>>>> 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 <bill.g...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> 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, October 12, 2021 at 2:15:36 PM UTC-7 Tom Keffer wrote: >>>>>>> >>>>>>>> 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 <bill.g...@gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> 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 imagine my surprise to see, yes there is non 0 data >>>>>>>>> in >>>>>>>>> there. >>>>>>>>> >>>>>>>>> OK, so I don't think I want to delete the tables. Should the >>>>>>>>> values be set to 0 or NULL? It looks like the value should be set to >>>>>>>>> NULL. >>>>>>>>> The puzzle for me is the difference between beta2 and beta3. As well >>>>>>>>> as >>>>>>>>> why I can't edit the skin to remove the generation of soilMoist1. On >>>>>>>>> the >>>>>>>>> other hand, it would work 'normally' if the soilMoist1 was 0 or NULL. >>>>>>>>> No >>>>>>>>> idea how those values would get in the database. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Tuesday, October 12, 2021 at 5:23:25 AM UTC-7 Tom Keffer wrote: >>>>>>>>> >>>>>>>>>> Thanks, Bill. >>>>>>>>>> >>>>>>>>>> The transmitter value was fixed in commit 378cd18 >>>>>>>>>> <https://github.com/weewx/weewx/commit/378cd18b42366391dba818dcd1d1581a509d46de> >>>>>>>>>> . >>>>>>>>>> >>>>>>>>>> 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 <bill.g...@gmail.com> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> I was running V4.6.0. beta 2. I upgraded. Lots of new readings >>>>>>>>>>> for soil* leaf* with values for sensors my Davis Vantage doesn't >>>>>>>>>>> have. >>>>>>>>>>> Also the transmitter value went from OK to 0.00000. I thought >>>>>>>>>>> these soil >>>>>>>>>>> and leaf values (along with others that were new) were defined in >>>>>>>>>>> the >>>>>>>>>>> seasons skin. No luck in removing them. The lack a valid >>>>>>>>>>> transmitter >>>>>>>>>>> value was also a deal breaker. I've reverted from beta3 to beta2. >>>>>>>>>>> I >>>>>>>>>>> neglected to try the Standard skin while on beta3. No issues >>>>>>>>>>> upgrading >>>>>>>>>>> from beta1 to beta2. >>>>>>>>>>> >>>>>>>>>>> No I don't have a 'test' environment for this, so further >>>>>>>>>>> diagnostics are not easy. I think I might just wait until V4.6.0 >>>>>>>>>>> and >>>>>>>>>>> upgrade then. This is the package I used, >>>>>>>>>>> python3-weewx_4.6.0b3-1_all.deb >>>>>>>>>>> On Tuesday, October 5, 2021 at 3:13:10 PM UTC-7 Tom Keffer wrote: >>>>>>>>>>> >>>>>>>>>>>> The Seasons skin has been parameterized. It should now work out >>>>>>>>>>>> of the box for any combination of types that appear in the >>>>>>>>>>>> extended wview >>>>>>>>>>>> schema. See PR #702 <https://github.com/weewx/weewx/pull/702>. >>>>>>>>>>>> >>>>>>>>>>>> http://weewx.com/downloads/development_versions/ >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>> Google Groups "weewx-development" group. >>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>> it, send an email to weewx-developm...@googlegroups.com. >>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>> https://groups.google.com/d/msgid/weewx-development/4dec109b-7d06-439c-953a-46fdfcc0b3abn%40googlegroups.com >>>>>>>>>>> >>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-development/4dec109b-7d06-439c-953a-46fdfcc0b3abn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>> . >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "weewx-development" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to weewx-developm...@googlegroups.com. >>>>>>>>> >>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/weewx-development/199909aa-2fe7-4829-bd84-2f4e0a6dfd8dn%40googlegroups.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/weewx-development/199909aa-2fe7-4829-bd84-2f4e0a6dfd8dn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "weewx-development" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to weewx-developm...@googlegroups.com. >>>>>>> >>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/weewx-development/48f63cae-debe-4ab8-908a-23e91e8f507cn%40googlegroups.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/weewx-development/48f63cae-debe-4ab8-908a-23e91e8f507cn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/4c69171b-8207-45c7-9b49-c033bb563231n%40googlegroups.com.
