Re: [weewx-user] Re: Shutdown of Tempest-dataflow & display

2022-06-10 Thread Anton vanNwnhzn@GMail

Thanks!
Confirms my view on the matter related to WeeWx.

Further confirmed by effort last night from Weatherflow under their 
'remote control':


- looking at the status reports from Weatherflow apparently repeated 
resets from their side


- such resets resulted in short sequences with 'realistic' data from 
WeeWx [which is listening to the UDP-dataflow between Tempest-hub and WLAN]


=> conclusion that connection from Weatherflow over internet and WLAN 
to/from Tempest-hub still exists


=> conclusion that also interface may exist between Tempest-hub and 
Tempest-sensorhead


=> unclear what is meaning of red Led at the Tempest-hub

=> *NOT* a problem of WeeWx, but of Weatherflow_Tempest

Op 10-6-2022 om 5:29 schreef gjr80:
Further to what Vince said, WeeWX runs the report generator and 
re-generates reports when a new archive record arrives. When using 
software record generation (as I understand is the case with the 
Weatherflow UDP driver) WeeWX synthesises a new archive record when an 
out-of-archive period loop packet arrives from the driver - if no loop 
packets arrive from the driver then no archive records are generated 
and no reports are generated. This may give the appearance that WeeWX 
is 'frozen', but I think this is better characterised as the 'station' 
is frozen; WeeWX is still running just sitting waiting for loop 
packets. A characteristic of this situation, if using one of the 
included skins, is that the date-time displayed on, say, the Seasons 
home page and included plots does not change. This situation is 
usually very apparent when you look at the log, there will be little 
or no activity and certainly no report cycles appearing in the log.


If a driver emits loop packets that contain no observational data then 
WeeWX will generate archive records, albeit lacking in observational 
data, which in turn causes reports to be updated. In this case 
date-times on the likes of the Seasons home page and plots will 
update, but the displayed data may be stale or N/A. Usually not so 
obvious in the logs as everything is working, it's just that no data 
is being presented to WeeWX (actually depending on the extent of 
driver's debug output the lack of data from the driver may or may not 
be evident in the log).


Gary

On Friday, 10 June 2022 at 09:07:10 UTC+10 vince wrote:

On Thursday, June 9, 2022 at 10:46:04 AM UTC-7 ton...@gmail.com
wrote:

is it correct observation that when an interface-driver of
WeeWX has no inputs with changing time-validity, then all
subsequent dataflows also stop & freeze?

If the hub is emitting no data, weewx has no data to process so I
would expect it to show NA and nothing on the graphs.

We cannot help without seeing actual data.

  * https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem

For a WeatherFlow system, always check 'their' server to see if
there is any data there.  The red light means your hub lost the
wifi connection according to a quick search of the WeatherFlow
forums (link)

.
 Did you possibly change something in your network or firewall
configuration on your LAN ?

The problem is almost certainly with your Hub, not weewx or
Domoticz or WeatherDisplay or any other add-on software.


--
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/3PMs0ANkce8/unsubscribe.
To unsubscribe from this group and all its topics, 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/919dda8b-d4c3-4d38-99af-d76040a52682n%40googlegroups.com 
.


--

===
Contactinfo voor Anton van Nieuwenhuijzen:
Email=tonv...@gmail.com
Fax2Mail = (+31/0)84.8397303 [ook Voice2Mail]
===
Deze E-mail en eventuele aanhangende files zijn
alleen bestemd voor de geadresseerde(n).
Als je deze E-mail ten onrechte hebt ontvangen,
dan aub verwijderen en de afzender informeren.

--
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/bea4bd61-ab23-1570-4bd2-7a2b92d7eaef%40gmail.com.


Re: [weewx-user] Re: Shutdown of Tempest-dataflow & display

2022-06-10 Thread Anton vanNwnhzn@GMail

Vince,

Nothing changed in the network.
Therefore have to assume that this defect is 'own initiative' of the 
Tempest-hub.
Sure, hints in 
https://help.weatherflow.com/hc/en-us/articles/360050786593-Troubleshooting-Guide-Setup-WiFi-Hub-Tempest-Device-


The simple remdy of reboot of hub, router and WAPs doesn't correct the 
situation:

means need to dig deeper in the hub's setup for communication.

Op 10-6-2022 om 1:07 schreef vince:

On Thursday, June 9, 2022 at 10:46:04 AM UTC-7 ton...@gmail.com wrote:

is it correct observation that when an interface-driver of WeeWX
has no inputs with changing time-validity, then all subsequent
dataflows also stop & freeze?

If the hub is emitting no data, weewx has no data to process so I 
would expect it to show NA and nothing on the graphs.


We cannot help without seeing actual data.

  * https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem

For a WeatherFlow system, always check 'their' server to see if there 
is any data there.  The red light means your hub lost the wifi 
connection according to a quick search of the WeatherFlow forums 
(link) 
. 
 Did you possibly change something in your network or firewall 
configuration on your LAN ?


The problem is almost certainly with your Hub, not weewx or Domoticz 
or WeatherDisplay or any other add-on software.



--
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/b51ea02d-306a-4230-862f-78f1d0452f15n%40googlegroups.com 
.


--

===
Contactinfo voor Anton van Nieuwenhuijzen:
Email=tonv...@gmail.com
Fax2Mail = (+31/0)84.8397303 [ook Voice2Mail]
===
Deze E-mail en eventuele aanhangende files zijn
alleen bestemd voor de geadresseerde(n).
Als je deze E-mail ten onrechte hebt ontvangen,
dan aub verwijderen en de afzender informeren.

