[bjorkert]

When no temp basal is running, the Basal row shows the scheduled rate at the current time, and the basal graph from the end of the last temp basal follows the schedule in the profile time zone, stepping at each schedule entry, at midnight and across daylight saving changes.

Before and after, with the last temp basal ending at 08:50 and the schedule changing from 0.65 to 0.5 at 08:55:

[oddst]

A little wish is that a check is also done to verify if insulin suspend delivery is on or not...! Or that the pod might be physically out of insulin...! This is something that I believe that both Trio and Loop both suffer with...!

[bjorkert]

A little wish is that a check is also done to verify if insulin suspend delivery is on or not...! Or that the pod might be physically out of insulin...! This is something that I believe that both Trio and Loop both suffer with...!

Thanks, I'm looking into this in a separate mr to avoid scope creep.

[dnzxy]

A little wish is that a check is also done to verify if insulin suspend delivery is on or not...! Or that the pod might be physically out of insulin...! This is something that I believe that both Trio and Loop both suffer with...!

That goes entirely contrary to how pump
managers interact with pumps and report pump
status.

[bjorkert]

Tested end to end in the simulator: Trio (dev) in open loop with MedtrumKit against a simulated Medtrum Nano, a basal schedule of 0.8 U/h, 0.4 from 21:00, 0.6 from 21:30 and 0.8 from 22:00, and LoopFollow on this branch following the Nightscout Trio uploaded to.

The last temp basal ended at 20:57. At 21:01 the Basal row showed 0,4 and the graph follows the schedule after the temp basal, stepping from 0.8 to 0.4 at 21:00. The suspend at 20:36 to 20:48 is drawn at the scheduled rate here because this branch doesn't include #800.