Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Blood glucose not updating #10

Closed
Thasgolas opened this issue Apr 19, 2018 · 62 comments
Closed

Blood glucose not updating #10

Thasgolas opened this issue Apr 19, 2018 · 62 comments
Labels
question Further information is requested

Comments

@Thasgolas
Copy link

When I get the watch face to rest, it'll load a neat cake, butt after that, it just stays there - no updates.
Samsung G8+, Fitbit Versa
@Rytiggy
Copy link
Owner

Rytiggy commented Apr 19, 2018

Could you send me a screenshot of what you are seeing?

@Thasgolas
Copy link
Author

Thasgolas commented Apr 19, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

@Thasgolas I don't think the image attached right could you send it again?

@Thasgolas
Copy link
Author

Thasgolas commented Apr 20, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

What API endpoint are you using?

@Rytiggy Rytiggy added the question Further information is requested label Apr 20, 2018
@Thasgolas
Copy link
Author

Thasgolas commented Apr 20, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

Does the endpoint have data when you go to that url on your phone?

@Thasgolas
Copy link
Author

Thasgolas commented Apr 20, 2018 via email

@jseaber
Copy link

jseaber commented Apr 20, 2018

@Rytiggy First, great work!

Just to add my first day of observations with a Versa and Google Pixel running Android 7.1.2, SVG is transmitting fairly reliably, with one mishap. The reading had not updated for 96 minutes when I woke up this morning. I'd swiped away a Fitbit notification on my phone before realizing the missed signal. Opening the Fitbit app and selecting the Versa forced a sync; SGV readings then updated, followed by several Versa notifications of unread emails and texts.

So, perhaps this issue is a deeper Fitbit sync or Bluetooth bug? @Thasgolas - Do you still receive other notifications on your Versa when SGV readings halt?

@Thasgolas
Copy link
Author

Thasgolas commented Apr 20, 2018 via email

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

K, I just got my versa up and running, got the glace clock face up and the settings set... weather api, http service on my phone/xdrip+ up with data if I look at the json data... but the clock face isn't showing any xdrip+ data... all dashes and in the top right it says "loading". Not sure what else to look at or configure.

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

@gitanO0 Are you on an iPhone or Android?

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

android pixel 2xl verizon

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

i verified that the http service on xdrip is working. lots of json data

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

the weather temp isn't coming up either in glace... just the time, heart rate, steps is all

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

is there something different about the versa that isn't allowing it to work?

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018 •
edited

There is no difference between the versa and ionic, Could you send me a picture of your settings?

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

screenshot_20180420-121505

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

Under the Api endpoint, you need to enter the URL it should look like this if you are using xdrip http://127.0.0.1:17580/sgv.json

You settings should look like this after
30742992_10211732286602737_8456260314801897472_n

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

geez, ok... what a dummy, I thougt that the xdrip default had that url set behind the scenes. my bad

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

bam, just like that. working. thx!!

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

Sorry about tha,t that was my fault for not updaing the UI yet. Great job!

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

I'm confused about how that url works between the phone and the watch. Does that data get transmitted over the air? What prevents someone else who is nearby transmitting that same URL from getting wires crossed?

@jseaber
Copy link

jseaber commented Apr 20, 2018 via email

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

ah

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

This is pretty cool. One thing I didn't take into consideration when buying this watch was my aging eyesight. The text on the screen, battery percent, time since last BG reading, etc... those really small fonts... are really hard to see without my reading glasses. Not sure if that can be helped.

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

This could be an added feature, we could make a larger text option on the companions settings that could be turned on and off.

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

or maybe even just those really small texts being in bold would do it.

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

on the versa here, the battery symobl and the actual battery text are a tad overlapping.

@Thasgolas
Copy link
Author

Thasgolas commented Apr 20, 2018 via email

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

how do we update the clock face, say when you update the published version? Will it do it automatically or do we need to manually install it?

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

You should get it automatically. Or going into pick the clockface should show an update button.

But I will be posting on all my social media when I post the update I would keep an eye on my Twitter if you are worried about not getting it.

@gitanO0
Copy link

gitanO0 commented Apr 20, 2018

Ok, following u on twitter now.

@Thasgolas
Copy link
Author

Thasgolas commented Apr 20, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 20, 2018

@Thasgolas haha looks like your eyesight must of gotten better :p how is glance working for you now?

@Thasgolas
Copy link
Author

Thasgolas commented Apr 21, 2018 via email

@Thasgolas
Copy link
Author

Thasgolas commented Apr 22, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 22, 2018

@Thasgolas I've made the watch re collect when it goes in to error state in the next release. I am trying to make the release available today. I believe that this is your issue.

You should get it automatically. Or going into pick the clockface should show an update button. Once I push the release later today.

But I will be posting on all my social media when I post the update I would keep an eye on my Twitter if you are worried about not getting it.

@jseaber
Copy link

jseaber commented Apr 23, 2018

Is it possible the re-collect upon error could get stuck in a loop?

