Wojciech, do you have something already planned (a PHP script) that would save the data directly from the WiFiLogger to a SQL database, somewhat similar to what Weather Display does? Would there be enough memory left on the WiFiLogger chip to incorporate the SQL option inside the WiFiLogger chip?
I have made this JSON export file and second one with archive records. This will be transport layer.
I don't know PHP. I could make script on tutorial level to save data to MySQL, but I think I will hire a company to make this.
I wanted to make also template to view this data, but I think backend should be made first.
I have to think about inteface to take out data from MySQL.
What I want from MySQL?
- One owner of MySQL. Multiple stations. - farmer with 5 stations. - Yacht club with 5 stations. - Owner of website who could invite friends.
In general typical hosting with MySQL and PHP is not very good for data aquisition, but for 40 stations should be ok.
- Real Time Data - only one entry per station(current). RapidFire skill.
- HiLows - updated every 3 minutes. Last entry from a day should be archived. HiLows are very nice statistic data, we should not lose it.
- Archive records from datalogger memory fully saved to MySQL. View with charts.
- Basic setup from station. Units, latitude, longitude, elevation, IP, etc.
It is very similar to WL.COM, because they take all data from console. WiFiLogger was built to export all data from console, there is no surprise here.
There is also GRAPH data in console. I have not used it. Probably there is also very nice data. Maybe it is time to examine it?
Wojciech could I ask you for a favour: Could you make available a web page where all the most recent firmware updates for the WiFiLogger would be available as well as the version number and the release date of the last firmware update ... please.
I could try, but I can't promise.
I do know that I make some mess in firmware versions, but this allow me to react fast. When I will have to make additional documents, because I have change one line in firmware, this will cause decrease of firmware updates.
I can't published firmware at the moment. This could damage WiFiLoggers with version 1.xx.
Version 2.0 has this HTTP update system, for version 1.xx there is only one firmware published to migrate to 2.0.