Closed RafaelBomfim128 closed 2 months ago
Apparently, the problem is in a disabled setting (I didn't notice when it was changed, probably accidental) in the additional xDrip sending settings for Nightscout. I noticed it when installing xDrip on an Android simulator and seeing the default sending settings for Nightscout. Thank you and sorry for any inconvenience!
Describe the bug Sensor age information updated in x-Drip, but outdated in Nightscout.
To Reproduce I'm not sure what caused this bug, it just stopped sending sensor age information to Nightscout for no apparent reason.
Expected behavior It is expected that sensor age information will be updated correctly in Nightscout with each sensor change.
Screenshots NOTE: I apologize for the Portuguese language in the screenshots.
![Print 4](https://github.com/nightscout/cgm-remote-monitor/assets/49501710/f45874ff-e40a-486e-85b9-fdfed9a8fb76)
Your setup information
What version of Nightscout (e.g. 0.10.3) R: 14.2.6
What type of CGM, and how do you get your data there? (e.g. G4 and ShareBridge, or wired receiver, etc.) R: Freestyle Libre 1 (14 days) with MiaoMiao 2
Is your issue specific to a browser (Firefox/Safari/Chrome?) or a device (Android phone, etc.)? R: I'm using the Moto G82 as an uploader.
Additional context Things I've already tried: Restarting the device (cell phone), disabling and activating sending to Nightscout again and changing the settings. Could it be some configuration when sending data to Nightscout? How could I debug better?
Why this is important to me: I'm creating an open source application for Windows that will read Nightscout's blood glucose levels and display them, similar to FloatingGlucose (currently archived), but with features such as: Sensor expiration alerts when it gets close to 14 days. I intend to read this information from the following path: /api/v2/properties/sage