Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot silence Omnipod low reservoir alarm on first pod #375

Open
g5WS opened this issue Aug 7, 2024 · 10 comments
Open

Cannot silence Omnipod low reservoir alarm on first pod #375

g5WS opened this issue Aug 7, 2024 · 10 comments
Labels
bug Something isn't working known issue Known issue with Trio or its submodules; possible duplicate

Comments

@g5WS
Copy link

g5WS commented Aug 7, 2024

Describe the bug

I'm on my first pod under Trio and have just passed the 10-unit-remaining mark. The pod is beeping intermittently, and I can't seem to silence it. I received no app pop-up or lock screen notification. I am running iOS18 (latest developer build)

This area of functionality does not seem to be described in the help files: https://docs.diy-trio.org/en/latest/search.html?q=%22Low+reservoir%22&check_keywords=yes&area=default

Attach a Log

*That's a lot of personal information... but here are some excerpts, and I'm happy to search and excerpt more if someone provides strings to search. Here are the first 3 log entries when the reservoir hits 10, and when it first goes below.

  • 2024-08-07T10:59:42-0700 [DeviceManager] DeviceDataManager.swift - pumpManager(:didReadReservoirValue:at:completion:) - 484 - DEV: Reservoir Value 10.0, at: 2024-08-07 17:59:42 +0000
    2024-08-07T10:59:53-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(
    :logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: 17364df508030e01000073
    2024-08-07T10:59:53-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: 17364df50c0a1d290551500008358cc80281

2024-08-07T11:04:24-0700 [DeviceManager] DeviceDataManager.swift - pumpManager(:didReadReservoirValue:at:completion:) - 484 - DEV: Reservoir Value 9.85, at: 2024-08-07 18:04:24 +0000
2024-08-07T11:05:08-0700 [DeviceManager] PluginSource.swift - deviceManager(
:logEventForDeviceIdentifier:type:message:completion:) - 86 - DEV: device Manager for Optional("83QR80") : Connected
2024-08-07T11:05:09-0700 [DeviceManager] PluginSource.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 86 - DEV: device Manager for Optional("83QR80") : New reading: 2024-08-07 18:04:55 +0000*

To Reproduce

Unknown reproducibility

Expected behavior

Acceptable: in-app notification that allows reminder to be silenced
Ideally: lock screen notification that allows reminder to be silenced and in-app notification that allows reminder to be silenced.
Stretch goal: pod does not beep when user is sleeping if it has enough insulin to carry you through the night. :-)

Screenshots

N/A

Setup Information (please complete the following information):

Smartphone:

  • Hardware: iPhone 15 Plus
  • OS Version: iOS 18.0 developer beta (22A5326f)

Pump:

  • Manufacturer: Insulet
  • Model: Omnipod Dash

CGM:

  • Device: Dexcom G6
  • Manager app: xDrip4iOS

Trio Version:

  • Version Number: 0.2.0 branch dev 4f080cf
  • Repo: nightscout/trio

Technical Details

It's my first pod. I did subsequently receive the 12-hour warning notification in the UI. Using the 'make a sound on my pod' feature also did not silence the alarm

Additional context

N/A

@g5WS g5WS added bug Something isn't working needs-triage labels Aug 7, 2024
@Sjoerd-Bo3 Sjoerd-Bo3 added this to Trio Aug 7, 2024
@marionbarker
Copy link
Contributor

I've heard this happens for iAPS / Trio for the first pod only. Not sure if that is true or not.

Please post these files:

Here's a couple of things to post:

Pod->Pod Diagnostics-> read triggered alerts and post the screenshot (or text) you see.

Pod->Pod Diagnostics -> Pump Manager Details hit the share button add the file here.

Not sure if any of this will be helpful. Tagging @itsmojo to look at it.

make it stop:

You have some options.
Pod -> Notifications -> Silence Pod -> enable
But if you want notifications, that turns them all off.

What used to work for Loop (not sure it works for Trio) was to quit the app and restart the app. When it restarts, it reads the triggered alert and puts up a notification. Be sure to do the read triggered alerts step first.

@g5WS
Copy link
Author

g5WS commented Aug 7, 2024

Thanks, Marion.

Triggered alerts (after hitting the 'Read Triggered Alerts' button):

slot0AutoOff:
slot1NotUsed:
slot2ShutdownImminent:
slot3ExpirationReminder: slot4LowReservoir: 57h6m
slot5SuspendedReminder:
slot6SuspendTimeExpired:
slot7Expired:

