Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Food log deletion problems on sync

Replies are disabled for this topic. Start a new one or visit our Help Center.

I enter my foods here on Fitbit and let it sync to my other app (Set Point Health).  But if I make a mistake here, and delete it, the deleted entry ALWAYS shows up on the other app.  If I delete it off the other app it reappearsd after jest a few minutes.  There seems no way to delete or modify the food log here on fit bit and have it properly modify on the other app!   The other app gets all sorts of extra calories and my doctors watch that, not fitbit 😞

Best Answer
0 Votes
4 REPLIES 4

I bought a FitBit recently and love it.    I connected my FitBit to my Lahey Medical Weight loss tool (Set Point Health technology - SPHPRO.COM).   This is great as it imports my activities and calories burned into Lahey/SetPoint automatically.

 

As part of this connectivity, the "food log" on Fitbit also imports to Lahey/Setpoint.

I enter foods in the log on FitBit.   These are then imported to Lahey/SPHPRO (Set Point Health tool). 

 

But I have encountered the following severe problems:

1) If I add a food on my log at Fitbit, but then delete it (immediately or after some time) it doesn't           delete off SetPoint/Lahey.    If I delete on FitBit and then manually delete off at SetPoint/Lahey it reappears a couple of page loads later.   I have tried manually deleting several times off SetPoint after deleting off at FitBit but it always reappears.   I have also tried only deleting at Setpoint but not at Fitbit and of course  that doesn't work either.  Again, the item will reappear.

2) While the calories and food name always imports from FitBit to Setpoint correctly, the details (Fat, Carbs, Protein...) do not always import from FitBit to SetPoint (they look and add up correctly on FitBit always.)

 

I guess letting fitbit and setpoint know that the APIs (and/or deletes from the log DB) are not working right is a first step.   In the meantime is there some way to override or *really* delete the erroneous things imported to Lahey/Setpoint from Fitbit?

 

 

Best Answer
0 Votes

Thank you for being part of the Community! To start I'd like to know if it is possible to unlink and relink these 2 apps. Restarting your Fitbit app will also be a good idea. 

 

Keep me posted. 

Fitbit Community ModeratorVivian | Community Moderator, Fitbit

Did this help you? Help others by marking it as a solution! 🙂

Best Answer
0 Votes

Thanks.   I did that.  Unlinked at both FitBit and Sertpoint.   Restarted Fitbit.   Then I added a dummy 1 calorie food on Fitbit and added it to my day.   It showed up on SetPoint almost immediately as usual.   I then deleted it from the fitbit log.   But it didn't go away on SetPoint.  I manually deleted it on Setpoint.  it went away for a few minutes and then reappeared.   Same behaviour as before I did the unlink/relink 😞    Seems deletes just don't propagate to linked apps.   Or to just Setpoint?

Best Answer
0 Votes

@hiramJim I've merged your older post with this thread to keep everything together.

 

When you sync your tracker to the Fitbit servers, they send out the new data to any connected 3rd party apps. If you have deleted something that is not new data (although it is technically a change), it is simply gone so the deleted data remains with SetPoint from a previous sync. The fact that deleting it on SetPoint and then having it return if you haven't added it again on Fitbit tells me there is a problem over at SetPoint. I would contact support over there and ask them why deleted data keeps coming back. It may be in the way they are handling the sync, ie; comparing all prior syncs as opposed to only the most recent.

 

You might want to try this:

 

Add a food item here and then sync. Wait for SetPoint to update. Then, delete the item here but do not sync again. Now delete it at SetPoint. Wait a couple of hours and do not sync again during that time period. Now go to SetPoint and see if it came back. That will tell you if the issue is with how they handle the syncs or if they have another issue that is causing it to reappear.

Best Answer
0 Votes