Nightscout “OpenAPS Offline” entry not cleared after re-enabling loop via AAPS Client - AAPS Client 3.3.3.0-dev-d

[gerison77]

Title: Nightscout “OpenAPS Offline” entry not cleared after re-enabling loop via AAPS Client

---

Description

Toggling the loop via the AAPS Client app creates an OTHER treatment in Nightscout marking OpenAPS Offline, but no corresponding entry is created to set the Loop back to "normal" Result: the grey “OpenAPS Offline” bar persists indefinitely (sometimes showing extreme durations, e.g. 4,085.78 years) until the entry is manually removed from the Nightscout database.

---

Steps to Reproduce

1. Use AAPS 3.3.3.0-dev-d .
2. Deactivate loop via AAPS Client app.
3. After a few minutes, re-enable the loop via Client.
4. In Nightscout:
   • An OTHER treatment “OpenAPS Offline” with runtime is present.
   • An OTHER` treatment “OpenAPS Offline” is present after reenabling the loop with not timestamp
   • No other event is logged when the loop is re-enabled.
   • The grey “Offline” bar persists with the initial (very long) duration.

---

Expected Behavior

• Log a “Loop re-enabled” / “OpenAPS Online” event; or
• Close/override the previous OpenAPS Offline entry when the loop is re-enabled.

---

Actual Behavior

• two single “OpenAPS Offline” (OTHER) treatments exists.
• No “OpenAPS Online” event is created/sent.
• The grey bar remains until the OTHER entry is manually deleted from the Nightscout DB.

---

Workaround

Manually delete the OTHER treatment entry from the Nightscout database.

Suggested Fix

When loop is re-enabled, AAPS should send a “Loop re-enabled” / “OpenAPS Online” event to Nightscout that closes or overrides the previous OpenAPS Offline entry.

---

/cc @psonnera @timbo007up @MilosKozak