Yellow warning triangle when change a G7 sensor

[MarkusKramer75]

Hello everyone, I have been using the Dexcom G7 for good 1 month now. I have noticed that every time I change the sensor, the yellow warning triangle remains next to the glucose value for more than 35 hours. Now I'm wondering if this is really necessary. There are no values for 30 minutes and then, in my opinion, this is not absolutely necessary. Perhaps this could be reconsidered and the time shortened? Personally, I think that would be a good idea. Thank you in advance for thinking about it. Best regards Markus

[olorinmaia]

We have recently started using G7 and since each G7 sensor has it's own transmitter every sensor change will trigger this warning. G7 also seem to send BG at irregular intervals if a few readings are missed. Short story, this warning is visible almost all the time for G7.

This is only a warning, and AAPS operates as normal. But this could be improved in two ways the way I see it.

1) Consider not raising yellow warning sign when CGM = G7 and data gets recalculated. 2) Improve error message in AAPS so that users don't think this is possibly something that require action? I have improved it in Norwegian translation to something like this: "Recalculated data is used because some BS data is missing or that BS data arrives at an unexpected time. Will reset after about 24 hours. No action required"

Thoughts @MilosKozak ?

[TWilhoWI]

Also got the issue!

[Navid200]

@olorinmaia Thanks for mentioning this in the xDrip discussions.

I just did a test and reported the results here: https://navid200.github.io/xDrip/docs/Dexcom/G7OnceAMinuteScan.html

Hopefully, this change in behavior in G7 with respect to G6 will not require too much change in xDrip or AAPS.

[Navid200]

After three consecutive missed handshakes (15 minutes), G7 moves into a once a minute transmission to help with the reconnect. This change of behavior with respect to G6 confused xDrip.
It was xDrip that screwed up the timestamps I am sorry about that. But, this is fixed now.

If you are using xDrip to collect from G7, please use the May 22, 2024 release or any after that. xDrip does not change the timestap any more under those conditions.

Every G7 (or G6) has a local free running oscillator. There is no timing relationship, neither phase nor frequency, between the local oscillators of different G7 devices. Every time you start using a new G7, xDrip will adapt to its local oscillator. Therefore, there will always be a shift in the tine stamp when starting a new G7. There is nothing we can do to xDrip to change this behavior.

If you think there is anything else we can do, please let me know.

[TWilhoWI]

Hi Navid, Don't know if it is related, but got a couple of connection issues after upgrade. This is also a new sensor.

[Navid200]

Looking at the logs you are showing, I can only see a calibration attempt.

You can calibrate if you need to. I personally don't recommend calibrating a G6 or G7.
There will be a hell of a lot of communication attempts between G7 and xDrip after a calibration and some of it fails and that's why you see those logs. Just ignore them.

[TWilhoWI]

Ow so the unknown packet is to be neglected?

[TWilhoWI]

Still frequent connection drops. Do I need to provide more logs?

[TWilhoWI]

Extra info.

[TWilhoWI]

[Navid200]

@TWilhoWI None of what you are reporting is related to AAPS. This is the AAPS repository.

[TWilhoWI]

Dammit, will repost it in G7 forum. Sorry