About jsinnott

@dwin : Thanks for this. I have not tried unpairing the Fitbit One but strongly suspect that an Inspire 3 by itself will function correctly. If that weren't the case we'd see (I'm guessing) lots of forum complaints about it. Also, @MarcyBT has (again, I'm guessing) done this and her posts suggest that things are working fine for her. ... View more

Update: Sorry, the post below was apparently premature. The steps below actually don't seem to fix the "zero steps" problem-- I'm confused as to what changed but the step data displayed when I wrote the post below has now disappeared. Sorry for the confusion... Hi everyone-- Good news (maybe): I believe I've found a work-around that restores correct syncing of step data from Fitbit One devices. It's not free and I'm not entirely sure *why* it works but it does seem to work. Here are the details: Based on a post by @MarcyBT on November 26, I started looking at the Fitbit Inspire 3 as a replacement for my Fitbit One. They were (and still are) on sale at Amazon for $70 so I bought one. It turns out that if you pair an Inspire 3 to the same phone that you've previously paired a One, the result is that step data from the Fitbit One shows up in the iOS app. I believe that both the One and the Inspire 3 need to be syncing with your phone for this to work which implies that both devices need to be charged and near your phone, but it does seem to work.  Link to the Inspire 3 at Amazon, currently on sale for $70 although it looks like that sale price ends later tonight: https://www.amazon.com/Fitbit-Management-Intensity-Tracking-Midnight/dp/B0B5F9SZW7 Other interesting (?) things I've learned: Un-pairing the Inspire 3 causes the "zero steps" problem to re-appear Preventing the Inspire 3 from syncing (I wrapped it in aluminum foil) causes the "zero steps" problem to re-appear Open questions: Probably nothing special about the Inspire 3, right? Inspire 3 is the cheapest solution but my guess is that doing this with any reasonably current Fitbit device would have the same effect? I've only tested this by having the One and Inspire 3 paired with the same phone and syncing at the same time. Not sure if these are necessary conditions or not-- my guess is that the "same phone" condition matters but I'm less certain about the "at the same time" condition. If, for example, the two devices are talking to each other (which I sort of doubt) then maybe the "at the same time" condition matters because it implies the two devices are close enough to talk to each other. 'Hope this is helpful-- one way to view it is that by paying $70 (plus the future work to keep my Inspire 3 charged) I got my Fitbit One working again. Well worth it for me. ... View more

Hi @LizzyFitbit -- It's been two weeks since you last posted on this topic-- any news you can offer us? Your last posting asked that we all report model and OS version of our phones and a bunch of us did that. Can you share anything about what happened with that information? You've also suggested that your engineering colleagues are working on a fix for this-- is that still true? Personally I'm committed to waiting for a fix-- I strongly prefer my Fitbit One and want very badly to continue using it. But others on this thread may have different ideas about waiting. Any information you can share about timelines would be *incredibly* valuable-- even if it's just a rough guess. It'd also be very useful to know if you've decided not to fix this bug-- so we can move on to other solutions as needed. But the current lack of information makes it difficult to make decisions about how to proceed.  Again, thanks for your past updates and for any information you can offer... ... View more

Hi @LizzyFitbit -- Thanks for this update. Here's (my version of) the information you requested: Fitbit iOS version: 4.30 (no update showing in the App Store) iPhone 13 Pro Max iOS 17.6.1 For what it's worth, as of this morning, the "activities/steps" resource api also still returns 0 steps for all days from August 28 through yesterday. Thanks! ... View more

Hi @LizzyFitbit -- Two weeks ago (November 4) you posted a super-helpful reply on this thread indicating that your colleagues were working on a fix for this problem (where "this problem" means "iOS app and web api report zero steps since August 28" 😄). Have you received any additional information since then? Anything you can share with us? I was heartened by the posting on this thread by @bobthompson on November 12 saying that up-to-date step data is available through the export facility (at https://www.fitbit.com/settings/data/legacy-export)-- to me this suggests that your colleague's fix might restore the visibility of historical step data. Anything you can share about that? Again, thanks for the time you've devoted to this 😄 ... View more

@penny26 : The attribute names I listed above (for example "activities_minutesSedentary") are identical to those used in the JSON returned by the web API except that I've changed "/" to "_". So the actual attribute name for "activities_minutesSedentary" is "activities/minutesSedentary". ... View more

Pointer to a community post I made on October 28 that describes this problem from a Web API perspective: https://community.fitbit.com/t5/Web-API-Development/Activities-steps-API-returning-0-steps-since-August-28-other-endpoints/m-p/5682411 A couple of notes that put this in a more "iOS app" context: My device is a Fitbit One My device shows step counts on it's LED display My device syncs sleep data correctly (i.e. sleep data displays in the iOS app and can be fetched through the web API) iOS app (and web API) show (what I believe to be) correct step count data on August 26, a likely incorrect value on August 27 (12 steps) and 0 stepss every day since The data for the following attributes (using their web API names) are also, I believe, incorrect since August 27-- my guess is that all of these are derived from step count data so it's all the same problem: [ activities_calories, activities_caloriesBMR, activities_steps, activities_distance, activities_floors, activities_elevation, activities_minutesSedentary, activities_minutesLightlyActive, activities_minutesFairlyActive, activities_minutesVeryActive ] Weirdly, the "activities_activityCalories" attribute still seems to be reasonable. @LizzyFitbit  I hope this is useful and am grateful (assuming I understand you correctly) that a fix is coming soon. Can you share any information about whether that fix will restore the data that is currently incorrect-- that is, will the historical data that currently showing bad values (mostly 0) be corrected? Or will the fix only cause future data to be displayed (or returned by the Web API) correctly? Thanks! 😄   ... View more

Hi Gordon-- Thanks so much for the quick reply. I'll look forward to your email 😄. ..j ... View more