--
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/90c67fab-842a-8c6d-96ad-d6c7fb69961c%40gmail.com.


[weewx-user] Re: Shutdown of Tempest-dataflow & display

2022-06-09 Thread gjr80
Further to what Vince said, WeeWX runs the report generator and 
re-generates reports when a new archive record arrives. When using software 
record generation (as I understand is the case with the Weatherflow UDP 
driver) WeeWX synthesises a new archive record when an out-of-archive 
period loop packet arrives from the driver - if no loop packets arrive from 
the driver then no archive records are generated and no reports are 
generated. This may give the appearance that WeeWX is 'frozen', but I think 
this is better characterised as the 'station' is frozen; WeeWX is still 
running just sitting waiting for loop packets. A characteristic of this 
situation, if using one of the included skins, is that the date-time 
displayed on, say, the Seasons home page and included plots does not 
change. This situation is usually very apparent when you look at the log, 
there will be little or no activity and certainly no report cycles 
appearing in the log. 

If a driver emits loop packets that contain no observational data then 
WeeWX will generate archive records, albeit lacking in observational data, 
which in turn causes reports to be updated. In this case date-times on the 
likes of the Seasons home page and plots will update, but the displayed 
data may be stale or N/A. Usually not so obvious in the logs as everything 
is working, it's just that no data is being presented to WeeWX (actually 
depending on the extent of driver's debug output the lack of data from the 
driver may or may not be evident in the log).

Gary

On Friday, 10 June 2022 at 09:07:10 UTC+10 vince wrote:

> On Thursday, June 9, 2022 at 10:46:04 AM UTC-7 ton...@gmail.com wrote:
>
>> is it correct observation that when an interface-driver of WeeWX has no 
>> inputs with changing time-validity, then all subsequent dataflows also stop 
>> & freeze?
>>
>> If the hub is emitting no data, weewx has no data to process so I would 
> expect it to show NA and nothing on the graphs.
>
> We cannot help without seeing actual data.
>
>- https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem
>
> For a WeatherFlow system, always check 'their' server to see if there is 
> any data there.  The red light means your hub lost the wifi connection 
> according to a quick search of the WeatherFlow forums (link) 
> .
>  
>  Did you possibly change something in your network or firewall 
> configuration on your LAN ?
>
> The problem is almost certainly with your Hub, not weewx or Domoticz or 
> WeatherDisplay or any other add-on software.
>
>
>

-- 
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/919dda8b-d4c3-4d38-99af-d76040a52682n%40googlegroups.com.


[weewx-user] Re: Shutdown of Tempest-dataflow & display

2022-06-09 Thread vince
On Thursday, June 9, 2022 at 10:46:04 AM UTC-7 ton...@gmail.com wrote:

> is it correct observation that when an interface-driver of WeeWX has no 
> inputs with changing time-validity, then all subsequent dataflows also stop 
> & freeze?
>
> If the hub is emitting no data, weewx has no data to process so I would 
expect it to show NA and nothing on the graphs.

We cannot help without seeing actual data.

   - https://github.com/weewx/weewx/wiki/faq-how-to-report-a-problem
   
For a WeatherFlow system, always check 'their' server to see if there is 
any data there.  The red light means your hub lost the wifi connection 
according to a quick search of the WeatherFlow forums (link) 
.
 
 Did you possibly change something in your network or firewall 
configuration on your LAN ?

The problem is almost certainly with your Hub, not weewx or Domoticz or 
WeatherDisplay or any other add-on software.


-- 
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/b51ea02d-306a-4230-862f-78f1d0452f15n%40googlegroups.com.


[weewx-user] Re: Shutdown of Tempest-dataflow & display

2022-06-09 Thread Ton vanN
Additional info.
WeatherDisplay parallel reading output from the Tempest-hub, same as 
Domoticz reports fixed values since that time, also with actual time-stamp, 
not the 'freezing' as for WeeWX.

Op donderdag 9 juni 2022 om 19:46:04 UTC+2 schreef Ton vanN:

> Some 24 hours ago I observed a 'freezing' of the WeeWX-picture at 
> https://vannwnhzn.nl/WeeWX0/index.html
> Still continues.
>
> First thought is that upload for the html-file has stopped.
> Because for upload using the FTP-function in WeeWX, implicitly it means 
> that WeeWX has to be checked.
> Observation in WeeWX is that all files of WeeWX still get actual 
> datestamp, but contents have completely been frozen on approx. June 8th, 
> 16:25
> Restart of WeeWX (regardless of route) has no effects: no further visible 
> processing.
>
> This afternoon (as second thought) the penny dropped that this was also 
> the time that Weatherflow_Tempest as datafeeding sensor through UDP went on 
> strike:
> Tempest hub shows red light, meaning that the dataflow from the sensor (or 
> the hub itself) has problems.
> Also see at the Weatherflow-server that data & display has been frozen at 
> the time mentioned above.
> Locally in Domoticz I see that since that time the data from the 
> UDP-sniffer is also solid as a rock.
> Hard reset of the Tempest hub has no effect.
>
> *Question:*
> is it correct observation that when an interface-driver of WeeWX has no 
> inputs with changing time-validity, then all subsequent dataflows also stop 
> & freeze?
> *Or* is this apparently simultaneous event just an unhappy coincidence? 
> *Or* some aspects specific for the Tempest hub & interface-driver? 
>

-- 
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/7e792e16-03e4-486d-b2db-a6ad16b7e2a9n%40googlegroups.com.