Topic: WiFiLogger - Connect your Davis console directly to the Internet via WiFi

[JamesDee64]

According to the person I talked to at WeatherCloud, I have to go through Weatherlink in order to send data to them.. This is not the case ?   My logger hasnt arrived yet, so I was just doing some preliminary checks before it got here.

[WheatonRon]

According to the person I talked to at WeatherCloud, I have to go through Weatherlink in order to send data to them.. This is not the case ?   My logger hasnt arrived yet, so I was just doing some preliminary checks before it got here.

You can send your pws data directly to WeatherCloud, WU, CWOP and others using this great WiFiLogger! You do not need to send it to Weatherlink although you can send your data to Weatherlink from the WiFiLogger. No computer necessary.

[JamesDee64]

Thanks very much.. I do like their website layout, and I will be connecting with them , when my logger hopefully arrives in a few weeks.

[PaulMy]

Things may have changed at WOW since I signed up several years ago and at that time I entered my own password and WOW provided an 8 digit numeric ID - i.e. 12345678
I have that 8 digit numeric code in WiFiLogger WOW settings as the Site ID and my password as Site PIN.
I also have a WOW API key for another purpose but not used in my WiFi upload settings and that is a very long allha/numeric string starting as 630eb...........

Enjoy,
Paul

[G0CNG]

Thanks for the reply Paul, but I think things are rather different now.  From what i can gather you don't use your password any more but instead the long station ID as in my previous post and the 6 digit authentication PIN which you set up yourself in your station details.
Chris
UPDATE.  All working well now😆.  Tried uploading every 15 mins rather than every 6 mins and data appeared on my WOW page.  And has updated reliably every 15 mins since. 

[xmas111]

Been running WiFiLogger since Saturday and everything appears to working fine except uploads to PWS.  It won't sent data to PWS.   I know my Station ID and password are correct.

So I decided to run the "Debug" and below is what Debug shows when trying to send data to PWS:


PWS 1
Renew RTD
Client response time: 52




Bad Request

Your browser sent a request that this server could not understand.



Apache/2.2.34 (Amazon) Server at pwsweather.com Port 80


new TCP Client: 192.168.1.102
new TCP Client: 192.168.1.102
new TCP Client: 192.168.1.102
new TCP Client: 192.168.1.102
new TCP Client: 192.168.1.102



I have no idea what it's means or how to fix the problem.

If anyone has any ides what it means or the fix I'd appreciate hearing them.

Thanks,
 John

[BigAlT]

Have you updated the firmware to the latest version of 2.14 ?.

[xmas111]

Have you updated the firmware to the latest version of 2.14 ?.

Yes it's using 2.14.

Thanks,
  John

[BigAlT]

Have you tried deactivating the PWS data upload in data export setup. Then rebooting your WFL and then reactivating PWS data upload ?.

[xmas111]

Have you tried deactivating the PWS data upload in data export setup. Then rebooting your WFL and then reactivating PWS data upload ?.

Yup, tried that too.

Thanks,
 John

[BigAlT]

There may be a variable that you will need to edit in the html files. Hopefully WIFILogger will respond to your problem with the solution. My WFL uploads to PWS properly with my Station ID and Password with the default reporting interval of 5 minutes.

[WiFiLogger]

Have you updated the firmware to the latest version of 2.14 ?.

Yes it's using 2.14.

Always when I have other job, here we have situation like this

We will solved this problem asap.
I will send you firmware which will print you more info about PWS export.
- PWS IP number
- HTTP GET message

We will check what is going on.

[xmas111]

Have you updated the firmware to the latest version of 2.14 ?.

Yes it's using 2.14.

Always when I have other job, here we have situation like this

We will solved this problem asap.
I will send you firmware which will print you more info about PWS export.
- PWS IP number
- HTTP GET message

We will check what is going on.

  Looks like I found the problem.    My password had a special character in it and PWS won't accept data to be uploaded if the password has special characters in it.
  As soon as I changed my password (with no special characters) it appears to finally work!

   Thank you for an awesome product!

    Here's my PWS station.   https://www.pwsweather.com/obs/KPLY111.html

   Thanks everyone for the help!
     John

[WiFiLogger]

Have you updated the firmware to the latest version of 2.14 ?.

Yes it's using 2.14.

Always when I have other job, here we have situation like this

We will solved this problem asap.
I will send you firmware which will print you more info about PWS export.
- PWS IP number
- HTTP GET message

