Merge #2615

Cherry picked for V4

Author: psonnera

docs/EN/Getting-Started/Introduction.md

@@ -19,7 +19,7 @@ So-called “dual-hormone” systems infuse glucagon alongside insulin, with the
 
 An artificial pancreas can be thought of as an [“autopilot for your diabetes”](https://www.artificialpancreasbook.com/). What does that mean?
 
-In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of permanently managing the aircraft, allowing the pilot to concentrate on wider monitoring. The autopilot receives signals from various sensors, a computer evaluates the data together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about constantly making decisions and this analogy can be applied to **AAPS**.
+In an aircraft, an autopilot does not do the complete job of the human pilot, the pilot cannot sleep through the entire flight. The autopilot aids the work of the pilot. It relieves them of the burden of constantly having to manage the aircraft, allowing the pilot to concentrate on wider monitoring. The autopilot receives signals from various sensors, a computer evaluates the data together with the pilot’s specifications and then makes the necessary adjustments, alerting the pilot to any concerns. The pilot no longer has to worry about continually making decisions and this analogy can be applied to **AAPS**.
 
 ![image](../images/autopilot.png)
 
@@ -96,7 +96,7 @@ To read about the safety features of the algorithms, known as oref0 and oref1, [
 
 Users can easily add or remove modules or functionality, and **AAPS** can be used in both open and closed loop mode. Here are some examples of the possibilities with the **AAPS** system:
 
- a) The ability to set a lower glucose target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L).
+ a) The ability to set a lower **BG** target 30 min before eating; you can set the target as low as 72 mg/dL (4.0 mmol/L).
 
  b) If you are insulin-resistant resulting in high blood sugars, **AAPS** allows you to set an **automation** rule  to activate when BG rises above 8 mmol/L (144 mg/dL), switching to (for example) a 120% profile (resulting in an 20% increase in basal and strengthening of other factors too, compared to your normal **profile** setting). The automation will last according to the scheduled time you set. Such an automation could be set to only be active on certain days of the week, at certain times of day, and even at certain locations.
 

docs/EN/RemoteFeatures/AapsClient.md

@@ -68,7 +68,9 @@ The client's home screen mirrors the followed loop:
 
 ## Treatments and actions
 
