The WiFi logger is a third-party (ie non-Davis) product and known simply as the ‘WiFi logger’ or WFL for short. This topic provides some notes to help configure and troubleshoot the logger and its software; if you’re interested in a more detailed overview of the logger and all its features then this can be found on our main website . UK users can buy the WFL direct from our secure online shop, while non-UK residents (except N America) are welcome to email us and we can organise payment via Paypal.
In brief, the WiFi logger completely replaces the standard Davis logger; it is compatible with all consoles running console firmware v1.9 or later and is much like a WeatherlinkIP logger except that it communicates only via WiFi and does not automatically confer the right to upload to weatherlink.com (though uploads to wl.com may well be possible). The WFL has 5 main features:
- WiFi connection to a local computer running weather station software, providing both real-time and archive data;
- Uploads to Internet weather networks such as Weather Underground, WOW, CWOP etc;
- Local viewing of current weather data direct from the WFL;
- Full device management via a web interface;
- Additional features, eg NTP time synchronisation;
There is relatively little to go wrong with the WFL other than potential damage caused by large AC mains spikes (eg when the mains power goes out or is restored), lightning strikes etc, which is obviously no different to any other Davis logger. These notes are therefore concerned more with questions and points that may crop up when configuring and using the WFL rather than faults per se. Overall, questions may arise about four aspects of using the WFL:
- Initial set-up;
- Scenarios where the WFL is not feeding any data to other software and weather networks;
- Potential issues with individual features/service/weather networks;
- Firmware updates;
Setting up the logger
The set-up process is fully described in the WiFi logger manual and doesn’t really need detailed comment here beyond a short note below outlining the principle of the WiFi set-up. With a newly-installed logger it’s often a good idea to check whether a new firmware update might be available – please see the firmware update topic for further details.
Understanding the WiFi setup
Please remember that the WFL is a WiFi-only device; therefore all setting-up must be done via a WiFi link.
Like many WiFi devices, the WFL cannot initially connect to your WiFi network automatically simply because it cannot know the password for your network in advance. There is an easy way around this initial gotcha: the WFL is able to act as its own WiFi hotspot to allow initial configuration once it is installed in a Davis console and powered up. Set-up is therefore a two-stage process:
- Use a smartphone, tablet or laptop to establish a connection to the WFL’s built-in WiFi hotspot. You should be able to see a screen that enables you enter further settings;
- Select your own WiFi network from the list provided and enter the password for your network.and reboot the WFL. It should then connect to your own WiFi network to allow further configuration.
Resetting the WiFi network
Occasionally it might be necessary to move a console with WFL fitted to a WiFi network with different credentials, for example if the router is changed and needs to use a different password etc. Obviously the WFL will stop uploading data at this point because it will no longer be able to sign in to a working WiFi network.
The answer here is that you need to repeat the initial set-up step as described in the ‘Initial Wi-Fi Setup:’ sections of our WFL manual. But to repeat briefly here:
- First step: Reactivate the WFL’s own hotspot by holding down the WFL red button for a few seconds. You can tell whether the hotspot is active by looking for the ‘DataLoggerSetup’ network to be showing on the network list of your phone/tablet/laptop;
- Connect to this network (remember that no password is needed for connecting to the built-in hotspot) before pointing your browser at IP address 192.168.4.1. The WFL’s setup pages cannot be seen unless you are connected to the WFL’s own network for setup purposes. You may occasionally need to experiment with longer or shorter presses on the red button.
- You should then be able to navigate to the WiFi setup page and enter the credentials for the new WiFi network before finally rebooting/restarting the WFL.
In addition to the information provided here, there are two main sources of support for the WiFi logger:
WXForum WFL forum: See https://www.wxforum.net/index.php?board=143.0 on the popular WX online forum. Support requests can also be posted to this thread (you will probably need to register as a forum member in order to be able to post) and the creator of WFL will usually respond within a day or two.
Direct email: The WFL designer can also be contacted directly by email . But it’s usually best to try the forum first and to leave direct email as a backup option.
WFL troubleshooting is divided into two parts: scenarios where no data at all seems to be available from the logger are described below. Then configuration and troubleshooting for individual program feeds and weather networks will be covered on a separate page.
No data is being supplied by the logger
If the WiFi logger has been working OK but the data flow unexpectedly stops (which should be a pretty rare occurrence) then the first place to look will be the WiFi connection. Overall, WiFi connections tend to work quite reliably and in this sense the WFL may well be more robust than systems using a USB connection, especially if the installation is at all prone to the USB port dropout issue. But in the event of a potential issue there are two WiFi-related points worth checking:
First, a general check can be made as to whether the local WiFi network is running OK or not – obviously try and see if other devices such as smartphones, tablets or laptops can reach the Internet or not. If not, then rebooting the WiFi router will often fix the problem, but remember to wait at least eg 5 minutes before checking WFL operation – it may take a few minutes for the network to re-establish and for the WFL to connect fully to it again.
Second, is it possible that the WiFi signal is too weak for reliable operation at the console location?
Third, note that the WiFi logger (in common with most comparable Espressif-based products) can only use 2.4GHz WiFi and not 5MHz.
If the WiFi connection seems OK then there may be a console-related issue. The WFL behaves in general much like any other Vue/VP2 logger and similar troubleshooting applies. So if the unit does not seem to be functioning correctly there are 4 points always worth checking as a first step:
- Simply reboot the console (remove all power, wait a few moments and then apply power again). Do remember to press the Done button on consoles to return to Current Weather mode. This will often cure transient faults caused by mains spikes etc. NB Stored data should not be lost during this reboot.
- When the console reboots listen for the correct number of beeps (all with logger installed – there will be one fewer in each case without the logger). The beeps are not evenly spaced so count carefully. If the correct number of beeps is not heard then there is a fault of some sort and the unit will not function properly until the basic issue is fixed:
- Vue console – 4 beeps
- VP2 console – 3 beeps
- Envoy console – 2 beeps
- Is the logger firmly in place in its socket. A loose logger cannot work properly and the logger needs to be fully home in its socket.
- Remember that the WFL needs more power than a USB or serial logger (though around the same as an IP logger) and, as a result, it can run for only a few short hours on battery power. It’s therefore strongly recommended to run a WFL system on mains power only, and perhaps also with a small PC UPS to provide back-up power in the event of a mains outage.
- Thee have been a few reports that the WiFi Logger web interface does not always work accurately with Firefox or Safari browsers. If you are experiencing apparent problems seeing the web interface then it may well be worth retrying with either Chrome or Edge browsers, if possible. (These browsers issues are being fixed in new firmware releases as specific issued are reported. So it may also be worth checking that you have the latest firmware installed,)
Please see the page on additional WFL issues.