There are a healthy number of apps/watchfaces in the Rebble app store, some of them rather old. I can’t comment on whether they work. It’s confusing as there are different tech stacks, so some CGMs will only work with certain Pebble watchfaces / apps.
Most of my research was on the Dexcom Share API, hence why there is more content there.
I’ve helped someone set up T1000 CGM watchface, which was released this year in 2026 - it was easy to setup and seems reliable (more reliable than FitBit Versa 4 running Glances, which supports a lot of different CGM interfaces).
I’ve heard that there is development happening on xDrip+ for Pebble! It sounds like they publish an interface over Pebblekit Android, with the intent that any watchapp or watchface would be able to subscribe to data from xDrip.
I skimmed it and it also looks like they have a local web server that works well, so regular PebbleJS works without internet access. If I was in that ecosystem I’d probably use that … But having push support via Pebble Android would be nicer than polling every minute or 5
I updated earlier today with a link to an active fork (sadly no PBWs built).
It’s not pretty at all (it requires internet access, etc.), but for LibreLink it works surprisingly well. Judging by the fact that the daily user I built it for hasn’t had to call me for major changes yet, it seems to be stable enough.
Obviously, this isn’t the ideal long-term solution or something that works for everyone. I just wanted anyone searching for a solution to know that this exists.
After building this, I can only emphasize how valuable a unified API would be.
The Urchin watchface is still looking really good in 2026. It links to nightscout or Dexcom share. It is almost completely customiseable with graphs and other areas of the display, and works great with colours. It isn’t on the store, but you can sideload it here: GitHub - woernsn/urchin-cgm: A graph of your CGM data on a Pebble watch. (this is a fork, last edited four years ago). All seems to work, EXCEPT the status line for things such as IOB and Loop data…
This is super interesting and something I think could be very beneficial to be able to help developers who don’t have any sort of reference point for these ecosystems to be able to integrate.
If I were making a very modular watch face, something like this is something I think I’d be interested in including, but from my perspective I think I’d run into three issue:
I don’t have T1D and therefore am not aware of how any of this stuff works (I can read API docs but I can’t necessarily use the user-facing software). If I had a reference point of the main integrations and how to tell users to get keys needed and what they are, I think the barrier to integrate would lower
Same as above, I don’t know how to make this information useful. Possibly having UI example of small, medium, large widgets on a watch face could help me understand what sort of information is useful at those size contexts.
If I’m making a watch face I think I’m concerned about battery life. I don’t know the useful frequency of data updates in the context of a watch face to be able to make a smart decision on refresh times I set. If it necessitates I update constantly that’d be something important to know
These examples and API reference points you’ve included are great and I think start to fulfill my two main issues above. I think the lower the barrier of entry for someone making a watch face is, the more likely something like this could become just another widget for that face to increase the options for people that want this data on a watch face
I’ve just ordered my first Pebble watch (Time 2). My goal is to build a companion watchface / set of apps to integrate with AndroidAPS. I was going to build something basic from the ground up but just discovered this Urchin-CGM via Google and now am thinking how to improve it.
I’d like something that communicates directly with the phone so I don’t need Internet access. Also, I often use the bolus calculator, temporary targets and other commands directly from my watch. But perhaps a watchface that integrates with Xdrip+ for reading, and separate apps for communication with AndroidAPS makes more sense.
I’m new to Pebble and the community, so am happy to team up or contribute to something ongoing. Is Urchin-Cgm an active project? I’m interested in extending it as the layouts seem very configurable and I’d like a watchface I can change colors etc over time - part of getting a pebble was for a bit of personality!