-Everything under **Manage** works like on the main app, with one important difference: on a client, actions that would change therapy (bolus, carbs, temp targets, profile switch, scenes…) are **hidden until the device is paired**, and once paired they are **relayed to the master** for confirmation and execution — see [Using remote control](#client-master-control).
+Everything under **Manage** works like on the main app, with one important difference: on a client, actions that would change therapy (bolus, carbs, temp targets, scenes…) are **hidden until the device is paired**, and once paired they are **relayed to the master** for confirmation and execution — see [Using remote control](#client-master-control).
+
+The **Profile** entry is the exception: it is shown even on an **unpaired** client, but opens **view-only** — the client shows the profiles it receives through Nightscout (it needs them for its own calculations), without edit or activate buttons. Once the client is **paired**, the profile list is synchronized with the master and you can edit and activate profiles from the client like any other remote action.
 
 ![The Manage screen on a paired client, including the Pair with master entry](../images/v4/AapsClient/aapsclient_manage.png)
 

docs/EN/RemoteFeatures/ClientMasterControl.md

@@ -67,7 +67,8 @@ Actions that can be triggered from a client in v4: **bolus**, **carbs / eCarbs**
 :class: important
 - The **master** runs the normal `full` **AAPS** build and is connected to your pump.
 - The **client** runs **[AAPSClient](AapsClient.md)** (or **AAPSClient2** / **AAPSClient3** for further patients — see [AAPSClient vs AAPSClient2](#remotecontrol-aapsclient-versions)).
-- **Both** phones use **NSClientV3** pointed at the **same** Nightscout, and are showing *connected*. Enabling **websockets** on **both** is strongly recommended for fast, near-instant round-trips.
+- **Both** phones use **NSClientV3** pointed at the **same** Nightscout, and are showing *connected*.
+- **Websockets** must be enabled on the **master** — without them the master cannot receive client commands at all, and your clients will see it as *not accepting commands*. Enable websockets on the client too for fast, near-instant round-trips.
 ```
 
 Pairing and synchronization are two different things:
@@ -86,6 +87,11 @@ On the master, open the **Manage** screen and choose **Authorized clients**.
 
 Turn on **Allow client control**. This is the master kill-switch: with it off, no client can send commands, but your paired clients are kept so you can turn it back on later.
 
+```{admonition} Websockets are required on the master
+:class: important
+Client commands only reach the master through the **websockets** connection of **NSClientV3**. If websockets are turned off, the **Authorized clients** screen shows a warning: *"Websockets are turned off, so commands from clients cannot be received. Clients see this master as not accepting commands until you turn websockets on."* Turn websockets on in the NSClientV3 settings to make client control work.
+```
+
 ![Authorized clients screen on the master](../images/v4/ClientMaster/authorized_clients_master.png)
 
 Tap the **+** button to add a client. Enter a **device name** (so you can recognize it in the list); the master then displays a short **pairing PIN**. This PIN is **one-time** and **expires after about two minutes**.
@@ -174,6 +180,12 @@ In the example below the mobile icon appears on *Smoothing*, *Calibration*, *Sen
 
 Connection details that are unique to each device — most importantly the **NSClient Nightscout URL / access token** — are *not* synced and are set on each phone individually.
 
+### Profiles
+
+Your **profile list** is also kept in sync between the master and its paired clients. On a paired client, **Manage → Profile** shows the same profiles as the master; you can **edit** a profile or **activate** one, and — like every other command — the change is sent to the **master**, applied there, and synced back.
+
+On a client that is **not paired**, the Profile screen is still available but **view-only**: the client shows the profiles it receives through Nightscout (it needs them for its own calculations), but there is no edit or activate button — there is no master to send the change to.
+
 ### Preferences
 
 A subset of **preferences** is **bidirectional**: you can change them on the **master or on a paired client**, and the change is synchronized to the other side. When you change such a preference on a client, it is sent to the master over the signed channel, applied there, and the authoritative value is sent back — so what you see on the client is always what the master stored. If the same preference is changed on two devices at almost the same time, the **most recent edit wins**.
@@ -214,7 +226,7 @@ If a client is restored from a backup that rolls its command counter backwards,
 | Client says it is **not paired** | Pair again from **Manage → Pair with master**. Confirm the client is **Active** in the master's **Authorized clients** list. |
 | Command **rejected** by the master | The master re-validates against its current state — e.g. the chosen profile no longer exists, or the pump type does not match. Re-check on the master. |
 | Commands work but are **slow** | Enable **websockets** on both phones (otherwise the apps fall back to slower polling). |
-| Nothing happens after pairing | Make sure **Allow client control** is ON on the master. |
+| Nothing happens after pairing | Make sure **Allow client control** is ON on the master, and that **websockets** are enabled on the master — without them the master cannot receive commands (the master's **Authorized clients** screen shows a warning). |
 
 For Nightscout / synchronization problems first see [Troubleshooting NSClient](../GettingHelp/TroubleshootingNsClient.md).
 

docs/EN/RemoteFeatures/RemoteMonitoring.md

@@ -10,25 +10,25 @@ __AAPS__ offers several features for remote monitoring of type 1 diabetic childr
 - Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using **AAPSClient apk** on their phone which must be an Android phone. Settings amended in __AAPS__ will synchronize with __AAPSClient__ and vice versa.
 - Caregivers can be alarmed by using **xDrip app in follower mode** on their Android phone if xdrip companion mode is set up.
 - Remote control of __AAPS__ using [SMS Commands](../RemoteFeatures/SMSCommands.md) is secured by two-factor authentication.
-- Remote control through __AAPSClient__ is only recommended if your synchronization is working well (i.e. you don’t see unwanted data changes like self modification of TT, TBR etc). See [release notes for Version 2.8.1.1](#important-hints-2-8-1-1) for further details. However, synchronization is less likely to be an issue if the user is using the latest version of __AAPS__ and __AAPSClient__ with NSClientv3/Nightscout 15.
+- Remote control through __AAPSClient__ uses the signed command channel introduced in **AAPS** 4: the client must first be **paired** with the master, and every command is confirmed and executed by the master — see [Master ↔ Client control](#client-master-control).
 
 ## Tools and apps for remote monitoring
 
-- [Nightscout](https://nightscout.github.io/) in web browser (mainly data display)
-- __AAPSClient__ apk is a stripped down version of __AAPS__ capable of following somebody, making __Profile Switches__, setting __TTs__ and entering carbs. There are 2 apps:  [AAPSClient & AAPSClient2 to download](https://github.com/nightscout/AndroidAPS/releases/). AAPSClient should be used if the caregiver wishes to install the apk twice on the same phone to follow 2 different persons (e.g. two children with type 1, each with their own Nightscout account).
-- Dexcom follow if you are using original Dexcom app (BG values only)
-- [xDrip](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**)
-- [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**)
-- Some users find a full remote access tool like [TeamViewer](https://www.teamviewer.com/) to be helpful for advanced remote troubleshooting 
+- [Nightscout](https://nightscout.github.io/) in web browser (mainly data display).
+- [__AAPSClient__](AapsClient.md) is a stripped down version of __AAPS__ capable of following the master __AAPS__ and, once **paired**, sending remote commands: carbs, __Temp Targets__, __Profile Switches__ and even boluses (see [Master ↔ Client control](#client-master-control)). There are 3 apps: [AAPSClient, AAPSClient2 & AAPSClient3 to download](https://github.com/nightscout/AndroidAPS/releases/), so a caregiver can follow up to three different persons from the same phone (e.g. two children with type 1, each with their own Nightscout account and master __AAPS__).
+- Dexcom follow if you are using original Dexcom app (BG values only).
+- [xDrip](../CompatibleCgms/xDrip.md) in follower mode (mainly BG values and **alarms**).
+- [Sugarmate](https://sugarmate.io/) or [Spike](https://spike-app.com/) on iOS (mainly BG values and **alarms**).
+- Some users find a full remote access tool like [TeamViewer](https://www.teamviewer.com/) to be helpful for advanced remote troubleshooting.
 
 ## Smartwatch options
 
 A smartwatch can be a very useful tool in helping manage __AAPS__ with T1D kids. A couple of different options are possible:
 
-- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current BG, loop status and allow carb entry, Temp Targets and Profile changes. It will NOT allow bolusing from the WearOS app.
-- Option 2 - Alternatively, the [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the parent. This includes all the functions listed above as well as the ability to bolus insulin. This allows the caregiver to administer insulin without needing to remove the kid's phone from however it is kept on them.
+- Option 1 - If __AAPSClient__ is installed on the caregiver's phone, the [AAPSClient WearOS app](https://github.com/nightscout/AndroidAPS/releases/) can be installed on a compatible smartwatch connected to the caregiver's phone. This will show current __BG__, loop status and bolus history, and allow carb entry, __Temp Targets__ and __Profile__ changes. If the client is **paired** with the master, the watch can also start a **bolus**: the command is relayed through the client to the master, which confirms and delivers it (see [Master ↔ Client control](#client-master-control)).
+- Option 2 - The [AAPS WearOS app](../WearOS/WearOsSmartwatch.md) can also be built and installed on a compatible smartwatch, connected to the kid's phone but worn by the caregiver. This includes all the functions listed above as well as the ability to bolus insulin directly, without the need to remove the kid's phone from their person.
 
 ## Things to consider
 
-- Consider time gap between master and follower due to time for up- and download as well as the fact that __AAPS__ master phone will only upload after loop run.
+- Consider time gap between master and follower due to time for up and download as well as the fact that __AAPS__ master phone will only upload after loop run.
 - What is your emergency plan for when remote control does not work (_e.g._ network problems or lost Bluetooth connection)? Always consider what will happen with **AAPS** if you suddenly can’t send a new command. **AAPS** overwrites the pump basal, ISF and ICR with the current profile values. Only use temporary profile switches (_i.e._ with a set time duration) if switching to a stronger insulin profile, in case your remote connection is disrupted. Then the pump will revert to the original profile when the time expires.