3.2.0.1 Increased connection Problems with Omnipod Dash

nightscout / AndroidAPS

Opensource automated insulin delivery system (closed loop)

https://wiki.aaps.app

GNU Affero General Public License v3.0

734 stars 1.78k forks source link

3.2.0.1 Increased connection Problems with Omnipod Dash #3031

Closed bionictom closed 9 months ago

bionictom commented 1 year ago

Ever since updating to 3.2 I'm having many more problems with connection to my Omnipod Dash. Multiple times of days, i'll get errors, where AAPS isnt' sure if SMB were delivered or profile changes didn't work. On top of that , I just had an error Pod-Fault: 095 ALARM_WIRE_TEST_OPEN_GROUND which I didnt have before.

I have been usind Dev-Version with DynISF before with no connection problems.

AndroidAPS_LOG_1699178398619.log.zip AndroidAPS.log

Reporting bugs

Note the precise time the problem occurred and describe the circumstances and steps that caused the problem
Note the Build version (found in the About dialog in the app, when pressing the three dots in the upper-right corner).
Obtain the app's log files, which can be found on the phone in /storage/emulated/0/Android/data/info.nightscout.androidaps/ See https://wiki.aaps.app/en/latest/Usage/Accessing-logfiles.html
Open an issue at https://github.com/nightscout/AndroidAPS/issues/new

jbr7rr commented 1 year ago

Do you know which dev version you were using before?

bionictom commented 1 year ago

The one before 3.2.1 I've used was Dev "D" if that makes sense.

robertrub commented 1 year ago

 I just had an error Pod-Fault: 095 ALARM_WIRE_TEST_OPEN_GROUND which I didnt have before.

That alert has nothing to do with AAPS. It is pod breakdown.

With the last master and Dev, DASH connections are working really fast and good. Can you check your pod's expiration dates ? Can you use another lot of pods to test ?

bionictom commented 1 year ago

Thanks for the feedback on that error.

Unfortunately, all the pods I have are the same lot-number. And i won't get any other ones for the next months

robertrub commented 1 year ago

And the expiry date is ???

bionictom commented 1 year ago

And the expiry date is ???

2024-12-07

robertrub commented 1 year ago

Sorry, with the expiry out of the solution, no more threads to pull in order to guess what goes wrong with your system 🤔

robertrub commented 1 year ago

Do you have other BT connected to phone (ear/headphones?) any new powerful 5G WiFi router/extender ?

For all those who have tested the modified 3.2 version DASH, it was always rock solid, always better than with the "old" version.

bionictom commented 1 year ago

The other device connected via bluetooth is a smartband, but that's been like it before the update too. And no Wifi changes in my apartment either.

Thanks for looking into it. Maybe a weird combination of phone/os (lineageOS)? Maybe a software update will change anything? Gonna try that.

robertrub commented 1 year ago

We didn't have any other OS to test the modified code. So that can be an explanation but I'm not really convinced.

Try disconnecting smartband first (easier than flashing the phone ;) )

robertrub commented 10 months ago

Did you update to 3.2.0.3 and see if you still have the connection problems? If you have no more the connection problems, please close this issue.

bionictom commented 9 months ago

I did update, but the problems persisted. I have now upgraded my phone (from Poco F3 on Lineage OS to Poxo X6 Pro on stock OS, and the problems went away. So I guess it was a phone/lineage problem?