Nightscout Configuration - trupici/G-Watch-Wear GitHub Wiki

Nightscout is a web application, G-Watch Wear App has a built-in client to poll BG data from it.

Use this solution if you are monitoring someone else. You can use this solution also in the case when your CGM app is not directly supported by G-Watch app.

Open the G-Watch Wear App Data source settings. Scroll down to Nightscout settings. You need to enter the NightScout application URL.

If you have your application hosted on Heroku, enter the URL in the following form: https://app-name.herokuapp.com

In this case you usually don’t need to enter API Secret as no data is uploaded to the server. You can also append path "/api/v1", otherwise it will be added automatically.

If your NightScout application is hosted on another cloud or you use custom security settings, you might need to enter also the API Secret to access your NightScout data.

If you use a specific role in NightScout settings and you have a special Access Token, then you have to enter also this token.

If you are using custom hosting and there is a problem with server certificate (self-signed certificate, unknown CA, etc, …), you can use “Explicit Certificate Trust” option to allow connection to server with untrusted certificate.

If you see missed readings from server (0 entries received message occurs in the packet view console) on nearly every regular 5 minutes schedule server request and values are received only at the next retry request (after 1 minute), you can increase the cloud latency parameter to avoid retries.

If you receive values always at the first server request (regular 5 minutes schedule) then you can try to decrease the cloud latency parameter to receive new values a bit sooner after measurement.

Note that only one cloud data source (follower) can be active at a time.

Always use menu option "Send all values" to apply configuration for NightScout data source.