diff --git a/docs/CROWDIN/it/AdvancedOptions/Autotune.md b/docs/CROWDIN/it/AdvancedOptions/Autotune.md
index 15075a1c35c1..f7e534a1000a 100644
--- a/docs/CROWDIN/it/AdvancedOptions/Autotune.md
+++ b/docs/CROWDIN/it/AdvancedOptions/Autotune.md
@@ -1,10 +1,18 @@
-# Come usare il plugin Autotune (solo con versione dev)
+# How to use Autotune plugin
Documentation about Autotune algorithm can be found in [OpenAPS documentation](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html).
Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
-**Attualmente Autotune Plugin è disponibile solo in [dev branch](../AdvancedOptions/DevBranch.md) e in modalità Engineering.**
+Autotune Plugin is available in AAPS releases since [3.4](#version3400) but is hidden by default.
+
+## Show the Autotune plugin
+
+Create an empty file named `enable_autotune` in the `extra` subfolder of your phone AAPS folder.
+
+
+
+Autotune will then display in Config Builder after you restart AAPS.
@@ -74,7 +82,7 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
- Se è stato aggiornato il profilo di input, il pulsante "Aggiorna profilo di input" viene sostituito dal pulsante "Revert input profile" (vedere la schermata sottostante). Puoi vedere immediatamente in questo modo se il tuo attuale profilo di input nel plugin del profilo locale include già il risultato dell'ultima esecuzione o meno. Hai anche la possibilità di recuperare il tuo profilo di input senza risultati automatici con questo pulsante
- 
+ 
@@ -86,6 +94,11 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
+```{admonition} Only DEV
+:class: info
+Automation Switch Profile feature is only available in Dev/Engineering mode.
+```
+
- Automation Switch Profile (default Off): see [Run Autotune with an automation rule](#autotune-run-autotune-with-an-automation-rule) below. Se si modifica questa impostazione in On, il profilo di input verrà automaticamente aggiornato dal profilo Tuned e verrà attivato.
- **Fai attenzione, devi fidarti e verificare durante diversi giorni successivi, che dopo un aggiornamento e l'attivazione del profilo Tuned senza modifiche, il tuo loop migliori**
@@ -136,6 +149,11 @@ Autotune plugin is an implementation of OpenAPS autotune algorithm within AAPS.
## Avvio Autotune con una regola automatica
+```{admonition} Only DEV
+:class: info
+Automation Switch Profile feature is only available in Dev/Engineering mode.
+```
+
Il primo passo è definire il corretto evento per una regola di automazione con Autotune:
Nota: per ulteriori informazioni su come impostare una regola di automazione, vedere [ qui](../DailyLifeWithAaps/Automations.md).
@@ -150,11 +168,11 @@ Nota: per ulteriori informazioni su come impostare una regola di automazione, ve
- Quindi è possibile selezionare la funzione "Esegui Autotune" dall' elenco
- 
+ 
- È quindi possibile selezionare la funzione Autotune per regolare i parametri per l'esecuzione. I parametri predefiniti sono "Profilo attivo", il valore di Tune days predefinito definito nelle preferenze di plugin di Autotune e tutti i giorni sono selezionati.
- 
+ 
- Dopo alcuni giorni, se ti fidi completamente dei risultati di Autotune e la percentuale di modifica è bassa, puoi modificare le [impostazioni di Autotune](#autotune-plugin-settings) "Profilo di commutazione di automazione" per abilitare l'aggiornamento automatico e attivare il profilo sintonizzato dopo il calcolo.
diff --git a/docs/CROWDIN/it/CompatibleCgms/DexcomG6.md b/docs/CROWDIN/it/CompatibleCgms/DexcomG6.md
index 943f3aa8905e..78478404e278 100644
--- a/docs/CROWDIN/it/CompatibleCgms/DexcomG6.md
+++ b/docs/CROWDIN/it/CompatibleCgms/DexcomG6.md
@@ -1,7 +1,5 @@
# Dexcom G6 e ONE
-WARNING --- [BYODA](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750)--- There are reported issues **AAPS** receiving no BG data when using either BYODA & DiaKEM as its data source. Users are recommended to use [X-Drip+](https://androidaps.readthedocs.io/en/latest/CompatibleCgms/xDrip.html) as **AAPS'** BG data source until this issue has been resolved.
-
## Prima le basi
- Segui i consigli generali di igiene del sensore e le impostazioni corrispondente [qui](../CompatibleCgms/GeneralCGMRecommendation.md).
@@ -33,7 +31,14 @@ Leggi di più nell'[articolo](https://www.diabettech.com/artificial-pancreas/diy
(DexcomG6-if-using-g6-with-build-your-own-dexcom-app)=
## Se usi un G6 con Build Your Own Dexcom App
-- [Costruisci la tua app Dexcom](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750) (BYODA) supporta la trasmissione locale su AAPS e/o xDrip+ (non per i sensori G5/ONE/G7!)
+```{admonition} No new users
+:class: warning
+Latest Dexcom servers update broke BYODA for new installs: the app no longer can get through the login and onboarding process that happens on a fresh install of the app.
+Existing users do not experience issues for now: do not logout, wipe data, or reinstall the BYODA app as that will prevent you from getting the app up and running again. If it is already running, you should be unaffected.
+New users are recommended to use [xDrip+](https://androidaps.readthedocs.io/en/latest/CompatibleCgms/xDrip.html) as **AAPS'** BG data source until this issue has been resolved.
+```
+
+- [Build Your Own Dexcom App](https://docs.google.com/forms/d/e/1FAIpQLScD76G0Y-BlL4tZljaFkjlwuqhT83QlFM5v6ZEfO7gCU98iJQ/viewform?fbzx=2196386787609383750) (BYODA) supports local broadcast to AAPS and/or xDrip+ (**not for** **G5/ONE/G7 sensors!**)
diff --git a/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md b/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md
index ed62cb0b34c1..92b8dbe1387d 100644
--- a/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md
+++ b/docs/CROWDIN/it/CompatibleCgms/DexcomG7.md
@@ -5,8 +5,6 @@
È da notare che i sensori G7 e ONE+, contrariamente al G6, non lisciano i valori della glicemia, né nell'app, né con il lettore. Maggiori dettagli [qui](https://www.dexcom.com/en-us/faqs/why-does-past-cgm-data-look-different-from-past-data-on-receiver-and-follow-app).
-
-
```{admonition} Smoothing method
Read [Smoothing method](../CompatibleCgms/SmoothingBloodGlucoseData.md) suggestions to use for Dexcom G7/ONE+/Stelo
```
@@ -20,12 +18,17 @@ Read [Smoothing method](../CompatibleCgms/SmoothingBloodGlucoseData.md) suggesti
## 2. App Dexcom G7 Patchata (DiaKEM)
+```{admonition} No new users
+:class: warning
+Latest Dexcom servers update broke DiaKEM for new installs: the G7 app no longer can get through the login and onboarding process that happens on a fresh install of the app.
+Existing users do not experience issues for now: do not logout, wipe data, or reinstall the G7 app as that will prevent you from getting the app up and running again. If it is already running, you should be unaffected.
+New users are recommended to use [xDrip+](https://androidaps.readthedocs.io/en/latest/CompatibleCgms/xDrip.html) as **AAPS'** BG data source until this issue has been resolved.
+```
+
**Note: AAPS 3.2.0.0 or higher is required! Not available for ONE+.**
### Installare una nuova app G7 patchata (!) e avviare il sensore
-WARNING --- There are reported issues **AAPS** receiving no BG data when using either DiaKEM as its data source. Users are recommended to use [X-Drip+](https://androidaps.readthedocs.io/en/latest/CompatibleCgms/xDrip.html) as **AAPS'** BG data source until this issue has been resolved.
-
A patched Dexcom G7 app (DiaKEM) gives access to the Dexcom G7 data. This is not the BYODA app as this app can not receive G7 data at the moment.
diff --git a/docs/CROWDIN/it/CompatiblePumps/Equil5.3.md b/docs/CROWDIN/it/CompatiblePumps/Equil5.3.md
index 1dbd61be94c3..cf4ec934d32a 100644
--- a/docs/CROWDIN/it/CompatiblePumps/Equil5.3.md
+++ b/docs/CROWDIN/it/CompatiblePumps/Equil5.3.md
@@ -1,8 +1,4 @@
-- - -
-orphan: true
-- - -
-
-# Equil 5.3
+# Equil
These instructions are for configuring the Equil insulin pump.
@@ -13,7 +9,7 @@ These instructions are for configuring the Equil insulin pump.
## Hardware and Software Requirements
* **Compatible Equil hardware**
-§todo
+ Currently Equil 5.3 and 5.4 is supported
* [Version 3.3.0.0](#version3300) or newer of AAPS
@@ -35,4 +31,6 @@ Navigate to the Equil Tab and press **Pair Equil Patch Pump**.
-
\ No newline at end of file
+
+
+If you set different password than default 0000 (recommended for your safety), do not forget to store this password on a safe place. This password is stored to the pump. Then this password is asked on every next pairing attempt until you do proper unpairing in AAPS. This makes the pump also unusable with original PDA until you unpair pump from AAPS.
diff --git a/docs/CROWDIN/it/CompatiblePumps/MedtronicPump.md b/docs/CROWDIN/it/CompatiblePumps/MedtronicPump.md
index ab59971afe14..5b59516b4bc7 100644
--- a/docs/CROWDIN/it/CompatiblePumps/MedtronicPump.md
+++ b/docs/CROWDIN/it/CompatiblePumps/MedtronicPump.md
@@ -1,7 +1,3 @@
-- - -
-orphan: true
-- - -
-
# Medtronic Pumps
The driver does not work with any newer models, including all models ending in G (530G, 600-series [630G, 640G, 670G], 700-series [770G, 780G], etc.).
@@ -52,7 +48,7 @@ When configuring your Medtronic pump with the setup wizard it is possible that y
While setting up AAPS to work with your medtronic pump you need to set following items: (see picture above)
- **Pump Serial Number**: Displayed on the back of your pump and starts with SN. You should only enter the 6 numbers shown without any alphabetic characters (e.g. 123456).
- **Pump Type**: The model pump you are using (e.g. 522).
-- **Pump Frequency**: There are two options based on where your pump was originally distributed. Please check the [FAQ](#faq) if you are unsure which option to select):
+- **Pump Frequency**: There are two options based on where your pump was originally distributed. Please check the [FAQ](#MedtronicPump-faq) if you are unsure which option to select):
- for US & Canada, frequency used is 916 Mhz
- for Worldwide, frequency used is 868 Mhz
- **Max Basal on Pump (U/h)**: This needs to match the setting set on your pump (see Configuration of the pump above). Again this setting must be carefully selected as it will determine how much AAPS can deliver via your basal rate. This will effectively set the maximum temporary basal rate. As an example, setting this value to four times your maximum standard basal rate would allow a 400% Temporary Basal Rate. The maximum value permitted by the pump is 34.9 units per hour.
@@ -88,8 +84,8 @@ While setting up AAPS to work with your medtronic pump you need to set following
At the bottom of the screen there are three buttons:
- **Refresh** is for refreshing the current status of the pump. This should only be used if the connection was lost for a sustained period as this will require a full data refresh (retrieve history, get/set time, get profile, get battery status, etc).
-- **Pump History**: Shows pump history (see [below](#pump-history))
-- **RL Stats**: Show RL Stats (see [below](#rl-status-rileylink-status))
+- **Pump History**: Shows pump history (see [below](#MedtronicPump-pump-history))
+- **RL Stats**: Show RL Stats (see [below](#MedtronicPump-rl-status-rileylink-status))
(MedtronicPump-pump-history)=
## Pump History
@@ -118,7 +114,7 @@ When the Medtronic driver is used, two additional actions are added to Actions T
AAPS is using serial number for synchronization and serial number is exposed to NS. Because knowledge of serial number of old Medtronic pump can be used to control the pump remotely take special care to hardening NS site preventing leakage of SN of your pump. See https://nightscout.github.io/nightscout/security/
### OpenAPS users
-OpenAPS users should note that AAPS with Medtronic uses a completely different approach than OpenAPS. Using AAPS the primary method of interacting with th pump is via your phone. In normal use cases it is likely that the only time it is required to use the pump menu is when changing resevoirs. This is very different when using OpenAPS where at least some of a bolus is usually delivered via the quick bolus buttons. In the event the pump is used to manually deliver a bolus there can be issues if AAPS attempts to deliver one at the same time. There are checks to try and prevent issues in such cases but this should still be avoided where possible.
+OpenAPS users should note that AAPS with Medtronic uses a completely different approach than OpenAPS. Using AAPS the primary method of interacting with the pump is via your phone. In normal use cases it is likely that the only time it is required to use the pump menu is when changing resevoirs. This is very different when using OpenAPS where at least some of a bolus is usually delivered via the quick bolus buttons. In the event the pump is used to manually deliver a bolus there can be issues if AAPS attempts to deliver one at the same time. There are checks to try and prevent issues in such cases but this should still be avoided where possible.
### Logging
In the event you need to troubleshoot your Medtronic pump function select the menu icon in the upper left corner of the screen, select Maintenance and Log Settings. For troubleshooting any Medtronic issues Pump, PumpComm, PumpBTComm should be checked.
@@ -165,4 +161,4 @@ On the back of the pump you will find a line detailing your model number along w
- NA - North America (in frequency selection you need to select "US & Canada (916 MHz)")
- CA - Canada (in frequency selection you need to select "US & Canada (916 MHz)")
- WW - Worldwide (in frequency selection you need to select "Worldwide (868 Mhz)")
-
+
diff --git a/docs/CROWDIN/it/CompatiblePumps/MedtrumNano.md b/docs/CROWDIN/it/CompatiblePumps/MedtrumNano.md
index 6cdee7d86b60..f3b7a2c46923 100644
--- a/docs/CROWDIN/it/CompatiblePumps/MedtrumNano.md
+++ b/docs/CROWDIN/it/CompatiblePumps/MedtrumNano.md
@@ -1,7 +1,3 @@
-- - -
-orphan: true
-- - -
-
# Medtrum Nano / 300U
These instructions are for configuring the Medtrum insulin pump.
@@ -120,7 +116,7 @@ This setting changes the time of the expiration warning, when [Patch Expiration]
***Default: 25U.***
-This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one hour. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -128,7 +124,7 @@ Set this to a sensible value for your insulin requirements.
***Default: 80U.***
-This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#reset-alarms).
+This setting changes the maximum amount of insulin that can be delivered in one day. If this limit is exceeded the patch will suspend and give an alarm. The alarm can be reset by pressing the reset button on in the overview menu see [Reset alarms](#nano-reset-alarms).
Set this to a sensible value for your insulin requirements.
@@ -189,9 +185,9 @@ This setting can be changed when using Medtrum pump but it is recommended to set
#### Activate patch from the Medtrum overview Tab
-Navigate to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
+Navigate to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button in the bottom right corner.
-If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#deactivate-patch).
+If a patch is already active, you will be prompted to deactivate this patch first. see [Deactivate Patch](#nano-deactivate-patch).
Follow the prompts to fill and activate a new patch. Please note - it is important to only connect the pumpbase to the reservoir patch at the step when you are prompted to do so. **You must only put the pump on your body and insert the cannula when prompted to during the activation process (after priming is complete).**
@@ -242,9 +238,11 @@ When activation is complete, the following screen will appear
Press **OK** to return to main screen.
+(nano-deactivate-patch)=
+
### Deactivate patch
-To deactivate a currently active patch, go to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+To deactivate a currently active patch, go to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -258,9 +256,11 @@ If Android APS in unable to deactivate the patch (For instance because the pumpb
Once deactivation is complete, press **OK** to return to main screen or press **Next** to continue the process to activate a new patch.
+(nano-resume-interrupted-activation)=
+
### Resume interrupted activation
-If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#overview) in the AAPS interface and press the **Change Patch** button.
+If a patch activation is interrupted, for instance because the phone battery runs out, you can resume the activation process by going to the [Medtrum TAB](#nano-overview) in the AAPS interface and press the **Change Patch** button.
@@ -270,6 +270,8 @@ Press **Next** to continue the activation process. Press **Discard** to discard
The driver will try to determine the current status of the patch activation. If this was successful it will go into the activation progress at the current step.
+(nano-overview)=
+
## Overview
The overview contains the current status of the Medtrum patch. It also contains buttons to change the patch, reset alarms and refresh the status.
@@ -343,6 +345,8 @@ This button will refresh the status of the patch.
This button will start the process to change the patch. See [Activate patch](#medtrum-activate-patch) for more information.
+(nano-reset-alarms)=
+
### Reset alarms
The alarm button will appear on the overview screen when there is an active alarm that can be reset. Pressing this button will reset the alarms and resume insulin delivery if the patch has been suspended due to the alarm. E.g. E.g. when suspended due to a maximum daily insulin delivery alarm.
@@ -370,9 +374,12 @@ From AAPS version 3.3.0.0 onwards, the sync progress is shown in the the home sc
If you are experiencing connection timeouts or other connection issues:
- In Android application settings for AAPS: Set location permission to "Allow all the time".
+### Bluetooth issues
+For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md)
+
### Activation interrupted
-If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#resume-interrupted-activation)
+If the activation process is interrupted for example by and empty phone battery or phone crash. The activation process can be resumed by going to the change patch screen and follow the steps to resume the activation as outlined here: [Resume interrupted activation](#nano-resume-interrupted-activation)
### Preventing patch faults
diff --git a/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md b/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md
index 78d5caf70838..a9e0adff5dfd 100644
--- a/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md
+++ b/docs/CROWDIN/it/CompatiblePumps/OmnipodDASH.md
@@ -1,221 +1,283 @@
-- - -
-orphan: true
-- - -
-
# Omnipod DASH
-Queste istruzioni sono per configurare il microinfusore di generazione **Omnipod DASH** **(NON Omnipod Eros)**, disponibile a partire di **AAPS** versione 3.0.
+These instructions are for configuring the **Omnipod DASH** generation pump **(NOT Omnipod Eros)**, available in **AAPS** from version 3.0.
## Specifiche Omnipod DASH
Queste sono le specifiche dell' **Omnipod DASH** ('DASH') e ciò che lo differenzia dall'**Omnipod EROS** ('EROS'):
-* I pod DASH sono identificabili dalla linguetta di protezione dell'ago blu (gli EROS hanno una linguetta trasparente). I pod sono altrimenti identici in termini di dimensioni fisiche.
-* Non c'è bisogno di un dispositivo separato per fare da ponte da Omnipod a Bluetooth (NO RileyLink, OrangeLink o EmaLink necessari).
-* Il Bluetooth del DASH si connette solo quando necessario, per inviare i comandi, e si disconnette subito dopo!
-* Non ci saranno più errori "nessuna connessione dal dispositivo al pod" con DASH.
-* **AAPS** attenderà che il pod sia accessibile per inviare i comandi.
-* Al momento dell'attivazione, **AAPS** troverà e connetterà il nuovo pod DASH.
-* Expected range: 5-10 meters (YMMV).
-
+- The DASH pods are identified by a **blue needle cap** (EROS has a clear needle cap). I pod sono altrimenti identici in termini di dimensioni fisiche.
+- Non c'è bisogno di un dispositivo separato per fare da ponte da Omnipod a Bluetooth (NO RileyLink, OrangeLink o EmaLink necessari).
+- The DASH's Bluetooth connection is used only when sending a command (e.g a Bolus), and disconnects right after issuing the command.
+- Non ci saranno più errori "nessuna connessione dal dispositivo al pod" con DASH.
+- **AAPS** attenderà che il pod sia accessibile per inviare i comandi.
+- Al momento dell'attivazione, **AAPS** troverà e connetterà il nuovo pod DASH.
+- Expected range from phone: 5-10 meters (YMMV).
+
+(omnipod-dash-constraints)=
+
+## Omnipod DASH known AAPS constraints/issues
+- Android 16 requires **AAPS** version 3.3.2.1 or later.
+- General advice is to run **AAPS** on Android 14 or 16. Android 15 has many reported [issues](https://github.com/nightscout/AndroidAPS/issues/3471) from the community. However, if you do run on Android 15 you will likely need to enable Bluetooth Bonding to successfully activate and use Pods, see [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) for more info on the Bonding settings.
+- Too frequent basal updates may cause basal insulin delivery [problems](https://github.com/nightscout/AndroidAPS/issues/4158) with Omnipod Dash. When using **SMB**, limit the interval to 5 minutes minimum to avoid this issue.
+- Dash only supports basal rate in 0.05 U/h steps. If you try to set basal with 0.01 steps in your **AAPS profile**, AAPS will not give a warning even though the pod will round up the rate into 0.05 steps. If you view POD MGMT/Pod History it will display that 0.05 basal was set. This also means the lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h.
+- The activation status of a Pod is stored in the settings file, if you export a settings file with an active pod. Then change to a new pod, then restore the settings from your previous export you will have now restored the old pod activation and removed the new pod activation. This is why we recommend to export settings after each pod activation to allow a restore of that pods activation state if something happens to your rig.
+- When setting a new basal profile, DASH will suspend delivery before setting the new basal **Profile**. If there is a communication interruption or error, the basal profile won't automatically re-start. See section [Resuming Insulin Delivery](#omnipod-dash-resuming-insulin-delivery) for details.
+- If alerts are configured, and the pod is about to expire, the pod will keep beeping until alerts are silenced, see [Silencing Pod Alerts](#omnipod-dash-silencing-pod-alerts) for details.
+- There are a number of known issues with Bluetooth which can cause pod activation problems. See [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md) for the known issue and solutions to these problems.
+
+(hardware-software-requirements)=
+
+(omnipod-dash-hardware-software-requirements)=
## Requisiti Hardware/Software
-* DASH è identificato con la linguetta blu di protezione dell’ago.
+- Omnipod DASH is identified by the blue needle cap.
-* **Telefono Android compatibile** con una connessione Bluetooth BLE
- Tieni presente che il driver **AAPS** Omnipod Dash si connette con il DASH tramite Bluetooth ogni volta che invia un comando, e scollega subito dopo. La connessione Bluetooth può essere disturbata da altri dispositivi bluetooth collegati al telefono che esegue **AAPS**, come auricolari ecc.. (che potrebbero causare, in rare occasioni, problemi di connessione o errori pod / perdita al momento dell'attivazione o in seguito con alcuni modelli di telefono).
- - **Versione 3.0 o più recente di AAPS costruita e installata** utilizzando le istruzioni [**Costruisci AAPS**](../SettingUpAaps/BuildingAaps.md).
-* [**Sensore di Glicemia (CGM)**](../Getting-Started/CompatiblesCgms.md)
+- **A Compatible Android phone** with a Bluetooth Low Energy (BLE) (see [Phones](../Getting-Started/Phones.md) for more info), additionally the following information will help guide you on other key considerations around successfully activating and using the DASH on a compatible phone:
+ - The **AAPS** Omnipod Dash driver connects with the DASH Pod using Bluetooth.
+ **AAPS** will automatically establish a new Bluetooth connection to the Pod every time it needs to send a command (e.g a Bolus), after sending the command the Bluetooth connection is immediately disconnected.
+ - **NOTE:**
+ - The Bluetooth connection can be interrupted/disturbed by other Bluetooth devices linked to the phone that is running **AAPS**, like earbuds etc... Devices like this can cause connection errors or pod activation issues on some models of phones. It's a good idea to review the [tested hardware setups](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true) list for known working configurations before committing to a new rig built around Omnipod DASH.
+ - There are a number of known issues with Bluetooth which can cause pod activation problems (See [Troubleshooting](#troubleshooting) for advice on other Bluetooth issues) specifically the [Bluetooth related issues](#omnipod-dash-bluetooth-related-issues) section.
+ - For **Android 15** or below: You **MUST** use **Version 3.0 or newer of AAPS** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions, however it's advisable to run the latest released version.
+ - For **Android 16**: you **MUST** use **Version 3.3.2.1 or newer of AAPS** using the [**Build APK**](../SettingUpAaps/BuildingAaps.md) instructions, due to Android 16 changing how its Bluetooth works. Any version earlier than 3.3.2.1 will likely cause pod failures and/or activation [issues](https://github.com/nightscout/AndroidAPS/issues/3471).
+- A supported [**Continuous Glucose Monitor (CGM)**](../Getting-Started/CompatiblesCgms.md)
-The instructions below explain how to activate a new pod session. Wait to close to expiry of a current pod session before trying to connect **AAPS** with a new pod. Once a pod is is cancelled it cannot reused and the disconnection will be final.
+The instructions below explain how to activate a new pod session using **AAPS**. You should wait for your current Pod to be close expiry, as you will need to activate a new Pod with **AAPS**. Once a pod is de-activated it cannot be reused/re-activated, the de-activation is final.
## Prima Di Iniziare
-**SAFETY FIRST** - you should not try to connect **AAPS** to a pod for the first time without having access to extra pods, insulin, and phone devices are a must have.
+Ensure you have read and understand this whole guide, have read and understand the **Before You Begin** section, as well as **[Omnipod and AAPS Constraints and Issues](#omnipod-dash-constraints)** to avoid running into a known problem.
-**Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.** Previously a user may have operated a PDM to send commands to your DASH. A DASH will only faciiliate a single device to send commands to communicate with it. The device that successfully activates the pod is the only device allowed to communicate with it from that point forward. This means that once you activate a DASH with your Android phone through the **AAPS**, **you will no longer be able to use your PDM with that pod**. The **AAPS** Dash driver in your Android phone is now your acting PDM.
+### **SAFETY FIRST** - You **SHOULD NOT** try to connect **AAPS** to a pod for the first time without having access to all of the following:
+1. Extra pods (3 or more spare)
+2. Spare Insulin and MDI equipment
+3. A working Omnipod PDM (In case **AAPS** fails)
+4. Supported Phones are a must! (See [Hardware/Software Requirements](#hardware-software-requirements))
+5. Correct version of AAPS built and installed
-*This does NOT mean you should throw away your PDM, it is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or AAPS is not working correctly.*
+### **Your Omnipod Dash PDM will become redundant after the AAPS Dash driver activates your pod.**
+- Before using **AAPS** you or your care giver would have had to manage the Pod using the Omnipod PDM (or in some regions a Phone app) to send commands to your DASH (e.g a Bolus).
+- The DASH can only facilitate a single Bluetooth device (e.g PDM or Phone) connection to manage and send commands.
+- The device that successfully activates the pod is the only device allowed to communicate with that Pod from that point forward. This means that once you activate a DASH with your Android phone using **AAPS**, **you will no longer be able to use your PDM with that pod!** For the time that Pod is active the **AAPS** Dash driver running on your Android phone is now the new PDM for your pod.
+- **DO NOT Throw away your PDM!** It is recommended to keep it around as a backup and for emergencies, for instance when your phone gets lost or **AAPS** is not working correctly.
-**Your pod will not stop delivering insulin when it is not connected to AAPS**. Default basal rates are programmed on the pod on activation as defined in the current active **Profile**. As long as **AAPS** is operational it will send basal rate commands that run for a maximum of 120 minutes. When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod - phone distance) the pod will automatically fall back to default basal rates.
+### Your pod **WILL NOT** stop delivering insulin when it is not connected to AAPS.
+Default basal rates are programmed on the pod on activation as defined in the current active [**Profile**](../SettingUpAaps/YourAapsProfile.md).
+As long as **AAPS** is operational it will send basal rate adjustment commands that run for a maximum of 120 minutes.
+When for some reason the pod does not receive any new commands (for instance because communication was lost due to Pod ➜ phone distance) the pod will automatically fall back to default basal rates as defined in your [**Profile**](../SettingUpAaps/YourAapsProfile.md).
-**AAPS Profile does not support a 30 minute basal rate time frame** If you are new to **AAPS** and are setting up your basal rate **Profile** for the first time, please be aware that basal rates starting on a half-hour basis are not supported, and programmes on an hourly basis. For example, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this im **AAPS**. You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does support this feature.
+### **AAPS Profile(s) do not support 30 minute basal rate time frames**
+If you are new to **AAPS** and are setting up your basal rate [**Profile**](../SettingUpAaps/YourAapsProfile.md) for the first time, please be aware that basal rates starting on a half-hour basis are not supported. For example, on your Omnipod PDM, if you have a basal rate of 1.1 units which starts at 09:30 and has a duration of 2 hours ending at 11:30, it is not possible replicate this exact basil **Profile** in **AAPS**.
+You will need to change this 1.1 unit basal rate to a time range of either 9:00-11:00 or 10:00-12:00. Even though the DASH hardware itself supports the 30 minute basal rate **Profile** increments, **AAPS** does NOT support this feature.
-**0U/h profile basal rates are NOT supported in AAPS** While the DASH does support a zero basal rate, since **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate. A temporary zero basal rate can be achieved through the "Disconnect pump" function or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate. The lowest basal rate allowed in **AAPS** is 0.05U/h.
+### **0U/h Profile basal rates are NOT supported in AAPS**
+While the DASH does support a zero basal rate, **AAPS** uses multiples of the user's **Profile** basal rate to determine automated treatment; it cannot function with a zero basal rate.
+Instead a temporary zero basal rate can be achieved through the "Disconnect pump" function, or through a combination of Disable Loop/Temp Basal Rate or Suspend Loop/Temp Basal Rate.
+**NOTE:** The lowest basal rate allowed by the DASH in **AAPS** is 0.05U/h.
## Selecting Dash in AAPS
-There are **two ways**:
+There are **two** available options to configure Omnipod in **AAPS**:
### Option 1: New installations
-When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**. Select “DASH” when you reach Pump selection.
+When installing **AAPS** for the first time, the **Setup Wizard** will guide new users through key features and installation requirements for **AAPS**.
+Select “DASH” when you reach Pump selection.
-When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (see option 2).
+When in doubt you can also select “Virtual Pump” and select “DASH” later, after setting up **AAPS** (See Option 2).
+(omnipod-dash-option-2-config-builder)=
### Option 2: The Config Builder
On an existing installation you can select the **DASH** pump from the Config builder:
-On the top-left hand corner **hamburger menu** select **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**.
+On the top-left hand corner **hamburger menu** select **Config Builder (1)** ➜ **Pump** ➜ **Dash** ➜ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**.
Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the DASH menu to be displayed as a tab in the **AAPS** interface titled **DASH**. Checking this box will facilitate your access to the DASH commands when using **AAPS**.
-**NOTE:** A faster way to access the [**Dash settings**](#dash-settings) can be found below in the DASH settings section of this document.
+**NOTE:** A faster way to access the [**Dash settings**](#omnipod-dash-settings) can be found below in the DASH settings section of this document.
### Verification of Omnipod Driver Selection
-To verify that you have selected the DASH in **AAPS**, if you have checked the box (4), **swipe to the left** from the **Overview** tab, where you will now see a **DASH** tab on **AAPS**. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left.
+To verify that you have selected the DASH in **AAPS**, if you have **checked the box (4)**, **swipe to the left** from the **Overview** tab, where you will now see a **DASH** tab on **AAPS**. If this box is left unchecked, you’ll find the DASH tab in the hamburger menu upper left.
## Dash Configuration
-Please **swipe left** to the **DASH** tab where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session):
+**Swipe left** to the [**DASH tab**](#omnipod-dash-tab) where you will be able to manage all pod functions (some of these functions are not enabled or visible without an active pod session):
 'Refresh' pod connectivity and status, be able to silence pod alarms when the pod beeps
- 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+ 'Pod Management' (Activate, Deactivate, Play test beep, and Pod history)
+(omnipod-dash-activate-pod)=
### Activate Pod
1. Navigate to the **DASH** tab and click on the **POD MGMT (1)** button, and then click on **Activate Pod (2)**.
-
+ 
+
+ 
+
+2. The **Fill Pod** screen is displayed. Fill a new pod with **at least 80 units** of insulin and listen for two beeps indicating that the pod is ready to be primed.
+
+ ***NOTE:** When calculating the total amount of insulin you need for 3 days, please take into account that priming the pod will use about 3-10 units.*
- 
+ 
-2. The **Fill Pod** screen is displayed. Fill a new pod with at least 80 units of insulin and listen for two beeps indicating that the pod is ready to be primed. When calculating the total amount of insulin you need for 3 days, please take into account that priming the pod will use about 3-10 units.
+ 
- 
+ Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button.
-Ensure that the new pod and the phone running **AAPS** are within close proximity of each other and click the **Next** button.
+ ***NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully.*
-**NOTE**: if the error message below pops up _'Could not find an available pod for activation'_ (this can happen), do not panic. Click on the **Retry** button. In most situations activation will continue successfully.
+ 
-
+3. On the **Initialize Pod** screen, the pod will begin priming (you will hear a click followed by a series of ticking sounds as the pod primes itself).
+ A green checkmark will be shown upon successful priming, and the **Next** button will become enabled. Click on the **Next** button to complete the pod priming initialization and display the **Attach Pod** screen.
-3. On the **Initialize Pod** screen, the pod will begin priming (you will hear a click followed by a series of ticking sounds as the pod primes itself). A green checkmark will be shown upon successful priming, and the **Next** button will become enabled. Click on the **Next** button to complete the pod priming initialization and display the **Attach Pod** screen.
+  
- 
+4. Next, prepare the infusion site ready to receive the new pod. Wash hands to avoid any risk of infection. Clean the infusion site by either using soap and water or an alcohol wipe to disinfect and let the skin air dry completely before proceeding.
+ If you get skin irritation from the adhesive consider using a Barrier Wipe or Barrier Spray.
-4. Next, prepare the infusion site ready to receive the new pod. Wash hands to avoid any risk of infection. Clean the infusion site by either using soap and water or an alcohol wipe to disinfect and let the skin air dry completely before proceeding. Remove the pod's blue plastic needle cap. If you see something that sticks out of the pod or unusual, cancel the process and start with a new pod. If everything looks OK, proceed to take off the white paper backing from the adhesive and apply the pod to the selected site on your body. When finished, click on the **Next** button.
+ Remove the pod's blue plastic needle cap. If you see something that sticks out of the pod or it looks unusual, **STOP** the process and start with a new pod. If everything looks **OK**, proceed to take off the white paper backing from the adhesive and stick the pod to the selected site on your body.
-
+ When finished, click on the **Next** button.
-5. The **Attach Pod** dialog box will now appear. **click on the OK button ONLY if you are ready to deploy the cannula**.
+ 
-
+6. The **Attach Pod** dialog box will now appear. **click on the OK button ONLY if you are ready to deploy the cannula!**
-6. After pressing **OK**, it may take some time before the DASH responds and inserts the cannula (1-2 minutes maximum). Be patient.
+ 
- *NOTE: Before the cannula is inserted, it is good practice to pinch the skin near the cannula insertion point. This ensures a smooth insertion of the needle and will decrease your chances of developing occlusions.*
+7. After pressing **OK**, it may take some time before the DASH responds and inserts the cannula (1-2 minutes maximum). **Be patient!**
- 
+ ***NOTE:** Before the cannula is inserted, it is good practice to pinch the skin near the cannula insertion point. This ensures a smooth insertion of the needle and will decrease your chances of developing occlusions.*
-7. A green checkmark appears, and the **Next** button becomes enabled upon successful cannula insertion. Click on the **Next** button.
+  
-
+8. A green checkmark is shown on the screen, and the **Next** button becomes available to select upon successful cannula insertion.
+ Click on the **Next** button.
-9. The **Pod activated** screen is displayed. Click on the green **Finished** button. Congratulations! You have now started a new pod session.
+ 
-
+1. The **Pod activated** screen is displayed.
-10. The **Pod management** menu screen should now display the **Activate Pod (1)** button *disabled* and the **Deactivate Pod (2)** button *enabled*. This is because a pod is now active and you cannot activate an additional pod without deactivating the currently active pod first.
+ Click on the green **Finished** button.
+
+ Congratulations! You have now started a new pod session.
+
+ 
+
+2. The **Pod management** menu screen should now display the **Activate Pod (1)** button *disabled* and the **Deactivate Pod (2)** button *enabled*. This is because a pod is now active and you cannot activate an additional pod without deactivating the currently active pod first.
Click on the back button on your phone to return to the **DASH** tab screen which will now display Pod information for your active pod session, including current basal rate, pod reservoir level, insulin delivered, pod errors and alerts.
- For more details on the information displayed go to the [**DASH Tab**](#dash-tab) section of this document.
+ ***NOTE:** For more details on the information displayed go to the [**DASH Tab**](#omnipod-dash-tab) section of this document.*
-
+ 
- 
+ 
-It is good practice to export settings AFTER activating the pod. Export settings should be done at each pod change and once a month, copy the exported file to your internet drive. see [**Export settings Doc**](../Maintenance/ExportImportSettings.md).
+ ***NOTE:** It is good practice to export settings AFTER activating the pod. Settings should be exported after each pod change and once a month, ensure you copy the exported settings file to a cloud storage location (e.g. Google Drive) or somewhere off your phone in case you loose your phone (see [**Export settings**](../Maintenance/ExportImportSettings.md)).*
-(OmnipodDASH-deactivate-pod)=
+(omnipod-dash-deactivate-pod)=
### Deactivate Pod
-Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of pod usage.
+Under normal circumstances, the expected lifetime of a pod is three days (72 hours) and an additional 8 hours after the pod expiration warning for a total of 80 hours of total pod usage.
To deactivate a pod (either from expiration or from a pod failure):
-1. Go to the **DASH** tab, click on the **POD MGMT (1)** button, on the **Pod management** screen click on the **Deactivate Pod (2)** button.
+1. Go to the **DASH** tab, click on the **POD MGMT (1)** button, on the **Pod Management** screen click on the **Deactivate Pod (2)** button.
+
+ 
-
+ 
- 
+2. On the **Deactivate Pod** screen, click on the **Next** button to begin the process of deactivating the pod.
-2. On the **Deactivate Pod** screen, click on the **Next** button to begin the process of deactivating the pod. You will receive a confirmation beep from the pod that deactivation was successful.
+ You will receive a confirmation beep from the pod that deactivation was successful.
-
+ 
- 
+ 
+3. A green checkmark will be displayed upon successful deactivation. Click on the **Next** button to display the pod deactivated screen.
-3. A green checkmark will appear upon successful deactivation. Click on the **Next** button to display the pod deactivated screen. You may now remove your pod as the active session has been deactivated.
+ You may now remove your pod as the active session has been deactivated.
-
+ 
4. Click on the green button to return to the **Pod Management** screen.
-
+ 
-5. You are now on the **Pod Management** menu; press the back button on your phone to return to the **DASH** tab. Verify that the **Pod status:** field displays a **No active Pod** message.
+5. You are now on the **Pod Management** menu; press the back button on your phone to return to the **DASH** tab.
-
+ Verify that the **Pod status:** field displays a **No active Pod** message.
- 
+ 
+
+ 
+
+
+(omnipod-dash-resuming-insulin-delivery)=
### Resuming Insulin Delivery
-**Note**: During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile** as delivery can be suspended. Read [**Delivery suspended**](#delivery-suspended) in the troubleshooting section for more details.
+**NOTE**: During **Profile Switches**, like when using the PDM, AAPS must suspend delivery on the Pod before setting the new basal **Profile**. If communication fails between the suspend and resume commands, then delivery can stay suspended, Read [**Delivery suspended**](#omnipod-dash-delivery-suspended) in the troubleshooting section for more details.
-Use this command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
+When insulin delivery is suspended you will need to issue a command to instruct the active, currently suspended pod to resume insulin delivery. After the command is successfully processed, insulin will resume normal delivery using the current basal rate based on the current time from the active basal **Profile**. The pod will again accept commands for bolus, **TBR**, and **SMB**.
1. Go to the **DASH** tab and ensure the **Pod status (1)** field displays **SUSPENDED**, then press the **RESUME DELIVERY (2)** button to start the process to instruct the current pod to resume normal insulin delivery. A message **RESUME DELIVERY** will display in the **Pod Status (3)** field.
- 
+  
2. When the Resume delivery command is successful, a confirmation dialog will display the message **Insulin delivery has been resumed**. Click **OK** to confirm and proceed.
-
+ 
3. The **DASH** tab will update the **Pod status (1)** field to display **RUNNING,** and the **Resume Delivery** button will no longer be displayed
-
+ 
-### Silencing Pod Alerts
+(omnipod-dash-silencing-pod-alerts)=
-*NOTE - The SILENCE ALERTS button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the SILENCE ALERTS button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.*
+### Silencing Pod Alerts
The process below will show you how to acknowledge and dismiss pod beeps when the active pod time reaches the warning time limit before the pod expiration of 72 hours (3 days). This warning time limit is defined in the **Hours before shutdown** Dash alerts setting. The maximum life of a pod is 80 hours (3 days 8 hours), however Insulet recommends not exceeding the 72 hours (3 days) limit.
-1. When the defined **Hours before shutdown** warning time limit is reached, the pod will issue warning beeps to inform you that it is approaching its expiration time and pod change will be required soon. You can verify this on the **DASH** tab, the **Pod expires: (1)** field will show the exact time the pod will expire (72 hours after activation), and the text will turn **red** after this time has passed. Under the **Active Pod alerts (2)** field the status message **Pod will expire soon** is displayed. This also will trigger displaying the **SILENCE ALERTS (3)** button.
+***NOTE**: The **SILENCE ALERTS (3)** button is only available on the **DASH** tab when the pod expiration or low reservoir alert has been triggered. If the **SILENCE ALERTS** button is not visible and you hear beep sounds from the pod, try to 'Refresh pod status'.*
-
+1. When the defined **Hours before shutdown** warning time limit is reached, the pod will issue warning beeps to inform you that it is approaching its expiration time and a pod change will be required soon.
+ You can verify this on the **DASH** tab, the **Pod expires: (1)** field will show the exact time the pod will expire (72 hours after activation), and the text will turn **red** after this time has passed.
+ Under the **Active Pod alerts (2)** field the status message **Pod will expire soon** is displayed. This also will trigger displaying the **SILENCE ALERTS (3)** button.
-2. Go to the **DASH** tab and press the **SILENCE ALERTS (2)** button . **AAPS** sends the command to the pod to deactivate the pod expiration warning beeps and updates the **Pod status (1)** field with **ACKNOWLEDGE ALERTS**.
+ 
-
+2. Go to the **DASH** tab and press the **SILENCE ALERTS (2)** button. **AAPS** sends the command to the pod to deactivate the pod expiration warning beeps and updates the **Pod status (1)** field with **ACKNOWLEDGE ALERTS**.
-3. Upon **successful deactivation** of the alerts, **2 beeps** will be issued by the active pod and a confirmation dialog will display the message **Activate alerts have been Silenced**. Click the **OK** button to confirm and dismiss the dialog.
+ 
+3. Upon **successful deactivation** of the alerts, **2 beeps** will be issued by the active pod and a confirmation dialog will display the message **Activate alerts have been Silenced**. Click the **OK** button to confirm and dismiss the dialog.
-
+ 
4. Go to the **DASH** tab. Under the **Active Pod alerts** field, the warning message is no longer displayed, and the active pod will no longer issue pod expiration warning beeps.
-(OmnipodDASH-view-pod-history)=
+(omnipod-dash-view-pod-history)=
### View Pod History
@@ -223,108 +285,125 @@ This section explains how to review your active pod history and filter by differ
This feature is helpful in verifying boluses, TBRs and basal commands that were sent to the pod. The remaining categories are useful for troubleshooting issues and determining the order of events that occurred leading up to a failure.
-*NOTE:* **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**.
+***NOTE:** **Only the last command can be uncertain**. New commands *will not be sent* until the **last 'uncertain' command becomes 'confirmed' or 'denied'**. The way to 'fix' uncertain commands is to **'refresh pod status'**.*
1. Go to the **DASH** tab and press the **POD MGMT (1)** button to access the **Pod Management** menu and then press the **Pod history (2)** button to access the pod history screen.
-
+ 
+ 
+2. On the **Pod history** screen, the default category of **All (1)** is displayed, showing the **Date and Time (2)** of all pod **Actions (3)** and **Results (4)** in reverse chronological order. Use your phone’s **back button 2 times** to return to the **DASH** tab in the main **AAPS** interface.
+  
- 
+(omnipod-dash-tab)=
+## DASH Tab
+Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface.
-2. On the **Pod history** screen, the default category of **All (1)** is displayed, showing the **Date and Time (2)** of all pod **Actions (3)** and **Results (4)** in reverse chronological order. Use your phone’s **back button 2 times** to return to the **DASH** tab in the main **AAPS** interface.
+***NOTE:** If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.*
+
- 
+### Fields
-(OmnipodDASH-dash-tab)=
-## DASH Tab
-Below is an explanation of the layout and meaning of the icons and status fields on the **DASH** tab in the main AAPS interface.
+- **Bluetooth Address:** Displays the current bluetooth address of the connected Pod.
-*NOTE: If any message in the **DASH** tab status fields report (uncertain), then you will need to press the Refresh button to clear it and refresh the pod status.*
+- **Bluetooth Status:** Displays the current connection status.
-
+- **Sequence Number:** Displays the sequence number of the active POD.
-### Fields
+- **Firmware Version:** Displays the firmware version for the active connection.
+
+- **Time on Pod:** Displays the current time on the Pod.
+
+- **Pod status:** Displays the Pod status.
+
+- **Last connection:** Displays time of last communication with the Pod.
+
+ - *Moments ago* - less than 20 seconds ago.
+
+ - *Less than a minute ago* - more than 20 seconds but less than 60 seconds ago.
+
+ - *1 minute ago* - more than 60 seconds but less than 120 seconds (2 min)
+
+ - *XX minutes ago* - more than 2 minutes ago as defined by the value of XX
+
+- **Last bolus:** Displays the amount of the last bolus sent to the active pod and how long ago it was issued in parenthesis.
+
+- **Base Basal rate:** Displays the basal rate programmed for the current time from the basal rate profile.
-* **Bluetooth Address:** Displays the current bluetooth address of the connected Pod.
-* **Bluetooth Status:** Displays the current connection status.
-* **Sequence Number:** Displays the sequence number of the active POD.
-* **Firmware Version:** Displays the firmware version for the active connection.
-* **Time on Pod:** Displays the current time on the Pod.
-* **Pod expires:** Displays the date and time when the Pod will expire.
-* **Pod status:** Displays the Pod status.
-* **Last connection:** Displays time of last communication with the Pod.
+- **Temp basal rate:** Displays the currently running Temporary Basal Rate in the following format
+ - {Units per hour} @{TBR start time} ({minutes run}/{total minutes TBR will be run})
- - *Moments ago* - less than 20 seconds ago.
- - *Less than a minute ago* - more than 20 seconds but less than 60 seconds ago.
- - *1 minute ago* - more than 60 seconds but less than 120 seconds (2 min)
- - *XX minutes ago* - more than 2 minutes ago as defined by the value of XX
+ - Example:* 0.00U/h @18:25 ( 90/120 minutes)
-* **Last bolus:** Displays the amount of the last bolus sent to the active pod and how long ago it was issued in parenthesis.
-* **Base Basal rate:** Displays the basal rate programmed for the current time from the basal rate profile.
-* **Temp basal rate:** Displays the currently running Temporary Basal Rate in the following format
+- **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
+
+- **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
+
+- **Errors:** Displays the last error encountered. Review the [Pod history](#omnipod-dash-view-pod-history) and log files for past errors and more detailed information.
+
+- **Active pod alerts:** Reserved for currently running alerts on the active pod.
- - {Units per hour} @{TBR start time} ({minutes run}/{total minutes TBR will be run})
- - *Example:* 0.00U/h @18:25 ( 90/120 minutes)
-* **Reservoir:** Displays over 50+U left when more than 50 units are left in the reservoir. Below 50 U, the exact units are displayed.
-* **Total delivered:** Displays the total number of units of insulin delivered from the reservoir. This includes insulin used for activating and priming.
-* **Errors:** Displays the last error encountered. Review the [Pod history](#view-pod-history) and log files for past errors and more detailed information.
-* **Active pod alerts:** Reserved for currently running alerts on the active pod.
### Buttons
+ Sends a refresh command to the active pod to update communication.
+
+ - *Use to refresh the pod status and dismiss status fields that contain the text (uncertain).*
+
+ - *See the [Troubleshooting](#omnipod-dash-troubleshooting) section below for additional information.*
- : Sends a refresh command to the active pod to update communication.
+ Navigates to the Pod management menu.
- * Use to refresh the pod status and dismiss status fields that contain the text (uncertain).
- * See the Troubleshooting section below for additional information.
+ When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..).
- : Navigates to the Pod management menu.
+ - *Button is displayed only when pod time is past expiration warning time.*
+ - *Upon successful dismissal, this icon will no longer appear.*
- : When pressed this will disable the pod alerts beeps and notifications (expiry, low reservoir..).
+ Resumes the currently suspended insulin delivery in the active pod.
- * Button is displayed only when pod time is past expiration warning time.
- * Upon successful dismissal, this icon will no longer appear.
- : Resumes the currently suspended insulin delivery in the active pod.
### Pod Management Menu
-Below is the meaning of the icons on the **Pod Management** menu accessed by pressing **POD MGMT (1)** button from the **DASH** tab.
+Below is describes the purpose of each icon on the **Pod Management** menu, accessed by pressing **POD MGMT (1)** button from the **DASH** tab.
- 
+
-* 2 - [**Activate Pod**](#activate-pod) : Primes and activates a new pod.
-* 3 - [**Deactivate Pod**](#deactivate-pod) : Deactivates the currently active pod.
-* 4 - **Play Test Beep** : Plays a single test beep on the pod when pressed.
-* 5 - [**Pod history**](#view-pod-history) : Displays the active pod activity history.
+**The table below describes each button and it's function:**
-(DanaRS-Insulin-Pump-dash-settings)=
+| Button | Function |
+| ------ | --------------------------------------------------------------------------------------------- |
+| 1 | Access the Pod Mgmt settings |
+| 2 | [**Activate Pod**](#omnipod-dash-activate-pod): Primes and activates a new pod. |
+| 3 | [**Deactivate Pod**](#omnipod-dash-deactivate-pod): Deactivates the currently active pod. |
+| 4 | **Play Test Beep** : Plays a single test beep on the pod when pressed. |
+| 5 | [**Pod history**](#omnipod-dash-view-pod-history) : Displays the active pod activity history. |
-## Dash Settings
-The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)**\ ➜\ **Pump**\ ➜\ **Dash**\ ➜\ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**.
+(omnipod-dash-settings)=
-
+## Dash Settings
+The Dash driver settings are configurable from the top-left hand corner **hamburger menu** under **Config Builder (1)** ➜ **Pump** **Dash** ➜ **Settings Gear (3)** by selecting the **radio button (2)** titled **Dash**. Selecting the **checkbox (4)** next to the **Settings Gear (3)** will allow the Dash menu to be displayed as a tab in the **AAPS** interface titled **DASH**.
+
-**NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu.
+***NOTE:** A faster way to access the **Dash settings** is by accessing the **3 dot menu (1)** in the upper right hand corner of the **DASH** tab and selecting **Dash preferences (2)** from the dropdown menu.*
The settings groups are listed below; you can enable or disable via a toggle switch for most entries described below:
-*NOTE: An asterisk (\*) denotes the default setting is enabled.*
+***NOTE:** An asterisk (\*) denotes the default setting is enabled.*
### Confirmation beeps
@@ -332,10 +411,15 @@ The settings groups are listed below; you can enable or disable via a toggle swi
Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery and changes.
-* **Bolus beeps enabled:** Enable or disable confirmation beeps when a bolus is delivered.
-* **Basal beeps enabled:** Enable or disable confirmation beeps when a new basal rate is set, active basal rate is canceled or current basal rate is changed.
-* **SMB beeps enabled:** Enable or disable confirmation beeps when a SMB is delivered.
-* **TBR beeps enabled:** Enable or disable confirmation beeps when a TBR is set or canceled.
+**Bolus beeps enabled:** Enable or disable confirmation beeps when a bolus is delivered.
+
+**Basal beeps enabled:** Enable or disable confirmation beeps when a new basal rate is set, active basal rate is canceled or current basal rate is changed.
+
+**SMB beeps enabled:** Enable or disable confirmation beeps when a SMB is delivered.
+
+**TBR beeps enabled:** Enable or disable confirmation beeps when a TBR is set or canceled.
+
+
### Alerts
@@ -343,41 +427,51 @@ Provides confirmation beeps from the pod for bolus, basal, SMB, and TBR delivery
Provides **AAPS** alerts for pod expiration, shutdown, low reservoir based on the defined threshold units.
-*Note an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.*
+***NOTE:** an AAPS notification will ALWAYS be issued for any alert after the initial communication with the pod since the alert was triggered. Dismissing the notification will NOT dismiss the alert UNLESS automatically acknowledge Pod alerts is enabled. To MANUALLY dismiss the alert you must visit the **DASH** tab and press the **Silence ALERTS button**.*
+
+**Expiration reminder enabled:** Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached.
+
+**Hours before shutdown:** Defines the number hours before the active pod shutdown occurs, which will then trigger the expiration reminder alert.
+
+**Low reservoir alert enabled:** Enable or disable an alert when the pod's remaining units low reservoir limit is reached as defined in the Number of units field.
+
+**Number of units:** The number of units at which to trigger the pod low reservoir alert.
+
-* **Expiration reminder enabled:** Enable or disable the pod expiration reminder set to trigger when the defined number of hours before shutdown is reached.
-* **Hours before shutdown:** Defines the number hours before the active pod shutdown occurs, which will then trigger the expiration reminder alert.
-* **Low reservoir alert enabled:** Enable or disable an alert when the pod's remaining units low reservoir limit is reached as defined in the Number of units field.
-* **Number of units:** The number of units at which to trigger the pod low reservoir alert.
### Notifications
-The Notification section allows the user to so select their preferred notifications and audible phone alerts when it is uncertain if TBR, SMB, or bolus, and delivery suspended events were successful.
+The Notification section allows the user to select their preferred notifications and audible phone alerts when AAPS is uncertain about the status of TBR, SMB, or bolus, and when delivery suspended events were successful.
+
+***NOTE:** These are notifications only, no audible beep alerts are made.*
+
+**Sound for uncertain TBR notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if a TBR was successfully set.
-*NOTE: These are notifications only, no audible beep alerts are made.*
+**Sound for uncertain SMB notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if an SMB was successfully delivered.
-* **Sound for uncertain TBR notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if a TBR was successfully set.
-* **Sound for uncertain SMB notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS**is uncertain if an SMB was successfully delivered.
-* **Sound for uncertain bolus notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS**is uncertain if a bolus was successfully delivered.
-* **Sound when delivery suspended notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when suspend delivery was successfully delivered.
+**Sound for uncertain bolus notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when **AAPS** is uncertain if a bolus was successfully delivered.
+
+**Sound when delivery suspended notifications enabled:** Enable or disable this setting to trigger an audible alert and visual notification when suspend delivery was successfully delivered.
## Actions (ACT) Tab
-This tab is well documented in the main**AAPS**documentation but there are a few items on this tab that are specific to how the DASH differs from tube based pumps, especially after the processes of applying a new pod.
+This tab is well documented in the main **AAPS** documentation but there are a few items on this tab that are specific to how the DASH differs from tube based pumps, especially after the processes of applying a new pod.
-1. Go to the **Actions (ACT)** tab in the main **AAPS**interface.
+1. Go to the **Actions (ACT)** tab in the main **AAPS** interface.
2. Under the **Careportal (1)** section the **Insulin** and **Cannula** fields will have their **age reset** to 0 days and 0 hours **after each pod change**. This is done because of how the Omnipod pump is built and operates. Since the pod inserts the cannula directly into the skin at the site of the pod application, a traditional tube is not used in Omnipod pumps. *Therefore after a pod change the age of each of these values will automatically reset to zero.* **Pump battery age** is not reported as the battery in the pod will always be more than the life of the pod (maximum 80 hours). The **pump battery** and **insulin reservoir** are self contained inside of each pod.
-
+ 
### Level
**Insulin Level**
-Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left. The DASH overview tab will display as described the below:
+Insulin level displayed is the amount reported by DASH. However, the pod only reports the actual insulin reservoir level when it is below 50 units. Until then “Above 50 units” will be displayed. The amount reported is not exact: when the pod reports ‘empty’ in most cases the reservoir will still have some additional units of insulin left.
+
+The DASH overview tab will display as described the below:
* **Above 50 Units** - The pod reports more than 50 units currently in the reservoir.
* **Below 50 Units** - The amount of insulin remaining in the reservoir as reported by the Pod.
@@ -386,53 +480,77 @@ Additional note:
* **SMS** - Returns value or 50+U for SMS responses
* **Nightscout** - Uploads value of 50 when over 50 units to Nightscout (version 14.07 and older). Newer versions will report a value of 50+ when over 50 units.
+(omnipod-dash-troubleshooting)=
+
## Troubleshooting
+(omnipod-dash-delivery-suspended)=
+
+This section covers common known issues and solutions for Omnipod DASH use with AAPS. There is also [General Troubleshooting](../GettingHelp/GeneralTroubleshooting.md) section in the documentation that should be reviewed as it covers relevant topics for some Pod issues too.
+
+---
+
+(omnipod-dash-bluetooth-related-issues)=
+
+## **Bluetooth related issues**
+
+For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md)
+
+---
### Delivery suspended
- * There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
- * During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile**. If communication fails between the two commands, then delivery can stay suspended. When this happens:
+ - There is no suspend button anymore. If you want to "suspend" the pod, you can set a zero **TBR** for x minutes.
+ - During **Profile Switches**, DASH must suspend delivery before setting the new basal **Profile**. If communication fails between the two commands, then delivery can stay suspended. When this happens:
- There will be no insulin delivery, that includes Basal, SMB, Manual bolusing etc.
- There might be notification that one of the commands is unconfirmed: this depends on when the failure happened.
- **AAPS** will try to set the new basal profile every 15 minutes.
- **AAPS** will show a notification informing that the delivery is suspended every 15 minutes, if the delivery is still suspended (resume delivery failed).
- - The [**Resume delivery**](#resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
+ - The [**Resume delivery**](#omnipod-dash-resuming-insulin-delivery) button will be active if the user chooses to resume delivery manually.
- If **AAPS** fails to resume delivery on its own (this happens if the pod is unreachable, sound is muted, etc), the pod will start beeping 4 times every minute for 3 minutes, then repeated every 15 minutes if delivery is still suspended for more than 20 minutes.
- * For unconfirmed commands, "refresh pod status" should confirm/deny them.
+ - For unconfirmed commands, "refresh pod status" should confirm/deny them.
-**Note:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, **so you need to check !**
+*****NOTE:** When you hear beeps from the pod, do not assume that delivery will continue without checking the phone, delivery might stay suspended, ***so you need to check !******
+---
### Pod Failures
-Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself. It is best practice not to call these into Insulet, since AAPS is not an approved use case. A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause.
+- Pods fail occasionally due to a variety of issues, including hardware issues with the Pod itself.
+- It is best practice not to raise support / replacement cases with Insulet, since AAPS is not an approved method of using the Pods.
+- A list of fault codes can be [**found here**](https://github.com/openaps/openomni/wiki/Fault-event-codes) to help determine the cause.
+---
### Preventing error 49 pod failures
This failure is related to an incorrect pod state for a command or an error during an insulin delivery command. This is when the driver and Pod disagree on the actual state. The Pod (out of a built-in safety measure) then reacts with an unrecoverable error code 49 (0x31) ending up with what is know as a “screamer”: the long irritating beep that can only be stopped by punching a hole at the appropriate location at the back of the Pod. The exact origin of a “49 pod failure” often is hard to trace. In situations that are suspected for this failure to occur (for instance on application crashes, running a development version or re-installation).
+---
+
### Pump Unreachable Alerts
-When no communication can be established with the pod for a preconfigured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences**\ ➜\ **Local Alerts**\ ➜\ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes.
+When no communication can be established with the pod for a pre-configured time a “Pump unreachable” alert will be raised. Pump unreachable alerts can be configured by going to the top right-hand side three-dot menu, selecting **Preferences** ➜ **Local Alerts** ➜ **Pump unreachable threshold [min]**. Recommended value is alerting after **120** minutes.
+---
### Export Settings
Exporting **AAPS** settings enables you to restore all your settings, and maybe more importantly, all your Objectives. You may need to restore settings to the “last known working situation” or after uninstalling/reinstalling **AAPS** or in case of phone loss, reinstalling on the new phone.
-Note: The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active.
+***NOTE:** The active pod information is included in the exported settings. If you import an "old" exported file, your actual pod will "die". There is no other alternative. In some cases (like a _programmed_ phone change), you may need to use the exported file to restore **AAPS'** settings **while keeping the current active Pod**. In this case it is important to only use the recently exported settings file containing the pod currently active.*
**It is good practice to do an export immediately after activating a pod**. This way you will always be able to restore the current active pod in case of a problem. For instance when moving to another backup phone.
-Regularly copy your exported settings to a safe place (as a cloud drive) that can be accessible by any phone when needed (e.g. in case of a phone loss or factory reset of the actual phone).
+Regularly (after each export preferably) copy your exported settings to a safe place (a cloud drive e.g. Google Drive) that is accessible by any phone when needed. This allows you to restore to a phone from anywhere in case of a phone loss or factory reset of your phone while you are not at home.
+---
### Import Settings
-**WARNING** Please note that importing settings will possibly import an outdated Pod status. As a result, there is a risk of losing the active Pod! (see **Exporting Settings**). It is better to only try it when no other options are available.
-
-When importing settings with an active Pod, make sure the export was done with the currently active pod.
+**WARNING**: Please note that importing settings will possibly import an outdated Pod status (depending when you made the last export/backup).
+As a result, there is a **risk of losing the active Pod!** (see **Exporting Settings**).
+1. Only try an import when no other options are available.
+2. When importing settings with an active Pod, make sure the export was done with the currently active pod.
**Importing while on an active Pod:** (you risk losing the Pod!)
-1. Make sure you are importing settings that were recently exported with the currently active Pod.
+1. **Make sure you are importing settings that were recently exported with the currently active Pod!**
2. Import your settings.
3. Check all preferences.
@@ -443,19 +561,25 @@ When importing settings with an active Pod, make sure the export was done with t
3. Check all preferences.
4. You may need to **Deactivate** the "non existing" pod if the imported settings included any active pod data.
+---
### Importing settings that contain Pod state from an inactive Pod
When importing settings containing data for a Pod that is no longer active, AAPS will try to connect with it, which will obviously fail. You can not activate a new Pod in this situation.
-To remove the old pod session “try” to de-activate the Pod. The de-activation will fail. Select “Retry”. After the second or third retry you will get the option to remove the pod. Once the old pod is removed you will be able to activate a new pod.
+To remove the old pod session:
+1. “try” to de-activate the Pod. The de-activation will likely fail.
+2. Select “Retry”.
+3. After the second or third retry you will get the option to remove the pod.
+4. Once the old pod is removed you will be able to activate a new pod.
+---
### Reinstalling AAPS
-When uninstalling**AAPS** you will lose all your settings, objectives and the current Pod session. To restore them make sure you have a recent exported settings file available!
+When uninstalling **AAPS** you will lose all your settings, objectives and the current Pod session. **To restore them make sure you have a recent exported settings file available!**
When on an active Pod, make sure that you have an export for the current pod session or you will lose the currently active pod when importing older settings.
-1. Export your settings and store a copy in a safe place.
+1. Export your settings and store a copy in a safe place (e.g Google Drive).
2. Uninstall **AAPS** and restart your phone.
3. Install the new version of **AAPS**.
4. Import your settings.
@@ -463,9 +587,10 @@ When on an active Pod, make sure that you have an export for the current pod ses
6. Activate a new pod.
7. When done: Export current settings.
+---
### Updating AAPS to a newer version
-In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session.
+In most cases there is no need to uninstall. You can do an “in-place” install by starting the installation for the new version. This is also possible when on an active Pod session.
1. Export your settings.
2. Install the new **AAPS** version.
@@ -473,21 +598,39 @@ In most cases there is no need to uninstall. You can do an “in-place” instal
4. RESUME the Pod or activate a new pod.
5. When done: Export current settings.
+---
### Omnipod driver alerts
-Please note that the Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action to take to resolve the cause of the triggered alert. A summary of the main alerts that you may encounter is listed below:
+The Omnipod Dash driver presents a variety of unique alerts on the **Overview tab**, most of them are informational and can be dismissed while some provide the user with an action requiring their input to resolve the cause of the triggered alert.
+
+A summary of the main alerts that you may encounter is listed below:
-* No active Pod session detected. This alert can temporarily be dismissed by pressing **SNOOZE** but it will keep triggering as long as a new pod has not been activated. Once activated this alert is automatically silenced.
-* Pod suspended Informational alert that pod has been suspended.
-* Setting basal **Profile** failed : Delivery might be suspended! Please manually refresh the Pod status from the Omnipod tab and resume delivery if needed.. Informational alert that the Pod basal **Profile** setting has failed, and you will need to hit *Refresh* on the Omnipod tab.
-* Unable to verify whether **SMB** bolus succeeded. If you are sure that the Bolus didn't succeed, you should manually delete the SMB entry from Treatments. Alert that the **SMB** bolus command success could not be verified, you will need to verify the *Last bolus* field on the DASH tab to see if **SMB** bolus succeeded and if not remove the entry from the Treatments tab.
-* Uncertain if "task bolus/TBR/SMB" completed, please manually verify if it was successful.
+- No active Pod session detected. This alert can temporarily be dismissed by pressing **SNOOZE** but it will keep triggering as long as a new pod has not been activated. Once activated this alert is automatically silenced.
+- Pod suspended Informational alert that pod has been suspended.
+- Setting basal **Profile** failed : Delivery might be suspended! Please manually refresh the Pod status from the Omnipod tab and resume delivery if needed.. Informational alert that the Pod basal **Profile** setting has failed, and you will need to hit *Refresh* on the Omnipod tab.
+- Unable to verify whether **SMB** bolus succeeded. If you are sure that the Bolus didn't succeed, you should manually delete the SMB entry from Treatments. Alert that the **SMB** bolus command success could not be verified, you will need to verify the *Last bolus* field on the DASH tab to see if **SMB** bolus succeeded and if not remove the entry from the Treatments tab.
+- Uncertain if "task bolus/TBR/SMB" completed, please manually verify if it was successful.
+
+(omnipod-dash-where-to-get-help-for-dash)=
## Where to get help for DASH
All of the development work for the DASH is done by the community on a **volunteer** basis; please keep this in mind and use the following guidelines before requesting assistance:
- **Level 0:** Read the relevant section of this documentation to ensure you understand how the functionality with which you are experiencing difficulty is supposed to work.
-- **Level 1:** If you are still encountering problems that you are not able to resolve by using this document, then please go to the *#AAPS* channel on **Discord** by using [this invite link](https://discord.gg/4fQUWHZ4Mw).
+- **Level 1:** If you are still encountering problems that you are not able to resolve by using this document, then please go to the *#AAPS* channel on **Discord** by using [this invite link](https://discord.gg/4fQUWHZ4Mw). There are also numerous Facebook and other groups you can ask in too (see [**Getting Help**](../GettingHelp/WhereCanIGetHelp.md))
- **Level 2:** Search existing issues to see if your issue has already been reported at [Issues](https://github.com/nightscout/AndroidAPS/issues) if it exists, please confirm/comment/add information on your problem. If not, please create a [new issue](https://github.com/nightscout/AndroidAPS/issues) and attach [your log files](../GettingHelp/AccessingLogFiles.md).
- **Be patient - most of the members of our community consist of good-natured volunteers, and solving issues often requires time and patience from both users and developers.**
+
+When requesting help come prepared with the following information to help those in the community with your specific questions and problems:
+- Android phone make and model
+- Android OS version (e.g 15 or 16)
+ - Did you recently upgrade your Android OS version?
+- The version of **AAPS** you are running
+- Plain english description of the problem you are facing considering some of the following things
+ - Was it working before now?
+ - When did it work or not work?
+ - Did you make any changes to configuration or profile settings?
+ - Did you pair a new bluetooth device?
+ - Did you upgrade or install a new app?
+ - How long was it working before it stopped working?
diff --git a/docs/CROWDIN/it/DailyLifeWithAaps/AapsScreens.md b/docs/CROWDIN/it/DailyLifeWithAaps/AapsScreens.md
index 67962f7e850a..fc033b4bb40a 100644
--- a/docs/CROWDIN/it/DailyLifeWithAaps/AapsScreens.md
+++ b/docs/CROWDIN/it/DailyLifeWithAaps/AapsScreens.md
@@ -8,7 +8,7 @@
(AapsScreens-the-homescreen)=
## Panoramica
-
+
Questa è la prima schermata che si incontra quando si apre **AAPS**, e contiene la maggior parte delle informazioni di cui si avrà bisogno di giorno in giorno.
@@ -85,13 +85,13 @@ The blocks in the middle shows:
On the right side, an icon shows the loop status:
-1. Green circle = loop running
-2. Green circle with dotted line = [low glucose suspend (LGS)](#objectives-objective6)
+1. Green circle = [closed loop](#KeyAapsFeatures-ClosedLoop), loop running
+2. Purple circle with dotted line = [low glucose suspend (LGS)](#KeyAapsFeatures-LGS)
3. Red circle = loop disabled (not working permanently)
4. Red circle = loop suspended (temporarily paused but basal insulin will be given) - remaining time is shown below icon
5. Grey circle = pump disconnected (temporarily no insulin dosage at all) - remaining time is shown below icon
6. Orange circle = super bolus running - remaining time is shown below icon
-7. Blue circle with dotted line = open loop
+7. Blue circle with dotted line = [open loop](#KeyAapsFeatures-OpenLoop)
Short press or Long press the icon to open the Loop dialog to switch loop mode (Close, Low Glucose Suspend, Open or Disable), suspend / re-enable loop or disconnect / reconnect pump.
@@ -206,22 +206,28 @@ Depending on the pump you use, you may not have all of these icons.
The graph shows your blood glucose (BG) as read from your glucose monitor (CGM).
-Notes entered in action tab such as fingerstick calibrations and carbs entries as well as profile switches are shown here.
-
Use the menu on top left of the graph or long press anywhere on the graph to change the timescale. You can choose between 6, 12, 18 or 24 hours.
The green area reflects your target range.
-Blue triangles show [SMB](#Open-APS-features-super-micro-bolus-smb) - if enabled in [Preferences > OpenAPS SMB](#Preferences-openaps-smb-settings).
+This information is also shown on this graph :
+* Boluses: blue triangle on the BG curve and insulin amount
+* Carbs entries: orange triangle on the BG curve and carb amount
+* Target as defined in the profile or modified by temporary target: green line
+* Profile switches: star at the top of the graph
+* Loop status: color line at the top of the graph when the status is anything else than closed loop - see [Loop status](#AapsScreens-loop-status) for the colors
+* [SMB](#Open-APS-features-super-micro-bolus-smb) - if enabled in [Preferences > OpenAPS SMB](#Preferences-openaps-smb-settings): blue triangles at the bottom of the graph
(AapsScreens-activate-optional-information)=
#### Activate optional information
-On the main graph, you can switch on these optional information:
-* Predictions
-* Treatments
+Using the top right arrow, you can switch on these optional information:
+* Predictions (see below)
+* Treatments : notes entered in action tab: grey, orange or red dot depending on the severity, as well as fingerstick calibrations: red dot
* Basals
-* Activity - insulin activity curve
+ * As defined in the profile: blue dotted line at the bottom of the graph
+ * Actually delivered basal: blue plain line with blue background
+* Activity - insulin activity curve: yellow line
To show this information, click the triangle on the right side of the main graph. For the main graph just the four options above the line "Graph 1 2 3 4" are available.
@@ -468,7 +474,7 @@ For details, see the hints on [COB calculation page](#CobCalculation-detection-o
(screens-action-tab)=
## Action tab
-
+
### Actions - section M
@@ -514,6 +520,48 @@ Section O reflects the Nightscout careportal. So exercise, announcement and ques
### Tools - section P
+(Aapsscreens-site-rotation)=
+
+#### Site Rotation
+
+Site Rotation button opens the Site Rotation Dialog in View mode:
+
+- You can select if you want to see Cannula sites only, Sensor sites only, or both with upper checkboxes
+- All Cannula change and Sensor change event since the past 45 days are available.
+- Click on a Site area, or in one entry in the list below to filter the list with only entries in selected area. The selected area will be highlighted in light green color.
+- You can open the Edit view to update Site location, Arrow, or Comment associated to each entry
+
+
+
+- The Setting tab (upper right cog) allows you to adjust the patient view (Man, Woman or Child), and to select if you want to manage only Pump sites, only Sensor sites or both.
+
+
+
+
+
+*Note: this setting will be used to automatically open or not Site Rotation Dialog (Edit mode) when a new entry is done from "Prime/Fill button" or "CGM Sensor Insert button"*
+
+- For Site change done directly from Pump, you have to open the View Mode and Edit the new entry to select Location and Arrow
+
+Edit Mode allows you to select Location, Arrow, and Note associated to selected Entry:
+
+- Entry type is visible on the to of Edit mode (Cannula Icon, or Sensor Icon)
+- You have to select Front or Back tab and then the Area
+- Once a Site selected (highlighted in green), you will see in the list below the list of all entries done in the pas 45 days in this site
+
+
+
+- You can adjust an optional arrow with a click on little arrow icon on the top (Arrow allow you to precise sub-location, from 2 to 9, or Pod Orientation)
+
+
+
+- You can also adjust comments concerning selected site
+- After confirmation, the site is recorded
+
+Filtering can be done graphically on the image, or clicking a therapy event in the list To remove filtering, just click on the image outside any sites
+
+
+
#### History Browser
Allows you to ride back in **AAPS** [history](../Maintenance/Reviewing.md).
@@ -592,6 +640,7 @@ This view can be accessed by pressing the 3 dots on the right of the menu, then
* [Temporary target](../DailyLifeWithAaps/TempTargets.md)
* [Profile switch](../DailyLifeWithAaps/ProfileSwitch-ProfilePercentage.md)
* Careportal: notes entered through action tab and notes in dialogues
+* Running mode : history of loop status
* User entry: other notes that are not sent to Nightscout
In the last column, the data source for each line is displayed in blue. It can be :
@@ -652,12 +701,21 @@ Deleting the entries only affects your reports in Nightscout and will never actu
You can use the **Clone** button shown on line **1** to make a copy of a **Profile Switch**. See [Your AAPS Profile > Manage your profiles](#your-aaps-profile-clone-profile-switch) for more information.
+(AapsScreens-running-mode)=
+### Running mode
+
+
+
+This tab shows the history of [loop status](#AapsScreens-loop-status) changes : open, closed, suspend loop.
+
### Care portal
This tab shows all notes and alerts recorded in Nightscout.
+(aaps-screens-running-mode)=
+
## History Browser
This view can be accessed by pressing the 3 dots on the right of the menu, then History. It is not possible to put in the main menu through the Config Builder. It can also be accessed through a button at the bottom of the [Action tab](#screens-action-tab).
diff --git a/docs/CROWDIN/it/DailyLifeWithAaps/Automations.md b/docs/CROWDIN/it/DailyLifeWithAaps/Automations.md
index b809cb1962ba..1fcf1dff3979 100644
--- a/docs/CROWDIN/it/DailyLifeWithAaps/Automations.md
+++ b/docs/CROWDIN/it/DailyLifeWithAaps/Automations.md
@@ -178,9 +178,10 @@ Note that for all age related triggers the equal comparison is unlikely to trigg
* Reservoir level trigger: Available for all pumps, comparison "NOT\_AVAILABLE" is not working for this trigger as the value is always filled in **AAPS**
* Pump battery level trigger: Available for supported pumps, comparison "NOT\_AVAILABLE" is not working for this trigger as the value is always filled in **AAPS**
+(automations-automation-action)=
## Action
-
+
**Actions:** start **Temp Target**
diff --git a/docs/CROWDIN/it/DailyLifeWithAaps/KeyAapsFeatures.md b/docs/CROWDIN/it/DailyLifeWithAaps/KeyAapsFeatures.md
index 7aa093294a38..a5239c2e9628 100644
--- a/docs/CROWDIN/it/DailyLifeWithAaps/KeyAapsFeatures.md
+++ b/docs/CROWDIN/it/DailyLifeWithAaps/KeyAapsFeatures.md
@@ -1,5 +1,41 @@
# Key AAPS features
+## Loop mode
+
+The loop status is shown on the main screen with one of the icons below.
+
+**AAPS** offers several loop modes, such as Open Loop (7), Closed Loop (1) and Low Glucose Suspend (LGS - 2).
+
+See [AAPS Screens > The Homescreen > Loop status](#AapsScreens-loop-status) for information on how to select the loop mode.
+
+
+
+(KeyAapsFeatures-OpenLoop)=
+### Open Loop
+**AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary.
+
+The suggestions will not be executed automatically (as in closed loop). The suggestions have to be enacted by the user manually into the pump (if using virtual pump) or by using a button if **AAPS** is connected to a real pump.
+
+This option is for getting to know how **AAPS** works or if you are using an unsupported pump. You will be in Open Loop, no matter what choice you make here, until the end of **[Objective 5](#objectives-objective5)**.
+
+(KeyAapsFeatures-LGS)=
+### Low Glucose Suspend (LGS)
+
+In this mode, [maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over) is set to zero.
+
+This means that if blood glucose is dropping, **AAPS** can reduce the basal for you. But if blood glucose is rising, no automatic correction will be made. Your basal rates will remain the same as defined in your current **Profile**. Only if IOB is negative (from a previous Low Glucose Suspend) additional insulin will be given to lower **BG**.
+
+This mode is available starting at **[Objective 6](#objectives-objective6)**.
+
+(KeyAapsFeatures-ClosedLoop)=
+### Closed Loop
+
+**AAPS** continuously evaluates all available data (IOB, COB, BG...) and automatically adjusts the treatment if necessary (_i.e._ without further intervention by you) to reach the set [target range or value](#profile-glucose-targets) (bolus delivery, temporary basal rate, insulin switch-off to avoid hypo etc.).
+
+The Closed Loop works within numerous safety limits, which can be set individually.
+
+Closed Loop is only possible if you are in **[Objective 7](#objectives-objective7)** or higher and use a supported pump.
+
(Open-APS-features-autosens)=
## Autosens
* Autosens is an algorithm which looks at blood glucose deviations (positive/negative/neutral).
@@ -95,13 +131,7 @@ See also [OpenAPS documentation for SMB](https://openaps.readthedocs.io/en/lates
This is the [DynamicISF](../DailyLifeWithAaps/DynamicISF.md) feature. When enabled, new settings become available. Settings are explained on the [DynamicISF](#dyn-isf-preferences) page.
-#### High temp-target raises sensitivity
-If you have this option enabled, the insulin sensitivity will be increased while having a temporary target above 100 mg/dl or 5.6 mmol/l. This means, the ISF will rise while IC and basal will decrease. This will effectively make **AAPS** less aggressive when you set a high temp target.
-
-#### Low temp-target lowers sensitivity
-If you have this option enabled, the insulin sensitivity will be decreased while having a temporary target lower than 100 mg/dl or 5.6 mmol/l. This means, the ISF will decrease while IC and basal will rise. This will effectively make **AAPS** more aggressive when you set a low temp target.
-
-### Enable Autosens feature
+### Use Autosens feature
This is the [Autosens](#Open-APS-features-autosens) feature. When using DynamicISF, Autosens can not be used, since they are two different algorithms altering the same variable (sensitivity).
@@ -109,7 +139,7 @@ Autosens looks at blood glucose deviations (positive/negative/neutral). It will
When enabled, new settings become available.
-### Sensitivity raises target
+#### Sensitivity raises target
If this option is enabled, the sensitivity detection (autosens) can raise the target when sensitivity is detected (below 100%). In this case your target will be raised by the percentage of the detected sensitivity.
If the target is modified due to sensitivity detection, it will be displayed with a green background on your home screen.
@@ -118,7 +148,7 @@ If the target is modified due to sensitivity detection, it will be displayed wit
This setting is available when one of "Enable dynamic sensitivity" or "Enable Autosens feature" are enabled.
-### Resistance lowers target
+#### Resistance lowers target
If this option is enabled, the sensitivity detection (autosens) can lower the target when resistance is detected (above 100%). In this case your target will be lowered by the percentage of the detected resistance.
This setting is available when one of "Enable dynamic sensitivity" or "Enable Autosens feature" are enabled.
diff --git a/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md b/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md
index ff0d492b6903..a9a7a125ebf8 100644
--- a/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md
+++ b/docs/CROWDIN/it/DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md
@@ -14,7 +14,9 @@ To avoid this there are two possibilities:
### Option 1: Keep home time and timeshift profile
* Turn off 'Automatic date and time' in your phone settings (manual time zone change).
+
* Phone must keep your standard time as at home for the whole travel period.
+
* Time-shift your profile according to time difference between home time and destination time.
* Long-press profile name (middle of top section on homescreen)
* Select 'Profile Switch'
@@ -24,7 +26,6 @@ To avoid this there are two possibilities:
* i.e. Vienna -> New York: profile switch +6 hours
* i.e. Vienna -> Sydney: profile switch -8 hours
-* Probably not an option if using [patched LibreLink app](#libre2-patched-librelink-app-with-xdrip) as automatic time zone must be set to start a new Libre 2 sensor.
### Option 2: Delete pump history
diff --git a/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md b/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
index 9e9136ce4845..4d31c89e0ebd 100644
--- a/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
+++ b/docs/CROWDIN/it/Getting-Started/CompatiblesCgms.md
@@ -11,9 +11,9 @@ Questa sezione fornisce una breve panoramica di tutti i **sensori CGMs/FGMs** co
| CGM | Available [BG Sources](#Config-Builder-bg-source) |
| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
-| [Dexcom G7](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md), DiaKEM app or [Juggluco](../CompatibleCgms/Juggluco.md) |
+| [Dexcom G7](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) or [Juggluco](../CompatibleCgms/Juggluco.md) |
| [Dexcom ONE+ and Stelo](../CompatibleCgms/DexcomG7.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
-| [Dexcom G6](../CompatibleCgms/DexcomG6.md) | [xDrip+](../CompatibleCgms/xDrip.md) or BYODA |
+| [Dexcom G6](../CompatibleCgms/DexcomG6.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
| [Dexcom ONE](../CompatibleCgms/DexcomG6.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
| [Dexcom G5](../CompatibleCgms/DexcomG5.md) | [xDrip+](../CompatibleCgms/xDrip.md) |
| [Libre 3/3+](../CompatibleCgms/Libre3.md) | [Juggluco](../CompatibleCgms/Juggluco.md) (with or without xDrip+) |
@@ -38,8 +38,8 @@ Trusted data sources allow **SMB** delivery, all the time.
| Sensor | CGM app |
| --------------------- |:----------------------------------------------------------------------------------------------------------------------:|
-| Dexcom G5/G6 | BYODA, xDrip+ (**Direct, Native**) |
-| Dexcom G7 | DiaKEM, xDrip+ (**Direct, Native**), Juggluco (**xDrip broadcast** without xDrip+) |
+| Dexcom G5/G6 | xDrip+ (**Direct, Native**) |
+| Dexcom G7 | xDrip+ (**Direct, Native**), Juggluco (**xDrip broadcast** without xDrip+) |
| Dexcom ONE/ONE+/Stelo | xDrip+ (**Direct, Native**) |
| Libre 2/2+ (EU) | xDrip+ (OOP2 **no calibration**), Juggluco (**xDrip broadcast** without xDrip+, or **Patched Libre** with xDrip+) |
| Libre 2/2+/3/3+ | Juggluco (**xDrip broadcast** without xDrip+, or **Patched Libre** with xDrip+) |
diff --git a/docs/CROWDIN/it/Getting-Started/PreparingForAaps.md b/docs/CROWDIN/it/Getting-Started/PreparingForAaps.md
index a0dd841cfbd0..3986f6f56572 100644
--- a/docs/CROWDIN/it/Getting-Started/PreparingForAaps.md
+++ b/docs/CROWDIN/it/Getting-Started/PreparingForAaps.md
@@ -220,7 +220,7 @@ Users are encouraged to keep their phone Android version up-to-date, including w
```{admonition} delaying Samsung phones updates
:class: warning
Samsung has an unfortunate track record of forcing updates of their phones which cause bluetooth connectivity issues. To disable these forced updates you need to switch the phone to "developer mode" by:
- go to settings and about then software information, then tap build number u til it confirms you have unlocked developer mode. Got back to main settings menu and you should see a new developer options menu item. Open developer options and scroll to find auto system update and turn it off
+ go to settings and about then software information, then tap build number until it confirms you have unlocked developer mode. Got back to main settings menu and you should see a new developer options menu item. Open developer options and scroll to find auto system update and turn it off
```
```{admonition} Google Play Protect potential Issue
diff --git a/docs/CROWDIN/it/GettingHelp/BluetoothTroubleshooting.md b/docs/CROWDIN/it/GettingHelp/BluetoothTroubleshooting.md
new file mode 100644
index 000000000000..ad752bffdf86
--- /dev/null
+++ b/docs/CROWDIN/it/GettingHelp/BluetoothTroubleshooting.md
@@ -0,0 +1,139 @@
+(bluetoothtroubleshooting-bluetooth-related-issues)=
+
+# **Bluetooth related issues**
+
+Some users have been running into issues with Omnipod DASH activation failures, Medtrum Nano connectivity problems, and other pod errors related to Bluetooth. Many of these issues can be traced to one of the following issues.
+
+Some of these issues likely apply to other Bluetooth Insulin pumps too, the Medtrum Nano has known issues with nearby device permission as well as the Omnipod DASH.
+
+---
+
+(bluetoothtroubleshooting-cannot-start-omnipod-with-android-16)=
+
+## Cannot start Omnipod with Android 16
+- Android 16 needs at a minimum **AAPS** version 3.3.2.1 for the Omnipod DASH to work correctly, as this versions has fixes added to specifically address [known problems](../GettingHelp/GeneralTroubleshooting.md#cannot-start-omnipod-with-android-16) introduced in Android 16 for Omnipod.
+
+---
+
+(bluetoothtroubleshooting-apps-using-nearby-device-permission)=
+
+## Apps that use the "Nearby devices" Android permission can cause connection drops and Pod activation problems
+
+Android allows you to control what each app is able to do or access on your phone via a permission model. For each app installed you can choose to allow or deny specific permissions, e.g. access files on the device, access to bluetooth, scan for nearby devices etc.
+
+**AAPS** requires a number of specific permission to function, one which is required ensure that Pods work is the "Nearby devices" permission. There are many other applications which also require this permission, the community is finding that a number of applications when they are granted this permission can cause issues with activating new Pods on some devices.
+
+(bluetoothtroubleshooting-apps-using-nearby-device-permission-known-apps)=
+
+### **Apps that use "Nearby device" permissions and are known to have caused problems:**
+
+Apps in this list have been discussed in one or more places in the community as causing problems for Omnipod DASH devices and in some cases Medtrum Nano too.
+
+```{admonition} Updating the list
+:class: note
+Ping @XiTatiON on #omnipod-dash Discord channel to discuss apps to be added to this list.
+```
+
+- **myBMW** MyBMW interrupted Medtrum Nano and Omnipod DASH. The MyBMW app prompts regarding permission for "find nearby devices" only once, if you don't grant it, it still works absolutely OK
+
+- **Amazon Alexa** Removing "Nearby devices" for Alexa app resolved problem for some people but will break the ability to pair Matter IOT devices
+
+- **MINI app** Appears the app is based on myBMW app and might mirror it's behavior as a result
+
+- **BM2** Solar Battery Monitoring app, used in a some camper van and camping solar setups, when the app is running it prevented activation of a new Pod. Force Stopping the app while activating an new pod is a workaround to the issue. Running the app after that didn't appear to interfere with Dash functionality (On a Pixel 8 Pro running A16).
+
+(bluetoothtroubleshooting-revoke-nearby-device-permission)=
+
+### **How to revoke "Nearby device" permissions for other apps:**
+If you are facing issues activating a new Pod and you are running on the correct supported version of **AAPS** for your version of Android. It may be necessary to revoked the permission for other apps while activating a new Pod.
+
+Follow this procedure to revoked the "Nearby device" permission for all apps except **AAPS**:
+
+```{admonition} Menus and settings
+:class: note
+The screenshots and instructions in this guide are from a Vanilla Android 16 install on Google Pixel 8 Pro. Other manufactures and devices will likely not exactly match these menus and settings descriptions, adjust the steps to suit the device you have and if you are stuck see [Where to get help for dash](#omnipod-dash-where-to-get-help-for-dash) section on how to reach out to the community for support.
+```
+
+1. Open Android settings on your phone, scroll down and press on **Security and privacy (1)**.
+
+ 
+
+2. Scroll down and press on **Privacy controls (1)**.
+
+ 
+
+3. Press on **Permission manager (1)**.
+
+ 
+
+3. Scroll down and press on **Nearby devices (1)**.
+
+ 
+
+4. Browse the list of apps and press on the app you wish to revoke **Nearby devices** permissions for.
+
+ In this guide **Android Auto (1)** is the app we will revoke the permission on.
+
+ To avoid bricking more pods we advise everyone initially to revoke the permission on all apps except **AAPS**.
+
+```{admonition} Which app to select?
+:class: tip
+If you are unsure which app is causing you an issue, disable them all (remember to check the list of known problem apps too and start with those) and if you can spare a few bricked pods on the way, enable the permission on one new app before every new Pod activation, until you can narrow down which app specifically causes your Pod issues. If you do identify new problematic apps please let us know on the #omnipod-dash Discord channel.
+```
+
+ 
+
+5. To revoke the permission Press on **Don't allow (1)**, then Press on **Don't allow anyway (2)**. If done correctly you should see **Don't allow (3)** as the selected Toggle option. You can now go back to the **Nearby device** menu by pressing the **Back arrow (4)** and change this setting on other apps if required.
+
+   
+
+(bluetoothtroubleshooting-re-enable-nearby-device-permission)=
+
+### **How to re-enable "Nearby device" permissions for system apps and other apps:**
+
+1. If required Reference the **"How to revoke "Nearby device" permissions for other apps"** section on how to get to the app privacy settings, then once in the **Nearby device** configuration proceed to 2.
+
+2. Browse the list of apps and press on the app you wish to allow **Nearby devices** permissions for.
+
+ In this guide **Android Auto (1)** is the app we will allow the permission on.
+
+ You will notice that **Android Auto (1)** is missing in the app list after the permission is revoked. This is because the **Android Auto** app is a **System app** and by default system apps are hidden.
+
+ 
+
+3. To show hidden system apps Press on the **Three Dotted Lines (Hamburger) (1)**, then Press on **"Show System (1)"**. You should now be able to see the hidden system app in the list **Android Auto (3)**.
+
+```{admonition} Find your app
+:class: tip
+If an app is revoked you will need to scroll down until you see the list of revoked apps lower down in the list.
+```
+
+   
+
+5. Follow the guidance in **"How to revoke "Nearby device" permissions for other apps"** in reverse to re-enable permissions for each app.
+
+---
+
+(bluetoothtroubleshooting-android-15-bluetooth-connection-problems)=
+
+## Android 15 Frequent Bluetooth connection problems
+
+After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15. Enabling the **Bond BT device on Android 15+** setting within **AAPS** settings may help improve stability of Bluetooth connections, follow guide below to enable this:
+
+```{admonition} Android 16
+:class: warning
+Only enable the **Bond BT device on Android 15+** option on Android 15, and only if you experience connectivity issues. DO NOT enable bonding option on Android 16.
+```
+
+1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen.
+
+ 
+
+2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**.
+
+ 
+
+
+3. If the pump asks for a pairing request, accept it.
+
+4. Restart your phone.
diff --git a/docs/CROWDIN/it/GettingHelp/GeneralTroubleshooting.md b/docs/CROWDIN/it/GettingHelp/GeneralTroubleshooting.md
index 97b291577d44..57447a6a5417 100644
--- a/docs/CROWDIN/it/GettingHelp/GeneralTroubleshooting.md
+++ b/docs/CROWDIN/it/GettingHelp/GeneralTroubleshooting.md
@@ -1,17 +1,23 @@
-# Troubleshooting
+(generaltroubleshooting)=
-You can find troubleshooting info on many pages in the wiki. This page is a collection of links to help you find the information to solve your problem.
+# **Troubleshooting**
+
+You can find troubleshooting info on many pages in the wiki. This page is a collection of links to help you find the information to solve your problem for various known issues.
Additional useful information might also be available in the [FAQ](../UsefulLinks/FAQ.md).
-## AAPS app
+---
+
+(generaltroubleshooting-aaps-app)=
+
+## **AAPS app**
-### Building & updating
+### **Building & updating**
* [Lost keystore](#troubleshooting_androidstudio-lost-keystore)
* [Troubleshooting AndroidStudio](TroubleshootingAndroidStudio)
-### Installing
+### **Installing**
You may see a Google Play Protect warning that the app is unsafe, was built for older Android versions and doesn't include latest privacy protections.
@@ -19,7 +25,7 @@ Ignore it: More details, Install anyway.
-### Settings
+### **Settings**
* Profile
@@ -30,46 +36,43 @@ Ignore it: More details, Install anyway.
* [Nightscout Client](../GettingHelp/TroubleshootingNsClient.md)
-### Usage
+### **Usage**
* [Wrong carb values](#CobCalculation-detection-of-wrong-cob-values)
* [SMS commands](#SMSCommands-troubleshooting)
-### Cannot start Omnipod with Android 16
-
-Upgrade to minimum version of AndroidAPS: 3.3.2.1.
-
-### Frequent Bluetooth connection problems
+---
-#### Android 15
+(generaltroubleshooting-bluetooth-related-issues)=
-After upgrading Android or moving to a recent phone, **AAPS** frequently loses Bluetooth connection to the pump. The problem disappears temporarily when restarting the phone. If the phone runs Android 15, you can try to enable the following:
-1) **Open preferences** by clicking the three-dot menu on the top right side of the home screen.
+## **Bluetooth related issues**
+For known issues with Bluetooth connections, dropouts of pump/pods, or activation and connection issues [Bluetooth Troubleshooting](../GettingHelp/BluetoothTroubleshooting.md)
-
+---
-2. Scroll down and open the **Confirmation beeps** / **Advanced** submenu. Enable **Bond BT device on Android 15+**.
+(generaltroubleshooting-android-related-issues)=
- 
+## **Android Related Issues**
-3. If the pump asks for a pairing request, accept it.
+### **Battery optimization**
-4. Restart your phone.
+Android has implemented battery saving setting that are enabled by default. These settings automatically suspend/pause applications that are not required for the system to function to help conserve the amount of battery energy used by apps that don't always need to be running.
-#### Battery optimization
+When this is enabled, it will very likely cause issue for **AAPS** and other supporting apps like **xDrip+**.
-This can happen with various pumps. Apart from excluding AAPS from any battery optimization, you can also exclude the system Bluetooth app from battery optimization. This can help in some cases. Depending on the phone you use, you will find the Bluetooth app differently.
+It's important to ensure that you have disabled Battery Optimization to ensure **AAPS** and other supporting apps remain active all the time.
-Here are examples how to find them on specific android phones.
+Depending on your phone model and make there may be more than one location and setting which needs to have this disabled.
+***NOTE:** Follow the steps below to Disable Battery Optimization for the Bluetooth service if your phone has this option, the same steps can be used to disable for **AAPS** and other apps, however the screenshots will only show how to do this for the Bluetooth service.*
-##### Pixel phones (stock Android)
+#### **Pixel phones (stock Android)**
-* Go to the android settings, select "Apps".
+* Go to the Android settings, select "Apps".
@@ -90,7 +93,7 @@ Here are examples how to find them on specific android phones.
-##### Samsung phones
+#### **Samsung phones**
* Go to the android settings, select "Apps"
@@ -112,28 +115,53 @@ Here are examples how to find them on specific android phones.
+#### **Huawei phones**
+
+See this guide for [Huawei bluetooth & battery optimization](../CompatiblePhones/Huawei.md)
+
+---
+
+(generaltroubleshooting-cgm)=
+
+## **Continious Glucose Monitor (CGM)**
-## CGM
+Useful links to known issues and steps to resolve for CGMs.
* [General](#general-cgm-troubleshooting)
* [Dexcom G6](#DexcomG6-troubleshooting-g6)
* [Libre 3](#libre3-experiences-and-troubleshooting)
-* [Libre 2](#Libre2-experiences-and-troubleshooting)
* [xDrip - no CGM data](#xdrip-identify-receiver)
* [xDrip - Dexcom troubleshooting](#xdrip-troubleshooting-dexcom-g5-g6-and-xdrip)
-## Pumps
+---
+
+(generaltroubleshooting-pumps)=
+
+## **Pumps**
+
+Useful links to known issues and steps to resolve for Pumps
* [DanaRS](#DanaRS-Insulin-Pump-dana-rs-specific-errors)
* [Accu-Chek Combo general](../CompatiblePumps/Accu-Chek-Combo-Tips-for-Basic-usage.md)
* [Accu-Chek Insight](#Accu-Chek-Insight-Pump-insight-specific-errors)
* [Medtronic + RileyLink](#MedtronicPump-what-to-do-if-i-loose-connection-to-rileylink-and-or-pump)
-## Phones
+---
+
+(generaltroubleshooting-phones)=
+## **Phones**
+
+Useful links to known issues and steps to resolve for Phones
+
+* [List of tested phone and device setups](https://docs.google.com/spreadsheets/u/1/d/e/2PACX-1vScCNaIguEZVTVFAgpv1kXHdsHl3fs6xT6RB2Z1CeVJ561AvvqGwxMhlmSHk4J056gMCAQE02sAWJvT/pubhtml?gid=683363241&single=true)
* [Jelly](../CompatiblePhones/Jelly.md)
* [Huawei bluetooth & battery optimization](../CompatiblePhones/Huawei.md)
+(generaltroubleshooting-smartwatches)=
+
## Smartwatches
+Useful links to known issues and steps to resolve for Smartwatches
+
* [Troubleshooting Wear app](#Watchfaces-troubleshooting-the-wear-app)
diff --git a/docs/CROWDIN/it/GettingHelp/ProfileTuning.md b/docs/CROWDIN/it/GettingHelp/ProfileTuning.md
new file mode 100644
index 000000000000..82e38d0e73ff
--- /dev/null
+++ b/docs/CROWDIN/it/GettingHelp/ProfileTuning.md
@@ -0,0 +1,136 @@
+# **Tweaking the AAPS' Profile**
+
+```{admonition} This is NOT a medical advice
+:class: warning
+Please work with your care team for support and advice on your diabetes management.
+Use this guide only once you have [set up your **Profile** correctly](https://androidaps.readthedocs.io/en/latest/SettingUpAaps/YourAapsProfile.md), following all **AAPS** objectives.
+```
+
+This guide explains the logic of the OpenAPS algorithm results with a given __Profile__, and provides information about which values to adjust when certain situations are observed. The suggestions about basal testing below may diverge from what your care team advises
+
+Using **closed loop** may make basal testing easier and may significantly reduce the hypo risk if your __Profile__ basal is too strong.
+
+## **Changing profile's settings, how to proceed**
+
+1. Ensure you have read and understand __AAPS’__ recommended settings and advice below. Not following this advice will make the whole process problematic and less likely to get a well tuned __Profile__
+2. Carefully observe and compare, **over several days**, what is happening with your __BG__ and __IOB__.
+3. Keep an eye out for patterns that happen around the same time (almost) everyday.
+4. It's important to do this over several days. Poor results tend to be yielded from using data observed on a single day to make __Profile’s__ adjustment decisions.
+5. After you have observed a repeatable pattern of behavior, e.g. at 1PM you see a spike in __BG__ or a negative __IOB__ value, only then start to make small changes to your __Profile__.
+6. It's important to limit the changes you make to one thing at a time. E.g. increase your basal by 10% around 1PM.
+7. After every change, it's important to monitor the impact on your __BG__ and __IOB__ for the next few days.
+8. Repeat this pattern, observe, decide, tweak again if needed
+
+Don't rush, go slow!
+
+## **Recommended settings and advice while tweaking basal**
+
+- Do all testing with [closed loop enabled](#AapsScreens-loop-status).
+- **Turn OFF all [automations](../DailyLifeWithAaps/Automations.md)**
+- **Turn OFF [DynISF](#Open-APS-features-DynamicISF), [AutoISF](../AdvancedOptions/DevBranch.md), [AutoSens](#Open-APS-features-autosens)** so that they will not try to adapt your profile.
+- Do not make manual user actions (manual bolus, temp targets etc…) while testing: let the system use the **Profile** settings only.
+- For the [additional graphs](#AapsScreens-section-g-additional-graphs): on graph 1, use Insulin On Board, Carbs On Board (and Sensitivity change). On graph 2, use Deviations and Blood Glucose Impact. When asking for advice, always include those on your screenshots.
+- COB=0[*](#profiletuning-cob-zero)
+- No physical activities.
+- No stress.
+- No illness.
+- No extreme weather like high or low temperatures.
+- If your [basal rate profile](#your-aaps-profile-basal-rates) is correct, when you are on target with COB=0[*](#profiletuning-cob-zero) and IOB=0, you will remain constantly on target whatever your ISF (ISF is only used when you are higher than your target).
+- You need to check the actual IOB but also, the IOB chart to see how the IOB was during the past few hours.
+
+(profiletuning-cob-zero)=
+
+***COB = 0**
+
+Meaning that the meal is digested, and there are no more carbs in your body.
+
+AAPS might indicate [COB=0 while you still have carbs on board](../DailyLifeWithAaps/CobCalculation.md).
+
+## **[Profile](../SettingUpAaps/YourAapsProfile.md) definitions**
+
+A too **strong Profile** indicates some combination of the following:
+
+- [ISF](#your-aaps-profile-insulin-sensitivity-factor) number is too small
+- The [basal](#your-aaps-profile-basal-rates) number is too big
+- [I:C](#your-aaps-profile-insulin-to-carbs-ratio) number is too small
+
+## **IOB Observations**
+
+*Note: you can also use Loopalyzer IOB graph in Nightscout reports to view IOB on several days.*
+
+If you observe the following patterns after a few days, consider the following changes
+
+### **IOB positive**
+
+- **Profile** basal might not be strong enough (this could also be because of things like unannounced food, illness, bad site absorption, etc.)
+
+
+
+### **IOB negative**
+
+- Default basal too strong
+- May be the effect from past exercise/physical activity
+
+
+
+- Previous meal: too much bolus (which resulted in a very long zero temp basal)
+
+
+
+## **BG Target Observations**
+
+### **Stuck High**
+
+- __ISF__ ‘s number is high and not strong enough (calculated insulin is too weak)
+
+
+
+- __Profile__ basal might not be strong enough (SMBs do not have enough "basal stock" to use)
+- A security ([MaxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over)?) might have kicked in and is limiting insulin injection. Verify in the [SMB](#Open-APS-features-super-micro-bolus-smb) tab.
+- Technical issue: site absorption, infusion set, ...
+
+### **Stuck Low**
+
+- __ISF__ too strong and the number needs to be raised higher
+- __Profile__ basal too strong (if also negative IOB)
+
+### **Rollercoaster (ups and downs)**
+
+- **ISF** too strong? See your [AAPS Profile](#your-aaps-profile-insulin-sensitivity-factor)
+
+
+
+## **BG After Meals Observations**
+
+### **Fast rise and BG going high**
+
+- Food contains fast carbs
+- Consider doing a pre-bolus
+- Bolus (IC or injected %) not strong enough
+
+
+
+### **Fast rise and then BG going low**
+
+- Consider doing a pre-bolus, profile might be too aggressive (over correction of the raise)
+- Bolus too strong
+
+
+
+## **[How to calculate your I:C](#your-aaps-profile-insulin-to-carbs-ratio)**
+
+1. First, you need the correct default basal settings in your **Profile**.
+2. Start on target, better without negative IOB.
+3. Record the total insulin given in the pump tab (or pump history) and call it Start insulin C4. Very accurately measure a known portion of carbs, and record the start time and Start IOB. Then enter carbs and bolus information into AAPS using the wizard (with the current configured CI). Don't forget to eat the carbs ;)
+4. After some hours, when COB=0[*](#profiletuning-cob-zero) and you're back on target, record end time, and note down the End IOB, check the total insulin given as before and call it End insulin. *NOTE: The time frame is NOT important, as long as it is longer than your digestion*
+5. From the difference between Start and End insulin amount, subtract/add the difference end IOB - start IOB. Then subtract the basal insulin calculated from your profile settings.
+6. If __BG__ is in target, you'll have the total insulin used to “digest” your carbs. Calculate your **I:C**.
+
+### **Explanations for the I:C calculations**
+
+- With a **Profile** that has the correct default basal rate, during any time frame, you should stay on target and have an IOB near 0. You get your **Profile** basal only.
+- You add carbs and bolus to this mix. Wait till your body digests all the carbs and be back on **BG** target. Your insulin usage will be the sum of your basal + the insulin needed for the carbs. You calculate the insulin used for your basal (by using your **Profile**) and the surplus will be the insulin used to digest the carbs.
+- If the time frame is too short, there will be carbs undigested, thus your "insulin needed for the carbs" will be wrong.
+- If the time frame is too long, nothing bad will happen. You'll use all your carbs and you'll get more basal. At the end, you'll subtract the basal from the total insulin used, the extended time frame (with more basal use) will not affect the result.
+
+Originally written up by @Robby (Discord) on tips and tricks to help tune your AAPS Profile, reviewed and edited by the community (thank you!).
diff --git a/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md b/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md
index 9110b4322763..e0d6f93548ba 100644
--- a/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md
+++ b/docs/CROWDIN/it/Maintenance/DocumentationUpdate.md
@@ -1,10 +1,28 @@
# Docs updates & changes
+## January 2025
+
+- [3.4](#version3400) release and documentation update roll-up (Wizard, Computer build versions, Config Builder)
+- CGM list update. Dexcom G5, Tomato, Glimp removed.
+- [Site rotation UI](#Aapsscreens-site-rotation)
+- [Running mode](#AapsScreens-running-mode)
+- [Autotune](../AdvancedOptions/Autotune.md)
+
+## December 2025
+
+- [Profile tuning](../GettingHelp/ProfileTuning.md) from @robrub
+
+## October 2025
+
+- DiaKEM: new installs don't work after servers upgrade @psonnera
+- Removed Libre 2 patched app (obsolete): doesn't work with new sensors @psonnera
+- Reworked Omnipod Dash page @XiTatiON
+
## August 2025
- Updated versions and Android Studio prerequisites
- Added [3.3.2.1](#version3321) release, removed Android 16 references (fixed)
-- Added [Browser Build](browser-build) @Angus
+- Added [Browser Build](#browser-build) @Angus
## May 2025
@@ -22,7 +40,7 @@
## November 2024
- Update of [Your AAPS Profile](../SettingUpAaps/YourAapsProfile.md) @emilise
-- Reorganisation of [Wear OS Smartwatches](../WearOS/BuildingAapsWearOS.md) content @psonnerat
+- Reorganization of [Wear OS Smartwatches](../WearOS/BuildingAapsWearOS.md) content @psonnerat
## October 2024
@@ -62,7 +80,7 @@ AAPS 3.1 documentation is available [here](https://androidaps.readthedocs.io/en/
## November 2021
-- Best practices for calibrating a [libre 2 sensor](#Libre2-best-practices-for-calibrating-a-libre-2-sensor)
+- Best practices for calibrating a libre 2 sensor
- [ISF](../UsefulLinks/FAQ.md) reformulation of impact
- Update [troubleshooting Android studio](../GettingHelp/TroubleshootingAndroidStudio)
- Removed patched [Dexcom](../CompatibleCgms/DexcomG6.md) app as it is obsolete
@@ -121,7 +139,7 @@ AAPS 3.1 documentation is available [here](https://androidaps.readthedocs.io/en/
## June 2020
-- [Libre 2](../CompatibleCgms/Libre2.md) - more details patched Libre Link app & use of bluetooth transmitters
+- Libre 2 - more details patched Libre Link app & use of bluetooth transmitters
- [Time zone travelling](../DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md) with Libre 2
## May 2020
@@ -129,7 +147,7 @@ AAPS 3.1 documentation is available [here](https://androidaps.readthedocs.io/en/
- [Extended bolus only for Dana + Insight pumps](#Extended-Carbs-extended-bolus-and-switch-to-open-loop-dana-and-insight-pump-only)
- [Insight deactivate vibration](#Accu-Chek-Insight-Pump-vibration) (firmware 3.x only)
- [Minimal request rate](#Preferences-minimal-request-change) to reduce number of notifications in open loop mode
-- [Patched Libre Link app](#libre2-patched-librelink-app-with-xdrip) - check if correctly patched
+- Patched Libre Link app - check if correctly patched
- [Prediction lines](#aaps-screens-prediction-lines) - more details
## April 2020
diff --git a/docs/CROWDIN/it/Maintenance/ReleaseNotes.md b/docs/CROWDIN/it/Maintenance/ReleaseNotes.md
index 7d720070e53d..688492cd5c4f 100644
--- a/docs/CROWDIN/it/Maintenance/ReleaseNotes.md
+++ b/docs/CROWDIN/it/Maintenance/ReleaseNotes.md
@@ -23,15 +23,20 @@ The chronology of these releases is not available at the moment but as this ques
## Android version and AAPS version
-If your smartphone uses an Android Version older than Android 11 you will not be able to use AAPS v3.3 and up as it requires at least Android 11.
+If your smartphone uses an Android Version older than Android 12 you will not be able to use AAPS v3.4 and up as it requires at least Android 12.
In order to allow users with older Android to use older version of AAPS new versions were pushed which only change version verification. No other improvements are included.
-### Android 11 and up
+### Android 12 and up
- Use latest AAPS version
- Download AAPS Code from
+### Android 11
+
+- Use AAPS version **3.3.2.1**
+- Download AAPS Code from branch 3.3.2.1
+
### Android 9,10
- Use AAPS version **3.2.0.4**
@@ -49,7 +54,7 @@ In order to allow users with older Android to use older version of AAPS new vers
## WearOS version
-- AAPS requires at least WearOS API level 28 (Android 9)
+- AAPS requires at least WearOS API level 30 (Android 11)
```{tip}
WearOS 5, API level 34 (Android 14) has [limitations](#BuildingAapsWearOs-WearOS5).
@@ -57,6 +62,59 @@ WearOS 5, API level 34 (Android 14) has [limitations](#BuildingAapsWearOs-WearOS
(latestrelease)=
+(version3400)=
+
+## Version 3.4.0.0
+
+Release date: 31-12-2025
+
+### Before upgrading:
+* This version requires Google Android 12.0 or above. Check your phone version before attempting to update.
+* Update to latest Android Studio or better setup using browser build.
+
+### New features
+* Running mode @MilosKozak
+ * Show [loop status history](#AapsScreens-running-mode) in treatment tabs
+ * Show and allow changing [loop status from AAPSClient](#RemoteControl_aapsclient).
NB : needs the setting [NSClient > Synchronization > Receive Running mode events](#Preferences-nsclient-synchronization)
+* [New CGMs](../Getting-Started/CompatiblesCgms.md) : Glunovo, Intelligo, Sinocare
+* [Site rotation](#Aapsscreens-site-rotation) support @Philoul
+* New [automation action](#automations-automation-action) : enable or disable SMBs @MilosKozak
+* Syai CGM is [trusted source](#GettingStarted-TrustedBGSource) and supports advanced filtering @MilosKozak
+
+### Wear OS Improvements
+* dramatically reduced battery usage @MilosKozak
+* UI improvements and fixes @olorinmaia
+* almost complete rewritten code to match current level of libs (WearOS 2 previously) @MilosKozak
+* 2 new complications for extended data @Philoul
+* Migrated to modern complication provider with DataStore @MilosKozak
+
+### Memory Leak Fixes
+* Fixed memory leaks in code @MilosKozak
+* Added LeakCanary memory leak reporting to Firebase Crashlytics @MilosKozak
+
+### Pump Driver Improvements
+* **DanaI**: fixed disconnection issues @MilosKozak
+* **RileyLink**: Speedup communication by minimizing delays @mifi100
+* **Medtrum**: Added patch activation time and age display @vanelsberg, password uppercase fix @MilosKozak
+* **Combo**: Fixed Test race conditions @MilosKozak @dv1
+* **Equil**: Optimized connectivity, reduced battery usage @MilosKozak
+
+### Nightscout Sync
+* Improved deduplication on NS failure @MilosKozak
+
+### UI/UX Improvements
+* various improvemnts @MilosKozak @Philoul @olorinmaia
+
+### Automation
+* New SMB control action - enable/disable SMB via automation @MilosKozak
+
+### Testing
+* Added comprehensive unit tests for Equil, Eopatch, Dana, and Medtronic pumps @MilosKozak
+* Improved test stability and coverage across multiple modules @MilosKozak
+
+### Tidepool
+* Tidepool OAUTH2 (Support for new Tidepool authentication) @MilosKozak
+
(version3321)=
## Version 3.3.2.1
@@ -571,7 +629,7 @@ You need at least start [objective 11 (in later versions objective 10!)](#object
- visualization of [dynamic target adjustment](#AapsScreens-visualization-of-dynamic-target-adjustment) @Tornado-Tim
- new [preferences layout](../SettingUpAaps/Preferences.md) @MilosKozak
- SMB algorithm update @Tornado-Tim
-- [Low glucose suspend mode](#Preferences-aps-mode) @Tornado-Tim
+- [Low glucose suspend mode](#KeyAapsFeatures-LGS) @Tornado-Tim
- [carbs required notifications](#key-aaps-features-minimal-carbs-required-for-suggestion) @twain47 @Tornado-Tim
- removed Careportal (moved to Actions) @MilosKozak
- [new encrypted backup format](ExportImportSettings.md) @dlvoy
diff --git a/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md b/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md
index 70e968b05c45..7bbb08512d33 100644
--- a/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md
+++ b/docs/CROWDIN/it/RemoteFeatures/RemoteControl.md
@@ -1,8 +1,8 @@
# Remote control of AAPS
There are four highly effective tools for remotely managing **AAPS**:
-1) [SMS commands](RemoteControl_SMS-Commands) (follower phone can be either Android or iOS), 2) [AAPSClient](RemoteControl_aapsclient) (follower phone is Android) 3) [Nightscout](RemoteControl_nightscout) (Android, iOS or other computer/device).
-4) [Smartwatches](RemoteControl_smartwatches) (Android)
+1) [SMS commands](#RemoteControl_SMS-Commands) (follower phone can be either Android or iOS), 2) [AAPSClient](#RemoteControl_aapsclient) (follower phone is Android) 3) [Nightscout](#RemoteControl_nightscout) (Android, iOS or other computer/device).
+4) [Smartwatches](#RemoteControl_smartwatches) (Android)
The first three are mostly appropriate for caregivers/parents, but smartwatches are very useful for caregivers/parents **and** for adults with diabetes themselves.
@@ -19,7 +19,7 @@ See the dedicated [SMS Commands](../RemoteFeatures/SMSCommands.md) page.
**AAPSClient** looks very similar in appearance to **AAPS** itself, offering the caregiver tabs that will remotely action commands in **AAPS**:
-
+
### About AAPSClient and AAPSClient2
@@ -94,15 +94,17 @@ If you are struggling with **AAPS** v3 to accept the 'NS access token' and using
### Features of AAPSClient include:
-| Tab / Hamburger | Features |
-| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| **Action** Tab | - Profile Switch
- Temp Target
- BG Check
- CGM Sensor Insert
- Note
- Exercise
- Announcement
- Question?
- History Browser |
-| **Food** Tab | |
-| **Treatments** Tab | - Check Treatments delivered including bolus and carbs entered |
-| **Maintenance** Tab | - Export and Import Settings |
-| **Profile** Tab | - Creating new profile
- Profile switch |
+| Tab / Hamburger | Features |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| **Action** Tab | - Profile Switch
- Loop Status change
- Temp Target
- BG Check
- CGM Sensor Insert
- Note
- Exercise
- Announcement
- Question?
- History Browser |
+| **Food** Tab | |
+| **Treatments** Tab | - Check Treatments delivered including bolus and carbs entered |
+| **Maintenance** Tab | - Export and Import Settings |
+| **Profile** Tab | - Creating new profile
- Profile switch |
+
+**AAPSClient** allows the caregiver to make many of the adjustments that are allowed directly in **AAPS** (excluding insulin boluses) remotely, via the mobile or internet network. The main benefits of **AAPSClient** are the speed and ease with which caregivers/parents can use it to remotely control **APPS**. __AAPSClient__ _can_ be much faster than entering SMS Commands, if delivering a command which would require authentication. Commands entered on **AAPSClient** are uploaded onto Nightscout. In order for the actions taken in **AAPSClient** to be actually actioned in **AAPS**, the NSClient settings must allow to receive such orders. See the [Synchronization section of NSClient preferences](#Preferences-nsclient-synchronization).
+
-**AAPSClient** allows the caregiver to make many of the adjustments that are allowed directly in **AAPS** (excluding insulin boluses) remotely, via the mobile or internet network. The main benefits of **AAPSClient** are the speed and ease with which caregivers/parents can use it to remotely control **APPS**. __AAPSClient__ _can_ be much faster than entering SMS Commands, if delivering a command which would require authentication. Commands entered on **AAPSClient** are uploaded onto Nightscout.
Remote control through **AAPSClient** is only recommended if your synchronization is working well (_i.e._ you don’t see unwanted data changes like self-modification of TT, TBR etc) see [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details.
diff --git a/docs/CROWDIN/it/Sandbox/sandbox1.md b/docs/CROWDIN/it/Sandbox/sandbox1.md
index cfe4b00cc551..66f725ea3f87 100644
--- a/docs/CROWDIN/it/Sandbox/sandbox1.md
+++ b/docs/CROWDIN/it/Sandbox/sandbox1.md
@@ -1,7 +1,3 @@
-- - -
-orphan: true
-- - -
-
# internal sandbox file 1 for testing our sprint
```{admonition} no need to translate this
@@ -30,10 +26,6 @@ You can directly jump from here to the second label in this file - ["Jump"](#thi
And you can jump to the first label too - ["Jump"](#this-is-a-test) or [tag jump](#sandbox1-this-is-a-test).
-Here you can jump to the second sandbox file - ["Jump"](./MoveTest/sandbox2.md) or [tag jump](#sandbox2-this-is-a-test).
-
-You can directly jump from here to the first label in the sandbox2.md file - ["Jump"](./MoveTest/sandbox2.md#this-is-a-test).
-
Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.
(sandbox1-in-the-middle-of-nowhere)=
diff --git a/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md b/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
index 56421231b7f6..4637dca54ba2 100644
--- a/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
+++ b/docs/CROWDIN/it/SettingUpAaps/BrowserBuild.md
@@ -60,6 +60,20 @@ Scroll down the next screen and tap **Create Fork**.
+```{note}
+You cannot fork and you see this?
+`**Create a new fork**`
+`A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. View existing forks.`
+`*Required fields are marked with an asterisk (*).*`
+`**No available destinations to fork this repository.**`
+This means you already have an existing fork of AndroidAPS.
+Make sure it's up to date and continue to Preparation Steps.
+```
+
+```{warning}
+**Never delete your fork without having done a backup of your secrets!**
+```
+
GitHub now displays your personal copy of AndroidAPS. Leave this web browser tab open.
diff --git a/docs/CROWDIN/it/SettingUpAaps/CompletingTheObjectives.md b/docs/CROWDIN/it/SettingUpAaps/CompletingTheObjectives.md
index 8814234c9a66..4d877bfe5535 100644
--- a/docs/CROWDIN/it/SettingUpAaps/CompletingTheObjectives.md
+++ b/docs/CROWDIN/it/SettingUpAaps/CompletingTheObjectives.md
@@ -93,7 +93,7 @@ The purpose of **Objective 4** is to recognise how often **AAPS** will evaluate
The minimal time to complete this objective: **7 days**. This is a mandatory wait time. It is not possible to proceed to the next **Objective**, even if all basal rate changes were enacted already.
-- Select Open Loop either from the [Preferences > OpenAPS](#Preferences-aps-mode) menu or by pressing and holding the Loop icon on the top left of the **Overview** screen.
+- Select Open Loop either by pressing and holding the [Loop icon](#AapsScreens-loop-status) on the top right of the **Overview** screen.
- Manually enact at least 20 of the temporary basal rate suggestions over a period of 7 days; key them into your (physical) pump and confirm in AAPS that you have accepted them. Ensure these basal rate adjustments show up in **AAPS** and **Nightscout**.
- Use [**Temp Targets**](../DailyLifeWithAaps/TempTargets.md) when necessary. After treating a hypo, use the predefined "hypo temp target" to prevent the system from overcorrecting upon the bounce back.
- If you are still in [Simple Mode](#preferences-simple-mode) at this point, now is probably a good time to switch it off.
@@ -114,7 +114,7 @@ As part of **Objective 5** you will start to understand how temporary basal reco
Estimated time to complete this objective: **7 days**.
-This **Objective** requires you to determine and set your “Max U/h a temp basal can be set to” (max-basal) value as described in [OpenAPS-features](#Open-APS-features-max-u-h-a-temp-basal-can-be-set-to). This value can be set in **Preferences > OpenAPS**. If you are still using a virtual pump, make sure this safety setting is set in both **AAPS** and your insulin pump.
+This **Objective** requires you to determine and set your “Max U/h a temp basal can be set to” (max-basal) value as described in [OpenAPS-features](#Open-APS-features-max-u-h-a-temp-basal-can-be-set-to). This value can be set in [Preferences > OpenAPS SMB](#Preferences-openaps-smb-settings). If you are still using a virtual pump, make sure this safety setting is set in both **AAPS** and your insulin pump.
You might wish to set your [**Profile** BG target](#profile-glucose-targets) higher than usual until you are comfortable with **AAPS**' calculations and settings. You may wish to experiment with adjusting your **BG target** in your **Profile** being in a tighter range (say, 1 or less mmol/l [20 mg/dl or less] wide) and observe the resulting behavior.
@@ -162,13 +162,14 @@ This means that when you are on **Objective 6**, if sensor glucose levels are dr
- Watch active temporary basals by looking at the turquoise basal text on the OVERVIEW screen or the turquoise basal render as part of the OVERVIEW graph.
- You may temporarily experience spikes following treated hypos without being able to increase basals on the rebound.
+(objectives-objective7)=
## Objective 7: Tuning the closed loop, raising maxIOB above 0 and gradually lowering BG targets
-To complete **Objective 7** you have to close your loop and raise your [maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over). **maxIOB** was zeroed out automatically in **Objective 6**. This is now reverted. **AAPS** will start to use your defined maxIOB value to correct high glucose values.
+To complete **Objective 7** you have to close your loop and raise your [maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over). **maxIOB** was zeroed out automatically in **Objective 6**, due to the Low Glucose Suspend mode. This is no longer the case. **AAPS** will start to use your defined maxIOB value to correct high glucose values.
Minimal time to complete this objective: **1 day**. This is a mandatory wait time. It is not possible to proceed to the next **Objective** until this period of time has expired.
-- Select **Closed Loop** either from [Preferences > OpenAPS](../SettingUpAaps/Preferences.md) or by pressing and holding the Loop icon in the top right corner of the **Overview** screen. Stay in **Closed Loop** over a period of 1 day.
+- Select **Closed Loop** by pressing and holding the [Loop icon](#AapsScreens-loop-status) in the top right corner of the **Overview** screen. Stay in **Closed Loop** over a period of 1 day.
- Slowly raise your 'Maximum total IOB OpenAPS can’t go over' (in OpenAPS called 'max-iob') above 0, until you find the settings that work best for you.
diff --git a/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md b/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md
index b1f72ba892b6..1908571be457 100644
--- a/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md
+++ b/docs/CROWDIN/it/SettingUpAaps/ComputerBuild.md
@@ -21,11 +21,11 @@ See [FAQ page](../UsefulLinks/FAQ.md) for details.
| ----------------------- | ---------------------------------------------------- | ------------------------------------------------------ | ------ |:--- |
| 2.6.2 | 3.6.1 | | 5.6.4 | 11 |
| 2.8.2.1 | 4.1.1 | | 6.1.1 | 13 |
-| [3.1.0.3](#version3100) | 2020.3.1 | up to Narwhal | 7.3.3 | 17 |
-| [3.2.0.4](#version3204) | Hedgehog (2023.1.1) | up to Narwhal | 8.2 | 17 |
-| [3.3.1.3](#version3300) | Ladybug Feature Drop (2024.2.2) | up to Narwhal | 8.10 | 21 |
-| [3.3.2](#version3300) | Meerkat (2024.3.1) | Narwhal | 8.11.1 | 21 |
-| [3.3.2.1](#version3321) | Narwhal (2025.1.2) | | 8.13 | 21 |
+| [3.1.0.3](#version3100) | 2020.3.1 | up to Otter | 7.3.3 | 17 |
+| [3.2.0.4](#version3204) | Hedgehog (2023.1.1) | up to Otter | 8.2 | 17 |
+| [3.3.1.3](#version3300) | Ladybug Feature Drop (2024.2.2) | up to Otter | 8.10 | 21 |
+| [3.3.2](#version3300) | Meerkat (2024.3.1) | up to Otter | 8.11.1 | 21 |
+| [3.3.2.1](#version3321) | Narwhal (2025.1.2) | Otter | 8.13 | 21 |
The "preferred version" is packaged with the appropriate JVM version. The preferred version is also the minimal version you can use to build **AAPS**. You will **NOT** be able to build on a version older than the "preferred" one. If using a different version, you may encounter issues related to JVM version. See the [Troubleshooting Android Studio](#troubleshooting_androidstudio-uncommitted-changes) page to help solve these issues. If your current Android Studio version is not listed in the table, you must update it first.
diff --git a/docs/CROWDIN/it/SettingUpAaps/ConfigBuilder.md b/docs/CROWDIN/it/SettingUpAaps/ConfigBuilder.md
index 95f3a766554e..e686f92dea3e 100644
--- a/docs/CROWDIN/it/SettingUpAaps/ConfigBuilder.md
+++ b/docs/CROWDIN/it/SettingUpAaps/ConfigBuilder.md
@@ -8,7 +8,7 @@ The **Config Builder** is the tab where you turn the modular features on and off
When there are additional settings available within the module, you can click on the cog wheel (B) which will take you to the specific settings within preferences.
-
+
(Config-Builder-tab-or-hamburger-menu)=
@@ -16,7 +16,7 @@ When there are additional settings available within the module, you can click on
With the checkbox under the eye symbol you can decide how to open the corresponding program section.
-
+
```{contents}
:backlinks: entry
@@ -89,10 +89,10 @@ Select the blood glucose source you are using. See [BG Source](../Getting-Starte
* [xDrip+](../CompatibleCgms/xDrip.md)
* [NSClient BG](../CompatibleCgms/CgmNightscoutUpload.md) - only if you know what you are doing, see [BG Source](../Getting-Started/CompatiblesCgms.md).
* [MM640g](../CompatibleCgms/MM640g.md)
-* [Glimp](#libre1-using-glimp) - only version 4.15.57 and newer are supported
+* Glimp - only version 4.15.57 and newer are supported
* [Build Your Own Dexcom App (BYODA)](#DexcomG6-if-using-g6-with-build-your-own-dexcom-app).
* [Poctech](../CompatibleCgms/PocTech.md)
-* [Tomato App](#libre1-using-tomato) for MiaoMiao device
+* Tomato App for MiaoMiao device
* [Glunovo App](https://infinovo.com/) for Glunovo CGM system
* [Ottai](../CompatibleCgms/OttaiM8.md)
* [Syai Tag](../CompatibleCgms/SyaiTagX1.md)
@@ -244,6 +244,10 @@ Through Wear tab or hamburger menu (top left of screen, if tab is not displayed)
* Resend all data. Might be helpful if watch was not connected for some time and you want to push the information to the watch.
* Open settings on your watch directly from your phone.
+### Autotune
+
+You can enable Autotune, see [here](../AdvancedOptions/Autotune.md).
+
### Maintenance
Access this tab to export / import settings.
diff --git a/docs/CROWDIN/it/SettingUpAaps/Preferences.md b/docs/CROWDIN/it/SettingUpAaps/Preferences.md
index d3840f615d9c..ea4ee5e93086 100644
--- a/docs/CROWDIN/it/SettingUpAaps/Preferences.md
+++ b/docs/CROWDIN/it/SettingUpAaps/Preferences.md
@@ -240,6 +240,10 @@ When using [SMB](#objectives-objective9), many people do not meal-bolus 100% of
* for people with slow digestion: sending all the bolus upfront can cause hypo because the insulin action is faster than the digestion.
* to leave more room to **AAPS** to deal by itself with **BG rise**. In both cases, **AAPS** will compensate for the missing part of the bolus with SMBs, if/when deemed adequate.
+### Old glycemia time threshold
+
+If the last **BG** received is older than this threshold, then the bolus wizard will by default offer a 100% dose instead of the **Deliver this part of bolus wizard result** setting above. The reason for this is that when **BG** is missing, **AAPS** will not be able to send the remaining part of the bolus afterward (the loop is not running), which would result in high **BG**.
+
### Enabled bolus advisor
Setting hidden in [simple mode](#preferences-simple-mode).
@@ -294,34 +298,7 @@ Use with caution and do not enable it until you learn what it really does. Basic
## Loop
-(Preferences-aps-mode)=
-### APS mode
-Switch between Open Loop, Closed Loop and Low Glucose Suspend (LGS).
-
-
-
-(Preferences-pen-loop)=
-#### Open Loop
-**AAPS** continuously evaluates all available data (IOB, COB, BG...) and makes treatment suggestions (temporary basal rates) on how to adjust your therapy if necessary.
-
-The suggestions will not be executed automatically (as in closed loop). The suggestions have to be enacted by the user manually into the pump (if using virtual pump) or by using a button if **AAPS** is connected to a real pump.
-
-This option is for getting to know how **AAPS** works or if you are using an unsupported pump. You will be in Open Loop, no matter what choice you make here, until the end of **[Objective 5](#objectives-objective5)**.
-
-(preferences-closed-loop)=
-#### Closed Loop
-
-**AAPS** continuously evaluates all available data (IOB, COB, BG...) and automatically adjusts the treatment if necessary (_i.e._ without further intervention by you) to reach the set [target range or value](#profile-glucose-targets) (bolus delivery, temporary basal rate, insulin switch-off to avoid hypo etc.).
-
-The Closed Loop works within numerous safety limits, which can be set individually.
-
-Closed Loop is only possible if you are in **[Objective 6](#objectives-objective6)** or higher and use a supported pump.
-
-#### Low Glucose Suspend (LGS)
-
-In this mode, [maxIOB](#Open-APS-features-maximum-total-iob-openaps-cant-go-over) is set to zero.
-
-This means that if blood glucose is dropping, **AAPS** can reduce the basal for you. But if blood glucose is rising, no automatic correction will be made. Your basal rates will remain the same as defined in your current **Profile**. Only if IOB is negative (from a previous Low Glucose Suspend) additional insulin will be given to lower **BG**.
+As of [AAPS version 3.4](#version3400), it is no longer possible to set the loop mode here. See [AAPS Screens > The Homescreen > Loop status](#AapsScreens-loop-status) to change loop mode now.
(Preferences-minimal-request-change)=
### Minimal request change
@@ -424,8 +401,11 @@ When using NSClientV3, all uploaders must be using the API V3. Since most are no
- Double check for typos here if you are stuck in Objective 1.
- Leave Connect to websockets enabled (recommended).
+(Preferences-nsclient-synchronization)=
### Synchronization
+
+
Synchronization choices will depend on the way you will want to use **AAPS**.
You can select which data you want to [upload and download to or from Nightscout](#Nightscout-aaps-settings).
diff --git a/docs/CROWDIN/it/SettingUpAaps/YourAapsProfile.md b/docs/CROWDIN/it/SettingUpAaps/YourAapsProfile.md
index 488ee9efcd6e..280f7b20d67d 100644
--- a/docs/CROWDIN/it/SettingUpAaps/YourAapsProfile.md
+++ b/docs/CROWDIN/it/SettingUpAaps/YourAapsProfile.md
@@ -1,11 +1,11 @@
# Your AAPS profile
Your **AAPS Profile** is a set of five key parameters which define how **AAPS** should deliver insulin in response to your sensor glucose levels. These are the main parameters **AAPS** is built upon. As you progress through the **Objectives**, you will unlock additional modifiable parameters (like SMB settings), but the performance of these features rely on your underlying **Profile** being correct. The **Profile** incorporates:
-* [duration of insulin action](#duration-of-insulin-action-dia) (DIA),
-* [glucose targets](#glucose-targets),
-* [basal rates](#basal-rates) (BR),
-* [insulin sensitivity factors](#insulin-sensitivity-factor-isf) (ISF) and
-* [insulin-to-carb ratios](#insulin-to-carb-ratio-icr) (IC or ICR).
+* [duration of insulin action](#your-aaps-profile-duration-of-insulin-action) (DIA),
+* [glucose targets](#profile-glucose-targets),
+* [basal rates](#your-aaps-profile-basal-rates) (BR),
+* [insulin sensitivity factors](#your-aaps-profile-insulin-sensitivity-factor) (ISF) and
+* [insulin-to-carb ratios](#your-aaps-profile-insulin-to-carbs-ratio) (IC or ICR).
As part of **AAPS**’ management, users should continually assess and scrutinise the accuracy of their **Profile** settings. It is recommended to take the settings in the order they are presented here. Aim to get one setting right before changing another. Work in small steps rather than making large changes at once. Don't forget to activate the new profile after each change. Regularly [backup your **Profile**](#YourAapsProfile_Profile-backup) settings by exporting your Preferences.
@@ -57,7 +57,7 @@ Example of a too-short **DIA** is a **high BG** followed by **AAPS** over-correc
### How to set it
-The **figure below** shows an example of how the **DIA** set in an **AAPS** profile.
+The **figure below** shows an example of how the **DIA** is set in an **AAPS** profile.
@@ -89,7 +89,7 @@ The **figure below** shows an example of how the target can be set in an **AAPS*
**BG** targets are set according to your personal preferences and requirements. For example, if you are concerned about hypos at night, you may set your target slightly higher at 117 mg/dL (6.5 mmol/L) from 9 pm - 7am. If you want to make sure you have plenty of insulin on board (IOB) in the morning before bolusing for breakfast, you may set a lower target of 81 mg/dL (4.5 mmol/L) from 7 am - 8 am.
-When In [Open Loop](#Preferences-pen-loop), especially when progressing through [the first objectives](../SettingUpAaps/CompletingTheObjectives.md), using a wide range target can be a good option while you are learning how **AAPS** behaves and adjusting your **Profile**.
When In [Closed Loop](#preferences-closed-loop) (starting at **[Objective 6](#objectives-objective6)**), it is recommended to reduce the range until you have a single target for each time of the day (_Low_ target = _High_ target), to make sure that **AAPS** reacts promptly to **BG** fluctuations.
+When In [Open Loop](#KeyAapsFeatures-OpenLoop), especially when progressing through [the first objectives](../SettingUpAaps/CompletingTheObjectives.md), using a wide range target can be a good option while you are learning how **AAPS** behaves and adjusting your **Profile**.
When In [Closed Loop](#KeyAapsFeatures-ClosedLoop) (starting at **[Objective 6](#objectives-objective6)**), it is recommended to reduce the range until you have a single target for each time of the day (_Low_ target = _High_ target), to make sure that **AAPS** reacts promptly to **BG** fluctuations.
(your-aaps-profile-basal-rates)=
@@ -123,11 +123,13 @@ The **figure below** shows an example of how the basal rates can be set in an **
Setting your basal rates right is done by trial and error, and should be done in consultation with your diabetic team.
-There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours.
+There are basal testing methods which usually entails observing your basal rates and insulin needs during an intermittent fasting over a 24-hour period. Although you need to test your basal rates for the whole day, it is not recommended to fast during 24h straight. This is because the body triggers mechanisms such as hormones to compensate. A recommended way is to fast 3 times for 8 hours.
-The recommended method is to suspend the loop, which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyse overnight BG lines in order to optimise your basal rates.
+The recommended method is to suspend the loop (for safety you can set AAPS to [**LGS**](#KeyAapsFeatures-LGS) to avoid lows, as done for achieving [objective 6](#objectives-objective6)), which will revert to your default background basal rate. Observe how your **BG** changes: if it is dropping, basal rate is too high. And vice versa.
An alternative method (may be more tricky) is to keep the loop running, and seeing how **IOB** changes. If **IOB** is negative, your basal rate is too high. And vice versa. Beware that this method relies on **ISF** to correct **BG**, and thus depends on other variables to be set reasonably well for it to be successful.
Another way of adjusting your basal rates is to watch the loop action during the night, when all COB have decayed. This method is particularly useful for children, when fasting is difficult or insulin needs change often. [Dr Saleh Adi from Tidepool](https://www.youtube.com/watch?v=-fpWnGRhLSo) provides useful ways on how to analyze overnight BG lines in order to optimize your basal rates.
-When taking action on the result of your basal testing, changes in the **Profile** should be done 1 hour before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings.
+See [here](../GettingHelp/ProfileTuning.md) how to tweak your basal profile, analyzing patterns in closed loop.
+
+When taking action on the result of your basal testing, changes in the **Profile** should be done 1 to 2 hours (depends on your insulin type) before the rise/drop. Repeat the test as necessary until you are comfortable with your **basal rates** settings.
(your-aaps-profile-insulin-sensitivity-factor)=
diff --git a/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md b/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md
index 217966ec0324..91f0d1eface2 100644
--- a/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md
+++ b/docs/CROWDIN/it/WearOS/WearOsSmartwatch.md
@@ -1,8 +1,8 @@
# Setup AAPS on your Wear OS watch
-The instructions below apply to the **AAPS Wear** apk that you need to build (see [here](../WearOS/BuildingAapsWearOS.md) if you haven't yet) as you've built the phone **AAPS** apk.
+The instructions below apply to the **AAPS Wear** apk that you need to build. If you haven’t built it yet, see the linked guide [here](../WearOS/BuildingAapsWearOS.md). When building, make sure to use the same keystore file that you used for the phone **AAPS** apk.
-You can also use some of the information for the **AAPSClient** and **PumpControl** **Wear** apk that are directly available in [GitHub](https://github.com/nightscout/AndroidAPS/releases/tag/3.2.0.4). Each **Wear** app will communicate with its matching phone app. For example: the **AAPSClient Wear** app can be used to display **AAPSClient** data and not **AAPS** data.
+You can also use some of the information for the **AAPSClient** and **PumpControl** **Wear** apk. Each **Wear** app will communicate with it's matching phone app. For example: the **AAPSClient Wear** app can be used to display **AAPSClient** data and not **AAPS** data.
## Wear OS Versions and compatibility
@@ -169,7 +169,7 @@ The final step is to configure **AAPS** on the phone to interact with **Wear.apk
* Select > Config Builder in the left-hand Hamburger tab
-* Tick for Wear selection under General
+* Tick for Wear selection under Synchronization
diff --git a/docs/CROWDIN/it/images/Pref2025_NSclient_Synchronization.png b/docs/CROWDIN/it/images/Pref2025_NSclient_Synchronization.png
new file mode 100644
index 000000000000..79428eff9630
Binary files /dev/null and b/docs/CROWDIN/it/images/Pref2025_NSclient_Synchronization.png differ
diff --git a/docs/CROWDIN/it/images/TreatmentsView6.png b/docs/CROWDIN/it/images/TreatmentsView6.png
new file mode 100644
index 000000000000..e96afed7f423
Binary files /dev/null and b/docs/CROWDIN/it/images/TreatmentsView6.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev.png b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev.png
new file mode 100644
index 000000000000..2ff9dd7602b6
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev_missing.png b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev_missing.png
new file mode 100644
index 000000000000..ec56fc94d59b
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev_missing.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev_missing_hamburger.png b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev_missing_hamburger.png
new file mode 100644
index 000000000000..da2179fe09c5
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dev_missing_hamburger.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_auto_nearby_dont_allow.png b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dont_allow.png
new file mode 100644
index 000000000000..f910368eecc9
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dont_allow.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_auto_nearby_dont_allow_anyway.png b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dont_allow_anyway.png
new file mode 100644
index 000000000000..d9007640643d
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_auto_nearby_dont_allow_anyway.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_auto_nearby_show_system.png b/docs/CROWDIN/it/images/android_16/android_auto_nearby_show_system.png
new file mode 100644
index 000000000000..6d39da7cd1be
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_auto_nearby_show_system.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_nearby_dev.png b/docs/CROWDIN/it/images/android_16/android_nearby_dev.png
new file mode 100644
index 000000000000..e949161a4ec5
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_nearby_dev.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_nearby_dev_system.png b/docs/CROWDIN/it/images/android_16/android_nearby_dev_system.png
new file mode 100644
index 000000000000..3bd3ab4acf0d
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_nearby_dev_system.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_perm_man_nearby_dev.png b/docs/CROWDIN/it/images/android_16/android_perm_man_nearby_dev.png
new file mode 100644
index 000000000000..b3c92ee38667
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_perm_man_nearby_dev.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_priv_control.png b/docs/CROWDIN/it/images/android_16/android_priv_control.png
new file mode 100644
index 000000000000..241c4d1b9406
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_priv_control.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_sec_priv.png b/docs/CROWDIN/it/images/android_16/android_sec_priv.png
new file mode 100644
index 000000000000..173733bf93f0
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_sec_priv.png differ
diff --git a/docs/CROWDIN/it/images/android_16/android_settings_sec_priv.png b/docs/CROWDIN/it/images/android_16/android_settings_sec_priv.png
new file mode 100644
index 000000000000..3e3c4c4fc579
Binary files /dev/null and b/docs/CROWDIN/it/images/android_16/android_settings_sec_priv.png differ
diff --git a/docs/CROWDIN/it/images/remote_control_and_following/AAPSClient_main_view.png b/docs/CROWDIN/it/images/remote_control_and_following/AAPSClient_main_view.png
new file mode 100644
index 000000000000..9991d5829ba5
Binary files /dev/null and b/docs/CROWDIN/it/images/remote_control_and_following/AAPSClient_main_view.png differ
diff --git a/docs/CROWDIN/it/index.md b/docs/CROWDIN/it/index.md
index 2d78031bcbed..dfebe1b55206 100644
--- a/docs/CROWDIN/it/index.md
+++ b/docs/CROWDIN/it/index.md
@@ -2,10 +2,10 @@
-```{admonition} Version 3.3
+```{admonition} Latest Release
:class: note
-29/12/2024 : La versione 3.3 è uscita. Controlla le [Release Notes](#version3300) per vedere cosa c'è di nuovo e ottenere le istruzioni per l'aggiornamento.
+14/08/2025 : Version 3.3.2.1 is out. Check the [Release Notes](#latestrelease) to see what's new and get update instructions.
```
@@ -21,7 +21,7 @@ Sezione **2) Per Iniziare**, l' [Introduzione](Getting-Started/Introduction.md)
Ora che hai una solida comprensione del processo, puoi iniziare a assemblare il tuo loop **AAPS**.
-Sezione **3) Impostare AAPS** contiene le istruzioni passo-passo per farlo. Copre la scelta e [l'impostazione del tuo server di rendicontazione](./SettingUpAaps/SettingUpTheReportingServer.md) (Nightscout o Tidepool) in modo da poter rivedere e condividere i tuoi dati, preparare il tuo computer per creare l'app AAPS, costruire l'app AAPS e trasferire l'app AAPS sul tuo telefono. Copre anche la configurazione dell'app **AAPS** utilizzando la procedura guidata di configurazione, collegarla con la tua app CGM, e un microinfusore reale o virtuale, oltre a collegare **AAPS** al tuo server di rendicontazione. Sei quindi lentamente introdotto al pieno utilizzo di ciò che **AAPS** ha da offrire tramite un processo passo dopo passo sicuro e accuratamente calibrato, progettato per assicurarsi che te/il tuo bambino siate completamente familiari e confortevoli navigando tutti i diversi livelli e configurazioni del menu prima di "diplomarti" nella fase successiva, comunemente indicato come il prossimo "Obiettivo", fino a quando non avrai esperienza sufficiente per iniziare a utilizzare le opzioni più avanzate disponibili all'interno dell'app. Questi Obiettivi sono appositamente progettati in modo tale da sbloccare gradualmente più possibilità di **AAPS** e passare dal circuito aperto al circuito chiuso.
+Sezione **3) Impostare AAPS** contiene le istruzioni passo-passo per farlo. It covers choosing and [setting up your reporting server](./SettingUpAaps/SettingUpTheReportingServer.md) (Nightscout or Tidepool) so you can review and share your data, getting ready for building the AAPS app, building the AAPS app and transferring the AAPS app to your phone. Copre anche la configurazione dell'app **AAPS** utilizzando la procedura guidata di configurazione, collegarla con la tua app CGM, e un microinfusore reale o virtuale, oltre a collegare **AAPS** al tuo server di rendicontazione. Sei quindi lentamente introdotto al pieno utilizzo di ciò che **AAPS** ha da offrire tramite un processo passo dopo passo sicuro e accuratamente calibrato, progettato per assicurarsi che te/il tuo bambino siate completamente familiari e confortevoli navigando tutti i diversi livelli e configurazioni del menu prima di "diplomarti" nella fase successiva, comunemente indicato come il prossimo "Obiettivo", fino a quando non avrai esperienza sufficiente per iniziare a utilizzare le opzioni più avanzate disponibili all'interno dell'app. Questi Obiettivi sono appositamente progettati in modo tale da sbloccare gradualmente più possibilità di **AAPS** e passare dal circuito aperto al circuito chiuso.
Sezione **4) Vita quotidiana con AAPS** copre le funzionalità chiavi di **AAPS**, per aiutarti a utilizzare (e personalizzare) **AAPS**. Include la comprensione degli schermi, CHO a bordo, sensibilità, cambio del profilo, target temporanei, CHO estesi (eCarbs), automazioni e sensibilità insulinica dinamica. Copre anche argomenti frequenti come: gestire diversi tipi di pasti, cambiare la cannula e il sensore, aggiornamenti dello smartphone, cambio dell'ora, [viaggiare con AAPS](DailyLifeWithAaps/TimezoneTraveling-DaylightSavingTime.md) e lo sport. Domande e risposte comuni si trovano nella sezione risoluzione dei problemi.
@@ -84,19 +84,21 @@ Panoramica componenti <./Getting-Started/ComponentOverview.md>
```
```{toctree}
-:caption: 3) Impostare AAPS
+:caption: 3) Setting up AAPS
-Impostazione del server di reportistica <./SettingUpAaps/SettingUpTheReportingServer.md>
+Setting up the reporting server <./SettingUpAaps/SettingUpTheReportingServer.md>
- Nightscout <./SettingUpAaps/Nightscout.md>
- Tidepool <./SettingUpAaps/Tidepool.md>
-Costruire AAPS <./SettingUpAaps/BuildingAaps.md>
-Trasferire e installare AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
-Configurazione guidata <./SettingUpAaps/SetupWizard.md>
-Il Tuo Profilo AAPS <./SettingUpAaps/YourAapsProfile.md>
-Cambiare la configurazione AAPS <./SettingUpAaps/ChangeAapsConfiguration.md>
+Building AAPS <./SettingUpAaps/BuildingAaps.md>
+- Browser Build <./SettingUpAaps/BrowserBuild.md>
+- Computer Build <./SettingUpAaps/ComputerBuild.md>
+Transferring and Installing AAPS <./SettingUpAaps/TransferringAndInstallingAaps.md>
+Setup Wizard <./SettingUpAaps/SetupWizard.md>
+Your AAPS Profile <./SettingUpAaps/YourAapsProfile.md>
+Change AAPS configuration <./SettingUpAaps/ChangeAapsConfiguration.md>
- Config Builder <./SettingUpAaps/ConfigBuilder.md>
-- Preferenze <./SettingUpAaps/Preferences.md>
-Completare gli obiettivi <./SettingUpAaps/CompletingTheObjectives.md>
+- Preferences <./SettingUpAaps/Preferences.md>
+Completing the objectives <./SettingUpAaps/CompletingTheObjectives.md>
```
```{toctree}
@@ -139,23 +141,26 @@ Scambio di quadranti personalizzati <./ExchangeSiteCustomWatchfaces/index.md>
```
```{toctree}
-:caption: 7) Manutenzione di AAPS
+:caption: 7) Maintenance of AAPS
-Esportazione/Importazione Impostazioni <./Maintenance/ExportImportSettings.md>
-Rivedere i tuoi dati <./Maintenance/Reviewing.md>
+Export/Import Settings <./Maintenance/ExportImportSettings.md>
+Reviewing your data <./Maintenance/Reviewing.md>
AAPS Release Notes <./Maintenance/ReleaseNotes.md>
-Aggiornamenti sulla documentazione <./Maintenance/DocumentationUpdate.md>
-Aggiornamento a una nuova versione di AAPS <./Maintenance/UpdateToNewVersion.md>
+Documentation updates <./Maintenance/DocumentationUpdate.md>
+Updating to a new version of AAPS <./Maintenance/UpdateToNewVersion.md>
+- Browser Update <./Maintenance/UpdateBrowserBuild.md>
+- Computer Update <./Maintenance/UpdateComputerBuild.md>
```
```{toctree}
-:caption: 8) Ottenere Aiuto
+:caption: 8) Getting Help
-Dove posso ottenere aiuto con AAPS <./GettingHelp/WhereCanIGetHelp.md>
-Risoluzione generale dei problemi <./GettingHelp/GeneralTroubleshooting.md>
-Risoluzione dei problemi Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md>
-Accesso ai file di log <./GettingHelp/AccessingLogFiles.md>
+Where can I get help with AAPS <./GettingHelp/WhereCanIGetHelp.md>
+General troubleshooting <./GettingHelp/GeneralTroubleshooting.md>
+- Bluetooth troubleshooting <./GettingHelp/BluetoothTroubleshooting.md>
+Troubleshooting Android Studio <./GettingHelp/TroubleshootingAndroidStudio.md>
+Accessing logfiles <./GettingHelp/AccessingLogFiles.md>
```
```{toctree}
@@ -184,4 +189,4 @@ FAQ <./UsefulLinks/FAQ.md>
Risorse generale diabete e looping <./UsefulLinks/BackgroundReading.md>
Account Google dedicato per AAPS (facoltativo)<./UsefulLinks/DedicatedGoogleAccountForAaps.md>
Per i medici (obsoleto) <./UsefulLinks/ClinicianGuideToAaps.md>
-```
\ No newline at end of file
+```