AndroidAPS
AndroidAPS copied to clipboard
nightscout
Enable SMB always while using xdrip in companion app mode and dexcom g7 original app
When using xdrip (latest nightly) in companion app mode fetching bg values from dexcom g7 app, aaps (3.2.0.3) still won't allow SMB to be enabled always. Please fix so that g7 users can use latest dexcom g7 app including clarity and still have hcl/fcl possibility in aaps.
Problem is that xDrip doesn't send which sensor the data comes from in companion app mode., so AAPS can't determine if it is data from G7 or e.g. a medtronic sensor So we need this information from xDrip when we want to enable it for ONE/G7 companion mode, I suggest you open a discussion/issue over at xDrip as well.
Thank you. I understand. I have posted this on xdrip repo: https://github.com/NightscoutFoundation/xDrip/discussions/3396
Though, why isn't AAPS enabling SMB always no matter which BG source xdrip is using? AFAIK, xDrip companion mode is available for the following vendor apps: G6 (master only) One (only if the app shows BG notifications) G7 (master only) CamAPS Guardian MiniMed Omnipod 5 app
Is any one of these apps a problem for always SMB in AAPS or why can't AAPS just enable it for the xdrip companion mode? But perhaps I'm misunderstanding something :)
Though, why isn't AAPS enabling SMB always no matter which BG source xdrip is using? AFAIK, xDrip companion mode is available for the following vendor apps: G6 (master only) One (only if the app shows BG notifications) G7 (master only) CamAPS Guardian MiniMed Omnipod 5 app
For Dexcom we know that they have good filtering, meaning that when there are erroneous values the sensor/transmitter doesn't send them. For the others we don't know
Why no mandatory smoothing (average/exponential) then when using xdrip companion data?
Why no mandatory smoothing (average/exponential) then when using xdrip companion data?
Dexcom does error detection, meaning it will not send data when there are erroneous values., with smoothing only there will still be a datapoint on the erroneous value, which can lead to wrong dosing. But this is already being discussed in other issues as well: https://github.com/nightscout/AndroidAPS/issues/3181 https://github.com/nightscout/AndroidAPS/issues/2121 https://github.com/nightscout/AndroidAPS/issues/2354
Can anyone provide current state?
@MilosKozak I tested it today on AAPS 3.3.0-dev-d (Build 986125e7e8) and now it seems to work! Closed loop possible even with xdrip companion app, nice!