Remote monitoring
AAPS offers several features for remote monitoring of type 1 diabetic children, and also facilitates remote commands which send instructions to AAPS remotely. Similarly, AAPSClient can also be used for remote monitoring to follow your partner’s or friend’s AAPS.
Functions
Kid’s pump is controlled by kid’s phone using AAPS.
Caregivers can remotely follow viewing all relevant data such as glucose levels, carbs on board, insulin on board etc. using AAPSClient apk on their Android phone (an iPhone version of AAPSClient is in development, see AAPSClient). 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 is secured by two-factor authentication.
Remote control through AAPSClient uses the signed command channel introduced in AAPS 4: the client must first be paired with the master (with a QR code or a PIN), and every command is confirmed and executed by the master. Each caregiver’s phone can get its own role, from read-only to full control — see Master ↔ Client control.
Tools and apps for remote monitoring
Nightscout in web browser (mainly data display).
AAPSClient 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). There are 3 apps: AAPSClient, AAPSClient2 & AAPSClient3 to download, 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 in follower mode (mainly BG values and alarms).
Some users find a full remote access tool like TeamViewer 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 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).
Option 2 - The AAPS WearOS app 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.
Option 3 - Display only: a watch that AAPS does not support directly (Xiaomi, Amazfit, or a Wear OS watch showing a complication) can display glucose, IOB, COB and loop status through a companion app such as WatchDrip+ or GlucoDataHandler, fed by the External Companion Apps plugin of the AAPS or AAPSClient phone it is connected to. See External Companion Apps.
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.
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.