WSWIN: no impport.csv

[julsing]

Hi,

I have just bought and installed the Meteohub system, wich does a fine job with WD (WeatherDisplay).
However, when I try to use Meteohub with WSWIN, something goes wrong.
I defined all sensors, I ticked the 'Generate WSWIN Data ongoing' box, I did a 'save' and a 'sync reset', I rebuilt the aggregated weather data, I waited for two hours, but I am still missing the 'import.csv' file in the export subdirectory.
The file 'exp01_00.csv' is present in the subdirectory and can be manually imported in WSWIN.

Has anyone got any ideas?

Thanks,


Frank

[skyewright]

Has anyone got any ideas?

Works fine here. I've rebuilt the files quite a few times.

When I do Save on the WSWIN page I usually wait till the export files have been rebuilt right up to date before clicking on the Sync Reset.

Maybe try doing the Sync Reset again?

[julsing]

I had to resend this post three times (!) because for some reason this forumsoftware works funny, to say the least.

I tried a rebuild and a sync reset a dozen times now, to no avail.
There's simply no 'import.csv' flie generated by Meteohub.

The system log says every 3 minutes:
cron.info /USR/SBIN/CRON[12026]: (root) CMD (/bin/pidof wswinimport || /usr/bin/nice /home/meteohub/wswinimport 2>>/data/log/messages) .

The EXP01_00CSV file is updated every 5 minutes.

Thanks,

Frank

[julsing]

Additional info: the update of exp01_00.csv is for some reason now every 10 minutes.

The MAIL command does not work : cron.info CRON[1683]: (root) MAIL (mailed 65 bytes of output but got status 0x0001 ), although email notification is setup and is (test)working.

The DHCP client does not recognize the Gateway info in the DHCP lease. So email notification only works in fixed IP address mode with gateway info manually entered.

The search function of this forum does not work: whatever I type in the search field, no posts are found.

That's it for the time being.

[binbags]

ah ah, thought it was just me that was having problems.

Some mornings I will open up the meteohub link and the forums that I read the day before are all ready for reading again (with no new inputs)some can be weeks/months old.

[skyewright]

Some mornings I will open up the meteohub link and the forums that I read the day before are all ready for reading again (with no new inputs)some can be weeks/months old.

I find that:

Home page
Logon
Forum
[F5] i.e. Refresh after the Forum page has loaded first time.

is a formula that works for me.

As to why, who knows... :S

[skyewright]

Additional info: the update of exp01_00.csv is for some reason now every 10 minutes.

10 minutes is what I'd expect as the interval (for import.csv generation too).

The search function of this forum does not work: whatever I type in the search field, no posts are found.

That's a known problme with the Forum Search. :(
The workaround is to use the other search (at the top right of the page).

[julsing]

Thanks, that's some good news.

Another surprise this morning: I had closed WD at 22:00 hour yesterday and restarted WD this morning at 10:29 AM: there were no data stored! All data between 22:00 and 10:29 were gone!

WD continued where I had left it yesterday: see attachment. WD didn't even notice the gap, which is probably a WD quirk.

Perhaps I was a bit too fast writing out a check for Boris :(

What went wrong?


Thanks,

Frank

[julsing]

I looked at the raw data in the weather subdirectory and they were all there!

How come WD didn't fetch the data between 22:00 yesterday and 10:29 today?
I'll take this to the WD forum.

[binbags]

Some mornings I will open up the meteohub link and the forums that I read the day before are all ready for reading again (with no new inputs)some can be weeks/months old.

I find that:

Home page
Logon
Forum
[F5] i.e. Refresh after the Forum page has loaded first time.

is a formula that works for me.

As to why, who knows... :S

Thanks

Will give this a go as soon as I arrive home tonight.

[skyewright]

How come WD didn't fetch the data between 22:00 yesterday and 10:29 today?
I'll take this to the WD forum.

Have you followed through the FAQ (on Weather-Watch.com) on setting up WD for Meteohub?

I (still) find that it's a good idea to be careful exactly when I start up WD.

I always start WD just after the roll over of a minute.

It was my experience that starting at other times just occasionally led to WD 'missing' out the 'missed data' stage. What I think happens is that a time value gets set at a critical moment, possibly at around the change of minute). Brian reported that he'd solved this, but I think I've seen it since, so I am still careful when I start up 'just in case'.

You can tell if this has happened by looking in View => Data logger setup/info (near right hand side of bottonm row) => [RightClick] => Select All => [Ctrl][C] => paste text into an editor => look at the top wheer you'll see what time WD started looking for data from.

If you spot this problem as it happens (i.e. WD goes straight to current data), the cure is to stop WD straight away (if possible before it writes any fresh data), then edit the time in the [Davis download] section of WDISPLAY.INI to when you want to pick up from, then (carefully) restart WD.

PS. Brian recently added an extra window that shows the initial collection of 'missed data' from Meteohub. If you don't have that, maybe an update would be in order.

[samikki]

I have lost all hope with WD. It missed all my data during the holiday and now it crashes while trying to get data from meteohub. Every day I'm missing out more and more data at WD. :(

But it doesn't matter because I've decided to ditch WD and use only Meteohub instead.

[julsing]

How come WD didn't fetch the data between 22:00 yesterday and 10:29 today?
I'll take this to the WD forum.

Have you followed through the FAQ (on Weather-Watch.com) on setting up WD for Meteohub?

Thanks, David.

Yes, I followed your setup guide and it worked fine as long as WD was running.
I looked at the datalogfile and, indeed, data between 22:13 and 10:40 is missing. I just had the same problem: I shutdown WD at 14:56 and started WD again at 15:12. I also think I know what went wrong. This from the data logger setup/info:
"Date /time (PC) that WD was last running is: 08/04/2008 15:12:00
Decoding missed data, raw actual Error: Given start date "20080804131300" is newer than actual date "20080804131205" (all in UTC). Hint: Omit start and end date to get the very latest recording"
The error is in "Date /time (PC) that WD was last running is: 08/04/2008 15:12:00". WD was shutdown on 14:56.

This confirms your findings re: the time to start WD. It also shows the problem is still there.

I'll take this to the WD forum.

Thanks,

Frank

[skyewright]

It missed all my data during the holiday and now it crashes while trying to get data from meteohub.

If you were away for more than 24hrs (as seems very likely) then you'll probably have come across something that I've reported to Brian on several occasions.

I find that 'missed data' will only collect so much data (around 14hours in my case), then it crashes. :(

The workaround is to take a look in logfiles, note how far it got, then manually set that value in the [Davis download] section of WDISPLAY.INI before you restart WD.

That way you can get there in stages.

But if you simply decide to manage without WD that's your choice. I have been extremely frustrated with it myself on a number of occasions!