Even those who follow this documentation precisely are bound to end up stuck at some point. This could be due to something unique to your system, a mistyped command, actions performed out of order, or even a typo in this guide. This section provides some tools to help diagnose the issue as well as some common errors that have been experienced and resolved before. If you get stuck, try re-reading the documentation again and after that, share what you’ve been working on, attempted steps to resolve, and other pertinent details in #intend-to-bolus in Gitter when asking for help troubleshooting.

Generally useful linux commands

More comprehensive command line references can be found here and here. For the below, since these are basic linux things, also try using a basic search engine (i.e. Google) to learn more about them and their intended use.

$ ls -alt (List all of the files in the current directory with additional details.)

$ cd (Change directory)

$ pwd (Show the present working directory (your current location within the filesystem).)

$ sudo <command>

$ tail -f /var/log/syslog

$ df -h

$ ifconfig

$ cat <filename> (Display the contents of the file.)

$ nano <filename> (Open and edit the file in the nano text editor.)

$ stat <filename>

$ pip freeze

$ sudo reboot

$ sudo shutdown -h now (The correct way to shut down the Raspberry Pi from the command line. Wait for the green light to stop blinking before removing the power supply.)

$ dmesg (Displays all the kernel output since boot. It’s pretty difficult to read, but sometimes you see things in there about the wifi getting disconnected and so forth.)


[add something for decocare raw logging]

Dealing with a corrupted git repository

OpenAPS uses git as the logging mechanism, so it commits report changes on each report invoke. Sometimes, due to “unexpected” power-offs (battery dying, unplugging, etc.),the git repository gets broken. When it happens you will receive exceptions when running any report from openaps. As git logging is a safety/security measure, there is no way of disabling these commits.

To fix a corrupted git repository you can run, it will try to fix the repository, and in case when repository is definitly broken it copies the remainings in a safe place (tmp) and initializes a new git repo.

Warning: do not run any openaps commands with sudo in front of it sudo openaps. If you do, your .git permissions will get messed up. Sudo should only be used when a command needs root permissions, and openaps does not need that. Such permission problems can be corrected by running sudo chown -R pi.pi .git in the openaps directory. If you are using an Intel Edison, run sudo chown -R edison.users .git.

Environment variables

If you are getting your BG from Nightscout or you want to upload loop status/resuts to Nightscout, among other things you’ll need to set 2 environment variabled: NIGHTSCOUT_HOST and API_SECRET. If you do not set and export these variables you will receive errors while running openaps report invoke monitor/ns-glucose.json and while executing script which is most probably part of your upload-recent-treatments alias.Make sure your API_SECRET is in hashed format. Please see this page for details. Additionally, your NIGHTSCOUT_HOST should be in a format like (without trailing slash). For the complete visualization guide use this page from the OopenAPS documentation.

Common error messages

Don’t have permission, permission not allowed, etc

The command you are running likely needs to be run with root permissions, try the same command again with sudo in front of it

json: error: input is not JSON

json: error: input is not JSON: Unexpected '<' at line 1, column 1:
        <head><title>Document Moved</title></head>

This error usually comes up when you have pulled a file down from Nightscount that was an invalid file. Typcially you might see this when trying to pull down treatments. Make sure that you have your HOST and API_KEY set correctly at the top of your cron, in your ~/.profile

Could not parse carbratio_date when invoking profile report

Could not parse carbratio_data.
Feature Meal Assist enabled but cannot find required carb_ratios.

This error may occur when you invoke settings/profile.json report.

Check report definition in openaps.ini. If you have line remainder = [] change it to remainder =

Below is correct definition

[report "settings/profile.json"]
use = shell
bg_targets = settings/bg_targets.json
settings = settings/settings.json
basal_profile = settings/basal_profile.json
reporter = text
json_default = True
max_iob = preferences.json
device = get-profile
remainder =
insulin_sensitivities = settings/insulin_sensitivities.json

Wifi and hotspot issues

See wifi troubleshooting page