-
Notifications
You must be signed in to change notification settings - Fork 555
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
Comments
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. 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. |
Thanks, Marion. Triggered alerts (after hitting the 'Read Triggered Alerts' button): slot0AutoOff: Here's a lightly redacted log:
Pump Manager Details: OmniBLEPumpManagerprovideHeartbeat: false podComms: ## PodComms statusObservers.count: 2
podStateObservers.count: 1
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. |
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? |
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. |
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. |
Yeah this is a known issue for the first pod indeed but that means that @g5WS also had this. And not another bug. |
But lets rename this issue to: First Pod ….. |
Third pod to hit 10 units. I was watching a full-screen video at the time.
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. |
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:
|
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: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:
Pump:
CGM:
Trio Version:
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
The text was updated successfully, but these errors were encountered: