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

The driver should emit 'rain' in the LOOP packet. It looks like yours is just emitting 'rain_total'. The SDR driver should be calculating 'rain' from 'rain_total'. See the discussion on genLoopPackets in the *Customizing Guide*. Not sure

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

Yes, that fixed the battery indicator. Running the master branch gets a rain plot, with development no rain plot. There is no rain in the new database since it has not rained today. The rtl_433 is a bit of a moving target, but looks to be working. I will create some rain tomorrow.

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

Not sure about this 'rain' problem, but there have been so many changes in this area since beta-3, that I'm hesitant to draw much of a conclusion. If you're comfortable with git, you could clone the repository and run directly from the development branch. If not, no worries. I'm planning on

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

The battery indicator problem was fixed in commit 378cd18 On Tue, Nov 2, 2021 at 3:01 PM Andy wrote: > > Battery status displayed as numbers > > Clean setup.py install of WeeWX version 4.6.0b3 > Battery Status >

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

No rain plot [image: noRainPlot.png] On Tuesday, November 2, 2021 at 3:01:13 PM UTC-7 Andy wrote: > > Battery status displayed as numbers > > Clean setup.py install of WeeWX version 4.6.0b3 > Battery Status > Outside Temperature Battery 1.00 > Inside Temperature Battery 0.00 > Wind

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

Battery status displayed as numbers Clean setup.py install of WeeWX version 4.6.0b3 Battery Status Outside Temperature Battery 1.00 Inside Temperature Battery 0.00 Wind Battery 0.00 On Saturday, October 16, 2021 at 10:12:03 AM UTC-7 vince...@gmail.com wrote: > I think the missing

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

I think the missing wind direction readings is weewx not reporting that item when the wind speed is zero. -- 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

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

Here's the output from my system (VP2) using a script similar in spirit to that provided by Vince. It's odd that some field's i'd expect, like wind direction, appear to not show up about half the time, but that is probably on my end. But it doesn't appear I am getting any spurious leaf or such

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

Tom - I added a check for the last 12 months and it looks good here for me. No extra fields in my VP2 db in the last year. # this checks a year ago as of this writing for e in `cat elements`; do echo -n "$e "; echo "select COUNT(*) from archive where ${e} is not NULL and (dateTime BETWEEN

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

No, the only customization was to add the windy extension and the fix for the battery status. I did try the real time steel skins but that was removed. I also tried the envoy extension, I see that is still there, I'll remove it and recheck. Removing the un configured, installed envoy

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

I’ll have to check my database when I get home, but if this is widespread, we may have to rethink our strategy of checking for data before generating a plot. On Fri, Oct 15, 2021 at 10:12 PM Vince Skahan wrote: > On Friday, October 15, 2021 at 7:46:37 PM UTC-7 Tom Keffer wrote: > >> What

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

Hi Bill, I've been following the mystery of where the soil and leaf data is coming from. Gary and Tom have given you excellent help in trying to track down the source. I'm hesitant to mention this , because I don't want to confuse the issue, however if you have done some customization in the

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

On Friday, October 15, 2021 at 7:46:37 PM UTC-7 Tom Keffer wrote: > What triggered all this is that V4.6 figures out what to display on the > basis of what's in the database. It's quite possible lots of Vantage > stations are emitting bogus data for missing sensors, but no one ever > bothered

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

What triggered all this is that V4.6 figures out what to display on the basis of what's in the database. It's quite possible lots of Vantage stations are emitting bogus data for missing sensors, but no one ever bothered to plot it. I'll have to check my own database when I get home. On Fri, Oct

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

Yes, I think I'd replace the Davis completely, the next thing will go bad is the super cap in the ISS so another decision time. I already have a spare Accurite on the shelf. All good points about the SDR implementation. I'm not sure about faulty hardware. I don't recall every seeing the

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

On Saturday, 16 October 2021 at 07:07:31 UTC+10 bill.g...@gmail.com wrote: > And another option, replace the ISS. > Yes, but given that ISS data is clearly getting to the console/logger (the loop packets are fine) and since the logger is solely responsible for constructing the hardware

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

And another option, replace the ISS. But the SDR method might be some interesting fun. I have a lot of money invested in the Davis console and their premium logger accessory.; I followed your recommendation. Corrections set to none for those values that are bogus. I'm puzzled why this is

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

Thank you so much for your exhaustive and informative analysis. I like using StdCalibrate/corrections method. I'll set that up now and clear the database etc. I think one final suggestion would be to make an update to the vantage driver documenation, suggesting the same fix for sensors not

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

Thanks, that seems pretty conclusive. There are two archive records in the console output you attached that contain leafTemp1 and friends, we have all of the loop packets for each of those archive intervals and none of the loop packets contain leafTemp1 or friends. This is consistent with the

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

> > This confirms my earlier testing, it's not coming from the console, > something is touching the LOOP packet, and it's the same value all the > time. > Well we don't know that for sure, certainly I've not seen a loop packet emitted directly by the driver/station that contains bogus data,

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

I meant 4.6.0.beta* So weewx has been running for a bit and that bad data is present. leafTemp1 -26.0°F leafTemp2 -82.0°F leafWet1 64 leafWet2 8 soilTemp1 -26.0°F soilTemp2 -82.0°F soilTemp3 -58.0°F soilTemp4 -90.0°F soilMoist1 2 cb

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

On Wednesday, 13 October 2021 at 17:37:33 UTC+10 bill.g...@gmail.com wrote: > DRIVER_NAME = 'Vantage' > DRIVER_VERSION = '3.2.3' > Good, current version of the driver. > output looks 'normal'. I let it run for a while, looking for leafTemp1, > nothing found, > So the output you refer - I am

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

DRIVER_NAME = 'Vantage' DRIVER_VERSION = '3.2.3' output looks 'normal'. I let it run for a while, looking for leafTemp1, nothing found, but the database is getting a new record every 5 minutes. After setting to 0.0 and confirming no none 0.0 records. sqlite> select leafTemp1 from archive

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: $

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

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:

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

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

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

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

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,

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*

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

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

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

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.0. I thought these soil and leaf values (along with others that were new) were defined in the seasons skin.

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

On Thursday, October 7, 2021 at 11:40:06 AM UTC-7 do...@dougjenkins.com wrote: > Docker Compose will not allow you to directly map a file (eg weewx.conf) > from your host to a target file inside a container. > > It does for me. I run my ecowitt weewx instance in docker that way. services:

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

Vince: Actually I was emailing Tom M. yesterday about his docker image. I have it "kind of" working with mqtt and belchertown extensions. my problem is that I use docker compose to setup a weewx "stack" of containers to support my solution (niginx container, mqtt container, mariadb container).

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

If you don't mind building your own, I have a repo up at https://github.com/vinceskahan/weewx-docker that takes a little different tact in building a docker image of weewx for a bunch of os variants all off those mainstream base os.If you build the ubuntu2004 'setup' variant then it's only

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

Tom: I will give your docker image a try and let you know. Been interested in moving my main WeeWx setup to Docker. Will report any issues and any suggestions back to you. Doug On Wednesday, October 6, 2021 at 1:45:49 PM UTC-4 t...@tom.org wrote: > Docker image updated for b3 at

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

Docker image updated for b3 at mitct02/weewx:4.6.0b3 if anyone wants to test/play without affecting your system. I am happy to support people who want to use it or try it. It works for me, but I have not worked closely with many people on supporting their use cases. On Tuesday, October 5, 2021