AAPS Release_3.4.2.1 Omnipod Dash didn't set the Profile

[kenkolden]

switched from Virtual MDI profile to Omnipod Dash
main screen shows Profile Not Set
unable to change profile

switched xDrip source to BYOD
Clean install AAPS 3.4.2.1 imported settings
Shows Profile Not Set unable to change profile

AndroidAPS_LOG_1775111057889.log.zip

Discord found comments to switch to Virtual Pump then switch back to Omnipod Dash not virtual pump fixed the Profile not set message

1:50 AM pod no longer able to connect i believe due to expiration date exceeded 6-7-2025

[imakeinterfaces]

I have the same problem but I was just doing a version upgrade on dash pod. App is no longer usable.

[imakeinterfaces]

Deleting my aaps directory fixed this for me. But there's definitely some incompatability with legacy settings here and the answer was non obvious. the tell is that when you do that, the profile finally sets. Then you need to try to deactivate pod, exit early, and then hit discard when it gives you the optoin. Hope this helps friends!

[imakeinterfaces]

Make sure to recreate/reset that aaps directory after you've done that. Otherwise you'll end up like I did where the pump initializes and then a half hour later the bluetooth id and everything goes missing and you have to put on a new pod. I'm assuming that this data gets written to disk after a while so that directory is indeed crucial.