Troubleshooting Nightscout issues¶

The major categories of Nightscout troubleshooting include:

Connectivity. The rig and Nightscout are practiced friends. Data is unremarkably two-way so long as the rig has access to the internet (aka, online use). When rigs go "offline", NS will go stale until cyberspace is again bachelor. If you lot're having issues with NS and it's a brand new setup, you'll want to double bank check per the beneath that URL, API hole-and-corner, etc. are correct.

Mlab size is too big and you demand to make clean it. See beneath for how to check the size of, and compact if needed, your mlab database, which tin can influence what displays in Nightscout.

Future data. Sometimes entries will get time stamped incorrectly, or the device time zones are off. See below for how to resolve.

Top level troubleshooting for rig-Nightscout issues

Setting up your NS hosting site¶

You will need to brand certain that you have setup yous site configuration settings in your NS hosting site (usually that means Heroku) according to the docs. See the Nightscout Setup page for assist in setting up your NS site. If you don't add the OpenAPS-specific settings to your setup, the communications with the rig will not piece of work properly.

What information is passed from rig to NS?¶

The rig uploads the following information to NS:

  • Bold pump communications are good, the rig will read information from the pump as follows:
    • boluses and carbs; entered through either the pump bolus wizard or the easy bolus button
    • current temp basal rate and duration/fourth dimension set
    • pump status; bolusing or suspended, reservoir volume, pump battery voltage
    • pump notes; time changes, profile changes, battery changes, alarms (these show as grey dots on NS site)
    • if a MDT enlite user, BGs will exist read directly from the pump
  • From OpenAPS looping, the additional information is also uploaded:
    • make up one's mind-basal data (such as IOB, COB, temp basal enacted, etc) goes to fill out the OpenAPS pill in NS
    • rig battery voltage and estimated %
  • If (ane) a dexcom receiver is continued to the rig and (2) the loop is setup with G4-upload equally the CGM type and (3) the rig has internet, and so the rig volition also upload BGs and/or rawBG straight to NS. This keeps the loop functional even if the Share app fails. For example, if the phone battery dies during the night, and Share App therefore goes down...the rig tin read BGs/rawBGs directly from the receiver and use your abode wifi to upload to NS even so.

What data is passed from NS to rig?¶

The careportal "treatment" entries and BG data are the two most of import items transmitted from NS to the rig.

  • Careportal entries transmitted and USED by the loop are:
    • carb entries
    • temp BG targets
  • BG values from Dexcom share servers via the NS span

mLab maintenance¶

Your NS data is stored in a place called an mLab database. This mLab database is free so long equally you stay below a 500mb information limit. Inevitably, later on several months of OpenAPS use, you may fill that free information storage limit. Typically, yous won't be notified of that issue...instead you'll start to detect sudden bug with your NS site when you haven't washed anything dissimilar. Strange symptoms include, only aren't limited to:

  • OpenAPS and Pump pills not working, but still looping and displaying temp basals (devicestatus collection)
  • BG values going stale and dexcom bridge stopping, which may break looping (entries collection)
  • temp basals no longer rendered, but looping still works (treatments collection)
  • careportal treatments (carbs, boluses) no longer displaying properly (treatments collection)

If yous are seeing strange behavior in your previously-working-fine NS site, you'll want to check your mLab database size. Strange behaviour tin include missing bolus or other treatment information. You may besides get a 500 fault (failed to insert record) message in NightScout when trying to save a treatment, such as logging carbs. To admission your mLab database, you will need to click on the mLab integration from within your Heroku dashboard as shown below. Based on which symptoms you're seeing from the above list, start past checking the size of the referenced collection.

mLab access from Heroku dashboard

From that screen, yous will need to click on the Home link nigh the pinnacle left of the page.

mLab home button

The resulting screen will prove you the important data to straight where you need to accept action. At that place are TWO areas where the 500 MB information limit tin be an effect. One issue area is the size on disk , which is the virtual space that your database takes upward. As data is written onto your database, sometimes information technology is written inefficiently and most "spreads out" to take up more room than information technology normally would. The other result surface area is the size which is the actual information stored in your database. Depending on where your issue is, yous may demand to compact data (if size on deejay is the event) or cleanout data (if size is the issue).

mLab database sizes

Compact data¶

If size on deejay is close to 500mb, you'll demand to compact your database. To begin the compaction process, click on your database name.

mLab database name

Then click on the Tools tab in the screen that opens. Click on the commands button and then select the repairDatabase from the dropdown menu of available commands. At the lesser of the screen, select the Run Control button.

mLab compact tools

Return to your dwelling screen and you volition exist able to verify the Size on Disk has decreased.

mLab compact verify

Annotation most inability to meaty data. Several people have reported that they go a timeout error when following the above compacting instructions and the size on disk is not reduced. Try once again and this text may appear. "If later on issuing this command your Sandbox database however has a Size on Disk (file size) greater than 496 MB, see our FAQ for possible explanations." If you run into this event, you can send an email to mLab support at support@mlab.com and they will meaty the database for yous.

Cleanout data¶

NOTE: Before you cleanout your information, please bank check out the option to upload (or "donate") your data anonymously to the OpenAPS Data Commons project. The OpenAPS Data Commons was created to enable a simple way to share data sets from the community, both with traditional researchers who will create traditional research studies, and with groups or individuals from the community who want to review data as role of their ain research projects. And then before yous delete or cleanout any information from your mLab, consider doing an upload to OpenAPS Data Commons first.

If your mLab database issue is size , and then you will demand to cleanout some of the historical data collected by your NS site. There are 2 methods to cleanout infinite and delete data in your mLab database:

  • mLab direct access
  • Nightscout admin tools

mLab Directly Admission¶

  • Login to your mLab database, as shown in a higher place, past clicking on the mLab logo in your Heroku dashboard. Your various collections are shown, like to the screen shot above. The amount of information each collection is using is listed to the far right of each collection's line. Do not cleanout your profile collection, that is needed past NS. Additionally, if you utilise tokens for your NS site, you will want to leave the auth_subjects collection intact. The entries collection are typically BG information from your bridge. The treatments collection are information from your careportal entries either through NS or uploaded via the rig (e.one thousand., carbs, boluses, temp basals, notes of pump events, and temp targets). The devicestatus collection houses basically all the information that is presented in the OpenAPS pill brandish (determine-basal, BG predictions, IOB, COB, etc). If y'all utilize NS reports for your endo appointments, try to time the data cleanout for after an appointment and then that you can rebuild a treatment history before the next date.
  • Click on a collection's name to open it.

mLab collection select

  • Click on the push that says "Delete all documents in collection" and then confirm the deletion.

mLab collection select

  • You can confirm that your cleanout has resolved the problem, by checking that your database size is below 500 MB now. Click on the Home link in pinnacle left. And then review the size of the database equally shown (note: Screenshots are from different databases...they are but to show how to navigate and what results you lot are looking for. Minor inconsistencies in continuity of the screenshots should be ignored).

mLab collection select

Future data¶

Sometimes data gets recorded into your NS site that can be date stamped into the future. For example, if your CGM or pump had the wrong time or date set. These futurity-data will cause problems in rendering (displaying) information correctly, and tin normally cause loop failures as well. Check your NS Admin Tools section (described above) to easily identify and cleanout your database of futurity data points. Every once in awhile withal, that futurity data indicate tool will not piece of work effectively because the future data will actually be stored within the devicestatus drove's information. If that is the example, you should try cleaning out the devicestatus collection, as described above in the Cleanout Data section.

Nightscout info incorrect¶

There are three pills (aka, information boxes) that are noteworthy about your NS display, and that people commonly translate as "incorrect" despite all the warnings/explanations in these docs.

  • IOB pill volition usually display the IOB reported by your OpenAPS pill. If your loop is declining or NS communications are down because the rig has gone offline, there's a skilful possibility that your IOB pill volition be displaying an incorrect IOB based on the careportal'due south method of computing IOB (rather than OpenAPS'due south way). You can determine the source of your IOB pill's information by clicking or hovering on the pill. If the pills says "OpenAPS", then information technology's practiced to utilise that data. Additionally, information technology should report the portion of IOB termed "basal IOB", which is the IOB from of temp basal adjustments and SMBs, if enabled.
  • COB pill should Non be included on your heroku settings "ENABLE" line. If you become confronting this advice, you may experience laggy NS performance and run into wrong COB reported in your COB pill on the NS site. Don't say you haven't been warned. Until NS dev squad can address these bug, the recommendation stands to Not include COB in your NS site settings.
  • BASAL pill should Non be used in your NS site. The data on that pill updates and so slowly sometimes, that y'all may incorrectly bound to assumptions that your rig is behaving differently than it actually is. Instead, apply the OpenAPS pill to find electric current information about your current basal rate...or press the ESC button on your pump in society to straight read the current temp basal. Additionally, the basal rendering (the blue lines of the NS display) can sometimes lag by upward to 2-5 minutes, depending on loop activities...so again utilize the OpenAPS pill or pump if you are interested in the most up-to-date information on temp basals.

​