Data stopped from Weatherflow Tempest

Ask a Question
, , ,
1

Hi, I have a Weatherflow Tempest that has been working fine. However, I went away for a few days and noticed that my data on my website was stuck at the same readings for the last few days. On return home, I have rebooted my computer but the data from the weather station is still not being picked up.

I have checked on the Tempest app and can see that the station is sending data up to the Weatherflow site OK. It’s just that Weather Display is not now picking it up from that site.

How do I get Weather Display to restart picking up data? What are the signs I should be looking out for? Thanks.

Windows 10. WD Ver 10.37S138

2

what shows in the separate running cronweatherflow program?

3

Hi Brian

The cronweatherflow program wasn’t running. I have now started it and it seems to be working. Thanks. Should this be started at the same time as weatherdisplay?

4

yes it should have been

5

Hi Brian

found out what the problem was. I have Malwarebytes installed and it had blocked and quarantined the cronweatherflow.exe program!

Put the cronweatherflow.exe program in the Malwarebytes ‘allow’ list and all is solved. Hope this helps anyone else with similar problems!

6

I started having this problem yesterday. cronweatherflow version 7.1 is running. It shows the correct station id 31760. The tempest app shows the station is alive and well. Weather display version 10.37S143 shows it is receiving data and logging such, but the data never changes. I have another app that is successfully getting data from the tempest web socket. I have attached the last few entries from the cronweatherflow.log below. Any help would be appreciated.
Thanks,
Doug

2023-05-30 17:05:44.818; rtcSocketSrvProv Finalizing …
2023-05-30 17:05:44.818; CloseThreadPool (0 Queued / 0 Busy / 0 Idle) begin …
2023-05-30 17:05:44.834; Worker Threads Runnning: 0
2023-05-30 17:05:44.851; Checking Virtual Threads …
2023-05-30 17:05:44.868; All Virtual Threads released.
2023-05-30 17:05:44.883; CloseThreadPool (0 Queued / 0 Busy / 0 Idle) end.
2023-05-30 17:05:44.898; rtcSocketSrvProv Finalized.
2023-05-30 17:05:44.914; rtcSynSocket Finalizing …
2023-05-30 17:05:44.930; rtcSynSocket Finalized.
2023-05-30 17:05:44.946; rtcWinSocket Finalizing …
2023-05-30 17:05:44.961; rtcWinSocket Finalized.
2023-05-30 17:05:44.979; rtcSockBase Finalizing …
2023-05-30 17:05:44.996; rtcSockBase Finalized.
2023-05-30 17:05:45.014; rtcWinSock Finalizing …
2023-05-30 17:05:45.033; rtcWinSock Finalized.
2023-05-30 17:05:45.049; rtcDataSrv Finalizing …
2023-05-30 17:05:45.066; DoneSessions Begin …
2023-05-30 17:05:45.081; DoneSessions Acquired
2023-05-30 17:05:45.097; DoneSessions UnLockList begin (0)…
2023-05-30 17:05:45.114; DoneSessions UnLockList free (0) …
2023-05-30 17:05:45.132; DoneSessions UnLockList end.
2023-05-30 17:05:45.147; DoneSessions LockList begin
2023-05-30 17:05:45.163; DoneSessions LockList free …
2023-05-30 17:05:45.177; DoneSessions LockList end.
2023-05-30 17:05:45.193; DoneSessions ExpList free …
2023-05-30 17:05:45.209; DoneSessions ExpList end.
2023-05-30 17:05:45.224; DoneSessions Releasing …
2023-05-30 17:05:45.238; DoneSessions Released.
2023-05-30 17:05:45.254; DoneSessions end.
2023-05-30 17:05:45.269; rtcDataSrv Finalized.
2023-05-30 17:05:45.285; rtcConn Finalizing …
2023-05-30 17:05:45.300; rtcConn Finalized.
2023-05-30 17:05:45.317; rtcTimer Finalizing …
2023-05-30 17:05:45.332; rtcTimer Finalized.
2023-05-30 17:05:45.347; rtcConnProv Finalizing …
2023-05-30 17:05:45.362; rtcConnProv Finalized.
2023-05-30 17:05:45.378; rtcLink Finalizing …
2023-05-30 17:05:45.393; rtcLink Finalized.
2023-05-30 17:05:45.409; rtcInfo Finalizing …
2023-05-30 17:05:45.424; rtcInfo Finalized.
2023-05-30 17:05:45.440; rtcThrPool Finalizing …
2023-05-30 17:05:45.455; Releasing Thread Pool
2023-05-30 17:05:45.470; Thread Pool released.
2023-05-30 17:05:45.485; Releasing Thread List
2023-05-30 17:05:45.500; Thread List released.
2023-05-30 17:05:45.515; Releasing Sync List
2023-05-30 17:05:45.530; Sync List released.
2023-05-30 17:05:45.545; rtcThrPool Finalized.
2023-05-30 17:05:45.560; rtcLog Finalizing …
2023-05-30 17:05:45.575; rtcLog STOP.

7

There was an update of WD in the last couple of days that refers to fixing a Weatherflow issue. Have you tried upgrading to see if that fixes the problem?

8

That fixed it. Thanks. I had checked the latest news and saw the latest was in January and confused the latest version 10.37S Build 148 with the one I was running 10.37S 143. So assumed I was current Maybe I need better glasses.

Anyway, all is well.
– Doug

9

thats a good question – i have version 8.7 cron – its working however temp data freezes – i have to exit and save – the load up again to get it to refresh and be current – help

10

Worked with Brian and ironed out all my issues with cronweatherflow. The latest upload build of WD fixes the import missed data from the Tempest.

11

d crooks — can i see your fixes

12

atellyer – was your problem fixed

13

Yes. My problem was caused by Malwarebytes thinking that the cronweatherflow.exe program was dodgy and then quarantining it. I simply added it to the Malwarebytes ‘allow’ list, reinstalled the cronweatherflow.exe program, and all was good.

14

The link I posted shows my current setup.