Here's a lightly redacted log:

  • scheduledExpirationReminderOffset: Optional ("12h")
  • defaultExpirationReminderOffset: 12h
  • 1owReservoirReminderValue: 10.0
  • podAttachmentConfirmed: true
  • activeAlerts: [OmniBLE.PumpManagerAlert.lowReservoir(triggeringSlot : Optional (OmniBLE.AlertSlot.slot4LowReserv
    oir), lowReservoirReminderValue: 10.0)]
  • alertsWithPendingAcknowledgment: []
  • acknowledgedTimeOffsetAlert: false
  • initialConfigurationCompleted: true

Pump Manager Details:

OmniBLEPumpManager

provideHeartbeat: false
connected: true

podComms: ## PodComms
[…]
delegate: true

statusObservers.count: 2
status: ## PumpManagerStatus

  • timeZone: GMT (-25200)
  • device: <<HKDevice: 0x3037607d0>, name:Omnipod-Dash, manufacturer:Insulet, model:Dash, hardware:4, firmware:4.10.0 1.4.0, software:1.0, localIdentifier:17364DF5>
  • pumpBatteryChargeRemaining: nil
  • […]
  • bolusState: noBolus
  • insulinType: Optional(LoopKit.InsulinType.novolog)
  • deliveryIsUncertain: false

podStateObservers.count: 1
state: ## OmniBLEPumpManagerState

  • isOnboarded: true

  • timeZone: GMT (-25200)

  • basalSchedule:
    […]

  • unstoredDoses: []

  • suspendEngageState: stable

  • bolusEngageState: stable

  • tempBasalEngageState: stable

  • lastPumpDataReportDate: Optional(2024-08-07 22:55:17 +0000)

  • isPumpDataStale: false

  • silencePod: false

  • confirmationBeeps: silent

  • controllerId: […]

  • podId: […]

  • insulinType: […]

  • scheduledExpirationReminderOffset: Optional("12h")

  • defaultExpirationReminderOffset: 12h

  • lowReservoirReminderValue: 10.0

  • podAttachmentConfirmed: true

  • activeAlerts: [OmniBLE.PumpManagerAlert.lowReservoir(triggeringSlot: Optional(OmniBLE.AlertSlot.slot4LowReservoir), lowReservoirReminderValue: 10.0)]

  • alertsWithPendingAcknowledgment: []

  • acknowledgedTimeOffsetAlert: false

  • initialConfigurationCompleted: true

  • PodState: ### PodState

  • address: […]

  • bleIdentifier: […]

  • activatedAt: Optional(2024-08-05 08:53:15 +0000)

  • expiresAt: Optional(2024-08-08 08:52:47 +0000)

  • podTime: 62h2m

  • podTimeUpdated: Optional(2024-08-07 22:55:17 +0000)

  • setupUnitsDelivered: Optional(2.8)

  • firmwareVersion: 4.10.0

  • bleFirmwareVersion: 1.4.0

  • lotNo: 139944754

  • lotSeq: 3090563

  • suspendState: resumed(2024-08-07 22:50:16 +0000)

  • unacknowledgedCommand: nil

  • unfinalizedBolus: Optional(Bolus: 0.1U 2024-08-07, 3:55:17 PM 4 seconds Certain)

  • unfinalizedTempBasal: Optional([…])

  • unfinalizedSuspend: nil

  • unfinalizedResume: nil

  • finalizedDoses: []

  • activeAlertsSlots: Low reservoir

  • messageTransportState: ## MessageTransportState
    eapSeq: 1059
    msgSeq: 23
    nonceSeq: 30
    messageNumber: 6

  • setupProgress: completed

  • primeFinishTime: Optional(2024-08-05 08:54:10 +0000)

  • configuredAlerts: Pod expired @ 72h, Expiration reminder @ 60h, Low reservoir @ 10U, Shutdown imminent @ 79h

  • insulinType: novolog

  • pdmRef: nil

  • Fault: nil

  • PreviousPodState: nil

I killed the app, and noticed it was at "!! No insulin" when I reloaded it. I am committed to my bug reports, so I decided to wait it out. :)

Eventually, I received notification on the lock screen and the app's "Error - Insulin delivery stopped. Change Pod now." red box pop up, but there was no way to silence the pod's screaming other than deactivating it.

