Nearcast data updates

[ldb]

I notice that the data fields for the Nearcast node updated regularly during a recent extended rain event but do not reset daily.  I have to restart the node server in order to update the values.  Would this be a Weatherflow or node server issue?

[bpwwer]

@ldb I'm not sure what you mean by "do not reset daily".  There are only two fields that should reset daily; the daily rainfall and yesterday's rainfall.

I do see a bug that looks like it would always set yesterday's rainfall to zero.  Is that what you mean?

I don't use nearcast data so I don't pay attention to what's there.

[ldb]

What I am seeing is that today's value and yesterday's value do not change overnight.  They remain stagnant until I restart the node server.  The yesterday value did change to the previous today value after last week's rainfall when I restarted it manually.

[bpwwer]

Ok, version 3.0.31 has been published to the store with the fix.  It should work correctly now.

[ldb]

Thank you!  Rain is forecast for this week so I will confirm and report back.

[ldb]

Following up to confirm successful operation of the nearcast data update.

FWIW, I see that Weatherflow amends nearcast rainfall amounts after the fact.  Thus, the rainfall reported in their app may be different from the amount captured by this node server.

Thanks again.

[ldb]

Two rain events this week and the nc node is showing my Tempest local data, not the nearcast data.  Restarting the plugin does update to the nearcast values.

[hart2hart]

On 6/27/2025 at 5:22 AM, ldb said:

Two rain events this week and the nc node is showing my Tempest local data, not the nearcast data.  Restarting the plugin does update to the nearcast values.

What node are you calling NC?  I only see/have Daily Rain in eISY.  Do you have NC rain enabled in the WeatherFlow Tempest app?

I do not have NC enabled.  We have lots of highly scattered storms here in middle Tennessee, so NC is often off since it averages around you -- manual rain gauge verified that at Tempest haptic station readings are much closer most of the time.

I get a daily message (right after midnight) with rainfall from previous day that I use to decide whether to run sprinklers the next day.  Yesterday's rainfall message looked lower than recalled from glance during a hard pop-up rain event.  Looked back and sure enough it was the NC amount and not the local at the station amount.

Is this what you are describing?  That said, maybe WeatherFlow have decided to always substitute it, or they have done it accidently.

EDIT: I restarted the eISY a couple times yesterday working on a ZWave issue and it was well after the rainfall.  Is this suggesting plugin may have picked up the NC amount after the restart even though we don't have NC enabled?

Edited June 28 by hart2hart

[bpwwer]

@Techman Looks like the disconnect and re-connect was caused by the MQTT broker.  It disconnected from the plug-in and the plug-in then properly re-connected.

There is a nearcast node that is created when you configure the plug-in to get it's data from the server vs. from the local hub.  WeatherFlow only provides the nearcast data via the server feed.  That data is supposedly separate fields in the data stream, but I can't control what they push out in the feed.

Since historical rain data is only available from the server, when the plug-in starts, it makes queries to get the historical data and populate those values.  Once it's running, it pulls the current rain data from the feed and updates the historical values as appropriate.

[hart2hart]

Since historical rain data is only available from the server, when the plug-in starts, it makes queries to get the historical data and populate those values.  Once it's running, it pulls the current rain data from the feed and updates the historical values as appropriate.

Thanks @bpwwer .  So that I'm clear, are you describing when I restarted the eISY that the plugin requested data to populate fields and that WeatherFlow responded with the NC rainfall? 

EDIT: My plugin config is for local but it reported the NC amount. Does that mean on restart that it got remote data to populate fields (NC)but that data should have been updated with local data? Edited June 28 by hart2hart

[bpwwer]

7 hours ago, hart2hart said:

Thanks @bpwwer .  So that I'm clear, are you describing when I restarted the eISY that the plugin requested data to populate fields and that WeatherFlow responded with the NC rainfall? 

EDIT: My plugin config is for local but it reported the NC amount. Does that mean on restart that it got remote data to populate fields (NC)but that data should have been updated with local data?

I don't know for sure.

The plug-in uses the rain value in field 12 for rain (both local and remote) and field 19 for nearcast rain.  That implies that they should be separate and you should not be seeing nearcast values at all if you're using just local.

But, it is certainly possible that they update field 12 with nearcast values at some point.

[hart2hart]

I don't know for sure.
The plug-in uses the rain value in field 12 for rain (both local and remote) and field 19 for nearcast rain.  That implies that they should be separate and you should not be seeing nearcast values at all if you're using just local.
But, it is certainly possible that they update field 12 with nearcast values at some point.

Thanks. I’ll try to pay a bit of attention to it and report to them if they are mixing it up.