great concept, very poor technical QA
I must also count myself amongst the "IT Professionals" with a bad experience with this product. Or, a bad string of experiences.<br /><br />It started out so nicely. It connected to my home network consisting of two Cisco Aironet 1252 WAPs (running a WPA2 key) using the OSX installer from my laptop. It worked great. We all used it for about three weeks.<br /><br />Then, it started saying it couldn't sync. Nothing had changed in the network config or topology.  So, I decided to try to put it into setup mode and have it re-connect. It was never able to "re-connect."<br /><br />I used a packet sniffer, as well as turning on debugging on the Aironets, and found that the device was actually able to successfully connect to the wifi network, to the point of getting a DHCP assignment, sending a few frames to the internet, and getting a few response frames from fitbit. It then continued to say it was unable to sync.<br /><br />Customer service, to whom I provided a pcap file and cisco debug logs showing what was happening, was not at all helpful, although friendly, they only were able to offer the sort of inane technical help you have probably come to expect.. things along the lines of move the scale, replace the batteries, etc (all of which i did, with the expected lack of change in behavior).<br /><br />I gave up on it for a few weeks, and then decided to try again and do a deeper packet dive into the exchange it was having. I used a desktop mac to try to get it out of setup mode, and failed. With the install utility, it was able to talk to the scale, but it never got it back out of setup mode. I eventually got it to get out of setup mode after failing with the installer on my osx desktop, failing with the web installer on my osx desktop in various browsers, failing with the installer on my laptop (which had worked previously), and failing with the web installer on my laptop unless i was using safari. Finally, having gotten it to move beyond the "setup" screen, it absolutely refused to advance (or to provide any feedback that it was failing to advance) beyond the attach to network stage, the same network and same config which had originally worked fine.<br /><br />Eventually, I pointed it to a cheap netlogic WAP that I happened to have set up and unprotected for some unrelated testing work. From the laptop only, from safari only, it finally attached to the network. I've decided to leave that junky WAP online for now & unprotected just to keep the scale online.<br /><br />In summary, if you can get this thing to work, and if you can get it to remain working even though it may appear to be working originally, it is a great product. Good luck with that, though.. this is seriously some of the worst QA'd hardware/software I have worked with in many years, excepting the junk that comes from China.<br /><br />Finally, I have an offer for fitbit. I live in the bay area. I have your product here. I am a network engineer with an EE & CS background. It still cannot attach to my home production network. Send someone over for dinner. I will feed them, and then show them & happily let them debug what is clearly a major set of QA issues with your product, in my house. I can & will help with the debugging, packet capture and analysis, and trying alternate configs to isolate the issues that so many customers are having. Seriously. I want this thing to work, I spend good money on it, and it presently does not. I am also not, by any means, the only person experiencing these issues. So, here is a live testbed for you to fix your broken firmware & installers. Please, please, take me up on this offer. Thanks!
Rating: 2 stars