WXforum.net
Weather Station Hardware => Davis Instruments Weather Stations => Topic started by: Mattk on January 01, 2020, 05:37:03 AM
-
Has anybody else noticed if their WLIP downloads have been failing since just after midnight (New Years Eve), I had 1 drop exactly at midnight, another 50 minutes after midnight, 1 just before midday, another just after midday.
This sounds like a Davis server issue or have Davis been messing with things again? Rather strange all this started occurring on or just after midnight 1/1/2020?
-
Hi, my weatherlink data stopped updating at 00:25 last night. Bulletin seems to be working and updating and WU is updating. Must be a Davis server issue.
-
Yes same here.
-
Yes Non Davis uploads to other sites all appear ok, WeatherLink.com bulletin is missing Barometer data for all sites and it would appear wind data is locked up on all sites. Embedded links appear ok?
-
It is the Y2.02K problem! :)
-
I made it till 12:10 am then stopped.
-
hey guys mine stopped at 12:20 as well!
-
Same here, no data in charts on weatherlink.com page post 12:50am CST. Bulletin appears to show current temperatures but many sections of app are blank / missing.
-
There's a post from Davis on this issue for dealers, which it's perhaps worth copying here:
We are currently experiencing issues with our data ingestion servers for WeatherLinkIP. This problem affects WeatherLinkIP systems only. Connect, EM, USB/serial and WeatherLink Live systems are not impacted. Customers may notice that both current conditions and archive records are not updating on WeatherLink.com. We are urgently working to resolve this issue. At this time no solution is imminent. I will provide an update later today.
-
John,
It is very very strange that ONLY WLIP loggers are affected? The only loggers still not requiring any subscription and all failing on Jan 1
-
I have a subscription and having problems. Might be their way to make us update to WLL??? I just wonder about losing data....
-
I understand that an initial fix is in place now but subject to continuing monitoring and user feedback.
And for the conspiracy theorists out there, I really doubt that WLIP has been picked on. The problem is more that weatherlink.com has to handle data from a variety of upload devices - the resulting code base must be fairly complex with - I'm guessing - major modules for each different device. When bugs do crop up, it's not at all uncommon for them to affect data from just one type of device, which on this occasion happens to be WLIP.
FWIW my opinion - and it is totally a personal opinion - is that the premium paid to buy WLIP rather than eg a USB logger effectively paid for a few years' subscription. So the WLIP model included an element of payment upfront for use of the weatherlink.com platform and it's not as if Davis received no extra money for a WLIP logger purchase. Whether Davis see it that way is another matter of course!
-
I understand that an initial fix is in place now but subject to continuing monitoring and user feedback.
And for the conspiracy theorists out there, I really doubt that WLIP has been picked on. . .
A handy quote: "Never attribute to malice that which can be adequately explained by stupidity." - Robert J. Hanlon
Rich K.
-
Had worked again for a while yesterday evening into this morning, as of ~6:30am CST data is not populating graphs again.
I submitted issue to Davis support email address yesterday - no reply as of yet. But sounds like they had notified dealers of known issue.
-
The purchase cost of the WLIP was as set by Davis and there was no set expiry time and the device was locked by Davis to their own servers. Davis can not turn around now and say this is a subscription device or it's no longer supported because it's too hard to fix, don't work with this, don't work with that, Davis created this, users purchased this as per the Davis terms & conditions at the time and Davis will dam well support it and some users won't be letting Davis forget this.
As for current status, intermittent downloads on some at times but long time between downloads and way not up to date, still totally dead on others so very inconsistent.
-
The purchase cost of the WLIP was as set by Davis and there was no set expiry time and the device was locked by Davis to their own servers. Davis can not turn around now and say this is a subscription device or it's no longer supported because it's too hard to fix, don't work with this, don't work with that, Davis created this, users purchased this as per the Davis terms & conditions at the time and Davis will dam well support it and some users won't be letting Davis forget this.
So you agree with me? ;)
An update from Davis is suggesting that the issue is somehow associated with the WLIP firmware and that updated firmware will be available for download early next week. (NB I don't have any further details - just passing on the gist of an update message from Davis to dealers.)
-
No attempt to inform customers about what's going on...only to dealers? All it takes is a note on their website explaining the problems. Unless someone reads this forum, they have no idea....shades of wunderground.
-
It's fairly obvious that Davis has done something to WeatherLink.com which reacted with WLIP on 1/1/2020 as prior to 1/1/2020 there has been no change to the logger and there hasn't been an issue since the pre-release bugs were ironed out in late 2018.
So if it wasn't broke last week, what broke it this week? AND Why?
-
Ok lets get a little cynical with this :) Question?
How would one ensure every WLIP somehow has "new firmware" installed?
Considering there was nothing actually wrong with the old firmware until the 1/1/2020 then what else is in this "new firmware" :roll:
-
WL.com isn't the only thing bit by a 2020 bug though, scroll down to 2020...
https://en.m.wikipedia.org/wiki/Time_formatting_and_storage_bugs
-
So if it wasn't broke last week, what broke it this week? AND Why?
New York City's electronic parking meters all stopped processing credit/debit/plan payments on 1/1/2020, allegedly due to a certificate expiring in each device. They will only accept cash until a manual firmware update is applied. Davis isn't the only company dealing with Y2020 firmware problems this week.....
-
Same thing happened with my mortgage payment. I went to hit the submit button and I couldn't do it. I did it fine last month. Not sure what's going on. :-P
-
From a security viewpoint, the Y2020 thing could bite you if you do not insist on 4 digit year on financial documents. Too easy change /20 (meaning 2020) to /2019 - instant non-stale dated cheque.
-
From a security viewpoint, the Y2020 thing could bite you if you do not insist on 4 digit year on financial documents. Too easy change /20 (meaning 2020) to /2019 - instant non-stale dated cheque.
When I'm elected Supreme Allied Commander of the Universe, my third action will be to make writing the date without all digits in the year eligible for capital punishment..... :twisted:
-
From a security viewpoint, the Y2020 thing could bite you if you do not insist on 4 digit year on financial documents. Too easy change /20 (meaning 2020) to /2019 - instant non-stale dated cheque.
When I'm elected Supreme Allied Commander of the Universe, my third action will be to make writing the date without all digits in the year eligible for capital punishment..... :twisted:
Ha Ha! It reminds me of the Y2K mess in the late 90's where we were hiring every programmer who still had a warm body to fix those billions of lines of COBOL code.
-
Ha Ha! It reminds me of the Y2K mess in the late 90's where we were hiring every programmer who still had a warm body to fix those billions of lines of COBOL code.
Been there, done that, got the t-shirt once already. Those who fail to learn from history are doomed to repeat it.....
-
I had exactly the same problem a bit after midnight on 1/1/2020. It got worse the next few days and I could not download data at all.
After trying everything, I realized that resetting the Archive Interval and clearing the memory of the data logger solved the problem and now
the data loss has been minimized. Is there any prospect for Davis releasing a new WeatherLinkIP Data Logger Firmware in the near future?
-
Is there any prospect for Davis releasing a new WeatherLinkIP Data Logger Firmware in the near future?
Yes. And it sounds to be imminent - eg possibly in the next few days - but it will depend on how well updating & testing new firmware works out, eg if there's any residual issue then it may be delayed. There was no update Monday.
-
....the data loss has been minimized....
Defined what you mean by minimized
-
Before I reset the archive internal, every few hours the ISS Reception was dropping to 30 or even 10% . I might be wrong but I got the impression that the data logger was trying desperately to get in contact and upload data without success resulting in the console freezing for a couple of seconds up to a couple of minutes. This behavior started a few hours after the change of year. After clearing the memory the problem was minimized. Meaning that the ISS Reception drops to 98 or 96% every few hours. So the problem is not solved but the data loss has been minimized. Has anyone else noticed similar behavior?
-
This has gotten ridiculous... No communication from Davis? Any updates?
-
I havent had any problems for weeks. Just now I noticed no upload in over 2 hours on all my listings. The console is updating fine.
-
haven't downloaded pages in awhile from my WeatherlinkIP. Today had 513 (100%) pages to download and it kept failing. moved all the wlt files and the data files and finally got what there is of this month, Jan 2020, plus Dec 2019 and only 1/2 of November. So I figure the pages memory is 513 and that's about 1 3/4 months. Anyhow, tried to get the rest of the data in November from the Weatherlink.com website and for some reason it's missing the second week although it does have the first week but the only way I could grab the month off the Weatherlink website is in increments of 30 minutes I believe it was. I would like to simply get the data in the month format similar to the way (day by day) it does the NOAA monthly report in Weatherlink. I see there is a monthly summary in landscape mode but not in same format as weatherlink software. Any way to grab the data off the weatherlink.com so that it is formatted in the same format as what I get from weatherlink software 6.05?
-
The problem appears very random...Checking thru saved stations on the app, last update times for the graphs is all over the place from current to way behind....my last update was about 18 hours ago.
-
Some sites are working a little better than other sites but none are totally up to date with a couple totally hopeless since 0:50 1/1/2020.
There is nothing to indicate anything is related to ISS RF reception
-
A fix in the form of new WLIP firmware is expected later today (California time), subject to progress with final testing.
-
A fix in the form of new WLIP firmware is expected later today (California time), subject to progress with final testing.
Lets hope they make this version installable remotely
-
Looks like another example here:
> Subject: The Ghost of Y2K hits Hamburg (Hamburger Abendblatt)
>
> The city of Hamburg in Germany has 120 new DT5 trains - and 95 of
> them still won't work after the new decade has blown in. As soon as a
> train reaches the end of the line and has to reverse its direction (and
> the train driver must turn it off and walk to the other end to drive it
> back), it won't turn on again. At all.
>
> The Hamburger Abendblatt reports in that an informer told them that this is
> attributable to a date problem, with the year flipping from 19 to 20.
>
> https://www.abendblatt.de/hamburg/article228038743/U-Bahn-Hamburg-DT5-ausgefallen-Hochbahn-Software-Fehler-Verkehr-Verspaetung-Stoerung.html
>
> All the trains stopped dead in their tracks, so to say. They have
> managed to fix the software on 25 of them, but so many are missing
> they are having to run short trains in the hopes of even keeping
> up with the schedule.
>
> A bit later in the article an update is mentioned as being at fault, the
> rest of the article is politicians blathering on.
>
> Their troubles don't stop there: a passenger purchased a ticket on 1 Jan
> 2020 that is not valid until 1.1.2040. Picture included.
Sorry, I can't read the original link so can't say if this is an accurate summary, but all sounds plausible.
-
Just Received This via e-mail from Davis:
CRITICAL UPDATE: Important firmware update for WeatherLinkIP
Who needs this update?
Everyone using a WeatherLinkIP datalogger (p/n 6555) with their Davis weather station.
Details:
Your WeatherLinkIP datalogger has a critical bug that will prevent it from keeping its time properly synched with Davis servers and cause it to stop uploading historical archive records. You may have noticed that when downloading archive records into your PC software or looking at archive records on weatherlink.com that they are not entirely up to date. This firmware patch will fix that and ensure your weather station clock stays accurate and in synch.
Installation instructions:
• Download the "WLIP_Updater_155.exe" firmware update from HERE.
• Run WLIP_Updater_155.exe.
• Click Find until your IP dataloggers DID is displayed.
• Click <Start> and wait for it to completely update the firmware in your WeatherLinkIP datalogger.
• Once the firmware is complete you should stop and wait for your archive records to catchup and be completely up to date. This may take up to 60 minutes.
If you have any problems, please contact
Davis Instruments Technical Support
M-F 7:00a to 5:30p Pacific time
510-732-7814 support@davisinstruments.com
Davis Instruments Inc., 3465 Diablo Ave, Hayward, CA 94545
-
No email notification received as yet, haven't had any response either from when I first notified them of the issue on the morning of the 1/1/2020
-
Got email.
Went to weatherlink.com website.
Info about update required, across top on my site.
Downloaded WLIP_Updater_115
Ran update per instructions, every appears to be working normally.
dedicated Win10 pc
-
Info can be found here:
https://support.davisinstruments.com/article/o3dfmlmgsp-weather-link-ip-data-logger-firmware-1-1-5-windows
-
For anybody with multiple loggers on the same network the update could FIND the first in the MAC address sequence list but then would not find any further so need to unplug the other loggers.
Interested to hear from anybody who will be or who has run the update remotely through a router & DNS.
-
For anybody with multiple loggers on the same network the update could FIND the first in the MAC address sequence list but then would not find any further so need to unplug the other loggers.
Interested to hear from anybody who will be or who has run the update remotely through a router & DNS.
I updated mine at a remote property via a remote desktop connection with an always-on PC on the local network at that property.
I understand that is not what you are asking, but I wanted to mention that it did not need to reboot anything like it does when you update console firmware. I have gotten burned in the past updating consoles remotely and then they don't reboot like they are supposed to and have gone months without a working station until I could physically get there.
-
Received email notification yesterday evening. Like others noted only currently supported on Windows (short of running a windows emulator on a mac) - as all my home computers are Macs will have to wait till tonight and try using my work laptop which is Windows.
Wish Davis would release a Mac based executable to perform the firmware update.
Glad to hear others haven't had an issue with the update.
-
The update has an inconvenient. With the old firmware I could run the stations in UTC/GMT. After the update they change spontaneously to Local Time. Since the stations I have are running in a professional environment, all Davis IP are now incompatible and useless. Trying to reinstall firmware V 109.
Note: Weatherlink V1.0 was much better in many details, one was the ability to specify the Time Zone. Davis quo vadis?
-
The update has an inconvenient. With the old firmware I could run the stations in UTC/GMT. After the update they change spontaneously to Local Time. Since the stations I have are running in a professional environment, all Davis IP are now incompatible and useless. Trying to reinstall firmware V 109.
Note: Weatherlink V1.0 was much better in many details, one was the ability to specify the Time Zone. Davis quo vadis?
WeatherLink 1.0 or 2.0 I don't believe has any bearing on this current WLIP issue, but lots have been said of the change from 1.0 to 2.0
Firmware V 1.09 is now over 10 years old and really not sure if going back to 1.09 would do much good in light of the current issue. At a local level there's no issue with whatever time you want to run but WL2.0 is a way different thing now and not necessarily for the better with the time controlled by the station position
-
Does not run on a Mac. I also sent note to Davis support to see when they will be releasing a Mac version if they do.
Here is the response I received from Davis about Mac support:
I am sorry to hear you are having troubles. Unfortunately, we only have a firmware updater available for Windows PCs.
If you need to update your IP firmware and you do not use a Windows based machine you can do any one of the following.
- Find a Windows PC on the same network your WeatherLinkIP is connected to and update from that PC.
- Bring a Windows PC laptop into your network and update from that PC.
- Use Parallels or Bootcamp on your Mac to run Windows and the WeatherLinkIP updater program.
- Take the console and WeatherLinkIP datalogger to another network and use a Windows PC at that site.
- Send your WeatherLinkIP datalogger to our service center for us to update the firmware.
You will only need to send us the datalogger itself, you can hold on to your console. Call and get an RMA and instructions from us at (510) 732-7814 | M-F 7:00am to 5:30pm pacific time
I realize these options are not ideal and if nothing else is possible at your end we are happy to update the firmware here in our service department.
-
At a local level there's no issue with whatever time you want to run
Tha'ts the problem. With that new firmware you are tied by the time the server thinks it should be. If you change this, it reverts to the time zone the server assign tou you, and in some cases this is wrong.
-
Tha'ts the problem. With that new firmware you are tied by the time the server thinks it should be. If you change this, it reverts to the time zone the server assign tou you, and in some cases this is wrong.
In summary : we pay for a weather station, we pay for a datalogger, we pay to have access to our own data on weatherlink.com, but the bugs are free! And now we have even not the choice to change the time zone of our console ... Thanks Davis
-
What I have seen with this issue is that there is nothing consistent. All my WLIP's are now normal yet did not update them all, a couple which were totally locked benefited and the update fixed them, the others which were running slow and behind are now normal so not sure why.
One thing I have noted with FW updates is the Hardware and Bootware versions never change and their is some variability with HW (1.02, 1.01, 1.11, 2.02) & BW (010, 101, 102) versions over the years but whatever it is they were and are simply not behaving all the same.
Another thing I noticed with router based WLIP links was dead on 31/12/19 into 1/1/20 data usage jumped dramatically from a year in year out average of 2mb/day to an equiv of 4 to 5 to even 12mb a day, data usage never seen before on this system. This logger has been updated to 1.15 so will be interested to see if the data usage drops back.
-
Sharing my personal experience:
I have a Davis VP2 (cabled) with Weatherlink IP attached to it. Previous WLIP firmware version was 1.1.3.
Starting Jan 1st (without knowing anything about the now known issue) I noticed my console started to constantly lock up. The console screen would freeze about 2-3 times per hour, spending as much as 7 minutes with the screen completely locked (but showing all the last data, so not a blank screen). I first noticed the issue because the clock was 7 minutes behind when I looked at the console. WLIP always stopped uploading to Davis Server during those locked-up periods as well. I tried to reboot the console, tried to reconnect the cables, everything, without any success. I was worried my console had an issue and I even thought of sending it to Davis for repair.
So a couple days later, Davis published the WLIP firmware issue. After being aware of the issue, I managed to have a friend come by my house with an Windows laptop (I use only Macs as many others here). Updated the firmware, which went quickly and without issues. After updating the firmware, I gave my console a 30-minute complete shut down just to be sure and to clean everything up, and powered everything back again.
Since this update my console screen never locked up again, and it's been running smooth.
So, definitely this WLIP issue can escalate to the whole console data processing. :roll:
-
WLIP v 1.1.5 as updated on 1/7/2020 .. note i just checked my archived data; i have no gaps in any data on 1/1/2020 and going forward.
WU: KOHSPRIN10 CWOP: EW1232
On 1/10, I hooked up a new Weatherlink Live and I have a *LOT* to talk about wrt to that effort. I've been chatting with Davis Tech support for probably at least 8 hours across 5-6 days really. Is there an appropriate thread for me to relay all of what I've learned or should a just start a new one? thanks!
I have info related to (and am planning a detailed suggestion note to Davis as a result):
1) Transferring updated data from an WLIP to Weatherlink Live weather station on weatherlink.com
2) Proper method of identifying device IDs from WLIP vs Live
3) Discrepancies in the way info is displayed on the Android Weatherlink App from each
4) Inability to Upload CWOP and WU from the Live (but is fine from WLIP )
5) Getting weatherlink.com to NOTIFY me when EXTRA sensor alarms fire (not possible on WLIP)
thanks!
John
-
I've been chatting with Davis Tech support for probably at least 8 hours across 5-6 days really. Is there an appropriate thread for me to relay all of what I've learned or should a just start a new one? thanks!
I have info related to (and am planning a detailed suggestion note to Davis as a result):
1) Transferring updated data from an WLIP to Weatherlink Live weather station on weatherlink.com
2) Proper method of identifying device IDs from WLIP vs Live
3) Discrepancies in the way info is displayed on the Android Weatherlink App from each
4) Inability to Upload CWOP and WU from the Live (but is fine from WLIP )
5) Getting weatherlink.com to NOTIFY me when EXTRA sensor alarms fire (not possible on WLIP)
TBH I'm not sure there's much there that hasn't already been discussed here in some detail in various threads. eg:
1. If you have a full local record of wlk files then these can be uploaded to your WLL a/c.
2. The DID is the DID. Provided you have it recorded accurately then that's all you need to identify the upload device unambiguously. Yes, you can infer what type of device it is from certain characters in the DID, but not sure that really helps anyone.)
3. Not sure exactly what this refers to? Is it the question of whether or not you have a supplementary anemometer set to be the primary one? (This is a setting in your WLL device configuration details on wl.com)
4. Not sure what this refers to either: wl.com accounts do support uploads to both WU and CWOP, so what's the issue? Standard wl.com does not support RapidFire (and cannot do so because wind data is uploaded only once per minute), but that's well-known.
5. Are you asking whether the WLL alarm features are going to be migrated to WLIP accounts? My guess would be no (or at least the commercial side of the project team might need a LOT of persuading), but no-one outside the immediate wl.com development team will know the proposed roadmap in detail, much less comment on it publicly.
-
Thanks johnd ... here is more detail:
1) I have to assume that the WLKs are the same as what I have in the BULLETIN tab of 6.0.5 of the PC software. I can see several gaps there .. but it isn't all that bad. I just don't understand why they have to make it so complicated for doing uploads; For that matter, I think (jmho) that we should be able to grab the "basic" data (if that's all we want), and export from anywhere, and it should be like GENEALOGY DATA that can use GEDCOM for instance for uploading into various Family Tree programs. Same idea. All of those are very complicated too, even though they're not "firmware" based usually...
2 - 3) The issue that is on WLIP, the way some of the DISPLAY tools the info is vastly different than the way WLL does ... i can add a few screen shots to show explain better. Basically WLIP doesn't care which wind sensor connection/device you have (mine is NOT on the ISS- but rather on a separate roof mounted sensor transmitter with it's onw solar panel), it assumes it belongs with the "PRIMARY" setting of the ISS (if that's what you have set) -- so WIND data is displayed on smart phone apps as "the" wind info. On my WLL, I only see WIND info on the "extra" sensor" display section, because WLL is smart enough (unfortunately) to keep things all separate. There needs to be a way to tell the different APPS as well as probably what data you want to upload to WCOP/WU what devices to report for which data explicitly rather than hoping that it gets it right...
4) when i was using WLL as the upload to cwop and wu, only the BAR was being reported, because that's the only item on the WLL itself; none of the other sensors were being picked up, especially the outside temp off of my ISS
5) Nope ... not expecting those features to be migrated to WLIP, other than for the value that would have in enabling the feature for folks who don't have WLL :) I have one (now) so i'm all set.
So there you have it... does that explain some of this a little better?
John
-
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
The one with data is from the WLIP...
-
Quickly on your points:
1. The wlk file situation is what it is - I wouldn't expect it to change, but I guess anything is possible at some future date. One less obvious problem for Davis is that wl.com has become relatively complex because of all the different upload devices and sensors that wl.com has to accommodate. 'One platform to rule them all' has real advantages but it means that there may well be implications and consequences that aren't always easy to foresee for any change in architecture hence the resistance to making changes;
2. What do you have configured for 'Select Anemometer' in the Device Configuration | Advanced Settings option for the ISS channel on your wl.com a/c?
4. That's an fault somehow with your account or configuration - talk to Davis support
-
Anemometer type is "VANTAGE PRO2 ISS" the other option being VANTAGE VUE ISS or 3rd party.... i do only have one of course so "this device" is the only option for the selection.
-
Correction on my issue with 4 (uploads) .. actually only the WIND is missing .. not surprisingly, just as it is on the smartphone app... hmmm
-
Anemometer type is "VANTAGE PRO2 ISS" the other option being VANTAGE VUE ISS or 3rd party.... i do only have one of course so "this device" is the only option for the selection.
I was asking about the 'Select Anemometer' setting ;)
-
Right....it is THIS DEVICE as it's the only option...
-
Right....it is THIS DEVICE as it's the only option...
Hmm, but you have a supplementary anemometer transmitter - right? Or am I getting confused with someone else's system? Might help if you could list your active channels and associated transmitter types.
-
Just to add a bit more to this, the Jan 1, 2020 rollover apart from the WeatherLink.com upload problem also continuously cycled ISS reception from 100 - 0% every 30 minutes or so and increased data usage by maybe 80% or more.
-
Just to add a bit more to this, the Jan 1, 2020 rollover apart from the WeatherLink.com upload problem also continuously cycled ISS reception from 100 - 0% every 30 minutes or so and increased data usage by maybe 80% or more.
Well, yes. But that was a secondary effect caused by the logger trying to upload too much data as a result of the date issue - while the console is busy with the uploads, I'm guessing it can't be doing other things, which therefore causes an apparent loss of reception.