Configure Loop remote commands

Remote control is separate from viewing and ordinary Loop uploads. Nightscout Pro supports the Nightscout side of compatible Loop remote features; the actual command, app versions and authorization must match the upstream workflow. The older blanket claim that only overrides exist is not a current feature guide.

Before configuration

Confirm Loop already uploads to the correct site. Record the Loop and Nightscout versions and how the installed app was distributed. Read LoopDocs remote configuration and remote command instructions before enabling actions. Loop 3 remote carbohydrate/bolus support has version requirements, including Nightscout 14.2.6 or later in upstream guidance.

Enter the Pro settings

1. Use the upstream Apple Developer procedure to create the appropriate APNs key. It is distinct from an App Store Connect/GitHub build API key.
2. In Pro Site Settings, open the Loop configuration and enter the complete key into LOOPAPNSKEY, its identifier into LOOPAPNSKEYID, and the matching team into LOOPDEVELOPERTEAMID.
3. Set Loop Build Method to match the installed app’s push environment. Pro labels the options xCode and GitHub. A direct Xcode-to-phone installation uses the development setting. TestFlight or other production distribution uses the production setting, even if originally built with Xcode; the Pro GitHub option sets that production environment.
4. Save the site settings and configure the authorized caregiver app/interface according to its exact version. Do not copy Loop instructions into Trio merely because both use Nightscout.

Keep APNs keys and command credentials private. A read-only viewer setup is not evidence that the separate remote-control authorization has been completed.

Missing LoopSettings in the profile

If a remote command returns HTTP 500: Loop notification failed: Could not find LoopSettings in Profile., first enable an override directly in the Loop app on the phone running Loop. This sends the profile data and device token to Nightscout so it can be used for overrides and remote commands. The Loop Build Method selection configures the push environment; it does not upload this profile data. See the LoopSettings troubleshooting steps.

Verify transport without inventing a treatment

Check source freshness, uploaded profile/device status, configuration and app/server errors first. For general connectivity checks, do not give a bolus or enter fake carbohydrates. The local override step above is the specific solution for the missing LoopSettings error. Any medically meaningful action must follow the user’s intended care workflow and upstream precautions.

A Careportal Correction Bolus record can be a logged event rather than a sent command. Determine which app/button was used and inspect the command result; a saved treatment or HTTP acknowledgement does not prove receipt or insulin delivery. If the result is uncertain, do not repeat the action blindly.

For an error such as BadDeviceToken, inspect the installed distribution environment and current uploaded device token with support. Provide versions, build/distribution method, exact UI path, action time and redacted error once. See command troubleshooting.