-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
MDT 523 Insulin Delivery Display Mismatch #2137
Comments
I confirm this behavior with Loop 3.2.3 and a MDT 515 pump. Configuration:
Test Details:
|
I confirm that the display is incorrect with dev as well. Configuration:
Test Details:
|
Conclusion: Display on MDT Pump screen shows the value initially exchanged with pump and is not updated when Therapy Settings are changed in Loop. Next test (same dev configuration as above). Test Details:
Also confirmed that the Loop Report indicates scheduled basal equivalent to pump and to therapy setting. |
This issue is stale because it has been open for 30 days with no activity. |
Bump |
This was fixed with the release of Loop 3.4. |
Describe the bug
I'm on steroids so I have increased my basal rate across the board. I updated my basal rates through the Loop interface and they appear to be written to the pump;however, there is a mismatch between the Insulin Delivery display and the actual current basal. Currently, my basal is set at 1.4 U/hr (12 AM-12PM) but the display reads as Scheduled Basal 0.7 U/hr. This is interesting because that is my typical basal rate without steroids. It is also the last basal rate that I likely entered manually into the pump and not via Loop's interface, although guessing a little here.
Attach an Issue Report
I'm happy to email the Issue Report--my github app keeps crashing
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I'd expect the Scheduled Basal display to match what is in Therapy Settings and what shows on the pump
Screenshots
Phone
Loop Version
?
CGM
Pump
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: