AAPS Setup Wizard

When you first start AAPS you are guided by the “Setup Wizard”, to quickly setup all the basic configurations of your app in one go. Setup Wizard guides you, in order to avoid forgetting something crucial. For example, the permission settings are fundamental for setting up AAPS correctly.

However, it’s not mandatory to get everything completely configured in the first run of using the Setup Wizard and you can easily exit the Wizard and come back to it later. There are three routes available after the Setup Wizard to further optimise/change the configuration. These will be explained in the next section. So, it’s okay if you skip some points in the Setup Wizard, you can easily configure them later.

During, and directly after using the Setup Wizard you may not notice any significant observable changes in AAPS. To enable your AAPS loop, you have to follow the Objectives to enable feature after feature. You will start Objective 1 at the end of the Setup Wizard. You are the master of AAPS, not the other way around.

Preview Objectives

If you are keen to know the structure of the objectives, please read Completing the objectives but then come back here to run the Setup Wizard first.

From previous experience, we are aware that new starters often put themselves under pressure to setup AAPS as fast as possible, which can lead to frustration as it is a big learning curve.

So, please take your time in configuring your loop, the benefits of a well-running AAPS loop are huge.

Ask for Help

If there is an error in the documentation or you have a better idea for how something can be explained, you can ask for help from the community as explained at Connect with other users.

Step-wise guide to the AAPS Setup Wizard

Welcome message

This is just the welcome message which you can skip with the “NEXT” button:


License agreement

In the end user license agreement there is important information about the legal aspects of using AAPS. Please read it carefully.

If you don’t understand, or can’t agree to the end user license agreement please don’t use AAPS at all!

If you understand and agree, please click the “I UNDERSTAND AND AGREE” button and follow the Setup Wizard:


Required permissions

AAPS needs some requirements to operate correctly.

In the following screens you are asked several questions you have to agree to, to get AAPS working. The Wizard itself explains why it asks for the relevant setting.

In this screen, we aim to give some more background information, translate more technical speak into common language or explain the reason.

Please click the “NEXT” button:


Battery consumption on smartphones is still a consideration, as the performance of the batteries is still quite limited. Therefore, the Android operating system on your smartphone is quite restrictive about allowing applications to run and consume CPU time, and therefore battery power.

However, AAPS needs to run regularly, e.g. to receive the glucose readings every few minutes and then apply the algorithm to decide how to deal with your glucose levels, based on your specifications. Therefore it must be allowed to do so by Android.

You do this by confirming the setting.

Please click the “ASK FOR PERMISSION” button:


Please select “Allow”:


Android requires special permission for apps if they want to send you notifications.

While it is a good feature to disable notifications e.g. from social media apps, it is essential that you allow AAPS to send you notifications.

Please click the “ASK FOR PERMISSION” button:


Select the “AAPS” app:


Enable “Allow display over other apps” by sliding the slider to the right:


The slider should look this way if it is enabled:


Android links the use of bluetooth communication to the ability to use location services. Perhaps you have seen it with other apps too. It’s common to need location permission if you want to access bluetooth.

AAPS uses bluetooth to communicate with your CGM and insulin pump if they are directly controlled by AAPS and not another app which is used by AAPS. Details may differ from setup to setup.

Click the “ASK FOR PERMISSION” button:


This is important. Otherwise AAPS can not work properly at all.

Click “While using the app”:


Click the “NEXT” button:


AAPS needs to log information to the permanent storage of your smartphone. Permanent storage means that it will be available even after rebooting your smartphone. Other information is just lost, as it is not saved to permanent storage.

Click the “ASK FOR PERMISSION” button:


Click “Allow”:


You are being informed that you have to reboot your smartphone after this change to take effect.

Please don’t stop the Setup Wizard now. You can do it after finishing the Setup Wizard.

Click “OK” and then the “NEXT” button:


Master password

As the configuration of AAPS contains some sensitive data (e.g. API_KEY for accessing your Nightscout server) it is encrypted by a password you can set here.

The second sentence is very important, please DO NOT LOSE YOUR MASTER PASSWORD. Please make a note of it e.g. on Google Drive. Google Drive is a good place as it is backed up by Google for you. Your smartphone or PC can crash and you may have no actual copy. If you forget your Master Password, it can be difficult to recover your profile configuration and progress through the Objectives at a later date.

After filling in the password twice, please click the “NEXT” button:


Fabric upload

Here you can setup the usage of an automated crash and usage reporting service.

It’s not mandatory, but it is good practice to use it.

It helps the developers to better understand your usage of the app, and informs them about crashes which happen.

They get:

  1. The information that the app crashed, which they would not otherwise know since in their own set-up everything works fine and

  2. In the send data (crash information), there is information about the circumstances under which the crash happened, and what kind of configuration is being used.

