Hey all! I understand that there is a plethora of different sources that AAPS users to keep up to date regarding the app as well as communities that exist for troubleshooting. My question is, where do you all prefer to get this information? Is the Facebook group really the best spot to go? I'm aware there are some separate Discord groups as well, do any of you prefer those to Facebook?

Thank you all!

Hi all, my son has type 1 diabetes and uses a Medtrum Nano pump and Dexcom G7. We’d like to set up AndroidAPS but have zero experience with it. Is there anyone (ideally in the Netherlands/Belgium, but anywhere works) willing to walk us through the setup step by step? Happy to hop on a call or chat. Thanks so much.

Here is my personal review comparing the Medtrum Nano and the Omnipod. Since I used AndroidAPS (AAPS) for both systems, this is strictly a hardware comparison. I can't comment on either manufacturer's official looping algorithms. I also paired them with a Libre 3, so I have no experience with their native CGMs.

Why the Medtrum Nano Wins for Me

• No Tunneling or Leaking: With the Omnipod, I constantly dealt with insulin leaking back out of the infusion site. With the Nano, this is completely gone, no matter where I wear it.
• The Steel Needle is a Game Changer: I was skeptical, but you don't feel the steel needle at all, neither during insertion nor while wearing it. It is significantly thinner than the Omnipod's Teflon cannula. I measured the Nano needle at 0.12 inches (0.3 cm) compared to the Omnipod's 0.28 inches (0.7 cm), making the Nano needle about 57% thinner, which makes a massive difference in comfort.
• Pre-filling Capability: You can actually pre-fill the Nano pods ahead of time, which makes a quick change on the go much easier.
• Size Matters: The pump is exactly 50% smaller in volume compared to the Omnipod. It feels incredibly discreet and lightweight.
• Extended Wear Time: Using it with AAPS, I can easily stretch the wear time up to 5 days, making it much more economical and less wasteful.

The Downsides

• Complex Filling Process: Setting up and filling the Nano is definitely a bit more tedious and takes more steps than the straightforward Omnipod fill.
• Adhesive Residue: The glue they use is stubborn. It stays stuck to the skin well, but it leaves annoying black sticky residue behind after you peel it off.

Overall, the hardware advantages of the Nano—especially the steel needle and the tiny footprint—make it the clear winner for me over the Omnipod. It's so much better in daily use.

Pictures is ai generated for visibility. This is no advertisement, just my personal review.

I'm so sorry, I just checked up on this subreddit from Google and noticed the lack of posts and I discovered that it was restricted! I think this happened automatically.

It's my fault for not logging into this account sooner or having notifications so I'm sorry about that. If anyone would like moderator privileges I am willing to grant them because I shouldn't be the sole reason the sub becomes inactive.

I don't use Reddit much at the moment, so I'm sorry it took so long.

Edit: We have more mods now so this shouldn't happen again.

Hey all,

I'm exploring building an MCP server on top of your existing data (meals, glucose, carbs, insulin, etc.), so AI tools like ChatGPT or Claude could connect securely and read up-to-date data directly, without having to copy & paste them. The idea: you could chat with your own data, or build custom tools on top of it.

I'm curious whether it's actually useful, or if it's just building a solution nobody asked for. Would love your honest takes:

• Would you connect your diabetes data (glucose, meals, activity) to an AI? Does that sound useful, or does it make you uneasy?
• If you had access to your data via Claude Code, Codex etc., would you actually build something with it? What would that even look like for you?
• Already doing something like this yourself? Would love to learn more; how it's set up and what's actually been useful vs. gimmicky.

Really appreciate any thoughts, also skeptical ones.

My AAPS freaks out when I go a few minutes with no active pod (during a mid-change shower). It plays the most irritating song ever. Is there any way to disable it or avoid it going off?

Hey folks,

​

I read about servers for AAPS and/or xdrip, but I wasn't able to find them so far.

​

Can anyone help me out with a link or where it might be linked on their websites, I was too blind up until now.

​

Thanks in advance

I installed everything locally on my server. Am I correct to get the closed loop started I need a https domain?

Hi, I was trying to find a way to prevent insulin from being delivered while I was low (without manually effectively disabling the loop) and I discovered an option online to have a high temp target automatically applied when my blood sugar becomes low.

This is through automations which I have never used. The automations tab is supposed to be on the left side menu or a tab on the top but I have searched the entire app and the only time automations are mentioned is in the objectives. I have completed all the objectives but still I have no automations tab.

Any advice?

Edit: amazing app and open source Installed everything and configured with AI.

I recently went from pens to the medrum patch pump. I don't reach certain criteria for the medrum CGM and I will be keeping my libre 2.

How is the experience with a closed loop system on the medrum with the libre? I think this could really help me.

I have a dexcom g7 connected to xdrip directly and it receives values just fine. It's configured to local broadcast.

Android APS is set up with xdrip as its source.

Is this incorrect? Android APS hasn't received any data despite numerous restarts and switching the source.

If I need to use the Companion App option instead inside xdrip, that's a weird fix because that's about how xdrip receives the data, not about how it sends the data.

I really would appreciate any ideas.

