Fix Loop remote-command errors

First distinguish an intended remote command from a logged treatment. A Careportal record, accepted request or current glucose chart does not prove delivery to the Loop phone or pump.

Identify the failure

Record the Loop/caregiver app and version, Nightscout version, exact screen/button, action time and displayed result. Do not repeat an uncertain bolus or other treatment command as a test.

HTTP 500: Could not find LoopSettings in Profile

If the error is:

HTTP Error
Status Code: 500
Body: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, including LoopSettings, along with the device token to Nightscout so it can be used for overrides and remote commands. Enable it locally in Loop before trying to use the Nightscout or caregiver remote interface.

Glucose readings can be current while this profile data is missing. Selecting xCode or GitHub in Nightscout Pro sets the push environment; it does not send the missing profile data from Loop.

Allow Loop to upload the profile and device token to the connected Nightscout site. If the same error remains after this step, provide the exact error and time so support can check the uploaded profile/device-token state. Do not repeatedly send a bolus to test whether the connection works.

Check configuration

1. Confirm the Loop phone still uploads current data to this site.
2. Review the remote-command prerequisites, including the APNs key, matching key/team identifiers and authorized app workflow.
3. Check the actual installation/distribution method. Pro’s Loop Build Method must select the correct development or production push environment; TestFlight distribution is production even when built with Xcode.
4. For BadDeviceToken, have support compare that environment with the current uploaded device-token/profile state. Do not expose the token or key in screenshots.
5. Separate permission rejection, transport failure and a command the receiving app refused. Each needs the corresponding app/server evidence.

Persistent or uncertain result

Send the existing evidence once and keep the support case open until the actual result is established. Support should not claim that a command succeeded just because it was submitted. The local Loop override step above applies specifically to the missing LoopSettings error; do not send a bolus as a connection test.

A Trio remote-control problem needs Trio-specific setup; do not apply Loop APNs instructions automatically. Follow your established local care workflow when remote reliability is uncertain.

LoopDocs remote errors.