Where to go for help¶
There are several ways to communicate with other participants and contributors in the #OpenAPS project. See also the Resources section for additional assistance.
Note: It’s best practice not to share your pump’s serial number, so make sure not to include it in pictures or pasted text output when seeking help on pump communication. Ditto for Nightscout URL and API secret and other private information that could enable someone to access your setup.
Related: You may want to read this blog post for tips on how to best seek help when troubleshooting online - there is a lot of information you can provide proactively when seeking help that will aid in getting your issue resolved more quickly.
Google Group - everyone is recommended and welcome to join!¶
A google group focused on #OpenAPS development work can be found here. You can add yourself directly to the group. It’s worth setting your preferences to receive all email from the group; there’s not a huge volume, and this is one of the ways we share updates about hardware or release announcements if you’re not hanging out on Gitter or Facebook or Twitter.
Gitter is a messaging/chat service similar to IRC. It provides integration with GitHub and several other services. It’s the best place to get real-time support with anything related to OpenAPS. (Here’s why we often recommend asking questions on Gitter.)
- The nightscout/intend-to-bolus channel is where you will find active #OpenAPS discussions ranging from technical issues with openaps tools to control theory to general information. It is a great place to introduce yourself and get some help from those who are a few steps further down the road.
- For Autotune conversations, use the openaps/autotune channel
- For TI stick communication, use the oskarpearson/mmeowlink channel
- For RileyLink conversations, use the ps2/rileylink channel
- For LoopKit conversations, use the LoopKit/Loop channel
Gitter has a search function to find old information, but since it isn’t threaded conversations, you may need to spend some time reading the posts after the search result to find the ultimate resolution to the question. So, if you find a particularly useful bit of information that you couldn’t find in the docs...please make a PR to the docs so that the information is permanently stored for others to find.
Tag someone! You can tag particular people if you are responding to them directly by using the
@ symbol and then typing their username. This will help notify the person that you are “speaking to them”. If someone asks you for information that shouldn’t be shared in the public channel, you can also private message people by hovering over their profile picture and choosing the “chat privately” button. Please do not abuse the tagging or PM features: most questions are best asked untagged in the appropriate channel, so that anyone can respond to them as soon as they read Gitter and see the question. There are people from all over the world online at all hours who can help with most kinds of questions, and the core developers usually read every message in Gitter a few times per day and try to answer any questions that got missed.
A note about posting photos or screenshots in Gitter
Gitter has a mobile app which works great for posting text, but does not allow for posting images directly. If you need to post a photo using the mobile app, you’ll have to host your photo file somewhere like Dropbox and post the link to the file location.
Using the desktop application, you can simply drag and drop the file into the Gitter chat window. The file will upload and then display in the chat thread after a short period of time to upload.
Posting copy-paste code from your rig is also another valuable activity for troubleshooting. To post a single line of information, you can use the single-backtick-quote that is found on the key to the left of the number 1 key on the keyboard. (hint: it is under the ~ on the same key). You can also long-press the single quote key on your iPhone keypad to bring up the single-backtick-quote that will work in Gitter. If you start and stop a portion of your text with those single quotes, it will
look like this.
Posting multiple lines of copy-paste from your rig will also sometimes be needed. You can do that by:
- start a single line of 3 single quotes (the same one we used in the example above)
control-enterto get a new line started
- paste the lines of code that you want to post
control-enteragain to get another new line
- enter 3 single quotes to end the section
The copy-pasted lines should have 3 backticks on the line above and the line below. The example below shows, on the bottom, how the formatted text yielded the black box of text in Gitter. Using this format helps troubleshooters read your information easier than unformatted copy and paste.
There is also a Looped Group in Facebook that is currently a discussion place for users on various DIY closed loop systems (OpenAPS, AndroidAPS, etc.). You will need to request membership for the group and respond to a message from the group administrators prior to joining.
The Looped Group has grown considerably in the last 6 months and has many users on both systems. You can search for previous posts on topics that may interest you. Note: If you are asking for troubleshooting help, screenshots and additional information about where you are in your problem will help get the best response.
Issues on GitHub¶
One of the above channels is the best place for real-time or near-time troubleshooting. However, you may occasionally stumble across a new bug or edge case that we want to work on resolving. If you’re asked to “create an issue”, that usually means going to the oref0 repository on Github and logging an issue there. (You may also be asked to create issues for the openaps toolkit or decocare, etc. but usually it’s oref0 related.)
Other online forums¶
Those in the #OpenAPS community are frequently found in other forums, such as on Twitter (using the #OpenAPS hashtag, as well as #WeAreNotWaiting) and on Facebook in the “CGM In The Cloud” and “Looped”group.
- There is also a Slack channel to discuss communication around other pumps that are being explored and worked on, but aren’t yet DIY loopable.