Since 4.6, seeing ET (no data) in Seasons

[Ryan Stasel]

Using the Ambientweather API driver, and since 4.6, I'm seeing Evapotranspiration in Seasons, yet my Vantage Vue doesn't have that data, and it's not reported in Ambientweather, so I'm unclear why Seasons is showing it. 

Is this a bug with Seasons, with driver, or did apt-get replace a template that I forgot I edited way back when? 

Thanks! 

[Tom Keffer]

Hi, Ryan

This is a (now) known issue: https://github.com/weewx/weewx/issues/737

The workaround is simple: set ET to 'software' in StdWXCalculate:

[StdWXCalculate]
    [[Calculations]]

        ...
        ET = software

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/37b3d4fe-6dc6-4fbc-99d5-7e2b5ed30a46n%40googlegroups.com.

[Ryan Stasel]

Thank you sir! 

[Ryan Stasel]

with 4.6.1 out now, should we change these back to prefer_hardware?

[Tom Keffer]

If you were to ever get a weather station that can calculate ET, prefer_hardware would automatically switch to using the hardware value. Otherwise, it doesn't matter.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/650d8c27-fe54-454b-a163-00d8f6080dacn%40googlegroups.com.

[Ryan Stasel]

Hi Tom,

Was never getting ET data (have always had a Vantage Vue), but the chart is still showing in Seasons, which sounds like it's intentional. However, how do I purge that bad ET data out of the sqlite database? I assume it's just a lot of 0's. 

[Tom Keffer]

Now I'm confused. You said you're using the AmbientWeather API driver. But, you have a VantageVue? Why not use the Vantage driver?

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/196433c4-9dd6-4850-9c3b-bbb32ba0ba0bn%40googlegroups.com.

[Ryan Stasel]

ha. you're right. I have a Meteobridge NanoSD, and to my knowledge, it can only do one LOOP/LOOP2 "destination", which in my case goes to Davis WeatherLink (I had an issue a couple years ago when Weathercat was taking the loop input, and then when I went to send to WeatherLink, I wasn't getting some of the aggregate data (windrun, total rain, etc) and that turned out to be this limitation. So I send data from MB to AmbientWeather, and then re-ingest that into WeeWX. AmbientWeather though doesn't show any kind of ET, and it only showed up since 4.6... 

Hopefully that answers. Looking at other thread going about errant data, guess I should check and see if ET is still being set in the DB... 

[Ryan Stasel]

So I just did a "select datetime,ET from archive;" and surprisingly, there are a TON of very small values in the archive. 

1237254720|1.17847719661706e-05

all the way to

1596513360|1.39902428567705e-05

Appears to be a byproduct of when I imported my data into weewx from whatever I used (might have been Meteobridge, or Meteotemplate, or Weathercat, I honestly can't recall. Looks like since I've been running weewx though there are just null values. 

Should I be able to just blank out all the data by doing:
update archive set ET = NULL where ET IS NOT NULL;

Would it also make sense to do a vacuum after? 

Thanks! 

[Tom Keffer]

That looks sensible. Make a backup first.

Vacuuming won't make any difference. It's for large deletions.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7c7a8ad7-2eb2-4320-8f2f-67e0c3723f41n%40googlegroups.com.