Blood glucose not updating

[Thasgolas]

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]

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

[Thasgolas]

It's a little intermittent, but here's what I'm seeing right now.

On Thu, Apr 19, 2018, 7:39 AM Ryan Mason notifications@github.com wrote:

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-382718641, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDjTyW3MYFJHyqjBFznihYhDr09C7ks5tqIWCgaJpZM4TbtZM .

[Rytiggy]

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

[Thasgolas]

Here you go again. I should have included an image from xDrip+, too, but didn't think of it at the time. XDrip was up to date, though.

On Thu, Apr 19, 2018, 8:02 PM Ryan Mason notifications@github.com wrote:

@Thasgolas https://github.com/Thasgolas I don't think the image attached right could you send it again?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-382929873, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDjQT-EFQya_P9eKVnM7PNlIBk5k4ks5tqTOmgaJpZM4TbtZM .

[Rytiggy]

What API endpoint are you using?

[Thasgolas]

http://127.0.0.1:17580/sgv.json

On Fri, Apr 20, 2018, 7:27 AM Ryan Mason notifications@github.com wrote:

What API endpoint are you using?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383079921, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDsHf_8PDa2FvgP19v7mAL3v78wVVks5tqdQ9gaJpZM4TbtZM .

[Rytiggy]

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

[Thasgolas]

Yes, though it seems to respond slowly.

On Fri, Apr 20, 2018, 8:37 AM Ryan Mason notifications@github.com wrote:

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

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383098425, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDm3-x_l-IQtjxV2LiN7iDsIX5SODks5tqeSmgaJpZM4TbtZM .

[jseaber]

@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]

I have most notifications turned off to my fitbit. When I've noticed long update delays, I've sometimes managed to get it updated by using one of the right buttons to move away from the watch face, then going back. It seems to usually catchup then.

On Fri, Apr 20, 2018, 10:55 AM John Seaber notifications@github.com wrote:

@Rytiggy https://github.com/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 https://github.com/Thasgolas - Do you still receive other notifications on your Versa when SGV readings halt?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383141016, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDtIHLf5wc4cfJAFBVhckepwBzi7uks5tqgT4gaJpZM4TbtZM .

[gitanO0]

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]

@gitanO0 Are you on an iPhone or Android?

[gitanO0]

android pixel 2xl verizon

[gitanO0]

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

[gitanO0]

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

[gitanO0]

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

[Rytiggy]

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

[gitanO0]

[Rytiggy]

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

[gitanO0]

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

[gitanO0]

bam, just like that. working. thx!!

[Rytiggy]

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

[gitanO0]

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]

The API endpoint is only accessible to the phone, or an authorized device connected to the phone (Bluetooth).

On Fri, Apr 20, 2018, 2:19 PM gitanO0 notifications@github.com wrote:

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?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383196061, or mute the thread https://github.com/notifications/unsubscribe-auth/AJgPTOl_IMWuJJOsuwMgeNuYdx7ylL-zks5tqjSvgaJpZM4TbtZM .

[gitanO0]

ah

[gitanO0]

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]

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]

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

[gitanO0]

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

[jseaber]

Agreed - I can barely read the small font. Would live to see adjustable sizes. A smaller clock would be fine.

On Fri, Apr 20, 2018, 2:26 PM Ryan Mason notifications@github.com wrote:

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

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383197784, or mute the thread https://github.com/notifications/unsubscribe-auth/AJgPTKDxeah20_O9Twn6VQrxlLHgZ-c6ks5tqjaCgaJpZM4TbtZM .

[gitanO0]

the very right hand side of the battery icon is just a hair over lapping the left digit of the battery percent number.

[gitanO0]

Right... certainly if real estate is an issue, which of course it is... I'd be all for slight reduction in clock since and the heart and foot symbols

[Rytiggy]

I've added a ticket for this! In the next release battery overlapping has already been fixed. here's the ticket https://github.com/Rytiggy/Glance/projects/1#card-9153056

[Thasgolas]

Yes and yes!

On Fri, Apr 20, 2018, 2:33 PM Ryan Mason notifications@github.com wrote:

https://github.com/Rytiggy/Glance/projects/1#card-9153056

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383199210, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDrcNfKfhqQsqvNYJaP5Ng88z_tRYks5tqjgGgaJpZM4TbtZM .

[gitanO0]

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]

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]

Ok, following u on twitter now.

[Thasgolas]

Did you already make the BG number bigger (or did my eyesight suddenly get younger get better? 😀)

On Fri, Apr 20, 2018, 3:22 PM gitanO0 notifications@github.com wrote:

Ok, following u on twitter now.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383211761, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDjTxH6j96leYVrbQlxH89tCi9OZzks5tqkNygaJpZM4TbtZM .

[Rytiggy]

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

[Thasgolas]

About the same

On Fri, Apr 20, 2018, 6:52 PM Ryan Mason notifications@github.com wrote:

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

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383249836, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDgsGBTbPhQlgKNEXA1vwhj50l2kPks5tqnTMgaJpZM4TbtZM .

[Thasgolas]

Still having same issue. This morning, I had to force the watch to re-collect the data several times. I'm also confused as to how app updates are delivered - (currently using the published version)

On Fri, Apr 20, 2018 at 7:15 PM, Rabbi Gutman thasgolas@gmail.com wrote:

About the same

On Fri, Apr 20, 2018, 6:52 PM Ryan Mason notifications@github.com wrote:

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

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-383249836, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDgsGBTbPhQlgKNEXA1vwhj50l2kPks5tqnTMgaJpZM4TbtZM .

--

Fight back spam! Download the Blue Frog. http://www.bluesecurity.com/register/s?user=bWFyazE4MDk%3D

[Rytiggy]

@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]

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:

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

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]

@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]

@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]

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

[jseaber]

Downloaded! There were no issues today on v1.1.2...

On Tue, Apr 24, 2018, 9:30 PM Ryan Mason notifications@github.com wrote:

@jseaber https://github.com/jseaber Could you check with the latest release 1.1.3 https://github.com/Rytiggy/Glance/releases/tag/1.1.3 now that the Fitbit gallery servers seem to be working better!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-384141867, or mute the thread https://github.com/notifications/unsubscribe-auth/AJgPTENH9Wi0J-zT1BYe7I3oVs_Fdoteks5tr9_RgaJpZM4TbtZM .

[tim2000s]

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

[jseaber]

@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:

[]

2) 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.

3) 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?

[Thasgolas]

FYI, I had several incidents of not pulling data today. Most of the time, I pushed the exercise button to rest the face, but twice I had to actually sync the fitbit to get it to start pulling again. xDrip+ was working thru all these.

On Thu, Apr 26, 2018, 1:21 PM John Seaber notifications@github.com wrote:

@Rytiggy https://github.com/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. xDrip+'s sgv.json output was null during this time, so this looks like an xDrip bug:

2. 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.

3. 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: image] https://user-images.githubusercontent.com/9965388/39323973-d685dbbe-4953-11e8-9525-ba174439e286.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Rytiggy/Glance/issues/10#issuecomment-384741254, or mute the thread https://github.com/notifications/unsubscribe-auth/APzPDgtHzvjyVCn8Ep_-Jx2GZ6BeZ-93ks5tshBCgaJpZM4TbtZM .