You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our country (Argentina) we only have access (for now) to fsl 1 sensors. To warm up and calibrate a new sensor, I start it in xdrip variant and after 24 hours, and calibrations achieved, I disable the connection of the main xdrip+, and then I have Xdrip variant transmit to aaps and to nightscout. I cannot simply switch the new sensor from the variant to xdrip+, b/c I lose the calibration and thus the accuracy of the fsl1. I have to disable the connection of xdrip+ and enable the connection/transmission of xdrip variant.
We are using Xdrip+ e50dfdf-2023.05.03
and xDrip-plus-variant4-20230525-2e4954e.apk
We use a bubble and a miaomiao1 with fsl1 to upload BG data to Xdrip. Xdrip transmits to AAPS and NS.
Xiaomi Mi A4 lite phone, Android 10.
The complication for us with using the xdrip variant as a transmitter to AAPS and NS is that we lose our daughter's MiBand5 connection with the Xdrip variant. The Watch Drip app will only connect to the main Xdrip+. Also, for the AAPS version we use, we have to use the dev version 15 of NS, and there is (also) a bug there in that the BG display in nightscout has about 20 digits. Which means that the 2 weeks the sensor is on the xdrip variant, neither I nor my daughter can use our smartwatches to follow BGs. (On my fitbit, the 20+ BG display does not fit on the screen.)
If the calibrations could also be transferred from Xdrip variant to Xdrip+, we could simply transfer the connection in Xdrip+ from sensor 1 to sensor 2 when the 2nd sensor was warmed up, calibrated, and ready to go. And we'd both (my daughter and I) have smart watches showing BG data, and no issues with BG display via dev version of NS.
Might not be possible! But thanks so much for looking at it. Would be a big help. Looping with fsl1 is a challenge, but we're going on 3 years of making it happen. The hardest days are the sensor change days, and the variant really helps make the transition easier! But having to use the Xdrip variant for transmission has presented some other glitches we're trying to smooth out. And so, here we are. Thanks so much to Navid for creating the bridge to being able to open the issue. Fingers crossed it's something that can be done easily!
The text was updated successfully, but these errors were encountered:
Link to the discussion thread: #2859
In our country (Argentina) we only have access (for now) to fsl 1 sensors. To warm up and calibrate a new sensor, I start it in xdrip variant and after 24 hours, and calibrations achieved, I disable the connection of the main xdrip+, and then I have Xdrip variant transmit to aaps and to nightscout. I cannot simply switch the new sensor from the variant to xdrip+, b/c I lose the calibration and thus the accuracy of the fsl1. I have to disable the connection of xdrip+ and enable the connection/transmission of xdrip variant.
We are using Xdrip+ e50dfdf-2023.05.03
and xDrip-plus-variant4-20230525-2e4954e.apk
We use a bubble and a miaomiao1 with fsl1 to upload BG data to Xdrip. Xdrip transmits to AAPS and NS.
Xiaomi Mi A4 lite phone, Android 10.
The complication for us with using the xdrip variant as a transmitter to AAPS and NS is that we lose our daughter's MiBand5 connection with the Xdrip variant. The Watch Drip app will only connect to the main Xdrip+. Also, for the AAPS version we use, we have to use the dev version 15 of NS, and there is (also) a bug there in that the BG display in nightscout has about 20 digits. Which means that the 2 weeks the sensor is on the xdrip variant, neither I nor my daughter can use our smartwatches to follow BGs. (On my fitbit, the 20+ BG display does not fit on the screen.)
If the calibrations could also be transferred from Xdrip variant to Xdrip+, we could simply transfer the connection in Xdrip+ from sensor 1 to sensor 2 when the 2nd sensor was warmed up, calibrated, and ready to go. And we'd both (my daughter and I) have smart watches showing BG data, and no issues with BG display via dev version of NS.
Might not be possible! But thanks so much for looking at it. Would be a big help. Looping with fsl1 is a challenge, but we're going on 3 years of making it happen. The hardest days are the sensor change days, and the variant really helps make the transition easier! But having to use the Xdrip variant for transmission has presented some other glitches we're trying to smooth out. And so, here we are. Thanks so much to Navid for creating the bridge to being able to open the issue. Fingers crossed it's something that can be done easily!
The text was updated successfully, but these errors were encountered: