search

nightscout / AndroidAPS

Opensource automated insulin delivery system (closed loop)
https://wiki.aaps.app
GNU Affero General Public License v3.0
725 stars 1.76k forks source link

Omnipod Eros / Profile Set catch 22 #1963

Closed thecubic closed 2 years ago

thecubic commented 2 years ago

I upgraded to AndroidAPS 3.1.0 (ca3637f0f) just now during an Omnipod Eros pump switch. When trying to activate the profile stored in the preferences, I got: "Failed to update basal profile: the Pod is in a wrong state"

I figured that meant I needed to activate the new pump. While at the cannula stage, the Omnipod Eros activation UI would not continue, because the basal rates were unset.

I'm not sure which action should happen first between the pod activation and profile set, but it looks as if the profile set requires an Omnipod basal push update despite a null pod state and the pod cannula insertion requires a profile to be set.

To attempt a workaround, I set the pump driver to the virtual pump, which allowed the profile switch to activate, then switched pump drivers back to Omnipod Eros. Happily, it didn't require a new pump and it was able to resume from before I switched

AndroidAPS 3.1.0 Build: ca3637f0f-2022.07.23-16:12 Remote: https://github.com/nightscout/AndroidAPS Flavor: fullrelease Nightscout version: 14.2.4

the exception error - being unable to switch profiles, occurred at 13:29:21.033 (7/24/2022). I'm attaching some logs; I was able to find the profile switch failure event but not anything representing the UI not allowing pump progress export.log

Chikibai commented 2 years ago

Have you try latest master 3.1.0.2 and can verify that error still exits?

vanelsberg commented 2 years ago

Thanks for reporting: Just to see if I understand the problem you are describing:

  1. You updated to version 3.1.0 with no active EROS pump.
  2. On upgrading you were getting the "Failed to update basal profile: the Pod is in a wrong state" error. Correct?

Question: from what version were you upgrading?

(Btw: good work around!)

vanelsberg commented 2 years ago

Problem may be the result of fix https://github.com/nightscout/AndroidAPS/pull/1896 on handling Pod state in earlier AAPS 3.0 dev versions and should not be a problem for current release.

Validation steps, using AAPS 3.01 or higher:

  1. Deactivate EROS pump.
  2. Upgrade to a newer version.

Result:

In case you do get the error use the work around as described by @thecubic: Set the pump driver to virtual pump to allow the profile switch to activate, then switch pump driver back to Omnipod Eros.

thecubic commented 2 years ago

I was upgrading from 3.0.0.1 I believe. Yes, that's a correct description of the problem I'm having