And again, you get at least 8 hours of history graphed on the display now. If it doesn't look sensible (w.r.t eating and insulin doses), you need a backup. If the old fashioned blood glucose meter gives a wrong reading, you are much worse off.
Note that the sensors are tested and approved, not the DIY hack the article talks about.
And the danger of “fully automatic” is there.
A sensor failure in closed loop is dangerous. I do not know how the control software detects and deals with this. I have no experience with them.
The new oref1 algorithm uses a method called super micro boluses, which can detect a sudden peak or unannounced meal, sees the first jump up, gives you a bolus so it borrows from the basals, setting the basals to 0%. The algorithm works really well for things such as eating a pizza, where you get about 50% of the carbs immediately and the rest + a bit more during the next five hours. So you take a bolus for the food, then when the fat hits in the oref1 will give you tiny boluses.
The latter is more sensitive to sensor failures, so it is on only when you told the system you have some carbs in your body, or if you happen to have a Dexcom G5 or G6 sensor with good noise readings, it will be on all the time and the system knows when the reading is faulty.
https://forum.fudiabetes.org/t/dexcom-out-of-range-calibrati...
The sensors are big things with the needle permanently in your body. You don't want three needles permanently to be sure that at least 2 from 3 work. If you have only one, you have a real problem if you trust it blindly.
Yes, it's good that some people try. But there are real risks, due to the current limitations as explained.
I know that most of the population is actually not technical, and that they can easily understand “correct when high, eat when low” but complex technical reasoning can’t be expected from them. In that context, sensors not functioning as in ideal lab conditions is a big issue.
As a type1 you must have a lot of knowledge to be able to survive. The software is a tool you must learn how to use, but takes away lots of burden from the decision making.
What happens when the sensor is not reading correctly? Isn’t that the biggest possible danger? The human “knows” it’s wrong but software?