Updating dev docs Aug 16 2017 (#1006)

* Update understanding-your-Explorer-Board-rig.md (#996)

Trying to get URL with a space to work in the link above. Inserting a %20 in the URL.
lipo to LiPo

* Update loops-in-progress.md (#999)

Adding my name to the "Loops in Progress"

* Update loops-in-progress.md (#1001)

Added my name

* Update loops-in-progress.md (#1003)

Added name to growing list of looping humans.

* Add update decocare to set temp basals > 6.3 (#1004)

* Add update decocare to set temp basals > 6.3

Includes log file error.

* Formatting for linkability

* Updated to clarify settings such as tethering are not impacted by re-runs (#1002)

There may be other settings which aren't impacted, so these can be added to the list!

* Adding some troubleshooting summary notes and links (#1000)

* Adding some troubleshooting summary notes and links

* Add note about reboot

* New phone added to list (#1005)

Updated to include our experience of using a Samsung Galaxy A3 2016

docs/docs/Build Your Rig/OpenAPS-install.md

@@ -141,6 +141,16 @@ If after 20 minutes, you still have some errors showing instead of the above suc
 
 **Done watching the logs? Type control-C to exit the pump-loop log.**
 
+#### **Temp basals > 6.3?**
+
+If your rig tries and fails to set a temp basal > 6.3 you should see "ValueError: byte must be in range(0, 256)" in the log.  To fix this error you need to update decocare.  This is easy.  Type control-C to exit the pump-loop log.  Then copy the following 3 lines to the terminal window.
+
+```
+cd ~/src && git clone git://github.com/openaps/decocare.git
+cd decocare
+python setup.py install
+```
+
 #### Rig Logs and Shortcut commands
 
 Checking your pump-loop.log is a great place to start anytime you are having looping failures.  Your error may not be in the pump-loop, but the majority of the time, you'll get a good head start on the issue by looking at the logs first. So, develop a good habit of checking the pump-loop log to get to know what a normal log looks like so that when a real error appears, you can easily see it as out of place and needing to be addressed.  Additionally, knowing how to access your pump-loop log is important if you come to Gitter or Facebook looking for troubleshooting help...one of the first questions will usually be "what does your pump-loop log look like?"

docs/docs/Customize-Iterate/bluetooth-tethering-edison.md

@@ -38,6 +38,7 @@ A few things to know about using your phone's hotspot feature:
 <TR><TH>iPhone<TD>Yes<TD>Users have experienced various levels of success with the iPhone bluetooth tethering and when the rig switches  between wifi and BT<TD>Not Applicable. Experimental version of Loop to do something similar doesn't yet have feedback.
 <TR><TH>Acer Phone<TD>No<TD>Many data drops on the bluetooth connection for rig. Recommended to avoid.<TD>xDrip compatibility is poor - numerous drops throughout the day.
 <TR><TH>Samsumg Galaxy S7 Edge (G935F) Android 7.0<TD>Yes<TD>Excellent BT tether using apps 'Bt AutoTether' and 'BT Tether'<TD>xDrip+ with G5 > 95% capture.
+<TR><TH>Samsung Galaxy A3 (2016) Android 6<TD>Yes<TD>Excellent BT tether using app 'Blue Car Tethering'<TD>xDrip+ with G4, reliable capture using xDrip+ and using normal tether when running with Dexcom in G4-upload mode
 </TABLE>
 
 ## Configure Bluetooth tethering on Edison running Jubilinux [optional]

docs/docs/Customize-Iterate/oref0-runagain.md

@@ -3,3 +3,9 @@
 In the future, you may want to run the setup script again (such as when you want to come back and turn on new, advanced features). To do so, you will be able to run `bash ~/myopenaps/oref0-runagain.sh` to start running the setup script again with those options you have selected for your current setup. (You may first want to `cd ~/myopenaps && cat oref0-runagain.sh` to see what options you have saved in there.  To run it again with different options, you can copy and paste and modify that output, or you can `cd ~/myopenaps && nano oref0-runagain.sh` to change what's saved in the file to run the next time.  Make sure to change `myopenaps` to your openaps directory name if you chose something non-standard when you ran oref0-setup originally.)
 
 Don't have a runagain or want to start fresh? `cd && ~/src/oref0/bin/oref0-setup.sh`
+
+Note: The following items are not impacted by re-running the setup script:
+
+- Wifi settings
+- Bluetooth tethering (assuming you have not changed the Bluetooth address you entered during the initial setup)
+- Papertrail settings (assuming you are update to the openaps directory name used in your intial setup, typically `myopenaps`)

docs/docs/Troubleshooting/Rig-NS-communications-troubleshooting.md

@@ -1,6 +1,14 @@
 # Troubleshooting Nightscout issues
 
-The rig and Nightscout are good friends. Information is usually two-way so long as the rig has access to the internet (aka, online use).  When rigs go "offline", NS will go stale until internet is again available.
+The major categories of Nightscout troubleshooting include:
+
+**Connectivity**. The rig and Nightscout are good friends. Information is usually two-way so long as the rig has access to the internet (aka, online use).  When rigs go "offline", NS will go stale until internet is again available. If you're having issues with NS and it's a brand new setup, you'll want to double check [per the below](http://openaps.readthedocs.io/en/latest/docs/Troubleshooting/Rig-NS-communications-troubleshooting.html#setting-up-your-ns-hosting-site) that URL, API secret, etc. are correct.
+
+**Future data**. Sometimes entries will get time stamped incorrectly, or the device time zones are off. [See below](http://openaps.readthedocs.io/en/latest/docs/Troubleshooting/Rig-NS-communications-troubleshooting.html#nightscout-admin-tools) for how to resolve.
+
+**Mlab size is too big and you need to clean it**. [See below](http://openaps.readthedocs.io/en/latest/docs/Troubleshooting/Rig-NS-communications-troubleshooting.html#mlab-maintenance) for how to check the size of, and compact if needed, your mlab database, which can influence what displays in Nightscout.
+
+**Note about jubilinux versions**. Some people experienced issues with jubilinux 0.2.0. There is a fix in the oref0 dev branch, so if none of the above steps resolve an "unknown" pill in Nightscout, try oref0 dev. (As of August 6, 2017). After you install dev, make sure to reboot your rig, after which the changes should resolve the problem in Nightscout. 
 
 ## Setting up your NS hosting site
 

docs/docs/While You Wait For Gear/loops-in-progress.md

@@ -197,3 +197,6 @@ List of people who are working on closed loops:
 - Rami Laakso (Nummela, Finland)
 - Steve Lund (PEI, Canada)
 - Paul Andrel (Phoenixville, PA)
+- Allan Evans (Ottawa, Canada)
+- Simon Lewinson (NE Victoria, Australia)
+- Angie Kabat (Fairbanks, AK)

docs/docs/While You Wait For Gear/understanding-your-Explorer-Board-rig.md

@@ -41,9 +41,9 @@ Watch this [video](https://www.facebook.com/groups/TheLoopedGroup/permalink/1854
 
 LiPo batteries are great for a lot of things, but taking damage is not one of them.  Please treat LiPo batteries with care.  Keep them protected from puncture.  The Explorer board has some “pointy” parts on the underside, so providing some protection from the board’s squish is a good idea.  A small piece of protection (such as a business card or non-conductive thin foam sheet) will help protect the battery from the board above it.  
 
-Since there is some warmth with an OpenAPS rig, it is also not recommended to put a rig unprotected in a pocket close to the body.  The LiPo battery can become warped from the heat or bent from being in the pocket and potentially compromised.  A durable case or waist-belt pouch is a good idea (see [here](http://openaps.readthedocs.io/en/latest/docs/Gear Up/edison.html#cases) for both hard and soft case ideas).  
+Since there is some warmth with an OpenAPS rig, it is also not recommended to put a rig unprotected in a pocket close to the body.  The LiPo battery can become warped from the heat or bent from being in the pocket and potentially compromised.  A durable case or waist-belt pouch is a good idea (see [here](http://openaps.readthedocs.io/en/latest/docs/Gear%20Up/edison.html#cases) for both hard and soft case ideas).  
 
-There are several places to get LiPo batteries, with lots of different dimensions and capacities.  A 2000 mAh lipo will get you about 12-14 hours of use, assuming you have the standard setup (which is what you get following these docs) running. 
+There are several places to get LiPo batteries, with lots of different dimensions and capacities.  A 2000 mAh LiPo will get you about 12-14 hours of use, assuming you have the standard setup (which is what you get following these docs) running. 
 
 ### What happens if you have multiple rigs?