Thanks for the detailed ET tutorial.
I do have a couple of lingering questions.
For my purposes, it isn't critical to use the MQTT server for data
acquisition. So, I reset the WeeWX instance to stock/clean state and ran
./bin/wee_config --reconfig selecting Vantage driver, answering ethernet to
connection method. In the weewx.conf I do notice I can choose LOOP1, LOOP2,
or both. I left all at the defaults.
I made one change to the resulting weewx.conf file adding loop_on_init =
True
With the stock/default settings, I let weewx run for awhile before and
after the hour.
The first report cycle, the Seasons skin had no ET displayed.
As you said, after the top of the hour, there is ET displayed. However, it
is 0.00, the High/Low has 0.00 0.00 The loop packet has dayET: 0.013
I see this in the current.inc and it looks like there should be data
displayed.
#if $day.ET.has_data and $day.ET.sum.raw is not None and $day.ET.sum.raw >
0.0
<tr>
<td class="label">$obs.label.ET</td>
<td class="data">$current.ET</td>
My question is this. If the console is reporting ET values, and the skin
wants to show ET values, when would the skin display the ET value?
On Monday, December 28, 2020 at 11:09:16 PM UTC-5 tke...@gmail.com wrote:
> In WeeWX, ET is treated like any other extensive quantity: a record
> contains the amount of evaporation that happened during the archive period,
> *not* the total for the day. Think of it as anti-rain.
>
> One complication: the Vantage series hardware emits ET only on the top of
> an hour. It is the amount of evaporation that happened during the hour. So,
> if you use hardware record generation, expect a non-zero value only once an
> hour. If you use software generation, it will appear with every archive
> record.
>
> That's how WeeWX treats it. As for how it's arriving from your MQTT feed,
> I have no idea.
>
> Finally, how it appears in a skin depends on what tag is used. Usually you
> want something like $day.ET.sum, which would be the total ET for the day,
> just like $day.rain.sum is the total rain for the day.
>
> -tk
>
> On Mon, Dec 28, 2020 at 6:30 PM G Hammer <gary....@gmail.com> wrote:
>
>> Well, it reset the etday at midnight I'm going to say. Nothing has been
>> displayed until now and ET is accumulated mostly during the day.
>> I'm puzzled with this one as it makes zero sense.
>> The way ET works on the console, the WLL and weatherlink.com, and in the
>> real-time stats from WiFiLogger is as the various parameters that make up
>> ET grow during a day, the etday is updated. At the end of the day, it is
>> zeroed.
>>
>> So, the ET value in WeeWX does not accumulate/add that value each time it
>> is reported. It stays 100 times what is in the loop. etday=1 ET=100,
>> etday=2 ET=200, if etday stops growing at 2, ET will remain at 200.
>> Somewhere, the calculation is just flat incorrect. WeeWX has no idea what
>> device is sending the data as the driver is not tied to hardware. No more
>> records are being sent than are reflected in the loop records, archives are
>> being created every 300 seconds.
>> I'm going to install a different skin tomorrow and see if this remains
>> the same.
>> Stay tuned.
>>
>> On Mon, Dec 28, 2020 at 6:58 PM bell...@gmail.com <bell...@gmail.com>
>> wrote:
>>
>>> You and me both... It might be worth seeing what a full day looks like.
>>> Also, if it would work for you using the day/month/year ET values might
>>> make sense...
>>>
>>> On Monday, 28 December 2020 at 17:31:42 UTC-5 gary....@gmail.com wrote:
>>>
>>>> Perhaps I need a tutorial on ET as used by reported by WeeWX.
>>>> So, I have made the setting change suggested.
>>>> Loop values have remained at ET: 0.0
>>>>
>>>> I'd think the actual value sent by the logger should be the value
>>>> displayed by the skin. Kinda like weatherlink does.
>>>>
>>>> [image: ET-WL.PNG][image: ET-WW1.PNG]
>>>>
>>>> On Monday, December 28, 2020 at 11:10:13 AM UTC-5 gary....@gmail.com
>>>> wrote:
>>>>
>>>>> This seems to work. Currently ET at the logger is 0.002 so it is being
>>>>> reported in loop packets as 0.0
>>>>> I'll see later in the day, but it sounds like exactly what is needed
>>>>> in this case.
>>>>>
>>>>> On Monday, December 28, 2020 at 10:26:13 AM UTC-5 bell...@gmail.com
>>>>> wrote:
>>>>>
>>>>>> I think the next step would be to capture the loop packets between
>>>>>> two archive records and manually sum up the ET values. Or you could
>>>>>> estimate the number of loop packets between archive records and if it is
>>>>>> close to 100 call it done. Net, it seems like everything is working as
>>>>>> expected. MQTTSubscribeDriver is creating the packets. WeeWX is summing
>>>>>> the
>>>>>> ET values in the packets to create the archive record.
>>>>>> Mulling this over a bit more, I think setting contains_total = true
>>>>>> for your etday field might be the answer. This was added for MQTT rain
>>>>>> data
>>>>>> that is cumulative to calculate a delta for WeeWX.
>>>>>> rich
>>>>>>
>>>>>> On Sunday, 27 December 2020 at 23:24:59 UTC-5 gjr80 wrote:
>>>>>>
>>>>>>> Also, remember under a traditional Davis console/logger/vantage
>>>>>>> driver setup you will see approx 120 loop packets per five minute
>>>>>>> archive
>>>>>>> record. So seeing an archive record value that is 100 times a loop
>>>>>>> value is
>>>>>>> not unreasonable for a cumulative field such as ET or rain. The
>>>>>>> difference
>>>>>>> here is that a traditional Davis console/logger/vantage driver setup
>>>>>>> you do
>>>>>>> not see loop ET values.
>>>>>>>
>>>>>>> The only way to know if it it working properly is to understand who
>>>>>>> is emitting what and then do the maths to confirm the result one way or
>>>>>>> another.
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>> --
>>> 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/d258f315-8929-46f3-99b1-0e11dee81541n%40googlegroups.com
>>>
>>> <https://groups.google.com/d/msgid/weewx-user/d258f315-8929-46f3-99b1-0e11dee81541n%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+...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CALBRR-1uXPeXk3mMaXsW7K1iT7CQaZEEjEGoD%3DmvMEiDoXLbvg%40mail.gmail.com
>>
>> <https://groups.google.com/d/msgid/weewx-user/CALBRR-1uXPeXk3mMaXsW7K1iT7CQaZEEjEGoD%3DmvMEiDoXLbvg%40mail.gmail.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/6cccd6b6-bb8d-41c7-b5be-9dce0f44125bn%40googlegroups.com.
