Thanks to all the advice I fixed the realtime.txt file, it was a question of setting the spacing.
I note that among the various options, I can use the wifi logger to load data on WU. I opened a free WU account, but in the settings it asks me whether to use RapidFire or not. What's the difference ? What interval should RapidFire give? Does the wifi logger manage all this stuff or is it overloaded ??? At the moment I'm uploading the files to WL Pro with a 10 minute interval, via FTP I'm sending the realtime.txt file for my site ..... if I add also WU, will everything work?
Some weather services don't want to have data upload more often than every 5 minutes.
RapidFire is a service in WU which accept 2.5sec. intervals, but in WiFiLogger minimum 3s. In my opinion it is for wind observation, temperature don't need such fast uploads.
WeatherLink IP is uploading to WL.COM data with interval 1min. This is for real time data.
WeatherLink.com accept also archive history data from logger. It is exported every 1 hour in WL IP, but WiFiLogger makes this when data is written to console flash memory. So when logger is set to 1 min, then WiFiLogge will send it to WL.com every 1 min.
This history data can be downloaded to your PC using WeatherLink PC software. Ten you will have history data table and graphs on your PC. In 1995 year style, but it is working fine.
Other services accept real time data. Only WeatherLink.com accept archive records. This is a littlebit different data than real time. It is statistical data from arch interval time like 15, or 30 min.
About how many uploads can make WiFiLogger?
When you open debug page of WiFiLogger.
http://WFL_IP/debug then there is text like : "Client response time: 202" this is in milliseconds.
Timeout is set to 15 sec. because of some services like wow.metoffice.gov.uk. It has big latency.
When you start to open new free accounts on different weather services you will notice that only WL.COM and WU.COM has servers good enought for all those weather stations. I like to use also PWS like this station here:
https://www.pwsweather.com/obs/JULIANOWO.htmlWhen WiFiLogger is triggered to make upload then it is a queue. So it should take 2-3 sec. to make uploads to all services, but sometimes can take more up to 15 sec. when connection is dropped and another service is served by WiFiLogger. Debug windows will show you the truth.
WiFiLogger has problem with one thing still, but I think I know what to do with it.
When WFL is reading archive from data logger memory, then console is freezeing. In this state It don't accept info from station, like temperature etc.
Reading of this memory can take up to 2 min and 15 sec.
So FTP export to CSV file it is not suitable for intervals like 1, 5 minutes.
WL.COM archive export works better because WL.COM server is sending info from when data should be uploaded. Then this operation take less than 1 sec. Great success.