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

Pump loop connection does not return #2231

Open
HaniaMierzwiak opened this issue Sep 25, 2024 · 2 comments
Open

Pump loop connection does not return #2231

HaniaMierzwiak opened this issue Sep 25, 2024 · 2 comments

Comments

@HaniaMierzwiak
Copy link

Loop Report 2024-09-25 21_09_34+02_00.md
Hello
Describe the bug
An error occurs when the loop crashes the glucose level data after 15 minutes. After the return of the glucose data, the loop does not return to work. You need to open the application and wait a while until it catches the signal
Attach an Issue Report
Tap the Loop settings icon on the bottom of the screen, then tap Issue Report and attach it to this ticket.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
If the glucose signal returns, the loop shold take up the work itself

Screenshots
If applicable, add screenshots to help explain your problem.
picture 1
picture 2

Phone

  • Hardware: [e.g. iPhone XS]
    Iphone 15

  • OS Version: [e.g. iOS 12.0.1]
    IOS 17.6.1
    Loop Version

  • Version Number: [e.g. 1.9.2] Loop 3.4.1 (3)

  • Repo: [LoopKit/Loop, Katie, etc] LoopKit

CGM

  • Device: [e.g. Dexcom G6] Nightscout
  • Manager app: [e.g. Dexcom App, Spike]

Pump

  • Manufacturer: [e.g. Medtronic] OmnipodDash
  • Model: [e.g. 723]
  • Firmware version: [e.g. 2.3A 1.1 0B 0B]

Additional context
Add any other context about the problem here.

@marionbarker
Copy link
Contributor

You are using Nightscout as a CGM. There is no way that can wake up the Loop app. So having a new glucose entry is irrelevant.

Instead you rely on the pump (DASH) to wake up the app. But if your pump does not connect (for whatever reason), Loop will not wake up and will not try to Loop.

I don't know why you are getting long times between pod connections. Perhaps the pod is out of range when Loop tries to connect.

For example, notice the big time gap in adjacent entries in your loop report. (There are no errors).

* 2024-09-25 06:56:50 +0000 Omnipod-Dash 17F8D82B receive 17f8d82b240a1d180050200000015bff815a
* 2024-09-25 10:32:03 +0000 Omnipod-Dash 17F8D82B connection Pod connected F82E6BB5-CC35-F369-A5EC-049B42235339

Tagging @itsmojo, but not sure he will have anything different to say.

Make sure there is not bluetooth interference - are games being played or videos watched or bluetooth headphones used?
If you have a bunch of Bluetooth items (look under iOS Settings, Bluetooth) that do not need to be there, try to remove them. Make sure you do not remove "TWI Board". That is your DASH pump.

Please close this issue and if you continue to have trouble, reach out on zulipchat or Facebook instead.

All the information posted remains available on GitHub, the issue simple gets moved to the closed tag and doesn't take up the time or attention of developers. You can continue to exchange messages or link to this issue to get help even after it it closed.

@HaniaMierzwiak
Copy link
Author

Thank you marionbarker #@itsmojo
The only device connected to the phone via Bluetooth is libre2 and Loop. I have no interference, I don't play games. Libra, if it loses range, will connect itself. Loop, if it loses range, will not connect itself. I have to open the application and only after a while will it catch the signal :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants