Drivebit stopped working - date and time setting issue?

[Wilkovian]

So, I use drivebit and have found it really useful but about a week ago it stopped working; on both of my android devices. 

I logged out to try logging back in again and it wouldn't let me connect to fitbit, saying my device has 'the wrong date or time setting' - both are Android devices and are set to automatically set date and time. I'm in the UK so it's currently BST which is GMT+1

One is an LG G3 the other is a HTC One M8. I've never had any issues then on the same day they both have this one? 

I'm not sure what to do but it's a pain to add the driving I do manually which I'm having to do at the moment.

Has anyone had similar issues and solved them or know of anyone that has?

[Wilkovian]

Ok after a scout about I discovered the update to the security settings that's recently taken place and I seem to be one amongst many on Android suffering this issue! My Apple brethren seem fine so it's just us until they update the app. 

But hey, for those of us in the same boat I'll leave the topic up so the title at least can direct people here so they can find out as well. 

Fingers crossed the developers get on it ASAP though as it is, as they say, a severe discomfort in the gluteus maximus to have to go back and input driving manually every time!

For those who haven't seen it yet here is the link to the security update; https://community.fitbit.com/t5/Third-Party-Integrations/Potential-connection-issue-between-apps-and...

[Poo]

Hi, thanks for that info.

I've emailed the developer twice in recent days but heard nothing back.

I've taken to noting my steps when getting in car and if they haven't changed on arrival I don't need to log the drive. The One isn't too bad on short trips especially if you keep it steady by place the seatbelt tightly across it. Not recommended for wrist devices   

Hope they sort it.

[Fizzii13]

Thanks for this - I drive a lot for work and it has been really frustrating that DriveBit stopped working! 

I appreciate finding out what the issue actually is and I will keep an eye on this thread for any updates. 

[Wilkovian]

Hey, there is now a drivebit replacement available on google play under the name TravelBit. 

It's a little different to Drivebit and I can't tell which I prefer yet but it works in a very similar way and is still far more convenient than manually logging on the fitbit app! If you haven't already I recommend checking it out.

I'd be intrigued to hear what you make of it actually; I've been away for two weeks on a cycling holiday and hadn't been using my Blaze whilst I was there so I've started again since Monday and am using Travelbit. I think it's making my 'calories burned' in the Fitbit app and on MyFitnessPal quite a bit lower than they used to be; I seem to be averaging 480 additional cals burned for a 12,000 step day as apposed to the 700ish I was before I went away and I think the difference is using TravelBit as opposed to manually inputting to FitBit or using Drivebit. 

I always set the activity as being 'Riding in a car or truck' though instead of 'Driving' as I found driving showed too high a calorie burn when I was starting out with Fitbit. That's a few years ago though and was when I was using my One instead of the Blaze I use now.

Let me know how you get on please!