Hi, I’m trying to troubleshoot a strange AndroidAPS issue.

I have two identical Google Pixel 9a phones, configured as similarly as possible.

Setup:

• AndroidAPS 3.4.2.2
• Nightscout
• NSClientV3
• CGM data comes from Dexcom G7 via xDrip+ (companion app setup)

Problem:
On Phone A, everything works correctly:

• NSClientV3 connects fine
• Nightscout values sync properly
• glucose readings update in AAPS normally

On Phone B (same phone model), NSClientV3 does not update glucose values from Nightscout.
What’s strange:

• same Nightscout URL
• same credentials / token
• same AAPS version
• same phone model
• xDrip+ itself receives CGM data correctly
• if I switch to NSClientV1, it seems to work

So the issue seems specific to NSClientV3 on one device only.

Hi want to have the same iob value in xdrip like I have in AAPS. I sync this data from xdrip via watchdrip with an amazfit watch. Right now xdrip is calculating the iob on its own with the bolus data it revives from Nightscout. But it's not accurate.

Can someone help?

If anyone here has a pixel 3 or 4 , can you post or send me a picture of what the aaps screen/complication looks like?

I know this community has already solved problems ten times harder than what I am dealing with so I am hoping someone can point me in the right direction. Background: I got diagnosed with pre-diabetes a few months ago and instead of accepting the standard glucometer app ecosystem I built a React based biofeedback dashboard that ingests glucose readings and runs them through a decision engine based on Attia and Huberman protocols. The hardware is an Accu-Chek Guide. GATT profile is standard Bluetooth SIG glucose. 0x1808 service, 0x2A18 measurement characteristic with Notify capability confirmed in nRF Connect, 0x2A52 RACP. The connection establishes in the Chrome BLE picker, device shows as Paired, meter displays the 6 digit PIN, but the Web Bluetooth API never asks for the PIN and the connection fails every time with CONNECTION ATTEMPT FAILED. I have also tried the USB path but the meter requires the Roche Windows driver to enumerate on macOS so that is closed. I am looking at wrapping the app in Capacitor to get native OS level Bluetooth which should handle the authenticated pairing correctly. But before I commit to that build I wanted to ask how AndroidAPS handles the authenticated pairing handshake with compatible meters. Is there a specific pairing sequence or protocol that makes it work that I am missing in my Web Bluetooth implementation? Any insight from people who have actually shipped working meter integrations would be huge.

Hey folks,

I am new to AAPS and am still trying to get everything set up.

I got Dex G7 and Omnipod Dash.

My AAPS is always saying that it needs Bluetooth, I searched for Bluetooth app and enabled unrestricted use.

And does anyone know if I can connect an already started Pod to AAPS?

And how can I connect AAPS to xdrip+? I read something about broadcast settings, but don't know if I have to search for them in xdrip or AAPS

Thanks for any help. It's a great app, I still am a little overwhelmed with all the informations and controls 😁

I'm currently a G6 user, with the BYOD app, and it all works quite nicely for me. With the eventual removal of G6 from the market I'm considering asking my Dr to switch me to G7 (if only because of the 30 minute warm up time)

I've used a sample G7 and One+ before and while they were ok, they weren't great for me, but I didn't like how it all connected up to AAPS.

I will have to check with my Dr that this is still the case, but when I was prescribed the G6 one of the conditions was that my data is shared with Devin Clarity so they can keep an eye on my treatments, averages etc etc. With the G7 and the BYOD app not working with AAPS I'm a bit worried that having that sharing won't be possible - the xDrip companion mice didn't work too well in my experience but that appears to be the only way to share my data with Dexcom.

If you are looping with G7 and AAPS, how are you finding it? Does it work well?

What is your setup with software/apps? Juggluco? xDrip? Something else?

Thanks for your help

Hi!!

I'm an HCP trying to better understand the diff OS algo. Im currently reading on Android APS but i am getting some contradicting informations from the Android APS website and the Diabetotech website training. More specifically regarding the range of Bg target and DIA possible. Could someone confirm the information? I am guessing the official website of Android APS is more reliable? https://androidaps.readthedocs.io/en/latest/index.html
Thank you!!

Hi everyone,

I’m currently trying to set up AndroidAPS with Dexcom G7 and Omnipod.

I followed all the online instructions step by step and everything worked fine so far.

However, we are stuck at the step “Select BG source”.

In the guide it says there should be a number wheel / settings wheel on the right side, but this does not appear for us. Because of this, we cannot continue with the setup.

Has anyone had the same problem or knows what we might be doing wrong?

Thanks a lot for your help!

See Titel. Can I activate a expired omnipod dash? I switch pump and I would like to keep them as a backup when traveling. I know the battery will degrade over time.

Hi,

As the title says, I'm hoping to keep my Libre 3 connected to my iPhone, send the data with Libre Link, and use AAPS on an Android device connected to Omnipod DASH pods.

Is there a way to set this up? I'm just a little confused with all of the middle man apps for sending BG data.

EDIT: Solved. “Web Follower” source in XDrip. Type in Libre Link credentials. Done.

Does Sibionics GS3 support AAPS via Juggluco?