@g5WS
Copy link
Author

g5WS commented Aug 10, 2024

I deliberately under filled my current pod to check this a little more quickly - I did receive the 10u popup both on my lock screen and in app. Tapping the in-app popup silenced the alarm.

@Sjoerd-Bo3
Copy link
Contributor

I deliberately under filled my current pod to check this a little more quickly - I did receive the 10u popup both on my lock screen and in app. Tapping the in-app popup silenced the alarm.

So that means it is fixed for you?

@g5WS
Copy link
Author

g5WS commented Aug 10, 2024

n=2. :) I don’t know if that’s enough to declare it fixed.

Sounded like Marion has seen this bug before and it may affect others. May be worth looking into.

@marionbarker
Copy link
Contributor

My understanding is this has been a first pod bug for iAPS from the beginning. I have never used iAPS or Trio myself. It does not happen with Loop. It does not happen with subsequent pods. I expect a lot of people will be getting this when switching to Trio.

The enable Silence Pod followed by disable Silence Pod clears the alert. One suggestion is set alert to 1 U for at least the first pod to limit likelihood of even having the problem.

This issue should probably stay open until someone figures it out. It is not an iOS 18 problem. Hard to track down. I don’t think the rPi DASH simulator has the right interface for testing.

@Sjoerd-Bo3
Copy link
Contributor

Yeah this is a known issue for the first pod indeed but that means that @g5WS also had this. And not another bug.

@Sjoerd-Bo3
Copy link
Contributor

But lets rename this issue to: First Pod …..

@g5WS
Copy link
Author

g5WS commented Aug 13, 2024

Third pod to hit 10 units. I was watching a full-screen video at the time.

  • Checked the lock screen, and observed no iOS notifications
  • Opened the app and did not receive a low reservoir pop up.

Noticed that my sensor was 2 minutes from a fresh reading, and decided to wait it out to see if an update would trigger anything. Decided to keep the app in the foreground for 2-3 minutes.

Waited 30-60 seconds, and then the in-app pop up and iOS notification banner appeared appropriately simultaneously.

It is possible that this technique could have worked on the first pod, too.

@dnzxy dnzxy changed the title No UI to silence Omnipod low reservoir alarm on iOS 18 Cannot silence Omnipod low reservoir alarm on first pod Aug 18, 2024
@dnzxy dnzxy added known issue Known issue with Trio or its submodules; possible duplicate and removed needs-triage labels Aug 18, 2024
@g5WS
Copy link
Author

g5WS commented Aug 26, 2024

I have experienced another long delay again between Omnipod low-volume beeping and UI appearing to silence.

Context: overnight. I was asleep and not interacting with my phone.

Log juicy bits:


