No BG values when Dexcom app shows "low"

[OFlannigan]

I went hypo tonight. So low, that the Dexcom app was only displaying "low". But was still receiving readings, so the sensor was connected all the time.

However, during the time of "low" my AAPS was not receiving any values from the Dexcom app. You can tell by the pale-red dots in the overview, that the values are recalculated.

The BYODA-tab also shows no readings from Dexcom during the period 1:16 to 1:36.

As soon as my levels started to rise and Dexcom was displaying an actual value, rather than "low", AAPS also picked up a value and was displaying as normal.

I've just switched from Dexcom G6 with BYODA to patched Dexcom app with G7, so I'm a bit stumped on whether this is an expected behavior.
Running the patched app's latest release 1.6 and AAPS 3.2.0 dev i.

[CaptainBalou]

I can confirm that behaviour. I had that previously with DiaKem Dexcom app 1.4.0.3906.

[khskekec]

Oh, thats sounds weird. I don't habe such a problem actually with g7 1.3 and the diakem aaps version. Possible that aps filtering it depending on some condition. It would be great if you could send a logcat capture during this phases to see whether if something is sent or not from dexcom.

Additionaly I will check the aaps Code of your specific version.

[OFlannigan]

I've attached the logs for that period here.
Please let me know if you need something else to investigate further.

AndroidAPS.2023-06-09_00-45-52.0.zip
AndroidAPS.2023-06-09_00-45-52.1.zip

[CaptainBalou]

Is there a how-to what I've to do to logcat debug that?

[khskekec]

No, so far. We should add it to the Readme.

[khskekec]

Hey,

i checked the logs and it looks like that the data was sent correctly by Dexcom App and it is also inserted into database:

01:21:28.458 [main] D/DATABASE: [DataReceiver.onReceive():36]: onReceive com.dexcom.g7.EXTERNAL_BROADCAST Bundle{ glucoseValues => Bundle[mParcelledData.dataSize=152]; }Bundle
01:21:28.502 [RxCachedThreadScheduler-42] D/DATABASE: [CompatDBHelper$dbChangeDisposable$2.accept():59]: Firing EventNewBg GlucoseValue(id=194726, version=0, dateCreated=1686266488501, isValid=true, referenceId=null, interfaceIDs_backing=InterfaceIDs(nightscoutSystemId=null, nightscoutId=null, pumpType=null, pumpSerial=null, temporaryId=null, pumpId=null, startId=null, endId=null), timestamp=1686266486000, utcOffset=7200000, raw=null, value=37.0, trendArrow=FLAT, noise=null, sourceSensor=DEXCOM_NATIVE_UNKNOWN)
01:21:28.503 [RxCachedThreadScheduler-42] D/DATABASE: [CompatDBHelper$dbChangeDisposable$2.accept():64]: Firing EventNewHistoryData 1686266486000 GlucoseValue(id=194726, version=0, dateCreated=1686266488501, isValid=true, referenceId=null, interfaceIDs_backing=InterfaceIDs(nightscoutSystemId=null, nightscoutId=null, pumpType=null, pumpSerial=null, temporaryId=null, pumpId=null, startId=null, endId=null), timestamp=1686266486000, utcOffset=7200000, raw=null, value=37.0, trendArrow=FLAT, noise=null, sourceSensor=DEXCOM_NATIVE_UNKNOWN)
01:21:28.506 [RxCachedThreadScheduler-44] D/NSCLIENT: [NSClientPlugin$onStart$5.accept():113]: ● QUEUE Resend started: NEW_DATA
01:21:28.507 [DefaultDispatcher-worker-3] D/DATABASE: [DexcomPlugin$DexcomWorker.doWorkAndLog():186]: Inserted bg GlucoseValue(id=194726, version=0, dateCreated=1686266488501, isValid=true, referenceId=null, interfaceIDs_backing=InterfaceIDs(nightscoutSystemId=null, nightscoutId=null, pumpType=null, pumpSerial=null, temporaryId=null, pumpId=null, startId=null, endId=null), timestamp=1686266486000, utcOffset=7200000, raw=null, value=37.0, trendArrow=FLAT, noise=null, sourceSensor=DEXCOM_NATIVE_UNKNOWN)
01:21:28.507 [DefaultDispatcher-worker-3] D/WORKER: [LoggingWorker$doWork$2.invokeSuspend():27]: Worker result SUCCESS for class info.nightscout.source.DexcomPlugin$DexcomWorker
01:21:28.517 [DefaultDispatcher-worker-2] I/NSCLIENT: [DataSyncSelectorV1Impl.processChangedGlucoseValues():370]: Loading GlucoseValue data Start: 194725 GlucoseValue(id=194726, version=0, dateCreated=1686266488501, isValid=true, referenceId=null, interfaceIDs_backing=null, timestamp=1686266486000, utcOffset=7200000, raw=null, value=37.0, trendArrow=FLAT, noise=null, sourceSensor=DEXCOM_NATIVE_UNKNOWN) forID: 194726
01:21:28.519 [RxCachedThreadScheduler-44] D/NSCLIENT: [NSClientPlugin$onStart$5.accept():113]: ► ADD entries Sent PairGlucoseValue {"device":"AAPS-Dexcom","date":1686266486000,"dateString":"2023-06-08T23:21:26.000Z","isValid":true,"sgv":37,"direction":"Flat","type":"sgv"} 194725/194726

This excerpt shows the procedure for 01:21:00, the first missing value. In my opinion the problem in this case, because the data is broadcasted correctly, in AAPS.

I am currently on AAPS 3.1.0.10. Do you have a chance to test it with this specific version. Maybe we can define this as special AAPS problem?

Kind regards

Selcuk

[OFlannigan]

Me and @khskekec just had a call to discuss this further.

According to the logs, the value was correctly transfered by the Dexcom app and also received in AAPS.
But the values are still not displayed and also not back filled.
The logs also show that the value was submitted to Nightscout, but it's also not visible there.

I will now create an issue in the AAPS repo. Maybe the devs there have an idea on how to fix this.

@khskekec will also try to test this with an earlier version than mine, but can't tell, when he'll have the chance to do so.

[OFlannigan]

Milos replied to the issue I created in the AAPS repo.
Apparently the value 37 is considered an invalid value by Dexcom.

nightscout/AndroidAPS#2586 (comment)

I will monitor this behavior in case I'll go that low again

[ideaweb]

Same issue with "high". It was never an issue with BYODA and G6. But without showing any value like 401, Loop im APS "stops".