Open moregubbinz opened 4 years ago
Were you able to get this working?
Yes Ryan, ty.
Also think we found a bug but haven't had time to post it:
Setting an alarm on the Versa clears all the data from the glance watchface. We observed the bug when our daughter was experiencing a high, and after every data clear we got the high BG notification which would restored data. Will try to catch it on camera next time.
Thanks again,
D
On Thu., Sep. 17, 2020, 8:04 a.m. Ryan Mason, notifications@github.com wrote:
Were you able to get this working?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/137#issuecomment-694298396, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACOEVLOBQIN2W2M5UBOP2ULSGIQQ3ANCNFSM4Q5BIGMA .
Thanks for the report. That issue was recently reported and fixed you can follow the thread here https://github.com/Rytiggy/Glance/issues/140
But make sure you upgrade to the latest version of Glance v2.1.114
I read the thread and it doesn't seem to be the exact issue I was seeing, but admittedly I'm no expert :)
We never lost, or had to resubmit our settings. We just lost the data that was displayed on the face, which was restored after a high alert.
Either way, I'm sure the update fixes the issue.
Cheers,
D
On Thu., Sep. 17, 2020, 8:19 a.m. Ryan Mason, notifications@github.com wrote:
Thanks for the report. That issue was recently reported and fixed you can follow the thread here #140 https://github.com/Rytiggy/Glance/issues/140
But make sure you upgrade to the latest version of Glance v2.1.114
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/137#issuecomment-694307541, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACOEVLPW5G5TTKKEGKKV4WLSGISJZANCNFSM4Q5BIGMA .
I understand now, thank you for the clarification. If I had to guess the reason why you lost the data would be a memory issue.
When the alert is fired it uses a decent amount of Glance's resources and if they are close to full when it happens it can crash the watch. This really only shows up when switching between display types or when memory is running low (aka having two BGs at once).
I think that the latest version of the fitbit SDK which I just updated on Glance should help tho as they have improved alot. Please keep me posted :)
Also in my next version I will have better memory management
Tried the latest version. The bug is still there but completely tolerable with the update.
Setting an alarm with the Versa's alarm feature still clears the glances display data, however it is restored after a second or two.
I've record a video to demonstrate the bug; and as chance would have it, our daughter was experiencing a rapid drop so I was able to catch the notification resetting the display data. I'll send you the video links as soon as they are uploaded.
And just to be clear, I'm not complaining and this bug will not stop me using this awesome app. I'm just letting you know about something it case it can be fixed, to save users a bit of frustration.
On Thu., Sep. 17, 2020, 8:44 a.m. Ryan Mason, notifications@github.com wrote:
I understand now, thank you for the clarification. If I had to guess the reason why you lost the data would be a memory issue.
When the alert is fired it uses a decent amount of Glance's resources and if they are close to full when it happens it can crash the watch. This really only shows up when switching between display types or when memory is running low (aka having two BGs at once).
I think that the latest version of the fitbit SDK which I just updated on Glance should help tho as they have improved alot. Please keep me posted :)
Also in my next version I will have better memory management
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/137#issuecomment-694322162, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACOEVLJ5VWZTQERAKGJJLFDSGIVELANCNFSM4Q5BIGMA .
Thanks a lot I really appreciate the feedback :)
But make sure you upgrade to the latest version of Glance v2.1.114
Is that version actually available on Fitbit yet?
The link you provided elsewhere goes to Fitbit, but the Fitbit app (profile picture > Versa 2 > Clock Faces > [Glance] > See all details) shows me version 2.1.112:
I'm on the latest Versa 2 Firmware version 35.70.714 and Fitbit app (Android) version 3.42. The landing page at https://glancewatchface.com/ is also still showing the text "Version: 2.1.112" under the button "Stable Glance".
Reason I'm asking: I'm also observing the Glance watch face losing all its settings when I open the Alarms app. I'm a new user and trying to set up xDrip as my data source (not working but might be a separate issue), so stripping whitespace from the username/password like you did in commit https://github.com/Rytiggy/Glance/commit/0c4b5d828d97430b11fc7d313e27bd12ba96f4bf won't help me, although the update to the later SDK version might.
I see that package.json currently specifies version 2.1.115, compared to 2.1.112 showing in the Fitbit app.
Long explanation but I want to be as clear as possible:
I setup my daughters Samsung S8 with her Fibit Versa and created a Fibit account in my name. Everything worked perfectly.
I setup my wifes Samsung A20 with her Fitbit Versa and created a Fitbit account in her name. Again everything worked perfectly.
Later I tried pairing my wifes Fitbit to my phone but messed up and used the account I created for my daughters phone/Fibit combo. I couldn't pair two watches to my account and ended up removing my daughters Versa by mistake. Doh!
Now glance has stopped working on all phones. We can load the watchface but there is no glucose data and an E500 error message that clears after powering off the watch. Also, changing the date, time or colour from settings does not change on either watch display.
Here's what I've tried so far:
I've factory reset both watches, reinstalled the app, and have done multiple power cycles. Also made sure only one Fitbit account is paired to each Versa watch.
Samsung S8 and Fitbit Versa
Samsung A20 and Fitbit Versa
I realize I've gotten here through user error but would greatly appreciate some guidance in getting things running again.