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

recurring com error and basal rate mismatch #1363

Open jumalakarhu opened 2 years ago

jumalakarhu commented 2 years ago

Build 23207a275-2022 3.0.0 master, Sony Xperia xz1c android 9 Omnipod Eros, OL with latest firmware (3.2?) Lots of errors for several days with different pods and with two different OL. Communication failed: received an invalid response Unable to verify bolus succeeded... Unabel to verify basal

It seems that the pod is in a different state than aaps. Sometimes basal rate reported by aaps is not the same as shown i omnipod tab. Especially after latest pod change when there was an error during deactivation and activation there has been many errors. Pod change was finished at 17:39 with errors before that and after.

AndroidAPS._2022-02-2218-55-01.1.zip

AndroidAPS._2022-02-2218-55-01.0.zip AndroidAPS._2022-02-2217-30-29.1.zip AndroidAPS._2022-02-2217-30-29.0.zip AndroidAPS._2022-02-2217-25-20.0.zip

jumalakarhu commented 2 years ago

Update: after 6 hours com errors came back.

_Testing again this morning and might have a path to reproduce error, but I am not in a position to test with new pod at the moment.

  1. Active permanent profile change that results in basal that is not an multiple of 0.05
  2. deactivate pod (I got errors here)
  3. activate pod (I got errors in last step)
  4. new pod get a lot of "communication error: invalid response" and "uncertain temp basal". Pod history was packed with errors. Also had basal value in omnipod tab different from value in aaps home screen after a pod refresh/update.

I've got pod working again, at least for 2 hours now, by deactivating loop (not sure if necessary), changing to 100% or other % that will give a multiple of 0.05 for all basal values, activate loop._