Weatherflow: Yesterday's ETO value not transfering to variable from program

[TJF1960]

Hi @bpwwer,

Since switching to Weatherflow my eto values have not been working properly. ETO value is available from the admin console tree:

So I set up  a number of programs to copy the value to a variable at different times throughout the night like this:

If 

Time is 1:00 AM

Then

$iEto_test6=Polyglot/weatherflow/yesterdays eto inches/day

I found all the test variable values were all 0. Forcing a run then also returns a value of 0.

Thanks,

Tim

[bpwwer]

Seems to be working fine for me.  I created variables for temperature, hub seconds sine seen, and eto and all had the right values when I manually ran the program.

New Program - [ID 0008][Parent 0001]

If
   - No Conditions - (To add one, press 'Schedule' or 'Condition')
 
Then
        $Weather_Variable  = 'WeatherFlow' Hub Seconds Since Seen second
        $Int_2  = 'WeatherFlow / AR-00012631' Temperature °F
        $Int_3  = 'something / somethingelse / WeatherFlow' Yesterday's etO inches/day
 
Else
   - No Actions - (To add one, press 'Action')

I have two copies of WeatherFlow installed so I mixed it up and used both.

[TJF1960]

Thank you for the help @bpwwer, I deleted Weatherflow from one slot and installed it in another in an attempt to test. I will have to wait until tomorrow for a value to be present in yesterday's eto in order to test again.

I did notice Hubs Seconds Since Seen transferred to a variable just fine, just not yest. eto.

Question, is there any way for yesterdays eto to carry thru a reboot?

Also, now that I installed Weatherflow in a new slot, yesterdays eto is in mm not inches, how can I change this? 

Lastly, the bottom row on the 2nd picture, is there a way to be able to view the last three items on the screen?

Thanks,

Tim

 

Edited April 2, 2022 by TJF1960

[bpwwer]

No, there isn't anyway to work immediately after a reboot.  It only does the calculation at midnight, because that's when it has the all the data it needs to calculate it.

mm/day is the default units, it will (or should) change the correct units when it next updates the value. 

Only by making the window bigger.  The node server has no control over that, the display is all up to the admin console.