CamAPS companion routes
There are several different routes with similar names. Choose based on the app that actually contains your data.
Android xDrip+ companion route
Nightscout Pro supports a partial route using Android xDrip+ alongside a compatible CamAPS/companion setup. First configure the phone-side collection using the xDrip companion instructions. Confirm xDrip itself shows new readings; notification access and the compatible source app must remain working.
To establish the companion input, confirm the source app’s glucose notification is visible, select Companion App in xDrip Settings → Hardware Data Source, and grant xDrip the requested Android notification access. Match its display units to the source. If Android blocks the permission, follow the upstream restricted-access instructions for your OS rather than disabling unrelated security. Confirm a genuinely new reading; notification access alone is not proof of ingestion.
Once xDrip has current data, follow the complete xDrip+ upload steps. Compare a new reading in CamAPS, xDrip and Nightscout. Treatment and profile completeness is not established by this glucose route.
MyLife cloud testing
The portal’s CamAPS My Life (Testing) source is a different account connection. Follow its guide and validate the needed record types.
Native CamAPS Companion adapter
An experimental adapter exists in the connector project, but it is not a selectable ordinary self-service source in the verified Pro Connect menu. Do not enter invented source names or follow key-registration steps from an unrelated build. Ask support for a specifically supported route.
If xDrip is not receiving data, sending its empty history to Nightscout cannot fix the phone-side problem. Report the exact app/version, phone, country and where readings stop. Do not change pump or therapy settings to restore a cloud connection.