Failed remote carb/bolus about loop HOT 3 OPEN

Export-20240604T135205Z.zip

from loop.

Summary:

The remote commands did not go through - that happens sometimes.

Instead of repeating remote commands quickly:

• If the first one does not show up on Nightscout, wait at least 5 minutes before trying again
• Always send Bolus first.
  • Follow up with Carb entry later to prevent the app staying at 0 U/hr. (One cycle won't make much difference.)

Analysis:

Time zone is -7 hours wrt UTC.
So an event at 1:40 am (1:43 on phone at 3 minutes ago) yesterday is 08:40 UTC June 3, 2024.
Before that, I see a number of entries in the notification about remote entries:

List in chronological order (apprx UTC, time ago, what) from phone time of 1:43 pm):

• 2024-06-03T08:33, 10 m ago, Remote Carb Entry: 10 g x 6 hours
• 2024-06-03T08:35, 8 m ago, Remote Bolus: 0.3 U
• 2024-06-03T08:36, 7 m ago, Remote Carb Entry: 15 g x 6 hours
• 2024-06-03T08:37, 6 m ago, Remote Bolus: 0.4 U
• 2024-06-03T08:40, 3 m ago, Remote Bolus: 0.3 U (Mom)
• 2024-06-03T08:40, 3 m ago, bolus in progress

Before I go any farther - please always send the remote bolus FIRST and then follow up with the remote carbs to go with it.

• https://loopkit.github.io/loopdocs/nightscout/remote-commands/#remote-bolus-then-remote-carb

All I can tell you is that none of these were enacted. (Which you already knew).

I examined the critical logs:

• (from carbs.json): None of those remote carbs were accepted by Loop.
• (from doses.json): The only dosing entries during this time were automatic and they match the amounts reported in the event history for bolus (the temp basal entries at top level show the rates, not the delivered dose, which for these cases as 0 U.)

from loop.

Thank you, appreciate your time.

from loop.