Using Nightscout Pro with APS apps

For an already configured Loop, Trio, iAPS or AAPS system, begin with the matching upload guide. The guide connects the app to Nightscout; it does not configure insulin delivery or validate a pump/sensor combination.

Keep the correct source of settings

APS apps normally manage their own therapy profiles and upload relevant records to Nightscout. Manual edits to an uploaded profile can be overwritten or change how another integration interprets it. AAPS configurations can also download selected data, so follow the documentation for the exact client and API version.

Do not activate an override, deliver a bolus, enter fake carbohydrates or change therapy settings just to refresh a Nightscout profile. Compare the app’s last upload, profile timestamp and connection error instead. If a profile remains stale, give support the app/version and the time of the legitimate change.

Verify more than glucose

After connecting, compare a new glucose reading and an existing treatment that the app is expected to upload. Check the profile timestamp if relevant. Missing treatment data is not repaired by adding a second glucose source.

Remote commands require their own permissions and configuration. A record appearing in Careportal is not proof that a command reached the phone or pump. Read remote-command guidance separately.