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

Trio will not finish loop due to incorrect user configuration and requires a restart #448

Open
yodax opened this issue Dec 30, 2024 · 2 comments
Assignees
Labels
bug Something isn't working fixed in 1.0 long-term For later, doesn't get staled

Comments

@yodax
Copy link

yodax commented Dec 30, 2024

Describe the bug

When you configure them smallest SMB below 0.1 on a pump that does not support (my mistake, I thought the MDT722 could do 0.025 bolusses), all is well until a bolus < 0.1 is being tried.
This will not result in an error, but it will cause the Loop to be stuck on updating until Trio is restarted.

Attach a Log

See line 45106 in log.txt.
log.txt

To Reproduce

Steps to reproduce the behavior:

  1. Configure an incorrect minimal SMB size
  2. Wait until Trio wants to deliver a bolus of that size
  3. Trio is stuck on "updating"

Expected behavior

An error message that the bolus could not be delivered or a maximum time for a Loop perhaps

Screenshots

signal-2025-12-30-141511

Setup Information (please complete the following information):

Smartphone:

  • Hardware: iPhone SE
  • OS Version: iOS 17

Pump:

  • Manufacturer: Medtronic
  • Model: 722

CGM:

  • Device: G6
  • Manager app: Dexcom

Trio Version:

  • Version Number: 0.2.2
  • Repo: nightscout/trio
  • Git Reference: Main branch
@yodax yodax added bug Something isn't working needs-triage labels Dec 30, 2024
@Sjoerd-Bo3 Sjoerd-Bo3 added this to Trio Dec 30, 2024
@MikePlante1
Copy link
Contributor

In the upcoming v1.0, this setting is automatically set to match the pump, so this will no longer be an issue.

@yodax
Copy link
Author

yodax commented Dec 30, 2024

Good to hear! I’ll leave it to you if you want this open or closed since it’s fixed privately but not on this repo.

@Sjoerd-Bo3 Sjoerd-Bo3 added fixed in 1.0 long-term For later, doesn't get staled and removed needs-triage labels Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed in 1.0 long-term For later, doesn't get staled
Projects
Status: No status
Development

No branches or pull requests

3 participants