2024-08-26T04:32:06-0700 [DeviceManager] PluginSource.swift - readCGMResult(readingResult:) - 173 - DEV: PLUGIN CGM - Process CGM Reading Result launched with noData
2024-08-26T04:33:06-0700 [Nightscout] FetchGlucoseManager.swift - subscribe() - 267 - DEV: FetchGlucoseManager timer heartbeat
2024-08-26T04:33:06-0700 [Nightscout] FetchTreatmentsManager.swift - subscribe() - 26 - DEV: FetchTreatmentsManager heartbeat
2024-08-26T04:33:06-0700 [Nightscout] FetchTreatmentsManager.swift - subscribe() - 27 - DEV: Start fetching carbs and temptargets
2024-08-26T04:33:06-0700 [DeviceManager] PluginSource.swift - readCGMResult(readingResult:) - 173 - DEV: PLUGIN CGM - Process CGM Reading Result launched with noData
2024-08-26T04:34:06-0700 [Nightscout] FetchGlucoseManager.swift - subscribe() - 267 - DEV: FetchGlucoseManager timer heartbeat
2024-08-26T04:34:06-0700 [Nightscout] FetchTreatmentsManager.swift - subscribe() - 26 - DEV: FetchTreatmentsManager heartbeat
2024-08-26T04:34:06-0700 [Nightscout] FetchTreatmentsManager.swift - subscribe() - 27 - DEV: Start fetching carbs and temptargets
2024-08-26T04:34:06-0700 [DeviceManager] PluginSource.swift - readCGMResult(readingResult:) - 173 - DEV: PLUGIN CGM - Process CGM Reading Result launched with noData
2024-08-26T04:34:38-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: Pod disconnected A2FF20C9-DA4D-7426-202C-06DECBFB07C5 Optional(Error Domain=CBErrorDomain Code=7 "The specified device has disconnected from us." UserInfo={NSLocalizedDescription=The specified device has disconnected from us.})
2024-08-26T04:34:39-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: Pod connected A2FF20C9-DA4D-7426-202C-06DECBFB07C5
2024-08-26T04:34:39-0700 [DeviceManager] DeviceDataManager.swift - pumpManager(_:didUpdate:oldStatus:) - 347 - DEV: New pump status Bolus: noBolus
2024-08-26T04:34:39-0700 [DeviceManager] DeviceDataManager.swift - pumpManager(_:didUpdate:oldStatus:) - 348 - DEV: New pump status Basal: Optional(LoopKit.PumpManagerStatus.BasalDeliveryState.tempBasal(LoopKit.DoseEntry(type: LoopKit.DoseType.tempBasal, startDate: 2024-08-26 11:31:39 +0000, endDate: 2024-08-26 12:01:39 +0000, value: 0.15, unit: LoopKit.DoseUnit.unitsPerHour, deliveredUnits: nil, description: nil, insulinType: Optional(LoopKit.InsulinType.novolog), automatic: Optional(true), manuallyEntered: false, syncIdentifier: nil, isMutable: true, wasProgrammedByPumpUI: false, scheduledBasalRate: nil)))
2024-08-26T04:34:40-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: 17364df708030e010082e8
2024-08-26T04:34:40-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: 17364df70c0a1d290508800008279cc780e0`
> 2024-08-26T04:34:40-0700 [DeviceManager] DeviceDataManager.swift - pumpManager(_:didReadReservoirValue:at:completion:) - 484 - DEV: Reservoir Value 9.95, at: 2024-08-26 11:34:40 +0000`
2024-08-26T04:34:40-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: 17364df710071105494e532e10805f
2024-08-26T04:34:40-0700 [Service] UserNotificationsManager.swift - ensureCanSendNotification(_:) - 319 - DEV: Sending notification was allowed
2024-08-26T04:34:41-0700 [DeviceManager] DeviceDataManager.swift - deviceManager(_:logEventForDeviceIdentifier:type:message:completion:) - 562 - DEV: Device message: 17364df7140a1d290508a00000279cc700fa
2024-08-26T04:34:41-0700 [Service] UserNotificationsManager.swift - addRequest(identifier:content:deleteOld:trigger:) - 347 - DEV: Sending pumpNotification notification
2024-08-26T04:34:49-0700 [Default] FreeAPSApp.swift - body - 71 - DEV: APPLICATION PHASE: inactive
2024-08-26T04:34:49-0700 [Default] FreeAPSApp.swift - body - 71 - DEV: APPLICATION PHASE: background
2024-08-26T04:34:58-0700 [Service] HealthKitManager.swift - createBGObserver() - 368 - DEV: Execute HealthKit observer query for loading increment samples
2024-08-26T04:34:58-0700 [Service] HealthKitManager.swift - createBGObserver() - 375 - DEV: Create increment query
2024-08-26T04:34:58-0700 [Default] FreeAPSApp.swift - body - 71 - DEV: APPLICATION PHASE: inactive
2024-08-26T04:34:59-0700 [Service] HealthKitManager.swift - getBloodGlucoseHKQuery(predicate:) - 456 - DEV: AnchoredQuery did execute
2024-08-26T04:34:59-0700 [Default] FreeAPSApp.swift - body - 71 - DEV: APPLICATION PHASE: active
2024-08-26T04:35:06-0700 [Nightscout] FetchGlucoseManager.swift - subscribe() - 267 - DEV: FetchGlucoseManager timer heartbeat
2024-08-26T04:35:06-0700 [Nightscout] FetchTreatmentsManager.swift - subscribe() - 26 - DEV: FetchTreatmentsManager heartbeat
2024-08-26T04:35:06-0700 [Nightscout] FetchTreatmentsManager.swift - subscribe() - 27 - DEV: Start fetching carbs and temptargets
2024-08-26T04:35:06-0700 [DeviceManager] PluginSource.swift - readCGMResult(readingResult:) - 173 - DEV: PLUGIN CGM - Process CGM Reading Result launched with noData```

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working known issue Known issue with Trio or its submodules; possible duplicate
Projects
Status: No status
Development

No branches or pull requests

4 participants