Tempest stopped reporting 17 hours ago

[TJF1960]

Hi @bpwwer, the batteries apparently died in my Tempest and it stopped reporting 17 hours ago according to the app. In the app there is a "Offline" indicator. I am not seeing an indication that the NS reports an offline condition.

Is there a way to incorporate the Offline status in the NS? If not, what would be your recommendation for creating a program based on what is reported in the NS that could notify me of a similar condition? My first thought was to use "Hub Seconds Since Seen" value in the NS but I haven't been able to figure out what the number reported indicates. Currently it is 7, last night the highest was 10. Is there a bug with using it? How often is it supposed to be reported to IoP? I think it has reported 7 since I opened the admin console a couple of hours ago but I could be mistaken.

IoP v5.4.5

Weatherflow v3.0.25

Thanks for your time.

Tim

WeatherFlow_12-4-2022_81616-AM.zip

Edited December 4, 2022 by TJF1960
added versions

[bpwwer]

The on-line status is for the node server to PG3 connection, not the node server to WeatherFlow device connection.

WeatherFlow doesn't provide any method to query if it is on-line or not.  It simply broadcasts data over your network and it uses a method that doesn't allow for any type of acknowledgement that the data was received by anyone. 

The seconds since seen is how many seconds have elapsed since the node server has seen a broadcast message from the hub.  The hub sends out a couple of different messages at different intervals the main message being the one with the actual weather data in it.  The main data message should come every 60 seconds.  Rapid wind messages are every 3 seconds (or not depending on the state of the batter charge).  And there are a couple of other messages it sends out.  Since broadcast message can be lost or temporarily blocked on the network, there's no specific time.  The value is going to vary depending on network load, when the hub was started, when the hub starts getting data from the Tempest device, the state of the battery charge.

With all that being said, if the time since last seen gets above 2 minutes, chances are pretty good that something is wrong.

[TJF1960]

@bpwwer, Does that mean that if the Tempest isn't reporting, say because the battery is dead, that the hub will not broadcast? Or does it broadcast even if it is not receiving data from Tempest?           And if it broadcasts even though the tempest is dead, does that mean the "Hub Seconds Since Seen" will reset to zero every time even with no new data?

And lastly, the Hub Seconds value showing in the admin console must not show the current value or change value, in other words, what I am seeing is that it is not updating the seconds. Right now it is still showing 7seconds, the same as when I opened the console a few hours ago.

Thanks!

Tim

[bpwwer]

Yes, the hub will broadcast messages even if the Tempest battery dies.  It just won't broadcast the Tempest data.

The hub has a fixed schedule that it broadcast data on and the node server is doing reporting on a fixed schedule so unless something changes (I.E. restarting the hub) the value shouldn't vary.