Upload AAPS to Nightscout Pro
Start with a working AAPS glucose source and record your AAPS version. Dexcom and Libre guide selections do not replace AAPS’s regional sensor/uploader requirements.
Choose the matching client
Open AAPS Config Builder and identify the Nightscout synchronization plugin in use. Follow that plugin’s preferences; do not mix credentials between the two clients.
- Original NSClient: enter the full HTTPS Nightscout site URL, without
/api/v1/, and the API Secret from Pro Site Settings. - NSClientV3: requires a compatible Nightscout version (15 or later in AAPS documentation). Use an admin-role access token from your Nightscout Admin Tools in NS access token. The API Secret is not the v3 token.
Keep Connect to websockets enabled for NSClientV3 as documented. Review the plugin’s upload/download synchronization choices for your intended setup; do not enable therapy-affecting downloads merely to test upload.
Avoid mixed streams
AAPS’s v3 guidance requires coordinated API v3 uploaders. Let AAPS provide the planned glucose/treatment stream and avoid adding a legacy bridge or independent non-v3 uploader to the same stream. If unsure, have support review the existing uploader list first.
Verify
Check the plugin’s connection/upload status and compare a new glucose reading plus an existing expected treatment in Nightscout. If glucose is present but treatments are missing, investigate the client’s data/synchronization settings rather than adding another glucose source.
For help, provide AAPS version, plugin name, Nightscout version, failed record type and redacted error. Keep the admin token private.