Scheduled basal rate not set correctly when adding pump

[scottf51]

Describe the bug

Scheduled basal rate not set correctly when adding pump on new install

Attach a Log

Tap the Trio settings icon at the bottom of the screen, then tap 'Share logs' on the bottom of the list and attach it to this ticket.

To Reproduce

Not sure if being a new install is relevant or triggers this bug but it was a new install ,from TestFlight , because if this CGM had just been added and it was open loop with no current pump

Steps to reproduce the behavior:

1. Add pump
2. Select Omnipod Dash
3. Follow onscreen prompts to setup pod
4. Check screen to view currently scheduled basal and observe it is 1u/hr and not my scheduled basal
5. Enable closed loop and force loop
6. observe the current basal has now changed
7. Checking in pump manager still showed 1u/hr as the scheduled basal, so I guess it would have reverted if I was away from my phone long enough

Shortly after I noticed this, in an attempt to force the settings to pump I updated my basal profile , saved , then changed it back and saved again, the pod beeped both times and then showed the correct scheduled basal (0.9u/hr) , although the main interface still showed previously running basal, forced loop again and this updated and pump went back to high temp basal to combat high

Expected behavior

Pump should start out with correct basal profiles after initial pod pairing per therapy settings

Screenshots

Setup Information (please complete the following information):

Smartphone:

• Hardware: iPhone SE 2022
• OS Version: iOS 26.0.1

Pump:

• Manufacturer: Insulet
• Model: * Omnipod Dash

CGM:

• Device: Dexcom one+
• Manager app: Dexcom app

Trio Version:

• Version Number: 0.6.0.3
• Repo: nightscout/trio (dev)
• Git Reference: 3ba02e0

Technical Details

No errors at all - was a bit scary that it was wrong, not by much but if it stayed like that any time I was away from my phone it would cause problems at some times of day

Additional context

Add any other context about the problem here.

[scottf51]

log 2.txt

log_prev 2.txt

[scottf51]

Looking at "pump manager details" now I see a list of basal entries in there under "basalSchedule" - I am 99.9% sure that was not there before , but I didn't export it , was just trying to force settings over.

Not sure how easy this will be to recreate, could be something to do with being a new install or having the loop open , they are the 2 things that seem likely different from most times people go through this process.

[scottf51]

also is this right ? I have temp basal max set in app at 4u/hr but pump manager shows 2u/hr - maybe these are talking about different things but thought it was worth noting

[scottf51]

After pod change rates appear to be set correctly right off the bat. No idea what was different about the first pod change to not set it

[dnzxy]

Closing this as a duplicate of #845, where thankfully @itsmojo also went ahead and debugged the issue further.

Thank you for the report.