Skip to content

max_iob stuck at 0 (after disabling dynISF) #5598

Open

Description

@jaapboon

Reporting bugs

After toggling off dynamicISF at 30-oct due to repeated hypos, the max_iob setting is stuck at 0. I only noticed it recently after several nights where my loop did not bolus or increase basal whilst having high BG. The issue is there since 31-oct until now. I can verify in nightscout that before 30-oct I did not have this issue. I completed all the objectives years ago. No automations / temp targets active at the moment. AAPS version 3.4.0.0.

Sensor = dexcom g7 via BYODA, exponential smoothing enabled.
Pump = medtrum nano 200U

I have open loop enabled, no duplicate BG readings, no pop-up of noisy BG readings.
I tried (all did not work, in chronological order):

  • switching between and forth closed loop / open loop
  • re-enabling dynamicISF, disabling it again after a day because this did not work
  • checking openAPS SMB settings; max IOB was set to 22 U nothing seems to block it
  • restarting phone / bluetooth
  • switching between openAPS SMB -> openAPS AMA -> openAPS SMB
  • importing old settings from before 30-oct
  • re-activating profile
  • reset finished state of objective 7 (cannot re-activate it now bacause "max iob set properly is not completed yet"

At this point the only solutions l can think of are updating androidAPS to 4.0.0 and hope this solves it, or deleting AAPS, reinstalling and importing the old backup. Both I don't want to do today because my pump still has two days remaining.

openaps constraints openaps max iob 0

AndroidAPS_LOG_1794908980156.log.zip

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions