Files not transfrerred to website

[newburyweather]

edit: Steve, I've just seen your latest post after answering your previous one. A quick comment is that I though the 65 were seconds. I will look at it later, more Christmas socialising to do.

Reply to previous post:
I've just lost my reply because the forum timed me out so a quick summary is

I set EWInterval=10 and updated my data every 30 secs. Not a solution. I still get"*** Data input appears to have stopped". It doesn't bother me but may indicate the problem.

I warmed a probe and the UI showed the the change so the file is being read.

The files are now being transferred by local file transfer and not ftp, process flag is not set.
The dates of the file are current but the contents refer back to yesterday at 16:30. Something obviously went wrong then (probably finger trouble).
Now I'm getting "The weather station is off line..." on the gauge page.

I'm thinking that I should delete all and start again but that won't sort out this issue.

Could you give me a set of timings for say a one minute update. I can supply data as quickly as 10 second intervals.

Cheers

Andy

[steve]

I think the problem must be that it's unable to read your file most of the time, hence the data stopped messages. Others are using this without the same issues. If you look at the dashboard, it will tell you the last time the data was read ("Last Station Update"), so you can see how often it's actually getting new data.

You say the json file timestamps are current but "the contents refer back to yesterday at 16:30". Are you looking at the first entry or the last entry? What do the graphs look like in the UI, compared to how they look using an up to date json file?

I'll add some more debugging to the next build, but you will need debug logging turned on in Cumulus.ini - it would be useful if you had that on already.

[newburyweather]

Now on the web page I get trends which are up to date, The NOW screen shows "
Conditions at local time 21:38 on 29 December 2015" which is now. The gauge page say the station has been off line for 8hours but the UI the last station update was 8 min ago and the gauges have current values. After watching for while it will catch up but then becomes a few minutes delayed.

I also note that the reatimegauge.txt file is 8 hours old so its not being updated and under Cumulus there is no reatimegauge.txt to copy over.

I changed the ExtraFiles local to /web/realtimegaugesT.txt and ticked the process box and now the gauges are update.
So it all now works.

The only outstanding issue is the reading of the file. I have noticed that the failed reading never occurs it the minute ends in 5, ie 21:55, 22:05 etc. so basically it reads successfully ever 10 minutes.

I can't find any timers that relate to that.

I've turned on the Debug log. I'll look at in the morning

Cheers

Andy

[steve]

I think I may know what the problem is with the reading of the file. I think I told you that EWinterval is in seconds - it's actually in minutes

It's a float, so you can supply 0.5 to get 30 seconds, for example.

[newburyweather]

Hi Steve,

Changing EWinterval to 0.5 has fixed the issues.

Thanks for you patience, unfortunately I can't say exactly what fixed what in my case but at least its working now.

I can now add other data into the data file as I get it online.

Great stuff

Andy

[mcrossley]

I think I may know what the problem is with the reading of the file. I think I told you that EWinterval is in seconds - it's actually in minutes

It's a float, so you can supply 0.5 to get 30 seconds, for example.

I fixed the Wiki, that referred to integer values as well.

[steve]

Thanks, Mark. I was intending to check whether the wiki said it was minutes or seconds, as I got it wrong myself, but I see it already correctly said minutes.