And the controller would beep if communication were lost.
There would not be an Internet API to change any parameters at all.
And the controller would beep if communication were lost.
There would not be an Internet API to change any parameters at all.
Your solution is surely better, but the current one exists.
Users have to be able to input when they're eating carbs. It's possible to do that through the pump (that's how I do it), but there are some ways in which that's not ideal. Most people enter carbs through the webapp. This is capable of creating a dangerous situation for the user (not of killing them). It's a security risk, but also a practical necessity.
Some peoples' setups are more internet dependent than that, though. For certain models of CGM, the way you get data from them is by giving them an internet connection and using a web API provided by the CGM maker. (This is built on abusing APIs that were intended for eg family members monitoring glucose values of children who might not be close by.) And, in the case of Loop, the decision algorithm executes on a phone.
These setups aren't ideal, but they're all made by hackers with limited time and resources desperate to get something that works, because the market isn't providing anything acceptable.
I’m not diabetic, so I’m probably missing something, but why? I would have expected the CGM to detect the extra glucose quickly enough without any extra input from the user. Kind of like how people with pacemakers don’t have to tell the pacemaker before they start jogging.
The lack of communication is a bit of a downside for people who are used to monitoring their levels on smartwatch, but overall the auto-mode features more than make up for that.