v1.1.2 was working last night. This morning, the Versa failed to sync, and showed "loading" on the clockface for 30 minutes:
image

I was unable to force a sync in the Fitbit app. Attempting to "Sync Now" would produce an error:
screenshot_20180423-074344

Pressing the Exercise button to reset the clockface also had no impact. It self resolved while I was driving to the office...

Any ideas for debugging next time?

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 23, 2018

@jseaber Do you know if you were receiving bgs to your phone during this time?

If it happens again restart the Fitbit app by closing out of it on your phone completely then go in to the Fitbit app and make sure it syncing with the watch. If it produces an error message could you share it?

@jseaber
Copy link

jseaber commented Apr 23, 2018

@Rytiggy Will do.

Yes, xDrip+ had successfully collected glucose for every point from 6:40-7:40am. Glance failed just before 7am

xDrip+ missed a single reading at 7:45am. The Versa resumed synchronization after 8:15am.

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 25, 2018

@jseaber Could you check with the latest release 1.1.3 now that the Fitbit gallery servers seem to be working better!

@jseaber
Copy link

jseaber commented Apr 25, 2018 via email

@tim2000s
Copy link

I’m seeing a similar issue via the iPhone. Only way to fix it seems to be to restart the Fitbit app.

@jseaber
Copy link

jseaber commented Apr 26, 2018 •
edited

@Rytiggy So far, v1.1.3 is running much smoother. I encountered some related data pulling bugs during a sensor change last night.

  1. Instead of displaying no data like Nightscout does during sensor warmup, Glance shows the last known data glucose reading and the duration since the last pull. xDrip+'s sgv.json output was null during this time, so this looks like an xDrip bug:
[]

  1. When the sensor finished warming up, Glance failed to resume pulling data despite sgv.json containing several data points. I had to press the watch Exercise button to reset the clock face.

  2. Once Glance resumed pulling data, new data points were incorrectly plotted on the left side of the graph. Missing/null data was also plotted at a default value of around 125 mg/dL. Shouldn't absent data not be plotted at all?

image

@Thasgolas
Copy link
Author

Thasgolas commented Apr 26, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 26, 2018

@Thasgolas Thanks for this great write up of your bug report, its super helpful! :) For me I have noticed the random loss of signal but I have a feeling that the loss of connection with the phone to watch is due to Fitbit right now. The connection seems to drop out for other apps for me around the same interval as Glance does. I will take a further look into this and see if there is anything I can do to make the connection more continuous!

If the graph does what you are showing me again could you send me a picture of the API endpoint open in your phone's browser (should look like the image below)? I want to check that the data that is being returned from Xdrip is what is expected.

image

@Thasgolas
Copy link
Author

Thasgolas commented Apr 29, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Apr 29, 2018

What does your API endpoint look like? Could you send me a pic of it?

@jseaber
Copy link

jseaber commented Apr 30, 2018

I'm seeing the same behavior as @Thasgolas, as of an hour ago. Loss of glucose sync in Glance coincides with a sync error in the Fitbit app. Interestingly, my wife's Fitbit Charge 2 is syncing just fine.

@Rytiggy Here's the API endpoint:
https://photos.app.goo.gl/QMue3eVSv1Y3GmTw7

@jseaber
Copy link

jseaber commented Apr 30, 2018

Update - Turning Bluetooth off and on again from the phone resolved.

@Thasgolas
Copy link
Author

Thasgolas commented Jun 3, 2018 via email

@Rytiggy
Copy link
Owner

Rytiggy commented Jun 3, 2018

@Thasgolas it seems like there is no attached file. could you try to upload it again?

@Thasgolas
Copy link
Author

Thasgolas commented Jun 3, 2018 via email

@Lien64
Copy link

Lien64 commented Jun 10, 2018

I think/hope that I’ve installed everything to my fitbit versa but my clock face isn't showing anydata... Not sure what else to look at or configure. I use a iphone 5s

@Thasgolas
Copy link
Author

Thasgolas commented Jul 9, 2018 via email

@dv1
Copy link
Contributor

dv1 commented Jul 16, 2018

@Rytiggy : Can the Fitbit API handle a push model? I mean, currently, it seems that the watchface pulls data from the xDrip web service in regular intervals. It would be better if instead xDrip pushed new data through the web service as soon as that data is updated, and the watchface is then immediately updated. But is this even possible?

@Rytiggy
Copy link
Owner

Rytiggy commented Jul 16, 2018

@dv1 An event-based system does seem to be a good idea, I am not sure if it is possible at this time. Fitbit has two different kinds of communications that can be done, a File transfer and a buffered stream.
https://dev.fitbit.com/build/reference/companion-api/file-transfer/
https://dev.fitbit.com/build/reference/companion-api/messaging/

I will do some research into an event-based system

@Rytiggy Rytiggy closed this as completed Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@dv1 @gitanO0 @jseaber @tim2000s @Thasgolas @Rytiggy @Lien64