nightscout
Omnipod Dash pairing problems
Reporting bugs
- I'm having issues with Omnipod Dash not pairing. Google Pixel 9 Pro on Android 15 (BT Bonded), never had a single problems till today. My old pump expired so I deactivated it and tried to pair a new one but I'm now on fifth Pod wiothout being able to pair
- Test I've done so far was to try with a different phone: If I import my settings is going to fail, if I use a new profile made from scratch it works. But I dont want to redo all the objectives
- It's clear the problem is something in the settings file, I already deleted all Twiboard in BT devices and now the error I get is this:
- version 3.3.1.3 and now 3.3.2.0
The thing that is strange is the address still on the Dash panel
Is the button to deactivate a pod still active? If yes use it.
Hi, Problem is my Pixel autoupdated to Android 16 and I was not aware of that, once discovered I managed to build the hotfix version and pair my pod. Only proem is that Dev version has not closed loop. Do anyone know when a ne stable release will come out?
You didn't need to build the dev version to apply the hotfix. But if you want to run closed loop in Dev builds you need to enable engineering mode. Instructions here: https://androidaps.readthedocs.io/en/latest/AdvancedOptions/DevBranch.html
You didn't need to build the dev version to apply the hotfix. But if you want to run closed loop in Dev builds you need to enable engineering mode. Instructions here: https://androidaps.readthedocs.io/en/latest/AdvancedOptions/DevBranch.html
Sorry I'm not a programmer and I use Android Studio just to compile AAPS. What is the other way to have the hotfix?
Open the terminal in Android Studio. Type:
git fetchand press ENTER, wait for it to finishgit checkout 39dd2e6151daafa3c98634eec77361b124779aadand press ENTER, wait for it to finish.
Rebuild the AndroidAPS APK.
Open the terminal in Android Studio. Type:
git fetchand press ENTER, wait for it to finishgit checkout 39dd2e6151daafa3c98634eec77361b124779aadand press ENTER, wait for it to finish.Rebuild the AndroidAPS APK.
well, nothing changes. Still in developer mode. It's so frustrating
I dont' know, i cloned repository on a new project then I've done what you told me but still It tells me that I'm in Dev Mode. Then all these attempts to fix have broken my settings. I have to reimport them but the most recent is from one week ago so different pod, will I loose the connection to the paired one? Because I'm on fifth pod today and I don't think the suppplier will give them back to me.
I dont' know, i cloned repository on a new project then I've done what you told me but still It tells me that I'm in Dev Mode. Then all these attempts to fix have broken my settings. I have to reimport them but the most recent is from one week ago so different pod, will I loose the connection to the paired one? Because I'm on fifth pod today and I don't think the suppplier will give them back to me.
If the settings file you have had an active pod, then yes you will lose the one that's active now.
Your settings are probably broken because you installed the dev version. I think the latest dev changed the settings. I think you are stuck on dev now. But honestly there is nothing wrong with dev for now. No need to stress about it. Just enable engineering mode by creating the engineering mode file and placing it in your AAPS directory, and all will be good. Make sure AAPS directory is properly set though:
You can stay on dev until it becomes the latest master.
Well, it's back to objectives so no way I can close the loop, too many security features prevents me from having back my pod. It should be nice to export/import only some settings, I would choose the objectives and leave everything else as is.
this is a long shot. What if I import the good old settings into another phone, then remove the old pod, re export the settings and import them into actual phone? Would it work or will I loose the pod?
By the way I managed to build the correct version so now at least i'm not in Dev mode anymore
this is a long shot. What if I import the good old settings into another phone, then remove the old pod, re export the settings and import them into actual phone? Would it work or will I loose the pod?
By the way I managed to build the correct version so now at least i'm not in Dev mode anymore
If you do what you are saying you will lose your pod. The settings file contains any active Pod state (either if it's not running a pod or active) as well as the connection keys needed to communicate with the pod. Those are unique to every active pod.
So if you want to keep the active pod running, it will only work with the settings you have at the moment. I wish there was a way to separate the two but there isn't at the moment.
@nickb24 built the apk with the hotfix for A16 but get following message when initializing new pod
@spanosp How long between filling the pod with insulin and then trying to activate it?
@nickb24 ..you guessed it right, the pod expired. Got it all to work with a new pod
Thank you.
Ref: https://github.com/nightscout/AndroidAPS/issues/4027#issuecomment-2994479952
I've been seeing people report this error a lot since the A16 activation bug. I assume it's because they fill the pod and then because they can't activate it they let it sit for hours until they compile a new AAPS with the hotfix. But by that time the pod was left in a filled but unactivated state for too long and now has turned into a "lump of coal" 😄
exactly.. the pod kept beeping for more than 1h after filling with insulin, so wrongfully thought it was still ok too initialize.
I would be curious to know if someone knows the exact time before it's too late to activate a pod after being filled.
Hi I started using aaps a few weeks ago with my dash and it worked great until a few days ago and now I seem to have this connection problem and I don't know how to solve it I'm a bit lost with all the information out there I have a pixel 6a
Hi I started using aaps a few weeks ago with my dash and it worked great until a few days ago and now I seem to have this connection problem and I don't know how to solve it I'm a bit lost with all the information out there I have a pixel 6a
Did you follow my recommendation here? https://github.com/nightscout/AndroidAPS/issues/4030#issuecomment-2970207250
I'm getting this error on every pod activation. Disabling and enabling bluetooth seems to fix it.
