feat: dexcom connector by Chin-eng · Pull Request #208 · RADAR-base/RADAR-REST-Connector

Chin-eng · 2026-08-03T14:32:08Z

No description provided.

this-Aditya · 2026-09-01T06:51:46Z

Hi @Chin-eng, I tried compiling this locally, and it failed. It looks like the issue isn’t only that the schemas haven’t been released, there are also some compilation issues even when the schemas are published locally.

Could you please try publishing the schemas locally and fixing the compilation issues first?
Thanks

Chin-eng · 2026-09-03T08:34:04Z

Hi @Chin-eng, I tried compiling this locally, and it failed. It looks like the issue isn’t only that the schemas haven’t been released, there are also some compilation issues even when the schemas are published locally.

Could you please try publishing the schemas locally and fixing the compilation issues first? Thanks

I hit the same failure. On my machine, gradle was using a cached radar-schemas-commons:0.9.0 jar without the Dexcom classes. After clearing that cache and compiling against a fresh publishToMavenLocal jar, the BUILD was sucessful.

[Incubating] Problems report is available at: file:///Users/chin-erdenegantulga/Developer/work/radar-base/dexcom/RADAR-REST-Connector/build/reports/problems/problems-report.html
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.14/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD SUCCESSFUL in 14s
9 actionable tasks: 8 executed, 1 up-to-date

I used 0.9.1 locally to dodge the stale 0.9.0 cache. Could you run ./gradlew --stop and delete ~/.gradle/caches/modules-2/files-2.1/org.radarbase/radar-schemas-commons, then publish schemas locally and compile again?

This way compilation works on my machine.

this-Aditya

Thanks @Chin-eng, could you please have a look at the comments inline?

this-Aditya · 2026-09-23T15:57:54Z

