[bjorkert]

Trio running in open loop uploads devicestatus with dosingMode "open" and only a suggested block, no iob and no enacted, and no Temp Basal treatments are created. LoopFollow therefore showed IOB and Basal as a dash for those users. IOB now falls back to suggested.IOB (or enacted.IOB), and when there are no temp basals the Basal row shows the scheduled basal from the profile.

The loop status next to the forecast shows ⏀ when Trio reports dosingMode "open", and for Loop when the profile's loopSettings.dosingEnabled is false (Loop's Closed Loop toggle). The existing Loop check on recommendedTempBasal stays for older Loop versions; Loop 3 does not upload that field.

Trio in open loop (left) and Loop with Closed Loop off (right):

[bjorkert]

Tested end to end in the simulator: Trio (dev) switched to open loop, with MedtrumKit against a simulated Medtrum Nano, and LoopFollow on this branch following the Nightscout Trio uploaded to.

The loop status shows ⏀. Trio dev uploads openaps.iob in open loop as well, so IOB came from iob and the fallback to suggested.IOB wasn't exercised. With no temp basals in Nightscout the Basal row shows the scheduled 0,4 (left).

Right after switching from closed loop the earlier temp basals are still in Nightscout, and on this branch alone the Basal row keeps the scheduled rate from when the last temp basal ended: 0,4 → 0,8 at 21:02, after the schedule stepped to 0.4 at 21:00 (right). #799 fixes that, so the two fit well in the same release, but neither is critical on its own.