-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fitbit versa suddenly no BG data #59
Comments
Has there been any software changes? Any updates? What do you see at this url could you send me a screenshot? |
No software changes in Glance, it has been running for at least 6 months without issue. I don't think xdrip changed at the time either. It's possible there was an Android update but don't remember the phone rebooting at the time (Pixel 2) Here are the contents of the URL:
|
Could you send me a screenshot of the settings in Glance you have entered and also could you send me what you are seeing on the watchface? |
What version of Glance are you running the official verson? Or the pre-release? |
I am using a pre-release version that I side loaded. I'll try loading up the official version and let you know if anything changes, and if not I'll post the settings I use. |
Do you have the latest update on the pre-prelease? |
I definitely didn't. I got the Versa back in August or so and that's when I installed Glance. It's worked fine since then so never even checked for any updates. Not sure how long it's supposed to take to load up a new watch face, but I've been trying to load the official version now for 6-10 minutes and it doesn't seem to actually be starting (the progress bar is just sliding back and forth, not showing a percentage complete). |
Ok, killed the fitbit app and tried again and it installed. It's now displaying my last reading and showing the graph properly. I'll give it a couple hours to see if there are any hiccups. Otherwise, sorry for the false alarm 😄 |
Possibly related, or not, but I've seen a lot of periods today (sobe the recent pre-release updates) where the Versa face does not update, unless I manually force a resync. I've seen this grin both xdrip and Dexcom sources
Sent from BlueMail
…On Mar 10, 2019, 7:09 PM, at 7:09 PM, jaknoll ***@***.***> wrote:
Ok, killed the fitbit app and tried again and it installed. It's now
displaying my last reading and showing the graph properly. I'll give
it a couple hours to see if there are any hiccups. Otherwise, sorry
for the false alarm 😄
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#59 (comment)
|
Using the latest official verion 2.0.49 and it doesn't reconnect (no BG is shown) if the watch was outside the BT range. I have to open then fitbit app > watch faces > settings. Then BG values are updated. As I'm a care giver and do not wear the watch it would be great to get it back to work without interruption. Thx. |
The Fitbit Versa and ionic require the watch to be within 35 ft (range of bluetooth) as the watch is not stand alone |
Range of BT is clear. In the past the BG was shown again if I double clicked on the watch. Now I have to open the fitbit app on the phone and do the steps, written in my last comment. |
By the way. We love your watchface. THANK YOU. |
Oh sorry for the misunderstanding! What version did the connection reconnect as expected? |
I'm not sure because there was also a fitbit app update installed. I guess we are on the latest watchface version from the beginning. (Started in December 2018) |
Hmm would you be interested in testing the pre-release? And see if it's still in the updated code for me? |
Sure. |
Awesome, I appreciate that. If you could join Glance's discord chat server and let me know once you join I'll add you to the pre-release channel where you can download the pre-release |
I'm pretty new to github. Where can I find the pre-release version? |
Ah...ok..you send a link. |
Joined. |
Hello I'm new to using a libre sensor, miaomiao, an iPhone SE, a fitbit versa and spike and nightscout, but my versa keeps disconnecting and all I get are flat lines and a E404 message. Can anyone help. I've tried resyncing and resetting my glance watch face, turning Bluetooth off and on etc, but have to wait until it decides to connect again (sometimes an hour, sometimes 12 hours). Can anyone help? Thanks |
@fayebee Do you have all day sync and always connected enabled in the fitbit app? |
I have all day sync on. Where can I enable always connected? Thanks for super speedy reply 😃 |
If you scroll down to the bottom of the menu where you see all day sync, it should be at the bottom |
Under sync I just have 'device lock' and 'remove this versa' - nothing to always connect |
Okay that could be an iphone vs android thing. Do you have batter optimization turned off for both the fitbit app and Spike? |
I can't find optimization on either app, but I have just reset all network settings on my iPhone and that seems to have reconnected it. Fingers crossed this might be how to keep it synced. Thanks very much for your help and an amazing watch face! |
@fayebee haha that was a typo, I ment battery optimization, which can be found here:
Then make sure that the toggle switch is off for both Spike and Fitbit |
Ah ha! I had not done that. I had managed to get it to sync with 3 network refreshes a day, which was better. Just done this so fingers crossed it works even better now. Thank you so, so much. |
Several days ago the data from xdrip stopped showing up on my fitbit versa. It constantly shows up as 'loading' regardless of how many times I force a sync in the fitbit app, reboot the fitbit or reboot the phone. I also tried deleting the glance app from the fitbit and reinstalling, but had no luck.
The error I see from the developer menu and logs from glance are:
The text was updated successfully, but these errors were encountered: