vanelsberg
commented
2 years ago Remark on Omnipod DASH implementation: in case of problems, after retrying (3x) user is offered the option to "forcefully" discarding the Pod.
Something like this maybe could also be implemented for EROS but expect this would need non-trivial driver changes? Expecting forcefully wiping pod state can be done with minimal impact on drive code?
AAPS version 3.0.0.1 release and higher Driver: Omnipod EROS
Problem description: The Omnipod EROS driver has a bug that can lead to a situation where users get stuck with a pod registration that can not be "forcefully" discarded. Several users reported running into this problem as a result of Pod failure.
Work around used for not losing Objectives is importing 3.0 settings in AAPS version 2.8.1, discard the Pod and then export preferences that can be imported by AAPS 3.0
Proposed work around Until the actual bug is solved, but also in general, I think the EROS driver should have a way to "wipe" the Pod state in case of "emergencies". Up to AAPS version 2.8 this could be done by editing the unencrypted preference file. As of version 3.0 this is no longer an option.
How about an option to clear Pod state when running in developer mode? This way users have an "escape" option to get out of situations where there is Pod state without option to Discard. For AAPS 2.8 editing the preference file was used as a last resort