+abstract class DexcomRoute(
+    private val userRepository: UserRepository,
+    override val maxIntervalPerRequest: Duration = DEFAULT_INTERVAL_PER_REQUEST,


I see every subclass passes base url into this constructor, but it only takes userRepository and a Duration, so the module doesn't compile. Do you meant to add some parameter here for base url?

Sorry, I forgot to stage the DexcomRoute file. I have a lot of unstaged local changes for running the connector locally, and I mixed this file up with those. I added apiBaseUrl.

this-Aditya · 2026-09-23T15:58:54Z

+    ): Sequence<RestRequest> {
+        val request = createRequest(
+            user,
+            "$DEXCOM_API_BASE_URL/${subPath()}",


This uses the hardcoded url, so requests can never go to sandbox or configurable url, even when the config says sandbox.

Yeah I changed it with the apiBaseUrl but forgot to stage the changes.

this-Aditya · 2026-09-23T16:00:16Z

+                    user,
+                    "$DEXCOM_API_BASE_URL/${subPath()}",


Same here, we can have the configurable base url so we can request any endpoint, eg. sandbox.

changed it with apiBaseUrl

this-Aditya · 2026-09-23T16:01:48Z

+class DexcomAlertsRoute(
+    userRepository: UserRepository,
+    apiBaseUrl: String = DEFAULT_API_BASE_URL,
+) : DexcomRoute(userRepository, apiBaseUrl) {


We are passing the base url here, The base class request the second argument as duration but we are passing this as a url string.

This is same for every subclass of dexcom route.

Yeah, I added the apiBadeUrl as the second argument for the parent class.

this-Aditya · 2026-09-23T16:02:54Z

+        .define(
+            SOURCE_URL_CONFIG,
+            Type.STRING,
+            DexcomRoute.DEFAULT_API_BASE_URL,


I don't see this defined anywhere.

Yeah I added it inside the new dexcomRoute file.

this-Aditya · 2026-09-23T16:07:37Z

+    private val dataRangeApiBaseUrl: String = DEFAULT_API_BASE_URL,
+) : DexcomRoute(userRepository, dataRangeApiBaseUrl) {


The Dexcom route won't compile with the apiBaseUrl param, i think it would be better to keep this param in the base class.

I put the apiBaseUrl inside the DexcomRoute

this-Aditya · 2026-09-23T16:10:15Z

+        start: Instant,
+        end: Instant,
+    ): Sequence<RestRequest> {
+        val request = createRequest(user, "$dataRangeApiBaseUrl/${subPath()}", "")


One the dataRangeApiBaseUrl parameter is shifted to base class, this variable can be renamed.

this-Aditya · 2026-09-23T18:16:55Z

+        user: User,
+    ): Sequence<RestRequest> {
+        val offset = dexcomOffsetManager.getOffset(route, user)
+        val startDate = user.startDate


IIRC, right now we can't get backfill data for more than 90 days. Even if we agreed to support 365 days of historical data, it could still fail if the user's start date is more than 365 days, so we should limit this if this is the real case. I am not sure exactly how much we can really backfill now, but please update the logic according to that.

I'm now using the dataRange window instead of user.startDate. When there is no saved offset, generateRequests calls dataRangeCache.windowFor and starts from that window's start.

this-Aditya · 2026-09-23T18:22:37Z

+                  })
+              .collect(Collectors.toList());
+      this.configuredUsers = SequencesKt.toSet(dexcomConfig.getUserRepository().stream());
+      logger.info("Received userTask Configs {}", userTasks);


I am not sure, but does userTasks also logs the clent id and secret, we can simply log the task and user counts:

Suggested change

logger.info("Received userTask Configs {}", userTasks);

logger.info("Configured {} tasks for {} users", userTasks.size(), configuredUsers.size());

this-Aditya · 2026-09-23T18:40:21Z

+            val nextOffset = if (dataAge <= Duration.ofDays(7)) {
+                maxOffsetTime.plus(OFFSET_BUFFER)
+            } else {
+                maxOf(maxOffsetTime.plus(OFFSET_BUFFER), request.endDate)


Why the next offset is after 12 hours from the newest record, with this logic I think the next 12 hours from the current offset won't be fetched?

Yeah, I meant to change it later. I was testing something. I was planning to make the poll wait window every 5 minutes. I will change it.

this-Aditya · 2026-09-28T11:58:42Z

+        fun parseDexcomTime(value: String): Instant {
+            return try {
+                OffsetDateTime.parse(value).toInstant()
+            } catch (_: DateTimeParseException) {
+                Instant.parse(value)
+            }
+        }


This still fails for timestamps without an offset. Dexcom's docs say records sourced from receivers will not have UTC offsets, and even their own /dataRange example uses a value that our parser can't handle right now. The docs say "systemTime is UTC", so we can parse it as UTC. I think this just needs one more try/catch inside the catch block to parse timestamps without a Z, since they are still in UTC:

LocalDateTime.parse(value).toInstant(ZoneOffset.UTC)

this-Aditya · 2026-09-28T12:01:10Z

+                if (window == null) {
+                    logger.info(
+                        "Skip {} for {}: no dataRange window",
+                        route,
+                        user.versionedId,
+                    )
+                    routeNextRequest[routeKey(route, user)] = Instant.now().plus(BACK_OFF_TIME)
+                    return emptySequence()
+                }
+                logger.info(
+                    "No offsets found for {} {}, using dataRange start {}",
+                    route,
+                    user.versionedId,
+                    window.start,
+                )
+                startOffset = window.start
+                endDate = minOf(endNow, window.end)


Starting at window.start can go before the participant's startDate, so we collect data from before they enrolled. Could we start from the window but not before user.startDate, and fall back to user.startDate when there is no window?

startOffset = window?.start?.coerceAtLeast(user.startDate) ?: user.startDate endDate = endNow

Chin-eng added 30 commits August 3, 2026 22:31

feat: dexcom connector

551365c

feat: dexcom initial files

e9774bd

feat: dexcom topicdata

c38aa09

feat: offsets

48f9da5

feat: dexcom EGV route

9fb32ae

feat: dexcom convertor: EGV

afdd0e6

feat: offsets

0807c02

feat: dexcom route

07ac68d

feat: dexcom requests

2199d25

feat: gradle change

6d7b786

feat: dexcom route

be4e226

feat: kafka dexcom connect files

44b9c4d

feat: connector gradle kts

ee29e02

feat: dexcom dockerfile

aa2e003

dexcom docker service

18a3bdf

feat: dexcom properties template

2616b55

feat: dexcom egv import

d7837fc

feat: dexcom egv

2d8d28a

feat: dexcom user repo addition

ed2c665

feat: dexcomUser and User not found file

59c8db1

feat: git user files

26cb46d

feat:dexcom more user files

d91ce32

feat: dexcom config files

80c82cd

feat: sequence extension

111ce26

feat: dexcom egv route update to mapctaching

037ca17

feat: added sequence extension

fd1e110

feat: dexcom events route

f45ecc0

feat: dexcom calibrations

1149c6e

feat: dexcom alerts

1cb11ba

feat: dexcom devices

9141190

Chin-eng added 7 commits August 17, 2026 14:17

feat: dexcom source connector

8120e41

feat: jackson empty consturctor

e1c8484

feat: dexcom caliberation endpoint

6196cb2

feat: dexcom events connctor route

fd2afb1

feat: alerts dexcom connector

b914b9b

feat: dexcom data range connctor

53564f4

feat: dexcom device connector

ce83721

yatharthranjan requested a review from this-Aditya August 27, 2026 10:11

Chin-eng closed this Sep 3, 2026

Chin-eng reopened this Sep 3, 2026

this-Aditya mentioned this pull request Sep 10, 2026

Dexcom schema RADAR-base/RADAR-Schemas#431

Open

Chin-eng added 6 commits September 14, 2026 20:20

fix: dexcom egv converter update

81a66d8

fix: dexcom alert converter update

119f9b9

fix: device converter update

ca8545a

fix: dexcom data range

2eed09f

fix: calibration update

d4874be

fix: events converter update

afcb028

this-Aditya reviewed Sep 23, 2026

View reviewed changes

Chin-eng added 7 commits September 24, 2026 20:59

feat: use dataRnage to poll data

c65791e

fix: 5 minutes poll window

26f7867

fix: apiBaseUrl

f6790a0

fix: apiBaseUrl

d098d04

fix: dataRange rename route

b9864b3

fix: dexcomDateRangeCache

564c5b4

fix: user count and task count

500423f

this-Aditya reviewed Sep 28, 2026

View reviewed changes

Chin-eng added 2 commits September 28, 2026 17:37

timestamps without an offset

d9a014f

fix: going before the participant's startDate

a7bc486

		private val dataRangeApiBaseUrl: String = DEFAULT_API_BASE_URL,
		) : DexcomRoute(userRepository, dataRangeApiBaseUrl) {

	logger.info("Received userTask Configs {}", userTasks);
	logger.info("Configured {} tasks for {} users", userTasks.size(), configuredUsers.size());

Conversation

Chin-eng commented Aug 3, 2026

Uh oh!

this-Aditya commented Sep 1, 2026

Uh oh!

Chin-eng commented Sep 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

this-Aditya left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Chin-eng Sep 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Chin-eng commented Sep 3, 2026 •

edited

Loading

Chin-eng Sep 23, 2026 •

edited

Loading