does software see /work with it as a IP data logger?
does software see /work with it as a IP data logger?
does software see /work with it as a IP data logger?
I believe so. One of the testers who has yet to weigh in was running it with WeatherLink.
Finally, we can talk about it. (https://www.wxforum.net/Smileys/default/icon_smile.gif)and I have done my penance... hi Wojtek,
It's the real deal, folks. I am one of the ones privileged to test this unit out. Link to my WU below, with rapid fire updates.
does software see /work with it as a IP data logger?
It would be really cool if it had AC capability directly instead of it being fed by the internal batteries :)
This is pretty awesome nonetheless!!
I'm assuming that, like the OEM Davis WL-IP data-logger, that *IF* the Console is being powered by the #6625 AC adapter that the internal 3xC-cell batteries are not truly necessary and could be eliminated. Yes? No? Maybe?
is it better that the davis IP data logger in relation to more than 1 connection?
Sweet! Any idea on pricing?
Curiosity question: What's the RF output power and thus 'nominal' operating range?
So if this only works with Cumulus or weatherlink one at a time just like the Davis logger and I'm using Cumulus already and not changing, I'm trying to see advantage of this over WL data logger which BTW is less money.
I'm not turning computer off because Cumulus and website uploads its needed, while wifi is nice it isn't something I really need so what advantage would I have using this product?
Wojtek, would it be possible as a future firmware upgrade to communicate with a mysql database? I have had some of my customers ask about that and I have to refer them to purchasing an envoy 8x which is an extra expense if they already have a console.
Please take it into consideration that WiFiLogger will have more functions in the future.
Please take it into consideration that WiFiLogger will have more functions in the future.
And, it's WiFi. There have been many posts here wanting a wireless connection from the console to computer or Internet. WiFi logger has already solved one problem for me in that manner.
I have idea to make program for server. PHP script which will receive data from WiFiLogger and put it to MySQL database.
I'd like to see/read the instructions on how one inputs/loads the (a) network name (SSID) and network security key (password) into the device...so the WiFi modem will talk to it; and, then, (b) the Davis WL password so its transmissions will be recognized (and not blocked) at the Davis website.Not sure if I can answer, or really understand Weatherlink.com.
....Before WiFiLogger I had to run Weatherlink on my computer for data to show on Weatherlink.com (free, non-subscription version)....
....Before WiFiLogger I had to run Weatherlink on my computer for data to show on Weatherlink.com (free, non-subscription version)....
But that would not have been a WLIP logger, would it?
Just wondering if anyone here has tested this with Weather Display?
Stuart
This is great but isnt the pricing too high? A belfryboy logger costs around 65$ I guess, add a raspberry pi to it for 35$ and you get same capability in 100$. Agreed that this has built in software to upload etc, but you can achieve the same using weewx etc on raspberry.
No, I have the USB logger connected to an Envoy and the computer and only run Weatherlink on occasion to maintain the .wlk data files and then switch back to Cumulus. I have again been experimenting with VVP to run both Cumulus and Weatherlink at the same time. But before WiFiLogger weatherlink.com did not show any data nor on the map until I was actually running Weatherlink. Now with WiFiLogger weatherlink.com has constant data. Not sure yet what consequences if I have WiFiLogger uploading to weatherlink.com and then also run Weatherlink off of the Envoy/USB logger on the computer.....Before WiFiLogger I had to run Weatherlink on my computer for data to show on Weatherlink.com (free, non-subscription version)....
But that would not have been a WLIP logger, would it?
Wojtek,Sweet! Any idea on pricing?
Pricing:
WiFiLogger price is $169. I think resellers will sell it with discount. You should expect -15% at the beginning.
There will be second product. WiFiLogger Lite with price $109. Also expect -15% at the beginning.
...
At the proposed price point these things should sell like hotcakes! Well done! I will likely get one. And I for one do not care about WL.com BTW, any chance we will see a Bluetooth version?
Ryan at Scaled Instruments for your US/North America dealer!!
Bluetooth is local communication, it will not give you a big advantage.exactly, not sure what the advantage is
QuoteBluetooth is local communication, it will not give you a big advantage.exactly, not sure what the advantage is
yes
but a WiFi connection does that and more,which is what this has
no need for bluetooth...what advantage is that?
yes, that is the only advantage, to get the data via bluetooth to your phone and an app running on that
but you would need to be in range
and then if you are in range, you would be able to see the console anyway
but getting the history data into an app via bluetooth would only be an advantage if no wifi connection, e.g remote location?
yes
so, really, no real need for bluetooth, agree?
great that it can generate a local wifi
I'd like to see/read the instructions on how one inputs/loads the (a) network name (SSID) and network security key (password) into the device...so the WiFi modem will talk to it; and, then, (b) the Davis WL password so its transmissions will be recognized (and not blocked) at the Davis website.
yes
so, really, no real need for bluetooth, agree?
great that it can generate a local wifi
If I understand how this thing works, I can buy a WiFi logger and put it in my second console and after I get credentials from CWOP, WU, etc., I can upload two sets of data and view them on the internet without needing a second computer! An excellent concept!YES! and Weatherlink too!
When and where will I be able to buy one here in the US?Wojtek will answer that.
If I understand how this thing works, I can buy a WiFi logger and put it in my second console and after I get credentials from CWOP, WU, etc., I can upload two sets of data and view them on the internet without needing a second computer!Ron not sure, but I think doing that will that will confuse APRS, unless you put in different coordinates. How far away though....
If I understand how this thing works, I can buy a WiFi logger and put it in my second console and after I get credentials from CWOP, WU, etc., I can upload two sets of data and view them on the internet without needing a second computer!Ron not sure, but I think doing that will that will confuse APRS, unless you put in different coordinates. How far away though....
I have finished programming firmware. I have sent newest version of software to 4 members of WXFORUM who agreed to use and test WiFiLogger.
I am preparing first lot for shipping and waiting for information from those forum members if they are agreed that product is good enough to be released.
I think on 15 of June it should be available in US.
I had negotiated with Scaled Instruments to take care about US and Canada distribution. Good news is that I have confirmation that You will be able to buy WiFiLogger through SI.
I was informed that SI is the best distributor. I hope You will confirm that.
If somebody want to buy one before 15 of June, please contact me by PM, or contact Scaled Instruments. Please note, that shipping Poland -> USA takes minimum 14 days.
Ron not sure, but I think doing that will that will confuse APRS, unless you put in different coordinates. How far away though....That may be correct!
I have finished programming firmware. I have sent newest version of software to 4 members of WXFORUM who agreed to use and test WiFiLogger.
I am preparing first lot for shipping and waiting for information from those forum members if they are agreed that product is good enough to be released.
I think on 15 of June it should be available in US.
I had negotiated with Scaled Instruments to take care about US and Canada distribution. Good news is that I have confirmation that You will be able to buy WiFiLogger through SI.
I was informed that SI is the best distributor. I hope You will confirm that.
If somebody want to buy one before 15 of June, please contact me by PM, or contact Scaled Instruments. Please note, that shipping Poland -> USA takes minimum 14 days.
Great news! Your selection of Scaled Instruments was outstanding. Ryan knows more about Davis' equipment than the folks at Davis support. He is honest, fairly prices Davis equipment and stands behind what he sells. But the console I want to put the wifi logger in has a firmware of 1.82 and if I understand your specs, I need 1.90. Not sure whether I can update my firmware, this console has a code of A60202... so that might mean it was made in 2006. I know the console that has 1.9 cannot be updated for the latest firmware.
Now I am confused. I know for a fact my consoles cannot be updated beyond 1.9. Does that mean the WiFi logger won’t work?
Now I am confused. I know for a fact my consoles cannot be updated beyond 1.9. Does that mean the WiFi logger won’t work?Ron I am currently testing it on 1.9 and it works fine.
Now I am confused. I know for a fact my consoles cannot be updated beyond 1.9. Does that mean the WiFi logger won’t work?Ron I am currently testing it on 1.9 and it works fine.
Yes, PWS Weather is one of the several auto uploads at whatever interval you choose
http://www.pwsweather.com/obs/KOMOKA2.html
Enjoy,
Paul
So, this new tool or “toy” will upload to pwsweather.com but Davis’ Weatherlink won’t? Goofy. Can’t wait to buy one!
So, this new tool or “toy” will upload to pwsweather.com but Davis’ Weatherlink won’t? Goofy. Can’t wait to buy one!
And power efficient (0.3 Watts).
Yes I have watched what is main used and I have programed it. So WU, PWS are common for everything.
FTP file is similar to WeatherLink FTP export.
I will program a few more weather sites, but I see that there is a many ideas come to me from other users. We will try make something new to weather data sharing.
But first of all I will enhance WiFiLogger with external GSM module. I have many questions for that. Should be useful.
Please go to ebay, google etc. and search for "Angle DC 3.5*1.35mm USB" this cable has little bigger head than original one, but its fit, maybe it's slightly tight, but works fine.
3-4 days, but I have programmed Sleep Mode to disable wifi chip for programmable interval.
5 min won't change anything, because it need 20-30s to connect to router, check time, download settings from console, make upload. When you want to export archive records it's 2min, 15 sec for full memory.
I think 15 min interval it's minimum to have profit with this function.
I did not tested yet how much time it will work on baterries with this mode. When I will have this data I will inform you.
My estimation is about 1 month.
I think having an upload minimum of 15 minutes or so will turn some people off as many, myself included, prefer 5 minutes.
I think having an upload minimum of 15 minutes or so will turn some people off as many, myself included, prefer 5 minutes.
What's the issue here though? Isn't this discussion just about battery life if the unit is run on battery power alone?
If you want network/Internet connectivity of any type (except maybe via BT LE), whether that's cabled (eg IP logger) or WiFi, AND reasonably frequent data updates then that's going to call for AC mains power (other than for short-term use eg to cover mains outages). The only alternative is a reasonably chunky solar PSU, ie panel+charger+battery, which gets progressively more costly at higher latitudes. But in general isn't the answer mains power and then you can update as often as you wish.
I am confused. If the update interval can be, for example, 5 minutes or so using AC power, then this limitation, in my mind, is moot. I thought the answer given by WiFiLogger applied to both AC and DC power of the console.
At the proposed price point these things should sell like hotcakes! Well done! I will likely get one. And I for one do not care about WL.com BTW, any chance we will see a Bluetooth version?
Thank you. A lot of good words were written under whole this post.
There is newer hardware to use with bluetooth onboard, but I would need another a few month to change it.
Bluetooth is local communication, it will not give you a big advantage.
I am thinking about external GSM addon. I should will be succeed. This is more important than Bluetooth.
WL.com it's under construction, we will see what it will can do. I don't know how about watching data on WL.com, but for transmit data from console to WL.com they have best solution of all.
No oder website accept archive data from data logger. All needs only current data. They accept also HiLows data.
For Davis weather stations it's the best.
For me to check data best site is www.pwsweather.com I like its data presentation.
What is GSM?General Service for Mobile = the mobile or cellular network
We are talking about GSM/GPRS Cellular Modem. Use your cellular provider service to connect to the Internet.Yeah, I knew that. :oops:
You need SIM card to use it.
…
I will sale through Ryan for USA + Canada and For EU I want to have contract with UK reseller. I won't sell directly. I won't make competition to my dealers.
…
I have informed Ryan I want one of your loggers as soon as he receives them from you. I assume the logger comes with instructions in English that even a retired accountant like me can understand and apply? I assume you log into a web page from a computer, say, 192.168.1.1 and enter the various sites I want to upload data to including their respective credentials assigned to my station, enter my coordinates, etc.?
My idea was to have reseller from UK, who can provide service to EU and Australia.Thanks and fair enough as either the US or UK are relative the same from a purchasing perspective to Australia
My idea was to have reseller from UK, who can provide service to EU and Australia.
Leaving certification out of the decision, I have never experienced any issues expect some new wifi device out of the US which identifies that you it is not the designated region (US).
Today I have only good news.
- Scaled Instruments will have WiFiLoggers in distribution in less than 10 days. 5-7 days I hope.
- PRODATA WEATHER SYSTEMS from UK will take care of distribution on EU market. I will deliver first set in 10 days.
@johnd: IIRC your company will be the EU distro for this product. Could we know when it's going to be up for purchase?
I have just realize that whole first lot has firmware with this CWOP fault, also this one in Europe, which will be available soon. That is shameful. I am sorry.
On the first post you can find new firmware file "WiFiLogger112.zip" + and instruction how to make update "WiFiLogger update.pdf"
Version 1.12 has additional features:
- wow.metoffice.gov.uk - upload function
- Pause duration parameter
- Weather Underground wind gust fixed
Now. I will try to add MQTT function.
What is MQTT and would that be the basis for firmware version 1.13?
MD5 d3112c9d54a9e05f5ffb232db94bfae0 is for ZIP file.
You have to unzip WiFiLogger112.zip
Then you will have folder WiFiLogger112 and inside you will find WiFiLogger112.bin and html folder with another 10 files.
BIN file has own form
HTML files has separated area to upload.
Does anyone think that there might be enough posts on the WiFi logger to ask The Management here for a separate WFL subforum?
Does anyone think that there might be enough posts on the WiFi logger to ask The Management here for a separate WFL subforum?
Does anyone think that there might be enough posts on the WiFi logger to ask The Management here for a separate WFL subforum?
I think it's fine the way it is - and we have entirely enough separate fora.
Does anyone think that there might be enough posts on the WiFi logger to ask The Management here for a separate WFL subforum?
I think it's fine the way it is - and we have entirely enough separate fora.
I know what you mean, but:
1. This obviously isn't a Davis product and so discussion doesn't really belong here. Ditto Weatherlink. I guess the only other potential home might be 'Other weather station hardware' but then it's not hardware in a sensor sense.
...
such as the MeteoBridge Nano (http://meteobridge.com/wiki/index.php/Meteobridge_NANO)
Probably more devices to come.
...
There is not much difference. The hardware seems the same for both devices and fits in the same area as the Davis logger. The software will be different, but both address the same market and will do similar things in similar ways.
...
such as the MeteoBridge Nano (http://meteobridge.com/wiki/index.php/Meteobridge_NANO)
Probably more devices to come.
...
What is the difference between the Nano and the WiFi Logger that has been discussed in this thread? I thought the latter was a totally new concept!
...
such as the MeteoBridge Nano (http://meteobridge.com/wiki/index.php/Meteobridge_NANO)
Probably more devices to come.
...
What is the difference between the Nano and the WiFi Logger that has been discussed in this thread? I thought the latter was a totally new concept!
When was the last time Davis released an enhancement to its VP2 product line? Shortly after California became a state? Seriously, the latest is probably the aerocone rain bucket which added little, if any, to the VP2.
There is not much difference. The hardware seems the same for both devices
When was the last time Davis released an enhancement to its VP2 product line? Shortly after California became a state? Seriously, the latest is probably the aerocone rain bucket which added little, if any, to the VP2.
Bit like predicting earthquakes isn't it? You never know when the next one is coming - could be sooner, could be later.
And guess I should add that Davis haven't been sitting still - there have been two major product launches in the past year or so - EM and wl.com 2.0. But EM especially doesn't get much attention here - it's obviously not really a hobbyist product.
And for the record, they killed the USB Weatherlink program—a great and wonderful decision!
[The deciding factor will be the price, I think.
When was the last time Davis released an enhancement to its VP2 product line? Shortly after California became a state? Seriously, the latest is probably the aerocone rain bucket which added little, if any, to the VP2.Well they did give us the SHT31, and that by no means is peanuts in the PWS world.
There is not much difference. The hardware seems the same for both devices
Nah, the HW is quite different. The ESP8266 in the WFL is limited in many ways. The Vocore2 in the new MB nano is capable of running a small Linux distro like LEDE or OpenWRT which is used by other, older MB devices IIRC. The deciding factor will be the price, I think. As others mentioned, the existing user base is a big plus and it's a lot easier to add new features to a more capable SOC.
When was the last time Davis released an enhancement to its VP2 product line? Shortly after California became a state? Seriously, the latest is probably the aerocone rain bucket which added little, if any, to the VP2.Well they did give us the SHT31, and that by no means is peanuts in the PWS world.
Go big or go home. :-PWhen was the last time Davis released an enhancement to its VP2 product line? Shortly after California became a state? Seriously, the latest is probably the aerocone rain bucket which added little, if any, to the VP2.Well they did give us the SHT31, and that by no means is peanuts in the PWS world.
Forgot that. I would elaborate but that may be viewed as being off-topic.
Ron, john nailed it.
You can upload data as frequent as 1 minute and even use WU Rapid Fire option on battery power but those frequent updates consume more battery power. Disabling Rapid Fire and stretching those other sites up to 10 or 15 minute updates will drastically reduce battery consumption.
I posted this back at the beginning of the thread about about Battery power.
Power Consumption. It does use the juice but not as much as I thought. I am uploading to 4 sites at these intervals. 10 minutes, 9 minutes, 1 minute, and WU Rapid Fire at 3 seconds. The batteries lasted
for 4 days and 15 hours. Voltage got down to 3.45 this morning so I plugged it back in.
Have we figured out how much battery life is consumed if we change the default 30 minute "archive interval" to 5 minutes? Not talking about how many sites we upload to, rapid fire, etc, but simply the archive internal. 30 minutes is just too long if I'm trying to export data from Wifilogger.
Curious in the case of power outages in storms.
Have we figured out how much battery life is consumed if we change the default 30 minute "archive interval" to 5 minutes? Not talking about how many sites we upload to, rapid fire, etc, but simply the archive internal. 30 minutes is just too long if I'm trying to export data from Wifilogger.
Curious in the case of power outages in storms.
Personally I don't like running IP loggers on battery power AT ALL - I've never found it very reliable with WeatherlinkIP loggers. My picture is that internal console batteries can only deliver 4.5v at most rather than the 5v of the mains supply. Then the batteries don't need to deplete far before the voltage might start to drop back from 4.5v and (cabled) Ethernet seems quite sensitive to this.
I'm no electronics engineer and don't know how accurate this picture is and how it might relate to WFL. But for higher power devices like the IP logger, WFL (or eg Nano) I'd always feel more comfortable with a 5v input than relying on batteries.
My preferred backup solution would be to use a UPS on the 5v input - either a mains UPS or eg a 5v power booster for smartphones (though I'm never sure which ones can be left permanently plugged in to the mains and still provide a 5v supply).
What bothers me about batteries is that you can never be sure about their state of charge.
I wonder if the WFL has an archive memory to replay old records from in case of network failures.Wojtek will need to answer this, but it does have archive FTP ability which I think is the logger's stored data at whatever interval logger is set.
One of the things I noted that took me a while was when I entered my data to send information to WU, after I updated the information...all of the fields were blank so I thought I was doing something wrong. I entered this information a number of times. I then realized that it must be sending the information to the WiFi Logger, but just wasn't showing the data on that page. I guess that is how it works, because it is sending the information to WU.
Again, I don't know if this is just me, but is anyone else having issues getting to the info page or connecting to the WiFi Logger after the initial setup? I will enter the IP address assigned to it in the address bar and try to connect to it, but it doesn't connect.
Thanks,
Rick
Have you read the manual? I also had some difficulty setting the logger up but when I compared my setup to the screenshots in the manual, I figured it out fairly quickly.
Rick which web browser do you use?
Please in a first step make update of WiFiLogger.
In firmware 1.11 is a little bug with display information on exports page. Please go to the first post and download firmware 1.13 and update manual.
You need to know IP number of WiFiLogger which was granted by DHCP service in you router. You can login to your router and there will be list of devices DHCP IP. You can use WeatherLink PC to find WiFiLogger inside your local network. You can scan your network using special soft (http://www.advanced-ip-scanner.com), you can press red button once more for 3-4s to enable SETUP MODE with open wifi "WiFILoggerSetup" connect to it and open page http://192.168.4.1/info.html there you can find your IP. Write it down, this number is key to access to you WiFiLogger from home network. Please remember to RESTART WiFiLogger to disable SETUP MODE. In SETUP MODE WiFiLogger won't connect to the Internet.
It works like this.
In first step HTML file is downloaded then after 2 sec, JAVASCRIPT is downloading your settings.
Can you use different web browser?
Chrome, FireFox, Edge, Internet Explorer 11
Please remember that firmware upgrade has two steps.
(not sure why one says Update and the other says Upload?).
This does require a router? Correct
Looking for a solution with someone that doesn't have traditional wired internet service. They are using a wireless cell signal (jetpack) Its basically a hot spot only.
The Verizon jetpack will take one of the WIFI WAN routers like Peplink Balance routers but this gets expensive and complicated for a novice.
This does require a router? Correct
Looking for a solution with someone that doesn't have traditional wired internet service. They are using a wireless cell signal (jetpack) Its basically a hot spot only.
The Verizon jetpack will take one of the WIFI WAN routers like Peplink Balance routers but this gets expensive and complicated for a novice.
Yes. It's required Internet access via WiFi medium. In practice needs a router with WiFi.
One unit is working with mobile router GSM/LTE and WiFi. This solutions is very good.
You can also make Hot Spot WiFi network using Android phone.
This does require a router? Correct
Looking for a solution with someone that doesn't have traditional wired internet service. They are using a wireless cell signal (jetpack) Its basically a hot spot only.
The Verizon jetpack will take one of the WIFI WAN routers like Peplink Balance routers but this gets expensive and complicated for a novice.
Please remember that firmware upgrade has two steps.
1. update using BIN file
2. Upload about 10 html files.
Some updates don't required to upload all HTML files. I will inform you when it's needed.
From version 1.11 to 1.12 or 1.13 you need to upload all html files.
From version 1.12 to 1.13 only export.html
I also would like to know how to get the data from my PWS to the software like Weather Display or Cumulus, which in turn can be displayed on a web page. Using the Weather Underground information is okay, but on my WU page it doesn't seem to keep track of the "history" like the pages generated by Cumulus does.
It is displaying a temp which is about 5-7 degrees higher than what it actually is. Is it possible the logger is creating any heat?
WiFiLogger I have the Davis VP2 console with the device installed, one thing I have noticed the last couple of days is my console is showing the inside temp inaccurately. It is displaying a temp which is about 5-7 degrees higher than what it actually is. Is it possible the logger is creating any heat?
IMHO, Davis should have provided (at least) an optional way of 'exteriorizing' the console sensor.
IMHO, Davis should have provided (at least) an optional way of 'exteriorizing' the console sensor.
Which there is on the current (wireless) Envoy consoles. The position of the RJ11 socket on the cabled consoles is used IIRC. Unfortunately because the Envoy board sits in the case less conveniently on the main VP2 console it's not possible to do the same there, to the best of my recollection.
Is this the one? (https://www.davisnet.com/product/temperature-probe-with-rj-connector/)
If so it has worse accuracy than the Sensirion one inside and I think it only allows whole C° or F° values. It's not a true solution, either. I never used it but isn't this handled as an add-on temp sensor and not a replacement for the internal one?
Measuring indoor humidity remains a problem. Your argument about the problems presented by the design of the VP2 console is a bit circular, since Davis were responsible for that design and could, presumably, have allowed for the possibility of an external sensor.
For what it is worth, I have two VP2 consoles side by side. Both are on AC power, one has the new WiFiLogger the other has the “green-dot” USB Davis logger. Both consoles report the same inside temperature, which is about 4 to 5 degrees warmer than reality. The console that has the WiFilogger has the SHT31 whereas the console that has the Davis logger is 10 years old and does not. Draw your own conclusions but since I don’t rely on the consoles to give me inside temperatures, I really don’t care. Others may have different thoughts.
@WiFiLogger: Isn't there a 3rd mode where the WFL automatically pauses eg. minutely to allow 3rd party software to access the console? This is actually the recommendation by Davis for 3rd party SW. In these pauses it becomes possible to read/catch up archive data.
On another note, I think it would be beneficial to everyone to make the FW update process completely seamless and automated. No phases, distinction is not necessary between static HTML data and FW blob, etc., from a user perspective. Leaving the possibility for uploading individual static files is a good idea as it's possible to customise the web layout, but I think it's better to hide these details from those who don't care. A smartphone app would be ideal, but obviously it's another development investment, both in time and money.
This is a problem with all loggers except the original serial one. The subject has been beaten to death for the USB logger (for which it tends to cause the most trouble) in numerous other threads.
I believe that I am correct in saying that the Envoy allows the plugging in only of an external temperature sensor. Measuring indoor humidity remains a problem. Your argument about the problems presented by the design of the VP2 console is a bit circular, since Davis were responsible for that design and could, presumably, have allowed for the possibility of an external sensor.
I believe that I am correct in saying that the Envoy allows the plugging in only of an external temperature sensor. Measuring indoor humidity remains a problem. Your argument about the problems presented by the design of the VP2 console is a bit circular, since Davis were responsible for that design and could, presumably, have allowed for the possibility of an external sensor.
Just to clarify that, the so called "External temperature sensor" than can be plugged directly into the Envoy when plugged becomes a replacement for the Internal on board sensor and is reported as Internal temp so effectively even though one might call it an external sensor it is actually being reported as the Internal temperature. A Temp/Humidity sensor plugged directly to the Envoy simply does not work and blows the temp way out (on the temp side only but does not affect the internal humidity) but then there is no real issue with the Humidity anyway.
I believe that I am correct in saying that the Envoy allows the plugging in only of an external temperature sensor. Measuring indoor humidity remains a problem. Your argument about the problems presented by the design of the VP2 console is a bit circular, since Davis were responsible for that design and could, presumably, have allowed for the possibility of an external sensor.
Just to clarify that, the so called "External temperature sensor" than can be plugged directly into the Envoy when plugged becomes a replacement for the Internal on board sensor and is reported as Internal temp so effectively even though one might call it an external sensor it is actually being reported as the Internal temperature. A Temp/Humidity sensor plugged directly to the Envoy simply does not work and blows the temp way out (on the temp side only but does not affect the internal humidity) but then there is no real issue with the Humidity anyway.
Because of the way Temperature/Humidity sensors work, a temperature error (due to the sensor being 'heated') leads to a humidity reading error as well, even if the sensor is otherwise working perfectly. I assume that even if an external temp sensor is plugged in, the Envoy's humidity reading is influenced by the temperature that the internal sensor is seeing (and would be reporting if the external sensor were not plugged in). I therefore don't see a way, even with the Envoy, of getting accurate internal humidity readings.
No the external connection switches the internal temp sensor off and uses the so called external temp which is essentially the internal temp relative to the humidity sensor which is not affected by internal heating
I have a question to the WiFiLogger users. Should I leave manual trigger for pause with manual duration setup? Or should I make only auto pause enable option, or auto pause should works always?
RapidFire Updates http://wiki.wunderground.com/index.php/PWS_-_Upload_Protocol (http://wiki.wunderground.com/index.php/PWS_-_Upload_Protocol)
RapidFire Updates allow you to update weather station conditions at a frequency up to once observation every 2.5 seconds. Web site visitors will see these observations change in real-time on the wunderground.com site.
-A real-time update should look almost like the standard update.
-However, the server to request is: rtupdate.wunderground.com, not weatherstation.wunderground.com
-And, please add to the query string: &realtime=1&rtfreq=2.5
-where rtrfreq is the frequency of updates in seconds.
I am testing now auto pause for Cumulus/WeatherLink connection.Hi Wojtek, great but still not 100% understanding, and having the manual option seems like the most appropriate to suit different software possibilities.
It works perfectly. I don't know why I didn't make it in a first step.
I have a question to the WiFiLogger users. Should I leave manual trigger for pause with manual duration setup? Or should I make only auto pause enable option, or auto pause should works always?
Hi Wojtek, great but still not 100% understanding, and having the manual option seems like the most appropriate to suit different software possibilities.
Enjoy,Paul
So if I don't use Cumulus I don't need to use the auto-pause feature when 1.14 is released?
Wojciech, I'm experiencing what seems to be a bug in v1.13 where it is sending the wrong temperature to Weather Underground. The temperature field is reading the same as the high temperature within each cycle period. Can you please check to see if that is the case? I want the normal temperature which is the average temperature the way I set it up. Thanks.
Hmm. It's actually quite a big limitation if the WFL doesn't handle and send archive records.
Do you think that WeatherLink or Cumulus is sending archive records to WU, PWS, WOW Awekas etc.?
What more do you like to do with archive records?
It would be nice if WFL continued to send data to services based on the archive records of the console. Basically that's it.
Do you think that WeatherLink or Cumulus is sending archive records to WU, PWS, WOW Awekas etc.?I don't think Cumulus is sending archive records to those sites, however Cumulus has settings to "Catch Up" to send to PWS, WB, WU and WOW from the time of Cumulus shut down and a restart.
I will make this option if it's really needed. Then Uploads will be synchronized with arch. interval. It's changing a lot, so time is needed for that.Yes, that is what I was expecting for the upload frequency to be aligned with the archival period (must match). Whereas, RapidFire would still use immediate LOOP data many times inbetween.
Yes, that is what I was expecting for the upload frequency to be aligned with the archival period (must match). Whereas, RapidFire would still use immediate LOOP data many times inbetween.
I'm asking because WeeWx (open source, so it's easy to verify) reads loop packets to allow plugins access to them, but actually uses archive records for display and upload
How did you determine that eg. Cumulus is using LOOP data for uploads and not archive records?
WeatherLink + WU plugin, before WU upload WeatherLink is connecting to console and download LOOP data.It's worth noting that before upload you can only query archive or hilo data, not real-time loop data, since that needs to be accumulated for the duration of the archive interval (OK, technically you can query LOOP data but makes little sense here). Isn't there a bit of mix up?
I am using 30 min arch. interval. Maybe when somebody use 1-5 min, that will change in those programs.For the software that sync uploads to the archive interval, it's most logical to use the archive records. Loop is only interesting of you want to see quick changes in conditions like wind gusts.
Best export option is WL.com. This system takes all data in proper way from console. Almost transfering whole memory to WL.com server.Yeah, it's Davis on both ends so whatever they see fit...
You are asking for arch. records, but really good data is HiLOWS. WeatherLink serves you day hi/low, but console has monthly and yearly as well. These are also exported to WL.com. Very good statistical data from the console and nobody is asking for it.Most probably because looking at historical data and extremes (~ hilo data) for a given period is what online services excel at. You can select a dynamic view you're interested in and not confined to the console's capabilities.
I forgot to say, and you likely already knew this, that the Catch up data is then at the logger interval. It is highly recommended that the logger and Cumulus data are set at the same interval otherwise issues can arise.QuoteDo you think that WeatherLink or Cumulus is sending archive records to WU, PWS, WOW Awekas etc.?I don't think Cumulus is sending archive records to those sites, however Cumulus has settings to "Catch Up" to send to PWS, WB, WU and WOW from the time of Cumulus shut down and a restart.
Paul
TBH I'd assumed that with most software the default was to use only LOOP data, with archive being reserved for catch-up scenarios. But not looked into it in great detail.
A note to Davis owners:Some changes may have been made through the ongoing development of CumulusMX so the extent of LOOP2 use may have changed.
I am experimenting with the use of the LOOP2 packet. The current code uses this for two purposes. First, it uses the 'peak 10-minute gust' value, to avoid the problem where a gust might be missed (although hopefully this will not be such an issue with Cumulus MX as it does not use the Davis DLL), and secondly it uses the 'absolute pressure' value to make calculation of 'altimeter pressure' easier and more accurate. This is mainly used if you upload to CWOP.
The LOOP2 packet is supported on the VP2 with firmware version 1.90 or later, and on the Vue. If you have a Vantage Pro (i.e. the original 'VP1'), or a VP2 with pre-1.90 firmware, or if you are using Virtual VP, none of these support the LOOP2 packet. In these cases, you should edit cumulus.ini and add a line to the [Station] section:
UseDavisLoop2=0
It's worth noting that before upload you can only query archive or hilo data, not real-time loop data, since that needs to be accumulated for the duration of the archive interval (OK, technically you can query LOOP data but makes little sense here). Isn't there a bit of mix up?
Some changes may have been made through the ongoing development of CumulusMX so the extent of LOOP2 use may have changed.
I have tested WiFiLogger with CumulusMX a few weeks ago and the only issue was the communication issue due to more than one program trying to get access.
Cumulus1 does not use LOOP2.
PaulMy noted that the still most used Cumulus version, never uses LOOP (LOOP2 more precisely) data.
I find that difficult to believe - there's a lot of readings in LOOP that are missing in LOOP2 like many of the supplementary sensor readings. I always imagined that Cumulus (or maybe CMX) polls for LOOP and LOOP2. But I've never had cause to look into it in detail.Far from my understanding how it all works but from what I have read Cumulus1 uses the Davis DLL and some of LOOP1. But LOOP2 use was introduced with CumulusMX.
With auto pause cooperating won't be a problem any more. It works perfectly good. Much better I was suspecting.Looking forward to trying that with CumulusMX.
LOOP(2) might miss values but the archive record (DMP/DMPAFT in the serial protocol docs) has them, like additional temp and humidity sensor data.
For PWS, do I use my user ID or station ID?
For PWS, do I use my user ID or station ID?
Hi David
For PWS and WU you are using Station ID, but password is same which you are using to login to those services.
I will change those descriptions with new firmware release.
With auto pause cooperating won't be a problem any more. It works perfectly good. Much better I was suspecting.You're right, with Auto pause got it working with CumulusMX for the past 12 hours and also WiFiLogger uploading to all the other sites. \:D/ =D>
Looking forward to trying that with CumulusMX.
Thanks, John. Sounds like a little gem, that one. A photo of the unit would be great, though.
Thanks, John. Sounds like a little gem, that one. A photo of the unit would be great, though.
Thanks, John. Sounds like a little gem, that one. A photo of the unit would be great, though.
Wojciech, can you please add a decimal place more precision to the dewpoint calculation for the data being sent to WU? In FW117, I'm only seeing a whole number precision for dewpoint temperatures when in fahrenheit units. The Real Time Data screen shows a digit to the right of the decimal point, but it appears to be rounded to zero every time I look at it.
Wojciech, can you please add a decimal place more precision to the dewpoint calculation for the data being sent to WU? In FW117, I'm only seeing a whole number precision for dewpoint temperatures when in fahrenheit units. The Real Time Data screen shows a digit to the right of the decimal point, but it appears to be rounded to zero every time I look at it.
How, with Davis equipment, would you be able to get dewpoint temperature accuracy (or precision or resolution) beyond whole degrees?
See, for instance:
https://www.researchgate.net/publication/52009269_Uncertainties_of_Derived_Dewpoint_Temperature_and_Relative_Humidity
How, with Davis equipment, would you be able to get dewpoint temperature accuracy (or precision or resolution) beyond whole degrees?I was asking for one additional digit past the decimal place (the same as what the Davis software already provides). This request has nothing to do with the absolute accuracy of the dewpoint calculation being used. With the Davis configuration & components in use, I realize that it is hardly accurate enough to even get to whole numbers. However, I'm after relative changes. If I get another decimal place, then I'll see a little less quantization noise. While the Davis RH is presented as a whole number, the formula to convert it to dewpoint has less impact than the temperature does in the range of interest for me.
See, for instance: https://www.researchgate.net/publication/52009269_Uncertainties_of_Derived_Dewpoint_Temperature_and_Relative_Humidity
Thanks for at least looking into it. I get your point and I don't expect any extra effort from you. However, if I may be allowed to rant a little (in general and NOT specifically toward you)... I encounter many people that get hung up on the notion that only absolute accuracy is of importance to EVERYONE and that there is no reason to include a finer resolution. But, please realize that there are some people that can appreciate precision in a relative way and that it's possible to be useful for another purpose. Davis admits that the console readout is a whole number due to various limitations of their processor/memory and therefore resort to a simple lookup table. Davis publishes the calculations that they use in software: https://www.davisnet.com/product_documents/weather/app_notes/AN_28-derived-weather-variables.pdf (https://www.davisnet.com/product_documents/weather/app_notes/AN_28-derived-weather-variables.pdf). If your processor has math functions like EXP and LN, then it should be straight forward to implement. Just a thought in case you change your mind later on down the road.
WFL only transfer console data.
Problem is that. I would like to stay with this philosophy. WFL is a tool to transfer data.
My Davis Weatherlink software records dewpoint and temperatures in tenths from my VP2. My uploads to CWOP using the Davis logger and the Weatherlink software rounds these measurements to the nearest whole degree. However, uploads to WU using that same logger and using Weatherlink reflects dewpoint and temperatures to the nearest tenth. I also have the new WiFilogger. My uploads from a different VP2 to CWOP and WU using this new WiFiLogger are displayed on these two websites rounded to the nearest whole degree. My guess, and is strictly a guess, such amounts are rounded by the WiFi logger so a software “tweak” in the WiFiLogger itself is possible, but let’s see what Wojtek, the developer, has to say!
Wojciech, can you please add a decimal place more precision to the dewpoint calculation for the data being sent to WU? In FW117, I'm only seeing a whole number precision for dewpoint temperatures when in fahrenheit units. The Real Time Data screen shows a digit to the right of the decimal point, but it appears to be rounded to zero every time I look at it.
Also, I don't know if this is just a coincidence or not, but I'm seeing smoother data now on WU once I disabled the main 'Mode' for WU and kept RapidFire enabled. I don't know what is happening under the hood when both are enabled. I would think you'd only want one or the other enabled at a time, but not both. I'm under the impression that WU can't mix both correctly.
[ You are not allowed to view attachments ]
There is more than one mathematical formula to calculate a dew point. I took this one from your post.
PWS, WU, WOW accept dew point value and natural dew point from console is in whole F degree.
When people will accept this calculation from version 1.18. I will change all dew point values to this calculated one.
Outside temp is exported in tenth of degree. Only CWOP accept whole F degree.
Quote from: WiFiLogger on Yesterday at 04:22:01 PM
WFL only transfer console data.
Problem is that. I would like to stay with this philosophy. WFL is a tool to transfer data.
You are lack of HTML files. No HTML files = no interface.
Please go to url http://192.168.4.1/admin/html
Use this simple interface to upload system.html file, then go to http://192.168.4.1/system.html to put all files from html folder.
You can use first url to upload all files if you like.
If you don't have wifi.html and want to establish connection with router use http://192.168.4.1/simplewifi
http://192.168.4.1/admin/infovalues - will show you IP adress.
PWS, WU, WOW accept dew point value and natural dew point from console is in whole F degree.
When people will accept this calculation from version 1.18. I will change all dew point values to this calculated one.
Outside temp is exported in tenth of degree. Only CWOP accept whole F degree.
I completely agree with kubuki -- and your previous decision.QuoteQuote from: WiFiLogger on Yesterday at 04:22:01 PM
WFL only transfer console data.
Problem is that. I would like to stay with this philosophy. WFL is a tool to transfer data.
Doing formulas to change the data from the Davis console would be a negative for me, in a decision to purchase a new logger.
The purpose of a logger is to log the data, and provide a way to access the log. And optionally, to transfer the console data to other systems, in the same way that other software now does. Not to modify the data. And certainly not to modify the data in ways that can't be unmodified.
You are the man. Not sure how I ended up with no HTML files loaded, but thank you so much for the quick response. I am back up and running.
Now I have just add second dew point in same line to check if everything is alright.
May I suggest to add this as an option only? Best would be to keep original values and only switch to the new algorithm when someone specifically requires it by the flip of a toggle setting.
You are the man. Not sure how I ended up with no HTML files loaded, but thank you so much for the quick response. I am back up and running.
You have latest firmware now? Or still problem to make update?
Please go to the first post there is an update manual.
This calculation of dew point value is harmless. Besides WeatherLink is calculating also this value, so it is still Davis standards.
This calculation of dew point value is harmless. Besides WeatherLink is calculating also this value, so it is still Davis standards.
Davis sometimes changes their calculation formula. So, you'll change your calculation when Davis changes theirs?
I will ask here what to do next. Replace, or add new algorithm.
The proposed change is to use the exact same calculation that Davis published. The data will be exactly the same but with one additional significant figure than what the console presents, but exactly the same as what WeatherLink provides.
I think there is some confusion here. Here are a few key points:...
RED console trace clearly exhibits rounding to the nearest whole number. Whereas, the GREEN WL trace is easier to see relative changes.
The
It is clear that as there is no Dewpoint sensor
Do you have any idea when this will be available in the US?
And how will it be announced? (In other words, how will I be able to find out that it's available?)
...
And add my thanks to the list of people who appreciate what you're doing for the WX-Davis community!
Hi Wojtek,
The uploads have been very intermittent over last couple of days, and now stopped to most sites - PWS, WL, CWOP, FTP archive
i.e. http://www.pwsweather.com/obs/KOMOKA2.html and http://www.findu.com/cgi-bin/rawwx.cgi?call=FW2530
However WU is mostly being updated http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=IMIDDLES37
I did reboot the Vue console (disconnect all power and reconnect) and that seemed to get at least one update to CWOP but nothing further.
WiFiLogger Real Time Data view looks fine.
Any suggestions?
Thanks,
Paul
It had been working for 4 months, just the last couple days when there are sometimes hours between upload, except for WU which is updating but not at the set 5 min interval.I am not familiar with network settings but does the NTP Time as 1969 and last boot as 1969 seem normal? If not, how would I change it?
It had been working for 4 months, just the last couple days when there are sometimes hours between upload, except for WU which is updating but not at the set 5 min interval.I am not familiar with network settings but does the NTP Time as 1969 and last boot as 1969 seem normal? If not, how would I change it?
That type of date is often an indication that the device rebooted or re-initialized, and during the start up process it was unable to connect to the network to get the current time. Since it cannot get the correct time it starts from 0 which for UNIX based systems is 12/31/1969 00:00:00.
That type of date is often an indication that the device rebooted or re-initialized, and during the start up process it was unable to connect to the network to get the current time. Since it cannot get the correct time it starts from 0 which for UNIX based systems is 12/31/1969 00:00:00.
This call for a possible bug. When the module is initialized without public internet access (or one that prohibits NTP server access), timestamps will be wrong where they're needed and possibly used for uploads. I think it would be nice if the module first initialized its clock from the console, then maintained accuracy using NTP.
Hello Wojciech,
I Just Installed WiFiLogger and I'm reporting to everything except CWOP. The problem is that I was not showing up on APRS/CWOP so I changed the port to 23. That didn't work either. After that I upgraded the firmware to 118 and now I can't increase the port number more that a few numbers at a time. I can't copy and paste or type in 14580 or any number more than 10 higher or it won't save. and after a 20 minutes of finally getting to 255, it will not go higher.... I need 14580... any suggestions?
Working perfectly now.
Thanks for the quick reply AND quick fix. You sir, are 'on the ball' Wojciech !! \:D/
This logger has a lot of features... However, I'm not sure if I see anything that can adjust (calibrate) settings like Tem & Humidity. Is this feature available and I've just overlooked it somehow?
Also, this may have been explained, but what's the story on Console Dewpoint vs Calculated?
Calibration: There are some console settings, but not all. I will check how long it will take to make calibration menu. Maybe next firmware version (next friday) it will be done.
Please remember that calibration is in console, WFL won't recalculate values, only units.
Another question. Would updating the Davis Pro2 CONSOLE firmware be possible through the WiFiLogger? I forgot to do this for the latest firmware and I'd rather not have to reinstall the WLIP logger to accomplish this. Any thoughts?
Hi all...new to the hobby and forums. Looking to purchase my first Davis VP2 station. Am I correct in thinking that the WiFiLogger eliminates the need for a meteobridge and a usb data-logger cable? Thanks!
Hi all...new to the hobby and forums. Looking to purchase my first Davis VP2 station. Am I correct in thinking that the WiFiLogger eliminates the need for a meteobridge and a usb data-logger cable? Thanks!
Hi all...new to the hobby and forums. Looking to purchase my first Davis VP2 station. Am I correct in thinking that the WiFiLogger eliminates the need for a meteobridge and a usb data-logger cable? Thanks!
OK...Just to make sure you have the right settings checked.
So I just got on to my Weatherlink software on my home PC and went to download the logger like I do about every couple of months so the logger doesn't get to full. As usual a dialog box appears...says downloading 150 pages (or whatever), BUT there is no data. If I make a plot the page loads to the year 2089 or 2150 or something and after scrolling back to 2018, all plots stop at 7:15 pm July 18th... the time and day I removed weatherlinkIP and plugged in Wifilogger.
Any Idea what I might have done wrong here? Am I supposed to even be getting logged archive data via wetherlink like before? i thought I would.
Just to make sure you have the right settings checked.
Under Wi-FI setup scroll all the way to the bottom. Under TCP settings make sure you have 22222 in the box. Click save.
Next go to the System page. Under TCP select Auto-Pause. Click save.
Next open Weatherlink but do not download any data. Click Set Up and go to Communications Port. In the Communications box make sure TCP/IP is checked. Under the TCP/IP Connections box make sure you have 22222 as the TCP port number. Under Remote IP Address put this number. 10.0.0.210 Click OK at the top.
Before you do download anything though delete those bad years. Have to get rid of that bad data.
Hopefully that helps.
OK...
So I just got on to my Weatherlink software on my home PC and went to download the logger like I do about every couple of months so the logger doesn't get to full. As usual a dialog box appears...says downloading 150 pages (or whatever), BUT there is no data. If I make a plot the page loads to the year 2089 or 2150 or something and after scrolling back to 2018, all plots stop at 7:15 pm July 18th... the time and day I removed weatherlinkIP and plugged in Wifilogger.
Any Idea what I might have done wrong here? Am I supposed to even be getting logged archive data via wetherlink like before? i thought I would.
Bobvelle you had this problem, because it is possible that you have unit which was not clear before shipping. I am sorry because of that.
I will need to add this point to quick manual, to clear arch memory before use. WeatherLink is asking for clearing arch. memory very often.
However, during initial setup of WiFilogger (before I updated to 1.18, I think) I remember going to "Set Archive Interval" and checking the block "new archive interval will automatically erase whole memory. Do it?"If you don't change interval then this command will be not executed. You have to change interval value before, then it will be done.
Is this not the same as clearing the memory via Weatherlink?
If you don't change interval then this command will be not executed. You have to change interval value before, then it will be done.
If you don't change interval then this command will be not executed. You have to change interval value before, then it will be done.
Check commands:
SETUP|Weather Station Setup
go to the bottom and find COMMAND SEND section.
11th command on list is CLRLOG, that will erase archiver memory.
Well I took the plunge and ordered one from Scaled Instruments last night. I had been thinking of buying Weatherlink IP since I only have laptops and don’t have one on 24/7. Hoping this fits the bill!
Okay... another issue. (rack'n 'em up now :-)).
I tried to use Wi-Fi logger to calibrate my barometer. Now my barometer is stuck at a certain pressure and will not change. I have another console and it's showing pressure in my area changing rapidly but the console with WiFiLogger is stuck. I tried clearing the calibration through WiFiLogger by entering '0' but this appeared to make no difference. It keeps returning -29.873 hg in the offset dialog box. I then tried setting the current pressure through the console itself but it still stays at whatever pressure I set without changing.
Well I took the plunge and ordered one from Scaled Instruments last night. I had been thinking of buying Weatherlink IP since I only have laptops and don’t have one on 24/7. Hoping this fits the bill!
Well I took the plunge and ordered one from Scaled Instruments last night. I had been thinking of buying Weatherlink IP since I only have laptops and don’t have one on 24/7. Hoping this fits the bill!
If you have a Wireless Router with internet access and a Davis Console you'll be up and reporting in no time. No computers necessary. (except to set up, of course) I think you will be Happy. Plus, the developer is making upgrades and improvements almost daily. So far I am very happy with this logger and I like it better than WeatherlinkIP that I was using. Please don't be concerned by the issues I've posted. My situation is unique in that my system, without going into detail, is a "Frankenstein" station. So I have issues that most users won't encounter.
Good Luck
If this thing would have been around 9 years ago, I'd of done the same as your doing :grin:
Then I wasn’t really thrilled with having to run 25 feet of cable from my console to the router or spending extra on a weatherbridge and logger. I could have just moved my console next to the router, but I like just glancing over at it while I’m sitting in my chair watching tv lol. This looks to be perfect for me.
Well that wasn't too hard of a setup at all! Up and sending to WU already. \:D/
So is anyone feeding the live data on a personal website with the WiFiLogger?
This looks amazing.
got my station hooked up with WifiLogger last evening pushing updates to WU and PWS every minute. But now 15 hours later, it stopped. I’m at work, but using my Linksys app, I can tell that my home has internet, but WifiLogger is offline 🙁.
Has this happened to anyone else?
I’ll have to play tonight, not sounding good so far.
I walked my daughter through:
(1) SETUP/SYSTEM/RESET - didnt work since WFL not connected
(2) Hit white button, then try (1) - still not connected
(3) power down /power up, then try (1) - still not connected
Maybe I need to restablish wifi connection with my phone?
but does it have to be actively running 24/7?No, and Cumulus should update the logger data since last running.
the WFL "Data Export Setup", what does this allow me to do?It will FTP the logger data to your webserver in the path/file specified
Date,Time,Temp Units,Bar Units,Wind Units,Rain Units,Temp Out,Hi Temp,Low Temp,Rain,Rain Rate,BAR,Solar
2018/07/29,13:00,C,hPa,km/h,mm,22.2,22.3,22.2,0.0,0.0,1019.9,189,26.7,52,65,8.0,14.5,SSW,S,1.4,14,190,1.4
2018/07/29,13:05,C,hPa,km/h,mm,21.2,21.2,21.2,0.0,0.0,1020.1,190,26.7,51,63,11.3,14.5,SSW,S,1.4,---,190,1.4
2018/07/29,13:10,C,hPa,km/h,mm,20.4,20.8,20.4,0.0,0.0,1020.0,79,26.8,49,64,4.8,8.0,SW,SSW,0.0,---,100,0.0
2018/07/29,13:15,C,hPa,km/h,mm,20.0,20.4,20.0,0.0,0.0,1020.1,67,26.6,49,68,8.0,22.5,S,S,0.5,---,77,0.5
2018/07/29,13:20,C,hPa,km/h,mm,19.9,19.9,19.9,0.0,0.0,1020.3,93,26.6,49,68,4.8,9.7,S,S,0.7,---,93,0.7
2018/07/29,13:25,C,hPa,km/h,mm,19.4,19.7,19.4,0.0,0.0,1020.1,93,26.7,49,71,4.8,8.0,S,WSW,0.7,---,93,0.7
2018/07/29,13:30,C,hPa,km/h,mm,19.4,19.5,19.4,0.0,0.0,1020.5,102,26.6,49,71,1.6,4.8,NNE,SW,0.5,---,125,1.0
2018/07/29,13:35,C,hPa,km/h,mm,19.4,19.4,19.4,0.0,0.0,1020.7,65,26.6,49,72,0.0,1.6,S,S,0.0,---,65,0.0
I want to try the Saratoga template, but I believe I need to figure out the "archive export" feature of WFL first. Attached is my screenshot, but I don't see any files getting uploaded by WFL.OK - figured it out. The full path should just be a file name prefaced by a slash, e.g. "/data.txt"
My ftp username of MillbridgeWeather@actulife.com is set up to upload files to http://www.actulife.com/public_html/MillbridgeWeather/
So am I correct that the "full path" should be: http://www.actulife.com/public_html/MillbridgeWeather/? Originally I had the full path at "/" which was the default, but that didn't help either.
Also, if is it recommended to leave the "number of days" at 7?
I was expecting the "Archive Export" to work automatically just like the "data export". But maybe it has to be done manually using the "Archive Data" menu? I can't find any documentation on either of these in the user manual.
Thanks!
I fitted the WiFiLogger to my Davis Vantage Vue today but I have not been able to read any weather data from it. The WiFi connection appears to be working fine; I can successfully read the "Weather Station Settings" page and it reads back (for example) the latitude and longitude and altitude settings previously entered into the console and I can use the "Send Command" function e.g. to turn the backlight on and off, so the communication to the unit is definitely working. However there is no data in any of the fields of the "Real Time Data" page. I have already updated the WiFiLogger to firmware version 1.19 and the Vantage Vue is already running version 3.00 firmware. (See attached screenshots.)Only thing I can suggest is go to your WiFi setup page and confirm that your 'AP' is "disabled" and "DHCP" is "ENABLED" and also check TCP port is 22222.
I initially was doing 1 minute intervals - definitely no good since due to the overlaying, I wasn't able to download a complete file. Changing the interval to 5 minutes deletes everything, but at it least it let me see a "complete" file. This could be useful data, but it's missing the all important dew point calculation. Interesting stuff, though.
I noticed that on WU the rain rate is always equal to rain accum. But on PWS the rate varies and looks reasonable. Is this a bug in WFL or WU?
WU: KNCWAXHA62
PWS: REDLYNR
look at the rain rates for today 7/31/2018
I fitted the WiFiLogger to my Davis Vantage Vue today but I have not been able to read any weather data from it. The WiFi connection appears to be working fine; I can successfully read the "Weather Station Settings" page and it reads back (for example) the latitude and longitude and altitude settings previously entered into the console and I can use the "Send Command" function e.g. to turn the backlight on and off, so the communication to the unit is definitely working. However there is no data in any of the fields of the "Real Time Data" page. I have already updated the WiFiLogger to firmware version 1.19 and the Vantage Vue is already running version 3.00 firmware. (See attached screenshots.)
Updated 31st Jul 2018: The logger is sending weather data to Wunderground.com but the local "Real Time Data" screen remains blank (as per screenshot attached).
As always I am late :-(
First website is using AJAX to show data on screen. Every 3s data from http://YOUR_WFL_IP/rtd are downloaded and show on screen.
[ You are not allowed to view attachments ]
Please check if this data is avaible. If yes, then there is a problem with your web browser and AJAX.
Maybe you should upload INDEX.html once more, from latest HTML folder.
Please try and let us know if everthing is alright.
I wasn’t home, but not far away. I did rain hard for a while, so PWS does sound reasonable. I’m sending to both at 1 minute intervals, but WU only saves every 5th minute in it’s table. I don’t see any decimal settings.WU: KNCWAXHA62
PWS: REDLYNR
look at the rain rates for today 7/31/2018
OK ... I'm confused...
What did you really get? Were you home? Did you actually get 3.6in/hr rainfall at 2:04 PM today? Because that is what PWS says....for a total .4 inches.
I assume PWS is right because it seems reasonable.
However, WU is showing a .04 in/hr every 5 min for ~ 1/2 hour. for a total of 0.04 inches. Not likely. It's accumulating you rain rate instead of total rainfall. I don't know why.
Only difference I see is your sending data to PWS every minute and WU every 5 minutes. I'm doing the opposite except PWS every 15 Min. I can't figure why that would matter... but its not working right, for sure.
Wait.. I just noticed something. WU and PWS look like they are seeing the same #s but the decimal point is off on WU. Hmmm
Might want to check WFL setup for any decimal place settings.. I thought I saw one.
PWS accept rain values:I think that explains why PWS looks good and WU doesn't. Is there a reason that your "rainin" is defined differently for WU as opposed to PWS? I would expect "rainin" to be calculated as (ObservedRain in interval) * (60 / update frequency)
rainin- Hourly rain in inches
dailyrainin- Daily rain in inches
Console has those values and those are being export.
WU accept:
rainin - [rain inches over the past hour)] -- the accumulated rainfall in the past 60 min
dailyrainin - [rain inches so far today in local time]
Also proper console values are exported.
While using FireFox please press F12. It will open diagnostic window. There should be information what is wrong.
Please reply this info here or send me on priv. or email wifilogger@qq.com
Here is a screenshot of the Real Time Data screen on Firefox after pressing F12.
I had this problem, but all seemed to be working OK. I then tried a different browser From Chrome to Microsoft Edge then all data appeared,I fitted the WiFiLogger to my Davis Vantage Vue today but I have not been able to read any weather data from it. The WiFi connection appears to be working fine; I can successfully read the "Weather Station Settings" page and it reads back (for example) the latitude and longitude and altitude settings previously entered into the console and I can use the "Send Command" function e.g. to turn the backlight on and off, so the communication to the unit is definitely working. However there is no data in any of the fields of the "Real Time Data" page. I have already updated the WiFiLogger to firmware version 1.19 and the Vantage Vue is already running version 3.00 firmware. (See attached screenshots.)Only thing I can suggest is go to your WiFi setup page and confirm that your 'AP' is "disabled" and "DHCP" is "ENABLED" and also check TCP port is 22222.
Other than that, you may have to wait and see what Wojtech or others who have had the same issue can chime in. Sorry.
I was also having problems with not been able to view the Charts on WL it was just dots and no lines.
I had this same issue for the first couple days, but like you, it corrected itself and I don't remember what I did, if anything, to fix it.
Only strange thing I see now is CWOP Findu page. Chart for solar radiation will not show above 999 W/m2. As soon as my station reports >or=1000 W/m2 it graphs as a zero or 1. It never did this before... but looking at the raw data being received by CWOP, it clearly shows Example "L1005" for 1005 W/m2 but graphs as though the decimal place is off Example 1.005 or .1005. This seems like a problem with FINDU, but it happened the day I switched to WFL and has been this way ever since... Maybe just a coincidence. Strange though.
I'm still not certain it's a WFL issue.Only strange thing I see now is CWOP Findu page. Chart for solar radiation will not show above 999 W/m2. As soon as my station reports >or=1000 W/m2 it graphs as a zero or 1. It never did this before... but looking at the raw data being received by CWOP, it clearly shows Example "L1005" for 1005 W/m2 but graphs as though the decimal place is off Example 1.005 or .1005. This seems like a problem with FINDU, but it happened the day I switched to WFL and has been this way ever since... Maybe just a coincidence. Strange though.
I don't have UV and Solar sensors. I can't test it properly. I will try to cheat ISS to send this data. I will test it again with WL60 and Cumulus.
Unfortunately it will not be the next day.
Regarding Weatherlink...
I fitted the WiFiLogger to my Davis Vantage Vue today but I have not been able to read any weather data from it. The WiFi connection appears to be working fine; I can successfully read the "Weather Station Settings" page and it reads back (for example) the latitude and longitude and altitude settings previously entered into the console and I can use the "Send Command" function e.g. to turn the backlight on and off, so the communication to the unit is definitely working. However there is no data in any of the fields of the "Real Time Data" page. I have already updated the WiFiLogger to firmware version 1.19 and the Vantage Vue is already running version 3.00 firmware. (See attached screenshots.)
Updated 31st Jul 2018: The logger is sending weather data to Wunderground.com but the local "Real Time Data" screen remains blank (as per screenshot attached).
I think I know where is the problem. Your console has firmware version 3.0 I have prepared WFL for 3.xx format.
I will repair that tomorrow and send you repaired firmware ASAP.
PLEASE make it clear upfront whether you're talking about 'local' Weatherlink for Windows (eg v6.0.4) or the weatherlink.com 2.0 cloud platform. Both are supported by WFL but the two have very different configurationAnd I thought I knew everything :oops: ?
Regarding Weatherlink, I didn't have any great expectations from reading this thread, but using the WFL option to send using the "WL IP" mode, all I can see in the WeatherLink "Bulletin" web page is the barometer data and the "wind rose" data. The temperature and rain sections and all of the other "gateways" are empty. Not much to see here. I tried switching the mode to "WL PC" and don't see any changes.
Regarding Weatherlink, I didn't have any great expectations from reading this thread, but using the WFL option to send using the "WL IP" mode, all I can see in the WeatherLink "Bulletin" web page is the barometer data and the "wind rose" data. The temperature and rain sections and all of the other "gateways" are empty. Not much to see here. I tried switching the mode to "WL PC" and don't see any changes.
Same problem with Weatherlink. WU, PWS, CWOP all work fine. Just get barometer and wind rose on Weatherlink.com, and that's just occasionally. Not that big of a deal to me since the others work flawlessly. It's entirely possible that I'm doing something wrong.
3. Click on "Activation"That was the trick! It wasn't obvious to me before that this was "clickable".
3. Click on "Activation"That was the trick! It wasn't obvious to me before that this was "clickable".
Thanks!
I just got the WiFi logger. Going to update the firmware and get it online. Nice hardware....
I just got the WiFi logger. Going to update the firmware and get it online. Nice hardware....
As noted below by the maker of this great tool, you don’t need to update the html files if your system had 1.19. If you just purchased yours new, that is not very likely so be sure and include the 10+ html files for updating if your firmware is 1.18 or earlier.
lol Where was this device 10 years ago?Thanks for choosing WFL.
Davis should have come up with it first though, in my opinion.
But that's the beauty of the free market.. =D>
I just got the WiFi logger. Going to update the firmware and get it online. Nice hardware....
As noted below by the maker of this great tool, you don’t need to update the html files if your system had 1.19. If you just purchased yours new, that is not very likely so be sure and include the 10+ html files for updating if your firmware is 1.18 or earlier.
Got it online and firmware with html files in about 2 minutes. lol Where was this device 10 years ago?
Found this APRS protocol for solar radiation. Maybe this will help?I'm still not certain it's a WFL issue.Only strange thing I see now is CWOP Findu page. Chart for solar radiation will not show above 999 W/m2. As soon as my station reports >or=1000 W/m2 it graphs as a zero or 1. It never did this before... but looking at the raw data being received by CWOP, it clearly shows Example "L1005" for 1005 W/m2 but graphs as though the decimal place is off Example 1.005 or .1005. This seems like a problem with FINDU, but it happened the day I switched to WFL and has been this way ever since... Maybe just a coincidence. Strange though.
I don't have UV and Solar sensors. I can't test it properly. I will try to cheat ISS to send this data. I will test it again with WL60 and Cumulus.
Unfortunately it will not be the next day.
These are the raw data packets at 7 Min intervals received by CWOP/APRS. The last set of numbers after the "L" is the Watts/meter2. Notice the 4 entries at 1826, 1833, 1847 and 1950 zulu. These are graphed below as "0" or almost "0" its hard to tell exactly.
DW5212>APRS,TCPXX*,qAX,CWOP:@021813z3135.15N/09236.10W_092/001g005t088r000p000P000h52b10159L977.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021819z3135.15N/09236.10W_005/001g005t088r000p000P000h52b10159L983.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021826z3135.15N/09236.10W_140/001g004t089r000p000P000h50b10158L1004.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021833z3135.15N/09236.10W_010/002g005t088r000p000P000h50b10156L1011.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021840z3135.15N/09236.10W_080/000g005t089r000p000P000h51b10155L990.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021847z3135.15N/09236.10W_082/002g007t088r000p000P000h49b10153L1035.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021854z3135.15N/09236.10W_005/002g007t088r000p000P000h48b10154L997.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021901z3135.15N/09236.10W_039/002g004t089r000p000P000h47b10150L983.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021908z3135.15N/09236.10W_249/001g004t089r000p000P000h48b10150L990.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021915z3135.15N/09236.10W_268/002g004t088r000p000P000h52b10149L993.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021922z3135.15N/09236.10W_033/001g004t089r000p000P000h50b10148L944.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021929z3135.15N/09236.10W_015/002g004t088r000p000P000h50b10148L967.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021936z3135.15N/09236.10W_027/001g005t090r000p000P000h48b10146L965.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021943z3135.15N/09236.10W_173/001g005t089r000p000P000h49b10148L940.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021950z3135.15N/09236.10W_030/002g005t090r000p000P000h49b10147L1018.WFL
DW5212>APRS,TCPXX*,qAX,CWOP:@021957z3135.15N/09236.10W_031/001g005t088r000p000P000h49b10146L990.WFL
The dips after 2000 and 2200 zulu were actual clouds. Notice it only dropped to ~200 W/m2.
[ You are not allowed to view attachments ]
This is the actual Solar Radiation recorded today at 15 minute intervals. Only one entry here showing >1000 due to the longer and offset record interval.
[ You are not allowed to view attachments ]
Other parameters that are available on some weather station units include:
L = luminosity (in watts per square meter) 999 and below.
l (lower-case letter “L”) = luminosity (in watts per square meter)
1000 and above.
(L is inserted in place of one of the rain values).
CW7324>APRS,TCPXX*,qAX,CWOP-7:@161605z4326.05N/07137.20W_322/003g015t079r000p000P000h76b10153L886.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-2:@161610z4326.05N/07137.20W_250/003g010t079r000p000P000h75b10154L898.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-6:@161615z4326.05N/07137.20W_005/004g013t079r000p000P000h68b10154L909.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-2:@161620z4326.05N/07137.20W_315/002g010t079r000p000P000h66b10154L911.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-5:@161625z4326.05N/07137.20W_360/003g013t079r000p000P000h74b10155L926.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-2:@161630z4326.05N/07137.20W_225/002g013t079r000p000P000h71b10155L940.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-3:@161635z4326.05N/07137.20W_005/002g009t079r000p000P000h63b10157l046.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-5:@161640z4326.05N/07137.20W_076/000g008t080r000p000P000h66b10155l032.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-1:@161645z4326.05N/07137.20W_294/004g010t080r000p000P000h59b10156L993.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-6:@161650z4326.05N/07137.20W_345/004g012t080r000p000P000h65b10156l025.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-1:@161655z4326.05N/07137.20W_288/004g013t080r000p000P000h64b10156L990.DsVP
CW7324>APRS,TCPXX*,qAX,CWOP-7:@161700z4326.05N/07137.20W_348/005g014t080r000p000P000h54b10156L937.DsVP
You can see in my APRS data that values above 999 get coded with "l" instead of "L".
I have an FTP server and noticed there is an FTP facility in WFL. Does this data arrive in some standard format easily read by say CumulusMX or is it raw for processing thro Excel or whatever? A polite finger in the right direction or some existing thread much appreciated. Don't want to be reinventing a square wheel :)
Cheers ... Keith
I have an FTP server and noticed there is an FTP facility in WFL. Does this data arrive in some standard format easily read by say CumulusMX or is it raw for processing thro Excel or whatever? A polite finger in the right direction or some existing thread much appreciated. Don't want to be reinventing a square wheel :)
Cheers ... Keith
FTP in WFL is the only option to export archive data. It send CSV file in WFL format, but .....
WeatherLink files are txt in two formats. Local and FTP export file. One has tabs, second space. Both have same headers, but in two rows.
I don't know who was inventor of those two rows headers, but for any programming language that is a pain ....
I have made this straight. WFL format is Davis headers in single row in CSV format where you can choose separator. I have add units columns. This is important. There is no units information in original one.
I believe my CSV format is very close to Davis standard. I wanted to repair same things, not to change entire system.
So WFL export file is CSV format with Davis headers + units columns + you can choose separator, or date format. It will stay that way. I don't know better idea.
You have to know one thing. WFL is reading console data and export it to FTP. Whole memory reading takes 2 min 15 sec. There is a problem with 1 min interval.
When WFL is making export then console is busy and there will be no new entry in arch. data. Also no other export function will be executed when FTP file is being exported. RapidFire will be postpone.
For 1 min export only WL.COM account is an answer for now.
Trigger is auto. Arch. interval (from console settings) + 15 sec.
Full path is:
/WeatherData/file.csv
Folder has to be there. WFL don't creat folders.
+ I didn't program IP address as a name. You have to use name of the server.
Hi All!
I have a question for the developer of WifiLogger.
Is it possible to add a function to send current data to a personal server (through FTP or HTTP)?
Hi All!
I have a question for the developer of WifiLogger.
Is it possible to add a function to send current data to a personal server (through FTP or HTTP)?
Not now. It is planed.
My ideas for real time exports are:
- MQTT JSON format data (JohnD idea)
- Same JSON file exported as a FTP file.
- PHP driver which I will provide and client will be able to install on own host. This driver bin.php will feed MySQL database, because that is (cheapest) standard on any hosting.
bin.php will allow to access of settings, current data and arch. records data = same export data what WL IP is providing.
bin.php won't be optimized. So there is no way that with bin.php you will be able to establish WL.COM service with 25k clients, but up to 30-50 units that should be ok.
Those are ideas. Time to make it. What should be first?
For me the important thing is the possibility to upload data to a personal web site, doesn't matter the method :)
How are the plans after Brexit?
How are the plans after Brexit?
This means vat and customs fee to other countries in Europe.
Nbr2 as before.
I tried the wireless console firmware update and it worked great. The Davis direct firmware update software was able to find the console by tcpip and the IP address. The whole upgrade process took about 15 minutes.
How are the plans after Brexit?
This means vat and customs fee to other countries in Europe.
Apply Occam's Razor: FTP or HTTP
Question.
It says everywhere that it should be version 1.90 for it to work, but I have 4.33 in my Vantage Vue. Or is there different t ways of finding version? HW-ver and SW-ver?
I pressed Done and +.
Hello, you're right, usually files of common Weather softwares doesn't include all parameters available in Davis' Console. Maybe you can create an XML file like Weatherlink.com API, otherwise a new file with your standard wich contain alla available values (include leaf wetness, soil parameters, extra temp, ecc...)I tried the wireless console firmware update and it worked great. The Davis direct firmware update software was able to find the console by tcpip and the IP address. The whole upgrade process took about 15 minutes.
No way. WeatherLink is finding WFL normally, but Davis firmware software do not want to do this. I don't know why, maybe MAC address is wrong. WL IP has pool of addresses.
I always need to write IP address manually.
Please use AUTO PAUSE option to update console, this is the safest way.
When something will go wrong, there is no problem. Console will not turn on, but there is always possibility to start from beginning. This operation is fully safe.
After correct console update, console will start to working again.How are the plans after Brexit?
This means vat and customs fee to other countries in Europe.
There is no problem at this moment, so there is no plan to solve it.
I believe that UK will be like Norway and Switzerland. These countries have appropriate international agreements.
If not, problem will be solved when it will be occurredApply Occam's Razor: FTP or HTTP
I have started with Realtime.txt, which will have same format like Cumulus has.
Not all fields will be populated, because Cumulus is making own statistics. WHL is not.
Realtime.txt via FTP will be first, but I will prepare other exports.
Problem is, I want to export all console data. Common interfaces are very nice, like this Cumulus onem there is a many tempates to read it, but these won't export extra temp, extra hum, soil moisture & temp, leaf etc. HiLow data ....
Hi there. Do you have a rough timeline on MQTT support? I'm hoping to use this to log data in InfluxDB and MQTT support would make that extremely easy.
Hello, you're right, usually files of common Weather softwares doesn't include all parameters available in Davis' Console. Maybe you can create an XML file like Weatherlink.com API, otherwise a new file with your standard wich contain alla available values (include leaf wetness, soil parameters, extra temp, ecc...)
I think the best result is to have all the values available.
Hello, you're right, usually files of common Weather softwares doesn't include all parameters available in Davis' Console. Maybe you can create an XML file like Weatherlink.com API, otherwise a new file with your standard wich contain alla available values (include leaf wetness, soil parameters, extra temp, ecc...)
I think the best result is to have all the values available.
JSON format is much more appropriate for this system. Unfortunately I am forced to make my own JSON file, otherwise I won't be able to send all data.
After I started using WIFILogger. which is working pretty awesome, I noticed that my weather station is reporting spikes in temp and pressure... I have noticed that others who are also using WIFILogger are also reporting spikes...
Here is a link to my station data:
https://www.wunderground.com/personal-weather-station/dashboard?ID=KFLSTPET130
Is this a known issue? I am using a wireless Davis Vantage Vue… please let me know if there is anything that can be done to resolve.
After I started using WIFILogger. which is working pretty awesome, I noticed that my weather station is reporting spikes in temp and pressure... I have noticed that others who are also using WIFILogger are also reporting spikes...
Here is a link to my station data:
https://www.wunderground.com/personal-weather-station/dashboard?ID=KFLSTPET130
Is this a known issue? I am using a wireless Davis Vantage Vue… please let me know if there is anything that can be done to resolve.
This is not spike. This is data at 6:01 from 9:59. I will check those time functions.
I am trying to make JSON export now. I need to make it as a first.
What time do you have? UTC -4h?
After I started using WIFILogger. which is working pretty awesome, I noticed that my weather station is reporting spikes in temp and pressure... I have noticed that others who are also using WIFILogger are also reporting spikes...
Here is a link to my station data:
https://www.wunderground.com/personal-weather-station/dashboard?ID=KFLSTPET130
Is this a known issue? I am using a wireless Davis Vantage Vue… please let me know if there is anything that can be done to resolve.
This is not spike. This is data at 6:01 from 9:59. I will check those time functions.
I am trying to make JSON export now. I need to make it as a first.
What time do you have? UTC -4h?
GMT -5 , but it is not showing on the network info tab. Also, just restarted the logger but still no time info showing on that screen. On the station info screen it is accurate at GMT -5.
After I started using WIFILogger. which is working pretty awesome, I noticed that my weather station is reporting spikes in temp and pressure... I have noticed that others who are also using WIFILogger are also reporting spikes...
Here is a link to my station data:
https://www.wunderground.com/personal-weather-station/dashboard?ID=KFLSTPET130
Is this a known issue? I am using a wireless Davis Vantage Vue… please let me know if there is anything that can be done to resolve.
This is not spike. This is data at 6:01 from 9:59. I will check those time functions.
I am trying to make JSON export now. I need to make it as a first.
What time do you have? UTC -4h?
GMT -5 , but it is not showing on the network info tab. Also, just restarted the logger but still no time info showing on that screen. On the station info screen it is accurate at GMT -5.
I think NTP time was downloaded. Was synchronized with one timer and not with second.
There is two times in WFL. UTC and local console. I think times where mixed for a second.
Thank you, when i look back at my station history I see this happening once or twice daily. Is there some setting I can make in wifilogger to adjust this?
Thank you, when i look back at my station history I see this happening once or twice daily. Is there some setting I can make in wifilogger to adjust this?
Navigate to SETUP|WiFi SETUP and change NTP interval to 0. Save.
This will disable NTP. I think there is a problem.
Please let us know if it's ok.
Hi Wojtek,I am on v1.19. Should I update to v1.20 before going to v1.21?
Paul
I want to start discussion how this wflexp.json file should looks like in final stage.Sorry, can't give any comments or suggestion on this at the moment as making a new script or template is beyond me.
When somebody will make template for this file, this file will not be change any more. So we have here maybe a week/two, to make final shape of this file. Then it will be fixed.
RealTime.txt has Cumulus format, but probably still need some work.I have my test http://www.komokaweather.com/pws-new-20180903/ successfully using www.komokaweather.com/wifi-console/realtime.txt
QuoteRealTime.txt has Cumulus format, but probably still need some work.I have my test http://www.komokaweather.com/pws-new-20180903/ successfully using www.komokaweather.com/wifi-console/realtime.txt
Enjoy,
Paul
Hi all, this question may have been answered but I can´t find it: is this logger compatible with weathercloud network?
No, but It won't be hard to make. Little problem is, there is not enought resources for all weather services.I do upload to Weathercloud through Cumulus https://app.weathercloud.net/d0280022074#profile
I need confirmation that https://weathercloud.net/ (https://weathercloud.net/) is most common for all WiFiLogger users.
Good morning PaulBrian's Home Weather Station thread on Cumulus http://sandaysoft.com/forum/viewtopic.php?f=29&t=17090#p131542 which uses the Cumulus realtime.txt as current data source.
I gotta say that your webpage setup is excellent........would love to do something similar myself!
Cheers Paul @flyingdutchwx (London Northeast)
Hi Wojtek,QuoteNo, but It won't be hard to make. Little problem is, there is not enought resources for all weather services.I do upload to Weathercloud through Cumulus https://app.weathercloud.net/d0280022074#profile
I need confirmation that https://weathercloud.net/ (https://weathercloud.net/) is most common for all WiFiLogger users.
but it doesn't rank any higher for me than the other uploads you currently have.
Enjoy,
Paul
So I assume that you need to have a computer switched on to upload to weathercloud...I do for my Cumulus upload, but if it were uploaded by WiFiLogger I presume that would suffice but Wojtek is better to answer that.
Thank you, when i look back at my station history I see this happening once or twice daily. Is there some setting I can make in wifilogger to adjust this?
Navigate to SETUP|WiFi SETUP and change NTP interval to 0. Save.
This will disable NTP. I think there is a problem.
Please let us know if it's ok.
Ok, I’ll make this change and watch for a few days and report back.
QuoteGood morning PaulBrian's Home Weather Station thread on Cumulus http://sandaysoft.com/forum/viewtopic.php?f=29&t=17090#p131542 which uses the Cumulus realtime.txt as current data source.
I gotta say that your webpage setup is excellent........would love to do something similar myself!
Cheers Paul @flyingdutchwx (London Northeast)
However, as my test page shows, the WiFiLogger new realtime.txt FTP does the same thing.
The Home Weather Station template download is here https://weather34.com/homeweatherstation/
I will gladly help you get started...
Enjoy,
Paul
Hi Brian,QuoteGood morning PaulBrian's Home Weather Station thread on Cumulus http://sandaysoft.com/forum/viewtopic.php?f=29&t=17090#p131542 (http://sandaysoft.com/forum/viewtopic.php?f=29&t=17090#p131542) which uses the Cumulus realtime.txt as current data source.
I gotta say that your webpage setup is excellent........would love to do something similar myself!
Cheers Paul @flyingdutchwx (London Northeast)
However, as my test page shows, the WiFiLogger new realtime.txt FTP does the same thing.
The Home Weather Station template download is here https://weather34.com/homeweatherstation/ (https://weather34.com/homeweatherstation/)
I will gladly help you get started...
Enjoy,
Paul
hello Paul
so am i right in thinking(correct me if I am totally wrong) the standard cumulus version of the template supports the wifi logger if cumulus realtime.txt is used as the option in wifi logger.forgive me but I have no background or experience of wifi logger . i did look at the json output but thats pretty confusing probably needs some documentation to highlight what some of the fields are, i understood some of them but got lost half way down and thought thats a complete rewrite to make the template that structure. I'm happy to include a note that the cumulus supports wifi logger but im not the expert to ask questions if any issues arise. brian
Got the wifilogger and it is sending to wunderground, but the new thing logging to ftp, can't get it to work.
No file what so ever is written to my ftp....?
Hi Brian,QuoteGood morning PaulBrian's Home Weather Station thread on Cumulus http://sandaysoft.com/forum/viewtopic.php?f=29&t=17090#p131542 (http://sandaysoft.com/forum/viewtopic.php?f=29&t=17090#p131542) which uses the Cumulus realtime.txt as current data source.
I gotta say that your webpage setup is excellent........would love to do something similar myself!
Cheers Paul @flyingdutchwx (London Northeast)
However, as my test page shows, the WiFiLogger new realtime.txt FTP does the same thing.
The Home Weather Station template download is here https://weather34.com/homeweatherstation/ (https://weather34.com/homeweatherstation/)
I will gladly help you get started...
Enjoy,
Paul
hello Paul
so am i right in thinking(correct me if I am totally wrong) the standard cumulus version of the template supports the wifi logger if cumulus realtime.txt is used as the option in wifi logger.forgive me but I have no background or experience of wifi logger . i did look at the json output but thats pretty confusing probably needs some documentation to highlight what some of the fields are, i understood some of them but got lost half way down and thought thats a complete rewrite to make the template that structure. I'm happy to include a note that the cumulus supports wifi logger but im not the expert to ask questions if any issues arise. brian
Yes the WiFiLogger realtime.txt file is the same format as the Cumulus. I have WiFiLogger FTP this realtime.txt at 1 min interval. Then the realtime path in your (Cumulus) template set to that WiFiLogger upload site. In a quick comparison to my Cumulus realtime.txt site and the WiFiLogger realtime.txt site all the current data seems the same. Not sure what else may be different in your template between the Cumulus and the other versions.
Regards,
Paul
Hi Brian,
Yes the WiFiLogger realtime.txt file is the same format as the Cumulus. I have WiFiLogger FTP this realtime.txt at 1 min interval. Then the realtime path in your (Cumulus) template set to that WiFiLogger upload site. In a quick comparison to my Cumulus realtime.txt site and the WiFiLogger realtime.txt site all the current data seems the same. Not sure what else may be different in your template between the Cumulus and the other versions.
Regards,
Paul
i looked at the json file to see if i could implement that but got lost on some of the fields .. anyway realtime.txt is a good simple solution to get it of the ground..brian
Thanks. Updated to 1.21 and sorry to say, took all html. I Hope this would not effect something else?Got the wifilogger and it is sending to wunderground, but the new thing logging to ftp, can't get it to work.
No file what so ever is written to my ftp....?
download this version http://wifilogger.net/files/WiFiLogger121.zip
download update guide http://wifilogger.net/files/WiFiLoggerUpdate.pdf
Check what WiFiLogger firmware version you have.
If you have versiob lower than 1.19 then please upload all HTML files.
If you have version 1.19 please upload only ftpexport.html file.
Navigate to SETUP| Archive Export Setup
go to bottom of this page.
There you can setup your FTP. Please not that you have put name of the server. IP number is not yet served.
Please check my settings
[ You are not allowed to view attachments ]
|
You can open debug window to checkThanks. Updated to 1.21 and sorry to say, took all html. I Hope this would not effect something else?Got the wifilogger and it is sending to wunderground, but the new thing logging to ftp, can't get it to work.
No file what so ever is written to my ftp....?
download this version http://wifilogger.net/files/WiFiLogger121.zip
download update guide http://wifilogger.net/files/WiFiLoggerUpdate.pdf
Check what WiFiLogger firmware version you have.
If you have versiob lower than 1.19 then please upload all HTML files.
If you have version 1.19 please upload only ftpexport.html file.
Navigate to SETUP| Archive Export Setup
go to bottom of this page.
There you can setup your FTP. Please not that you have put name of the server. IP number is not yet served.
Please check my settings
[ You are not allowed to view attachments ]
Made the setup and nothing.....? 😲🙄
Please make sure that you have folder on server WFL don't create foldersI initially had mine getting lost. I changed the Folder path to /public_html/wifi-console/ and that put realtime.txt and json files in my site's /wifi-console folder
path should be
/
/stationFolder/
etc.
Very nice with the Weather34 template: http://www.actulife.com/pws (http://www.actulife.com/pws)
I like this (http://www.wxforum.net/Smileys/default/eusa_dance.gif)
ok - next challenge. I'm trying to add a webcam image (from Arlo). I copy/modified a python script to take a snapshot, scheduled this with Windows task manager to put in a dropbox folder that syncs to the web. My webcam image is inserted into webcamsmall.php in the below text, but it doesn't work, any ideas why? I'm very "old school" with html and don't understand php.
<img src="https://www.dropbox.com/s/3cwuo5dbb6me4jj/snapshot.jpg?version=<?php echo filemtime("https://www.dropbox.com/s/3cwuo5dbb6me4jj/snapshot.jpg");?>" alt="weathercam" class="webcam">
Please note, the current web cam image doesn't look very nice since my Arlo is charging.
I have a feeling that maybe the dimensions of my webcam image are the problem, but I don't have an easy way to resize.
ok - next challenge. I'm trying to add a webcam image (from Arlo). I copy/modified a python script to take a snapshot, scheduled this with Windows task manager to put in a dropbox folder that syncs to the web. My webcam image is inserted into webcamsmall.php in the below text, but it doesn't work, any ideas why? I'm very "old school" with html and don't understand php.
<img src="https://www.dropbox.com/s/3cwuo5dbb6me4jj/snapshot.jpg?version=<?php echo filemtime("https://www.dropbox.com/s/3cwuo5dbb6me4jj/snapshot.jpg");?>" alt="weathercam" class="webcam">
Please note, the current web cam image doesn't look very nice since my Arlo is charging.
I have a feeling that maybe the dimensions of my webcam image are the problem, but I don't have an easy way to resize.
still doesn't work - I tried multiple times, but is this correct?
<img src="https://www.dropbox.com/s/3cwuo5dbb6me4jj/snapshot.jpg?raw=1?php echo filemtime("https://www.dropbox.com/s/3cwuo5dbb6me4jj/snapshot.jpg");?>" alt="weathercam" class="webcam">
does the word "version" still need to be there?
This weekend I'll have the first major test of my new weatherstation as the remnants of hurricane Florence pass by my home (near Charlotte, NC). I have a whole house generator and ups backup for my server/computer/console, but my past experience is that my cable internet connection only lasts for about an hour after the power goes off. I'd like to keep broadcasting the weather data to WU and my new website, but I'm wondering if there is a break in internet connection, will WIFI logger automatically transmit all of the data it has collected while the internet is down, or will these "packets" be lost as far as WU is concerned?
so I’m not sure I understand - currently there’s no way to update WU (for year to date, etc. charting) if say 5 inches of rain was missed due to internet outage?
I'm getting the spikes too on weather underground.
Ok... Right now I have it going to my raspberry pi that is a ntp gps pps time server.
so I’m not sure I understand - currently there’s no way to update WU (for year to date, etc. charting) if say 5 inches of rain was missed due to internet outage?
Now WFL is transmitting current data when it can.
WU takes two rain values: day rain and hour rain. If WFL will be lack of the Internet for 24h WU will miss that rain.
so I’m not sure I understand - currently there’s no way to update WU (for year to date, etc. charting) if say 5 inches of rain was missed due to internet outage?
Now WFL is transmitting current data when it can.
WU takes two rain values: day rain and hour rain. If WFL will be lack of the Internet for 24h WU will miss that rain.
Ok - so as long as I have power, and the outage is less than a day, there will be no loss of rainfall? That’s nice!
Ok... Right now I have it going to my raspberry pi that is a ntp gps pps time server.
I think problem is when NTP is renew, it's updating UTC time, then is recalculated to console local time.
Spikes are data shifted in time. UTC +/- Time zone +/- summer time.
When you disable NTP in WFL, then it will stop updating internal WFL timers UTC and Local.
Please check it. That will help to solve this problem.
Let me also add that with battery back power it will still keep logging data. I'm not sure of the days but the shorter archive interval you have the quicker the data builds up. Example a 1 minute interval will fill up the memory faster then say a 10 minute interval. The exact days are somewhere in this thread somewhere.so I’m not sure I understand - currently there’s no way to update WU (for year to date, etc. charting) if say 5 inches of rain was missed due to internet outage?
Now WFL is transmitting current data when it can.
WU takes two rain values: day rain and hour rain. If WFL will be lack of the Internet for 24h WU will miss that rain.
Ok - so as long as I have power, and the outage is less than a day, there will be no loss of rainfall? That’s nice!
(Hint for exportfile. Don't use the same separator inside bracket-values as separator used to separate different items.)
Too late for me, just finished the update 10 min ago :(
Should I go back or just wait it out?
Enjoy,Paul
Should I be watching for something in particular?No Paul. If you are interested in MQTT this option is now avaible. Also I have add weathercloud.net service.
Enjoy,
Paul
I've tried to understand MQTT and see how or for what I could use that, but not there yet :oops:
Should I be watching for something in particular?No Paul. If you are interested in MQTT this option is now avaible. Also I have add weathercloud.net service.
Enjoy,
Paul
+ now you can use IP address for NTP/FTP, before was only server name allowed.
I hope that this problem with time shifting on WU was repaired now.
15 min for NTP is to much in my opinion. I don't think that time synchronization is needed so frequently.
It always checking time on startup. When NTP time was reach from the Internet then console time is checked and updated.
1 min can be diffrence between console and NTP. With bigger difference console time will be updated.
In my opionion this mechanizm can be triggered 2-4 times a day (interval 360-720)
With version 1.23 can I re-enable the NTP?Should I be watching for something in particular?No Paul. If you are interested in MQTT this option is now avaible. Also I have add weathercloud.net service.
Enjoy,
Paul
+ now you can use IP address for NTP/FTP, before was only server name allowed.
I hope that this problem with time shifting on WU was repaired now.
15 min for NTP is to much in my opinion. I don't think that time synchronization is needed so frequently.
It always checking time on startup. When NTP time was reach from the Internet then console time is checked and updated.
1 min can be diffrence between console and NTP. With bigger difference console time will be updated.
In my opionion this mechanizm can be triggered 2-4 times a day (interval 360-720)
With version 1.23 can I re-enable the NTP?Should I be watching for something in particular?No Paul. If you are interested in MQTT this option is now avaible. Also I have add weathercloud.net service.
Enjoy,
Paul
+ now you can use IP address for NTP/FTP, before was only server name allowed.
I hope that this problem with time shifting on WU was repaired now.
15 min for NTP is to much in my opinion. I don't think that time synchronization is needed so frequently.
It always checking time on startup. When NTP time was reach from the Internet then console time is checked and updated.
1 min can be diffrence between console and NTP. With bigger difference console time will be updated.
In my opionion this mechanizm can be triggered 2-4 times a day (interval 360-720)
Yes I have make changes in NTP function. Now WU should work ok. Please let me know if there are still problems.
I have to say this is a great piece of kit - installed fairly easily into my Vantage Vue and the real time data webpage is great. I do however have one query - I am running WeatherLink 6.0.4 locally on a PC and have set up the TCP/IP connections for it (TCP port is 22222) It successfully found the WiFi Logger but now when I try to poll data into WeatherLink I often get Communication error - it has polled successfulyl 3 times today but in the comms log it keeps saying communication error. I am running v1.20 firmware on the logger. On the logger I have the web interface enabled and TCP port set to Auto Pause with pause duration of 10 mins. On Weatherlink it is set to poll hourly at 2 mins past the hour. Is there anything else I need to set up/look at to enable both the real time page and WeatherLink to populate. ThanksPause duration works with manual pause. On first page Real Time Data you trigger manual pause by clicking time. This is old function probably I will erase that function.
(Hint for exportfile. Don't use the same separator inside bracket-values as separator used to separate different items.)
I am not sure if I am understanding.
Could you paste example?
Also. When I access the System menu, the button on updating html-files is clickable, but the button to make system-upgrade isn't. it's disabled.
Cheers.
PS. Thanks for a fine product.
No change. Using Firefox. Tried to do it on my phone and it worked.Also. When I access the System menu, the button on updating html-files is clickable, but the button to make system-upgrade isn't. it's disabled.
Cheers.
PS. Thanks for a fine product.
Try to upload once more "system.html" and "spark-md5.js". Please use system.html from newest firmware.
Which web browser do you use?
This button will be enabled when proper information from WFL will comes, but it's 2s delay. Do you know how to use debug console in
Chrome? CTRL + SHIFT + J -> then Network tab
File is in JSON format. You don't need to parse it. It's very common file. You need to find library which will parce it for you.
http://php.net/manual/en/function.json-decode.php
https://www.w3schools.com/js/js_json_parse.asp
The Realtime.txt, where is this file supposed to end up?In my FTP Archive Records Export Setup tab I have Folder path: /public_html/wifi-console
The only file I get is the wflexp.json.QuoteThe Realtime.txt, where is this file supposed to end up?In my FTP Archive Records Export Setup tab I have Folder path: /public_html/wifi-console
to get http://www.komokaweather.com/wifi-console/realtime.txt
Enjoy,
Paul
The only file I get is the wflexp.json.Wojtek may have an answer.
I'm on v1.23, but I only get .json..... (guess I'm too picky, but it would be great to be able to see that the whole system is updated ok to match 1.23.)QuoteThe only file I get is the wflexp.json.Wojtek may have an answer.
From that one setting in FTP Archive Records Export setup I get both realtime.txt and wflexp.json
http://www.komokaweather.com/wifi-console/wflexp.json
http://www.komokaweather.com/wifi-console/realtime.txt
I am on v1.23
Enjoy,
Paul
I'm on v1.23, but I only get .json..... (guess I'm too picky, but it would be great to be able to see that the whole system is updated ok to match 1.23.)
Edit: Reinstalled 1.23, still no file.
Started Debug on Firefox and gotI'm on v1.23, but I only get .json..... (guess I'm too picky, but it would be great to be able to see that the whole system is updated ok to match 1.23.)
Edit: Reinstalled 1.23, still no file.
Probably your FTP server is using some other commands. Please open http://IP_WFL/debug wait for interaval time or click on TEST text in FTP windows.
You will have information like below. Could you send it to me on priv or share with us here?
Command connected
220 ProFTPD 1.3.5a Server (Debian) [185.135.88.161]
331 Password required for username
230 User username logged in
215 UNIX Type: L8
200 Type set to I
227 Entering Passive Mode (185,135,88,161,152,121).
FTPPasv: Data port: 39033
FTPPasv: Data connected
150 Opening BINARY mode data connection for /public_html/station/wflexp.json
FTP Writing
226 Transfer complete
Data disconnected
227 Entering Passive Mode (185,135,88,161,170,131).
FTPPasv: Data port: 43651
FTPPasv: Data connected
150 Opening BINARY mode data connection for /public_html/station/realtime.txt
FTP Writing
226 Transfer complete
Data disconnected
200 Type set to A
221 Goodbye.
Command disconnected
Edit.http://wifilogger.net/files/WFLexport.xlsx
I think I've seen somewhere in the thread about all the parameters in the file, but can't find it. Someone who can help me? (Meaning of them.)
Thanks!Edit.http://wifilogger.net/files/WFLexport.xlsx
I think I've seen somewhere in the thread about all the parameters in the file, but can't find it. Someone who can help me? (Meaning of them.)
You need to click on white button on WFL. It will reboot WFL. Don't reboot console if it works, just WFL itself.
Data are stored as archive records on flash memory, regular logger feature. You can always download it.
WFL is not making own cache, just transmit what can get from console.
You need to click on white button on WFL. It will reboot WFL. Don't reboot console if it works, just WFL itself.
Data are stored as archive records on flash memory, regular logger feature. You can always download it.
WFL is not making own cache, just transmit what can get from console.
When I press the white button to reset it, how much of a history is saved? Obviously set by amount of flash memory but generally like 30 days or so? (I’m out of the country and concerned that if we press the white button before I get back, all the history will be overwritten ...
This is a fantastic product. Just wrote a custom parser that reads wflexp.json and sends the data to my RainMachine sprinkler system.
Happy to have received my WiFiLogger yesterday. I am in the midst of setting it up and have run into a problem. Not sure if I should post it here or try for the developer's support email directly.
Because of the layout of my home, my primary router (192.168.x.x) doesn't reach easily from one end to the other. As such, I put in a secondary router (10.0.x.x) linked to the first through a powerline link. It's worked great for years. The secondary router, because of the central location in the house, provides my "guest" wifi that is isolated from my home's main wifi. I use that for guests as well as IoT devices in case they like to snoop around (not that they every would :roll:). As an IoT device, I put the WiFiLogger on the public wifi. I have a network at home that incorporates PiHole as my DNS on a RaspberryPi to help filter content across my entire network, but it has rarely caused problems for some devices. For those devices, I switch from the DNS from the PiHole to Google's 8.8.8.8 on those specific devices. However, I cannot change that setting in the WiFiLogger. It keeps reverting to the Gateway setting of the router, even if I press "save" on the screen.
I am able to connect to the WiFiLogger as indicated in the instructions during the setup mode. I am able to see a "connected" status on the device after setup and can see a number of the local wifi SSID's. I can see real-time weather data, which is terrific. I entered in my Wunderground and WeatherLink information. Unfortunately, when I try to finalize setup by resetting the device and connecting through the local IP on the router and not the 192.168.4.1 address, I am unable to connect, getting a timeout error. I checked the secondary router and confirmed the IP address had been issued to the WiFiLogger, but I cannot connect to it, whether I am on the public or private wifi of the secondary router. I have disabled the PiHole, with no success. I went to the primary router's setting, which generates the main DNS routing through the PiHole and reverted the DNS to the local cable provider's automatic setting, yet still no luck. The other devices are able to connect to the internet, regardless of whether I have the automatically-provided DNS from the cable company or the PiHole DNS.
Any thoughts on how I can troubleshoot this? I confess the only change I've not made is to update the firmware yet.
So, explain to me how it's uploading data to both WeatherUnderground and WeatherLink 2.0. So, I'm happy it's working, but I don't know why I cannot connect to it using the IP address assigned by the router.
Dear Wojtek,
Congratulations on your marvelous invention. I've just bought a Davis Instrument Pro2 6163 with UV and solar sensors and would love to buy your gadget and hook it up to my console.
I have read in forums that data from the sensors are transmitted to the console every 2.5 seconds and I have two questions.
1) Does WFL capture this data and sends it every 2.5 seconds or does it send it every minute?
2) Can I customize the WFL to send this raw data to automatically update an existing text file / database on an FTP server / file share?
Thanks and great work.
Chris
I'm thoroughly confused now. As you suggested, I'd gone through the reset after setting up the wifi. I tried to use the new IP address and not the setup IP address, but no luck. So, explain to me how it's uploading data to both WeatherUnderground and WeatherLink 2.0. So, I'm happy it's working, but I don't know why I cannot connect to it using the IP address assigned by the router.
The wonderful WeatherUnderground and WeatherLink signature links don't seem to work. I'm sure there are many comments and threads to address this, but I don't have time to figure out another problem. I'm just thrilled I seem to be getting most data (except barometric data) out to the 'net. My station is
So data can be collected at around circa 6 seconds - I understand your hardware and software latencies argument. So what is the best way forward to get the data "out" of the console as soon as it is available? Can the WFL write the data to a share or can I have a server poll the data from the WFL and manage the sync?
Are there any forum members who know whether the WiFiLogger Davis console interface functions with WeatherCat 3, Apple Mac OSX Software?
https://trixology.com/weathercat/
Thanks.
Are there any forum members who know whether the WiFiLogger Davis console interface functions with WeatherCat 3, Apple Mac OSX Software?Just got the logger today. Set up was easy as pie and so was the firmware update. All weather sites receiving data. Except I'm stumped on the WeatherCat set up. Not sure how to go about it. Anyone?
https://trixology.com/weathercat/
Thanks.
Are there any forum members who know whether the WiFiLogger Davis console interface functions with WeatherCat 3, Apple Mac OSX Software?Just got the logger today. Set up was easy as pie and so was the firmware update. All weather sites receiving data. Except I'm stumped on the WeatherCat set up. Not sure how to go about it. Anyone?
https://trixology.com/weathercat/
Thanks.
Please go to SETUP|SYSTEM set TCP port as AUTO PAUSE.
In SETUP|WIFI SETUP you will find TCP port number. Default is 22222, please just check if it's not 0.
You should be able to connect WeatherCat by writing ip address of WFL. Interface the same like WL IP.
Please note that AUTO PAUSE has safety feature. It will reject client when there is no data transfer from WeatherCar to WFL in 60s. Cumulus works like this just start command to continues data transfer from console and no other activity from Cumulus. So WFL will reject Cumulus, but Cumulus has feature to release connection every minute. WL IP and WFL can make own uploads in this "DISCON PERIOD".
I don't know how WeatherCat is working. I hope there will be no problem with it.
Question.
When looking at the Real Time Data on the loggers homepage it looked a bit strange.
Under the heading Today's Highs, wind it says, 2,7m/s at 0:04. But when I looked in the .json-file it said 6,0 at 0:00.
Why doesn't the json-file get the right timestamp?
I have a couple of strange things -There are two possibilities. One is that you have assigned a fixed IP address to the Logger in its own setup, but the network's DHCP server (which, of course, has no way of knowing this!) has now assigned that address to another device. Alternatively, you may simply be allowing the DHCP server, which is usually associated with the router, to assign the WiFiLogger's address 'at random' rather than specifying (preferably in the router's control panel rather than on the Logger itself!) a fixed address.
1. It appears that my local IP address for WiFiLogger has changed. Now when I use 192.168.0.25 (which has been the IP) it asks for user name and password and is for a different device on my network. I have tried all IPs from 192.168.0.10 to 192.168.0.40 and have not found the correct one for WiFiLogger.
Any suggestion on how I can connect to the WiFiLogger settings, etc?
Paul
hi Wojtek.
Been up and running about 4 months now. Updating on a regular basis. I was using v120 and noticed v123 was out, so I updated the firmware and .. well now Weatherlink.com (I use Weatherlink IP) account has no archive data. I updated the firmware about 9:45 Pm last night. All archive data stopped at 9:45 PM.
It's only weatherlink though, all other weather sites I download to are showing all current data and history as usual. So I went back to firmware v 120 and all is good now. Any Idea whats Up?
BTW: My WL Bulletin page showed current conditions except for the barometer. It was stuck at 29.883 in/hg the whole time.
I have a couple of strange things -
1. It appears that my local IP address for WiFiLogger has changed. Now when I use 192.168.0.25 (which has been the IP) it asks for user name and password and is for a different device on my network. I have tried all IPs from 192.168.0.10 to 192.168.0.40 and have not found the correct one for WiFiLogger.
2. WiFiLogger continues to update WU http://www.pwsweather.com/obs/KOMOKA2.html but sometimes at longer than the set 5 min interval so not a big deal. However PWS, CWOP, WL and others are only updating occasionally - sometimes hours in between like http://www.pwsweather.com/obs/KOMOKA2.html
Any suggestion on how I can connect to the WiFiLogger settings, etc?
Paul
I have a couple of strange things -There are two possibilities. One is that you have assigned a fixed IP address to the Logger in its own setup, but the network's DHCP server (which, of course, has no way of knowing this!) has now assigned that address to another device. Alternatively, you may simply be allowing the DHCP server, which is usually associated with the router, to assign the WiFiLogger's address 'at random' rather than specifying (preferably in the router's control panel rather than on the Logger itself!) a fixed address.
1. It appears that my local IP address for WiFiLogger has changed. Now when I use 192.168.0.25 (which has been the IP) it asks for user name and password and is for a different device on my network. I have tried all IPs from 192.168.0.10 to 192.168.0.40 and have not found the correct one for WiFiLogger.
Any suggestion on how I can connect to the WiFiLogger settings, etc?
Paul
Assuming the latter, if you login to the router's control panel (usually at 192.168.n.1, where n is zero for your network), you should be able to see what address is assigned to the Logger and to specify an address for it to use in future. If you then reboot the router and the Logger (in that order), it should continue to use the address you have set for the future.
If you originally set the fixed address 'locally' on the Logger, and the router now has something else at that address, as well, the easiest solution is likely to be to disconnect the 'interfering' device, and reboot the router and Logger, when you should be able to access it again. When you can do this, set the logger back to its default of getting its IP address from the router and proceed as above to specify a fixed address for it in the router's control panel.
Changed my loggingtime from 3 to 10 minutes and got loctime = 1617469200. What happened????? (Sat 3 2021 17:00)I will rewrite NTP function. Something is wrong with this feature. At this moment is async function. I will put it into queue. I hope that will help.
Since I parse the data into db I check if new time is bigger than old time, I didn't get any data. Strange....
Hello, I have a question.
If I want to upload in Wifi Logger a modified version of html pages, how much memory do I have available?
I have a couple of strange things -There are two possibilities. One is that you have assigned a fixed IP address to the Logger in its own setup, but the network's DHCP server (which, of course, has no way of knowing this!) has now assigned that address to another device. Alternatively, you may simply be allowing the DHCP server, which is usually associated with the router, to assign the WiFiLogger's address 'at random' rather than specifying (preferably in the router's control panel rather than on the Logger itself!) a fixed address.
1. It appears that my local IP address for WiFiLogger has changed. Now when I use 192.168.0.25 (which has been the IP) it asks for user name and password and is for a different device on my network. I have tried all IPs from 192.168.0.10 to 192.168.0.40 and have not found the correct one for WiFiLogger.
Any suggestion on how I can connect to the WiFiLogger settings, etc?
Paul
Assuming the latter, if you login to the router's control panel (usually at 192.168.n.1, where n is zero for your network), you should be able to see what address is assigned to the Logger and to specify an address for it to use in future. If you then reboot the router and the Logger (in that order), it should continue to use the address you have set for the future.
If you originally set the fixed address 'locally' on the Logger, and the router now has something else at that address, as well, the easiest solution is likely to be to disconnect the 'interfering' device, and reboot the router and Logger, when you should be able to access it again. When you can do this, set the logger back to its default of getting its IP address from the router and proceed as above to specify a fixed address for it in the router's control panel.
Thats right. You can have two devices with same IP address. That makes a lot of problems. When you trying to log to this IP, then once you have luck to log to first one, then after a few sec. you are connected to second.
Example. You have log to WFL web page, but when you trying to save some settings those can be send to second device with same IP address.
Routers have very nice feature called DHCP. This service server IP addresses to devices when those are being connected.
Without that you should write all network settings manually. IP, netmask, gateway, dns.
You have to check DHCP range and for static IP you should use addresses beyond range.
I have a couple of strange things -There are two possibilities. One is that you have assigned a fixed IP address to the Logger in its own setup, but the network's DHCP server (which, of course, has no way of knowing this!) has now assigned that address to another device. Alternatively, you may simply be allowing the DHCP server, which is usually associated with the router, to assign the WiFiLogger's address 'at random' rather than specifying (preferably in the router's control panel rather than on the Logger itself!) a fixed address.
1. It appears that my local IP address for WiFiLogger has changed. Now when I use 192.168.0.25 (which has been the IP) it asks for user name and password and is for a different device on my network. I have tried all IPs from 192.168.0.10 to 192.168.0.40 and have not found the correct one for WiFiLogger.
Any suggestion on how I can connect to the WiFiLogger settings, etc?
Paul
Assuming the latter, if you login to the router's control panel (usually at 192.168.n.1, where n is zero for your network), you should be able to see what address is assigned to the Logger and to specify an address for it to use in future. If you then reboot the router and the Logger (in that order), it should continue to use the address you have set for the future.
If you originally set the fixed address 'locally' on the Logger, and the router now has something else at that address, as well, the easiest solution is likely to be to disconnect the 'interfering' device, and reboot the router and Logger, when you should be able to access it again. When you can do this, set the logger back to its default of getting its IP address from the router and proceed as above to specify a fixed address for it in the router's control panel.
Thats right. You can have two devices with same IP address. That makes a lot of problems. When you trying to log to this IP, then once you have luck to log to first one, then after a few sec. you are connected to second.
Example. You have log to WFL web page, but when you trying to save some settings those can be send to second device with same IP address.
Routers have very nice feature called DHCP. This service server IP addresses to devices when those are being connected.
Without that you should write all network settings manually. IP, netmask, gateway, dns.
You have to check DHCP range and for static IP you should use addresses beyond range.
Back to the same problem. I had pressed WiFiLogger red button and no change. I did a complete shut down and power off of the Modem/Router and then got WiFiLigger back to 192.168.0.25 so all was good then.[ You are not allowed to view attachments ]
During the time that I could not find WiFiLogger IP the WU updates were occurring mostly at the 5 min interval and occasionally at a bit longer. However all the other uploads, PWS, WL, CWOP were only updating with most times hours in between. When it was back at 192.168.0.25 all the updates were occurring again at the 5 min interval.
Then yesterday, as Wojtek had cautioned, the IP address changed again and can't find/access WiFiLogger and the uploads are again hours apart except WU updates which continue at the 5 min interval or close to it.
I really don't understand DHCP and static or fixed or other IP setting, nor most of the Hitron modem setting options. WiFiLogger had just been working perfect for months until this started over the past week. I have periodically gone in the modem/router settings and looked at the IP address for the various devices and have seen MAC address to be usually consistent but the IP addresses, at least the ones that show, to vary often except two: my weather computer is always at .13 and my Blitzortung is at .16. I think I had some guidance in the past from somewhere where to set the computer fixed IP and also from the Blitzortung assistance.
I likely can get WiFiLogger back to a known IP by re-powering the modem/router but expect it would change later on. So exactly how/where could I set a fixed IP for WiFiLogger? I have looked in settings but can't see where/how to do that.
Also what could be the reason that WU http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=IMIDDLES37 continues to be updated but others like PWS http://www.pwsweather.com/obs/KOMOKA2.html and CWOP http://www.findu.com/cgi-bin/wxpage.cgi?call=FW2530 only occasionally.
Thanks for any further help,
Paul
DHCP end IP: 192.168.0.199 and should this now be changed to 192.168.0.250 as I changed WiFiLogger IP to 192.168.0.250?
Finally got some rain here.
Console reporting 114mm/h, logger 0mm.
Console reporting 3mm last hour, logger 1mm.
logger, Stormrain, 3mm.
Cumulus reporting 3mm last hour.
Daily high wind at 00:12 1,3m/s
Cumulus 04:35 1,3m/s
I could have made some mistake, but I checked and checked.....
What is the latest version of SW?
Jason, the other file doesn't upload.Finally got some rain here.
Console reporting 114mm/h, logger 0mm.
Console reporting 3mm last hour, logger 1mm.
logger, Stormrain, 3mm.
Cumulus reporting 3mm last hour.
Daily high wind at 00:12 1,3m/s
Cumulus 04:35 1,3m/s
I could have made some mistake, but I checked and checked.....
What is the latest version of SW?
1.23 I don't have newer, but will be.
Using which export method do you use?
Please note that JSON export is in console native units. You have F, mph, inch.
Got mine from Prodata just the other day, and got it all working.
However I thought I should upgrade my VP2 firmware from 3.15 to 3.80, it fails to complete the firmware upgrade.
It reads the console to tell it that it's on the 3.15 firmware, and let's me go ahead with it.
Comes up with the error :-
Problem entering boot section, check fuse bits!
Is this something Davis requires, one of their genuine WLIP's or is there something else ?
I've got two failed Davis WLIP's here, so I can't use either of them to try it out.
Jason, the other file doesn't upload.Finally got some rain here.
Console reporting 114mm/h, logger 0mm.
Console reporting 3mm last hour, logger 1mm.
logger, Stormrain, 3mm.
Cumulus reporting 3mm last hour.
Daily high wind at 00:12 1,3m/s
Cumulus 04:35 1,3m/s
I could have made some mistake, but I checked and checked.....
What is the latest version of SW?
1.23 I don't have newer, but will be.
Using which export method do you use?
Please note that JSON export is in console native units. You have F, mph, inch.
Recalculating to mm.
However I thought I should upgrade my VP2 firmware from 3.15 to 3.80, it fails to complete the firmware upgrade.
It reads the console to tell it that it's on the 3.15 firmware, and let's me go ahead with it.
Comes up with the error :-
Problem entering boot section, check fuse bits!
Console is still working or it is not?
"Problem entering boot section, check fuse bits!" this is from Davis update tool? Or from console?
You should go to SETUP|SYSTEM and change TCP port mode to AUTO PAUSE. I need to change AUTO PAUSE to be default.
1. Set Auto Pause
2. power off, then power on console with logger
3. run Davis update tool again.
I have tried this many times with success and with interference. All work perfectly. After fail you are able to make it again and again.
Let us know if everything is alright.
Console did initially lock up, but power cycle brought it back.However I thought I should upgrade my VP2 firmware from 3.15 to 3.80, it fails to complete the firmware upgrade.Console is still working or it is not?
It reads the console to tell it that it's on the 3.15 firmware, and let's me go ahead with it.
Comes up with the error :-
Problem entering boot section, check fuse bits!
"Problem entering boot section, check fuse bits!" this is from Davis update tool? Or from console?
You should go to SETUP|SYSTEM and change TCP port mode to AUTO PAUSE. I need to change AUTO PAUSE to be default.
1. Set Auto Pause
2. power off, then power on console with logger
3. run Davis update tool again.
I have tried this many times with success and with interference. All work perfectly. After fail you are able to make it again and again.
Let us know if everything is alright.
Step 2, remove battery and power from console then reconnect.... done.
I Find local id okay, then start it.
sometimes comes up can't find, then other times it finds it okay.
still getting that initial error.
My VP2 has Bootware 1.2
Yes, using both untill I know everything is reliable.Jason, the other file doesn't upload.Finally got some rain here.
Console reporting 114mm/h, logger 0mm.
Console reporting 3mm last hour, logger 1mm.
logger, Stormrain, 3mm.
Cumulus reporting 3mm last hour.
Daily high wind at 00:12 1,3m/s
Cumulus 04:35 1,3m/s
I could have made some mistake, but I checked and checked.....
What is the latest version of SW?
1.23 I don't have newer, but will be.
Using which export method do you use?
Please note that JSON export is in console native units. You have F, mph, inch.
Recalculating to mm.
Lars probably you are the only user of this JSON file up to date.
Do you use Cumulus and WFL exports in same time?
Yes, using both untill I know everything is reliable.
Json is very easy to use uploading all the data into a db all by it self with a cronjob.
I've written a php-script that is run by cron. The script parses the json file and upload to db.QuoteYes, using both untill I know everything is reliable.
Json is very easy to use uploading all the data into a db all by it self with a cronjob.
Could you share in a step-by-step how to import to db? I have a db with several tables which are imported regularly for Meteotemplate and also a Cumulus once a minute by cron job. Both of these with scripts and instruction by others and I have no knowledge how I would add a new one.
Thanks,
Paul
Wojtek.
When the month changed, all data from hlrainr except year disappeared!????
/Lars
Finally got some rain here.
Console reporting 114mm/h, logger 0mm.
Console reporting 3mm last hour, logger 1mm.
logger, Stormrain, 3mm.
Cumulus reporting 3mm last hour.
Daily high wind at 00:12 1,3m/s
Cumulus 04:35 1,3m/s
Wojtek.
When the month changed, all data from hlrainr except year disappeared!????
/Lars
Lars could you paste example?
Hi.Wojtek.
When the month changed, all data from hlrainr except year disappeared!????
/Lars
Lars could you paste example?
Have set the rainperiod start to january.
Data last month,
0.00;0.11;---;6:26;0.92;---;4.49;---
Data this month,
0.00;0.00;---;---;0.00;---;4.49;---
/L
Actually I don't get it. What's the point of having rainmon if that is the same as month in hlrainr. If it is connected to calendar month in both, it should show the same. Otherwise the hlrainr should not be zeroed until the Rain period starts, setting in console. The function would then be the same as the year doesn't zero until 1/1. If the high low zeroes each month, what does rainmon do?Hi.Wojtek.
When the month changed, all data from hlrainr except year disappeared!????
/Lars
Lars could you paste example?
Have set the rainperiod start to january.
Data last month,
0.00;0.11;---;6:26;0.92;---;4.49;---
Data this month,
0.00;0.00;---;---;0.00;---;4.49;---
/L
HiLow data have schema:
Outside Temp Section
Day Low Out Temp
Day Hi Out Temp
Time Day Low Out Temp
Time Day Hi Out Temp
Month Hi Out Temp
Month Low Out Temp
Year Hi Out Temp
Year Low Out Temp
When day is starting (0:00) first 4 data are zero or dash, when month is starting data 4 and 5 (month hi/low) will be cleared. On 01.01.2019 you will have all zero or dashed.
Those data are from console. Davis works like this.
All I need to make is better interface for arch records and send them via MQTT as JSON. Console data + arch. records makes weather data complete.
e.g. in arch data you will have rain in arch period (30 min). In console loop data you will have data like RAIN: last 15 min, RAIN: last hour, RAIN: day, RAIN: last 24h, RAIN: month, RAIN: year.
Only when you combine those two (loop + arch.) weather data are complete
Actually I don't get it. What's the point of having rainmon if that is the same as month in hlrainr. If it is connected to calendar month in both, it should show the same. Otherwise the hlrainr should not be zeroed until the Rain period starts, setting in console. The function would then be the same as the year doesn't zero until 1/1. If the high low zeroes each month, what does rainmon do?Hi.Wojtek.
When the month changed, all data from hlrainr except year disappeared!????
/Lars
Lars could you paste example?
Have set the rainperiod start to january.
Data last month,
0.00;0.11;---;6:26;0.92;---;4.49;---
Data this month,
0.00;0.00;---;---;0.00;---;4.49;---
/L
HiLow data have schema:
Outside Temp Section
Day Low Out Temp
Day Hi Out Temp
Time Day Low Out Temp
Time Day Hi Out Temp
Month Hi Out Temp
Month Low Out Temp
Year Hi Out Temp
Year Low Out Temp
When day is starting (0:00) first 4 data are zero or dash, when month is starting data 4 and 5 (month hi/low) will be cleared. On 01.01.2019 you will have all zero or dashed.
Those data are from console. Davis works like this.
All I need to make is better interface for arch records and send them via MQTT as JSON. Console data + arch. records makes weather data complete.
e.g. in arch data you will have rain in arch period (30 min). In console loop data you will have data like RAIN: last 15 min, RAIN: last hour, RAIN: day, RAIN: last 24h, RAIN: month, RAIN: year.
Only when you combine those two (loop + arch.) weather data are complete
Sorry for my perhaps strange questions.
Actually I don't get it. What's the point of having rainmon if that is the same as month in hlrainr. If it is connected to calendar month in both, it should show the same. Otherwise the hlrainr should not be zeroed until the Rain period starts, setting in console. The function would then be the same as the year doesn't zero until 1/1. If the high low zeroes each month, what does rainmon do?Hi.Wojtek.
When the month changed, all data from hlrainr except year disappeared!????
/Lars
Lars could you paste example?
Have set the rainperiod start to january.
Data last month,
0.00;0.11;---;6:26;0.92;---;4.49;---
Data this month,
0.00;0.00;---;---;0.00;---;4.49;---
/L
HiLow data have schema:
Outside Temp Section
Day Low Out Temp
Day Hi Out Temp
Time Day Low Out Temp
Time Day Hi Out Temp
Month Hi Out Temp
Month Low Out Temp
Year Hi Out Temp
Year Low Out Temp
When day is starting (0:00) first 4 data are zero or dash, when month is starting data 4 and 5 (month hi/low) will be cleared. On 01.01.2019 you will have all zero or dashed.
Those data are from console. Davis works like this.
All I need to make is better interface for arch records and send them via MQTT as JSON. Console data + arch. records makes weather data complete.
e.g. in arch data you will have rain in arch period (30 min). In console loop data you will have data like RAIN: last 15 min, RAIN: last hour, RAIN: day, RAIN: last 24h, RAIN: month, RAIN: year.
Only when you combine those two (loop + arch.) weather data are complete
Sorry for my perhaps strange questions.
Daylight savings time change this morning:Same thing here. Everything had to be done manually.
My Envoy/USB/Cumulus and my standalone VP2 console made the time change ok,
however my Vue console and WiFiLogger did not change back the one hour. The Vue was set as Daylight Savings Auto, Eastern Standard Time UTC -5. WiFiLogger was set at GMT: -05:00 Eastern Time, Daylight Savings - Auto ticked.
I manually changed the time in the Vue console, and also in WiFiLogger station set up so all is fine now.
Enjoy,
Paul
Daylight savings time change this morning:Same thing here. Everything had to be done manually.
My Envoy/USB/Cumulus and my standalone VP2 console made the time change ok,
however my Vue console and WiFiLogger did not change back the one hour. The Vue was set as Daylight Savings Auto, Eastern Standard Time UTC -5. WiFiLogger was set at GMT: -05:00 Eastern Time, Daylight Savings - Auto ticked.
I manually changed the time in the Vue console, and also in WiFiLogger station set up so all is fine now.
Enjoy,
Paul
how do I get a device id and key to enter into the WFL setup screen for Weather link?
how do I get a device id and key to enter into the WFL setup screen for Weather link?
I've uploaded some instructions to our Davis knowledgebase. Please see:
https://www.manula.com/manuals/pws/davis-kb/1/en/topic/wfl-uploads-to-weatherlink-com (https://www.manula.com/manuals/pws/davis-kb/1/en/topic/wfl-uploads-to-weatherlink-com)
Should we select WL IP or WL PC for the mode?
1 Will this device upload automatically to my website, how does it know what software I am runningWiFiLogger has abiliti to export via FTP two files: WFL JSON file with all current and hilow data from console. Realtime.txt file similar to Cumulus, but it contains only data which are represented in console memory. Cumulus makes own statistics. WFL export only console data.
2 Will it also upload the data to my Cumulus program,Cumulus with WiFiLogger can work like WL IP. You have to set Discon Period. Then Cumulus will release WFL every minute for discon period when WFL will be able to send own exports.
3 I assume I disable the internet settings on my Cumulus configuration page.No. Cumulus can have 40s access to the console from every minute and WFL can have 20 sec./min. Both can have enought time and data from console to make proper exports.
4 Do I need anything else, I assume my current Data logger will be superfluousCurrent USB data logger won't be needed.
Can I use my current Device ID and key for WeatherLink or do I need to register again with the WFL?
The current ID/key was obtained with the WeatherLink program and Davis USB data logger. It will not go online again after the mailman shows up this afternoon with my WFL.
Thanks
First a little background.. I have over a dozen WiFi devices that all access the router which does NOT broadcast its SSID, every device is assigned a static IP on the device itself as opposed to DHCP IP reservations by the router, and I use MAC filtering so that only devices whose MAC address I have entered are allowed to connect. Never a problem with all this.
I finally got the WFL to connect only after broadcasting the SSID, enabling DHCP on the router and disabling MAC address filtering. The router shows it as connected but I still cannot access the WFL GUI except via my cell phone using the WFL AP. Of course I have rebooted the router several times and nothing changes.
Any suggestions? Is there a way to reset the WFL back to out of box condition?
Thanks
"Set enable „AP Station”
Type your home Wi-Fi network SSID to „SSID”
Type your home Wi-Fi password to „Password”
Set disable „AP”I received my new logger today. Took a little fiddling, but I got it on the network. I'm seeing it at the correct IP and the live data is appearing.
I plan on utilizing Weather Display as the primary tool. So I'm only looking to use the logger abilities. No current plans to do any of the uploads to other services.
Anything I need to do out of the box? Reason I ask is I'm also switching from Cumulus to WD. WD isn't connecting. Any guidance would be appreciated.
I just installed WeatherLink 6.03. It was able to communicate with the logger.If you're not familiar, unless 6.0.3 was a full install or you have (for instance) 6.0.0 as a base, 6.0.3 may not work properly.
I did find a full download someone had here posted to the full 6.03.Okay, good, the someone was probably me. ;)
I think I finally got WD working. Had to check and uncheck the "Rev B", not "Rev B" settings. Not sure why that made it start working.
What is auto pause actually pausing? Would that pause prevent the Weather Display software from getting the live data for 7 minutes?
I think I understand.
Would the logger have anything to do with a drop out in my wind readings? I have a separate anemometer transmitter on channel 8. ISS on channel 1. My secondary console where the WiFi logger is installed lost communication to the wind data. Lost it for about 2 hours.
I went to my main console still running the serial connection. It was getting the data. That console is in my basement and is farther away from the transmitters. The secondary console is upstairs and fairly close.
I went into the secondary console and double checked the receiver settings that 8 was still wind. I then also went into the logger and made your recommended change to the pause. A couple of minutes later, it started receiving again.
I've never had that console drop connection before, so it's odd. Been working again for an hour now. I'll just be monitoring it for any other drops.
Thanks for the support.
How much data can the WiFiLogger hold ?
Well, I had another drop out in my wind data. It started at 2:18 am and went to 5:24.
Technically I have no way of knowing for sure if it is the console or logger causing it. I could have had drop outs before and never noticed it.
OK, I looked at the stats. On my ISS Channel 1, I was getting 98% on the reception rate. But on the Wind Channel 9, it was 71%.
So I've pulled the WiFi Logger out and will watch it for a day and see what shows up for reception.
I just checked my main console with the Davis Serial logger and it was showing 97/98 percent reception rates. And that is in my basement. You'd think worse reception. But you never know. That one is in my mechanical room and has all my network equipment and furnace ducting in the way.
I'll give it a day or so and see what the secondary WiFI console is showing without the logger.
OK, I looked at the stats. On my ISS Channel 1, I was getting 98% on the reception rate. But on the Wind Channel 9, it was 71%.
...
Well, after 24 hours, I checked the stats again without the logger installed. My reception rate on the ISS was still 98%. But the wind one was even worse! Only 58%. So I can report to everyone here, it's not the logger.
My guess is I've been having an issue with the location of the second console, and just didn't know until I had something actually logging it. Problem is I could move the console to get better reception. But then the console is in a place in the house where I won't be able to conveniently read it. I like to read the temp/wind on my way out the door.
So I'm just going to hang onto the logger for now. I'll just have to flip my current setup over still using the existing serial logger.
Is there any way of purchasing this from Australia yet? Dying to try it out. I'm using the Australian version of the Vue with belfryboy's logger currently.
Is there any way of purchasing this from Australia yet? Dying to try it out. I'm using the Australian version of the Vue with belfryboy's logger currently.
Please just contact us at sales@weatherstations.co.uk . Once we've got details and checked shipping price then we can send a Paypal invoice.
Is there a way to add a cert for secure connection via MQTT?
Is there a way to add a cert for secure connection via MQTT?
All connection are open without any security. WL.com, WU, PWS, FTP etc. all are open.
WeatherLink, Cumulus also use plain connection, so I didn't expect that security is expected for weather data.
ESP8266 which is heart of WiFiLogger has libraries to make secure connection. I think for MQTT as well.
I don't know if this solution won't "eat" RAM to much.
But I can also prepare special firmware which will have secured MQTT or other exports, but I will have to cut off some other functions.
At this moment I think no one is using MQTT feature of WFL :-(
Advice needed WifiLogger setup:
Just got my Christmas present. Have installed WifiLogger in console. Does this screen shot look complete to you? Do I need the NTP time?
Thanks so much
[ You are not allowed to view attachments ]
Advice needed WifiLogger setup:
Just got my Christmas present. Have installed WifiLogger in console. Does this screen shot look complete to you? Do I need the NTP time?
Thanks so much
[ You are not allowed to view attachments ]
Wojciech, would it be possible for you to make a few 'appearance/cosmetic' modifications to the 'Real Time Data' screen.
Advice needed WifiLogger setup:
Just got my Christmas present. Have installed WifiLogger in console. Does this screen shot look complete to you? Do I need the NTP time?
Thanks so much
[ You are not allowed to view attachments ]
You have time data missing here. This data comes as EVENT in javascript. Your web browser can have disabled events, or even not used it.
Please try it on different web browser. On my computer Internet Explorer don't use EVENTS, but Chrome and Firefox work fine.
Wojciech, would it be possible for you to make a few 'appearance/cosmetic' modifications to the 'Real Time Data' screen.
I have in mind to put some more info on first page: IP address, name of device, maybe some more.Wojciech, I have never thought of making the display of the WiFiLogger available to any one other than myself, the person who owns the console where the WiFiLogger has been installed. Thus, I do not understand why you would need to go through the trouble of creating/reading cookies when all the default parameters (ie: temperatures, wind speeds, barometric pressures, rainfall and ET) should all be set within the 'Weather Station Settings' screen - why would I make the display of the WiFiLogger available to any one else and risking challenging hackers when the same weather data is available on my website! :mad:
I can make different data format, but It will involve cookie mechanizm like in http://wifilogger.net/station/php/ when you click on unit it is change and saved in current web browser.
Hi Wojtek.
Tried to sign up and send data to WOW but it doesn't seem to work....
This is the debug.
Wojciech, would it be possible for you to make a few 'appearance/cosmetic' modifications to the 'Real Time Data' screen.
I do not have a webpage; future endeavor?
Please unpack and upload this HTML to your WiFiLogger...Wojciech, the modification works perfectly. Thank you. :-)
You have just helped to improve my product. Why do you feel bad with it?Please unpack and upload this HTML to your WiFiLogger...I feel somewhat sorry
Hi Wojtek.
Tried to sign up and send data to WOW but it doesn't seem to work....
This is the debug.
Thanks.Hi Wojtek.
Tried to sign up and send data to WOW but it doesn't seem to work....
This is the debug.
Lars I have checked WOW. It is working. WOW can't be uploaded to often, but that is not your case.
typical debug:
WOW 15
Renew RTD
Client response time: 950
{}
to often:
WOW 5
Client response time: 850
The custom error module does not recognize this error.
Please check once more
ID should looks like this: 2566e7c4-3e6b-e811-9ccb-1233f459g2da
PIN you can define on WOW website.
Thanks.
Put in the data in cumulus to see if something was wrong, and it works fine. But still not working from logger.
Don't know why the logger wont do it.
Cheers.
Davis vantage vue.Thanks.
Put in the data in cumulus to see if something was wrong, and it works fine. But still not working from logger.
Don't know why the logger wont do it.
Cheers.
Which station do you have? What set of sensors?
Does anyone know if it is possible to update vantage Vue firmware via WiFi Logger?
What is the latest sw?1.24 - no new options, just some problems resolved.
Does anyone know if it is possible to update vantage Vue firmware via WiFi Logger?
No problem with that, but you have to turn on AUTO PAUSE in SYSTEM menu and Davis upgrade software won't find automatically your WiFiLogger. You have to retype IP address of WFL by your own.
You have just helped to improve my product. Why do you feel bad with it?Please unpack and upload this HTML to your WiFiLogger...I feel somewhat sorry
You have just helped to improve my product. Why do you feel bad with it?Please unpack and upload this HTML to your WiFiLogger...I feel somewhat sorry
when changing to local time, the time zone is off... but 24hr time it is correct.
Will there eventually be an option to view previous days' recorded data?
You have just helped to improve my product. Why do you feel bad with it?Please unpack and upload this HTML to your WiFiLogger...I feel somewhat sorry
when changing to local time, the time zone is off... but 24hr time it is correct.
Yes. My fault. Javascript has quite problem with time display.
I have change this file now is:
var timeFormat = 0;
// 0 - 24h
// 1 - 12 AM/PM
Time format is in console memory. I will change it in future to do this job automatically from the console settings.
Will there eventually be an option to view previous days' recorded data?
I have concept how to do this, but I can't make it in one week :(
Will this work reliably with Cumulus MX?
Will this work reliably with Cumulus MX?
We need to wait for answer from PaulMy. He is testing WFL with MX.
I know that there were some problems, but were resolved and should work fine now.
could I (theoretically) use the WFL to upload to the paid WeatherLink service? Or does WL require a valid serial of one of their WLIP products?I have the free wl.com 2.0 and it is being updated by my WiFiLogger at 5 min interval and don't have and never had a WeatherlinkIP or previous wl.com account, and it works fine.
Sorry if my question doesn't belong to this thread, but could I (theoretically) use the WFL to upload to the paid WeatherLink service? Or does WL require a valid serial of one of their WLIP products?
First message in this thread has the downloads.Thanks.
Thanks for the responses. However, as I stated - I'd like to know if I can upload to the paid service with extended functionality.
Sorry if my question doesn't belong to this thread, but could I (theoretically) use the WFL to upload to the paid WeatherLink service? Or does WL require a valid serial of one of their WLIP products?
First message in this thread has the downloads.
It can use DID from broken oryginal WL IP, or you can generate DID on WL.COM site. Generated DIDs are for USB/RS232 data loggers, but works perfectly with WiFiLogger.
To view charts from archive data, you have to buy subscription. No matter what. If you have original WL IP, you need to pay for charts as well.
I don't have a weather station yet, but this device may push me over the edge to purchase one of the current gen Davis products. My eventual goal is to integrate the collected data with modern open source platforms like Prometheus.
I've got a few questions around the JSON data and it's various delivery methods:
- Is there any detailed developer focused documentation on the JSON produced by the WFL at this point?
- Are the JSON documents produced by the /wflexp.json endpoint, MQTT, FTP, and the HTTP PUT are all the same?
- Has any consideration been given to cleaning up the data model in JSON to make it more consistent (i.e. make date/time always represented using the same notation, make high/low data a dictionary/hash instead of a positional array, etc.)? If there is, and there's enough memory, I'd suggest switching to a versioned API for the HTTP endpoint (e.g. /v1/wflexp.json, then /v2/wflexp.json, etc.)
Lastly, is there a product page that summarizes the knowledge spread throughout this thread? On that page I'd imagine some FAQs, a full changelog, and maybe a product roadmap (maybe just a GitHub page even if the intent is to keep the source closed)
I see many of the elements I'm looking for as differentiators between a strong product and something neat the community has built, even if it is closed source.
Thanks!
Wojciech, would it be possible, one day, for the 'WiFiLogger' to produce a data text file that would be similar (compatible with) the data text file ('clientraw.txt') produce by the Weather Display software.
Currently, the 'WiFiLogger' is producing the data text file ('realtime.txt') which is (used to be) produce by the Cumulus software.
By getting involved in replying to some users' questions in the 'Weather-Watch.com (https://www.weather-watch.com/smf/index.php/)' forums, I have been promoting the 'WiFiLogger' to replace the somewhat outdated Davis Instruments Data Loggers - the Weather-Watch.com forums are the main support forums for the Weather Display software.
In my opinion this is good direction.
I have 2 questions:Yes, indeed. Both the upgrade/update instructions (PDF document) and the MQTT information can be found in the first message of this thread 'WiFiLogger - Connect your Davis console directly to the Internet via WiFi (https://www.wxforum.net/index.php?topic=34312.0)'
- Is it possible to upgrade the firmware? How?
- Is it possible to send data to a proprietary system via post HTTP or MQTT?
Hi Folks
Please can someone direct me on how to sync my Vantage vue date with of the online platforms.
I have set up an account with wow met office and weatheground but then I am stuck and have no clue what to do next to get my data loaded on to these websites. My Ip link is all set up and I can see my data on my phone whilst connected to my router. Any help will be appreciated! Thx
Hi, Thank you for coming back to me really appreciate it.
I did that in WU but it says my station is not active.
In WU it says password but on the website it says key?! not sure what to use.
I must be honest on Wow met office I don't even know where to start. I cannot find where to create my ID and password.
Any further help will very appreciated .thx mate
One you sign up where do you find the details that has to be entered in the Wifi logger set up up menu? Thx
I have now the site ID on Wow but no pin?!
I can see that and it's an empty tab so I must populate it with a pin of my choice ans save?
Is there anything else that I am missing as my location still doesn't show on the map?WiFiLoggerSetup is only to establish connection with your router. To disable it you have to reboot WFL (white button, or SYSTEM and REBOOT button) You have to disable SETUP mode to start sending data by WFL.
Also when I am connected to my IP address on my phone I always have ti switch my wifi to regain access to the internet is that normal? When I am logged in its called Wifiloggersetup?!
Any idea how to set up with weatherlink as I see they have a nice app that I would love to see my data linked to it.
By the way my WU still not working it says not responding :-(Even if all you have made right WU needs some time for new ID. Set interval to 5 min and please wait an hour.
And Mode enables and rapid fire enabled?
When configuring WU do you need to put a URL?
I feel like I am doing something wrong there!
Thx mate
Now I have it all working :-)
Bow can I make the upload speed faster so the wind speed on the app updates faster?
Thank you chap.
I just received my logger and installed it tonight and it works great! I'm very interested in using MQTT to publish data to Home Assistant however I noticed the temperatures are all sent in F instead of C. Is there any way to change the MQTT settings to send in C? I noticed that in the FTP settings it can be changed.
Thanks this is an awesome product and I'm happy to support it!
My other post on the Home Assistant forum, maybe we can get some more people from there!
https://community.home-assistant.io/t/wifi-logger-for-davis-weather-stations/88966/3
function Ubar(bar){
var b=0;
switch(UNITS[0]) {
case "mm": b = bar * 25.4 ;break;
case "hPa": b = bar * 33.8639;break;
case "mb": b = bar * 33.8637526; break;
default: return Math.round((bar)*1000) /1000;
}
return Math.round((b)*10) /10;
}
function Uwind(wind){
if(wind == "---") return "---";
var w=0;
switch(UNITS[4]) {
case "mph": w = wind;break;
case "m/s": w = wind * 0.447; break;
case "km/h": w = wind * 1.6093;break;
case "knots": w = wind * 0.869;break;
default:w = wind;
}
return Math.round((w)*10) /10;
}
function Urain(rain){
var r=0;
switch(UNITS[3]) {
case "mm": r = Math.round((rain*25.4)*10) /10; return r.toFixed(1);break;
default: r = Math.round((rain)*100) /100; return r.toFixed(2);
}
}
function Utemp(unit){
if(UNITS[1] == "F") return unit;
else{
return Math.round(((unit-32)/1.8)*10) / 10;
}
}
I just received my logger and installed it tonight and it works great! I'm very interested in using MQTT to publish data to Home Assistant however I noticed the temperatures are all sent in F instead of C. Is there any way to change the MQTT settings to send in C? I noticed that in the FTP settings it can be changed.
Thanks this is an awesome product and I'm happy to support it!
My other post on the Home Assistant forum, maybe we can get some more people from there!
https://community.home-assistant.io/t/wifi-logger-for-davis-weather-stations/88966/3
When I was preparing CSV(text) file for archive export, I wanted to make something similar to WeatherLink standard, but now I know that was bad idea.
When you have original TXT file from WeatherLink PC you don't know what units are in it. I have add units columns to my file.
JSON file is in native console units and has to be like this. It's universal. You have to recalculated units before showing on screen like WU, or PWS make it.
Please visit my website
http://wifilogger.net/station/php/wflexp.json
and template to show data from this JSON
http://wifilogger.net/station/php/
When you click on unit lik C or mph, units will change and settings will be stored by cookies in your web browser. So when you visit this site again it will have your (local)preferences.
It's quite convenient. In same time when you want to store data in data base from multiple people, then data will always be the same F, mph, inch, no mismatch possible.
My next move is to export archive data via JSON format. It will also be in native units from console.
Check how looks recalculating in JavaScript(maybe not very clean code):
Changing from F to C is only return Math.round(((unit-32)/1.8 )*10) / 10;Code: [Select]function Ubar(bar){
var b=0;
switch(UNITS[0]) {
case "mm": b = bar * 25.4 ;break;
case "hPa": b = bar * 33.8639;break;
case "mb": b = bar * 33.8637526; break;
default: return Math.round((bar)*1000) /1000;
}
return Math.round((b)*10) /10;
}
function Uwind(wind){
if(wind == "---") return "---";
var w=0;
switch(UNITS[4]) {
case "mph": w = wind;break;
case "m/s": w = wind * 0.447; break;
case "km/h": w = wind * 1.6093;break;
case "knots": w = wind * 0.869;break;
default:w = wind;
}
return Math.round((w)*10) /10;
}
function Urain(rain){
var r=0;
switch(UNITS[3]) {
case "mm": r = Math.round((rain*25.4)*10) /10; return r.toFixed(1);break;
default: r = Math.round((rain)*100) /100; return r.toFixed(2);
}
}
function Utemp(unit){
if(UNITS[1] == "F") return unit;
else{
return Math.round(((unit-32)/1.8)*10) / 10;
}
}
I am adding JSON structire in XLS
Thanks the Excel file will help out a lot! I couldn't sleep this morning so I got up at 4am to start integrating it into my Home Assistant. Also, my Homeassistant exports all its data into an Influx Database so I am able to see the data in Grafana. I am still working on a dashboard and I'll share it when it is ready.
Something else I noticed (And its a good thing :grin:) is that now WU reports wind speeds other than calm or 0 all the time.
Before, when WLIP uploaded to WU, it was wind speed at that very moment. So most uploads (<90%) showed calm wind.
The option in WiFiLogger 'Data Export Setup' for CWOP asks for type of wind speed to report. I don't know how or why this would effect WU but since I set it to '2-Min Avg Wind Speed', CWOP AND WU seem to report the 2 minute average. Maybe I'm interpreting this wrong, but either way, I'm not complaining.
Something else I noticed (And its a good thing :grin:) is that now WU reports wind speeds other than calm or 0 all the time.
Before, when WLIP uploaded to WU, it was wind speed at that very moment. So most uploads (<90%) showed calm wind.
The option in WiFiLogger 'Data Export Setup' for CWOP asks for type of wind speed to report. I don't know how or why this would effect WU but since I set it to '2-Min Avg Wind Speed', CWOP AND WU seem to report the 2 minute average. Maybe I'm interpreting this wrong, but either way, I'm not complaining.
Will there be a way to do this for PWS in future?
To move forward with WiFiLogger firmware and new features we need to do one hard thing.
I have chosen bad partition table on the beginning. Firmware can be only 512kB. Now it's bigger, so partition table has to be changed.
Problem is, this operation will clear whole memory and your settings will be wiped out.
I need to find volunteers. Computer super users, who will check my procedure and help to improve manual for other great WFLs users.
You have only this: https://wifilogger.net/files/WFL_Update_200.zip
On the other hand if you don't mind that your WFL after migration to version 2.00 will be restored to factory settings. Then procedure is very simple. Just update your WFL to 2.00 and wait for max 5 min.
Please write suggestion here, or send me via email wifilogger@qq.com
Thank you
Wojtek
I will volunteer, but I'm not exactly sure what you want me to do other than download and update to 2.00. What else do you need to know?
Update to 2.00 went smoothly. Nothing to really add. Instructions were easy to understand. Nothing much else I can think of to be honest.
Edit: Under Rain and ET, I notice there's an area that just has "---". Any idea what this is?
Edit again: Also, at the top of my Real Time Data page, I'm getting, "undefined". My clock / real time data is no longer updating either.
Update to 2.00 went smoothly. Nothing to really add. Instructions were easy to understand. Nothing much else I can think of to be honest.
Edit: Under Rain and ET, I notice there's an area that just has "---". Any idea what this is?
Edit again: Also, at the top of my Real Time Data page, I'm getting, "undefined". My clock / real time data is no longer updating either.
It takes up to 5 min. First HTML files are being downloaded, then after success version 2.08 will be downloaded and updated.
Please refresh web site of WFL and check firmware version SETUP|SYSTEM.
Is there a any way I can kick-start the download process again?http://YOUR_WFL_IP/update
Is there a any way I can kick-start the download process again?http://YOUR_WFL_IP/update
chose first option: Firmware update
Is there a any way I can kick-start the download process again?http://YOUR_WFL_IP/update
chose first option: Firmware update
And update to 2.00 again?
"Update failed to install. Restarting."
Is there a any way I can kick-start the download process again?http://YOUR_WFL_IP/update
chose first option: Firmware update
And update to 2.00 again?
"Update failed to install. Restarting."
Ver 2.00 is downloading new firmware, it's triggered to start downloading after reboot.
Your units can't download full update and it's rebooting.
please try to use this: https://wifilogger.net/files/WiFiLogger208.zip to make regular update to 2.08
All working fine after manual update. Thanks.
Updated to version 2.0 with no issues.
All working fine after manual update. Thanks.
No it's not fine, because your WFL has reboot 12 times and start to downloading HTML files again and again.
Probably internet problem, but maybe auto trigger to make update it is not good idea.
I will check this operation with several people and maybe change this procedure.
Thank you for your help.
Upgraded to 2.08, also with no problems.
Upgraded to 2.08, also with no problems.From 2.00 to 2.08 should be done by itself in about 5 minutes.
By the way, how does the forecast feature work? Would it be possible to make it so it can be disabled? It says precipitation possible yet we're in a severe drought and there's no sign of any rain for the next week at least.
By the way, how does the forecast feature work? Would it be possible to make it so it can be disabled? It says precipitation possible yet we're in a severe drought and there's no sign of any rain for the next week at least.
It's forecast from console. If you don't like I could distribute index.html (first page) with this thing off, or add option and instruction how to disable.
I was thinking that WFL should be 1:1 with console.
1. Download index.zipBy the way, how does the forecast feature work? Would it be possible to make it so it can be disabled? It says precipitation possible yet we're in a severe drought and there's no sign of any rain for the next week at least.
It's forecast from console. If you don't like I could distribute index.html (first page) with this thing off, or add option and instruction how to disable.
I was thinking that WFL should be 1:1 with console.
Yeah, I thought it was from the console. Either method you mention to remove it would do. :)
1. Download index.zipBy the way, how does the forecast feature work? Would it be possible to make it so it can be disabled? It says precipitation possible yet we're in a severe drought and there's no sign of any rain for the next week at least.
It's forecast from console. If you don't like I could distribute index.html (first page) with this thing off, or add option and instruction how to disable.
I was thinking that WFL should be 1:1 with console.
Yeah, I thought it was from the console. Either method you mention to remove it would do. :)
2. unpack
3. upload index.html to WFL as HTML file SETUP|SYSTEM bottom of the page
4. go to http://YOUR_WFL_IP/edit
5. chose index.html from list on the left
6. find :
var forecastdisplay = 1;
//0 - disable forecast
//1 - enable forecast
7. change var forecastdisplay = 1; to var forecastdisplay = 0;
8. click "save" button
9. reload your WFLs web page
mzac, sounds like you missed the second step to upgrading firmware. After you've gone up a version, you have to go into that ZIP file and find the HTML files as well. On the Wifi screen, there was a spot where you have to upload the updated HTML files as well. That will likely fix your link issue.
Hmm however it said to go to 1.24S you didn't need to upload the HTML files... This was just a .bin file upload which is what the instructions said:
Go to SETUP|SYSTEM menu of your WFL and perform firmware update with WiFiLogger124S.bin file, as you have likely done before with any other firmware change. HTML files won’t be needed in this step.mzac, sounds like you missed the second step to upgrading firmware. After you've gone up a version, you have to go into that ZIP file and find the HTML files as well. On the Wifi screen, there was a spot where you have to upload the updated HTML files as well. That will likely fix your link issue.
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=arch.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=edit.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=export.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=ftpexport.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=index.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=info.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=setup.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=style.css' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=system.html' davis/admin/html
root@pi3:/media/nas1-downloads/WFL_Update_200/WFL_Update_200/WiFiLogger124S/html# curl -F 'data=wifi.html' davis/admin/html
Hmm however it said to go to 1.24S you didn't need to upload the HTML files... This was just a .bin file upload which is what the instructions said:
Go to SETUP|SYSTEM menu of your WFL and perform firmware update with WiFiLogger124S.bin file, as you have likely done before with any other firmware change. HTML files won’t be needed in this step.mzac, sounds like you missed the second step to upgrading firmware. After you've gone up a version, you have to go into that ZIP file and find the HTML files as well. On the Wifi screen, there was a spot where you have to upload the updated HTML files as well. That will likely fix your link issue.
Ok I got the files re-uploaded using curlHmm however it said to go to 1.24S you didn't need to upload the HTML files... This was just a .bin file upload which is what the instructions said:
Go to SETUP|SYSTEM menu of your WFL and perform firmware update with WiFiLogger124S.bin file, as you have likely done before with any other firmware change. HTML files won’t be needed in this step.mzac, sounds like you missed the second step to upgrading firmware. After you've gone up a version, you have to go into that ZIP file and find the HTML files as well. On the Wifi screen, there was a spot where you have to upload the updated HTML files as well. That will likely fix your link issue.
Ok I got the files re-uploaded using curlHmm however it said to go to 1.24S you didn't need to upload the HTML files... This was just a .bin file upload which is what the instructions said:
Go to SETUP|SYSTEM menu of your WFL and perform firmware update with WiFiLogger124S.bin file, as you have likely done before with any other firmware change. HTML files won’t be needed in this step.mzac, sounds like you missed the second step to upgrading firmware. After you've gone up a version, you have to go into that ZIP file and find the HTML files as well. On the Wifi screen, there was a spot where you have to upload the updated HTML files as well. That will likely fix your link issue.
Hacker
can you open
http://YOUR_WFL_IP/config.json
http://YOUR_WFL_IP/stationconfig.json
??
:)No, version 1.24S was to download JSONs. Now you will need to configure your WFL manually :(
Yes now I was able to upgrade to v2.0, and now it has upgraded to 2.08. I was able to download the json files yes...
:)No, version 1.24S was to download JSONs. Now you will need to configure your WFL manually :(
Yes now I was able to upgrade to v2.0, and now it has upgraded to 2.08. I was able to download the json files yes...
It has factory settings now.
I don't know why your update to 1.24S wiped out all files. It could happened with first batch, but not now. Sorry.
I saw there is 'trbat' being sent in the json and mqtt, mine is currently '8' and in your spreadsheet it didn't say what the values meant?
I saw there is 'trbat' being sent in the json and mqtt, mine is currently '8' and in your spreadsheet it didn't say what the values meant?
To better understand WiFiLogger and console maybe you will need this: https://www.davisinstruments.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf
WiFiLogger is transmission device. All I need to do is to take data from console and send it in convinient way via wifi to the Internet.
This Davis manual will allow you to understand that only main temp has decimal, all other are in full F degree and other usefull informations.
trbatt = Transmitter Battery Status
I think it's 8 bits.
trbatt = 00000000b means no problem
trbatt = 00000001b LOW BATTERY ON STATION 1
trbatt = 00000010b LOW BATTERY ON STATION 2
trbatt = 10010001b LOW BATTERY ON STATION 1,5 and 8
I like that you can now see the low battery warning on the transmitter.:)
BTW you've done a really good job on this product! I'm very happy! :D
BTW you've done a really good job on this product! I'm very happy! :D
There is nothing like a happy client. :)
Hi, I had a bit of time today while the kids were watching tv so I got some more data points entered into Homeassistant. While I was doing that I came up with a few questions, notes:
- Does the wifi logger set the time of the console with SETTIME?
- Is there any way to clear monthly rain? I tried with clear highs but it didn't work as my console went nuts with a dead battery in the transmitter and shows 2000+mm of rain!
- Under the wifi setup, there is a tcp port setting of 22222, what is the purpose of this port? Telnetting to it doesn't give anything
- The json output seems to have the version sent twice, looks like a bug?
{"stnmod":17,"ver":2.12,"ver":2.12,"loctime":1547916190,"utctime":1547934190
- You mentioned about sending more info in the json, here are some ideas:
- station name
- mac address
- ip address
- SSID connected
- Wifi RSSI
- Wifi Mode (b/g/n)
- Last boot (utc time?)
- Uptime (in seconds?)
- wifi logger firmware
- type/model of console (I have vantage vue)
- lat/long of station
To move forward with WiFiLogger firmware and new features we need to do one hard thing.
I have chosen bad partition table on the beginning. Firmware can be only 512kB. Now it's bigger, so partition table has to be changed.
Problem is, this operation will clear whole memory and your settings will be wiped out.
I need to find volunteers. Computer super users, who will check my procedure and help to improve manual for other great WFLs users.
You have only this: https://wifilogger.net/files/WFL_Update_200.zip
On the other hand if you don't mind that your WFL after migration to version 2.00 will be restored to factory settings. Then procedure is very simple. Just update your WFL to 2.00 and wait for max 5 min.
Please write suggestion here, or send me via email wifilogger@qq.com
Thank you
Wojtek
A question; when I upload my data from WifiLogger to the likes of Wunderground and PWSweather, I notice that rainfall is calculated in 0.1mm increments (both sites report 0.5mm to have fallen). Thing is, I did change the setting to enable 0.2mm increments in WifiLogger which works and reports the correct 0.4mm on the main Wifilogger page. My question is why am I getting the correct output on WifiLogger page but incorrect 0.1mm increments to PWS / Wunderground? Thank you in advance.Don't use 0.1mm this exist probably only in Davis manual. I should erase this from WFL.
I’m very new to the Forum and new to weather stations. I have a Davis VantageVue. How does the WIFI Logger compare to the NANO SD? on the surface they appear to be similar except for the price!
Thanks.
A question; when I upload my data from WifiLogger to the likes of Wunderground and PWSweather, I notice that rainfall is calculated in 0.1mm increments (both sites report 0.5mm to have fallen). Thing is, I did change the setting to enable 0.2mm increments in WifiLogger which works and reports the correct 0.4mm on the main Wifilogger page. My question is why am I getting the correct output on WifiLogger page but incorrect 0.1mm increments to PWS / Wunderground? Thank you in advance.Don't use 0.1mm this exist probably only in Davis manual. I should erase this from WFL.
I can see this problem.
- Davis not measure rain, but counts clicks from rain gauge.
- If you have regular Davis then 1 click = 0.01 inch = 0.254mm
- If you have 2mm weight adapter, then 1 click = 0.2mm = 0.007874015748 inch
WU takes rain in inches.
I have made 3 clicks = 0.6mm = 0.023622047244inch. WFL and console shows 0.02inch. This value goes to WU 0.02inch * 25.4 = 0.508, but WU shows 0.51mm
I will examine this. Maybe WU will take better precision than 0.01 inch. This will solve problem. US customers should not have such problem. Measure in inches, send in inches.
I've just gone to download WiFiLogger124.zip using the link in the first post but received a 404 - Not found error.
That's interesting. I have a 0.2mm metric adapter in my VP2 and have console also set to 0.2mm. What about PWSweather? It is showing the same 0.5mm as well. Do I wait for a fix from your end?
Hi, Wojtek.
The firmware update got rid of the firmware version of the console, which I liked because I would periodically check to make sure Davis hadn't released a new update to my Vue console (ver. 4.30 currently). Would it be easy to bring that small feature back? Also, is there a way to pull the battery level/voltage from the ISS, considering the console gives a low battery warning when the ISS is low? Thanks, in advance. The constant improvements are intriguing.
Hi, Wojtek.
The firmware update got rid of the firmware version of the console, which I liked because I would periodically check to make sure Davis hadn't released a new update to my Vue console (ver. 4.30 currently). Would it be easy to bring that small feature back? Also, is there a way to pull the battery level/voltage from the ISS, considering the console gives a low battery warning when the ISS is low? Thanks, in advance. The constant improvements are intriguing.
Hi John
Version is hided. Please let me know if that is ok for you. I had to put some more info. I wanted this page still in same size, so I hided version.
ISS and other satelites gives only info 0,1 (YES/NO) about batttery. Only console has battery measure function.
If it can be retrieved with a click, that would be just fine.
My upgrade didn't go so well. I followed all the steps but am left with some undefined values. I've restarted several times including using the white reset button. It seems to be working other wise.
[ You are not allowed to view attachments ]
I’m very new to the Forum and new to weather stations. I have a Davis VantageVue. How does the WIFI Logger compare to the NANO SD? on the surface they appear to be similar except for the price!
Thanks.
There are three standalone devices:
1. WeatherLink IP
2. WiFiLogger
3. MB Nano and MB Nano SD
1. WeatherLink IP
- Sending data through ethernet.
- Sending data to WeatherLink.com ONLY
- Working with WeatherLInk PC/Cumulus etc.
2. WiFiLogger
- is enchanced WeatherLink IP
- Using WiFi only
- Sending data to WeatherLink.com
- Working with WeatherLInk PC/Cumulus etc.
- Allow to send data to services like WU, PWS, WOW etc.
- Allow to export data to custom server FTP/HTTP/MQTT
3. MB Nano and MB Nano SD
I have never used this, but it has plenty of functions.
SD version allows to store archive data on SD card + SD can contain HTML website.
For sure it allows to send data to custom servers.
Nano is based on minimized Linux router/board
What has WiFiLogger which Nano don't have?
WiFiLogger is compatible with WeatherLink.com.
WFL has similar power consumption like original WeatherLinkIP. Nano needs 3x power.
If you know what to do with all Nano's functions and you need them, then probably that would be good choice for you.
If you are looking for 500% enhanced WeatherLinkIP(which is very good device) with WiFi to send data to WU, PWS etc. Then WiFilogger is absolutely good choice.
WiFiLogger was designed to be simple to use and setup. I hope that was done properly, but for this topic, users needs to say about.
A question; when I upload my data from WifiLogger to the likes of Wunderground and PWSweather, I notice that rainfall is calculated in 0.1mm increments (both sites report 0.5mm to have fallen). Thing is, I did change the setting to enable 0.2mm increments in WifiLogger which works and reports the correct 0.4mm on the main Wifilogger page. My question is why am I getting the correct output on WifiLogger page but incorrect 0.1mm increments to PWS / Wunderground? Thank you in advance.Don't use 0.1mm this exist probably only in Davis manual. I should erase this from WFL.
I can see this problem.
- Davis not measure rain, but counts clicks from rain gauge.
- If you have regular Davis then 1 click = 0.01 inch = 0.254mm
- If you have 2mm weight adapter, then 1 click = 0.2mm = 0.007874015748 inch
WU takes rain in inches.
I have made 3 clicks = 0.6mm = 0.023622047244inch. WFL and console shows 0.02inch. This value goes to WU 0.02inch * 25.4 = 0.508, but WU shows 0.51mm
I will examine this. Maybe WU will take better precision than 0.01 inch. This will solve problem. US customers should not have such problem. Measure in inches, send in inches.
That's interesting. I have a 0.2mm metric adapter in my VP2 and have console also set to 0.2mm. What about PWSweather? It is showing the same 0.5mm as well. Do I wait for a fix from your end?
Is there an official standard? NOAA? NWS?
Is there an official standard? NOAA? NWS?
I am preparing option to choose wind data which will be exported.
Console has wind data as:
- current wind
- current wind direction
- 2 min average
- 10 min average
I will make option for user to choose which one should be exported to WU, PWS, etc. as wind data.
Question is:
Option should be next to every export settings. Separate for WU, separate for PWS etc. (RapidFire is always current)
Or option can be one for all exports. When you pick 2 min avg, then all weather services will get 2 min avg.
How this should be realized?
I seem to be getting erroneous data readings which have occured at exactly 6:00am the last two mornings and 6:00pm three mornings ago. This never happened before three days ago. They do not show up in Today's Highs / Lows on Real-Time Data page, only on PWSweather. Does this sound WifiLoggger related? What could be the cause?
Just want to chime in here. I believe I was the first paying customer for Wifilogger in the US (tough times when this is what you think of yourself!!!). I'm still on firmware 1.20. This device and my VP2 have been running flawlessly for months. Never one disconnection or issue. I keep it simple and only upload to WU, PWS, and CWOP.:grin: :oops:
Thank you to Wojtek for making such a great product and for the continued support.
I seem to be getting erroneous data readings which have occured at exactly 6:00am the last two mornings and 6:00pm three mornings ago. This never happened before three days ago. They do not show up in Today's Highs / Lows on Real-Time Data page, only on PWSweather. Does this sound WifiLoggger related? What could be the cause?
Hey Guys! i just updated my WIFI logger following the instructions to update BIN 124s and then uploading 2.00 firmware, after waiting 30 min the logger never returned so i went to setup mode and tried to setup the wifi and it said file not found ? did i just wipe my logger clean? I fear it's dead! any help!?
Question: Does the WiFi Logger send Altimeter Pressure to CWOP?
I suspect but I'm not sure that the WiFi Logger is sending Sea Level Pressure to CWOP instead of sending Altimeter Pressure. CWOP requests that stations send Altimeter Pressure. Altimeter Pressure is something that other weather software is able to send to CWOP by using LOOP2 where the Davis console provides Absolute Pressure (Station Pressure) to then be used to compute Altimeter Pressure by the weather software (the WiFi Logger in this case). Not sending Altimeter to CWOP is a pretty big deal and it throws off quality reporting analysis of not just your station but of your neighbors which won't be happy with you if you continue to send Sea Level Pressure.
This came to my attention in this thread:
https://www.wxforum.net/index.php?topic=35756.msg370181#msg370181
Exactly. If I may add further for those who'd like to try this option, set your VP2 console when the weather is benign and the altimeter is "around" 29.92", which is standard barometric pressure.Question: Does the WiFi Logger send Altimeter Pressure to CWOP?
I suspect but I'm not sure that the WiFi Logger is sending Sea Level Pressure to CWOP instead of sending Altimeter Pressure. CWOP requests that stations send Altimeter Pressure. Altimeter Pressure is something that other weather software is able to send to CWOP by using LOOP2 where the Davis console provides Absolute Pressure (Station Pressure) to then be used to compute Altimeter Pressure by the weather software (the WiFi Logger in this case). Not sending Altimeter to CWOP is a pretty big deal and it throws off quality reporting analysis of not just your station but of your neighbors which won't be happy with you if you continue to send Sea Level Pressure.
This came to my attention in this thread:
https://www.wxforum.net/index.php?topic=35756.msg370181#msg370181
most of us have set our elevation on the console to zero then calibrated our Davis consoles to match a nearby airport that reports altimeter.
I have just checked.Too ambiguous. I assume you mean whatever the console is displaying, right?
WiFiLogger to all services is sending barometer from console.
I have just checked.
WiFiLogger to all services is sending barometer from console.
I have just checked.
WiFiLogger to all services is sending barometer from console.
Thank you. That confirms my suspicion.
Fix Request:
So now can we request the the WiFi Logger use LOOP2 to pull Absolute Pressure and then calculate Altimeter and then report Altimeter to CWOP like other weather software?
It is sending same value which is displayed on console screen.I have just checked.Too ambiguous. I assume you mean whatever the console is displaying, right?
WiFiLogger to all services is sending barometer from console.
I have just checked.
WiFiLogger to all services is sending barometer from console.
Thank you. That confirms my suspicion.
Fix Request:
So now can we request the the WiFi Logger use LOOP2 to pull Absolute Pressure and then calculate Altimeter and then report Altimeter to CWOP like other weather software?
Yes. No problem I will fix this ASAP.
Do you have direct link to CWOP instruction? I have just been looking for it, but with no luck.
Altimeter Formula, A:
A = (P^N + K*Z)^(1/N), where P is the raw station pressure (in. Hg), N = 0.1903, K = 1.313E -5,
Z is elevation (feet).
REFERENCE
"Smithsonian Meteorological Tables". Smithsonian Institution Press, Washington, DC, 4th Ed.
1968.
So, if I understand you correctly, you can program your logger to do what the Vue console already does? If so, you'd probably make a lot of happy VP2 user that want an accurate altimeter setting that don't want a Vue.I have just checked.
WiFiLogger to all services is sending barometer from console.
Thank you. That confirms my suspicion.
Fix Request:
So now can we request the the WiFi Logger use LOOP2 to pull Absolute Pressure and then calculate Altimeter and then report Altimeter to CWOP like other weather software?
Yes. No problem I will fix this ASAP.
So, if I understand you correctly, you can program your logger to do what the Vue console already does? If so, you'd probably make a lot of happy VP2 user that want an accurate altimeter setting that don't want a Vue.I will make function to calculate altimeter pressure and send this data to CWOP.
All very interesting but the airplanes of the world and our local TV stations report altimeter why do you want to see barometric pressure differently?
=D> Now, can you make our ISS's take i2c protocol......? :grin:So, if I understand you correctly, you can program your logger to do what the Vue console already does? If so, you'd probably make a lot of happy VP2 user that want an accurate altimeter setting that don't want a Vue.I will make function to calculate altimeter pressure and send this data to CWOP.
This CWOP pressure is my mistake. I didn't know that CWOP needs altimeter. It should be done on the beggining.=D> Now, can you make our ISS's take i2c protocol......? :grin:So, if I understand you correctly, you can program your logger to do what the Vue console already does? If so, you'd probably make a lot of happy VP2 user that want an accurate altimeter setting that don't want a Vue.I will make function to calculate altimeter pressure and send this data to CWOP.
Maybe someone can also explain what “pressure” means as listed on MesoWest vs. altimeter vs. sea level pressure.Pressure is "station pressure", which has no correction factor. If you take your "pressure" and add your altitude MSL, you'll get in the ballpark of your SLP or altimeter, not sure which it more eludes to, probably SLP. For instance, if your station pressure is 29.00" and your altitude is 700' MSL, add .70" (that equates to 700' of elevation) your SLP should be around 29.70".
But at the end of the day, if NOAA that oversees CWOP believes altimeter is the right way to view weather pressure, how does a lay person argue otherwise unless you believe NOAA is not objective or has a particular bias in mind.
Note: Altimeter is the CWOP pressure standard because it is the simplest pressure reduction format that most CWOP members can reliably deliver and which can be useful by the National Meteorological Services.
But at the end of the day, if NOAA that oversees CWOP believes altimeter is the right way to view weather pressure, how does a lay person argue otherwise unless you believe NOAA is not objective or has a particular bias in mind.
I don't believe NOAA started off overseeing CWOP at its inception. Regardless the CWOP system is old. It was designed before the fancy weather consoles and software that we use today I believe. Even if back then the technology existed to properly calculate Sea Level Pressure, the idea was that they wanted CWOP to be something that was easily available for the weather station enthusiasts to use and for many with a lot of equipment back then it was not possible to easily calculate and submit Sea Level Pressure, or perhaps it required prohibitively more expensive hardware. So the decision was made early on to use Altimeter because it is simpler to deal with (meaning easier to calculate) and we are now stuck with it. So it came about as a necessity and limitation of the times. Want proof? No problem read the CWOP Guide:
https://weather.gladstonefamily.net/CWOP_Guide.pdfQuoteNote: Altimeter is the CWOP pressure standard because it is the simplest pressure reduction format that most CWOP members can reliably deliver and which can be useful by the National Meteorological Services.
So using Altimeter wasn't the best choice for meteorology back then and they knew it. But it was the best option to create a weather network that would allow everyone to submit data easily and adhear to a standard. Because apparently back then delivering Sea Level Pressure was out of the capability of most.
Makes perfect sense. Doesn’t Weather Underground also want altimeter?
Makes perfect sense. Doesn’t Weather Underground also want altimeter?
Nope. Weather Underground wants Sea Level Pressure. You can see it defined in their API documentation.
https://goo.gl/ZUoqvC
Makes perfect sense. Doesn’t Weather Underground also want altimeter?
Nope. Weather Underground wants Sea Level Pressure. You can see it defined in their API documentation.
https://goo.gl/ZUoqvC
What we have here is apples, oranges and pears. The feeds received by CWOP, WU, PWS, etc. are or could be all different. Fortunately, pressure may be the least important measure to many but it shows the problems when pressure is defined in more than 1 way.
Barometer: 30.011
Barometric Reduction Method: 2 - NOAA Bar Reduction. For VP2, this will always be 2.
User-entered Barometric Offset: 0
Barometric calibration number: 23
Barometric Sensor Raw Reading: 29.643
Absolute Barometric Pressure: 29.643
Altimeter Setting: 29.999
Elevation in feet: 330
Calculated Altimeter: 29.999
Barometer: 29.682
Barometric Reduction Method: 0 - user offset
User-entered Barometric Offset: 0
Barometric calibration number: 65534
Barometric Sensor Raw Reading: 29.682
Absolute Barometric Pressure: 29.682
Altimeter Setting: 30.036
Elevation in feet: 328
Calculated Altimeter: 30.036
Barometer: 30.038
Barometric Reduction Method: 1 - Altimeter Setting
User-entered Barometric Offset: 0
Barometric calibration number: 65534
Barometric Sensor Raw Reading: 29.684
Absolute Barometric Pressure: 29.684
Altimeter Setting: 30.038
Elevation in feet: 328
Calculated Altimeter: 30.038
Barometer: 30.050
Barometric Reduction Method: 2 - NOAA Bar Reduction. For VP2, this will always be 2.
User-entered Barometric Offset: 0
Barometric calibration number: 65534
Barometric Sensor Raw Reading: 29.684
Absolute Barometric Pressure: 29.684
Altimeter Setting: 30.038
Elevation in feet: 328
Calculated Altimeter: 30.038
// see http://www.wxqa.com/archive/obsman.pdf
//A = (P^N + K*Z)^(1/N),
/*
double P = rcd.BarometricSensorRawReading/1000.0;
int16_t Z = davisSetup.elevation;
double N = 0.190263;
double K = 1.312603E-5;
double A = pow( (pow(P,N) + (K*Z) ),1/N);
So I will just switch in CWOP export function from Barometer to Altimeter Setting.
From WiFiLogger's firmware 2.12. CWOP will have console Altimeter Setting value.