I removed the ET field from the loop and now see ET 0.00 in the Seasons skin. It's winter so this value has little meaning for me. In the growing season though, I do use it in my irrigation system that is fed local data from WeeWX.
On Sunday, December 27, 2020 at 7:38:52 PM UTC-5 [email protected] wrote: > Since the ET value wants to be for the loop period, then I'll just let > weewx calculate this value as I have only ETDay as the smallest interval. > These are the fields I can choose from with my current values from the VP2: > "etday":"0.018" > "etmon":"0.60" > "etyear":"1.95" > > Either way, it doesn't seem to be incrementing in the skin and displays a > suspicious 100 times the loop value. > > > On Sunday, December 27, 2020 at 7:29:25 PM UTC-5 [email protected] wrote: > >> I'm running a VP2+ via WiFiLogger2 >> >> This is a loop from my weewx instance: >> LOOP: 2020-12-27 19:25:13 EST (1609115113) altimeter: None, appTemp: >> 25.040385870017634, barometer: 30.341, cloudbase: 2600.178047939499, >> consBatteryVoltage: 4.76, dateTime: 1609115113.643625, dewpoint: 20.0, ET: >> 0.018, heatindex: 30.0, humidex: 30.0, inDewpoint: 40.586487665962366, >> inHumidity: 30.0, inTemp: 74.0, maxSolarRad: 0.0, outHumidity: 67.0, >> outTemp: 30.0, pressure: None, radiation: 0.0, rain: 0.0, rainRate: 0.0, >> usUnits: 1, UV: 0.0, windchill: 30.0, windDir: None, windGust: 2.0, >> windGustDir: 247.0, windSpeed: 0.0 >> >> This is where it appears in Seasons skin. >> [image: ET.png] >> On Sunday, December 27, 2020 at 6:27:05 PM UTC-5 gjr80 wrote: >> >>> Ultimately ET comes from either your driver or StdWXCalculate, depending >>> on the capabilities of your station (it could also come from another >>> service if your are running a driver that is capable of providing ET as a >>> service). Seasons draws ET data from the database. >>> >>> When you say ‘Seasons displays ET 1.80 in’ where is that? Seasons can >>> display a number of different ET values/aggregates. Remember that the loop >>> packet value is the amount of ET in the period covered by the loop packet, >>> Seasons can display the cumulative amount of ET over an archive period, a >>> day, a week, a month or a year depending on what you are looking at. >>> >>> This construct: >>> >>> <td class="data new_row">$archive.ET.sum.format(add_label=False)</td> >>> >>> is used by Seasons to display day, week, month or year ET, so not really >>> able to be compared to a loop value. >>> >>> Gary >>> >>> On Monday, 28 December 2020 at 08:58:49 UTC+10 [email protected] wrote: >>> >>>> I'm setting up WeeWX 4.2.0 with WeeWx-MQTTSubscribe and after getting >>>> help from Rich, have it working well. >>>> In the Seasons skin, I see that ET is reported at 100 times the value >>>> in the loop packets. >>>> Loop has ET: 0.018 >>>> Seasons displays ET 1.80 in >>>> >>>> Before I make an entry in weewx.conf StdCalibrate Corrections, where is >>>> the value calculated for the Seasons skin? >>>> I only find items like these in the skin files: >>>> #if $day.ET.has_data and $day.ET.sum.raw > 0.0 >>>> #if $day.ET.has_data and $day.ET.sum.raw > 0.0 >>>> <td class="label">$obs.label.ET</td> >>>> <td class="units">$unit.label.ET</td> >>>> <td class="data >>>> new_row">$archive.ET.sum.format(add_label=False)</td> >>>> >>>> -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/fc0fa503-6963-4a48-8b49-f7e14c31efa5n%40googlegroups.com.