So it helps the developers to improve the app.

Please enable the “Fabric Upload” by sliding the slider to the right:


Furthermore you can identify yourself that just in case the developers want to reach out to you for questions or urgent concerns:


After filling in your “contact information” click the “OK” button. Contact information can be your identification on Facebook, on Discord, … Just the information you think is helpful to contact you through the best route:


Click the “NEXT” button:


Units (mg/dl <-> mmol/dL)

Please select if your glucose values are in mg/dl or mmol/L and then please click the “NEXT” button:


Display settings

Here you select the range for the sensor glucose display, which will be shown as “in range” between the values you set. You can leave it as the default values for now, and edit it later.

The values you choose only affect the graphical presentation of the diagram, and nothing else.

Your glucose target e.g. is configured separately in your profile.

Your range to analyze TIR (time in range) is configured separately in your reporting server.

Please press the “NEXT” button:


Synchronization with the reporting server and more

Here you are configuring the data upload to your reporting server.

You could do other configurations here too, but for the first run we will just focus on the reporting server.

If you are not able to set it up at the moment, skip it for now. You can configure it later.

If you select an item here on the left tick box, on the right you can then ticking the visibility (eye) box, which will place this plugin in the upper menu on the AAPS home screen. Please select the visibility too if you configure your reporting server at this point.

In this example we select Nightscout as reporting server, and will configure it.

Make sure to choose the correct NSClient version for your needs!

Click here for the release notes of AAPS which explain the differences between the top option NSClient (this is “v1”, although it is not explicitly labelled) and the second option, NSClient v3.

Nightscout users should choose NSClient v3, unless you want to monitor or send remote treatments (e.g. as a parent or caregiver using AAPS for a child) through Nightscout, in which case, choose the first option “NSClient” until further notice.

For Tidepool it is even simpler, as you only need your personal login information.

After making your selection, please press the “NEXT” button:


Here you are configuring the Nightscout reporting server.

Please click on “Nightscout URL”:


Enter you Nightscout URL which is your personal Nightscout server. It’s just an URL you setup yourself, or you were given from your service provider for Nightscout.

Please click the “OK” button:


Enter your nightscout access token. This is the access token for your Nightscout server you configured. Without this token, access will not work.

If you don’t have it at the moment please check the documentation for setting up the reporting server in the AAPS documentation.

After filling in the “NS access token” and clicking “OK”, please click on the “Synchronization” button:


Please select “Upload data to NS” if you already configured nightscout in the previous steps of the Setup Wizard.

If you have stored profiles on Nightscout and want to download them to AAPS, enable “Receive profile store”:


Go back to the previous screen and select “Alarm option”:


For now, leave the switches disabled. We only walked to the screen to make you familar with possible options you might configure in the future. At the moment there is no need to do it.

Go back to the previous screen before and select “Connection settings”.

Here you can configure how to transfer your data to the reporting server.

Caregivers must enable “use cellular connection” as otherwise the smartphone which serves the dependant/child can not upload data outside of WiFi range e.g. on the way to school.

Other AAPS users can disable the tranfer via cellular connection if they want to save data or battery.

If in doubt, just leave all enabled.

Go back to the screen before and select “Advanced Settings”.


Enable “Log app start to NS” if you want get this information in the reporting server. It can help you to know remotely if and when the app has been restarted, particularly as a caregiver.

It might be interesting to see if AAPS is correctly configured now, but later it is usually not that important to be able to see AAPS stopping or starting in Nightscout.

Enable “Create announcements from errors” and “Create announcements from carbs required alerts”.

Leave “Slow down uploads” disabled. You would only use it in unusual circumstances if for example a lot of information is to be transfered to the Nightscout server, and the Nightscout server is being slow in processing this data.

Go back to the screen before and select “NEXT” to go to the next screen:


Patient name

Here you can setup your name in AAPS.

It can be anything. It’s just for differentiating users.

To keep it simple just enter first name and last name.

Press “NEXT” to go to the next screen.


Patient type

Here you select your “Patient type” which is important, as the AAPS software has different limits, depending on the age of the patient. This is important for security and safety reasons.

Here is where you also configure the maximum allowed bolus for a meal. That is, the largest bolus you need to give to cover your typical meals. It’s a security feature to help avoid accidentally overdosing when you are bolusing for meal.

The second limit is similar in concept, but relates to the max carbohydrate intake you expect.

After setting these values, press “NEXT” to go to the next screen:


Used insulin

Select the type of insulin being used in the pump.

The insulin names should be self-explanatory.

Don’t use the “Free-Peak Oref” unless you know what you are doing

