nightscout / cgm-pebble Goto Github PK

Hello - I just got my CGM working through Android DROID Maxx, uploading to my MongoDB using Azure. I just got a Pebble watch, and I'm trying to understand how it works. From my initial research, the Pebble watch only uses Bluetooth as the mechanism to get to the iOS or Android device, in order to get to the CGM In the Cloud. I quickly read the Pebble App Dev Guide, and I see that it uses the XMLHttpRequest.

So my question is simply to confirm that the "cgm-pebble" watchface/app is requiring the underlying bluetooth connectivity to the iOS or Android in order to make the HTTP Request -- otherwise, I am confused as to how it's "getting" to the CGM data.

I'm new to GitHub and couldn't find a way to directly email. Thank you!

(GitHub: gregwaehner // email: [email protected])

Would it be possible to implement error code icons instead of just the error code? I would be happy to create the image files... That way it would be easier to distinguish the errors as they appear?

From FB

Dorrie

Has anyone gotten a pebble to pull consistent data when paired with their personal iPhone 4 or 5s on sprint network? I know in theory it should work but I haven't gotten it to pull continuous data when off wifi. I asked this a few months back and no one had- but there are a lot more people up and running now so I thought I'd try again. I've gotten the pebble to work with all other combos except that one.

I think it is weird too. That's why I need to see if anyone more knowledgable then me has figured it out. I can set it up with any other phone/carrier and I've been troubleshooting for months and am out of ideas. John, Jason and Laurie and more have all tried to help but to no avail. So I thought throwing it out to the group again may help. I have switched to a droid on sprint now and it works fine, but it would be nice to get it working in case others have that same combo.

Jason

I wonder if it's related to how they charge for personal hotspot / pairing
And other apps can get data?

Dorrie

Yes Jason other apps like pebble cards works fine off wifi.. Only Nightscout won't continuously work as far as I can tell.
I was hoping others have had experiences with it to help.. But not finding anyone who made it work or kept trying beyond the initial issues

Jason
@bewest , are you still going to Pebble HQ this week? Can you ask about this? It seems like there might be some with iPhones on the Sprint network that that cause problems for Nightscout, but not other apps.

icon is missing

Here is an example...

Doesn't look right on round watch face

Hi - I'm helping Cheryl and she has 2 children with T1D. I tried getting creative tonight and modified the metadata information in the CloudPeddle deployment process. Unfortunately, it looks like there is a limit of one cgm-pebble instance per phone. I'm guessing it's tied to the App UUID. So my question...

1. Is there a way to run two cgm-pebble instances on the same phone?
2. Is there a way for a single cgm-pebble instance to query / display from 2 cgm-remote-monitor Azure websites?

Thanks.

• Greg

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hello.. I have some problems with the new 7.1 interface that was not in 7.0
In the "time" field where it states the time since the last read, it seems to stick on now sometimes.
It says now for a long time, even if the last read was 15 minutes ago..
I did not have that issue with 7.0 No alarms watchface..

Recommend / request validation of "custom data endpoint" as entered by end-user:

1. Trim whitespace

2. Make field "dynamic" -- put "http://" as prefix box, middle text field for Azure website name, with "suffix" endpoint /pebble as third endpoint. The "data endpoint URL" would be dynamically created based upon the 3 fields.

3. Create a button to "test connection" to ensure HTTP 200 response in order to save.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Howdy, I'm opening this issue on several projects just to touch base with developers and take a poll in a few places with a bit more limited audience.

I'm working on a suite of documents to describe how the development processes work, I've mentioned cgm-pebble here: http://process-controls.readthedocs.org/en/latest/operations/2014-01/02-questions.html#cgm-pebble
One of the more interesting questions FDA asked was how versions are distributed, and how update might be tracked. I was hoping the pebble crew might have something to contribute. I also wanted to make accurate notes on how each team does it's work, and how to get in touch with them.

I'm curious if pebble provides any notes on how many users are using which version? You might have some good notes on how long pebble update process takes also.

Thanks!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

The new share2 version sometimes has battery information, and in some cases (such as with some of the bridge projects) the battery information is not needed.

If there's a simple way to hide/remove the battery info, perhaps through toggle in config, that would be awesome. Thoughts/feedback welcome. The other way for people to handle this is to delete the battery info from mongodb, so perhaps we can take care of this purely on the webapp side. Feel free to close and toss the issue over there if that would be preferred.

P.S., ❤️ sleep mode. Thanks, all.

jshintrc should be named .jshintrc. With that change, jshint will generate the following warnings:

$ jshint src/js/pebble-js-app.js
src/js/pebble-js-app.js: line 200, col 18, 'MessageQueue' was used before it was defined.
src/js/pebble-js-app.js: line 11, col 23, 'window' is not defined.
src/js/pebble-js-app.js: line 51, col 17, 'clearTimeout' is not defined.
src/js/pebble-js-app.js: line 273, col 25, 'toString' is not defined.
src/js/pebble-js-app.js: line 296, col 21, 'clearTimeout' is not defined.
src/js/pebble-js-app.js: line 307, col 21, 'clearTimeout' is not defined.
src/js/pebble-js-app.js: line 358, col 25, 'window' is not defined.

7 errors

Happy to submit a PR to resolve the above. I can also include a Travis configuration to catch future warnings.

The at 1200, 12-hour users are seeing 12:00 AM, while at 0000, 12-hour users are seeing 12:00 PM. It has been this way since my original setup, and appears to still be persistent in a new install last night.

I just started up with Nightscount with my Dexcom G4 Share. I'm wondering if anyone has started looking into having the Pebble app speak directly to the Dexcom cloud (pulling over the parsing code from the cgm-remote-monitor repo).

The website can still provide the historical data and trends, but the watch doesn't really need to go through the website (which for me is extremely flakey because of Azure), when it can just query the last datapoint directly from the Dexcom servers and get all of the information it needs for the watchface (Dexcom provides the raw value, trending direction, time, etc.).

For some people, this is enough since we can use the Dexcom device itself to get more long term trends and it would be a more reliable way of getting the data than going through the website.

I've started taking a look at this, but I work in High Performance Computing in C all day so getting up to speed with user facing APIs and Javascript with JSON objects will take me a bit of time, so it will be a while before I can get a PR together.

As discussed with Ben and Kevin I would like to localize the three parts of Nightscout. I'm Italian and I'm supporting the Italian community in order to setup and manage Nightscout and I think it would beneficial for many to have a localized software.
I'm translating android-uploader in Italian and German via a German friend of mine.

I'm not sure how to do it for cgm-pebble but maybe with a choice in the setup.

I hope I'm using the right tool to start a discussion and keep track of changes, if not please let me know.

Ivan

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I've had a Pebble watch for quite some time and have enjoyed the week-long battery life that comes with it. When I started using the Nightscout watchface, I noticed my battery life drop to maybe 2 to 3 days, at best. On Facebook, I've seen people regularly report that they need to charge their Pebble daily.

Upon reviewing the code, it seems that the watchface is essentially polling the Nightscout website backend every minute. This means bi-directional communication over Bluetooth and network requests from the cell phone every minute for data that we know will only ever be updated every 5 minutes. This seemed like overkill to me, so I've forked the codebase and set up the poll to happen 5 minutes and 30 seconds after the most recent reading received, so we're not wasting battery and data getting information that we know we've already got.

This seems to vastly improve battery life. I wanted to open an issue and try to get some feedback on the topic before I make a PR from my fork, however, to ensure that I haven't overlooked something simple that would be essential to hit the data endpoint once a minute.

In the event that there is a problem receiving data, my edits will poll once a minute until it gets another BG value and then wait for 5 minutes and 30 seconds after that value was reported.

Hi... I compiled the cgm-pebble in CloudPebble tonight and deployed onto my iPhone. Once I got the custom data url right, the watch face displayed the BG and timestamp. However, there was a picture on FB CGM Cloud with an arrow. I'm not getting the arrow -- is there a different fork, or did I do something wrong in the compile?

A lot of people are loading multiple watchfaces, and the "T1name" is only dispalyed after the "loading" is successful. So if there is an unsuccessful attempt, or you have to scroll through a bunch to find "camping mode," it takes a long time. Is it possible to display the "T1name" immediately, since that is static data and not wait for the results of the data query?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I don't know if it is a quirk with my setup, but I have been experiencing almost constant crashes by the watch app. Upon reviewing log entries, it appeared to be crashing after waves of 5 or more rapid attempts to resend a message to the JavaScript portion of the app. After changing APPSYNCANDMSG_RETRIES_MAX to 0, the crashes have gone away and my watch's battery life is much improved, probably because the bluetooth interface has a chance to shut down when the phone is busy and waiting on the JavaScript engine to start up.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.