diff --git a/docs/CROWDIN/ar/images/favicon.ico b/docs/CROWDIN/ar/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/ar/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/cs/Configuration/xdrip.md b/docs/CROWDIN/cs/Configuration/xdrip.md index e90c831f141..9348f0ea2d7 100644 --- a/docs/CROWDIN/cs/Configuration/xdrip.md +++ b/docs/CROWDIN/cs/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/cs/Usage/Automation.md b/docs/CROWDIN/cs/Usage/Automation.md index 7e6d95be409..2cbea81a1f1 100644 --- a/docs/CROWDIN/cs/Usage/Automation.md +++ b/docs/CROWDIN/cs/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/cs/images.BACKUP/favicon.ico b/docs/CROWDIN/cs/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/cs/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/cs/images/favicon.ico b/docs/CROWDIN/cs/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/cs/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/de/Configuration/xdrip.md b/docs/CROWDIN/de/Configuration/xdrip.md index b274a59e827..46c86a4a0f6 100644 --- a/docs/CROWDIN/de/Configuration/xdrip.md +++ b/docs/CROWDIN/de/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/de/Usage/Automation.md b/docs/CROWDIN/de/Usage/Automation.md index c5410292dc6..1811b740852 100644 --- a/docs/CROWDIN/de/Usage/Automation.md +++ b/docs/CROWDIN/de/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? @@ -265,5 +265,5 @@ Check your rule prioritisation order as discussed above here. ## Alternatives to Automations -Für fortgeschrittene Benutzer gibt es andere Möglichkeiten, Aufgaben mit IFTTT oder einer Drittanbieter-Android-App namens Automate zu automatisieren. +For advanced users, there are other possibilities to automate tasks using IFTTT or a third party Android app called Automate. diff --git a/docs/CROWDIN/de/images.BACKUP/favicon.ico b/docs/CROWDIN/de/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/de/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/de/images/favicon.ico b/docs/CROWDIN/de/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/de/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/el/Configuration/xdrip.md b/docs/CROWDIN/el/Configuration/xdrip.md index 84c928c7516..1b52acf5127 100644 --- a/docs/CROWDIN/el/Configuration/xdrip.md +++ b/docs/CROWDIN/el/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/el/Usage/Automation.md b/docs/CROWDIN/el/Usage/Automation.md index c2411af5266..46080ca0436 100644 --- a/docs/CROWDIN/el/Usage/Automation.md +++ b/docs/CROWDIN/el/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/el/images.BACKUP/favicon.ico b/docs/CROWDIN/el/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/el/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/el/images/favicon.ico b/docs/CROWDIN/el/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/el/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/es/Configuration/xdrip.md b/docs/CROWDIN/es/Configuration/xdrip.md index 968abc1a7a7..248baef2855 100644 --- a/docs/CROWDIN/es/Configuration/xdrip.md +++ b/docs/CROWDIN/es/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/es/Usage/Automation.md b/docs/CROWDIN/es/Usage/Automation.md index f72b801880a..5e8f7fbb926 100644 --- a/docs/CROWDIN/es/Usage/Automation.md +++ b/docs/CROWDIN/es/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/es/images.BACKUP/favicon.ico b/docs/CROWDIN/es/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/es/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/es/images/favicon.ico b/docs/CROWDIN/es/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/es/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/fr/Configuration/xdrip.md b/docs/CROWDIN/fr/Configuration/xdrip.md index 0de0201de54..433375e0760 100644 --- a/docs/CROWDIN/fr/Configuration/xdrip.md +++ b/docs/CROWDIN/fr/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/fr/Usage/Automation.md b/docs/CROWDIN/fr/Usage/Automation.md index 65e5476c801..2098206774b 100644 --- a/docs/CROWDIN/fr/Usage/Automation.md +++ b/docs/CROWDIN/fr/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? @@ -265,5 +265,5 @@ Check your rule prioritisation order as discussed above here. ## Alternatives to Automations -Pour les utilisateurs avancés, il existe d'autres possibilités pour automatiser les tâches à l'aide de IFTTT ou d'une application Android tierce appelée Automate. +For advanced users, there are other possibilities to automate tasks using IFTTT or a third party Android app called Automate. diff --git a/docs/CROWDIN/fr/images.BACKUP/favicon.ico b/docs/CROWDIN/fr/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/fr/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/fr/images/favicon.ico b/docs/CROWDIN/fr/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/fr/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/he/Configuration/xdrip.md b/docs/CROWDIN/he/Configuration/xdrip.md index beb51bf9ab7..0dbc2f12c5e 100644 --- a/docs/CROWDIN/he/Configuration/xdrip.md +++ b/docs/CROWDIN/he/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/he/Usage/Automation.md b/docs/CROWDIN/he/Usage/Automation.md index d7c37c77c06..201b89a5c45 100644 --- a/docs/CROWDIN/he/Usage/Automation.md +++ b/docs/CROWDIN/he/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? @@ -265,5 +265,5 @@ Check your rule prioritisation order as discussed above here. ## Alternatives to Automations -למשתמשים מתקדמים, ישנן אפשרויות אחרות לבצע אוטומציה של משימות באמצעות IFTTT או אפליקציית אנדרואיד צד שלישי בשם Automate. +For advanced users, there are other possibilities to automate tasks using IFTTT or a third party Android app called Automate. diff --git a/docs/CROWDIN/he/images.BACKUP/favicon.ico b/docs/CROWDIN/he/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/he/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/he/images/favicon.ico b/docs/CROWDIN/he/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/he/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/it/images.BACKUP/favicon.ico b/docs/CROWDIN/it/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/it/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/it/images/favicon.ico b/docs/CROWDIN/it/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/it/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/ko/Configuration/xdrip.md b/docs/CROWDIN/ko/Configuration/xdrip.md index 6f0f12aed60..96c2cc5cd86 100644 --- a/docs/CROWDIN/ko/Configuration/xdrip.md +++ b/docs/CROWDIN/ko/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/ko/Usage/Automation.md b/docs/CROWDIN/ko/Usage/Automation.md index 47d1004de3e..66aae738512 100644 --- a/docs/CROWDIN/ko/Usage/Automation.md +++ b/docs/CROWDIN/ko/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/ko/images.BACKUP/favicon.ico b/docs/CROWDIN/ko/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/ko/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/ko/images/favicon.ico b/docs/CROWDIN/ko/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/ko/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/lt/Configuration/xdrip.md b/docs/CROWDIN/lt/Configuration/xdrip.md index 60b562907ea..33d51d803ba 100644 --- a/docs/CROWDIN/lt/Configuration/xdrip.md +++ b/docs/CROWDIN/lt/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/lt/Usage/Automation.md b/docs/CROWDIN/lt/Usage/Automation.md index 7172698d86c..561a189860a 100644 --- a/docs/CROWDIN/lt/Usage/Automation.md +++ b/docs/CROWDIN/lt/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/lt/images.BACKUP/favicon.ico b/docs/CROWDIN/lt/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/lt/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/lt/images/favicon.ico b/docs/CROWDIN/lt/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/lt/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/nl/Configuration/xdrip.md b/docs/CROWDIN/nl/Configuration/xdrip.md index 26a89f68917..5f1641f3013 100644 --- a/docs/CROWDIN/nl/Configuration/xdrip.md +++ b/docs/CROWDIN/nl/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/nl/Usage/Automation.md b/docs/CROWDIN/nl/Usage/Automation.md index fdae656d6cf..7ed891640da 100644 --- a/docs/CROWDIN/nl/Usage/Automation.md +++ b/docs/CROWDIN/nl/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/nl/images.BACKUP/favicon.ico b/docs/CROWDIN/nl/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/nl/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/nl/images/favicon.ico b/docs/CROWDIN/nl/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/nl/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/pb/Configuration/xdrip.md b/docs/CROWDIN/pb/Configuration/xdrip.md index 5a3e90bcc84..ce134185b43 100644 --- a/docs/CROWDIN/pb/Configuration/xdrip.md +++ b/docs/CROWDIN/pb/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/pb/Usage/Automation.md b/docs/CROWDIN/pb/Usage/Automation.md index eb453ad3f60..b6efb4f4d2d 100644 --- a/docs/CROWDIN/pb/Usage/Automation.md +++ b/docs/CROWDIN/pb/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/pb/images.BACKUP/favicon.ico b/docs/CROWDIN/pb/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/pb/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/pb/images/favicon.ico b/docs/CROWDIN/pb/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/pb/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/pl/Configuration/xdrip.md b/docs/CROWDIN/pl/Configuration/xdrip.md index d84e4ecf5db..535eeb8aa36 100644 --- a/docs/CROWDIN/pl/Configuration/xdrip.md +++ b/docs/CROWDIN/pl/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/pl/Usage/Automation.md b/docs/CROWDIN/pl/Usage/Automation.md index 81a04ccf55c..b20e380838b 100644 --- a/docs/CROWDIN/pl/Usage/Automation.md +++ b/docs/CROWDIN/pl/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/pl/images.BACKUP/favicon.ico b/docs/CROWDIN/pl/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/pl/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/pl/images/favicon.ico b/docs/CROWDIN/pl/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/pl/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/pt/Configuration/xdrip.md b/docs/CROWDIN/pt/Configuration/xdrip.md index 1241d1c1c56..35a6b40fc53 100644 --- a/docs/CROWDIN/pt/Configuration/xdrip.md +++ b/docs/CROWDIN/pt/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/pt/Usage/Automation.md b/docs/CROWDIN/pt/Usage/Automation.md index d89b072d908..5f1cb9a9ba6 100644 --- a/docs/CROWDIN/pt/Usage/Automation.md +++ b/docs/CROWDIN/pt/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/pt/images.BACKUP/favicon.ico b/docs/CROWDIN/pt/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/pt/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/pt/images/favicon.ico b/docs/CROWDIN/pt/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/pt/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/ro/Configuration/xdrip.md b/docs/CROWDIN/ro/Configuration/xdrip.md index 952dedada93..35f8ba65f16 100644 --- a/docs/CROWDIN/ro/Configuration/xdrip.md +++ b/docs/CROWDIN/ro/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/ro/Usage/Automation.md b/docs/CROWDIN/ro/Usage/Automation.md index d0565818e75..6ccd4b25163 100644 --- a/docs/CROWDIN/ro/Usage/Automation.md +++ b/docs/CROWDIN/ro/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/ro/images.BACKUP/favicon.ico b/docs/CROWDIN/ro/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/ro/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/ro/images/favicon.ico b/docs/CROWDIN/ro/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/ro/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/ru/Configuration/Preferences.md b/docs/CROWDIN/ru/Configuration/Preferences.md index 759a6187d55..1af4735329f 100644 --- a/docs/CROWDIN/ru/Configuration/Preferences.md +++ b/docs/CROWDIN/ru/Configuration/Preferences.md @@ -59,12 +59,12 @@ (Preferences-master-password)= ```{image} ../images/Pref2020_General2.png -:alt: Preferences > General - Protection +:alt: Настройки > Общие - Защита ``` #### Главный пароль -- Necessary to be able to [export settings](../Usage/ExportImportSettings.md) as they are encrypted from version 2.7. **Защита биометрией (отпечаток пальца, распознавание лица) может не работать на некоторых телефонах OnePlus. Это известная проблема телефонов OnePlus.** +- Необходимо для [экспорта настроек](../Usage/ExportImportSettings.md), т. к. они шифруются начиная с версии 2.7. **Защита биометрией (отпечаток пальца, распознавание лица) может не работать на некоторых телефонах OnePlus. Это известная проблема телефонов OnePlus.** - Откройте настройки (трехточечное меню в правом верхнем углу начального экрана) @@ -111,7 +111,7 @@ - Можно выбрать одну из четырех тем оформления: ```{image} ../images/Pref2021_SkinWExample.png - :alt: Select skin + :alt: Выбор внешнего вида ``` - 'Тема оформления в низком разрешении' содержит укороченные подписи и не показывает возраст сенсора, катетера /уровень инсулина, чтобы освободить больше места на экране с низким разрешением. @@ -153,17 +153,17 @@ - Определите, какие кнопки будут видны в нижней части главного экрана. ```{image} ../images/Pref2020_OV_Buttons.png - :alt: Preferences > Buttons + :alt: Настройки > Кнопки ``` - Для простоты ввода при помощи величины приращения можно задать параметры трех кнопок в диалоговых окнах инсулина и углеводов. ```{image} ../images/Pref2020_OV_Buttons2.png - :alt: Preferences > Buttons > Insulin + :alt: Настройки > Кнопки > Инсулин ``` ```{image} ../images/Pref2020_OV_Buttons3.png - :alt: Preferences > Buttons > Carbs + :alt: Настройки > Кнопки > Углеводы ``` (Preferences-quick-wizard)= @@ -174,7 +174,7 @@ - При настройке вы можете определить время, в течение которого кнопка будет видна на главном экране - только одна кнопка в определенный период. ```{image} ../images/Pref2020_OV_QuickWizard.png - :alt: Preferences > Quick Wizard Button Setup + :alt: Настройки: > Кнопка Мастера Быстрой настройки ``` - При нажатии на кнопку быстрого мастера AAPS будет вычислять и предлагать болюс на углеводы, основанный на ваших текущих коэффициентах (с учетом текущего значения ГК, активного инсулина и т. п.). @@ -199,7 +199,7 @@ - Выполните долгое нажатие в правом верхнем углу на главном экране или используйте оранжевую кнопку «Углеводы» внизу. ```{image} ../images/Pref2020_OV_DefaultTT2.png - :alt: Preferences > Use default temp targets + :alt: Настройки > Временные цели по умолчанию ``` ### @@ -263,7 +263,7 @@ ### Расширенные настройки (обзор) ```{image} ../images/Pref2021_OV_Adv.png -:alt: Preferences > Advanced Settings +:alt: Настройки > Дополнительные настройки ``` (Preferences-superbolus)= @@ -284,14 +284,14 @@ ### Максимально разрешённый болюс \[ед.\] - Максимальное количество болюсного инсулина, разово разрешаемое в AAPS. -- This setting exists as a safety limit to prevent the delivery of a massive bolus due to accidental input or user error. +- Эта настройка существует как ограничение безопасности для предотвращения подачи чрезмерного болюса из-за случайного ввода или ошибки пользователя. - Рекомендуется установить это значение как разумный предел, приблизительно соответствующий максимальному количеству болюсного инсулина, который вы когда-либо можете подать на еду или на коррекцию. - Это ограничение также налагается на результаты калькулятора болюса. ### Макс разрешенные углеводы [г.] - Это максимальное количество углеводов, на которое калькулятор болюса AAPS может подать дозу инсулина. -- This setting exists as a safety limit to prevent the delivery of a massive bolus due to accidental input or user error. +- Эта настройка существует как ограничение безопасности для предотвращения подачи чрезмерного болюса из-за случайного ввода или ошибки пользователя. - Рекомендуется установить это значение как разумный предел, приблизительно соответствующий максимальному количеству углеводов, которые вам когда-либо понадобится на еду. ## Замкнутый цикл @@ -464,51 +464,51 @@ :alt: Клиент NS ``` -Original communication protocol, can be used with older Nightscout versions. +Оригинальный протокол коммуникации, может использоваться с более ранними версиями Nightscout. -- Set your *Nightscout URL* (i.e. ). +- Создайте свой сайт *Nightscout URL* (напр. ). - **Убедитесь, что URL-адрес БЕЗ /api/v1/ в конце.** -- The *[API secret](https://nightscout.github.io/nightscout/setup_variables/#api-secret-nightscout-password)* (a 12 character password recorded in your Nightscout variables). +- *[API secret](https://nightscout.github.io/nightscout/setup_variables/#api-secret-nightscout-password)* (12-значный пароль записан в переменных Nightscout). - Это позволит считывать и записывать данные веб-сайту Nightscout и приложению AAPS. - Если вы застряли на Цели 1, еще раз проверьте поля с адресом и паролем на наличие опечаток. -## NSClientV3 +## Клиент NSV3 ```{image} ../images/Pref2024_NSClientV3.png -:alt: NSClientV3 +:alt: Клиент NSV3 ``` -[New protocol introduced with AAPS 3.2.](../Installing-AndroidAPS/Releasenotes.md#important-comments-on-using-v3-versus-v1-api-for-nightscout-with-aaps) Safer and more efficient. +[Новый протокол, начиная с AAPS 3.2.](../Installing-AndroidAPS/Releasenotes.md#important-comments-on-using-v3-versus-v1-api-for-nightscout-with-aaps) - безопаснее и эффективнее. -:::{admonition} V3 data uploaders -:class: warning When using NSClientV3, all uploaders must be using the API V3. Since most are not compatible yet, this means **you must let AAPS upload all data** (BG, treatments, ...) to Nightscout and disable all other uploaders if they're not V3 compliant. +:::{admonition} V3 загрузчики данных +:class: предупреждение При использовании NSClientV3, все загрузчики должны иметь API V3. Поскольку большинство из них пока несовместимы, это означает, что **следует разрешить AAPS загружать все данные** (BG, процедуры, ...) в Nightscout и отключить все остальные загрузчики, если они не совместимы с версией 3. ::: -- Set your *Nightscout URL* (i.e. ). +- Создайте свой сайт *Nightscout URL* (напр. ). - **Убедитесь, что URL-адрес БЕЗ /api/v1/ в конце.** -- In Nightscout, create an *[Admin token](https://nightscout.github.io/nightscout/security/#create-a-token)* (requires [Nightscout 15](https://nightscout.github.io/update/update/) to use the V3 API) and enter it in **NS access token** (not your API Secret!). +- В Nightscout создайте *[атрибут доступа администратора ](https://nightscout.github.io/nightscout/security/#create-a-token)* (для APIV3 требуется [Nightscout 15](https://nightscout.github.io/update/update/)) и введите его в качестве атрибута входа в **NS** (не путать с API Secret!). - Это позволит считывать и записывать данные веб-сайту Nightscout и приложению AAPS. - Если вы застряли на Цели 1, еще раз проверьте поля с адресом и паролем на наличие опечаток. -- Leave Connect to websockets enabled (recommended). +- Оставьте Подключение к websocket включенным (рекомендуется). -### Synchronization +### Синхронизация -Synchronization choices will depend on the way you will want to use AAPS. +Выбор синхронизации будет зависеть от способа использования AAPS. -You can select which data you want to [upload and download to or from Nightscout](../Installing-AndroidAPS/Nightscout.md#aaps-settings). +Выберите, какие данные [загружать в и выгружать из Nightscout ](../Installing-AndroidAPS/Nightscout.md#aaps-settings). ### Опции оповещения ```{image} ../images/Pref2024_NSClient_Alarms.png -:alt: Alarm options +:alt: настройки оповещений ``` -- Alarm options allows you to select which Nightscout alarms to use through the app. AAPS will alarm when a Nightscout alarms trigger. - - For the alarms to sound you need to set the Urgent High, High, Low and Urgent Low alarm values in your [Nightscout variables](https://nightscout.github.io/nightscout/setup_variables/#alarms). - - They will only work whilst you have a connection to Nightscout and are intended for parent/caregivers. - - If you have the CGM source on your phone (i.e. xDrip+ or BYODA) then use those alarms instead of Nightscout Alarms. -- Create notifications from Nightscout [announcements](https://nightscout.github.io/nightscout/discover/#announcement) will echo Nightscout announcements in the AAPS notifications bar. -- You can change stale data and urgent stale data alarms threshold when no data is received from Nightscout after a certain time. +- Опции звуковых оповещений позволяют выбрать оповещения Nightscout по умолчанию для использования через приложение. AAPS будет подавать звуковые сигналы при срабатывании оповещений Nightscout. + - Для того, чтобы работали оповещения, следует настроить значения переменных для Чрезвычайно Высокой, Высокой, Низкой и Чрезвычайно Низкой ГК в переменных [Nightscout](https://nightscout.github.io/nightscout/setup_variables/#alarms). + - Они будут работать только во время подключения к Nightscout и предназначены для родителей/опекунов. + - Если на телефоне есть источник мониторинга CGM (например xDrip+ или самостоятельно собранное приложение BYODA), то используйте сигналы этих приложений вместо оповещений Nightscout. +- [Оповещения ](https://nightscout.github.io/nightscout/discover/#announcement)Nightscout при соответствующих настройках будут повторяться в строке уведомлений AAPS. +- Вы можете изменять порог срабатывания оповещений при отсутствии данных от Nightscout в течение определенного времени. ### Параметры подключения @@ -516,7 +516,7 @@ You can select which data you want to [upload and download to or from Nightscout :alt: настройки подключения NSClient ``` -- Connection settings define when Nightscout connection will be enabled. +- Настройки подключения определяют, когда включено соединение с Nightscout. - Ограничьте загрузку в Nightscout только через Wi-Fi или даже через Wi-Fi SSID. - Если вы хотите использовать только конкретные сети WiFi, в настройках подключения укажите конкретный идентификатор сети WiFi SSID. - Несколько идентификаторов SSID разделяются точкой с запятой. @@ -529,7 +529,7 @@ You can select which data you want to [upload and download to or from Nightscout :alt: Дополнительные настройки NS клиента ``` -Options in advanced settings are self-explanatory. +Большинство опций в расширенных настройках самоочевидны. ## СМС-коммуникатор diff --git a/docs/CROWDIN/ru/Configuration/xdrip.md b/docs/CROWDIN/ru/Configuration/xdrip.md index 0a72a4bb24f..40af963b8b6 100644 --- a/docs/CROWDIN/ru/Configuration/xdrip.md +++ b/docs/CROWDIN/ru/Configuration/xdrip.md @@ -214,7 +214,7 @@ - Сканируйте Bluetooth и подключите мост. - → Сэндвич-меню (1) → Искать устройства Bluetooth (2) →Менее распространенные настройки (3) → Настройки Bluetooth (4) + → сэндвич-меню (1) → Сканировать Bluetooth (2) → Скан (3) - Если xDrip+ не может найти мост, убедитесь, что он не подключен к приложению поставщика. Зарядите его и выполните сброс его настроек. diff --git a/docs/CROWDIN/ru/Usage/Automation.md b/docs/CROWDIN/ru/Usage/Automation.md index e88fd723515..40d06f2049a 100644 --- a/docs/CROWDIN/ru/Usage/Automation.md +++ b/docs/CROWDIN/ru/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? @@ -265,5 +265,5 @@ Check your rule prioritisation order as discussed above here. ## Alternatives to Automations -Для опытных пользователей есть и другие возможности для автоматизации задач с помощью IFTTT или приложения других разработчиков Android под названием Automate. +For advanced users, there are other possibilities to automate tasks using IFTTT or a third party Android app called Automate. diff --git a/docs/CROWDIN/ru/Usage/completing-the-objectives.md b/docs/CROWDIN/ru/Usage/completing-the-objectives.md index 9b6b7cac57f..2f6e9559a4a 100644 --- a/docs/CROWDIN/ru/Usage/completing-the-objectives.md +++ b/docs/CROWDIN/ru/Usage/completing-the-objectives.md @@ -46,57 +46,57 @@ - Задачи для выполнения **Цели 2**: - Установите свой профиль в 90% на 10 минут (_Подсказка_: нажмите и удерживайте на имени своего профиля на экране НАЧАЛО) (_Примечание_: AAPS не принимает базальные дозы ниже 0,05 ЕД/ч. Если ваш профиль содержит базальные дозы 0,06 ЕД/ч или ниже, вам потребуется создать новый профиль с более высокими базальными дозами, прежде чем выполнять эту задачу. Вернитесь к своему обычному профилю после выполнения этого задания.) - Симитируйте «принятие душа», отключив помпу в **AAPS** на 1 час (_Подсказка_: нажмите значок петли на экране НАЧАЛО, чтобы открыть диалоговое окно «Цикл») - - End "taking a shower" by reconnecting your pump (_Hint_: press the "disconnected"-icon to open the loop dialog) - - Create a custom temporary target with a duration of 10 min (_Hint_: press the target bar on the OVERVIEW screen to bring up the temporary target dialog) - - Activate the **ACTIONS** plugin in **CONFIG BUILDER** to make it appear on the top scrollable menu bar (_Hint_: Go to **CONFIG BUILDER** and scroll down to 'General") - - Display the LOOP plugin's content - - Scale the BG-Chart to be able to look at larger or smaller timeframes: toggling between 6h, 12h, 18h 24h of past data (_Hint_: Tap the chart) + - Завершите приём душа, повторно подключив помпу (_Подсказка_: нажмите на значок «Разъединено», чтобы открыть диалоговое окно цикла) + - Создайте временную цель c продолжительностью 10 минут (_Подсказка_: нажмите на панель цели в экране НАЧАЛО, чтобы открыть диалоговое окно временной цели) + - Активируйте плагин **ДЕЙСТВИЯ** в **Конфигураторе**, чтобы он появился в верхней строке прокручиваемого меню (_Подсказка_: перейдите в **Конфигуратор** и прокрутите вниз до пункта «Общее») + - Отобразите содержимое плагина Замкнутый Цикл + - Масштабируйте диаграмму ГК, переключаясь между 6 часами, 12 часами, 18 часами и 24 часами данных за прошедшее время (_Подсказка_: короткое касание графика) (Objectives-objective-3-prove-your-knowledge)= ## Цель 3: Подтвердите ваши знания -- Pass a multiple-choice exam testing your **AAPS** knowledge. +- Пройдите тест с выбором варианта ответа для проверки на знание AndroidAPS. -Some users find **Objective 3** to be the most difficult objective to complete. Please do read the **AAPS** documents in conjunction with the questions. If you are genuinely stuck after researching the **AAPS** documents, please search the Facebook group for "Objective 3" (because it is likely that your question has been asked- and answered - before). If you are still stuck, ask in a post on either the Facebook or Discord group. These groups can provide friendly hints, or redirect you to the relevant part of the **AAPS** documents. +Некоторые пользователи считают **Цель 3** самой трудной. Прочитайте документацию **AAPS** вместе с вопросами. Если вы надолго застряли на цели после изучения документации **AAPS**, можете выполнить поиск в группе Facebook по запросу «Цель 3» (вполне вероятно, что ваш вопрос уже задавался и на него уже был дан ответ). Если вы все ещё застряли, спросите в группе Facebook или Discord. Эти группы могут дать подсказки или перенаправить вас на соответствующую часть документации AAPS. -To proceed with **Objective 3**, click on the orange text “**Not completed yet**” to access the relevant question. Please read each question carefully and select your answer(s). +Чтобы приступить к реализации цели 3, нажмите на оранжевый текст «Не завершено», чтобы получить доступ к соответствующему вопросу. Прочтите внимательно все вопросы и выберите ответ(ы). -- To reduce the number of decisions you are asked to make while in Open Loop, set a wide target range _e.g._ 90 - 150 mg/dl or 5.0 - 8.5 mmol/l. +- Чтобы уменьшить количество предлагаемых изменений базальной скорости в режиме открытого цикла, установите более широкий целевой диапазон, например 90–150 мг/дл или 5,0–8,5 ммоль/л. -- You might want to set a wider upper limit, or even disable Open Loop, at night. +- Вы можете увеличить верхнюю границу диапазона на ночь или вовсе отключить цикл на это время. -Для каждого вопроса правильным может быть больше одного ответа! If an incorrect answer is selected, the question will be time-locked for a certain amount of time (60 minutes) before you can go back and answer the question again. Be aware that the order of the answers may have changed when you next try to answer, this is to make sure you read them carefully and really understand the validity (or not) of each response. +Для каждого вопроса правильным может быть больше одного ответа! Если выбран неверный ответ, вопрос будет заблокирован на определенное время (60 минут), прежде чем вы сможете вернуться и ответить на вопрос. Имейте в виду, что порядок ответов может измениться при следующей попытке ответа,, чтобы убедиться, что вы внимательно прочитали их и действительно понимали правильность (или нет) каждого ответа. -When **AAPS** is installed for the first time, you will have to complete the whole of **Objective 3** before moving on to **Objective 4**. Каждая цель должна быть выполнена в последовательном порядке. Постепенно, по мере преодоления целей, будут открываться новые возможности приложения. +Когда **AAPS** устанавливается в первый раз, необходимо полностью пройти **цель 3** для того, чтобы перейти к **цели 4**. Каждая цель должна быть выполнена в последовательном порядке. Постепенно, по мере преодоления целей, будут открываться новые возможности приложения. -:::{admonition} **What happens if new question(s) are added to an Objective when I update to a newer version of AAPS?** +:::{admonition} **Что произойдет, если к Цели добавятся новые вопросы при обновлении до более новой версии APPS?** :class: Note -From time to time, new features are added to **AAPS** which may require a new question to be added to the Objectives, particularly Objective 3. As a result, any new question added to **Objective 3** will be marked as “incomplete” because **AAPS** will require you to action this. Do not worry, as each **Objective** is independent, you will **not lose the existing functionality of AAPS**, providing the other Objectives remain completed. +Время от времени в **AAPS** добавляется новая функциональность, что может потребовать добавления нового вопроса к Целям обучения, особенно к Цели 3. В результате любой новый вопрос, добавленный к **Цели 3**, будет помечен как «незавершённый», поскольку **AAPS** потребует от вас выполнить это действие. Не волнуйтесь, поскольку каждая **Цель** независима, вы **не потеряете существующую функциональность AAPS**, при условии, что другие Цели останутся выполненными. ::: ## Цель 4: Начните с открытого цикла -The purpose of this objective is to recognise how often **AAPS** will evaluate the basal rate's impact on glucose levels, and recommend temporary basal rate adjustments. As part of this objective, you will activate open looping for the first time, and will perform 20 proposed temporary basal rate changes manually on your pump. Furthermore, you will observe temporary and default temporary targets' impact (_e.g._ for activity or hypo treatments). If you are not familiar with setting a temporay basal rate change in **AAPS** yet, please refer to the [ACTIONS tab](Screenshots#Screenshots-action-tab). +Эта цель обучения нужна, чтобы показать, как часто **AAPS** будет оценивать влияние базальной дозы на уровень гликемии и как часто он рекомендует изменить базальную скорость. В рамках этой цели обучения вы впервые активируете открытый цикл, и вручную смените скорость временного базала до 20 раз. Кроме того, вы увидите влияние временных целей и Временных Целей По Умолчанию (например, при физической нагрузке или гипотерапии). Если вы еще не знакомы со сменой временной базальной скорости в **AAPS**, обратитесь к [вкладке ДЕЙСТВИЯ](Screenshots#Screenshots-action-tab). -Estimated time to complete this objective: **7 days**. This is a mandatory wait time. You can't proceed to the next Objective, even if you enacted all basal rate changes already. +Расчетное время для прохождения этой цели: **7 дней**. Это обязательное время ожидания. Вы не сможете перейти к следующей цели раньше, даже если выполнили все изменения базальной скорости. -- Select Open Loop either from the "Preferences" menu or by presssing and holding the Loop icon on the top left of the OVERVIEW screen. -- Walk through the [Preferences](../Configuration/Preferences.md) to set it up for you (scroll down to "Loop/APS Mode" and select "Open Loop". -- 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. -- Enable [temp targets](../Usage/temptarget.md) if necessary. After treating a hypo use hypo temp targets to prevent the system from overcorrecting upon the bounce back. +- Выберите «ОТКРЫТЫЙ ЦИКЛ» либо в меню «Настройки», либо нажав и удерживая значок «Цикл» в левой верхней части экрана НАЧАЛО. +- Просмотрите [Настройки](../Configuration/Preferences.md), чтобы настроить его для себя (прокрутите вниз до «Режим APS» и выберите «ОТКРЫТЫЙ ЦИКЛ». +- Вручную активируйте по крайней мере 20 предложений временного базала на протяжении 7 дней, введите их в помпу (физическую) и подтвердите в AAPS что вы их приняли. Убедитесь, что эти изменения базальной дозы отображаются в AAPS и Nightscout. +- При необходимости включите [временные Цели](../Usage/temptarget.md). После купирования гипогликемии используйте Временную Цель Гипо, чтобы предотвратить чрезмерную коррекцию системы при откате (при постгипогликемической гипергликемии). ### Сократите количество уведомлений -- To reduce the number of proposed basal rate changes while in Open Loop set a wider target range like 90-150 mg/dl or 5.0-8.5 mmol/l. -- You might even consider to raise your upper limit (or disable Open Loop) at night. -- You can set a minimum percentage for recommended basal rate changes to change the number of triggered notifications. +- Чтобы уменьшить количество предлагаемых изменений базальной скорости в режиме открытого цикла, установите более широкий целевой диапазон, например 90–150 мг/дл или 5,0–8,5 ммоль/л. +- Вы можете увеличить верхнюю границу диапазона на ночь (или вовсе отключить открытый цикл на это время). +- Вы можете установить минимальный процент предлагаемых изменений базальной скорости, чтобы повлиять на количество уведомлений. ```{image} ../images/OpenLoop_MinimalRequestChange2.png :alt: изменение минимального запроса на незамкнутом цикле ``` -:::{admonition} You don't need to action each and every system recommendation! +:::{admonition} Нет необходимости применять каждую рекомендацию системы! :class: Note ::: @@ -104,34 +104,34 @@ Estimated time to complete this objective: **7 days**. This is a mandatory wait ## Цель 5: Глубже понимаем работу системы в режиме незамкнутого цикла, включая ее рекомендации по временным базалам -As part of **Objective 5** you will start to understand how temporary basal recommendations are derived. This includes the [determination of basal logic](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html), analyzing the impact by observing [prediction lines in AAPS OVERVIEW](Screenshots-prediction-lines)/Nightscout and looking at detailed calculations shown on your OPENAPS tab. +В **Цели 5** вы начнете понимать, как формируются рекомендации по временному базальному инсулину. Сюда входит [определение логики базальной скорости](https\://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal. tml), анализ влияния с помощью наблюдения [линий прогноза в AAPS OVERVIEW](Screenshots-prediction-lines)/Nightscout и детальных расчетов, показанных на вкладке OPENAPS. -Estimated time to complete this objective: 7 days. +Расчетное время для прохождения этой цели: 7 дней. -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#Open-APS-features-max-u-h-a-temp-basal-can-be-set-to-openaps-max-basal). This value can be set in Preferences > OpenAPS. -Make sure this safety setting is set in both **AAPS** and your insulin pump. +Эта цель требует, чтобы вы определили и установили "максимально возможную для установки величину временного базала" (макс базал) согласно описанию в [OpenAPS-features](Open-APS-features#Open-APS-features-max-u-h-a-temp-basal-can-be-set-to-openaps-max-basal). Это значение может быть установлено в Настройках > OpenAPS. +Убедитесь, что эта настройка безопасности установлена как в **AAPS**, так и в помпе. -You might want to set your target higher than usual until you are comfortable with the calculations and settings. +Целевые значения гликемии следует несколько завысить до тех пор, пока вы не убедитесь в правильности всех вычислений и настроек. -**AAPS** allows: +**AAPS** допускает: -- a low target to be a minimum of 4 mmol/l (72 mg/dl) or maximum of 10 mmol/l (180 mg/dl) -- a high target to be a minimum of 5 mmol/l (90 mg/dl) and maximum of 15 mmol/l (225 mg/dl) -- a temporary target as a single value can be anywhere in the range of 4 mmol/l to 15 mmol/l (72 mg/dl to 225 mg/dl) +- установить нижнюю границу целевого значения ГК в диапазоне между 4 ммоль/л (72 мг/дл) и 10 ммоль/л (180 мг/дл) +- установить верхнюю границу целевого значения ГК в диапазоне между 5 ммоль/л (90 мг/дл) и 15 ммоль/л (225 мг/дл) +- временная цель может иметь любое значение от 4 до 15ммоль (72 мг/дл до 225 мг/дл) -Your target is a core value. All calculations are based on it. It is different from a target range which you usually aim to keep your blood glucose values in. If your target is very wide (say, 3 or more mmol/l [50 mg/dl or more] wide), you will often find little **AAPS** action. This is because sensor glucose is predicted to be somewhere in that wide range, and thus temporary basal rate changes are rarely suggested. +Ваша цель является основным значением. Все расчеты основаны на нем. Оно отличается от целевого диапазона, в котором вы обычно стремитесь поддерживать значения уровня глюкозы в крови. Если целевой диапазон широк (скажем, 3 или более ммоль/л [50 мг/дл или более]), реакция **AAPS** незначительна. Это связано с тем, что, по прогнозам уровня глюкозы он всё ещё находится где-то в этом широком диапазоне, и поэтому, временные изменения базальной скорости предлагаются редко. -You may want to experiment with adjusting your targets being in a tighter range (say, 1 or less mmol/l [20 mg/dl or less] wide) and observe a resulting system behaviour. +Можно поэкспериментировать и задать более близкие значения (например, чтобы их разность не превышала 1 ммоль) и наблюдать, как в результате изменится поведение системы. -You can adjust (widen or tighten) the graph’s green area, representing your target range, by entering different values in [Preferences](../Configuration/Preferences.md) > Range for Visualisation. +Вы можете скорректировать (расширить или сузить) зеленую область графика, представляющую ваш целевой диапазон, введя значения в [Настройки](../Configuration/Preferences.md) > Диапазон для визуализации. ```{image} ../images/sign_stop.png :alt: знак "Стоп" ``` -:::{admonition} If you have been using a virtual pump, change to a real insulin pump now! +:::{admonition} Если до этого вы использовали виртуальную помпу, переключитесь на настоящую инсулиновую помпу прямо сейчас! -If you are open looping with a virtual pump stop here. Only click verify at the end of this Objective once you have changed to using a "real" physical pump. +Если вы используете открытый цикл с виртуальной помпой, остановитесь на этой цели. Нажмите «Подтвердить» в конце этой цели только после того, как перейдете на использование «настоящей» физической помпы. ::: ```{image} ../images/blank.png @@ -146,55 +146,55 @@ If you are open looping with a virtual pump stop here. Only click verify at the :alt: предупреждающий знак ``` -:::{admonition} Closed loop will not correct high BG values in objective 6 as it is limited to low glucose suspend only! -:class: Note -You will still need to correct high BG values by yourself (manually with corrections by pump or pen)! +:::{admonition} Замкнутый цикл не будет корректировать высокие значения ГК в цели 6, поскольку он ограничен только приостановкой на низком уровне глюкозы! +:class: Примечание +Вам придётся корректировать высокие значения ГК самостоятельно (вручную с помощью помпы или ручки)! ::: -As part of **Objective 6** you will close the loop and activate its Low Glucose Suspend (LGS) mode while [max IOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob) is set to zero. You have to remain in LGS mode for 5 days to complete this objective. You should use this time to check if your profile settings are accurate and don't trigger LGS events too often. +В рамках **Цели 6** вы замкнёте цикл и активируете режим приостановки помпы на низкой ГК (LGS), пока значение [max IOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over- openaps-max-iob) установлено на ноль. Для достижения этой цели вы должны оставаться в режиме LGS в течение 5 дней. Следует использовать это время, чтобы убедиться в правильности настроек профиля и что события по приостановке помпы на низкой ГК не запускаются слишком часто. -Estimated time to complete this objective: 5 days. +Расчетное время для прохождения этой цели: 5 дней. -It's crucial that your current profile (basal, ISF, IC) is well tested before you close your loop in Low Glucose Suspend mode. Incorrect profile settings might force you into hypo situations which have be treated manually. An accurate profile will help to avoid needing low glucose treatments during the 5 days period. +Крайне важно, чтобы текущие параметры профиля (базал, ISF, IC) были тщательно протестированы, прежде чем вы закроете цикл в режиме приостановки помпы на низком ГК. Неправильные настройки профиля могут привести к гипогликемиям, которые придется купировать вручную. Точные настройки профиля помогут избежать необходимости в купировании гипогликемии в течение 5-дневного периода. -**If you still observe frequent or severe low glucose episodes consider refining your DIA, basal, ISF and carb ratios.** +**Если эпизоды низкой гликемии все же сохраняются, поправьте параметры DIA (продолжительность действия инсулина), скорость базала, ISF (фактор чувствительности к инсулину) и пропорции инсулин-углеводы.** -During objective 6, **AAPS** will take care of setting maxIOB to zero. **This override will be reversed when moving to objective 7.** +Во время выполнения цели 6 **AAPS** обнуляет maxIOB. **Это переопределение будет отменено при переходе к цели 7.** -This means that when you are on Objective 6, if sensor glucose levels are dropping, **AAPS** will reduce basal insulin delivery for you. If sensor glucose levels are rising, **AAPS** will only increase the basal rate above your profile value if basal IOB is negative as a result of from a previous Low Glucose Suspend. Otherwise, **AAPS** will not increase basal above your current profile value, even if glucose levels are rising. This caution is to avoid hypos as you are learning to use **AAPS**. +Это означает, что при выполнении цели 6, если уровень глюкозы падает, **AAPS** снизит количество базального инсулина. Если уровень глюкозы сенсора повышается, **AAPS** увеличит базальную дозу выше значения вашего профиля только в том случае, если базальный IOB отрицательный в результате предыдущей Приостановки помпы на Низкой ГК (LGS). В противном случае, **AAPS** не увеличит базальную скорость вашего профиля, даже если уровень глюкозы растёт. Эта сделано, чтобы избежать гипогликемии, когда вы только учитесь пользоваться **AAPS**. -**As a consequence, you have to handle high glucose values with manual insulin bolus corrections.** +**Как следствие, вам придётся корректировать высокие значения глюкозы вручную, через болюс.** -- If your basal IOB is negative (see screenshot below) a temporary basal rate (TBR) > 100% can be triggered in objective 6. +- Если ваш базальный IOB отрицательный (см. снимок экрана ниже), временная базальная скорость (TBR) > 100% может быть активирована в цели 6. ```{image} ../images/Objective6_negIOB.png :alt: Пример отрицательного IOB ``` -- Set your target range slightly higher than you usually would aim at, just to be safe and to add a safety buffer. -- Enable 'Low Glucose Suspend' mode by pressing and holding the Loop icon at the top right corner of the OVERVIEW screen and selecting the Loop - LGS mode icon. -- 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. +- В качестве дополнительной предосторожности установите целевой диапазон немного шире, чем ваш обычный. +- Включите режим «РЕЖИМ ОСТАНОВКИ НА НИЗКИХ LGS» нажав и удерживая значок Цикла в правом верхнем углу главного экрана и выбрав значок «Приостановка помпы на низкой ГК». +- Активные временные базалы отображаются бирюзовым цветом на экране OVERVIEW в виде текста или как часть графика. +- Возможны временные пики вслед за мерами против гипогликемии без возможности увеличить базу на откате. (Objectives-objective-7-tuning-the-closed-loop-raising-max-iob-above-0-and-gradually-lowering-bg-targets)= ## Цель 7: Настройка замкнутого цикла с поднятием макс величины IOB выше 0 и постепенным понижением целевой ГК -To complete **Objective 7** you have to close your loop and raise your [maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob). 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. +Для прохождения **Цели 7** нужно замкнуть цикл и повысить свой [maxIOB](Open-APS-features-maximum-total-iob-openaps-cant-go-over-openaps-max-iob). maxIOB был автоматически обнулен в **цели 6**. Сейчас это обнуление отменено. **AAPS** начнёт использовать заданное вами значение maxIOB для коррекции высоких значений глюкозы. -Estimated time to complete this objective: 1 day. +Расчётное время для прохождения этой цели: 1 день. -- Select 'Closed Loop' either from [Preferences](../Configuration/Preferences.md) or by pressing and holding the Loop icon at the top right corner of the OVERVIEW screen, over a period of 1 day. +- В течение одного дня выберите "Замкнутый цикл" либо в [Настройках](../Configuration/Preferences.md), либо нажав и удерживая значок цикла в правом верхнем углу главного экрана НАЧАЛО. -- Поднимите значение "Максимальный суммарный активный инсулин которое не может превысить алгоритм OpenAPS " (в OpenAPS называется "max-iob") выше 0. The default recommendation is "average mealbolus + 3x max daily basal" (for the SMB algorithm) or "3x max daily basal" (for the AMA algorithm) but you should slowly work up to this maximum until you know your settings work for you (max daily basal = the maximum hourly value in any time segment of the day). +- Поднимите значение "Максимальный суммарный активный инсулин которое не может превысить алгоритм OpenAPS " (в OpenAPS называется "max-iob") выше 0. Рекомендация по умолчанию - "средний болюс на прием пищи + 3-кратная максимальная базальная доза" (для алгоритма SMB) или "3-кратная максимальная базальная доза" (для более старого алгоритма AMA), но переходить к этому следует постепенно, пока не убедитесь, что настройки подходят для вас (максимальная базальная доза (в течение суток) = максимальное почасовое значение в любой временной отрезок дня). -Эта рекомендация должна рассматриваться как отправная точка. If you set it to the 3x and you are seeing AAPS giving too much insulin as glucose levels rise, then lower the "Maximum total IOB OpenAPS can’t go over" value. Alternatively, if you are very resistant, raise it very cautiously. +Эта рекомендация должна рассматриваться как отправная точка. Если вы установили это значение в 3 раза и видите, что AAPS выдает слишком много инсулина при повышении уровня глюкозы, тогда уменьшите значение "Максимальное общее количество IOB, которое не может превысить OpenAPS ". Кроме того, если у вас значительная резистентность, поднимайте его с осторожностью. ```{image} ../images/MaxDailyBasal2.png :alt: максимальный суточный базал ``` -- Once confident on how much IOB suits your looping patterns, reduce your targets to your desired level. +- Определив величину активного инсулина IOB, подходящую именно вам, понизьте целевое значение ГК до желаемого уровня. (Objectives-objective-8-adjust-basals-and-ratios-if-needed-and-then-enable-autosens)= @@ -202,7 +202,7 @@ Estimated time to complete this objective: 1 day. As part of this objective you will revist your profile's performance and will use autosens functionality as an indicator for wrong settings. -Estimated time to complete this objective: 7 days. +Расчетное время для прохождения этой цели: 7 дней. - You can use [autotune](https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html) as a one off to check your basals remain accurate or do a traditional basal test. - Enable [autosens](../Usage/Open-APS-features.md) over a period of 7 days and watch OVERVIEW's graph white line showing your insulin sensitivity rising or falling due to exercise or hormones etc. and keep an eye on the OpenAPS report tab which shows **AAPS** adjusting the basals and/or targets accordingly. diff --git a/docs/CROWDIN/ru/images.BACKUP/favicon.ico b/docs/CROWDIN/ru/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/ru/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/ru/images/favicon.ico b/docs/CROWDIN/ru/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/ru/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/sk/Configuration/xdrip.md b/docs/CROWDIN/sk/Configuration/xdrip.md index 5a3e90bcc84..ce134185b43 100644 --- a/docs/CROWDIN/sk/Configuration/xdrip.md +++ b/docs/CROWDIN/sk/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/sk/Usage/Automation.md b/docs/CROWDIN/sk/Usage/Automation.md index eb453ad3f60..b6efb4f4d2d 100644 --- a/docs/CROWDIN/sk/Usage/Automation.md +++ b/docs/CROWDIN/sk/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/sk/images.BACKUP/favicon.ico b/docs/CROWDIN/sk/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/sk/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/sk/images/favicon.ico b/docs/CROWDIN/sk/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/sk/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/sv/images.BACKUP/favicon.ico b/docs/CROWDIN/sv/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/sv/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/sv/images/favicon.ico b/docs/CROWDIN/sv/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/sv/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/tr/Configuration/xdrip.md b/docs/CROWDIN/tr/Configuration/xdrip.md index 2a2db76c310..0cc84cdaafb 100644 --- a/docs/CROWDIN/tr/Configuration/xdrip.md +++ b/docs/CROWDIN/tr/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/tr/Usage/Automation.md b/docs/CROWDIN/tr/Usage/Automation.md index 0062260a0e9..57097c5cd1e 100644 --- a/docs/CROWDIN/tr/Usage/Automation.md +++ b/docs/CROWDIN/tr/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? @@ -265,5 +265,5 @@ Check your rule prioritisation order as discussed above here. ## Alternatives to Automations -İleri düzey kullanıcılar için, IFTTT veya Automate adlı üçüncü taraf Android uygulamasını kullanarak görevleri otomatikleştirmenin başka olanakları da vardır. +For advanced users, there are other possibilities to automate tasks using IFTTT or a third party Android app called Automate. diff --git a/docs/CROWDIN/tr/images.BACKUP/favicon.ico b/docs/CROWDIN/tr/images.BACKUP/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/tr/images.BACKUP/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/tr/images/favicon.ico b/docs/CROWDIN/tr/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/tr/images/favicon.ico and /dev/null differ diff --git a/docs/CROWDIN/zh/Configuration/xdrip.md b/docs/CROWDIN/zh/Configuration/xdrip.md index 5a3e90bcc84..ce134185b43 100644 --- a/docs/CROWDIN/zh/Configuration/xdrip.md +++ b/docs/CROWDIN/zh/Configuration/xdrip.md @@ -215,7 +215,7 @@ Follow [these instructions](https://navid200.github.io/xDrip/docs/Dexcom/SensorF - Scan Bluetooth and connect the bridge. - → Hamburger Menu (1) → Scan Bluetooth (2) → Less common settings (3) → Bluetooth Settings (4) + → Hamburger Menu (1) → Scan Bluetooth (2) → Scan (3) - If xDrip+ can't find the bridge, make sure it's not connected to the vendor app. Put it in charge and reset it. diff --git a/docs/CROWDIN/zh/Usage/Automation.md b/docs/CROWDIN/zh/Usage/Automation.md index eb453ad3f60..b6efb4f4d2d 100644 --- a/docs/CROWDIN/zh/Usage/Automation.md +++ b/docs/CROWDIN/zh/Usage/Automation.md @@ -10,11 +10,11 @@ There are a wide range of automation options, and users are encouraged to study ## How Automation can help -1) **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. +1. **Decreasing decision fatigue:** The primary benefit of **automations** is to relieve the user from the burden of having to make manual interventions in **AAPS**. [Research](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6286423/#ref4) estimates that an average of 180 additional daily decisions have to be made by those living with Type 1 diabetes. **Automations** can lessen the mental load, freeing up the user’s mental energy for other aspects of life. -2) **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. +1. **Potentially improving glycemic control:** for example, **automations** can help ensure **Temp Targets** are always set when needed, even during busy schedules or periods of forgetfulness. For example, if a child with diabetes has sport scheduled at school on Tuesdays at 10am and Thursdays at 2pm and always needs a high temp target actioned 30 min before these activities, these can be actioned by automation. -3) **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. +1. **Enabling AAPS to be highly customised** to be more or less aggressive in specific situations, according to user preference. For example, triggering a temporary reduced profile% for a set period of time if negative **IOB** develops in the middle of the night, indicating that the existing profile is too strong. The example below illustrates how an **Automation** can enable steps to be eliminated. The user has set an **Automation** to trigger a 5 am ‘Temp Target Exercise’ to ensure their **BG** and **IOB** are optimal, in preparation for their 6 am exercise: @@ -22,17 +22,17 @@ The example below illustrates how an **Automation** can enable steps to be elimi ## Key considerations before starting with Automations -1) Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). +1. Before setting up an **Automation**, you should have reasonable BG control with **AAPS**. **Automations** should not be used to compensate for sub-optimal basal, ISF or ICR settings (discussed further below). Avoid setting an automated **Profile switch** to compensate for BG rises due to _e.g._ food, these are better dealt with via other strategies (SMBs etc). -2) As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. +1. As with any technology, **CGMs** and **Pumps** and **phones** can malfunction: Technical issues or sensor errors can disrupt the **Automation** actions, and manual intervention may be needed. -4) **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. +1. **Requirements for automations are likely to change as routines change**. When changing between work/school/holiday periods, set a reminder in your calendar to review which automations are currently active (they are easy to activate and de-activate). For example, if you go on holiday, and no longer need the automations set up for school sports or daily exercise, or need to adjust the timings. -5) Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. +1. Automations may conflict with each other, and it is good to review any new automation(s) setting carefully in a safe environment, and understand why an automation may or may not have triggered in the way you expect. -6) If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. +1. If using Autosense, try to use **Temp Targets** instead of **Profile Switches**. **Temp Targets** do not reset Autosens back to 0. **Profile Switches** reset Autosens. -7) Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. +1. Most automations should only be set for a **limited time duration**, after which **AAPS** can re-evaluate and repeat the automation, if necessary, and if the condition is still met. For example, "start temp target of 7.0 mmol/l for 30 min" or "start profile 110% for 10 min" _and_ "start temp target of 5.0 mmol/l for 10 min". Using automations to create permanent changes (e.g. to stronger %profile) risks hypoglycemia. ## When can I start using Automation? diff --git a/docs/CROWDIN/zh/images/favicon.ico b/docs/CROWDIN/zh/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/CROWDIN/zh/images/favicon.ico and /dev/null differ diff --git a/docs/EN/Installing-AndroidAPS/Update-to-new-version.md b/docs/EN/Installing-AndroidAPS/Update-to-new-version.md index 43a975933f5..0efd3573b6a 100644 --- a/docs/EN/Installing-AndroidAPS/Update-to-new-version.md +++ b/docs/EN/Installing-AndroidAPS/Update-to-new-version.md @@ -9,9 +9,7 @@ * When a new release is available, in the **AAPS** app itself, you will receive an information banner about the new version. * The new version will also be announced on Facebook at the time of release. * Following the release, please read the [Release Notes](../Installing-AndroidAPS/Releasenotes.md) in detail, and clarify any queries with the community on Facebook or Discord, before proceeding with the update. -* For **AAPS** versions 2.7 and newer, the location for the new files is at [https://github.com/nightscout/AndroidAPS](https://github.com/nightscout/AndroidAPS). -* You need to use the latest version of Android Studio, **[Hedgehog, 2023.1.1](https://developer.android.com/studio/)**. -* If building the **AAPS** app using a Windows platform, you will need to use a Windows 64-bit system since 32-bit systems are not supported. +* You need to use version **[Hedgehog (2023.1.1) or Iguana (2023.2.1)](https://developer.android.com/studio/)** of Android Studio. If your version is older, please update first Android Studio first! ## Overview for updating to a new version of AAPS @@ -31,9 +29,10 @@ See the [Export & import settings](ExportImportSettings-export-settings) page if (Update-to-new-version-update-your-local-copy)= ## 2. Update your local copy -As of version 2.7 repository location changed to [https://github.com/nightscout/AndroidAPS](https://github.com/nightscout/AndroidAPS). If you are not familiar with git the easiest way for update is remove directory with AAPS on your disk and follow the instructions to do a [New clone](../Installing-AndroidAPS/Building-APK.md). - -If you have already changed the URL or update from version 2.8.x, follow these steps: +:::{admonition} WARNING +:class: warning +If you update from versions prior to 2.8.x, please follow the instructions to do a [New clone](../Installing-AndroidAPS/building-AAPS), as this guide will not work for you! +::: * Open your existing AAPS project with Android Studio. You might need to select your project. (Double) click on the AAPS project. @@ -94,3 +93,5 @@ If anything goes wrong, don't panic. Take a breath! Then see the separate page [troubleshooting Android Studio](../Installing-AndroidAPS/troubleshooting_androidstudio) if your problem is already documented! + +If you need further help, please reach out to other **AAPS** users on [Facebook](https://www.facebook.com/groups/AndroidAPSUsers) or [Discord](https://discord.gg/4fQUWHZ4Mw). diff --git a/docs/EN/Installing-AndroidAPS/building-AAPS.md b/docs/EN/Installing-AndroidAPS/building-AAPS.md index 9110e25ff36..c8706d4a0bb 100644 --- a/docs/EN/Installing-AndroidAPS/building-AAPS.md +++ b/docs/EN/Installing-AndroidAPS/building-AAPS.md @@ -11,7 +11,7 @@ See [FAQ page](../Getting-Started/FAQ.md) for details. (Building-APK-recommended-specification-of-computer-for-building-apk-file)= ## Computer and software specifications for building AAPS -* Please use the **[Android Studio version called "Hedgehog"(2023.1.1)](https://developer.android.com/studio/)** to build the apk. If you use an older version, please use one which is no older than "**Giraffe**". +* Please use the **[Android Studio version called "Hedgehog"(2023.1.1) or "Iguana"(2023.2.1)](https://developer.android.com/studio/)** to build the apk. Older versions of Android Studio need to be updated first! * [Windows 32-bit systems](troubleshooting_androidstudio-unable-to-start-daemon-process) are not supported by Android Studio. Please keep in mind that both **64 bit CPU and 64 bit OS are mandatory condition.** If your system DOES NOT meet this condition, you have to change affected hardware or software or the whole system. @@ -64,6 +64,12 @@ If you think something in the building instructions is wrong, missing or confusi ## Step-by-step guide to building the AAPS app +:::{admonition} WARNING +:class: warning +If you have built AndroidAPS before, you don't need to take all the following steps again. +Please jump directly to the [update guide](../Installing-AndroidAPS/Update-to-new-version)! +::: + The overall steps for building the **AAPS** apk file are as follows: 4.1 [Install Git](Install-Git) @@ -134,7 +140,7 @@ When you first start Android Studio, you will be greeted as follows: ![Welcome](../images/Building-the-App/02_Welcome_AS_Hedgehog.png) - select "Next": +Select "Next": ![ChooseASComponents](../images/Building-the-App/03_choose_AS_components.png) @@ -158,6 +164,10 @@ Now select "Finish": Android Studio will now start. +If asked if you want to import settings, select "Do not import settings". We don't want to import settings from previous installations: + +![Do not import settings](../images/studioSetup/01_ImportSettings.png) + Decide whether you want to share data with Google or not (if unsure, just select "Don't send"). ![Share data with Google](../images/Building-the-App/08_Googlesharedata.png) @@ -202,7 +212,6 @@ Once everything is downloaded, the "Finish" button turns blue, and you can click ![finished_download_components](../images/Building-the-App/14_finished_downloading_components.png) You are now greeted with the "Welcome to Android Studio" screen. -See that Meet the New UI suggestion bottom right? **Do not** Enable New UI. ![Welcome_AS](../images/Building-the-App/15_Welcome_AS.png) @@ -218,7 +227,7 @@ Android Studio will then use **Gradle** (a development tool in Android studio) ::: -On the Android Studio Welcome screen, check that "**Projects**" (1) is highlighted on the left. Then click "**Get from VCS**" (2) at the top right: +On the Android Studio Welcome screen, check that "**Projects**" (1) is highlighted on the left. Then click "**Get from VCS**" (2) on the right: ![Get_from_VCS](../images/Building-the-App/16_Get_from_VCS.png) @@ -236,7 +245,12 @@ https://github.com/nightscout/AndroidAPS.git and paste it into the URL textbox (3). -* Check the (default) directory for saving the cloned code is sensible (4). +* Check the (default) directory for saving the cloned code is sensible (4). + +:::{admonition} INFORMATION +:class: information +Make a note of the directory. It is where your sourcecode is stored! +::: * Now click the button "Clone" (5). @@ -252,28 +266,30 @@ At some point, you may be asked whether you want to trust the project. Click on ![Trust project](../images/Building-the-App/18a_trust_project.png) -* If your firewall asks for permission, grant access: +Only for Windows users: If your firewall asks for permission, grant access: ![Firewall permission java](../images/AndroidStudio361_18.png) -If asked if you want to import settings, select "Do not import settings". We don't want to import settings from previous installations: - -![Do not import settings](../images/studioSetup/01_ImportSettings.png) +After the repository is cloned successfully, Android Studio will open the cloned project. -After the repository is cloned successfully, Android Studio will open the cloned project. Wait patiently (this may take a few minutes), and particularly, **do not** update the project as suggested in the pop-up. -:::{admonition} **My screen looks different...** -:class: dropdown +Click on the cog top right and select "**Switch to Classic UI...**" to return to the view used in this documentation. -You might have enabled the new graphic **U**ser **I**nterface (i.e. the appearance of Android Studio) by mistake. -Click on the cog top right and select "**Switch to Classic UI...**" to return to the view used in this documentation. -Restart Android Studio to validate the change. +If you do not see that cog, don't worry. You already use the classic UI! ![Switch to Classic UI](../images/Building-the-App/OldUI.png) +Restart Android Studio to make the changes effective. +![Confirm restart of Android Studio](../images/Building-the-App/18b_ConfirmRestartUI.png) + +You might get one or both of the following warnings about running processes. It's save to abort them! + +![Confirm abort background processes](../images/Building-the-App/18c_AbortBackgroundTasks.png) ![Confirm process AndroidAPS import](../images/Building-the-App/18d_AbortProcessImport.png) + + +When Android Studio opened again, wait patiently (this may take a few minutes), and particularly, **do not** update the project as suggested in the pop-up. -::: ![AS_download_dependencies](../images/Building-the-App/19_downloading_dependencies.png) @@ -289,18 +305,15 @@ _Optional_ - If you want to clear the pop-up for **"project update recommended"* ![AS_close_gradle_popup](../images/Building-the-App/20_close_popup.png) - If any errors occur, do not continue with the following steps, consult the [troubleshooting section](../Installing-AndroidAPS/troubleshooting_androidstudio) for known problems. - -Now close Android Studio (select _File_-_Exit_). - -If you have not restarted your computer since installing or updating Git, restart your computer now, and then re-open Android Studio. +For Windows users only: +If you have not restarted your computer since installing or updating Git, close Android Studio now. Then restart your computer, and re-open Android Studio. (Building-APK-set-git-path-in-preferences)= ### Set git path in Android Studio preferences Now we will tell Android studio where to find Git, which you installed [earlier](Install-Git). -* Make sure you have restarted your computer after [installing Git](Install-Git). +* Windows users only: Make sure you have restarted your computer after [installing Git](Install-Git). * Open **Android Studio** (you can find it by searching in the Start menu). * In the top left corner of **Android Studio**, navigate to _File-Settings_ (Windows) or _Android Studio > Preferences_ (Mac). This opens the following window, click to expand the dropdown called "version control" (1): @@ -351,8 +364,21 @@ Android requires each app to be _signed_, to ensure that it can only be updated ![APK instead of bundle](../images/Building-the-App/26_generate_APK.png) * In the next screen, make sure that "Module" is set to "AAPS.app" (1). + +(Building-APK-wearapk)= +:::{admonition} INFORMATION! +:class: information +If you want to create the apk for your watch, you need to select AAPS.wear! +::: + * Click "Create new..." (2) to start creating your key store. +:::{admonition} INFORMATION! +:class: information +You will only need to create the keystore once. +If you have build AndroidAPS before, do NOT create a new keystore but select your existing one! +::: + **_Note:_** The key store is a file in which the information for signing the app is stored. It is encrypted, and the information is secured with passwords. ![Create_key_store](../images/Building-the-App/27_new_keystore.png) @@ -366,7 +392,12 @@ Android requires each app to be _signed_, to ensure that it can only be updated ![Create key store](../images/Building-the-App/29_choose_keystore_file.png) -This will take you back to the previous screen. Your chosen location for saving the key store file is shown. +This will take you back to the previous screen. Your chosen location for saving the key store file is shown. + +:::{admonition} WARNING! +:class: warning +Make sure to note down for yourself where your keystore is stored. You will need it when you build the next AndroidAPS update! +::: Now choose a simple password (make a note of it), enter it in the password box (1), and confirm it (2). The passwords for key store and key do not have to be sophisticated. If you lose your password in the future, see [troubleshooting for lost key store](troubleshooting_androidstudio-lost-keystore). @@ -374,6 +405,11 @@ The default alias (3) for your key is "key0", leave this unchanged. You now need a password for your key. To keep it simple, if you want, you can use the same password you used for your keystore, above. Enter a password (4) and confirm (5) it. +:::{admonition} WARNING! +:class: warning +Note down these passwords! You will need them when you build the next AndroidAPS update! +::: + The validity (6) is 25 years by default, leave it as it is. Enter your first and last name (7). No other information needs to be added. @@ -416,7 +452,6 @@ In the Notifications box, click on the blue link "locate": Open the folder "release". The file "app-full-release.apk" (1) is the **AAPS** apk that you have just built, you will be transferring this file to your smartphone in the next section of the docs: -_Optional at this stage - if you are planning to also build the "**AAPS** wear" app for your smartwatch so you can remotely control **AAPS**, delete the "output-metadata" .json file (2) from this folder, to avoid the error of [uncommitted changes](troubleshooting_androidstudio-uncommitted-changes) during the **AAPS** wear app build_: ![apk_file](../images/Building-the-App/37_full_release_apk.png) diff --git a/docs/EN/conf.py b/docs/EN/conf.py index f1a6d7e3b05..8922110c43c 100644 --- a/docs/EN/conf.py +++ b/docs/EN/conf.py @@ -5,7 +5,7 @@ # The name of an image file (relative to this directory) to place at the top # of the sidebar. #html_logo = None -html_logo = '../drawing.png' +html_logo = '../androidaps-logo.png' # The name of an image file (relative to this directory) to use as a favicon of # the docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32 diff --git a/docs/EN/images/Building-the-App/15_Welcome_AS.png b/docs/EN/images/Building-the-App/15_Welcome_AS.png index aead4e8c1a0..f9474db0d7e 100644 Binary files a/docs/EN/images/Building-the-App/15_Welcome_AS.png and b/docs/EN/images/Building-the-App/15_Welcome_AS.png differ diff --git a/docs/EN/images/Building-the-App/16_Get_from_VCS.png b/docs/EN/images/Building-the-App/16_Get_from_VCS.png index 5e94a3c9683..b4fb05cdc73 100644 Binary files a/docs/EN/images/Building-the-App/16_Get_from_VCS.png and b/docs/EN/images/Building-the-App/16_Get_from_VCS.png differ diff --git a/docs/EN/images/Building-the-App/18_cloning_repository.png b/docs/EN/images/Building-the-App/18_cloning_repository.png index 5c314b37fd3..df59ea0a749 100644 Binary files a/docs/EN/images/Building-the-App/18_cloning_repository.png and b/docs/EN/images/Building-the-App/18_cloning_repository.png differ diff --git a/docs/EN/images/Building-the-App/18b_ConfirmRestartUI.png b/docs/EN/images/Building-the-App/18b_ConfirmRestartUI.png new file mode 100644 index 00000000000..ba678767ceb Binary files /dev/null and b/docs/EN/images/Building-the-App/18b_ConfirmRestartUI.png differ diff --git a/docs/EN/images/Building-the-App/18c_AbortBackgroundTasks.png b/docs/EN/images/Building-the-App/18c_AbortBackgroundTasks.png new file mode 100644 index 00000000000..d30f7ddf686 Binary files /dev/null and b/docs/EN/images/Building-the-App/18c_AbortBackgroundTasks.png differ diff --git a/docs/EN/images/Building-the-App/18d_AbortProcessImport.png b/docs/EN/images/Building-the-App/18d_AbortProcessImport.png new file mode 100644 index 00000000000..ca857a88299 Binary files /dev/null and b/docs/EN/images/Building-the-App/18d_AbortProcessImport.png differ diff --git a/docs/EN/images/favicon.ico b/docs/EN/images/favicon.ico deleted file mode 100644 index da2a0269569..00000000000 Binary files a/docs/EN/images/favicon.ico and /dev/null differ diff --git a/docs/drawing.png b/docs/androidaps-logo.png similarity index 100% rename from docs/drawing.png rename to docs/androidaps-logo.png diff --git a/docs/favicon.ico b/docs/favicon.ico index da2a0269569..84aa9be6199 100644 Binary files a/docs/favicon.ico and b/docs/favicon.ico differ diff --git a/docs/shared.conf.py b/docs/shared.conf.py index 10b3bc43070..4c42549b204 100644 --- a/docs/shared.conf.py +++ b/docs/shared.conf.py @@ -167,7 +167,7 @@ # The name of an image file (relative to this directory) to place at the top # of the sidebar. #html_logo = None -html_logo = '../../drawing.png' # path relative to languages conf.py +html_logo = '../../androidaps-logo.png' # path relative to languages conf.py # The name of an image file (relative to this directory) to use as a favicon of # the docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32