Something went wrong last night. I don’t know what’s wrong. I will test again.
But the Sleep App started tracking without the watch. Normally was waiting. Today in the morning I was seeing that the companion App was not tracking. But the vibration alarm in the watch was working normally, so I don’t know what was wrong.
I have the same Situation with Versa Lite
Hi everyone, sorry it took so long this time to get back to you with some news. It seems that letting it go for a while, going on a vacation, and returning with a set of fresh eyes might have had some upside as I bring a new release which should have heart rates working.
I’m not sure how large battery impact it will have but I’ve tried to do it in a battery efficient fashion.
Unfortunately regarding those of you with Versa Lites - I don’t know what might be the issue but maybe it has something to do with a lack of checks for sensors in the previous builds, which I have now added. But not sure about that as there is no way for me to debug this without the actual device.
Link as usual: https://gallery.fitbit.com/details/90650cd6-76fa-40db-a747-240ac7da8a02
1 Like
Thank you @jiri-urbandroid. Hope you enjoyed your vacations.
You were missed for sure.
Installing and testing tonight.
Previous version has worked fine every night, just some issues that were Bluetooth fault and not Sleep fault.
1 Like
Worked fine yesterday with HR active.
Still not sure if the HR was gotten from the watch of by the way of FitToFit app coming from Fitbit, but no crash all night.
1 Like
Everything seemed to work fine last night. Except did not get any heart rate data. But this is the first time in a long time I got a graph, as opposed to a flat line all night. Lets see how it goes tonight.
1 Like
The HR worked fine yesterday to me too, but still gets flat line. What can I do to help you resolve this Versa Lite issue?
1 Like
@ludohavil There’s probably no way to tell if it’s from FittoFit or from us, but if you had HR turned on (in Sleep on the phone) and no crash the whole night, I’d call it a success.
@djjstew Okay, let’s see how it unfolds. Please make sure to enable HR in Sleep as Android (settings > wearables > heart rate monitoring)
@Mochrul Well that’s a really important point. If HR went through, then the problem is not in communication between watch and phone but probably in the sensor part of my app. I’ll try to look for anything that might differ on Lite regarding sensors…
Last night was the first one where I’ve gotten a graph for the full night despite having heart rate enabled.
But: the Heart rate is shown for the first ~2.5h of the night only, and disappears after that. I’ll keep an eye on that if that happens again.
One other thing: I do think it is quite inconvenient to have to start tracking on the phone first. What do you think about a feature that would automatically enable the Fitbit server 2h before the predicted bedtime? That would fix the inconvenience for 95% of the cases.
1 Like
The problem is that the app doesn’t have the ability to start a sleep logging. According to Jiri this is a flaw in the Fitbit operating system… 
@Korbinian
Could you send me a debug log (menu > report a bug)?
Regarding the server start - are you using automatic sleep tracking or do you always start manually? I agree with you that the current flow is not perfect. As @JabbaMoon says…if Fitbit was able to send a message first there would be no hassle with the server at all 
disabled FitToFit yesterday before start track Sleep and the graph was nice this morning, HR and all.
Congrats @jiri-urbandroid.
Comparing with Fitbit own sleet tracking Sleep is better, Fitbit did not got the time I was awake around 6 am and Sleep did.
About the battery use, I think is less than before, in previous test the watch was using about 10% when tracking with Sleep, and about 5-6 % when not, today it was about 7-8 % so looks about 2% more efficient even with HR enabled.
Let’s not jump to conclusions I think the battery drain numbers may vary but all in all it seems like a good percentage.
So hopefully we just need to sort it out for Versa Lite and it’s gonna be ready for release.
Currently I start tracking in the app and then start tracking on my watch. So the manual option. I’ll have to look into the automatic tracking, that seems more like what I want.
Also I’ve sent you the debug log.
I haven’t used in a little bit, because the main purpose I wanted it for (smart alarm) has been negated by having young kids that have me awake well before my alarm. 
I’ll give it a go tonight, though, to see how the tracking fares, with HR.
@Brian_Deleeuw I feel you there man. I’m just about to bring a second one onto this world so smart alarm for me is an utopia
While I’m waiting, I would like to report another issue I found lately. When I try to test the sensor, the helper process does not start (at least I could not find it int the notification bar) and therefore the watch unable to connect, which means the sensor cannot be actually tested.
I tested a few times with HR tracking, before I wrote this post.
Working great since last update with Fitbit Ionic. Thanks a lot.
@jiri-urbandroid
what sensors you use? on this page in the Tab “specs” you can see what sensors the Versa has and the Versa Lite not:
https://www.fitbit.com/shop/versa
So if you are using the “3-axis gyroscope” it is clear why it is not working. the HR Tracking is working on my Versa Lite and only my moves are not tracked.
I’m using the accelerometer, not the gyroscope, so this is not the cause. Could you please send me a debug log (menu > report a bug) to let me take a look?