For advanced users or medical studies there is the possibility to define with “Free-Peak Oref” a customised profile of how insulin acts. Please don’t use it unless you are an expert, usually the pre-defined values work well for each branded insulin.

Press “NEXT” to go to the next screen:


Blood sugar source

Select the BG source you are using. Please read the documentation for your BG source.

As there are several options available, we don’t explain the configuration for all of them here. We are using Dexcom G6 with the BYODA app in our example here:


If you are using Dexcom G6 with BYODA, enable the visibility in the top level menu by clicking the tickbox on the right side.

After making your selection, press “NEXT” to go to the next screen:


If you are using Dexcom G6 with BYODA, click on the “cog/gearwheel” to access the settings for BYODA.

Enable the “Upload BG data to NS” and “Log sensor change to NS”.

Press “NEXT” to go to the next screen:



Now we are entering a very important part of the Setup Wizard.

Please read the documentation about profiles before you try to enter your profile details on the following screen.

Working profile required - no exceptions here !

An accurate profile is necessary to control the safe action of AAPS

It’s required that you have determined and discussed your profile with your doctor, and that it has been proven to work by successful basal rate, ISF and IC testing!

If a robot has an incorrect input it will fail - consistently. AAPS can only work with the information it is given. If your profile is too strong, you risk hypoglycemia, and if it is too weak, you risk hyperglycemia.

Press “NEXT” to go to the next screen. Enter a “profile name”:


You can have several profiles in the long-term if needed. We only create one here.

Profile only for tutorial - not for your usage

The example profile here is only to show you how to enter data.

It is not intended to be an accurate profile or something very well optimised, because each person’s needs are so different.

Don’t use it for actually looping!

Enter your Duration of insulin Action (DIA) in hours. Then press “IC”:


Enter your IC values: image

Press “ISF”. Enter your ISF values:


Press “BAS”. Enter your basal values:


Press “TARG”. Enter your blood sugar target values.

For open looping this target can be a wider range, as otherwise AAPS notifies you permanently to change the temporary basal rate or another setting, which can be exhausting.

Later, for closed looping, you will generally have only one value for top and bottom. That makes it easier for AAPS to hit the target and give you better overall diabetes control.

Enter/confirm the target values:


Save the profile by clicking on “SAVE”:


After saving a new buttom “Activate Profile” occurs.

Several defined but only one active profile

You can have several profiles defined, but only one activated profile running at any given time.

Press “Activate Profile”:


The profile switch dialogue appears. In this case let it stay as preset.

Several defined but only one active profile

You will learn later how to use this general dialog to handle situations like illness or sport, where you need to change your profile suitable for the circumstances.

Press “OK”:


A confirmation dialog for the profile switch appears.

You can confirm it with pressing “OK”. Press “NEXT” to go to the next screen:


Your profile has now been set:


Insulin pump

Now you are selecting your insulin pump.

You get an important warning dialog. Please read it, and press “OK”.

If your have already setup your profile in the steps before and you know how to connect your pump, feel free to connect it now.

Otherwise, leave the Setup Wizard, using the arrow in the top left corner and let AAPS first show you some blood glucose values. You can come back anytime or use one of the direct configuration options (not using the Wizard).

Please read the documentation for your insulin pump.

Press “NEXT” to go to the next screen.


In this case we select “Virtual Pump”.

Press “NEXT” to go to the next screen:


APS algorithm

Let the standard OpenAPS AMA algorithm remain selected.

Only use the newer algorithm SMB if you know what you are doing

OpenAPS AMA is the most basic algorithm which does not support micro boluses to correct high values. It is the default setting for the earlier objectives before SMB features can be used.

Press “NEXT” to go to the next screen:


Only read the text and change nothing here.

Due to the limitations which are imposed by the Objectives you can’t use either “closed loop” or “SMB features” at the moment anyway.

Press “NEXT” to go to the next screen:


APS mode

Let “Open Loop” remain selected.

Press “NEXT” to go to the next screen:


Sensitivity detection

Let “Sensitivity Oref1” the standard for the sensitivty plugins selected.

Press “NEXT” to go to the next screen:


Start Objective 1

You are entering now the Objectives. The qualification for access to further AAPS features.

Here we start Objective 1, even if at the moment our setup is not completely ready to successfully complete this Objective.

But this is the start.

Press the green “START” to to start objective 1:


You see that you already made some progress, but other areas are to be done.

Press “FINISH” to go to the next screen.


You are coming to the home screen of AAPS.

Here you find the information message in AAPS that you set your profile.

This was done when we switched to our new profile.

You can click “SNOOZE” and it will disappear.


If you accidentally leave the Setup Wizard at any point, you can either simply re-start the Wizard, or change the configuration of the AAPS loop manually.

If your AAPS loop is now fully setup, please move on to the next section “Completing the objectives”.