After a very lazy Saturday (think pajama-day-TV/book/movie marathon complete with Korean take-out for dinner), I woke early to a 63° Sunday morning!
(!!!!!!)
After feeding the cats just past six, I walked out onto the porch and startlingly basked in the beautiful chill of a spring morning.
Having woken early on Saturday morning to work half a day, James was less than amused by my noisy coffee-making and general prancing about; once he realized how awesome our long distance run was going to be, he perked up considerably.
The 8-mile run turned out to be every bit as lovely as I hoped. We kept right smack at a 9:45 pace for the duration and held conversation for the entirity. Yesterday's run re-energized me in the way that the first cool weather run in the fall does. To not struggle for breath against the heat and humidity and to not sweat in torrents was the sweetest gift Mother Nature could have given me yesterday.
Especially because of what happened Saturday.
You will note that I do not have any fun pictures or graphs to share with you today. It is with sadness and frustration that I report that I will be returning my Nike+ Sportwatch and retract my initial review and endorsement on purchasing.
As I have written in my return note to Nike, I maintain that the watch is fantastic - easy to wear and easy to use. However, the other half of the package (and a big reason so many people have paid $200 for this watch) is being able to store, access, and analyze the data on your computer post-run.
And there, something has gone completely wonky.
On Thursday, I noticed that my watch uploaded the data from the run, but wouldn't let me access the GPS route information. I just chalked it up to the Nike+ website always being a little buggy and didn't think anything of it. On Saturday, I noticed that the Nike Connect application wasn't registering the device, so I unplugged from and replugged it into the USB port.
Windows does not recognize your device. Please uninstall and reinstall.
Funnily enough, I had had a similar problem with a USB port with my coworker's computer. However, that error was seated in a USB issue - nothing worked on any port. But my issue was seated with the watch; James's Garmin remote antenna, however, for example, worked just fine.
(Yeah, that was especially annoying.)
I tried all of the usual steps - uninstalling/reinstalling the program and drivers, checking for any Windows updates that could have interfered, restarting the computer. No luck. Then I search on the Nike+ forum site.
Where I found 16 pages on the same issue, dating back to the launch in April.
Everyone - from people running Windows XP to Mac Air - had little trouble for the first few weeks to first few months, only to have the watch suddenly stop communicating with their computer. Particularly frustrating? The watch still will charge in the USB port, but it won't transfer the data. This runner summed it up well:
I also find it troubling that there wasn't even a whiff of these issues in the internet air when I was first researching the watch. The internet buzzed with positive reviews - nowhere does anyone report on this issue. Additionally, as the above runner says, there is zero information in their FAQs about how to deal with this challenge. I smell cover-up.
James's position on the issue? "Should've got a Garmin."
No comments:
Post a Comment