The json values.txt you provided includes no per-period ET value, only cumulative values. So what is calculating that ET value? If the json file you posted is a loop ‘packet’ from the wifi logger then does the MQTTSubscribe driver calculate ET from successive cumulative ET values? StdWXCalculate does not calculate loop based ET so that really only leaves the driver.
Then look at the archive record and ask the same question, who is providing the ET value? The MQTTSubscribe driver has a genArchiveRecords() method so the driver and not StdArchive is responsible for creating and emitting an archive record. Does the driver calculate ET or is it received from the wifilogger (Davis stations include hourly ET values in the archive record at the top of the hour, all other archive records have ET=0, again don’t know what the wifilogger does)? If not then in this case StdWXCalculate can step in and calculate ET or since ET is appearing in loop packets StdArchive could calculate ET by summing the loop packet ET values seen during the archive period. I would suggest looking at the archive records coming directly out of the driver(note that is different to observing loop packets/archive records on the console when running WeeWX directly, running WeeWX directly shows packets/records after all services have processed the packet/record), if ET is there then you answer lies in the driver. If it is not it is StdWXCalculate or StdArchive that is calculating it then we need to look at those services. Gary On Monday, 28 December 2020 at 13:17:53 UTC+10 gary....@gmail.com wrote: > Ok, I have no idea what I would ask them for. > The WiFilogger sends good data to the MQTT server and MQTTSubscribe > retrieves those accurately into loop packets. > > That one of them is multiplied by 100 for display doesn't seem to be on > either of them. > > > On Sun, Dec 27, 2020, 8:40 PM gjr80 <gjrod...@gmail.com> wrote: > >> OK, never used a wifilogger or MQTTSubscribe, suggest you get some help >> from the respective developers. >> >> Gary >> On Monday, 28 December 2020 at 11:18:52 UTC+10 gary....@gmail.com wrote: >> >>> Here's an exported json file content. >>> >>> >>> On Sunday, December 27, 2020 at 8:09:34 PM UTC-5 gjr80 wrote: >>> >>>> So where was the ET coming from that was in the loop packet? The >>>> vantage driver does not emit field ET in loop packets and the >>>> StdWXCalculate service does not calculate an ET field for loop packets. >>>> Also are you using software or hardware archive record generation, there >>>> are some peculiarities to the hardware archive record ET value emitted by >>>> the Vantage driver/station. >>>> >>>> Gary >>>> >>>> On Monday, 28 December 2020 at 10:57:05 UTC+10 gary....@gmail.com >>>> wrote: >>>> >>>>> 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 gary....@gmail.com >>>>> 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 gary....@gmail.com >>>>>> 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 gary....@gmail.com >>>>>>>> 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 a topic in the >> Google Groups "weewx-user" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/weewx-user/oo6K0FVMny4/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> weewx-user+...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/8a28d3c5-4df5-425f-ac7e-7e20dbcfa7a1n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/8a28d3c5-4df5-425f-ac7e-7e20dbcfa7a1n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9d0fba52-67e3-4854-b286-aedb588753f1n%40googlegroups.com.
