Thanks for helping out. It seems that setting to http:// is working. On /debug page I see:
Wflexp.json was a first idea to make export to database over PHP.
After some work. I have decided to chunk it to different data, because HiLows data you don't need every 3 sec. Archive records are made every 1,5,10,15,30 minutes. Setup console data is needed once. etc. etc.
After new idea. I wanted to erase Wflexp.json, but some people started to use it. I had idea to rebuild it, because JSON standard has null, but in my JSON is Davis 1995 "---" as null. "---" is not treated by JSON parser as null, but string.
It was too late. Wflexp.json was used by others. It had to stay in this form.
PHP&MySQL
this is solution with couple of JSONs, depend on data.
- wflreg.json - registration - setup of console and WiFi (no passwords) / on boot
- wflrtd.json - real time data / interval can be set, should be 3-60 sec.
- wflhilow.json - hilows basic/ every 3 minutes
- wflhilowex.json - hilows extended VP2 additional modules like leafs, soil moisture etc. (this is exported for every VP2, even if additional module is not avaible) / every 3 minutes
- lastlog.json - short message asking for last exported to data base datalogger entry. / when new entry was made.
- wfllastlog.json - batches up to 7 data logger data. This is being send up to latest entry, but when connection is stable and all is working, then only last entry in data logger is send. So one json every 30 minutes.
The most important is logger data. WiFiLogger is a logger. It is device to register data. Only WeatherLink.com and local software like WeatherLink PC, Cumulus etc. can download and save this data.
WeatherUnderground is using current weather data and then they are making some statictics from it.
Other weather services the same.
WiFiLogger has FTP export option, but this is the worst technic. WiFiLogger every interval (15 minutes egzample) Is reading flash data from console. Reading 512 Pages takes 2min. 15 sec. In this time console is blocked and can't receive data from sensors.
15/30 minute interval is not very big problem, but for 1 or 5 min. interval it is just not working. Not only export is bad, but also data, because console can't receive it.
WiFiLogger can't save information to its flash memory every 1 minute, because flash can't be used so often.
WeatherLink.com export and PHP&MySQL both has same technic. Ask database what was the last datalogger entry and inform WiFiLogger about last log time.
After that WiFiLogger will send all avaible data, but this is only for the first time, because then every time new data logger entry was made, it is exported in same time when was made.
PHP&MySQL makes full export of data from console to database with RapidFire speed.
It is not finished, but works fine.
I want to add: to HiLows month and year.
Console has very nice graph data. It has 25 entries for some different data.
I don't know which data I would like to export at the moment. I just know I like to make it. There is no software making such thing.
What is nice in graph data (console display purpose). It has data like rain: 25 days back, 25 months back and 25 years back.
The same with wind, temp, etc.
I can give you access to my test database. (please contact on priv.).
When you put address of right php file to your WiFiLogger. Database will be populated with data.
I don't have any website to view weather data, but data base can be check via database manager.
Purpose of PHP&MySQL, why for who:
It can be used by companies to save data on own server (WeatherLink saves only 10000 entries). Maybe for club. Imagine club of 50 farmers with Davis Weather Station. Or 50 schools with some new social project.
I know companies who are gathering and recalculating data to some special charts and sells this info.
PHP&MySQL is closed technic, not by me, but by console firmware. How it works, how it is sharing data etc.
To make easy setup for end user I have made minimal options.
You have to only enable PHP&MySQL option and paste link to php file.
My is:
http://wifilogger.net/wflsql/wflsql.phpThats it.
WeatherLink IP was better. No http link paste, no WiFi password and SSID during setup.
WiFiLogger need these two steps, which are two steps too much for users.
I am using MAC address changed to decimal as ID in database. Called WID (WiFiLogger ID). This number you can have on SETUP-> Network Info.
MAC address is unique, so it can be used. User don't have to write it.
No KEY like it is in WeatherLink IP.
You have to know proper link to proper PHP before export. Treat this link knowledge as a KEY.
+ you can make white/black list in database/PHP.
My plan is to deliver PHP script, MySQL script, export scripts from database to JSONs, some simple tempate to view this JSONs imported from database.
Some raw info in attachement.