We will check what is going on.

  Looks like I found the problem.    My password had a special character in it and PWS won't accept data to be uploaded if the password has special characters in it.
  As soon as I changed my password (with no special characters) it appears to finally work!

   Thank you for an awesome product!

    Here's my PWS station.   https://www.pwsweather.com/obs/KPLY111.html

   Thanks everyone for the help!
     John

Yes, before saving all data is coming through URL DECODE function. This comes with library. I will change it, because is not needed here.

[WiFiLogger]

Hi, I noticed that firmware 2.14 is available. Is there a place to go to other than reading through this thread to find out when updates are available and what has changed?

Not that I have seen other than at the beginning of this thread which is still showing 2.00 download.
A running changelog would be nice.

Firmware 1.xx has old file structure. I had to change it.
Firmware 2.00 is ok to be uploaded on 1.xx version.
Firmware 2.14 is not ok to be uploaded on 1.xx version.

How it works now?
I have release 2.00 firmware on my website.
Version 2.00 is downloading automatically version 2.14.
I don't release 2.14 to manual update because somebody could want to update it on version 1.xx. What could cause a problem.

Version 2.14 gives you nothing but, TCP port server was rebuild for @chriaquilina case. Now it works some different. Should be better for PC software.
I will let you know here on forum, when I will bring you some really good update, not just simple small repair.

[twcmaster]

Hi, I noticed that firmware 2.14 is available. Is there a place to go to other than reading through this thread to find out when updates are available and what has changed?

Not that I have seen other than at the beginning of this thread which is still showing 2.00 download.
A running changelog would be nice.

Firmware 1.xx has old file structure. I had to change it.
Firmware 2.00 is ok to be uploaded on 1.xx version.
Firmware 2.14 is not ok to be uploaded on 1.xx version.

How it works now?
I have release 2.00 firmware on my website.
Version 2.00 is downloading automatically version 2.14.
I don't release 2.14 to manual update because somebody could want to update it on version 1.xx. What could cause a problem.

Version 2.14 gives you nothing but, TCP port server was rebuild for @chriaquilina case. Now it works some different. Should be better for PC software.
I will let you know here on forum, when I will bring you some really good update, not just simple small repair.

Got it, thanks!

[xmas111]

I've run into another issue and not sure how (if possible) to solve it.

I still use VWS to automatically open WeatherLink (software) once a day to download all the data from the logger and create the NOAAMO.TXT and NOAAYR.TXT files.  But since using the WiFiLogger WeatherLink can't download the data from the WiFiLogger unless I go into WeatherLink and do it manually.

You can see WeatherLink recognizes the logger.

I have WiFiLogger set to Auto Pause.

Here's the log from Weatherlink when it tries to download automatically.

Any suggestions how to resolve this would greatly appreciated.

Thanks,
John

[WiFiLogger]

Any suggestions how to resolve this would greatly appreciated.

Do you have firmware 2.14 which was rebuilt to solve this problem?
http://YOUR_WFL_IP/update

I will provide new update system soon. Much more convenient.

[xmas111]

Any suggestions how to resolve this would greatly appreciated.

Do you have firmware 2.14 which was rebuilt to solve this problem?
http://YOUR_WFL_IP/update

I will provide new update system soon. Much more convenient.

 Yes, I'm running firmware 2.14.

 I will wait for your new update. I'm sure that will resolve the problem.

 Thank you again for a great device!

  John

[Herbaldew]

This was a post about my time not updating after daylight savings time went into effect this morning and some seemingly odd behaviors of the WFL....

Turns out that I had "Daylight Savings" set to "Manual" on the console...changed it to "Auto" and all is good.

[92merc]

After reading your post, I noticed the same thing.  I gave my logger a reboot.  A couple of minutes later it updated the time.

[ocala]

Mine was set to auto but it did not update. Had to go the manual route.
All is good now.
Only glitch since I've had it. No complaints here.

[BigAlT]

Mine is set to Auto and updated to Daylight Savings without any problems.

[rockncola]

Where is the link for 2.13/14? I'm still on 2.09 and the one on the first page is an old version. Is it worth updating from 2.09?

Also, is there any way to make PWSWeather record rainfall in .2mm increments yet? WifiLogger does this, but once uploaded, PWS converts it back to .1mm increments which is extremely frustrating.

[WiFiLogger]

After reading your post, I noticed the same thing.  I gave my logger a reboot.  A couple of minutes later it updated the time.

Daylight saving comes from console. WiFiLogger is reading console settings on startup and when user will open SETUP|Weather Station Setup.
That why you had to reboot WFL to change time. I don't have repair for that. Simplest solution would be reading console settings at 4:00 every day.