I started testing unannounced meals in Android APS on Saturday 30 July 2022. I am a bit of a control freak and really couldn’t believe that a system could manage my diabetes better than I could. I had more information available to me to make more informative decisions “I would tell myself”. But I seem to be wrong, well at least partly. I am using a branch of AAPS that delivers insulin early, but I found that managing protein and fat was more problematic than carbs seemed to be. Stubborn high blood sugar that seemed to take a few hours to correct. So I decided to do a little testing with automatons to try and improve those numbers.
Announcing carbs and pre-bolusing
Eerm…what? How is this possible? It seems with accurate carb counting I still cant account for digestion times as well as AAPS can.
Automations
I use two (2) automations to try and manage my readings more closely. These automations are over and above the Boost logic that provides insulin earlier than the standard code.
The first automation simply sets a lower target when my reading is above 7.8 mmol/l AND not dropping. This allows AAPS to bring down my readings more quickly.
The second is to try and compensate for protein and fat in the low carb meals I eat. This automation will activate if
- my reading is above 6.5 mmol/l AND
- between meal times AND
- my reading isn’t dropping AND
- there is active resistance detected (not sure if this even matters)
My hypothesis is that the system can detect the resistance post the meal window but I need to test this assertion further.
Dick The Diabetic's APS Adventures 