404 - Page not found
+Copy the URL and report it here.
+ +
+
+
+
+
+## Next steps:
+
+Follow the links below.
+
+- [Setup the main view](setup) to add or view all available information.
+- [Generate reports](reports).
diff --git a/_sources/clinicians/reports.md.txt b/_sources/clinicians/reports.md.txt
new file mode 100644
index 00000000..446d46ec
--- /dev/null
+++ b/_sources/clinicians/reports.md.txt
@@ -0,0 +1,173 @@
+# Nightscout reports
+
+Access reports from the drawer menu,
+
+
+
+
+
+## View profiles
+
+Profiles view gives important information on the patient therapy parameters.
+
+Select profiles then SHOW (no additional setup is necessary).
+
+
+
+Patients profile(s) will display.
+
+
+
+DIA is the duration of the [insulin action](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4454113/).
+
+Carbs absorption rate is [complex](https://diyps.org/2014/05/29/determining-your-carbohydrate-absorption-rate-diyps-lessons-learned/) to calculate for patients and can be undefined (or zero) if the DIY system doesn't update the value (when existing).
+
+Insulin to Carbs ratio (IC) and Insulin Sensitivity Factor (ISF) can be defined by time periods. Only one visible value means whole day.
+
+Basal rates should match the pump settings.
+
+
+
+## Select a report
+
+Select the report type:
+
+
+
+- `Day to day`
+- `Week to week`
+- `Daily Stats`
+- `Distribution`
+- `Hourly stats`
+- `Percentile Chart`
+- `Weekly Distribution`
+
+
+
+## Setup the report
+
+Select the period used to analyze data.
+
+Enable the check box and either select `From:` and `To: `dates to define the interval
+
+
+
+or:
+
+
+
+- `Today`
+- `Last 2 days`
+- `Last 3 days`,
+- `Last week`
+- `Last 2 weeks`
+- `Last Month`
+- `Last 3 months`
+
+ Avoid selecting too long periods of time for daily reports.
+
+
+
+Unless looking for specific `Notes` or `Event type` leave the checkboxes disabled.
+
+
+
+
+
+You can select which week days to use.
+
+
+
+
+
+Confirm `Target BT range` `bottom` and `top` for TIR (or TITR) and graph range lines.
+
+You can sort the report from older to newer or newer first.
+
+
+
+
+
+Click `SHOW` and wait for data to load and rendering to complete. This might take some time if the period is long (this will also depend on the Nightscout host engine).
+
+
+
+
+
+## Day To day
+
+This report will show BG, day by day, including selected treatments.
+
+
+
+
+
+Enable insulin, carbs and basal rate to have consistent insulin distribution information.
+
+
+
+
+
+When changing selections, click again `SHOW` to update the view.
+
+
+
+## Week to Week
+
+This report will give a week by week spaghetti view, with color code for week days selected.
+
+
+
+
+
+## Daily stats
+
+This report will give a daily distribution view.
+
+
+
+
+
+## Distribution
+
+This report will give a complete distribution view.
+
+You also can filter by hours (scroll to the bottom of the page).
+
+
+
+
+
+You can quickly find %TIR, %TUR, %TAR and the rough estimated HbA1c values.
+
+
+
+Range must be modified to see %TITR.
+
+
+
+## Percentile Chart
+
+This report will give a percentile distribution view.
+
+
+
+
+
+
+
+## Hourly stats
+
+This report will give an hourly distribution view with a box plot showing 25% and 75% percentile plus mean and standard deviation, then additional hour by hour statistics in a table.
+
+
+
+
+
+## Weekly Distribution
+
+This report will give a weekly view.
+
+
+
+
\ No newline at end of file
diff --git a/_sources/clinicians/setup.md.txt b/_sources/clinicians/setup.md.txt
new file mode 100644
index 00000000..43ca4861
--- /dev/null
+++ b/_sources/clinicians/setup.md.txt
@@ -0,0 +1,87 @@
+# Setup the main view
+
+Before checking reports, you should verify your patient has setup correctly data upload.
+The steps below might not be necessary but will probably give you more insights on the patient system.
+
+If you're only looking for reports, skip this step and continue to [reports](/clinicians/reports).
+
+
+
+## Customize your view
+
+Open the main menu, located at the top right of the window, select the drawer icon:
+
+
+
+Select the units for blood glucose values.
+
+
+
+Select the language used for Nightscout display.
+
+
+
+If the patient uses a pump that can send its basal rates, or has setup programmed basal rates, enable basal default display.
+
+
+
+Enable all available plugins and save.
+This will only modify the way you visualize Nightscout on the device you're using. It will not interfere with the patient settings.
+
+
+
+
+
+## Identify displayed items
+
+A typical DIY closed loop user display will look like this.
+
+
+
+Last 48 hours are visible, you can select the upper graph time scale clicking on the corresponding length (2 to 24 hours). You can slide the lower graph selection to visualize the corresponding time period on the top graph.
+
+The rounded rectangle indicators are called "pills" and contain immediately visible indications, or more insights if you hover on them with the mouse.
+
+They can be automatically or manually updated by the patient or its closed loop/uploader device, else they will be empty or meaningless. As setting warning and urgent limit values for these pills is not always adjusted by the user in Nightscout variables, they might appear in yellow or red for values that are within normal usage.
+
+
+
+Current blood glucose is displayed top left, the arrow only indicates the difference between the current measurement and the previous one (you'll see the measurement age on the left of the view).
+
+
+
+- IOB: Insulin on board, is calculated using the insulin duration parameter in the current profile if no external closed loop system is used, or by this external algorithm if any (OpenAPS/Loop).
+
+- COB: Carbs on board are calculated by the absorption rate set in the profile.
+- CAGE, SAGE, BAGE, IAGE are timers counting the time since last Cannula (infusion site), Sensor, Battery and Insulin cartridge change.
+- BASAL displays the current basal rate.
+
+Uploading device battery level and Nightscout storage used space are not of clinical interest.
+
+
+
+Connected pumps will show available insulin units, battery status and last registered activity.
+
+
+
+DIY closed loop systems can be identified with the [Loop](https://loopkit.github.io/loopdocs/faqs/algorithm-faqs/) (Loop) or [OpenAPS](https://openaps.readthedocs.io/en/latest/docs/While%20You%20Wait%20For%20Gear/Understand-determine-basal.html#understanding-the-determine-basal-logic) (OpenAPS, AndoidAPS, Trio, FreeAPS X, iAPS) pill. Only one will be enabled, if the other one appears it will normally show an exclamation mark. If a DIY closed loop system Nightscout doesn't show any active pill, configuration needs to be fixed so that Nightscout receives all necessary data (patient responsibility).
+
+
+
+Basal display shows the programmed basal in dotted lines and the actual basal modulation. This is an example for the default basal display.
+
+
+
+Loop adds rich details to Nightscout real time display, like food types and visual information.
+
+Hovering on the DIY closed loop system pill (Loop/OpenAPS) will show insights of the algorithm decisions.
+
+
+
+
+
+## Next step:
+
+Follow the link below.
+
+- [Generate reports](reports).
diff --git a/_sources/index.md.txt b/_sources/index.md.txt
new file mode 100644
index 00000000..b1c8382b
--- /dev/null
+++ b/_sources/index.md.txt
@@ -0,0 +1,313 @@
+# Welcome to Nightscout
+
+
+
+
+
+
+
+Health professional? You might not want to build a Nightscout site and just need to find out how to get data from it, [jump to the dedicated pages here](/clinicians/home/).
+
+
+
+## Introduction
+
+Nightscout (also known as CGM in the Cloud) is an open-source cloud application used by people with diabetes and parents of kids with diabetes to visualize, store and share the data from their Continuous Glucose Monitoring sensors in real-time. Once setup, Nightscout acts as a central repository of blood glucose and insulin dosing/treatment data for a single person, allowing you to view the CGM graph and treatment data anywhere using just a web browser connected to the internet.
+
+There are several parts to this system. You need somewhere online to store, process and visualize this data (a Nightscout Site), something to upload CGM data to your Nightscout (an Uploader), and then optionally you can use other devices to access or view this data (one - or more - Follower).
+
+### Nightscout Site
+
+- The Nightscout cloud application can be installed by yourself (Do It Yourself, in short: DIY) using hosting services from various cloud service providers.
+- You can also pay to use a fully-managed Nightscout hosting service and avoid having to personally build and maintain your site.
+
+### Uploader
+
+The CGM data is usually sent to Nightscout by an uploader device such as a mobile cellphone running an app like xDrip+, Spike, xDrip4iOS, Medtronic Uploader and others. Alternatively, the CGM data can be pulled directly from your online Dexcom account. The application you'll need for uploading the data depends on which CGM device you're using and what type of mobile device you have.
+
+### Followers
+
+In addition to viewing the data using a web browser, there are also applications available for mobile devices, smartwatches, electronic devices and other cloud-based services which allow you alternative ways to view and interact with the information stored within your Nightscout site (often known as "Followers").
+
+
+
+## Development History
+
+Nightscout was developed by people with Type 1 Diabetes and parents of kids with T1D and has continued to be developed, maintained, and supported by volunteers, clinical use, and commercial sponsorship. The web portal known as Nightscout is made by the [CGM Remote Monitor Contributors](https://github.com/nightscout/cgm-remote-monitor/graphs/contributors) and the Nightscout community over years.
+
+When first implemented, Nightscout was a solution specifically for remote monitoring of [Dexcom G4 CGM data](https://github.com/hackingtype1/original-android-cgm). Today, there are Nightscout solutions available for nearly all commercial CGM sensors. The goal of the project is to allow the remote monitoring, sharing and analysis of any T1D's glucose levels using existing monitoring devices.
+
+## What are the values of Nightscout
+
+We are compelled in the pursuit of **humane** and **equitable** application of technology to **liberating people from the burden of diabetes**. We are not waiting to deliver the benefits we've found in **sharing _all_ diabetes experiences**. Nightscout is free to contribute, free to access, free to criticize, free to try, free to depend on, free to modify, and free to distribute. The Nightscout community demands **respect** and **dignity** for all community members. The reputation of the Nightscout community is affected by the **quality** of the source code, the quality of our relationships, the quality of our discussions, what we are known for doing: the way we treat each other.
+Users of Nightscout are impacted by **reliability**, **security** and **confidentiality** of Nightscout. Therefore, the developers and contributors of Nightscout strive to improve the quality of Nightscout while making these opportunities **accessible** to all.
+
+Nightscout's **longevity**, the application, the ecosystem, and the culture demand we use all tools at our disposable to achieve the values in a **sustainable** way. We are not waiting to do whatever it takes to meet the needs of people affected by the inhumane demands of diabetes. Our active **collaboration** against the burden of diabetes creates the results we desire.
+
+## What Do I Need?
+
+You will need:
+
+- A CGM sensor
+
+- A way to [upload](uploader/uploaders) your data, to be stored in Nightscout (this is generally an internet-connected mobile phone with a matching uploader app)
+
+- Internet access
+
+- **For Nightscout DIY:** Basic computer skills and the ability to **_carefully_** follow the installation guides shown on this site
+
+ **\*"Carefully"** means that you will thoroughly read, follow and complete each step without skipping any and without giving up thinking that it is too difficult - it isn't, you just need to be patient.\*
+
+```{admonition} IMPORTANT
+:class: danger
+
+Before using Nightscout, it is important to understand that this project:
+
+- is an open-source, community-based project and is not supported by any company
+- is not officially approved or regulated for diabetes therapy and/or treatment in any way
+
+**If you will be using DIY: You must understand that you take full responsibility for building and running this system and you agree to do so at your own risk.**
+```
+
+```{admonition} SAFETY
+:class: danger
+
+- This project requires a working internet connection and availability of third-party cloud services
+- Do not rely only on Nightscout as the only way you have of knowing your blood glucose values and trends
+- Make sure you're ready to cope with an unexpected failure and always have alternative ways to check your blood glucose levels
+```
+
+## How Much Does It Cost?
+
+There's no simple answer to this. You basically have two options:
+
+1. **[DIY](#build-your-own-nightscout-site)**: Use instructions on this website to create your own installation. You will need to maintain this installation yourself. There are cloud providers that offer the needed hosting services for free, so your monthly hosting cost can be free - $0 with this option. Of note, with this option you are the person responsible for ensuring the service is up when you need it. The community aims to support people who choose this option, but this is entirely driven by a voluteer effort and support might not be available when you need it.
+2. **[Use a service](#nightscout-as-a-service)**: You can use a hosting provider that does all of this work for you in exchange for a monthly fee. There are many options available for this. If you're a non-technical person, this is a **great choice**.
+
+## Build your own Nightscout site
+
+```{tip}
+
+
+
+
+When it comes to `treatments` and `entries`, deleting data is something you need to carefully evaluate if you like Nightscout to be the main repository for your history.
+
+### Mongo `treatments` Database
+
+
+
+
+
+
+
+### Mongo `entries` Database
+
+
+
+
+
+
+
+### Remove future items from Database
+
+
+
+Future treatments and entries generated by an incorrect time zone, daylight saving time change, or any other mistake can completely block your site. Using this feature will purge the database of these unwanted values automatically. Detected issues will appear in `Database contains `*`x`*` future records` and should be fixed.
+
+
+
+
+
+
+
diff --git a/_sources/nightscout/advanced.md.txt b/_sources/nightscout/advanced.md.txt
new file mode 100644
index 00000000..1aadf9a1
--- /dev/null
+++ b/_sources/nightscout/advanced.md.txt
@@ -0,0 +1,63 @@
+# Advanced Nightscout deployments
+
+
+
+```{admonition} Too complicated? Not what you're looking for?
+:class: seealso
+Consider a hosted Nightscout service! Check for easier solutions [here](/index.md#nightscout-as-a-service).
+```
+
+
+
+## Building Nightscout DIY in a cloud platform
+
+You can run your Nightscout site in several vendors platforms, using free or paid accounts.
+
+We documented Heroku, Azure, Railway, Northflank and Fly.io. There are probably others, don't hesitate to [open an issue in the documentation](https://github.com/nightscout/nightscout.github.io/issues) with the easiest deployment method if you want to see them named here.
+
+
+
+## Building Nightscout DIY in a virtual server
+
+You can run your Nightscout site in physical or virtual private servers, using free or paid accounts.
+The [original](https://github.com/jasoncalabrese/project-glu/blob/master/README.md) Nightscout project was also developed to run in Digital Ocean.
+
+You can use step by step Linux commands or deploy with a **simple** scripted install.
+
+Below is a list of some VPS. There are probably others, don't hesitate to [open an issue in the documentation](https://github.com/nightscout/nightscout.github.io/issues) with the easiest deployment method if you want to see them named here.
+
+[Google Cloud](https://navid200.github.io/xDrip/docs/Nightscout/GoogleCloud.html) with a Scripted deployment (one command).
+[Oracle](https://www.dropbox.com/s/5twlqrndofqno0t/0-amber-oracle.pdf) and extensive documentation (npm and Docker).
+[Amazon Web Service](https://github.com/rajdeut/terraform-aws-nightscout#readme)
+
+Some common deployment methods:
+
+[Ubuntu](/vendors/VPS/ubuntu) commands.
+[Docker](/vendors/VPS/docker) container.
+
+
+
+(nas)=
+
+## Building Nightscout inside your NAS
+
+Don't buy a NAS device just for this, but if you already have one that's worth a try!
+
+You can host your Nightscout site in your [Synology](/vendors/NAS/synology) NAS.
+You can also try with your [QNAP](https://docs.google.com/document/d/1zpF6Y3kPQqc9KOsClIQt686HDLhGfFxwz4vGfq8E254/edit) NAS.
+
+
+
+## Building Nightscout with a Raspberry PI 4
+
+If you own one, you can use it to host your Nightscout, see [here](https://gist.github.com/Andries-Smit/daac75cd4c06af78cde68c5dec941705).
+
+
+
+## Home Assistant Add-On for Nightscout
+
+This add-on is a wrapper around nightscout/cgm-remote-monitor. It includes a Mongo Database which is used to store the uploaded values.
+
+See [here](https://github.com/marciogranzotto/addon-nightscout).
+
+
diff --git a/_sources/nightscout/close_loop.md.txt b/_sources/nightscout/close_loop.md.txt
new file mode 100644
index 00000000..771a9241
--- /dev/null
+++ b/_sources/nightscout/close_loop.md.txt
@@ -0,0 +1,60 @@
+# Closed loop systems
+
+
+
+Nightscout is integrated with DIY closed loop systems.
+
+Look into the specific app documentation to know more about optimal Nightscout settings.
+
+The heading for each section is a link to the Nightscout overview page for that closed-loop system.
+
+You will also find general support in **Loop and Learn**.
+
+* [The *Loop and Learn* Website](https://www.loopandlearn.org/)
+* [The *Loop and Learn* *Facebook* group](https://www.facebook.com/groups/LOOPandLEARN)
+
+
+
+## [Loop](https://loopkit.github.io/loopdocs)
+
+[Loop](https://loopdocs.org) is an open source iOS app that assists in the many insulin dosing decisions people with diabetes face every day. You enter your own settings for desired correction range, basal schedule, insulin sensitivity factor (ISF), carbohydrate ratio (CR) and the type of insulin you are using. The glucose predictions, using your settings and meal entries, provide Loop with the information needed to modify insulin delivery to attain a targeted glucose range in the future.
+
+**See [here](https://loopkit.github.io/loopdocs/loop-3/services/#nightscout-login) how to configure Loop to upload to Nightscout.**
+
+Facebook group: [Looped](https://www.facebook.com/groups/TheLoopedGroup)
+
+
+
+## [AAPS](https://androidaps.readthedocs.io/en/latest/index.html)
+
+AndroidAPS is an open source app for people living with insulin-dependent diabetes that acts as an artificial pancreas system (APS) on Google Android smartphones. AAPS uses an openAPS software algorithm.
+
+**See [here](https://androidaps.readthedocs.io/en/latest/Configuration/Preferences.html#nsclient) how to configure AAPS NSClient to upload to Nightscout.**
+
+Facebook group: [Android APS Users](https://www.facebook.com/groups/AndroidAPSUsers)
+
+
+
+## [Trio](https://diy-trio.org)
+
+Trio is an open source iOS app that automates insulin delivery using OpenAPS' algorithm.
+
+[Documentation](https://docs.diy-trio.org/en/latest/)
+[Facebook group](https://www.facebook.com/groups/1351938092206709)
+[Discord](http://discord.diy-trio.org)
+
+
+
+## [iAPS](https://iaps.readthedocs.io/en/main/)
+
+iAPS is a open source artificial pancreas system based on the OpenAPS algorithm.
+
+Facebook group: [iAPS](https://www.facebook.com/groups/1351938092206709)
+
+
+
+## [OpenAPS](https://openaps.org/)
+
+*Mind the documentation is not up to date for Nightscout DIY options.*
+
+The Open Source Artificial Pancreas System (OpenAPS) is a safe but powerful, advanced but easily understandable, Artificial Pancreas System (APS) designed to automatically adjust an insulin pump’s insulin delivery to keep blood glucose (BG) in a safe range at all times. It does this by communicating with an insulin pump to obtain details of all recent insulin dosing (basal and boluses), by communicating with a Continuous Glucose Monitor (CGM) to obtain current and recent BG estimates, and by issuing commands to the insulin pump to adjust insulin dosing as needed.
diff --git a/_sources/nightscout/database.md.txt b/_sources/nightscout/database.md.txt
new file mode 100644
index 00000000..0eedb049
--- /dev/null
+++ b/_sources/nightscout/database.md.txt
@@ -0,0 +1,113 @@
+# Choose your database
+
+```{admonition} Too complicated? Not what you're looking for?
+:class: seealso
+Consider a hosted Nightscout service! Check for easier solutions [here](/index.md#nightscout-as-a-service).
+```
+
+
+
+You must create a database unless it's already included in the platform you selected, check below.
+
+````{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Heroku/Railway/Azure/Northflank/Fly.io
+You need to create a database.
+:::
+
+:::{tab-item} Google Cloud script
+You don't need to create a database: continue [**here**](https://navid200.github.io/xDrip/docs/Nightscout/GoogleCloud.html)
+:::
+
+:::{tab-item} Hosted
+You don't need to create a database: go directly to the [hosting site](/index.md#nightscout-as-a-service).
+:::
+
+````
+
+
+
+Find a list of commonly used database hosting services below, decide which one you'll want to use and create your database.
+
+
+
+```{warning}
+Using a free, limited size database (like M0 Atlas) means you will have to maintain it.
+Since it will regularly grow with the data you send to Nightscout, take a note to perform **regular cleanup** to avoid your site crashing.
+```
+
+```{card}
+## MongoDB Atlas Database
+
+^^^
+MongoDB bought [mLab](https://twitter.com/chrisckchang/status/506959446753284096) in 2018 and shutdown its service in 2020. Most users migrated to MongoDB Atlas, using a free M0 database with a limited 512MB capacity.
+
+**Pros**:
+* The M0 cluster is free
+* Nightscout was adapted to MongoDB Atlas
+
+**Cons**:
+* M0 clusters are designed for learning and testing, not production: performance and availability are not guaranteed
+* There is no warranty the M0 cluster will remain in the future
+* A larger M2 cluster costs 9$ per month (not competitive against hosted solutions)
+* A full M0 database crashes Nightscout, this is a common issue for DIY closed loop system users
++++
+Follow [these instructions](/vendors/mongodb/atlas.md) to build a small database to host your Nightscout data if you don't already have one.
+```
+
+```{card}
+## Railway Mongo Database
+ 
+^^^
+Railway offers a Mongo database.
+
+**Pros**:
+* Simple to create
+* Less overhead than Atlas (more space)
+
+**Cons**:
+* Requires a 5$/month hobby plan as billing starting amount
+* Running a database together with a Railway Nightscout site will increase billing above ~200MiB used
+* Simple Mongo 4.4 database
++++
+Follow [these instructions](/vendors/railway/database.md) to create a database in Railway.
+```
+
+```{card}
+## Northflank Mongo Database
+ 
+^^^
+Northflank offers a Mongo database.
+
+**Pros**:
+* Simple to create
+* Economic reliable database
+* High quality Mongo database with a replica set
+
+**Cons**:
+* Billing will occur but the cost is really limited: 0.3$ per GiB (it usually takes years to reach 1GB for Nightscout)
+* There is no warranty this offer will be maintained in the future
++++
+Follow [these instructions](/vendors/northflank/database.md) to create a database in Northflank.
+```
+
+```{card}
+## VPS Mongo Database
+
+^^^
+You can create a Mongo Database in a Virtual Private Server, either using a free plan (Oracle, Google) or a paid account (Digital Ocean and so many others ...).
+
+**Pros**:
+* Lot of space
+* Standard community method largely supported by IT specialists
+
+**Cons**:
+* Requires commands to be typed and some IT knowledge
++++
+Waiting for something easier (work in progress) [these are the instruction](https://www.mongodb.com/docs/manual/administration/install-on-linux).
+```
+
diff --git a/_sources/nightscout/discover.md.txt b/_sources/nightscout/discover.md.txt
new file mode 100644
index 00000000..05e20778
--- /dev/null
+++ b/_sources/nightscout/discover.md.txt
@@ -0,0 +1,308 @@
+# Discover your Nightscout site
+
+
+
+```{admonition} Privacy
+:class: tip
+Having the URL of your Nightscout site, anybody can view your BG and run reports of your data. It it strongly recommended that you [secure](/nightscout/security) your site.
+```
+
+
+
+It should look very similar to this when your [uploader](/uploader/setup.md) has added some data.
+
+
+
+
+
+The central part will show your recent BG, you can select how many hours you want to be displayed with `Hours: 2 3 4 6 12 24`. The pale blue dots are the AR2 prevision as explained [here](/nightscout/setup_variables.md#ar2-ar2-forecasting). The lower part will display the last 48 hours and you can use the lower right selection to browse your old data.
+
+
+
+
+
+In the upper part you'll see the current time of your site, your current BG (and how long ago it was measured) plus the delta with the previous measurement and a trend arrow. More explanations [here](/nightscout/setup_variables.md#default-plugins).
+
+Optionally you will see other indications (pills) that can be personalized in your variables and plugins like detailed [here](/nightscout/setup_variables.md#plugins).
+
+
+
+
+
+## Authenticate yourself
+
+By default you site opens read only, you need to authenticate using your [API secret](api-secret) in order to modify settings and add treatments. Click on the lock icon, enter your API secret and click `Update`.
+
+
+
+This will unlock your `careportal` ([if enabled](/nightscout/setup_variables.md#careportal-careportal)) and `edit` ([if enabled](/nightscout/setup_variables.md#edit_mode-on)).
+
+
+
+
+
+## Add a treatment (`careportal`)
+
+Some uploaders will send treatments to Nightscout but others won't. If you whish to do this manually, `careportal` is here for that.
+
+`+` will open an interface to manually enter treatments.
+
+
+
+
+
+In the `Event Type` drop down menu, you can select the treatment type you want to add. Additional available entries will depend on the [plugins you enabled](/nightscout/setup_variables.md#advanced-plugins) like Loop and OpenAPS/AAPS.
+
+### BG Check
+
+`BG check` allows you to enter a blood glucose reading value from your `Meter`. With a CGM using `Sensor` reading doesn't add much value.
+
+Keep in mind the value will be inserted now (unless you modify the event time) and might not match your CGM value for non stable BG due to capillary time lag.
+
+
+
+
+
+### Correction Bolus
+
+`Correction Bolus` allows you to enter the amount of insulin units injected for a correction.
+
+It will show as a circle with the lower half blue, with its size depending on the amount of units, UI indicated below (depending on [bolus rendering](/nightscout/setup_variables.md#bolus_render) setting).
+
+
+
+
+
+### Meal Bolus
+
+### Carb Correction
+
+### Snack Bolus
+
+These treatments allow you to enter the amount of food you eat (and eventually the matching insulin treatment).
+
+It will show as a circle with the higher half white (if including carbs), with its size depending on the amount of food. Without carbs the upper half will not be filled with the white color. If you add proteins and fat, the amount will display in this order: `carbs/proteins/fat`. With insulin the lower half of the circle will fill in blue and units will be indicated below.
+
+You can select the timing of carbs absorption in `Carb Time` (i.e. when did you or will you actually eat these carbs)
+
+
+
+
+
+### Combo Bolus
+
+Combo bolus allows you to insert the corresponding bolus if you use a pump. Insert the total amount of insulin in `Insulin Given` then break down in `Split` with the percentage administered `now` and the `extended` amount. Enter the`Duration` of the extended bolus below.
+
+It will display as a classic bolus at treatment time and [basal](/nightscout/setup_variables.md#basal-basal-profile) will reflect the extended amount for the selected duration.
+
+
+
+
+
+### Announcement
+
+Announcements are used to change your page title in order to alert viewers.
+
+Entering another treatment will acknowledge the announcement and return your page title to [default](/nightscout/setup_variables.md#custom_title-nightscout).
+
+
+
+
+
+### Note
+
+### Question
+
+Notes and questions are a way to add comments and interact with others using your Nightscout page.
+
+
+
+
+
+### Exercise
+
+You can log physical activities and specify the duration.
+
+
+
+
+
+### Pump Site Change `cage`
+
+### CGM Sensor Start `sage`
+
+### CGM Sensor Insert
+
+### CGM Sensor Stop
+
+### Pump Battery Change `bage`
+
+### Insulin Cartridge Change `iage`
+
+Logging these events will help you remember various expirations dates and will update the [corresponding pills](/nightscout/setup_variables.md#age-pills) if enabled.
+
+
+
+
+
+### Temp Basal Start
+
+### Temp Basal Stop
+
+You can indicate temporary basal rate changes using either a percentage change in `Percent` or the absolute rate in `Basal value`. You need [basal](/nightscout/setup_variables.md#basal-basal-profile) to be enabled to visualize it.
+
+
+
+
+
+### Profile Switch
+
+If you have more than one profile stored, you can switch profile to keep your profile parameters synchronized.
+
+For a temporary switch (like for physical activities) you can select the duration.
+
+
+
+
+
+### D.A.D. Alert
+
+Log a Diabetic Alert Dog event.
+
+
+
+
+
+## Edit Mode (`edit`)
+
+For values still present on your display (last 48 hours), you can use Edit to move or delete bolus and correction treatments.
+
+
will change color to red in edit mode 
.
+
+1. Drag the treatment in the past or future in the black area to move both food and insulin.
+2. If you want to move only insulin drop in the blue area.
+3. For carbs only, in the white area.
+4. To delete a complete treatment drop it in the red delete area.
+
+Once done, exit the edit mode by de-selecting it (white on black background). 
+
+
+
+## Drawer Menu
+
+Once authenticated (click the lock icon up right) you'll find many features in the drawer menu like access to advanced plugins and customizations of your web page (local view only, in order to modify the default view look into your Heroku variables [here](/nightscout/setup_variables/)).
+
+
+
+`Reports` will drive you to a powerful reporting toolset detailed [here](/nightscout/reports/).
+
+`Profile Editor` will allow you to modify and add profiles, see [here](/nightscout/profile_editor/).
+
+`Food Editor` handles your customized [food database](/nightscout/setup_variables.md#food-custom-foods).
+
+`Admin Tools` gives you access control and database tools, see [here](/nightscout/admin_tools).
+
+
+
+### Simple views:
+
+
+
+
+
+- `Clock` - Shows current BG, trend arrow, and time of day. Grey text on a black background.
+
+
+
+- `Color` - Shows current BG and trend arrow. White text on a color background.
+
+
+
+- `Simple` - Shows current BG. Grey text on a black background.
+
+- `[+]` - Create custom, simplified views using a predefined set of elements.
+
+
+
+
+
+List of available items:
+
+- `SGV` - Sensor Glucose Value
+- `SGV age` - time since the last SGV read
+- `SGV delta` - change of SGV in the last 5 minutes
+- `Trend arrow` - icon of the SG trend
+- `Time` - current time
+- `Line break` - invisible item that will move following items to the next line (by default all are showing on the same level)
+
+All visible items have `Size` property which allows to customize the view even more. Also, all items may appear multiple times on the view.
+
+Apart from adding items, it is possible to customize other aspects of the views, like selecting `Color` or `Black` background. The first one will indicate current BG threshold (green = in range; blue = below range; yellow = above range; red = urgent below/above). `Show SGV age` option will make `SGV age` item appear `Always` or only if the predefined threshold is reached: `Only after threshold`. Breaching `SGV age threshold` will also make `Color` background turn grey and strike through `SGV`. `Clock view configurator` will generate an URL (available under `Open my clock view!` link) that could be bookmarked.
+
+If you launch one of these views in a fullscreen view in iOS, you can use a left-to-right swipe gesture to exit the view.
+
+
+
+### Settings:
+
+
+
+
+
+You can customize your view using Settings. Changes will only be applied to your current browser view, if you want to make these settings default for any browser you need to change directly the corresponding [system variables](/nightscout/setup_variables) indicated below and add the corresponding plugins in [`SHOW_PLUGINS`](/nightscout/setup_variables.md#plugins).
+
+You need to [authenticate](#authenticate-yourself) to save your settings.
+
+#### [**Units `DISPLAY_UNITS`**](display-units)
+
+#### [**Date Format `TIME_FORMAT`**](/nightscout/setup_variables.md#time_format-12)
+
+#### [**Language `LANGUAGE`**](/nightscout/setup_variables.md#language-en)
+
+#### [**Scale `SCALE_Y`**](/nightscout/setup_variables.md#scale_y-log)
+
+#### [**Render Basal `BASAL_RENDER`**](/nightscout/setup_variables.md#basal-basal-profile)
+
+#### [**Render Bolus Amount `BOLUS_RENDER`**](/nightscout/setup_variables.md#bolus_render)
+
+#### [**Alarms `ALARM`**](/nightscout/setup_variables.md#alarms)
+
+
+
+
+
+
+
+#### [**Edit Mode `EDIT`**](/nightscout/discover.md#edit-mode-edit)
+
+#### [**Show Raw BG Data `rawbg`**](/nightscout/setup_variables.md#rawbg-raw-bg)
+
+#### [**Custom Title `CUSTOM_TITLE`**](/nightscout/setup_variables.md#custom_title-nightscout)
+
+#### [**Theme `THEME`**](/nightscout/setup_variables.md#theme-colors)
+
+#### [**Show Plugins `SHOW_PLUGINS`**](/nightscout/setup_variables.md#plugins)
+
+
+
+
+
+
+
+In order to `Save` your changes you need to Authenticate, click `Authenticate` and enter your [API Secret](api-secret).
+
+`Reset, and use defaults` will reverse your changes to defaults from your [config variables](/nightscout/setup_variables.md#nightscout-config-vars).
+
+In `About` you'll see your current Nightscout version.
+
+
+
+### API
+
+You can find information about your site API at:
+
+https://{url}/api-docs[?token=TOKEN]
+
+https://{url}/api/v2/properties.json[?token=TOKEN]
diff --git a/_sources/nightscout/dns.md.txt b/_sources/nightscout/dns.md.txt
new file mode 100644
index 00000000..5c041a34
--- /dev/null
+++ b/_sources/nightscout/dns.md.txt
@@ -0,0 +1,129 @@
+---
+orphan: true
+---
+
+```{warning}
+Nightscout developers advice: not a good idea.
+```
+
+# Use a Dynamic DNS
+
+
+
+Either because running a VPS, Northflank or simply because you'd like an alternate name to your Nightscout page, you can use either you own DNS name or free services like those below.
+
+```{warning}
+Adding a free DNS service to your Nightscout setup increases the possibility of unexpected outage.
+Paid DNS services are available at 1$ per month.
+```
+
+
+
+## No-IP
+
+No-IP provides one free dynamic DNS hostname.
+
+```{warning}
+Using No-IP for free requires you to **confirm your hostname every month**.
+```
+
+
+
+1. Sign up to [No-IP](https://www.noip.com/sign-up). Do not create a `Hostname` yet.
+
+
+
+2. From the dashboard, in `Dynamic DNS`, `No-IP hostnames` click `Create Hostname`.
+ 
+
+
+
+3. Invent your `Hostname` and select a `Domain` in the `Free Domain` list. This will be the URL you will be able to browse from any computer to your Nightscout site.
+ 
+
+
+
+4. If you're using a VPS or you know the IP address of your current Nightscout, select `DNS Host (A)` and enter it in `IPv4 Address`.
+ 
+
+
+
+5. Else, if you only know your current Nightscout site name, select `DNS Alias (CNAME)` and enter it in `Target`.
+ 
+
+
+
+6. Click `Create Hostname` bottom right.
+
+
+
+You now can use this URL when accessing your Nightscout site, in any browser and also for your uploaders and followers.
+
+
+
+## Dynu
+
+1. Sign up to [Dynu](https://www.dynu.com/en-US/ControlPanel/CreateAccount).
+
+
+
+2. From the `Control Panel`, select `DDNS Services`.
+ 
+
+
+
+3. Invent your `Host` name and select a `Top Level` domain in the list. This will be the URL you will be able to browse from any computer to your Nightscout site.
+ 
+
+
+
+4. Click `Add`.
+
+
+
+5. Replace the proposed IP address in `IPv4 Address` by your own Nightscout IP, (you can disable IPv6 features) and click `Save`.
+ 
+
+
+
+You now can use this URL when accessing your Nightscout site, in any browser and also for your uploaders and followers.
+
+
+
+## FreeDNS
+
+FreeDNS proposes thousands of free DNS names, with the issue that many are flagged as dangerous when you'll want to browse them from your cellular or within public/private networks. You'll find one that fits your needs but you might need several attempts.
+
+```{warning}
+Using FreeDNS for free requires you to **login to confirm your account every six months**.
+```
+
+
+
+1. Sign up to [FreeDNS](https://freedns.afraid.org/signup/?plan=starter). Enter all required information and click `Send activation email`.
+ 
+
+
+
+2. Check your inbox (search Spam if you don't receive the email) and click on the activation link.
+ 
+
+
+
+3. Select `Subdomains` in the menu, then `Add a subdomain`.
+ 
+
+
+
+4. Invent your host name in `Subdomain`, select a domain name in the list (there are more than you can see) and put your Nightscout IP in the `Destination` field. Write the text in the image and click `Save`.
+ 
+
+ Note: you might want to select a less popular name than those proposed by selecting Registry in the left menu (example below for us.to).
+ 
+
+
+
+5. You now can use this URL when accessing your Nightscout site, in any browser and also for your uploaders and followers.
+ 
+
+
\ No newline at end of file
diff --git a/_sources/nightscout/docker.md.txt b/_sources/nightscout/docker.md.txt
new file mode 100644
index 00000000..c3df58c0
--- /dev/null
+++ b/_sources/nightscout/docker.md.txt
@@ -0,0 +1,48 @@
+---
+orphan: true
+---
+
+
+
+
+Build your own Docker hub image
+
+1. Clone the cgm-remote-monitor project locally
+
+2. Open a shell in the project root directory (cd cgm-remote-monitor)
+
+3. Login
+ docker login --username username --password xxxxx
+
+4. Create the image
+
+ docker build . -t cgm-remote-monitor
+
+5. Get the image ID
+
+ docker image ls
+
+ REPOSITORY TAG IMAGE ID CREATED SIZE
+ cgm-remote-monitor latest 81a5bfa0c365 50 seconds ago 263MB
+
+6. Create an empty cgm-remote-monitor repository in Docker hub
+
+7. Match your own Docker hub username with your Docker username
+
+ docker image tag 81a5bfa0c365 username/cgm-remote-monitor
+
+8. Push the image to Docker hub
+
+ docker push username/cgm-remote-monitor
+
+9. Your image is available as username/cgm-remote-monitor
+
+
+
+
+
+cleanup:
+
+```
+docker image prune -a
+```
diff --git a/_sources/nightscout/downloaders.md.txt b/_sources/nightscout/downloaders.md.txt
new file mode 100644
index 00000000..c1d083c8
--- /dev/null
+++ b/_sources/nightscout/downloaders.md.txt
@@ -0,0 +1,276 @@
+# Setup Downloaders - Followers
+
+
+
+```{admonition} Smartwatches
+:class: tip
+
+See the dedicated page [**here**](/nightscout/wearable.md).
+
+```
+
+
+
+Note: 
indicates applications compliant to [Nightscout access tokens](/nightscout/security.md).
+
+
+
+## Android
+
+### [xDrip+](https://github.com/NightscoutFoundation/xDrip/releases)
+
+
+
+Select the Nightscout Follower data source and type your Nightscout URL:
+
+*Example:* `https://name.domain.tld`
+
+For a secured site add the token and @ before:
+
+ *Example:* `https://token@name.domain.tld`
+
+
+
+Facebook group [xDrip](https://www.facebook.com/groups/xDripG5/)
+
+
+
+### [AAPSClient](https://github.com/nightscout/AndroidAPS/releases)
+
+
+
+
+
+
[GlucoDataAuto](https://github.com/pachi81/GlucoDataAuto/blob/main/README.md) for Android Auto.
+
+
+
+### [Nightwatch](https://play.google.com/store/apps/details?id=se.cornixit.nightwatch) (Google Play Store)
+
+
+
+
+
+### [Nightwatch](https://github.com/StephenBlackWasAlreadyTaken/NightWatch/releases) (legacy)
+
+
+
+
+
+### [Diabox](https://www.bubblan.org/diabox/)
+
+
+
+In Settings, set Data Collection to Follower, select Nightscout and type your Nightscout URL.
+
+
+
+
+
+## iOS
+
+### [Nightscout X](https://apps.apple.com/us/app/nightscout-x/id1333154219)
+
+
+
+
+
+### [Nightguard](https://apps.apple.com/us/app/nightguard/id1116430352)
+
+
+
+
+
+### [Nightscouter](https://testflight.apple.com/join/UczafrJp)
+
+
+
+Look [here](https://github.com/SpikeApp/Spike/wiki/Spike-Follower-Mode#configure-spike-follower-manually).
+
+
+
+### [xDrip4iOS](https://xdrip4ios.readthedocs.io/en/latest/)
+
+
+
+Facebook group [xDrip4iOS](https://www.facebook.com/groups/853994615056838)
+
+
+
+### [sugarmate](https://sugarmate.io/)
+
+```{admonition} Important limitation
+:class: warning
+**Sugarmate doesn't allow Nightscout as a data source if you included `bridge` in `ENABLE`.**
+If you need this data source: enable [obscuration](/nightscout/setup_variables.md#bridge-share2nightscout-bridge) variables.
+```
+
+
+
+Add Nightscout as a data source, type your Nightscout URL.
+
+
+
+
+
+### [Diabetes Cockpit](https://apps.apple.com/us/app/diabetes-cockpit/id1580577116)
+
+
+
+
+
+### [Gluco-Tracker](https://apps.apple.com/it/app/gluco-tracker/id1526976290)
+
+
+
+
+
+### [NightscoutMenuBar](https://github.com/mpangburn/NightscoutMenuBar)
+
+### [BitBar Nightscout](https://github.com/pdaddyo/bitbar-nightscout)
+
+
+
+## Mac
+
+### [Nightscout MacOS Menu Bar](https://github.com/adamd9/Nightscout-MacOS-Menu-Bar)
+
+Show your current BG in the system bar at the top of your screen on Mac (including Loop details). Available directly through the [Apple Store](https://apps.apple.com/au/app/nightscout-menu-bar/id1639776072?mt=12).
+
+
+
+
+
+### [GlucoseBar](https://github.com/t1dtools/glucosebar)
+
+Show your current BG in the menu bar and a nice chart for your historic data. Also available on the [Apple App Store](https://apps.apple.com/se/app/glucosebar/id6468110131?l=en-GB&mt=12).
+
+
+
+
+
+## Windows
+
+### [FloatingGlucose](https://github.com/dabear/FloatingGlucose) (archived)
+
+
+
+
+
+### [Owlet](https://github.com/kashamalasha/nightscout-widget-electron)
+
+
+
+
+
+### [NS2Win](https://github.com/emp-00/NS2Win)
+
+
+
+
+
+## Displays
+
+### [M5Stack NightscoutMon](https://github.com/mlukasek/M5_NightscoutMon/wiki)
+
+
+
+### [M5Stick NightscoutMon](https://github.com/mlukasek/M5StickC_NightscoutMon)
+
+
+
+
+
+
+
+### [SugarPiDisplay](https://github.com/bassettb/SugarPiDisplay)
+
+
+
+
+
+## Other
+
+[Home assistant](https://www.home-assistant.io/integrations/nightscout/)
+
diff --git a/_sources/nightscout/first_setup.md.txt b/_sources/nightscout/first_setup.md.txt
new file mode 100644
index 00000000..f978009f
--- /dev/null
+++ b/_sources/nightscout/first_setup.md.txt
@@ -0,0 +1,69 @@
+---
+orphan: true
+---
+
+## New Nightscout Setup
+
+
+
+a) Your Nightscout site should open and direct you to a new profile creation.
+
+
+
+
+
+b) Setup your `Time zone` and eventually all other fields. Do not leave any fields empty. If you don't know which value to use, just use the default value. You can change these values later at any time.
+
+
+
+
+
+c) Browse down to `Authentication status` and click `Authenticate`. Enter your API secret. Click `Update`.
+
+
+
+
+
+d) Click `Save`.
+
+
+
+
+
+e) If the following pop-up shows up click `OK`, and check status (upper right of the window).
+
+
+
+
+
+f) If you need to modify your profile after this, authenticate with the lock icon (top right of the page): enter your API secret. Then click on the hamburger menu and select `Profile Editor`.
+
+
+
+
+
+```{admonition} Privacy warning
+:class: warning
+Anyone with access to the URL of your Nightscout site, can view your BG and run reports of your data. It it strongly recommended that you enable [security](/nightscout/security) to your site once you're done with the setup
+```
+
+
+
+g) Dexcom Share users should see data flowing in after some minutes.
+xDrip+ users (including Medtronic [CareLink followers](/uploader/setup.md#medtronic-carelink)) should setup the uploader as shown [**here**](/uploader/setup.md#xdrip).
+xDrip4iOS users [here](https://xdrip4ios.readthedocs.io/en/latest/connect/cgm/#nightscout-upload).
+[AAPS](https://androidaps.readthedocs.io/en/latest/Configuration/Preferences.html#nsclient) and [Loop](https://loopkit.github.io/loopdocs/operation/loop-settings/services/): consult the relative documentation.
+
+
+
+
+
+------
+
+You have completed a new Nightscout site creation. You can continue [here](/nightscout/discover) now.
+
+The following section provides more information that you might not need to use now.
+
+------
+
+
diff --git a/_sources/nightscout/github.md.txt b/_sources/nightscout/github.md.txt
new file mode 100644
index 00000000..a8611182
--- /dev/null
+++ b/_sources/nightscout/github.md.txt
@@ -0,0 +1,36 @@
+---
+orphan: true
+---
+
+# GitHub
+
+You will need your own GitHub account if you want to deploy Nightscout in some platforms (check below).
+
+````{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Heroku/Railway/Northflank
+You need your own GitHub account and `cgm-remote-monitor` fork (copy).
+:::
+
+:::{tab-item} Fly.io
+A GitHub account and `cgm-remote-monitor` fork (copy) is not mandatory but it is recommended.
+:::
+
+:::{tab-item} Google Cloud (xDrip+ script)
+You don't need a GitHub account.
+:::
+
+````
+
+
+
+## Create a GitHub account
+
+```{include} /vendors/github/create.md
+```
+
+
diff --git a/_sources/nightscout/ifttt.md.txt b/_sources/nightscout/ifttt.md.txt
new file mode 100644
index 00000000..68f766c2
--- /dev/null
+++ b/_sources/nightscout/ifttt.md.txt
@@ -0,0 +1,200 @@
+# IFTTT Integration
+
+If This, Then That (IFTTT) is a useful Nightscout integration. By using IFTTT, you can have single button presses on your iPhone that will set an override, log a cannula change, log a sensor change and much more.
+
+
+## Step 1: Get your API Secret Hash
+
+First we need to gather one thing called your "hashed API Secret". In your internet browser, open a "console" window while viewing your Nightscout site. Make sure you have "authenticated" your site by using your API secret in the Nightscout settings area (hint: if you see a little padlock in the upper left corner of the site, you haven't authenticated it). Refresh the site and your hashed secret key will be shown as "apisecrethash: "xxxxxxxxxx...""
+
+**For Safari users on Mac**, you can open the console window by selecting "Develop" from the Safari top menu, and then "Show Page Source" (if you do not see "Develop" in the top menu, activate it by going to Safari > Preferences... > Advanced, and checking the "Show Develop menu in menu bar" option). If you're having problems seeing the apisecrethash, click the little grey triangle next to the "status isAuthenticated" line and the objects below it will display (see screenshot). Your hashed API secret can be copied and pasted from that line, as shown below. Save that somewhere easy to get to again, because you will be using it later.
+
+
+
+**For Chrome users**, the console window is found through the View >> Developer >> View Source. Click on the Console tab and scroll to find the "status isAuthenticated" row to find your apisecrethash. Copy your API hash to somewhere you can retreive it again, we will be copy/pasting it in Step 2.
+
+
+
+
+## Step 2: Create your "Applets"
+
+IFTTT calls their little actions that you'll create an "applet". I have no idea why. But, I will go along and use their terminology so we are all consistent. We are basically interested in creating applets that will be buttons on your phone to do cool things in Nightscout. So, you'll have a button that will log when you changed your sensor last...letting you see in Nightscout easily just how old a sensor is at any given time. Or you can create a button that will turn on an "exercise" override that you already programmed into your kid's Loop app. So, let's make our first applet (aka button).
+
+* Get an [IFTTT account](https://ifttt.com/join)
+
+
+
+
+
+* Login to your IFTTT.com account and select click [this link](https://ifttt.com/create) to get to the page for creating your first "New Applet". (You can also get to this Applet creation page by selecting your Account icon in the upper right of the IFTTT website, then clicking on "Create".)
+
+* In the screen that appears, click on the black "+this" part of the screen
+
+
+
+
+
+
+* In the next screen, type "button" in the search field and then click on the red box labelled "ButtonWidget"
+
+
+
+
+
+
+* Connect the button widget by clicking on the large black"connect" button twice, once on the main screen and then second on the pop-up window that will appear immediately after that. (You will only have to "connect" the widgets for the first applet you make. After that the widgets will already connected to your IFTTT account.)
+
+
+
+
+
+
+* Click on the large red "button press" box
+
+
+
+
+
+* Click on the black "+that" text
+
+
+
+
+
+
+* Enter "Webhooks" in the search field and click on the Webhooks app
+
+
+
+
+
+
+* Connect the Webhooks app
+
+
+
+
+
+* Select the blue "Make a Web Request" box
+
+
+
+
+
+* Now you will have a blank web request template to complete. Screenshot below is an example of a completed recipe for eating soon IFTTT action. There are four parts you will need to fill in, and they are described below the screenshot.
+
+
+
+```{danger} URL
+`https://yoursite.platform.fqd/api/v1/treatments.json`(for all IFTTT recipes that are NOT remote overrides...so things like cannula changes, sensor changes, pump battery changes, etc.)
+ Change the your URL to your actual site's info.
+```
+
+```{warning} Method
+The method will be `POST`
+```
+
+```{hint} Content Type
+The content type will be `application/json`.
+```
+
+```{danger} Body
+The content of the body will depend on the action that you would like this particular button press to perform. While many recipes are available, any recipe that log carbs to NS will only display the carbs in Nightscout...Loop will not "use" those carbs in treatment or prediction math. The display of carbs in NS though may still be helpful for remote care givers to leave an indication that a low is being noticed and treated. Some sample content for actions that may be useful in Loop:
+ **Pump Site Change**
+ {"enteredBy": "IFTTT-button", "eventType": "Site Change", "duration": 0, "secret": "your_hashed_api_goes_here!!!"}
+ **CGM Sensor Start**
+ {"enteredBy": "IFTTT-button", "eventType": "Sensor Start", "duration": 0, "secret": "your_hashed_api_goes_here!!!"}
+ **Note**
+ {"enteredBy": "IFTTT-button", "eventType": "Note", "notes": "Hi mom, please don't text me for a bit. I'm taking a test.", "secret": "your_hashed_api_goes_here!!!"}
+```
+
+```{warning} Special note for IFTTT to set a Remote Override with dev branch
+Triggering a remote override with IFTTT takes a couple considerations;
+1. You have followed [the directions for setting up remote overrides](https://loopkit.github.io/loopdocs/nightscout/remote-overrides/) in Nightscout already.
+2. Remote overrides will use **`https://yoursite.herokuapp.com/api/v2/notifications/loop`** for the URL line of the applet. Notice that is different from the other type of applets' URL.
+3. The Body message of the applet needs to match the override already programmed in Loop app; the reason, reasonDisplay, and duration all need to match what is preset in your Loop app. The "duration" is giving in minutes in the body message (vs hours in Loop), and if the override is one that is "enabled indefinitely" then the duration is "infinite". The "reason" is the name of the override but NO EMOJI, and the "reasonDisplay" is the override name with the emoji. Check out the samples Body messages for overrides below. You will have to edit your body messages to match your reason and reasonDisplay. The target range and duration of the override does not need to be specified.
+**Body message for override named "hormones"**
+{"eventType": "Temporary Override", "reason": "hormones", "reasonDisplay": "🧟♀️ hormones", "secret": "your_hashed_api_goes_here!!!"}
+**Body message for override named "running"**
+{"eventType": "Temporary Override", "reason": "running", "reasonDisplay": "🏃♀️ running", "secret": "your_hashed_api_goes_here!!!"}
+**Body message for override named "Low Treatment"**
+{"eventType": "Temporary Override", "reason": "Low Treatment", "reasonDisplay": "🍬 Low Treatment", "secret": "your_hashed_api_goes_here!!!"}
+**Body message to cancel any override**
+{"eventType": "Temporary Override Cancel", "secret": "your_hashed_api_goes_here!!!"}
+```
+
+
+* Click the `Create Action` button on the bottom of the screen when you finish.
+
+* Now is your chance to change the title of your applet now to something meaningful. You can turn on notifications, too, using the slider shown. If you turn on the notifications, you will get an alert on your phone and pebble watch when the button press has been successfully deployed. Finish the IFTTT button by clicking on the Finish button that appears.
+
+
+
+
+
+* Repeat the setup for new applets for as many automated actions/overrides as you would like to setup.
+
+
+
+
+
+## Step 3: Enable IFTTT in your Nightscout site
+
+Now that we have cool applets made, we need to give Nightscout some information so that it will accept commands from our applets. It's pretty simple to do...just a couple additions to your Heroku settings.
+
+* Find your Maker Key by going to your IFTTT account icon in upper right corner, choose "My services" and then click on the Webhooks service, settings.
+
+********
+
+
+
+
+* You will see your Maker Key as the last part of the URL after the `use/`; copy and paste that last part (the red circled part as shown)
+
+
+
+
+
+* Login to your Nightscout site host (azure or heroku) and (1) add your Maker Key to the MAKER_KEY line and (2) add "maker" to your ENABLE line.
+
+
+
+
+
+
+
+
+
+## Step 4: Install IFTTT app on your iPhone/Android
+
+Now that all the hard work is done, we can take easy street and just add that work to the phone via the IFTTT app. By accessing the IFTTT widget on your iPhone, you'll be able to easily and quickly access the useful buttons you've just created.
+
+* Download the IFTTT app on your phone and log in using your IFTTT account.
+
+* For iPhone users, if you swipe right from your iPhone's home screen, you will have the Today view showing. Scroll to the bottom, click "edit". This should show a list of existing widgets, followed by a list of "more widgets" with green + signs. Click on the IFTTT's green circle and the widget will be moved to the top, active widgets area. You can hold your finger on the three left lines of the IFTTT widget row to drag it to the top of your widget panel, if you prefer to have it as the top-most widget.
+
+
+
+
+
+If you end up with more than four IFTTT applets, they will appear in reverse-order of when they were created...which may not be the same as you'd prefer them to appear on your widget bar. If you'd like to reorder them:
+
+ * go into your iPhone's IFTTT app
+ * click on My Applets
+ * click on the gear icon in upper left of screen
+ * click on Widgets
+ * click on the pencil icon in upper right of screen
+ * click and hold the three lines that appear on the right side of the widget that you want to move. Drag the widget to the order in the list that you'd like it to appear in your widget quickscreen.
+
+
+
+
+
+## Extra Credit: Alexa integration
+* Since you have IFTTT/Maker requests working, you can get it to work with anything that supports IFTTT, including Alexa. You will need to add "alexa" to your ENABLE line in your Heroku settings. And then repeat the steps above, but instead of using "ButtonWidget" service we started with earlier (the "+if" part of the setup)...you will use the "AmazonAlexa" service.
+
+
+
+
+
+ * Alexa requests do not need underscores, FYI.
diff --git a/_sources/nightscout/multiadmin.md.txt b/_sources/nightscout/multiadmin.md.txt
new file mode 100644
index 00000000..489485a0
--- /dev/null
+++ b/_sources/nightscout/multiadmin.md.txt
@@ -0,0 +1,231 @@
+# Multiple sites and support
+
+
+
+You might need to have access to multiple accounts without having to juggle between logins and passwords. Below are described some centralizing methods reducing the administrative burden.
+
+
+
+## Remote support and security
+
+Giving username and passwords to someone in order to obtain help to fix Nightscout raises serious security issues. Malicious code can be added to your Nightscout project by ill-intentioned people. Always make sure the version deployed is a fork of the official project. After receiving help, good practice is to change your passwords (if shared) and your API secret.
+
+When possible prefer inviting collaborators (see below) and remove them once the issue is fixed.
+
+
+
+## Github
+
+You need only one Github account since you can connect multiple web apps to the same GitHub account.
+
+Using this strategy you only need to update one GitHub account when a new Nightscout version is released and you will be able to deploy it in all your web apps.
+
+```{hint}
+If you have several web apps connected to the same GitHub repository you must use the [standard update method](/update/update/).
+**Not redeploy** (else you'll break all the links to the repository).
+```
+
+
+
+### Enable automatic deploys in Heroku
+
+Automatic deploys will allow you to update automatically your Heroku apps when you update the GitHub repository: you will not need to login into Heroku and perform Manual Deploy, as soon as a new version will be merged into GitHub an automated deploy will trigger in all enabled Heroku apps.
+
+- To enable automatic deploy, [log in Heroku](https://dashboard.heroku.com/apps/) and select your app, then `Deploy`. Verify GitHub and your `cgm-remote-monitor` app are connected.
+
+
+
+
+
+- Verify the `master` branch is selected and click `Enable Automatic Deploys`.
+
+
+
+
+
+- Your Heroku site will update automatically every time you update the GitHub repository.
+
+
+
+
+
+### Automatic deploys in Railway and Northflank
+
+You don't need to do anything as all your web apps will upgrade automatically when you upgrade GitHub.
+
+
+
+## Heroku
+
+You can setup multiple Nightscout sites per Heroku account. You be charged the Eco/Basic plan fee for **each app**.
+
+You can setup collaborators in Heroku. This is very useful for remote support.
+
+
+
+### Invite someone as a collaborator
+
+- Log into your Heroku account and select your app.
+
+
+
+
+
+- Click `Add collaborator` and enter the email address of the person supporting you (that is the email address he used to setup his own Heroku account).
+
+
+
+
+
+- You will now see it as a collaborator. Using the pen icon you can modify it or delete it (useful when asking for support, once everything is working).
+
+
+
+
+
+### Being a collaborator
+
+*Note: you will receive an email with the invitation.*
+
+- Log in your Heroku account. You will see the apps you are collaborating to in the same list than your primary app. You can now perform most tasks directly in that one Heroku account (deploys, change variables, ...).
+
+
+
+
+
+## Atlas
+
+You can invite another user in your organization in order to manage several organizations from the same Atlas account. This is very useful for remote support.
+
+### Invite another user
+
+[Log into](https://account.mongodb.com/account/login) your Atlas account.
+
+
+
+- Top menu, click `Access Manager` and select `Organization Access` from the drop down menu
+
+
+
+
+
+- Click `Invite Users`
+
+
+
+
+
+- Enter the email address of the person supporting you (that is the email address he used to setup his own Atlas account).
+
+
+
+
+
+- Select `Organization Owner` then click `Invite to Organization`.
+
+```{warning}
+**Make sure you enable `Organization Owner` for the invited user!**
+```
+
+
+
+
+
+### Being invited
+
+*Note: you will receive an email with the invitation.*
+
+- Log in your own Atlas account.
+
+- Top left, from the drop down menu click the caret and select `View all Organizations`
+
+
+
+
+
+- In the left menu, click `Invitations` then click `ACCEPT` the invitation.
+
+
+
+
+
+- Going back to all your organizations you can now see and administer both of them from this account. In the example below `Nightscout` is your own organization and `My Org 2020-09-20` is a guest organization.
+
+
+
+
+
+```{hint}
+You can rename your organizations from the top left cog (Settings) then clicking the pen icon.
+```
+
+
+
+
+
+## Northflank
+
+You can setup two Nightscout sites per Northflank account. The 20$ per month credit applies.
+
+You can setup teammates in Northflank.
+
+
+
+### Invite a teammate
+
+- Log into your Northflank account and select `Overview`, in `Members` click **`+`** to add a teammate.
+
+
+
+
+
+- Enter the email address of the person supporting you (that is the email address he used to setup his own Northflank account). Add `Admin` privileges if you want him to interact with your data, leave `Default` for an observer.
+
+
+
+
+
+- You can manage teammates in `Members`: change privileges and delete them, or revoke invitations.
+
+
+
+### Being invited
+
+You will receive an email with the invitation.
+
+You will see the invitee project with yours.
+
+
+
+## Railway
+
+- Open your Railway [dashboard](https://railway.app/dashboard) and select your project.
+
+
+
+- Confirm the invite with `Invite to project`.
+
+
+
+
+
+### Being invited
+
+You will receive an email with the invitation.
+
+You will see the invitee project with yours.
+
+
diff --git a/_sources/nightscout/new_user.md.txt b/_sources/nightscout/new_user.md.txt
new file mode 100644
index 00000000..5d30a3b7
--- /dev/null
+++ b/_sources/nightscout/new_user.md.txt
@@ -0,0 +1,84 @@
+# New Nightscout Users
+
+
+
+**From this you understand there are three main pieces necessary to build your Nightscout:**
+
+1. **The Nightscout code also known as cgm-remote-monitor**
+2. **A cloud platform running the Nightscout web app**
+3. **A cloud database storing Nightscout data**
+
+Some platforms offer both engine and database like Azure, Railway, Northflank and all VPS servers. But you can use an external database if you want. Some others like Heroku or Fly.io don't propose a database and require you to use an external one. Traditionally the database holding Nightscout data is hosted by another provider (mLab, now MongoDB Atlas) but it might not be the most reliable solution.
+
+
+
+## Free DIY
+
+These are the current solutions not involving, or limiting to a strict minimum, costs.
+
+```{note}
+Most vendors will require a credit card to authenticate users and avoid abuse.
+```
+
+[Azure](/vendors/azure/new_user), [Northflank](/vendors/northflank/new_user), [Fly.io](/vendors/fly.io/new_user), [Render](/vendors/render/new_user), [Atlas](/vendors/mongodb/atlas), [Google Cloud](/vendors/google/new_user), [Oracle](https://www.dropbox.com/s/5twlqrndofqno0t/0-amber-oracle.pdf)
+
+
+
+
+
+## Paid DIY
+
+These solutions require a monthly fee.
+
+```{note}
+Paying for a platform doesn't imply your database is included and covered by the plan.
+```
+
+[Heroku](/vendors/heroku/new_user), [Railway](/vendors/railway/new_user) with [database](/vendors/railway/database), [Northflank database](/vendors/northflank/database) or [NAS](nas)
+
+
+
+
+
+## Security and safekeeping
+
+
+- Do not use the same password for all your accounts, and choose passwords that are not easy to guess.
+- Do not use the `API_SECRET` for the Atlas database password.
+- Do not use your Dexcom or CareLink user name or password for Nightscout components.
+- Do not share the `API_SECRET` or other passwords of your accounts to others.
+- Do not use Nightscout or any related applications on rooted and/or otherwise compromised devices, and ensure you always have the latest operating system and virus protection updates installed.
+
+If you want to read more about Nightscout security, including about additional configuration options to make your installation more secure, please check our [security guide](/nightscout/security.md).
+
+
diff --git a/_sources/nightscout/platform.md.txt b/_sources/nightscout/platform.md.txt
new file mode 100644
index 00000000..288b11a0
--- /dev/null
+++ b/_sources/nightscout/platform.md.txt
@@ -0,0 +1,159 @@
+# Choose your platform
+
+```{admonition} Too complicated? Not what you're looking for?
+:class: seealso
+Consider a hosted Nightscout service! Check for easier solutions [here](/index.md#nightscout-as-a-service).
+```
+
+
+
+Various platforms are available to host your Nightscout site in the cloud.
+
+```{warning}
+**Creating a [database](/nightscout/database) is mandatory if you want to use: Heroku, Railway, Northflank, Fly.io or Azure.**
+Make sure you have one before creating a Nightscout web app in these platforms.
+```
+
+Find a list of commonly used hosting services below, decide which one you'll want to use.
+
+
+
+```{card}
+## Heroku
+
+^^^
+Since the [beginning](https://github.com/nightscout/cgm-remote-monitor/pull/98) Heroku has been a very popular platform for Nightscout. Most of the documentation was based on a Heroku Nightscout.
+On August 25th 2022, Salesforce decided to [drop the free plan](https://blog.heroku.com/next-chapter).
+You can [create your new Nightscout site with Heroku](/vendors/heroku/new_user) using an [Eco plan](https://www.heroku.com/pricing) (5$/month).
+
+**Pros**:
+* Large platform with a reliable history
+* Well documented, well known by the community
+
+**Cons**:
+* The Eco plan has the same limitations than the previous Free plan, for 5$ per month
+* For a Nightscout site a 7$ per month Basic plan is not really worth it (compared to hosted solutions)
+* **Doesn't include a database**
+
++++
+Follow [these instructions](/vendors/heroku/new_user.md) to build your Nightscout site in Heroku.
+```
+
+```{card}
+## Azure
+
+^^^
+Nightscout DIY was [originally](https://github.com/rnpenguin/cgm-remote-monitor) created with Azure but most users dropped it after costs increased.
+A new deployment method fitting in the [free tier](https://azure.microsoft.com/en-us/pricing/free-services) has [been created using a Docker container](/vendors/azure/new_user).
+
+**Pros**:
+* Large platform with a reliable history
+* Well known by the community IT specialists
+* Using a basic plan and free services keep it free
+
+**Cons**:
+* Trial account lasts maximum 12 months
+* Basic plan and pay as you go is free if you stay within quotas
+* The F1 free app service plan is designed for testing, not production
+* **The Cosmos database doesn't integrate correctly with Nightscout**
+
++++
+Follow [these instructions](/vendors/azure/new_user.md) to build your Nightscout site in Azure.
+```
+
+```{card}
+## Railway.app
+
+^^^
+You can easily create a new Railway Nightscout site with a MongoDB Atlas or a Railway MongoDB database. The [Hobby plan](https://railway.app/pricing) (5$ per month) allows one Nightscout site and a small database.
+
+**Pros**:
+* Easy to deploy or migrate an existing site from Heroku (but not worth it without free tier)
+* Simple to use and troubleshoot
+* Can use a reliable native Railway MongoDB database, the cost will add-up within the subscription ($)
+
+**Cons**:
+* The free tier has been removed, only active developers can have 5$ credit per month
+* The railway.app domain is blocked for safety by some companies
+* Railway network model causes issues with some follower app and devices
+
++++
+Follow [these instructions](/vendors/railway/new_user.md) to build your Nightscout site in Railway.
+```
+
+```{card}
+## Northflank
+
+^^^
+You can create your new [free](https://northflank.com/pricing) Northflank Nightscout site, with its own Northflank database or with a MongoDB Atlas database.
+
+**Pros**:
+* Nightscout fits in the free tier
+* Easy to deploy or migrate an existing site from Heroku
+* Simple to use and troubleshoot
+* Can use a professional native Northflank MongoDB database ($)
+
+**Cons**:
+* The Nightscout address generated for your site is impossible to remember
+
++++
+Follow [these instructions](/vendors/northflank/new_user.md) to build your Nightscout site in Northflank.
+```
+
+```{card}
+## Fly.io
+
+^^^
+Fly.io proposed a simple migration wizard from Heroku and you can create your new Nightscout site in Fly.io. Using a computer is mandatory with Fly.io as managing your site will require the use of a command line utility. Not recommended for beginners.
+
+**Pros**:
+* Nightscout fits in the free tier
+* Easy to migrate an existing site from Heroku
+
+**Cons**:
+* **Maintaining your site requires the use of command line instructions, not very intuitive**
+* **Doesn't include a database**
+
++++
+Follow [these instructions](/vendors/fly.io/new_user.md) to build your Nightscout site in Fly.io.
+```
+
+```{card}
+## Google Cloud
+
+^^^
+A scripted Nightscout installation in Google Cloud is a new complete solution proposed by the xDrip+ developers team. Whilst deploying Nightscout manually in Ubuntu can be complex, their approach makes is rather simple for non-technical people.
+
+**Pros**:
+* Complete solution offering a large free database
+* A web interface to edit your variables
+* Tools provided to migrate the database from another platform
+* Virtually free (<5c/month)
+
+**Cons**:
+* Not available for free for Australia and Cina users
+* Relying on a free DNS provider
+
++++
+Follow [these instructions](https://navid200.github.io/xDrip/docs/Nightscout/GoogleCloud.html) to build your Nightscout site in Google Cloud.
+```
+
+```{card}
+## Render
+
+^^^
+A free solution with little experience.
+
+**Pros**:
+* No credit card required
+
+**Cons**:
+* The free plan doesn't guarantee any reliability
+* App will sleep after 15 minutes
+* Render URLs are considered unsafe by some internet providers
+* **Doesn't include a database**
+
++++
+Follow [these instructions](/vendors/render/new_user.md) to build your Nightscout site in Render.
+```
+
diff --git a/_sources/nightscout/plugins-old.md.txt b/_sources/nightscout/plugins-old.md.txt
new file mode 100644
index 00000000..dfb08c82
--- /dev/null
+++ b/_sources/nightscout/plugins-old.md.txt
@@ -0,0 +1,4 @@
+---
+orphan: true
+---
+
diff --git a/_sources/nightscout/plugins-v15.md.txt b/_sources/nightscout/plugins-v15.md.txt
new file mode 100644
index 00000000..1adfd179
--- /dev/null
+++ b/_sources/nightscout/plugins-v15.md.txt
@@ -0,0 +1,68 @@
+---
+orphan: true
+---
+
+# [Nightscout-connect](https://github.com/nightscout/nightscout-connect)
+
+As the dependencies of the historical plugins (`bridge` and `mmconnect`) have been deprecated, a new plugin has being created to allow long term sustaining and increase the number of supported cloud providers.
+
+This plugin is under test and is currently only available in the `dev` branch of Nightscout ([version 15.0](https://github.com/nightscout/cgm-remote-monitor/tree/dev)).
+
+## Prerequisites
+
+You need to use the development branch of Nightscout.
+
+```{admonition} AAPS users
+:class: warning
+Do not upgrade Nightscout to V15 unless you use the `dev` version of AAPS.
+```
+
+Follow [these guidelines](/update/dev_branch) to update your Nightscout app to `dev`.
+
+
+
+In order to enable the `nightscout-connect` plugin you need to add `connect` in your ENABLE variable.
+
+Edit your variables following [these instructions](/nightscout/setup_variables.md#nightscout-configuration), search the `ENABLE` variable, modify its contents to add the word `connect`, separated by a space, at the end of the line.
+
+
+
+## `dexcomshare`
+
+`dexcomshare` is the replacement of `bridge`.
+
+In order to use it you need to add the following variables in your [Nightscout configuration](/nightscout/setup_variables.md#nightscout-configuration):
+
+Remove the word `bridge` from the `ENABLE` variable list.
+
+`CONNECT_SOURCE=dexcomshare`
+
+`CONNECT_SHARE_SERVER=ous` Add this variable **only** if you're not in the US. **Else don't add it (us).**
+
+`CONNECT_SHARE_ACCOUNT_NAME=` The username on your master device (the one connected to the sensor)
+
+`CONNECT_SHARE_PASSWORD=` The password matching the username above.
+
+
+
+## `minimedcarelink`
+
+`minimedcarelink` is the replacement of `mmconnect`.
+
+In order to use it you need to add the following variables in your [Nightscout configuration](/nightscout/setup_variables.md#nightscout-configuration):
+
+Remove the word `mmconnnect` from the `ENABLE` variable list.
+
+`CONNECT_SOURCE=minimedcarelink`
+
+`CONNECT_CARELINK_REGION=us` or `eu` Match the area with minimed.carelink.**eu** or .com (i.e. **us**)
+
+`CONNECT_CARELINK_USERNAME=` The username on your master device Minimed app
+
+`CONNECT_CARELINK_PASSWORD=` The password matching the username above.
+
+If you are caregiver of more than one patient also add:
+
+`CONNECT_CARELINK_PATIENT_USERNAME=` The name of the patient whom data you'll want in Nightscout.
+
+
diff --git a/_sources/nightscout/profile_editor.md.txt b/_sources/nightscout/profile_editor.md.txt
new file mode 100644
index 00000000..7b483c5a
--- /dev/null
+++ b/_sources/nightscout/profile_editor.md.txt
@@ -0,0 +1,67 @@
+# Setup your Profile
+
+
+
+The top part will show your site settings: [`Title`](/nightscout/setup_variables.md#custom_title-nightscout), [`Units`](display-units) and [`Date Format`](/nightscout/setup_variables.md#time_format-12).
+
+
+
+
+
+## Profile view
+
+Profile Editor will display your active profile. If you created more than one profile you can select the one you want with the drop down menu `Stored Profiles`.
+
+You can add a profile with `+`, delete it with `X` and duplicate (clone) it to create a new one starting with the values in the current one.
+
+Note: changing profile selection keeps the modifications you've made in other profiles.
+
+
+
+
+
+Each profile has a `Name`, a `Timezone` and a `DIA` that you can modify. If you don't know which DIA to use, ask you endocrinologist since this is a complex subject. See also [here](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4454113/).
+
+
+
+
+
+For each profile you can define `Insulin to carb ratio (I:C)`, `Insulin sensitivity factor (ISF)` and `Carbs absorption rate`. Both `I:C` and `ISF` can be defined for specific times of the day by slices of 30 minutes, click the `+` sign to add another interval.
+
+These values are key to diabetes management. Ask your endocrinologist about them if you don't know where to start.
+
+Look [here](https://diyps.org/2014/05/29/determining-your-carbohydrate-absorption-rate-diyps-lessons-learned/) for calculating the carbs absorption rate.
+
+
+
+
+
+If your uploader doesn't send pump `basal` values to Nightscout, you can duplicate the information in `Basal rates` in order to match your current basal profile (and Nightscout is also a nice place to save this information). Basal rates can be defined by 30 minutes intervals, click `+` to add another one .
+
+
+
+
+
+You can also define your `Target BG range` Low and High for various moments of the day.
+
+
+
+
+
+After you defined your profile you need to `Authenticate` with your API Secret in order to be able to save it.
+
+For modifications, read the next paragraph and make sure you understand the `Database records` mechanism.
+
+
+
+
+
+## Modifying a profile and Database records
+
+When you modify a profile and save it, the whole database record will be updated to reflect the profile change. This means all periods of time using this specific profile since the database record `Valid time and date` will be updated to your profile modification. If you don't want this to happen, you should create a new database record and recreate your profiles in this new record.
+
+You can add a record with `+`, delete one with `X` (it will delete the corresponding profiles information in the time frame of the record) and duplicate (clone) it.
+
+
+
+
\ No newline at end of file
diff --git a/_sources/nightscout/pushover.md.txt b/_sources/nightscout/pushover.md.txt
new file mode 100644
index 00000000..3c3ec8c0
--- /dev/null
+++ b/_sources/nightscout/pushover.md.txt
@@ -0,0 +1,349 @@
+# Remote notifications
+
+While Loop app currently sends notifications locally on Loop user's iPhone, parents and caregivers likely want those messages on their phones, too. We can achieve this functionality through a combination of Nightscout, IFTTT, Google, and Pushover.
+
+Traditionally, most people may already know of Pushover alerts through their NS site. The old Loop docs had set up for how to add your `PUSHOVER_ANNOUNCEMENT_KEY` , `PUSHOVER_API_TOKEN`, and `PUSHOVER_USER_KEY` in your Heroku settings to get notifications on the non-looping phones of parents and caregivers. The drawback for that method is that you could not necessarily fine-tune the alerts (maybe you wanted battery alarms on your NS website, but not get pushovers for them...a bit hard to separate out the environments that way) and Pushover had a demanding acknowledgment requirement. If you failed to acknowledge an alert, you may end up getting alarm fatigue fairly quickly as the alarm repeated itself.
+
+Using Pushover **THROUGH** IFTTT however, we can improve the possible notifications and who receives which ones. For example, a teenage Looper may want notifications when his/her pump site needs changing and when his/her Dexcom is about to expire in the next day. S/he already gets local notifications on his/her phone via Loop for low reservoir volumes, low pump battery, and Loop failures. Dexcom app provides high/low BG notifications locally, too. If s/he were to get those same alarms via Pushover, s/he would inevitably get alarm fatigue. A remotely-monitoring parent may want additional information, like a pushover alert when the school nurse boluses for lunch, as well as Loop failures, low iPhone battery level for the child, low pump battery, and other such information that might be useful. Perhaps there's also an emergency contact person that you only want to get high/low BG alerts...you can set that up as well quite easily.
+
+The basic concept is that NS puts out an event that triggers the IFTTT service called Webhooks (old name was "Maker Webhooks" hence you may see references to "maker" in NS docs). Actually, there are several types of events that NS has programmed in all ready to use in IFTTT.
+
+
+
+
+
+For this setup, we are going to use the most general logging event called `ns-event`. You'll get all the alarms and notifications logged, and then you can decide in subsequent steps which ones you'd actually like to send to your phone for pushover notification.
+
+As a brief roadmap for what we are going to do:
+
+1. Get necessary accounts setup
+2. Add a folder to your Google Drive
+3. Make an IFTTT applet to log NS events to your Google Spreadsheets
+4. Enable NS to work with that new IFTTT applet
+5. Make an IFTTT applet to send Pushover alert when the Google Spreadsheet is updated
+
+## Get Prepped
+
+If you don't already have these steps done, you will need them. Skip any that you already have done.
+
+* Setup a Nightscout site
+* Get an [IFTTT account](https://ifttt.com)
+* Get a [Pushover Account](https://pushover.net)
+* Get a [Google Account](https://accounts.google.com/SignUp)
+* Download the Pushover app onto your phone, and any other phone you'd like to receive Pushover alerts
+* Download the IFTTT app onto your phone, and any other phone you'd like to use IFTTT applets on
+* Login to the Pushover and IFTTT apps with your login information
+
+## Add a Google Drive folder
+
+* Login to your Google account and select Google Drive
+
+
+
+
+
+* Click on the blue "New" button and create a new folder named IFTTT.
+
+
+
+
+
+* Double click on the newly created IFTTT folder, select the blue "New" button again, and create a new subfolder called "Nightscout-Alarms"
+
+
+
+
+
+This IFTTT/Nightscout-Alarms folder will eventually contain numerous Google Spreadsheets, one for each NS alarm or information that is logged. As new alarms are triggered, the IFTTT applet we are about to write will add a row to the appropriate spreadsheet logging the time of the alarm and any other reported details that go with the entry. For now though, your drive will be blank...screenshot below just to give you an idea of where we are going.
+
+
+
+
+
+## Make 1st IFTTT Applet to Log NS Alarms
+
+* Login to your IFTTT.com account and select the "New Applet" button.
+
+
+
+
+
+* In the screen that appears, click on the blue "+this" part of the screen
+
+
+
+
+
+* Click on the blue "+that" text
+
+
+
+
+
+* Enter `google` in the search field and click on the Google Sheets icon
+
+
+
+
+
+* Select the green "Add row to spreadsheet" box
+
+
+
+
+
+* Delete the contents of the "Spreadsheet Name" and "Drive folder path". For the "Spreadsheet Name", click the "Add Ingredient" button and select the "Value1". For the "Drive folder path", enter `IFTTT/Nightscout-Alarms`. You do not have to modify the "Formatted row" box's contents. Click the "Create action" button at the bottom.
+
+
+
+
+
+* Turn off the toggle for receiving notifications when the applet runs, and then click the Finish button
+
+
+
+
+
+* You'll now have the finished IFTTT applet that will cause a row to be added to a Google spreadsheet...tracking all your NS notifications and alarms. If it is the first time that alarm has been logged, the applet will also create the spreadsheet itself. After a while, your IFTTT/Nightscout-Alarms folder will start to look like the screenshot posted above with numerous spreadsheets for each alarm type.
+
+
+
+
+
+## Enable IFTTT Webhooks in your Nightscout site
+
+```{note}
+If you already have created IFTTT buttons previously to work with your NS site, you can skip this section. If those buttons are working, then you've already added your MAKER_KEY and "maker" to your ENABLE line in Heroku.
+```
+
+* To actually make that first applet work, we need to enter a "Maker Key" to get NS and IFTTT talking to each other. Find your Maker Key by going to your IFTTT account, Services and then clicking on Webhooks. (Your screen may not have as many services showing; the example account below just happens to already use several services.)
+
+
+
+
+********
+
+
+
+
+* In the screen that appears, click on the blue "+this" part of the screen
+
+
+
+
+
+* Enter the following information: Folder path is `IFTTT/Nightscout-Alarms` and for the filename you are going to enter the name of the particular NS alarm or information that you would like to get pushover alerts for. Click on the "Create trigger" button to save the trigger.
+
+
+
+
+```{note}
+This applet can't be created unless your filename (alarm spreadsheet) already exists. If your 1st applet we created above hasn't run for a long time, the spreadsheets may not exist yet because the alarms haven't triggered. You have two options...(1) manually create the file in your Google Drive so that you can finish the applet now or (2) wait several days/weeks for the alarms to happen and that will automatically create the files in your Google drive.
+If you choose option 1, here's a partial list of some of the filenames you could create in advance:
+```
+
+ * Loop isn't looping
+ * Cannula age 48 hours
+ * Cannula age 72 hours
+ * Meal Bolus
+ * Warning, Pump Reservoir Low
+ * Warning Uploader Battery is Low
+ * Temporary Override
+
+ Depending on your alert levels you specified in NS, some of the hours in the titles may vary to match your settings
+
+* Click on the blue "+that" text
+
+
+
+
+
+* Select the "Send a Pushover notification" box
+
+
+
+
+
+* Delete the contents of the "Title" and "Message" and "URL" boxes. For the Title, click the "Add Ingredient" button and add `ColumnC`. For the "Message", click the "Add Ingredient" button and add the values of various columns from your spreadsheet for the information you would like to include. For the alerts: `ColumnC` contains the alarm name, `ColumnA` is the date/time of the alarm, and `ColumnD` has more detailed information about the info/alarm. This is a pretty decent recipe to follow to get the useful information in your notification.
+
+
+
+
+* Select the "Message Priority" that you would like for this particular alarm type.
+
+
+
+
+
+* Select the "Device" that you would like to receive this particular alarm type. The devices listed will be all your devices that have Pushover app installed and logged into. Click "Create Action" when you are finished.
+
+
+
+
+
+* You'll now have made the IFTTT applet that will cause a Pushover notification to a particular device for a particular NS alarm, once the first applet records the alarm in the google spreadsheet. Keep the "receive notification when this Applet runs" toggled off and click the Finish button.
+
+
+
+
+
+## Revisit Nightscout Alert Levels
+
+Putting all these notifications together may cause you to want to revisit the alert levels you have set in your Heroku settings. Here's a short summary of NS for the looping-related alerts (Note: the last row, Upbat, is the Looping iPhone battery level for Loop users; or the rig's battery level for OpenAPS users.) If you'd like some of these alarms for your site and don't currently have them activated (they are all off by default unless specifically turned on), the lines you'd need to add are in the last column. If you like the default values of the WARN and/or URGENT, you don't have to add those extra lines...just the line to enable the alerts will be sufficient.
+
+
+
+
+* Here are examples of the Meal Bolus and Temp Basal ns-event logging spreadsheets
+
+
+
+
+
+
+
+* The 1st applet can only create up to 2000 active rows in a given spreadsheet. After that, the applet will automatically create a new spreadsheet. For most alarms, it may take quite some time to reach 2000 rows of info. For other alerts, such as temp basals being set, that may fill up rather fast for the average looper. You can either clean out the data rows periodically to make room, or update your filename in the 2nd applet periodically when a new spreadsheet is made.
+
diff --git a/_sources/nightscout/reports.md.txt b/_sources/nightscout/reports.md.txt
new file mode 100644
index 00000000..7eb8a7c8
--- /dev/null
+++ b/_sources/nightscout/reports.md.txt
@@ -0,0 +1,217 @@
+# Create Reports
+
+Nightscout offers some fantastic data-crunching report tools in the drawer menu,
+
+
+
+
+
+First select the report type you'd like to see (see below for an overview).
+
+`Day to day`, `Week to week`, `Daily Stats`, `Distribution`, `Hourly stats`, `Percentile Chart`, `Weekly Distribution`, `Calibrations`, `Treatments`, `Profiles` or `Loopalyzer`
+
+Then select the period for which you want your data analyzed.
+
+Enable the check box and either select `From:` and `To: `dates or `Today`, `Last 2 days`, `Last 3 days`, `Last week`, `Last 2 weeks`, `Last Month`, `Last 3 months`.
+
+
+
+
+
+You can filter your data using key `Notes` or `Event type` (select one in the drop down list).
+
+
+
+
+
+You can select which week days to use in order to better analyze patterns.
+
+
+
+
+
+Click `SHOW` and wait for data to load and rendering to complete. This might take some time if the period is long.
+
+
+
+
+
+If you want to change selections, you need to click again `SHOW` to update the view.
+
+
+
+
+
+If you select `Insulin distribution` you will get a short report.
+
+Note: You need `Basal rate` enabled to see bolus vs basal information.
+
+
+
+
+
+You can change the vertical scale to `Logarithmic` or `Linear`.
+
+You can change the graph `Size`.
+
+
+
+
+
+## Week to Week
+
+This report will give you a week by week view, with color code for week days selected.
+
+
+
+
+
+## Treatments
+
+This will give you a table of your treatments, day by day.
+
+
+
+
+
+## Profiles
+
+This report will display [profiles](/nightscout/profile_editor.md) used in the time range.
+
+
+
+
+
+## Loopalyzer
+
+Loopalyzer is an utility made to help analyze and tune closed loop systems. It may work with other setups as well, both closed and open loop, and non loop.
+
+Select the period on which you want to run the report then click `Show`. A set of graphs will display top to bottom your basal profile, blood glucose, loop deviation from basal (that should be minimized for an optimized closed loop system), insulin on board and carbs on board. On the last two graphs, treatments are represented by vertical black bars.
+
+
+
+
+
+Using the dedicated menu you can display your profiles below the graph and use `Timeshift`. Click `Show` to update the display when changing the options.
+
+You can navigate day to day with `< Previous day` and `Next day >` or by period length with `<< Previous` and `Next >>` (i.e. if you selected a week it will go backwards and forward week by week).
+
+ 
+
+`Timeshift` will allow you to synchronize meals within a time range in order to better analyze your data. Obviously the rest of the day will not make sense since the shift only highlights the time range you are analyzing now. For example below: dinner analysis.
+
+
+
+
+
+You might also be interested by [AutoTune](https://autotuneweb.azurewebsites.net/).
+
+```{warning}
+Make sure to temporarily [disable authentication](/nightscout/security.md#how-to-turn-off-unauthorized-access) before running AutoTune.
+```
+
+
+
+## Nightscout Reporter
+
+[https://nightrep.zreptil.de/](https://nightrep.zreptil.de/) can be used to generate PDF documents with the data stored at Nightscout.
+
+You need to add [`cors`](/nightscout/setup_variables.md#cors-cors) to your [`ENABLE`](enable) variables
+
+Facebook group [Nightscout Reporter](https://www.facebook.com/nightrep)
+
+
+
+## Power BI
+
+Facebook group [Nightscout Power BI Reporting](https://www.facebook.com/groups/857487091295727)
diff --git a/_sources/nightscout/security.md.txt b/_sources/nightscout/security.md.txt
new file mode 100644
index 00000000..e14860dd
--- /dev/null
+++ b/_sources/nightscout/security.md.txt
@@ -0,0 +1,134 @@
+
+# Nightscout Security and Privacy
+
+Nightscout security model is based on the following assumptions:
+
+* The users of Nightscout only use it to process information about themselves or someone they're legally responsible for and thus own all of the data being stored in Nightscout.
+* Given the user / operator of Nightscout is assumed to have full ownership of the data stored in Nightscout, it is assumed the user has full responsibility around the use and sharing of the data.
+* Nightscout provides a set of APIs for reading and writing data into the Nightscout database. Nightscout itself does not directly interface with any devices. Nightscout users should verify any applications using the APIs to process the data in Nightscout have been implemented in a secure fashion and have data validation processes in place in case an unauthorized user gains access to Nightscout and alters the data.
+* If unauthorized users gain access to the server being used to host Nightscout, the database used with Nightscout or any device used to access the Nightscout APIs, the entire system's security has to be considered compromised and the user must assume any data stored in the system might be altered and thus should not be trusted.
+
+```{admonition} Personal use only
+:class: warning
+The system has not been designed for scenarios where a third party operates a Nightscout installation on behalf of others and if such installations are made, both the users and operators of such installations need to understand there is a large body of legislation across the world that covers use cases and data storage enabled by Nightscout and the liability issues around such installations are extremely complicated.
+```
+
+
+
+## Security and safekeeping
+
+- Use the same email address for all accounts so you'll have access to all your accounts after installation. **Do not use a disposable email address** - use something you know you can access later.
+- Use a safe password for all accounts related to Nightscout, including the password for the email account for the accounts. We highly recommend using a password manager such as 1Password and allowing it to generate the passwords for you.
+- Do not reuse the same password for all your accounts.
+- Do not use your Dexcom or CareLink user name or password for Nightscout components.
+- Do not use the API_SECRET for the Atlas database password.
+- Do not share the API_SECRET or access tokens with administration privileges to anyone, ever. If you need to grant access to Nightscout, see below for instructions how to create access tokens for this purpose.
+- Do not use Nightscout or any related applications on rooted and/or otherwise compromised devices, and ensure you always have the latest operating system and virus protection updates installed.
+
+
+
+## HTTPS and certificate errors
+
+One of the core security mechanisms on web is the SSL encryption applied to HTTP connections. When installed to Heroku, Nightscout by default forces connections to use HTTPS, thus ensuring the connection is encrypted. For secure Nightscout use, it's crucial that you assume something is wrong if you ever see your browser complain the SSL certificate of your Nightscout site does not match or work as expected by the browser. This can be a sign of a so called Man In The Middle (MITM) attack and proceeding with the problematic certificate will subsequently compromise your Nightscout site. If you see an error related to SSL, you should immediately rename the site (see below for instructions).
+
+
+
+## Administration messages
+
+Nightscout 14.2 introduced a new feature called Admin Notifies, which can warn you about issues with Nightscout installation and security issues.
+
+If you see the red megaphone in your navigation bar, it means you have messages in the queue.
+
+
+
+You have to be authenticated to Nightscout using the API_SECRET or an authentication token that has administration access to read the messages.
+
+
+
+There are multiple types of messages that might be shown:
+
+
+
+### I'm seeing a message about the API_SECRET being weak
+
+
+
+This message is shown when cryptographic analysis if the API_SECRET shows the secret is easily guessable by a computer and should be changed. Things you can do to have this message go away:
+
+* The API_SECRET must be at least 12 characters long, but making it even longer makes it more secure
+* Use a mix of small and CAPITAL letters, numbers and non-alphanumeric characters such as !#%&/()= in the API_SECRET
+ *Note: make sure your uploader and downloaders can handle special characters, you might need to express them using [Percent encoding](https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters) for example an API_SECRET like `D0n't*H4ck@M3%` would be expressed as: `D0n%27t%2AH4ck%40M3%25`*
+* Consider generating the API_SECRET using a password manager
+
+
+
+### I'm seeing a message about authentication failures
+
+
+
+This is highly likely caused by you having installed an app on some device with the wrong API_SECRET or access token, and the app trying to authenticate to your Nightscout, or you or one of the family members have just tried to sign into Nightscout with wrong credentials.
+
+If you have apps running that use the Nightscout REST API, check you have the correct API_SECRET and/or access token configured to each.
+
+If the message keeps appearing unexpectedly or is reported against multiple IP numbers, it's possible someone is trying to brute force attack your installation and guess your API_SECRET to be able to modify data in your Nightscout. In this situation, we highly recommend you rename the Nightscout site to change it's address and pick a name that's hard to guess.
+
+
+
+### I'm seeing a message Nightscout is readable by the world
+
+
+
+This means the site shows the CGM data to users who can guess the site address without authentication. Note Nightscout never allows data to be saved or edited without authentication, so this is not necessarily a problem depending on how hard your site address is to guess and how you want the information to be shared.
+
+If you want to have the site require authentication, read the "How to Turn Off Unauthorized Access" section below.
+
+
+
+## Renaming the Nightscout site
+
+See the instructions in the specific platform section for a new Nightscout creation.
+
+Once done, make sure all apps (uploaders and downloaders) are updated accordingly.
+
+
+
+## How to Turn Off Unauthorized Access
+
+```{admonition} Privacy warning
+In a default setup, **anyone** with your Nightscout URL can view your site.
+```
+
+```{hint}
+Make sure [the app you use to see your data](/nightscout/downloaders) can handle a secured Nightscout site.
+```
+
+To Take Advantage of Roles, Turn Off Unauthorized Access to Your Site:
+
+If you want to ensure that ONLY someone with permission to view your site (e.g., a token) is able to view the data, you should configure the [`AUTH_DEFAULT_ROLES`](auth_default_roles) variable. Set the value as: `denied`.
+
+Edit (or add) this variable and set it to `denied` (see [here](/nightscout/setup_variables.md#nightscout-configuration) how to edit variables).
+
+
+
+This creates a scenario in which a token will be required for all access (even only view).
+
+
+
+
+
+#### `CUSTOM_TITLE` (`Nightscout`)
+
+The display name for the Nightscout site. Appears in the upper left of the main view. Often set to the name of the CGM wearer.
+
+
+
+#### `THEME` (`colors`)
+
+Color theme of the CGM graph.
+
+`default`
+
+
+
+`colors`
+
+
+
+`colorblindfriendly`
+
+
+
+
+
+#### `SHOW_PLUGINS`
+
+Default setting for whether or not these plugins are checked (active) by default, not merely enabled. Include plugins here as in the `ENABLE` line; space-separated and lower-case.
+
+When you `ENABLE` a plugin, it will be used by Nightscout but might not be visible unless you select it in the [drawer menu](/nightscout/discover.md#settings). If you want a plugin to display by default you need to add it to the `SHOW_PLUGINS` list.
+
+More details [below](#plugins).
+
+
+
+#### `SHOW_FORECAST` (`ar2`)
+
+Plugin forecasts that should be shown by default, supports space delimited values such as:
+`ar2 openaps loop false`
+
+Note the ar2 forecast is selected by default so if no value is set, it will be AR2. AR2 is an early attempt at forecasting BG and you should not base any medical decisions on it's predictions.
+
+If you are looping, you can chose instead to use either `loop` or `openaps` which will use the appropriate algorithm.
+
+You should also add the parameter to the `SHOW_PLUGINS` and `ENABLE` variables.
+
+For example, if you are using the Loop app for iPhone, you should have the following settings (In addition to any others outlined in the docs):
+
+```
+ENABLE=loop
+SHOW_PLUGINS=loop
+SHOW_FORECAST=loop
+```
+
+
+
+#### `LANGUAGE` (`en`)
+
+Language of Nightscout. If not available English is used.
+
+Currently supported language codes are: `bg` (Български), `cs` (Čeština), `de` (Deutsch), `dk` (Dansk), `el` (Ελληνικά), `en` (English), `es` (Español), `fi` (Suomi), `fr` (Français), `he` (עברית), `hr` (Hrvatski), `it` (Italiano), `ko` (한국어), `nb` (Norsk (Bokmål)), `nl` (Nederlands), `pl` (Polski), `pt` (Português (Brasil)), `ro` (Română), `ru` (Русский), `sk` (Slovenčina), `sv` (Svenska), `tr` (Turkish), `zh_cn` (中文（简体)), `zh_tw` (中文（繁體))
+
+
+
+#### `SCALE_Y` (`log`)
+
+The type of scaling used for the Y axis of the charts system wide.
+
+The default `log` (logarithmic) option will let you see more detail towards the lower range, while still showing the full CGM range.
+
+
+
+The `linear` option has equidistant tick marks; the range used is dynamic so that space at the top of chart isn't wasted.
+
+
+
+The `log-dynamic` is similar to the default `log` options, but uses the same dynamic range and the `linear` scale.
+
+
+
+
+
+#### `EDIT_MODE` (`on`)
+
+Possible values `on` or `off`. Enables the icon allowing for editing of treatments in the main view. More about edit [here](/nightscout/discover.md#edit-mode-edit).
+
+
+
+
+
+#### `BOLUS_RENDER`
+
+Settings to configure Bolus rendering
+
+`BOLUS_RENDER_OVER` (`0`) - U value over which the bolus labels use the format defined in `BOLUS_RENDER_FORMAT`. This value can be an integer or a float, e.g. `0.3`, `1.5`, `2`, etc.
+
+`BOLUS_RENDER_FORMAT` (`default`) - Possible values are `hidden`, `default` (with leading zero and U), `concise` (with U, without leading zero), and `minimal` (without leading zero and U).
+
+`BOLUS_RENDER_FORMAT_SMALL` (`default`) - Possible values are `hidden`, `default` (with leading zero and U), `concise` (with U, without leading zero), and `minimal` (without leading zero and U).
+
+
+
+
+
+------
+
+### Split View
+
+Some users will need easy access to multiple Nightscout views at the same time. We have a special view for this case, accessed on /split path on your Nightscout URL. The view supports any number of sites between 1 to 8 way split, where the content for the screen can be loaded from multiple Nightscout instances. Note you still need to host separate instances for each Nightscout being monitored including the one that hosts the split view page - these variables only add the ability to load multiple views into one browser page. To set the URLs from which the content is loaded, set:
+
+`FRAME_URL_1` - URL where content is loaded, for the first view (increment the number up to 8 to get more views)
+
+`FRAME_NAME_1` - Name for the first split view portion of the screen (increment the number to name more views)
+
+
+
+For example:
+
+`FRAME_URL_1` `https://janecgm.myurl.fqd`
+
+`FRAME_NAME_1` `Jane`
+
+`FRAME_URL_2` `https://joecgm.myurl.fqd`
+
+`FRAME_NAME_2` `Joe`
+
+
+
+To display the split view browse to:
+
+`https://myAppName.myurl.fqd/split`
+
+
+
+8 split view example:
+
+
+
+
+
+------
+
+## Plugins
+
+Plugins are used to extend the way information is displayed, how notifications are sent, alarms are triggered, and more.
+
+If you want the `ENABLE`'d plugins to **show by default on any browser**, you should put them in the `SHOW_PLUGINS` variable.
+
+If you want to specifically disable a plugin (mainly a default plugin) you should place it in the `DISABLE` variable.
+
+You also can decide to visualize them or not on your Nightscout view with the drawer menu. `Authenticate` and `Save` the settings on your browser. Your site variables will not be modified and only default view will be seen on a new browser window.
+
+
+
+
+
+### Default Plugins
+
+Below some default plugins: `timeago`, `upbat`, `direction` and `delta`.
+
+
+
+
+
+Hovering the mouse on (computer) or touching (touch screen) some plugins will give you additional information.
+
+#### `delta` (BG Delta)
+
+Calculates and displays the change between the last 2 BG values. Delta shows a `*` if time difference is more than 5 minutes.
+
+#### `direction` (BG Direction)
+
+Displays the trend direction, the arrow change is only based on the difference from the current to the latest measurement.
+
+#### `upbat` (Uploader Battery)
+
+Displays the most recent battery status from the uploader phone(s) and bridge. Use these extended setting to adjust behavior:
+
+`UPBAT_ENABLE_ALERTS` (`false`) - Set to `true` to enable uploader battery alarms via Pushover and IFTTT.
+
+`UPBAT_WARN` (`30`) - Minimum battery percent to trigger warning.
+
+`UPBAT_URGENT` (`20`) - Minimum battery percent to trigger urgent alarm.
+
+
+
+#### `timeago` (Time Ago)
+
+Displays the time since last CGM entry. Use these extended setting to adjust behavior:
+
+`TIMEAGO_ENABLE_ALERTS` (`false`) - Set to `true` to enable stale data alarms via Pushover and IFTTT.
+
+`ALARM_TIMEAGO_WARN` (`on`) - possible values `on` or `off`
+
+`ALARM_TIMEAGO_WARN_MINS` (`15`) - minutes since the last reading to trigger a warning
+
+`ALARM_TIMEAGO_URGENT` (`on`) - possible values `on` or `off`
+
+`ALARM_TIMEAGO_URGENT_MINS` (`30`) - minutes since the last reading to trigger a urgent alarm
+
+
+
+#### `devicestatus` (Device Status)
+
+Used by `upbat` and other plugins to display device status info. Supports the `DEVICESTATUS_ADVANCED="true"` extended setting to send all device statuses to the client for retrospective use and to support other plugins.
+
+Example: `upbat` information using `devicestatus`.
+
+
+
+
+
+#### `errorcodes` (CGM Error Codes)
+
+Generates alarms for CGM codes `9` (hourglass) and `10` (???).
+
+Use extended settings to adjust what errorcodes trigger notifications and alarms:
+
+- `ERRORCODES_INFO` (`1 2 3 4 5 6 7 8`) - By default the needs calibration (blood drop) and other codes below 9 generate an info level notification, set to a space separate list of number or `off` to disable
+
+- `ERRORCODES_WARN` (`off`) - By default there are no warning configured, set to a space separate list of numbers or `off` to disable
+
+- `ERRORCODES_URGENT` (`9 10`) - By default the hourglass and ??? generate an urgent alarm, set to a space separate list of numbers or `off` to disable
+
+
+
+#### `ar2` (AR2 Forecasting)
+
+Generates alarms based on forecasted values.
+
+- Enabled by default if no thresholds are set **OR** `ALARM_TYPES` includes `predict`.
+ - You can permanently disable AR2 setting the `SHOW_FORECAST` variable to `false` (or removing `ar2` if you use it for `openaps` or `loop`).
+
+- `AR2` forecasting display can be enabled/disabled from `... `
+- Use extended settings to adjust AR2 behavior:
+ - `AR2_CONE_FACTOR` (`2`) - to adjust size of cone, use `0` for a single line.
+
+
+
+
+
+#### `simplealarms` (Simple BG Alarms)
+
+- Uses `BG_HIGH`, `BG_TARGET_TOP`, `BG_TARGET_BOTTOM`, `BG_LOW` thresholds to generate alarms.
+
+ Simple alarms are enabled by default if one of the `BG_HIGH`, `BG_TARGET_TOP`, `BG_TARGET_BOTTOM`, `BG_LOW` thresholds is set or `ALARM_TYPES` includes `simple`.
+
+ You'll find the plugin in the drawer menu. You can change thresholds in `Profile editor`.
+
+ You can click the loudspeaker icon to test the alarms volume or to snooze an active alarm. If you want to use sound alarms, you should click the icon to enable playback at least once after opening your Nightscout page in order to allow the browser to play it.
+
+
+
+
+
+#### `profile` (Treatment Profile)
+
+Add a link in the drawer menu to [Profile Editor](/nightscout/profile_editor/) and allows to enter treatment profile settings. Also uses the extended setting:
+
+- `PROFILE_HISTORY` (`off`) - possible values `on` or `off`. Enable/disable NS ability to keep history of your profiles (still experimental)
+- `PROFILE_MULTIPLE` (`off`) - possible values `on` or `off`. Enable/disable NS ability to handle and switch between multiple treatment profiles
+
+More variables of your profile will be used by Nightscout plugins like treatments, see below or [here](https://github.com/nightscout/cgm-remote-monitor#treatment-profile).
+
+
+
+
+
+#### `dbsize` (Database Size)
+
+Show size of Nightscout Database, as a percentage of declared available space or in MiB.
+
+
+
+
+
+Many deployments of Nightscout use free tier of MongoDB Atlas on Heroku, which is limited in size to 512MiB. After some time, as volume of stored data grows, it may happen that this limit is reached and system is unable to store new data. This plugin provides pill that indicates size of Database and shows (when configured) alarms regarding reaching space limit.
+
+```{admonition} IMPORTANT
+This plugin can only check how much space database already takes, *but cannot infer* max size available on server for it. To have correct alarms and realistic percentage, `DBSIZE_MAX` need to be properly set - according to your own mongoDB hosting configuration.
+```
+
+**NOTE:** This plugin rely on db.stats() for reporting *logical* size of database, which may be different than *physical* size of database on server. It may work for free tier of MongoDB on Atlas, since it calculate quota according to logical size too, but may fail for other hostings or self-hosted database with quota based on physical size.
+
+**NOTE:** MongoDB Atlas quota is for **all** databases in cluster, while each instance will get only size of **its own database only**. It is ok when you only have **one** database in cluster (most common scenario) but will not work for multiple parallel databases. In such case, spliting known quota equally beetween databases and setting `DBSIZE_MAX` to that fraction may help, but wont be precise.
+
+All sizes are expressed as integers, in *Mebibytes* `1 MiB == 1024 KiB == 1024*1024 B`
+
+Extended settings available:
+
+- `DBSIZE_MAX` (`496`) - Maximal allowed size of database on your mongoDB server, in MiB. You need to adjust that value to match your database hosting limits - default value is for standard Heroku mongoDB free tier.
+- `DBSIZE_WARN_PERCENTAGE` (`60`) - Threshold to show first warning about database size. When database reach this percentage of `DBSIZE_MAX` size - pill will show size in yellow.
+- `DBSIZE_URGENT_PERCENTAGE` (`75`) - Threshold to show urgent warning about database size. When database reach this percentage of `DBSIZE_MAX` size, it is urgent to do backup and clean up old data. At this percentage info pill turns red.
+- `DBSIZE_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications about database size.
+- `DBSIZE_IN_MIB` (`false`) - Set to `true` to display size of database in MiB-s instead of default percentage.
+
+
+
+------
+
+### Advanced Plugins:
+
+#### `careportal` (Careportal)
+
+An optional form to enter treatments.
+
+Care Portal is an important plugin that gives access to the `Log a treatment` interface. Unlock it entering your API secret with the lock icon top right, then use the `+` icon to log a treatment. More information [here](/nightscout/discover.md#add-a-treatment-careportal).
+
+
+
+
+
+#### `boluscalc` (Bolus Wizard)
+
+Bolus Wizard plugin gives access to the `Bolus Wizard` interface. You can access it with the calculator icon top right.
+
+
+
+
+
+#### `food` (Custom Foods)
+
+Custom Foods enabled by the variable `food` allows to to customize your food database and adds a `Food Editor` entry in the menu.
+
+
+
+
+
+#### `rawbg` (Raw BG)
+
+Calculates BG using sensor and calibration records from and displays an alternate BG values and noise levels. Defaults that can be adjusted with extended setting. Raw BG will only display if your sensor provides this data, your bridge device transfers it and your uploader sends it to Nightscout.
+
+- `DISPLAY`(`unsmoothed`) - Allows the user to control which algorithm is used to calculate the displayed raw BG values using the most recent calibration record.
+
+ - `unfiltered` - Raw BG is calculated by applying the calibration to the glucose record's unfiltered value.
+
+ - `filtered` - Raw BG is calculated by applying the calibration to the glucose record's filtered value. The glucose record's filtered values are generally produced by the CGM by a running average of the unfiltered values to produce a smoothed value when the sensor noise is high.
+
+ - `unsmoothed` - Raw BG is calculated by first finding the ratio of the calculated filtered value (the same value calculated by the `filtered` setting) to the reported glucose value. The displayed raw BG value is calculated by dividing the calculated unfiltered value (the same value calculated by the `unfiltered` setting) by the ratio. The effect is to exaggerate changes in trend direction so the trend changes are more noticeable to the user. This is the legacy raw BG calculation algorithm.
+
+
+
+
+
+#### `iob` (Insulin-on-Board) - `cob` (Carbs-on-Board)
+
+
+
+
+
+#### `iob` (Insulin-on-Board)
+
+Adds the IOB pill visualization in the client and calculates values that used by other plugins. Uses treatments with insulin doses and the `dia` and `sens` fields from the treatment profile.
+
+#### `cob` (Carbs-on-Board)
+
+Adds the COB pill visualization in the client and calculates values that used by other plugins. Uses treatments with carb doses and the `carbs_hr`, `carbratio`, and `sens` fields from the treatment profile.
+
+When you enter the information with the Care Portal or Nightscout receives if from the uploader, you can see remaining insulin on board and carbs.
+
+
+
+#### `bwp` (Bolus Wizard Preview)
+
+This plugin in intended for the purpose of automatically snoozing alarms when the CGM indicates high blood sugar but there is also insulin on board (IOB) and secondly, alerting to user that it might be beneficial to measure the blood sugar using a glucometer and dosing insulin as calculated by the pump or instructed by trained medicare professionals. ***The values provided by the plugin are provided as a reference based on CGM data and insulin sensitivity you have configured, and are not intended to be used as a reference for bolus calculation.*** The plugin calculates the bolus amount when above your target, generates alarms when you should consider checking and bolusing, and snoozes alarms when there is enough IOB to cover a high BG. Uses the results of the `iob` plugin and `sens`, `target_high`, and `target_low` fields from the [treatment profile](/nightscout/profile_editor/). Defaults that can be adjusted with extended settings
+
+- `BWP_WARN` (`0.50`) - If `BWP` is > `BWP_WARN` a warning alarm will be triggered.
+- `BWP_URGENT` (`1.00`) - If `BWP` is > `BWP_URGENT` an urgent alarm will be triggered.
+- `BWP_SNOOZE_MINS` (`10`) - minutes to snooze when there is enough IOB to cover a high BG.
+- `BWP_SNOOZE` - (`0.10`) If BG is higher then the `target_high` and `BWP` < `BWP_SNOOZE` alarms will be snoozed for `BWP_SNOOZE_MINS`.
+
+
+
+
+
+#### Age pills
+
+
+
+
+
+#### `cage` (Cannula Age)
+
+Calculates the number of hours since the last `Site Change` treatment that was recorded.
+
+- `CAGE_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications to remind you of upcoming cannula change.
+- `CAGE_INFO` (`44`) - If time since last `Site Change` matches `CAGE_INFO`, user will be warned of upcoming cannula change
+- `CAGE_WARN` (`48`) - If time since last `Site Change` matches `CAGE_WARN`, user will be alarmed to to change the cannula
+- `CAGE_URGENT` (`72`) - If time since last `Site Change` matches `CAGE_URGENT`, user will be issued a persistent warning of overdue change.
+- `CAGE_DISPLAY` (`hours`) - Possible values are `hours` or `days`. If `days` is selected and age of canula is greater than 24h number is displayed in days and hours
+
+#### `sage` (Sensor Age)
+
+Calculates the number of days and hours since the last `Sensor Start` and `Sensor Change` treatment that was recorded.
+
+- `SAGE_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications to remind you of upcoming sensor change.
+- `SAGE_INFO` (`144`) - If time since last sensor event matches `SAGE_INFO`, user will be warned of upcoming sensor change
+- `SAGE_WARN` (`164`) - If time since last sensor event matches `SAGE_WARN`, user will be alarmed to to change/restart the sensor
+- `SAGE_URGENT` (`166`) - If time since last sensor event matches `SAGE_URGENT`, user will be issued a persistent warning of overdue change.
+
+#### `iage` (Insulin Age)
+
+Calculates the number of days and hours since the last `Insulin Change` treatment that was recorded.
+
+- `IAGE_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications to remind you of upcoming insulin reservoir change.
+- `IAGE_INFO` (`44`) - If time since last `Insulin Change` matches `IAGE_INFO`, user will be warned of upcoming insulin reservoir change
+- `IAGE_WARN` (`48`) - If time since last `Insulin Change` matches `IAGE_WARN`, user will be alarmed to to change the insulin reservoir
+- `IAGE_URGENT` (`72`) - If time since last `Insulin Change` matches `IAGE_URGENT`, user will be issued a persistent warning of overdue change.
+
+#### `bage` (Battery Age)
+
+Calculates the number of days and hours since the last `Pump Battery Change` treatment that was recorded.
+
+- `BAGE_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications to remind you of upcoming pump battery change.
+
+- `BAGE_DISPLAY` (`days`) - Set to `hours` to display time since last `Pump Battery Change` in hours only.
+
+- `BAGE_INFO` (`312`) - If time since last `Pump Battery Change` matches `BAGE_INFO` hours, user will be warned of upcoming pump battery change (default of 312 hours is 13 days).
+
+- `BAGE_WARN` (`336`) - If time since last `Pump Battery Change` matches `BAGE_WARN` hours, user will be alarmed to to change the pump battery (default of 336 hours is 14 days).
+
+- `BAGE_URGENT` (`360`) - If time since last `Pump Battery Change` matches `BAGE_URGENT` hours, user will be issued a persistent warning of overdue change (default of 360 hours is 15 days).
+
+
+
+#### `treatmentnotify` (Treatment Notifications)
+
+Generates notifications when a treatment has been entered and snoozes alarms minutes after a treatment. Default snooze is 10 minutes, and can be set using the `TREATMENTNOTIFY_SNOOZE_MINS` extended setting.
+
+
+
+#### `basal` (Basal Profile)
+
+
+
+
+
+Adds the Basal pill visualization to display the basal rate for the current time. Also enables the `bwp` plugin to calculate correction temp basal suggestions. Uses the `basal` field from the [treatment profile](https://github.com/nightscout/cgm-remote-monitor#treatment-profile). Also uses the extended settings:
+
+- `BASAL_RENDER` (`none`)
+
+Possible values are `none`,
+
+`default`,
+
+
+
+or `icicle` (inverted)
+
+
+
+
+
+#### `bridge` (Share2Nightscout bridge)
+
+Glucose reading directly from the Dexcom Share service, uses these extended settings (***** mandatory):
+
+- `BRIDGE_USER_NAME` - Your username for the Share service. *****
+- `BRIDGE_PASSWORD` - Your password for the Share service. *****
+- `BRIDGE_INTERVAL` (`150000` *2.5 minutes*) - The time (in milliseconds) to wait between each update.
+- `BRIDGE_MAX_COUNT` (`1`) - The number of records to attempt to fetch per update.
+- `BRIDGE_FIRST_FETCH_COUNT` (`3`) - Changes max count during the very first update only.
+- `BRIDGE_MAX_FAILURES` (`3`) - How many failures before giving up.
+- `BRIDGE_MINUTES` (`1400`) - The time window to search for new data per update (the default value is one day in minutes).
+- `BRIDGE_SERVER` (`US`) - Set to `US` to fetch data from Dexcom servers in the US. Set to (`EU`) to fetch from non US servers instead. *****
+
+- `OBSCURED` (`bridge`) - Obscure data source when using `bridge` uploader.
+- `OBSCURE_DEVICE_PROVENANCE` (`dexcom-dont-own-my-body-data`) - Self explanatory.
+
+
+
+#### `mmconnect` (MiniMed Connect bridge)
+
+```{warning}
+This plugin is **NOT** functional with 7xx pumps do not enable it.
+```
+
+Transfer real-time MiniMed Connect data from the Medtronic CareLink server into Nightscout ([read more](https://github.com/nightscout/minimed-connect-to-nightscout)) (***** mandatory) with the following extended settings:
+
+- `MMCONNECT_USER_NAME` - Your user name for CareLink Connect. *****
+- `MMCONNECT_PASSWORD` - Your password for CareLink Connect. *****
+- `MMCONNECT_INTERVAL` (`60000` *1 minute*) - Number of milliseconds to wait between requests to the CareLink server.
+- `MMCONNECT_MAX_RETRY_DURATION` (`32`) - Maximum number of total seconds to spend retrying failed requests before giving up.
+- `MMCONNECT_SGV_LIMIT` (`24`) - Maximum number of recent sensor glucose values to send to Nightscout on each request.
+- `MMCONNECT_VERBOSE` - Set this to "true" to log CareLink request information to the console.
+- `MMCONNECT_STORE_RAW_DATA` - Set this to "true" to store raw data returned from CareLink as `type: "carelink_raw"` database entries (useful for development).
+- `MMCONNECT_SERVER` - Set this to `EU` if you're using the European Medtronic services *****
+
+
+
+#### `pump` (Pump Monitoring)
+
+
+
+
+
+Generic Pump Monitoring for OpenAPS, MiniMed Connect, RileyLink, t:slim, ...
+
+- Requires `DEVICESTATUS_ADVANCED="true"` to be set
+- `PUMP_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications for Pump battery and reservoir.
+- `PUMP_WARN_ON_SUSPEND` (`false`) - Set to `true` to get an alarm when the pump is suspended.
+- `PUMP_FIELDS` (`reservoir battery`) - The fields to display by default. Any of the following fields: `reservoir`, `battery`, `clock`, `status`, and `device`
+- `PUMP_RETRO_FIELDS` (`reservoir battery clock`) - The fields to display in retro mode. Any of the above fields.
+- `PUMP_WARN_CLOCK` (`30`) - The number of minutes ago that needs to be exceed before an alert is triggered.
+- `PUMP_URGENT_CLOCK` (`60`) - The number of minutes ago that needs to be exceed before an urgent alarm is triggered.
+- `PUMP_WARN_RES` (`10`) - The number of units remaining, a warning will be triggered when dropping below this threshold.
+- `PUMP_URGENT_RES` (`5`) - The number of units remaining, an urgent alarm will be triggered when dropping below this threshold.
+- `PUMP_WARN_BATT_P` (`30`) - The % of the pump battery remaining, a warning will be triggered when dropping below this threshold.
+- `PUMP_URGENT_BATT_P` (`20`) - The % of the pump battery remaining, an urgent alarm will be triggered when dropping below this threshold.
+- `PUMP_WARN_BATT_V` (`1.35`) - The voltage (if percent isn't available) of the pump battery, a warning will be triggered when dropping below this threshold.
+- `PUMP_URGENT_BATT_V` (`1.30`) - The voltage (if percent isn't available) of the pump battery, an urgent alarm will be triggered when dropping below this threshold.
+
+
+
+------
+
+#### `openaps` (OpenAPS)
+
+
+
+
+
+Integrated OpenAPS loop monitoring, uses these extended setting:
+
+- Requires `DEVICESTATUS_ADVANCED="true"` to be set
+- `OPENAPS_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications when OpenAPS isn't looping. If OpenAPS is going to offline for a period of time, you can add an `OpenAPS Offline` event for the expected duration from Careportal to avoid getting alerts.
+- `OPENAPS_WARN` (`30`) - The number of minutes since the last loop that needs to be exceed before an alert is triggered
+- `OPENAPS_URGENT` (`60`) - The number of minutes since the last loop that needs to be exceed before an urgent alarm is triggered
+- `OPENAPS_FIELDS` (`status-symbol status-label iob meal-assist rssi`) - The fields to display by default. Any of the following fields: `status-symbol`, `status-label`, `iob`, `meal-assist`, `freq`, and `rssi`
+- `OPENAPS_RETRO_FIELDS` (`status-symbol status-label iob meal-assist rssi`) - The fields to display in retro mode. Any of the above fields.
+- `OPENAPS_PRED_IOB_COLOR` (`#1e88e5`) - The color to use for IOB prediction lines. Colors can be in `#RRGGBB` format, but [other CSS color units](https://www.w3.org/TR/css-color-3/#colorunits) may be used as well.
+- `OPENAPS_PRED_COB_COLOR` (`#FB8C00`) - The color to use for COB prediction lines. Same format as above.
+- `OPENAPS_PRED_ACOB_COLOR` (`#FB8C00`) - The color to use for ACOB prediction lines. Same format as above.
+- `OPENAPS_PRED_ZT_COLOR` (`#00d2d2`) - The color to use for ZT prediction lines. Same format as above.
+- `OPENAPS_PRED_UAM_COLOR` (`#c9bd60`) - The color to use for UAM prediction lines. Same format as above.
+- `OPENAPS_COLOR_PREDICTION_LINES` (`true`) - Enables / disables the colored lines vs the classic purple color.
+
+Also see [Pushover](https://github.com/nightscout/cgm-remote-monitor#pushover) and [IFTTT Maker](https://github.com/nightscout/cgm-remote-monitor#ifttt-maker).
+
+
+
+------
+
+#### `loop` (Loop)
+
+
+
+
+
+iOS Loop app monitoring, uses these extended settings:
+
+- Requires `DEVICESTATUS_ADVANCED="true"` to be set
+- `LOOP_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications when Loop isn't looping.
+- `LOOP_WARN` (`30`) - The number of minutes since the last loop that needs to be exceeded before an alert is triggered
+- `LOOP_URGENT` (`60`) - The number of minutes since the last loop that needs to be exceeded before an urgent alarm is triggered
+- Add `loop` to `SHOW_FORECAST` to show forecasted BG.
+
+For remote overrides, the following extended settings must be configured:
+
+- `LOOP_APNS_KEY` - Apple Push Notifications service (APNs) Key, created in the Apple Developer website.
+- `LOOP_APNS_KEY_ID` - The Key ID for the above key.
+- `LOOP_DEVELOPER_TEAM_ID` - Your Apple developer team ID.
+- `LOOP_PUSH_SERVER_ENVIRONMENT` - (optional) Set this to `production` if you are using a provisioning profile that specifies production aps-environment, such as when distributing builds via TestFlight.
+
+
+
+#### `override` (Override Mode)
+
+Additional monitoring for DIY automated insulin delivery systems to display real-time overrides such as Eating Soon or Exercise Mode:
+
+- Requires `DEVICESTATUS_ADVANCED="true"` to be set
+
+
+
+#### `xdripjs` (xDrip-js)
+
+Integrated xDrip-js monitoring, uses these extended settings:
+
+- Requires `DEVICESTATUS_ADVANCED="true"` to be set
+
+- `XDRIPJS_ENABLE_ALERTS` (`false`) - Set to `true` to enable notifications when CGM state is not OK or battery voltages fall below threshold.
+
+- `XDRIPJS_STATE_NOTIFY_INTRVL` (`0.5`) - Set to number of hours between CGM state notifications
+
+- `XDRIPJS_WARN_BAT_V` (`300`) - The voltage of either transmitter battery, a warning will be triggered when dropping below this threshold.
+
+
+
+#### `alexa` (Amazon Alexa)
+
+Integration with Amazon Alexa, [detailed setup instructions](https://github.com/nightscout/cgm-remote-monitor/blob/master/docs/plugins/alexa-plugin.md)
+
+
+
+#### `googlehome` (Google Home/DialogFlow)
+
+Integration with Google Home (via DialogFlow), [detailed setup instructions](https://github.com/nightscout/cgm-remote-monitor/blob/master/docs/plugins/googlehome-plugin.md)
+
+
+
+#### `speech` (Speech)
+
+Speech synthesis plugin. When enabled, speaks out the blood glucose values, IOB and alarms. Note you have to set the LANGUAGE setting on the server to get all translated alarms.
+
+
+
+#### `cors` (CORS)
+
+Enabled [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) so other websites can make request to your Nightscout site, uses these extended settings:
+
+- `CORS_ALLOW_ORIGIN` (`*`) - The list of sites that are allow to make requests
+
+
+
+------
+
+## Extended Settings
+
+Some plugins support additional configuration using extra environment variables. These are prefixed with the name of the plugin and a `_`. For example setting `MYPLUGIN_EXAMPLE_VALUE=1234` would make `extendedSettings.exampleValue` available to the `MYPLUGIN` plugin.
+
+Plugins only have access to their own extended settings, all the extended settings of client plugins will be sent to the browser.
+
+- `DEVICESTATUS_ADVANCED` (`true`) - Defaults to true. Users who only have a single device uploading data to Nightscout can set this to false to reduce the data use of the site.
+- `DEVICESTATUS_DAYS` (`1`) - Defaults to 1, can optionally be set to 2. Users can use this to show 48 hours of device status data for in retro mode, rather than the default 24 hours. Setting this value to 2 will roughly double the bandwidth usage of nightscout, so users with a data cap may not want to update this setting.
+
+
+
+### [Pushover](/nightscout/pushover)
+
+In addition to the normal web based alarms, there is also support for [Pushover](https://pushover.net/) based alarms and notifications.
+
+To get started install the Pushover application on your iOS or Android device and create an account.
+
+Using that account login to [Pushover](https://pushover.net/), in the top left you’ll see your User Key, you’ll need this plus an application API Token/Key to complete this setup.
+
+You’ll need to [Create a Pushover Application](https://pushover.net/apps/build). You only need to set the Application name, you can ignore all the other settings, but setting an Icon is a nice touch. Maybe you'd like to use [this one](https://raw.githubusercontent.com/nightscout/cgm-remote-monitor/master/static/images/large.png)?
+
+Pushover is configured using the following Environment Variables:
+
+```
+* `ENABLE` - `pushover` should be added to the list of plugin, for example: `ENABLE="pushover"`.
+* `PUSHOVER_API_TOKEN` - Used to enable pushover notifications, this token is specific to the application you create from in [Pushover](https://pushover.net/), ***[additional pushover information](#pushover)*** below.
+* `PUSHOVER_USER_KEY` - Your Pushover user key, can be found in the top left of the [Pushover](https://pushover.net/) site, this can also be a pushover delivery group key to send to a group rather than just a single user. This also supports a space delimited list of keys. To disable `INFO` level pushes set this to `off`.
+* `PUSHOVER_ALARM_KEY` - An optional Pushover user/group key, will be used for system wide alarms (level > `WARN`). If not defined this will fallback to `PUSHOVER_USER_KEY`. A possible use for this is sending important messages and alarms to a CWD that you don't want to send all notification too. This also support a space delimited list of keys. To disable Alarm pushes set this to `off`.
+* `PUSHOVER_ANNOUNCEMENT_KEY` - An optional Pushover user/group key, will be used for system wide user generated announcements. If not defined this will fallback to `PUSHOVER_USER_KEY` or `PUSHOVER_ALARM_KEY`. This also support a space delimited list of keys. To disable Announcement pushes set this to `off`.
+* `BASE_URL` - Used for pushover callbacks, usually the URL of your Nightscout site, use https when possible.
+* `API_SECRET` - Used for signing the pushover callback request for acknowledgments.
+
+If you never want to get info level notifications (treatments) use `PUSHOVER_USER_KEY="off"`
+If you never want to get an alarm via pushover use `PUSHOVER_ALARM_KEY="off"`
+If you never want to get an announcement via pushover use `PUSHOVER_ANNOUNCEMENT_KEY="off"`
+
+If only `PUSHOVER_USER_KEY` is set it will be used for all info notifications, alarms, and announcements
+
+For testing/development try [localtunnel](http://localtunnel.me/).
+```
+
+
+
+### [IFTTT Maker](/nightscout/ifttt)
+
+In addition to the normal web based alarms, and pushover, there is also integration for [IFTTT Webhooks](https://ifttt.com/maker_webhooks).
+
+With Maker you are able to integrate with all the other [IFTTT Services](https://ifttt.com/services). For example you can send a tweet when there is an alarm, change the color of hue light, send an email, send and sms, and so much more.
+
+1. Setup IFTTT account: [login](https://ifttt.com/login) or [create an account](https://ifttt.com/join)
+2. Follow the [Detailed IFTTT setup Instructions](https://github.com/nightscout/cgm-remote-monitor/blob/master/docs/plugins/maker-setup.md)
+3. Configure Nightscout by setting these webpage environment variables:
+
+- `ENABLE` - `maker` should be added to the list of plugins, for example: `ENABLE="maker"`.
+- `MAKER_KEY` - Set this to your secret key (see [[Detailed Instructions](https://github.com/nightscout/cgm-remote-monitor/blob/master/docs/plugins/maker-setup.md) ) `MAKER_KEY="abcMyExampleabc123defjt1DeNSiftttmak-XQb69p"` This also supports a space delimited list of keys.
+- `MAKER_ANNOUNCEMENT_KEY` - An optional Maker key, will be used for system wide user generated announcements. If not defined this will fallback to `MAKER_KEY`. A possible use for this is sending important messages and alarms to another device that you don't want to send all notification too. This also support a space delimited list of keys.
+
+Plugins can create custom events, but all events sent to IFTTT webhooks will be prefixed with `ns-`. The core events are:
+
+- `ns-event` - This event is sent to the maker service for all alarms and notifications. This is good catch all event for general logging.
+- `ns-allclear` - This event is sent to the maker service when an alarm has been acknowledged or when the server starts up without triggering any alarms. For example, you could use this event to turn a light to green.
+- `ns-info` - Plugins that generate notifications at the info level will cause this event to also be triggered. It will be sent in addition to `ns-event`.
+- `ns-warning` - Alarms at the warning level with cause this event to also be triggered. It will be sent in addition to `ns-event`.
+- `ns-urgent` - Alarms at the urgent level with cause this event to also be triggered. It will be sent in addition to `ns-event`.
+- see the [full list of events](https://github.com/nightscout/cgm-remote-monitor/blob/master/docs/plugins/maker-setup.md#events)
+
+
+
+### Treatment Profile
+
+Some of the [plugins](#plugins) make use of a treatment profile that can be edited using the [Profile Editor](/nightscout/profile_editor/).
+
+Treatment Profile Fields:
+
+- `timezone` (Time Zone) - time zone local to the patient. *Should be set.*
+- `units` (Profile Units) - blood glucose units used in the profile, either "mg/dl" or "mmol"
+- `dia` (Insulin duration) - value should be the duration of insulin action to use in calculating how much insulin is left active. Defaults to 3 hours.
+- `carbs_hr` (Carbs per Hour) - The number of carbs that are processed per hour, for more information see [#DIYPS](http://diyps.org/2014/05/29/determining-your-carbohydrate-absorption-rate-diyps-lessons-learned/).
+- `carbratio` (Carb Ratio) - grams per unit of insulin.
+- `sens` (Insulin sensitivity) How much one unit of insulin will normally lower blood glucose.
+- `basal` The basal rate set on the pump.
+- `target_high` - Upper target for correction boluses.
+- `target_low` - Lower target for correction boluses.
diff --git a/_sources/nightscout/stringhelp.md.txt b/_sources/nightscout/stringhelp.md.txt
new file mode 100644
index 00000000..f7916ff1
--- /dev/null
+++ b/_sources/nightscout/stringhelp.md.txt
@@ -0,0 +1,8 @@
+---
+orphan: true
+---
+
+
+
+
+
diff --git a/_sources/nightscout/tokens.md.txt b/_sources/nightscout/tokens.md.txt
new file mode 100644
index 00000000..165b55b0
--- /dev/null
+++ b/_sources/nightscout/tokens.md.txt
@@ -0,0 +1,79 @@
+---
+orphan: true
+---
+
+***Note: authentication tokens are also called access tokens***
+
+```{admonition} Changing API_SECRET
+If you change your [`API_SECRET`](api-secret) all your tokens will change. Make sure you update your devices and send the new token link to those you allowed to access your Nightscout
+```
+
+To access the Authentication options, click the settings panel (three horizontal bars in the top right) in your website and select Admin Tools. The Authentication options are at the top of the Admin page. (Note: you must be logged in with your `API SECRET` to access these tools.)
+
+
+
+
+
+You will see several predefined roles:
+
+
+
+
+
+### Roles
+
+- **`admin`**: full access
+- **`careportal`**: can view the site and make CarePortal/treatment entries
+- **`readable`**: read-only access; no ability to make CarePortal/treatment entries. This user CAN see reports and profile information.
+- **`denied`**: no access (this role only works if the `AUTH_DEFAULT_ROLES` setting is also `denied`. You can’t have a site that is readable to everyone and create a “denied” token for a specific user.)
+- **`devicestatus-upload`**: used by devices
+
+```{hint}
+There is currently no way to limit a user so that he cannot view the Reports section if he has access to the site. Time/date-based roles are not currently possible.
+```
+
+
+
+### Create a Token
+
+- Click the “Add New Subject” button.
+
+
+
+
+
+- Fill in the name of the subject and the “role” you are giving this subject (from the list of roles shown above). Note you should only grant the `readable` role for users who do not need to save or edit data in Nightscout. For example, you might want to share the site to a school nurse, but not have him able edit the data.
+
+
+
+- An `admin` token is necessary for AAPS to upload using the API V3.
+
+
+
+
+
+- Click save.
+- The token will be shown. You can use it in two different ways:
+ - Copy the token URL (right-click on it in the browser and select the option to copy the link address) and provide it to the user (e.g., paste it into an email). If the user enters the entire URL (with token), the token will be in effect.
+ - Copy the token string (in the example below `school-a595d5f0aeff64c0`) and use it for authentication at site opening, instead of the API secret (Nightscout minimum version 14.1.0 required).
+
+
+
+
+
+You can also add the token to the site URL to authenticate using a token. Your site link with token will look like this:
+
+`https://yoursitename.yourplatform.com/?token=school-a595d5f0aeff64c0`
+
+Anybody with this link can use your Nightscout with the role defined for this token.
+
+```{hint}
+If the user copies only your core URL into a browser, and your site is readable by default, the token will be bypassed. (Possible strategies to ensure the user puts the role-based URL into a browser include using a [tinyurl](https://tinyur.com/app) or [bit.ly](https://bitly.com).)
+```
+
+- You can edit a subject by clicking the edit icon, making changes, and saving.
+- You can delete a subject by clicking the red **`X`** icon to remove the subject from the list.
+
+See [how to setup your downloaders (followers)](/nightscout/downloaders) with a secured site.
+
+
\ No newline at end of file
diff --git a/_sources/nightscout/ubuntu.md.txt b/_sources/nightscout/ubuntu.md.txt
new file mode 100644
index 00000000..39c9205a
--- /dev/null
+++ b/_sources/nightscout/ubuntu.md.txt
@@ -0,0 +1,8 @@
+---
+orphan: true
+---
+
+
+
+
+
diff --git a/_sources/nightscout/wearable.md.txt b/_sources/nightscout/wearable.md.txt
new file mode 100644
index 00000000..794e6aca
--- /dev/null
+++ b/_sources/nightscout/wearable.md.txt
@@ -0,0 +1,252 @@
+# Nightscout on your Watch
+
+
+
+## Pebble Smartwatches
+
+
+
+Pebble smartwatch use is a historic milestone of CGM in the Cloud. Pebble has been bought by Fitbit in 2016 and necessary resources have moved to archives and [rebble.io](https://rebble.io/). Pebble support is still maintained in Loop, AndroidAPS, FreeAPS and xDrip+.
+
+You still can find the Pebble app for iOS in the [Apple Store](https://apps.apple.com/us/app/pebble/id957997620). For Android you need to download it from [APKMirror](https://www.apkmirror.com/apk/pebble-technology-corp/pebble/pebble-4-4-2-1405-62d45d7d7-endframe-release/pebble-4-4-2-1405-62d45d7d7-endframe-android-apk-download/) or [APKPure](https://apkpure.com/it/pebble/com.getpebble.android.basalt).
+
+For authentication and getting the watchfaces, the original server closed so you'll need to register with [Rebble](https://auth.rebble.io/auth/).
+
+You'll find Nightscout watchfaces [here](https://apps.rebble.io/en_US/search/watchfaces/1). Search for Nightscout, CGM, ...
+
+Configure the watchface with your Nightscout site URL.
+
+
+
+### [urchin](https://github.com/mddub/urchin-cgm)
+
+A Pebble watchface to view data from a continuous glucose monitor in graph format.
+
+
+
+If you want to use your Pebble with Loop look [here](https://loopkit.github.io/loopdocs/nightscout/pebble/), for AndroidAPS [here](https://androidaps.readthedocs.io/en/latest/EN/Configuration/Watchfaces.html#pebble) and FreeAPS [here](https://github.com/mddub/pancreabble).
+
+
+
+### [xDrip+](https://github.com/NightscoutFoundation/xDrip/releases)
+
+Enable Pebble Integration in Smartwatch features.
+
+
+
+
+
+You can answer no to default watchface install so that you will be able to select another one. You can then decide to install or not the snooze control.
+
+
+
+
+
+## [Android Wear OS smartwatches](https://wearos.google.com/#hands-free-help)
+
+With an Android smartphone.
+
+````{tab-set}
+
+:::{tab-item} Android Wear 1
+- Recommended: Install an old version of Android Wear on your phone (search APKMirror for example: Android Wear 2.9.0.185084575.gms) and pair your watch. Make sure to allow GPS and Wear OS access to position on the watch. Allow Wear OS to run in background on your phone.
+
+***Note:If you installed Wear OS, you will need to manually update the watch Google Play Services see [here](https://androidaps.readthedocs.io/en/latest/EN/Usage/SonySW3.html).***
+
+ - Once your smartwatch Google Play Service has been updated to a version above 9.x you can safely update Android Wear to Wear OS.
+ - Change the watchface to match your app (in Wear OS or on your watch).
+:::
+
+:::{tab-item} Android Wear 2
+- Install [Wear OS](https://play.google.com/store/apps/details?id=com.google.android.wearable.app) on your phone and pair your watch. Make sure to allow GPS and Wear OS access to position on the watch. Allow Wear OS to run in background on your phone.
+
+- [Install](https://support.google.com/wearos/answer/7314014?hl=en) your app wear extension from the smartwatch Google Play store, selecting the apps installed on your phone.*Note: Newer versions of Wear OS do not support this feature anymore, use [Wear Installer](https://youtu.be/8HsfWPTFGQI) or Use [GeminiMan Wear OS Manager](https://play.google.com/store/apps/details?id=com.geminiman.wearosmanager) or [Easy Fire Tools](https://play.google.com/store/apps/details?id=de.agondev.easyfiretools).*
+
+- Change the watchface to match your app (in Wear OS or on your watch).
+:::
+
+:::{tab-item} Android Wear 3
+- Install [Wear OS](https://play.google.com/store/apps/details?id=com.google.android.wearable.app) on your phone and pair your watch. Make sure to allow GPS and Wear OS access to position on the watch. Allow Wear OS to run in background on your phone.
+
+- Use [Wear Installer](https://youtu.be/8HsfWPTFGQI) or Use [GeminiMan Wear OS Manager](https://play.google.com/store/apps/details?id=com.geminiman.wearosmanager) or [Easy Fire Tools](https://play.google.com/store/apps/details?id=de.agondev.easyfiretools).
+
+- Change the watchface to match your app (in Wear OS or on your watch).
+:::
+
+
+
+````
+
+
+
+### [xDrip+](https://github.com/NightscoutFoundation/xDrip/releases)
+
+Enable Android Wear Integration to send xDrip+ BG to the smartwatch. Do not enable neither Collection nor Force Collection.
+
+
+
+Full xDrip+ wear documentation [here](https://github.com/jamorham/xDrip-plus/blob/master/Documentation/WatchGuide.md).
+
+*NB: you can also use [Tasker](#xdrip-with-tasker).*
+
+### [AndroidAPS](https://androidaps.readthedocs.io/en/latest/EN/Installing-AndroidAPS/Building-APK.html)
+
+For AndroidAPS [here](https://androidaps.readthedocs.io/en/latest/EN/Configuration/Watchfaces.html#aaps-on-wear-os-smartwatch).
+
+### [Glimp](https://play.google.com/store/apps/details?id=it.ct.glicemia)
+
+Select your Wearable device and enable the Glimp watchface.
+
+
+
+### [NightWear](https://github.com/rahim/nightwear)
+
+NightWear is a minimal Wear OS watch face and complication available in the [Google Play Store](https://play.google.com/store/apps/details?id=im.rah.nightwear) directly from your watch.
+
+It uses Wear's standalone app support, so requires no companion app installed on the phone, or no phone at all as long as the watch has an internet connection. This also means it's possible to display Nightscout data on a Google Wear OS watch paired with an Apple iPhone.
+
+
+
+## Amazfit Pace & Stratos
+
+### [xDrip+](https://github.com/NightscoutFoundation/xDrip/releases)
+
+- Install the [Amazfit watch app](https://play.google.com/store/apps/details?id=com.huami.watch.hmwatchmanager) on your phone.
+- Install the [Amazfit tool](https://forum.xda-developers.com/t/tool-pace-stratos-verge-tool-all-in-one-drivers-unlock-twrp-factory-image.3874802/) on a Windows PC.
+- Download the [widget](https://github.com/Klaus3d3/XdripWidgetForAmazfit-Klaus/releases) from the project author (Klaus3d3) GitHub [repository](https://github.com/Klaus3d3/XdripWidgetForAmazfit-Klaus).
+- OEM unlock and enable USB debug on the watch, run TOOL ALL IN ONE and click the APK Installer button, select the widget apk file and INSTALL it. Close the install window and click Reboot System.
+- In xDrip+, enable the Amazfit service and select the options you want to enable.
+
+
+
+*Original instructions [here](https://crazyinfo.de/2018/07/25/xdrip-smartwatch-widget-fuer-amazfit-pace-stratos).*
+
+
+
+## Xiaomi MiBand 2, 3, 4, 5 and 6
+
+## Amazfit Band 5, Bip, Bip Lite, Bip S and Bip S lite, T-Rex Pro
+
+## Amazfit GTR2, GTR2e, GTS2, GTS 2 mini, GTS2e, GTR42 and 47
+
+### xDrip+
+
+Follow Artem's instructions [here](https://bigdigital.home.blog/).
+
+
+
+## Apple Watch
+
+### [Nightguard](https://apps.apple.com/us/app/nightguard/id1116430352#?platform=appleWatch)
+
+Apple Watch series 3 and above.
+
+[GitHub](https://github.com/nightscout/nightguard)
+
+
+
+### [sugarmate](https://sugarmate.io/)
+
+```{admonition} Important limitation
+:class: warning
+**Sugarmate doesn't allow Nightscout as a data source if you included `bridge` in `ENABLE`.**
+If you need this data source: enable [obscuration](/nightscout/setup_variables.md#bridge-share2nightscout-bridge) variables.
+```
+
+You can setup sugarmate as a calendar complication to display Nightscout on your Apple watch.
+
+
+
+### [Gluco-Tracker](https://apps.apple.com/it/app/gluco-tracker/id1526976290?platform=appleWatch)
+
+
+
+### [Loop Follow](https://www.loopandlearn.org/loop-follow/)
+
+You can setup Loop Follow as a calendar complication to display Nightscout on your Apple watch.
+
+
+
+## Fitbit
+
+### [Nightscout Monitor](https://gallery.fitbit.com/details/eaed806d-9ff5-4aa9-a2c8-518f1f852f5a)
+
+Ionic/Sense/Versa/Versa 2/Versa 3/Versa Lite
+
+[Repository](https://github.com/sulkaharo/nsfitbit)
+
+
+
+### [Glance](https://gallery.fitbit.com/details/7b5d9822-7e8e-41f9-a2a7-e823548c001c)
+
+Ionic/Sense/Versa/Versa 2/Versa 3/Versa 4/Versa Lite
+
+[Web site](https://glancewatchface.com/)
+
+
+
+### [Sentinel](https://gallery.fitbit.com/developer/b50ac7f5-b932-441a-be18-e258b17c736b)
+
+Ionic/Sense/Versa/Versa 2/Versa Lite
+
+Facebook group: [Sentinel](https://www.facebook.com/groups/3185325128159614)
+
+
+
+### [Marclock](https://gallery.fitbit.com/details/9eacf714-5b23-40c8-9621-ded74bd9edf9)
+
+Ionic/Sense/Versa/Versa 2/Versa Lite
+
+[Instructions](https://github.com/cramis1/Marclock-with-CGM-weather/blob/master/README.md)
+
+
+
+### Analog watchfaces
+
+#### [Analog CGM](https://gallery.fitbit.com/details/4d7b46b1-aaba-49b4-aa10-183321014dd3)
+
+#### [Orbits NS](https://gallery.fitbit.com/details/44de5c81-b77c-4f90-baa8-38f3e3d28695)
+
+#### [Radial CGM](https://gallery.fitbit.com/details/0173730e-5381-4495-bc6e-6ec93c8df029)
+
+Ionic/Versa/Versa 2/Versa Lite/Versa 3/Sense
+
+
+
+## Samsung Gear Smartwatches
+
+### xDrip+ with Tasker
+
+*Note: also available for Android Wear devices*
+
+[Instructions](https://github.com/FreDiabetics/xDrip--Tasker-Tizen-Watchface-Integration/blob/master/README.md)
+
+
+
+### [G-Watch app](https://play.google.com/store/apps/details?id=sk.trupici.g_watch)
+
+Facebook group: [G-Watch App](https://www.facebook.com/gwatchapp)
+
+
+
+## Garmin Smartwatches and Computers
+
+By [Phimby](https://apps.garmin.com/en-US/developer/74d80f40-f80a-45c2-b934-321cc86f9dac/apps)
+
+By [Horsetooth](https://apps.garmin.com/en-US/developer/e985e9ec-bcf6-4aef-bfe9-77c1c93fc854/apps)
+
+By [andreas-may](https://apps.garmin.com/en-US/developer/f9420c47-810f-47ac-a7dd-9fa7b8ecd22d/apps)
+
+By [Fredrik_S](https://apps.garmin.com/en-US/developer/c3842ca7-a645-4758-b9ed-4ee6f8e3abec/apps)
+
+By [John_](https://apps.garmin.com/en-US/developer/b2d30711-2708-4f3a-8e83-009c16d07081/apps)
+
+By [floheigl](https://apps.garmin.com/en-US/apps/488ffa72-5994-4d0f-90ff-3eeb99f3ea41)
+
+
+
+## Karoo/Karoo 2
+
+By [Henry Haspden](https://github.com/haspden/INFLITE-TYPE-ONE-Hammerhead-CGM#readme)
+
+
diff --git a/_sources/nightscout/xdripteam.md.txt b/_sources/nightscout/xdripteam.md.txt
new file mode 100644
index 00000000..6b87e85f
--- /dev/null
+++ b/_sources/nightscout/xdripteam.md.txt
@@ -0,0 +1,8 @@
+---
+orphan: true
+---
+
+
+
+
+
\ No newline at end of file
diff --git a/_sources/pages/configure/index.md.txt b/_sources/pages/configure/index.md.txt
new file mode 100644
index 00000000..06b8aa02
--- /dev/null
+++ b/_sources/pages/configure/index.md.txt
@@ -0,0 +1,456 @@
+---
+orphan: true
+---
+```{warning}
+Historical pages
+```
+
+ 
| [Update](/update/update/) |
+| 
| [Update](/update/update/) |
+| 
| [Update](/update/update/) |
+| 
| Google Cloud xDrip+Continue [here](https://navid200.github.io/xDrip/docs/Nightscout/update_nightscout.html) |
+| 
| [Update](/update/update/) |
+| 
| [Update](/update/update/) |
+| 
| [Update](/update/update/) |
diff --git a/_sources/translate.md.txt b/_sources/translate.md.txt
new file mode 100644
index 00000000..0c679203
--- /dev/null
+++ b/_sources/translate.md.txt
@@ -0,0 +1,54 @@
+# Google Translate links
+
+
+
+- Click the leaf top left in your Atlas account. Look at the `Project Name` you wanted to use when creating your new cluster, it shouldn't contain a cluster yet (like the example below, I tried to create a new Nightscout site but there is already a cluster inside the project I wanted to use). You can't have two clusters in a free project. Click your `Project Name`.
+- This should not happen in normal conditions. Before deleting a cluster, check it doesn't contain your data!
+
+
+
+- Click on `Collections` in the cluster you selected.
+
+
+
+- Click on `entries`
+
+
+
+- In the case there is data, like in the example below, **don't use this cluster**. Leave it like this and create a new one.
+
+
+
+- **If there no data**, you can safely delete it.
+
+
+
+- In this cluster you want to delete click `...` then `Terminate`
+
+
+
+- Copy the cluster name to confirm then click `Terminate`
+
+
+
+- Wait until the operation completes.
+- You can now use this project name to create a new site.
+
+
+
+## Meet your connection string
+
+For technical details look [here](https://docs.mongodb.com/manual/reference/connection-string/#mongodb-uri).
+
+A typical mLab migrated string will look like this:
+
+`mongodb+srv://heroku_0v50k8rf:ddfsjcpfu8fcoj9n6dueabfd5u@cluster0.g03wh.mongodb.net/ `
+`heroku_0v50k8rf?retryWrites=true&w=majority`
+
+A typical new string created with Atlas will look like this:
+
+`mongodb+srv://johndoe:V3ry53cr3t@cluster0.a01bc.mongodb.net/myCGMiC?retryWrites=true&w=majority`
+
+- It will start by `mongodb+srv://` with `mongodb` a **standard prefix** for a connection string, and `+srv` adding a security layer.
+
+- After `://` you'll find your **database username**, that is not your Atlas account username. In the examples above `heroku_0v50k8rf` or `johndoe`.
+
+- Following the username, a separator `:` and your **database password** that is not your Atlas account password. In the examples above a typical 26 characters password created automatically with the mLab add-on `ddfsjcpfu8fcoj9n6dueabfd5u` and a user created password `V3ry53cr3t`.
+
+- Following the password, a separator `@` then the **host name** that was provided by Atlas after you created you cluster. typically it will look like `cluster0.`*`a1b2c3`*`.mongodb.net`
+
+- [Optional] After the host name and the separator `/` you'll see your Nightscout **database name**. If you migrated from mLab it will be identical to your database username (unless you modified it). If you created your Atlas cluster it will be the one you decided. In the examples above `heroku_0v50k8rf` or `myCGMiC`.
+
+- Another separator `?` and you'll see two options: `retryWrites=true&w=majority`
+
+
+
+## Unable to connect to Mongo
+
+
+
+Common reasons:
+
+- The database is not available. If you don't have a database yet, create a new one.
+ If you do have a database, check it's functional then restart your web app:
+
+```{tab-set}
+
+:::{tab-item} Heroku
+[Restart all dynos](/troubleshoot/heroku.md#restart-all-dynos)
+:::
+
+:::{tab-item} Railway
+[Restart your web app](/troubleshoot/railway.md#restart-your-app)
+:::
+
+:::{tab-item} Azure
+[Restart app](/troubleshoot/azure.md#restart-app)
+:::
+
+:::{tab-item} Northflank
+[Restart](/troubleshoot/northflank.md#restart)
+:::
+
+:::{tab-item} Fly.io
+[Restart your app](/troubleshoot/fly.io.md#restart-your-app)
+:::
+
+:::{tab-item} Render
+[Restart service](/troubleshoot/render.md#restart-service)
+:::
+
+```
+
+- Your Atlas connection string is incorrect. Check [here](#bad-connection-string).
+
+### MongoDB paused
+
+- If you haven't been using Nightscout for a while but it was working before, check the database didn't go to sleep mode. If it did, select `Resume` to restart it.
+- Once done:
+
+```{tab-set}
+
+:::{tab-item} Heroku
+[Restart all dynos](/troubleshoot/heroku.md#restart-all-dynos)
+:::
+
+:::{tab-item} Railway
+[Restart your web app](/troubleshoot/railway.md#restart-your-app)
+:::
+
+:::{tab-item} Azure
+[Restart app](/troubleshoot/azure.md#restart-app)
+:::
+
+:::{tab-item} Northflank
+[Restart](/troubleshoot/northflank.md#restart)
+:::
+
+:::{tab-item} Fly.io
+[Restart your app](/troubleshoot/fly.io.md#restart-your-app)
+:::
+
+:::{tab-item} Render
+[Restart service](/troubleshoot/render.md#restart-service)
+:::
+
+```
+
+
+
+
+
+If you see this message
+
+
+
+- [Update to latest version](/vendors/github/update/) and come back after you have a more accurate error message.
+
+
+
+## MongoDB in read only mode
+
+If you see this message:
+
+
+
+- Verify your database is not read only, else click `Edit`
+
+
+
+- Change the permissions to `Atlas Admin` and `Update User`
+
+
+
+- Once done:
+
+```{tab-set}
+
+:::{tab-item} Heroku
+[Restart all dynos](/troubleshoot/heroku.md#restart-all-dynos)
+:::
+
+:::{tab-item} Railway
+[Restart your web app](/troubleshoot/railway.md#restart-your-app)
+:::
+
+:::{tab-item} Azure
+[Restart app](/troubleshoot/azure.md#restart-app)
+:::
+
+:::{tab-item} Northflank
+[Restart](/troubleshoot/northflank.md#restart)
+:::
+
+:::{tab-item} Fly.io
+[Restart your app](/troubleshoot/fly.io.md#restart-your-app)
+:::
+
+:::{tab-item} Render
+[Restart service](/troubleshoot/render.md#restart-service)
+:::
+
+```
+
+
+
+## `MONGODB_URI` missing
+
+If you see this message:
+
+
+
+- If you don't have a database yet, create a new one.
+- It might be a transient error in MongoDB Atlas, try to restartyour web app:
+
+```{tab-set}
+
+:::{tab-item} Heroku
+[Restart all dynos](/troubleshoot/heroku.md#restart-all-dynos)
+:::
+
+:::{tab-item} Railway
+[Restart your web app](/troubleshoot/railway.md#restart-your-app)
+:::
+
+:::{tab-item} Azure
+[Restart app](/troubleshoot/azure.md#restart-app)
+:::
+
+:::{tab-item} Northflank
+[Restart](/troubleshoot/northflank.md#restart)
+:::
+
+:::{tab-item} Fly.io
+[Restart your app](/troubleshoot/fly.io.md#restart-your-app)
+:::
+
+:::{tab-item} Render
+[Restart service](/troubleshoot/render.md#restart-service)
+:::
+
+```
+
+- Check your [database is not full](#database-full)!
+- If your Nightscout was still functional after November 11th 2020, continue [below](#bad-connection-string) to recover:
+
+
+
+## Generic Unable to connect to Mongo
+
+If you see this message:
+
+
+
+- Check you authorized all IPs to access your Atlas database:
+- Open your Atlas cluster and select your Nightscout project, then `Network access`
+
+
+
+- If you see an IP (in red above) instead of 0.0.0.0/0 click `Edit` select `ALLOW ACCESS FROM ANYWHERE` then `Confirm`.
+
+
+
+- Once done:
+
+```{tab-set}
+
+:::{tab-item} Heroku
+[Restart all dynos](/troubleshoot/heroku.md#restart-all-dynos)
+:::
+
+:::{tab-item} Railway
+[Restart your web app](/troubleshoot/railway.md#restart-your-app)
+:::
+
+:::{tab-item} Azure
+[Restart app](/troubleshoot/azure.md#restart-app)
+:::
+
+:::{tab-item} Northflank
+[Restart](/troubleshoot/northflank.md#restart)
+:::
+
+:::{tab-item} Fly.io
+[Restart your app](/troubleshoot/fly.io.md#restart-your-app)
+:::
+
+:::{tab-item} Render
+[Restart service](/troubleshoot/render.md#restart-service)
+:::
+
+```
+
+
+
+## Bad connection string
+
+If you see this message:
+
+
+
+
+
+- [Edit your Nightscout configuration](/nightscout/setup_variables) and search for a variable called `MONGODB_URI` or `MONGO_CONNECTION`.
+
+- If you find none, go [here](#recover-your-connection-string).
+
+```{admonition} MONGODB_URI or MONGO_CONNECTION
+:class: warning
+There should be at least one and only one of them, not both.
+```
+
+If you migrated from mLab Heroku add-on it is usually `MONGO_CONNECTION`
+
+if you deployed a brand new Nightscout it should be `MONGODB_URI`
+
+- Verify it is looking like this:
+
+`mongodb+srv://atlasusername:atlaspassword@cluster0.zzzzz.mongodb.net/dbname?retryWrites=true&w=majority`
+
+Note that your `atlasusername`, `atlaspassword` and `dbname` will be different from the example above.
+
+- Paste the string in the box below:
+
+
+
+
+- Click the `Analyze` text below:
+
+
+
+
+
+
+
+If you've just created a new site, try to use [this help page](/_static/stringhelp.html) to verify or recreate it.
+
+
+
+If you're still in trouble continue below:
+
+
+
+## Recover your connection string
+
+If you've tried several times to deploy or migrate, you might end-up with many useless items in your accounts. At this point, you could benefit doing some cleanup in order to identify the correct Atlas database you want to connect to. Consider [cleanup](#cleanup) before continuing.
+
+
+
+a) Go to your MongDB account. Log in if necessary [https://cloud.mongodb.com/](https://cloud.mongodb.com/)
+
+b) Click `Connect` below your cluster name (in the example below `Cluster0`, but it might have another name)
+
+
+
+
+
+c) Click `Connect your application`
+
+
+
+
+
+d) A new view opens, in `(2) Add your connection string into your application code` you will find your `MONGODB_URI` or `MONGO_CONNECTION` string.
+
+Click `Copy` then `Close`
+
+
+
+
+
+e) Paste it into a place where you can edit the text (i.e. a Word or a Notepad document).
+
+Edit your string so that you add the database user password after the database user info. You defined them during your MongoDB Atlas database creation, when you reached [step **e)**](/vendors/mongodb/atlas/).
+
+Here’s an example of how the string is built up (`myFirstDatabase` might not show, this is normal):
+
+`mongodb+srv://` `nightscout` `:`**`
+
+
+
+- At the end of the line, click `Edit`
+
+
+
+
+
+- In `Password` click `Edit Password`
+
+```{hint}
+*Take a look at the top of this view, after `Edit User` you can see your database user name before `@`. Check it's matching the one in your connection string.*
+```
+
+
+
+
+
+- If you forgot your password invent a new one (use only letters and numbers: no special characters) or better: use `Autogenerate Secure Password` and click `Copy`
+- Else make it the same than the one in your `MONGODB_URI` connection string variable
+
+
+
+
+
+- Click `Update User`
+
+
+
+
+
+- Make sure the password matches in your connection string variable `MONGODB_URI` or `MONGO_CONNECTION`
+
+
+
+## Database full
+
+Free databases like M0 Sandbox provided by Atlas will only hold a limited amount of data (512MB) and you will eventually need to manually cleanup. You can extend the capacity to 2 and 5GB paying for an M2 or M5 Shared cluster.
+
+**Note:** *If you consider paying for a database upgrade, also think about a [paid hosting service](/index.md#nightscout-as-a-service).*
+
+```{warning}
+Make sure your Nightscout site has `Database Size` enabled to monitor database capacity.
+In order to have the database size pill, add `dbsize` in the `ENABLE` variable.
+Look [here](/nightscout/setup_variables.md#dbsize-database-size) for more information on this plugin.
+```
+
+
+
+
+
+```{hint}
+Your database size might not decrease immediately (it might even increase temporarily) after you perform cleanup with Admin Tools (see below: Normal cleanup). Allow a few hours to see the effects. In the meantime your site should recover functionality.If your site keeps crashing, go ahead to emergency cleanup.
+```
+
+
+
+### Restart
+
+**Try to recover temporary access to Nightscout to perform normal cleanup:**
+
+```{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Heroku
+[Restart all dynos](/troubleshoot/heroku.md#restart-all-dynos)
+:::
+
+:::{tab-item} Railway
+[Restart your web app](/troubleshoot/railway.md#restart-your-app)
+:::
+
+:::{tab-item} Azure
+[Restart app](/troubleshoot/azure.md#restart-app)
+:::
+
+:::{tab-item} Northflank
+[Restart](/troubleshoot/northflank.md#restart)
+:::
+
+:::{tab-item} Fly.io
+[Restart your app](/troubleshoot/fly.io.md#restart-your-app)
+:::
+
+:::{tab-item} Render
+[Restart service](/troubleshoot/render.md#restart-service)
+:::
+
+:::{tab-item} Google Cloud
+The probability your database is full is very low, make sure you selected the maximum disk size for your compute engine. See [Here](https://navid200.github.io/xDrip/docs/Nightscout/FullDisk.html).
+:::
+
+:::{tab-item} Hosted services
+Contact your provider. The probability your database is full is virtually null.
+:::
+
+```
+
+### Normal cleanup
+
+You can cleanup (enter the number of days to keep) or delete your devices status (recommended as a first recovery action):
+
+
+
+Same for `Treatments`:
+
+
+
+And `Glucose entries`. If you are reluctant to lose historical data you should consider opting for a paid database solution or [hosted](/index.md#nightscout-as-a-service) Nightscout.
+
+
+
+If your Nightscout page doesn't open after restarting your app and you want to rule out a full database, you can try an emergency cleanup of the less important part of your Nightscout site: `devicestatus`.
+
+
+
+### Emergency cleanup
+
+- Log in [Atlas](https://account.mongodb.com/account/login)
+- Open your Nightscout database and select `Browse collections` in `Database`
+
+
+
+- Select the `devicestatus` collection and click the bin icon to delete it.
+
+- You will lose all device status history (battery, ..) but **you won't lose neither BG, treatments nor profiles**.
+
+
+
+- Write `devicestatus` in the box then click `Drop`
+
+
+
+
+- [Restart](#restart) your site and when it opens, consider again [cleanup](#normal-cleanup) from Admin Tools if your database size exceeds 80%.
+
+
+
+### Atlas database size verification
+
+- Log in [Atlas](https://account.mongodb.com/account/login)
+- Open your Nightscout database and select `Collections`
+
+
+
+
+
+- Click your database name (hidden left). Check the`DATABASE SIZE` is indeed close to or at the limit (512MB) then look at these three collections `Documents size`: `devicestatus`, `entries` and `treatments`.
+
+
+
+- Open Nightscout [`Admin tools`](/nightscout/discover.md#drawer-menu). If your site doesn't open jump to [Emergency cleanup](#emergency-cleanup).
+- Depending on the collection you identified above, choose which of the following you want to cleanup.
+
+
+
+## Reports slow loading or timeout
+
+Loopers might experience Nightscout taking an extremely long time or even timing out when creating reports due to the profiles collection database growing too big.
+
+Two solutions are available:
+
+1. Follow this video (set it full screen in 720p) to selectively delete profiles [https://www.youtube.com/watch?v=iipp0MfPKNQ](https://www.youtube.com/watch?v=iipp0MfPKNQ)
+2. Delete all profiles in Atlas
+
+Log in to Atlas [https://account.mongodb.com/account/login](https://account.mongodb.com/account/login)
+
+Select your cluster then `COLLECTIONS`
+
+
+
+
+
+Select the `profile` collection and click the bin icon to delete all profiles.
+
+
+
+
+
+Write `profile` in the box then click `Drop`
+
+
+
+
+
+Open your Nightscout and create a new profile (mind the time zone!), authenticate and save it.
+
+If you are using Loop, temporarily change a basal rate in Loop, and confirm your profiles now show up in Nightscout.
+
+
+
+## Data in the future
+
+First try to [remove future items with the Admin Tools](/nightscout/admin_tools.md#remove-future-items-from-database).
+
+If it doesn't give the expected result:
+
+- Check in [Atlas](https://account.mongodb.com/account/login)
+
+- Open your Nightscout cluster and select `Collections`
+
+
+
+
+
+- In `Entries` type `{date:-1}` and click `Find`
+
+
+
+
+
+- Delete the entries in the future (manually) with the bin icon
+
+
+
+
+
+## Cleanup
+
+It is very easy to get lost in Atlas.
+
+The structure from top to bottom is: Organization, Projects and Databases. You can have several organizations, each of them several projects and each of them several databases.
+
+```{hint}
+If you are deploying a brand new Nightscout make sure you have one organization, one project and one cluster created. No more no less.
+```
+
+If you want to cleanup Atlas, unless you don't have data, you must first find out which database contains your data. For this, start from `View All Organizations`:
+
+
+
+You can delete empty organizations (those without any project inside).
+
+
+
+Select the organization, then top left the cog wheel to go in `Settings`, then scroll down to `Delete Organization`: `Delete`.
+
+
+
+Deleting an organization without projects will not delete your data.
+
+
+
+------
+
+Once inside an organization, you will see its projects. You can safely delete projects without clusters.
+
+
+
+Deleting an empty project doesn't delete your Nightscout data.
+
+
+
+For non-empty projects continue reading before deciding to delete them.
+
+------
+
+You can then move to your project (select it) and check its database(s) selecting `COLLECTIONS`
+
+
+
+An empty project will look like below, and this is typically what you have before deploying Nightscout. Once Nightscout is deployed in a project, a new database will be created there.
+
+
+
+The database currently used by your Nightscout is the one specified in the connection string, in the example below `dbname`. Whenever you change the database name in the connection string, a new database will be created in your project.
+
+`mongodb+srv://atlasusername:atlaspassword@cluster0.zzzzz.mongodb.net/`**`dbname`**`?retryWrites=true&w=majority`
+
+There is usually one database for Nightscout, if there are several, select one and then the other(s) to understand which one contains your data. For this, select `entries`.
+
+
+
+A large database is most probably one you want to keep.
+
+
+
+You can safely delete empty databases (check the size first).
+
+
+
+```{warning}
+If you're not sure you're deleting the right database, just leave it.
+```
+
+Hover on the database name and click the bin icon. Confirm deletion by copying the database name and click `Drop`.
+
+
+
+If your database gets recreated after you deleted it this means your `MONGODB_URI` or `MONGO_CONNECTION` string is pointing to it.
+
+
+
+If you want to delete a non-empty Project you need to terminate all clusters belonging to it.
+
+
+
+```{warning}
+Terminating a cluster will delete all information and databases in this cluster!
+```
+
+Confirm with your cluster name and wait until shutdown is complete.
+
+
+
+You can then delete the empty project.
+
+
+
+## Backup your database
+
+```{admonition} Not a normal operation
+:class: warning
+Making a backup of your database is either a good idea or necessary if you want to migrate it to another database.
+This is not an easy operation and requires command line instructions using a computer.
+```
+
+### Install the database tools
+
+Follow [this link](https://www.mongodb.com/docs/database-tools/installation/installation/) to install the CLI tool on your computer.
+
+### Dump your database
+
+Get your `MONGODB_URI` handy to find the missing pieces (password and database name).
+
+Log in your MongoDB account [https://cloud.mongodb.com/](https://cloud.mongodb.com/).
+
+1. Select your organization
+2. Select your database
+3. In the advanced options menu, select `Command line tools`
+
+
+
+
+
+Scroll down to `Binary import and Export tools`, copy the `mongodump` command line.
+
+
+
+Paste the command line in a text editor.
+
+Look into your `MONGODB_URI` and replace `
+
+
+
+Open a command line utility (CMD, Terminal, ...) and make your way to the utility folder (if you don't want to include it in your system path).
+For example in Windows 64bits it's in `C:\Program Files\MongoDB\Tools\100\bin`.
+
+Copy and paste your `mongodump` command, run it.
+
+
+
+
+
+You will find the database dump in a subfolder called `dump` with your database name in a subfolder.
+
+
+
+
\ No newline at end of file
diff --git a/_sources/troubleshoot/azure.md.txt b/_sources/troubleshoot/azure.md.txt
new file mode 100644
index 00000000..3118b0b1
--- /dev/null
+++ b/_sources/troubleshoot/azure.md.txt
@@ -0,0 +1,36 @@
+# Troubleshoot Azure
+
+
+
+## Error 403
+
+This usually happens when you reach free credits limit.
+Make sure you have an active [Basic plan subscription](https://azure.microsoft.com/en-us/pricing/purchase-options/pay-as-you-go/). If you only used free services as specified in the installation guide, you shouldn't be billed.
+
+
+
+
+
+## Restart app
+
+Log in [Azure](https://portal.azure.com/#home) and select your App Service (`cgmitc` in the picture is an example, yours will have a different name).
+
+
+
+
+
+Click on Restart and confirm. Wait a few minutes until restart completes.
+
+
+
+
+
+## Billing occurred
+
+Make sure you didn't add technical support.
+
+Check [here](https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview) and click the link at the top of the page: Choose the right support plan.
+
+You should have a Basic support plan, that is free.
+
+
\ No newline at end of file
diff --git a/_sources/troubleshoot/cleanup.md.txt b/_sources/troubleshoot/cleanup.md.txt
new file mode 100644
index 00000000..97ec4d38
--- /dev/null
+++ b/_sources/troubleshoot/cleanup.md.txt
@@ -0,0 +1,38 @@
+---
+orphan: true
+---
+
+# Cleanup
+
+After unsuccessful attempts you might want to cleanup the various accounts to avoid confusion.
+
+If you're still trying to deploy your first Nightscout, ignore all data loss recommendations below.
+
+If you have a large amount of CGM data, be extra cautious when performing Atlas cleanup.
+
+
+
+## [GitHub](https://github.com/login)
+
+The most efficient way to cleanup GitHub and restart with an up-to-date Nightscout project is to [redeploy](/update/redeploy.md) it.
+
+You will then need to reconnect your repository to [Heroku](/troubleshoot/heroku.md#cannot-find-cgm-remote-monitor-in-heroku-item-cannot-be-retrieved) or [Railway](/troubleshoot/railway.md#reconnect-github-to-your-project).
+
+
+
+## [Heroku](https://id.heroku.com/)
+
+Look [here](/troubleshoot/heroku.md#cleanup).
+
+
+
+## [Atlas](https://account.mongodb.com/account/login)
+
+Look [here](/troubleshoot/atlas.md#cleanup).
+
+
+
+## [Railway](https://railway.app)
+
+Look [here](/troubleshoot/railway.md#cleanup).
+
diff --git a/_sources/troubleshoot/connection_string.md.txt b/_sources/troubleshoot/connection_string.md.txt
new file mode 100644
index 00000000..6ef2af92
--- /dev/null
+++ b/_sources/troubleshoot/connection_string.md.txt
@@ -0,0 +1,7 @@
+---
+orphan: true
+---
+
+# Connection string
+
+Moved [here](/troubleshoot/atlas.md#unable-to-connect-to-mongo).
\ No newline at end of file
diff --git a/_sources/troubleshoot/dexcom_bridge.md.txt b/_sources/troubleshoot/dexcom_bridge.md.txt
new file mode 100644
index 00000000..20947fb4
--- /dev/null
+++ b/_sources/troubleshoot/dexcom_bridge.md.txt
@@ -0,0 +1,159 @@
+# Troubleshoot Dexcom Share
+
+
+
+## Username and password
+
+Your Dexcom account is the one that identifies you to access all services: Store, Clarity and mobile apps. In order to make sure you're accessing the right account, log into Clarity to check your credentials are valid.
+
+For US account: [https://clarity.dexcom.com/](https://clarity.dexcom.com/)
+For all others: [https://clarity.dexcom.eu/](https://clarity.dexcom.eu/)
+
+
+
+In the case you have linked accounts, check you are using the right credentials for the profile you want to `bridge` to Nightscout.
+
+**Verify you actually have current data in this profile/account!** You want to put the username and password of the account that has CGM data in `BRIDGE`, this is usually the credentials you are using with the master phone (the one connected to the sensor).
+
+
+
+```{admonition} Password
+:class: tip
+Some people have had problems with their bridge connecting when their Dexcom passwords are entirely numeric. If you have connection issues in that case, try changing your password to something with a mix of numbers and letters.
+```
+
+```{admonition} Changing password
+:class: warning
+Before you decide to change your password, make sure to update your Nightscout variables accordingly and make sure you have recent data in Clarity before exiting maintenance mode.
+```
+
+
+
+## Username is an email
+
+Newly created Dexcom users do not have an username but only an email address.
+
+
+
+This can be an issue if you want to use `bridge` to have your data directly in Nightscout. Make sure you're using the [latest release](/update/update/) if you experience problems.
+
+Common symptoms are:
+
+- no data in Nightscout even with correct credentials
+- account locking once or more per day even with correct credentials
+
+
+
+## Username is a phone number
+
+New users might have the phone app setup with their phone number including country code and the symbol `+`. This is not supported by Nightscout. Continue below and create a dependent account with an alphanumerical username.
+
+
+
+## Obtaining a username
+
+Dependent accounts can have a username.
+
+
+
+You can create your Dexcom account and add dependent accounts for children, wife, ...
+
+Some dependent accounts with an email address can generate problems when trying to connect directly to Nightscout.
+
+
+
+## Account lock
+
+You can check if your account is locked by trying to log into Clarity.
+
+
+
+If you see this message, you must disable (enter an empty username for example) all devices and apps trying to get data from or push data into Dexcom share.
+
+In order to recover from an account lock, it is usually enough to wait for 10-15 minutes after you disabled all devices and apps trying to access the account with a wrong password.
+
+Do not forget any app or device!
+
+- Nightscout
+- Smartwatches apps
+- Sugarmate, Happy Bob, xDrip+,...
+- ...
+
+
+
+## Dexcom Share
+
+Make sure you have Dexcom Share turned ON in your Dexcom app. In the Dexcom app's main screen, find the triangle made of dots. If the dots are grey, you do not have Share turned on. Tap the triangle, and follow the directions to add a follower (yourself if you don't have someone else you'd like to invite) and turn on Share.
+
+
+
+
+
+If you are using a Dexcom system, and your data is not appearing in Nightscout, there are only a limited number of reasons for that. You should check your (1) Heroku settings and (2) Dexcom Share.
+
+NOTE: The #1 reason why BGs aren't showing is that you have mismatched password and user names in Heroku settings and Dexcom.
+
+### Verify your configuration
+
+Variables location will depend on the platform you use:
+
+````{tab-set}
+
+:::{tab-item} Heroku
+[**→ Here**](/vendors/heroku/new_user.md#editing-config-vars-in-heroku)
+:::
+
+:::{tab-item} Railway
+[**→ Here**](/vendors/railway/new_user.md#editing-variables-in-railway)
+:::
+
+:::{tab-item} Northflank
+[**→ Here**](/vendors/northflank/new_user.md#editing-variables-in-northflank)
+:::
+
+:::{tab-item} Azure
+[**→ Here**](/vendors/azure/new_user.md#editing-config-vars-in-azure)
+:::
+
+:::{tab-item} Fly.io
+[**→ Here**](editing-config-vars-in-fly-io)
+:::
+
+:::{tab-item} Google Cloud
+[**→ Here**](https://navid200.github.io/xDrip/docs/Nightscout/NS_Variables.html)
+:::
+
+````
+
+
+
+1. You must use the same `BRIDGE_PASSWORD` or `BRIDGE_USER_NAME` that your Dexcom mobile app is using.
+2. You must have `bridge` and `careportal` on the `ENABLE` line (you can have other values there...but don't forget these two).
+3. If you are outside the USA, you must add `BRIDGE_SERVER` set to `EU` in Heroku settings.
+4. Your `careportal` must be one word in the `ENABLE` line, sometimes autocorrect makes it two words.
+5. If using `mmol`, make sure you have spelled that value correctly in the `DISPLAY_UNITS`.
+
+
+
+### Authentication errors
+
+One thing that can happen if you have an incorrect Dexcom login/password in your Share account settings and/or in your Nightscout `BRIDGE` settings is that Dexcom will lock your account...and you won't see CGM data in Nightscout. If you notice your CGM readings disappeared, but everything else is flowing...
+Check your Heroku logs that are viewable by selecting `View Logs` from the drop-down menu underneath the `More` option.
+
+
+
+With Railway they are available selecting your app, then `Deployments` and `View Logs` at the end of the top (last) deployment line.
+
+
+
+
+
+Do your logs have "`SSO authentication errors`" like in the red box highlighted above? If you do, then:
+
+1. Delete your `BRIDGE` entries within Heroku settings. Don't delete the variables, just delete the values of `BRIDGE_PASSWORD` and `BRIDGE_USER_NAME`.
+2. Wait 15 minutes and then follow the directions below. It is important to wait 15 minutes: the reason you can't log in right now is that your Dexcom account has a temporary lock from the passwords in the step above being incorrect. The temporary lock will expire after 10-15 minutes of giving the account login a break from the incorrect logins. So, definitely wait or else you'll just keep prolonging the issue.
+
+```{hint} About your Bridge password and user name
+The most common error on initial Nightscout setups is that people incorrectly use an old account or an old password. To test your username and password, go to Dexcom's Clarity page (check [here for USA accounts](https://clarity.dexcom.com) and [here for the others](https://clarity.dexcom.eu)) and try logging in to your Dexcom account. If your account info isn't valid, or you don't see any data in your Clarity account... you need to figure out your actual credentials before moving ahead.
+```
+
diff --git a/_sources/troubleshoot/fly.io.md.txt b/_sources/troubleshoot/fly.io.md.txt
new file mode 100644
index 00000000..cfa0c2a6
--- /dev/null
+++ b/_sources/troubleshoot/fly.io.md.txt
@@ -0,0 +1,272 @@
+# Troubleshoot Fly.io
+
+
+
+```{warning}
+The web terminal feature was removed from Fly.io.
+You need a computer with flyctl.
+```
+
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer. You also need to [install git](https://git-scm.com/downloads) if you're using a Windows computer.
+
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+
+
+
+## Restart your app
+
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer.
+
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+
+- Log in Fly.io:
+
+`flyctl auth login`
+
+- Verify your Nightscout app name
+
+`flyctl app list`
+
+- Restart your app (replace `example-ns` by the name of your Nightscout app in Fly.io)
+
+`flyctl machine restart --app example-ns`
+
+
+
+(recover-fly-toml)=
+
+## Recover `fly.toml`
+
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer.
+
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+
+- Log in Fly.io:
+
+`flyctl auth login`
+
+- Verify your Nightscout app name
+
+`flyctl app list`
+
+- Copy your Nightscout app (replace `example-ns` with your own) configuration file `fly.toml`.
+
+`flyctl config save --app example-ns`
+
+- Keep this file in a safe place as you'll need it to redeploy or upgrade your Nightscout.
+
+
+
+## Cleanup
+
+After several failed attempts to deploy or migrate, you might need to delete some apps.
+
+Log into Fly.io [https://fly.io/app/sign-in](https://fly.io/app/sign-in) (GitHub recommended)
+
+
+
+In normal running condition you will see only two apps on your dashboard:
+The first one is your Nightscout site and the second one the builder (necessary).
+If you used the migration wizard you will see another builder (three apps).
+
+
+
+
+
+Clicking on your site you will see if it's healthy and running. This is where you go to open your site.
+
+
+
+
+
+### Delete an app
+
+Select an app from the dashboard. Then click `Settings`.
+Click `Delete app`.
+
+
+
+Confirm copying the app name below, then click `Yes, delete it`.
+
+
+
+You have deleted your app.
+
+If you delete the builder (like in the picture above) you won't be able to deploy anymore.
+
+
+
+### Delete your local repository
+
+#### If you deployed with your own computer.
+
+```{warning}
+Make a backup of the `fly.toml` file present in the `cgm-remote-monitor` folder!
+This is essential to make your site maintainable!
+```
+
+You can delete the `cgm-remote-monitor` folder on your computer and fork it again.
+
+Exit the folder before deleting it, in task manager end the `flyctl.exe` task.
+
+#### If you deployed from the web terminal.
+
+You don't have a local repository.
+
+
+
+## Downscale your app
+
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer.
+
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+
+
+
+March 31st 2023, apps deploy in V2 and V1 apps are automatically migrated too.
+This causes some issues as V2 automatically deploys in a more than one machine, your Nightscout site might not work correctly.
+
+Type the following command in the terminal (replace ***`example-ns`*** with your own app name):
+
+- Authenticate in Fly.io:
+
+
+`flyctl auth login`
+
+- Verify your Nightscout app name
+
+`flyctl app list`
+
+- Downscale your app:
+
+`flyctl scale --app `***`example-ns`***` count 1`
+
+
+
+- Your app should now only be running on one machine. Check [here](https://fly.io/dashboard/personal/machines).
+
+
+***Note:*** *the builder app is normal, it is stopped: don't worry about it.*
+
+
+
+
+
+## Obtain a free shared IP
+
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer.
+
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+
+
+
+Apps migrated from Heroku will use a dedicated IP billed $1.90/month.
+
+If you want to run your Nightscout site in Fly.io for free, you will need to release the IP and request a shared IP.
+
+Follow the instructions below. The IP `137.66.11.78` and the site name `example-ns` are examples, yours will be different. Use your own IP and site name.
+
+Open a browser and authenticate:
+
+`flyctl auth login`
+
+List the apps to see the name of your Nightscout project:
+
+`flyctl app list`
+
+```
+NAME OWNER STATUS PLATFORM LATEST DEPLOY
+example-ns personal deployed machines 2023-05-26T07:24:51Z
+```
+
+List the IPs used by your app (replace *`example-ns`* by your own):
+
+`flyctl ips list -a example-ns`
+
+```
+VERSION IP TYPE REGION CREATED AT
+v4 137.66.11.78 public global 2022-09-13T14:17:58Z
+v6 3b09:8280:1::3:723c public global 2022-09-13T14:18:00Z
+```
+
+Release the dedicated IP you found above (example: 137.66.11.78):
+
+`flyctl ips release 137.66.11.78 -a example-ns`
+
+```
+Released 137.66.11.78 from example-ns
+```
+
+Assign a shared IP to your Nightscout site:
+
+`flyctl ips allocate-v4 --shared -a example-ns`
+
+```
+v4 
+
+If you didn't upgrade Heroku to an Eco or Basic plan, you need to [create a new Nightscout site](/nightscout/new_user) and [recover your MongoDB Atlas connection string](/troubleshoot/atlas.md#recover-your-connection-string).
+
+If you just upgraded to an Eco or Basic plan, make sure you enabled the web app (that turned off when the Free plan was removed).
+
+
+
+If you just tried to deploy a new Nightscout site, something went wrong. [Cleanup](#cleanup) your Heroku apps and retry...
+
+
+
+## Application Error
+
+
+
+ [Update Nightscout to latest release](/update/update.md). It might not fix your issue but it will help find a solution.
+
+- Check your MongoDB Atlas [database is not full](/troubleshoot/atlas.md#database-full).
+- If you're creating a new Nightscout site, it might have failed because of a [wrong connection string](/troubleshoot/atlas.md#unable-to-connect-to-mongo).
+- If you don't see any good reason [restart all dynos](#restart-all-dynos).
+
+
+
+## A valid GitHub Directory could not be found.
+
+When trying to deploy a new Nightscout site, this message appears when clicking `Deploy to Heroku`.
+
+
+
+- Change browser and retry.
+
+
+
+(heroku-nogit)=
+
+## Cannot find cgm-remote-monitor in Heroku / No GitHub source visible
+
+When updating Nightscout, `cgm-remote-monitor` doesn't appear automatically in Heroku under your repository name.
+
+
+
+When updating Nightscout, your repository name doesn't appear in `Manual Deploy` so that you can't select the `master` branch.
+
+
+
+- `Disconnect` and re-`Connect` like this:
+
+
+
+
+
+- If it doesn't help try to re-authorize as explained below:
+
+
+
+## Cannot find cgm-remote-monitor in Heroku: Item cannot be retrieved
+
+When updating Nightscout, `cgm-remote-monitor` doesn't appear automatically in Heroku under your repository name and an error message appears when you try to connect to GitHub.
+
+
+
+- In Heroku, go to `Account Settings`
+
+
+
+- Select `Applications` and click `Re-authorize`
+
+
+
+- Click `Authorize GitHub` in the pop-up.
+- If it doesn't help, you can also try to `Revoke access`... before going back to Re-`Connect` your GitHub account. This is necessary if someone else did setup Nightscout for you and left his own GitHub connected to your Heroku account.
+
+
+
+## I can't log into Heroku
+
+If you lost your password use the [password reset option](https://id.heroku.com/account/password/reset).
+
+If you lost your authenticator use the recovery codes (that you hopefully saved when [securing your account)](/vendors/heroku/mfa).
+
+If you lost or don't have anymore access to the email you used to create your Heroku account you will need to deploy a new Nightscout site. You can use the same GitHub account and the same MongodB Atlas database you currently have but will have to use another Nightscout site name in Heroku as the current one is already in use. First [recover your connection string](/troubleshoot/atlas.md#recover-your-connection-string), and proceed to [creating a new Nightscout](/vendors/heroku/new_user/) **skipping Step 3**.
+
+
+
+## Restart all dynos
+
+- Log in Heroku, go to `Settings`, `More`, `Restart all dynos`.
+
+
+
+
+
+## Sleeping app
+
+Check you app didn't fall asleep:
+
+
+
+
+
+A sleeping app can be due to your Heroku Eco plan: a Basic plan makes the app never sleep. [https://www.heroku.com/pricing](https://www.heroku.com/pricing)
+
+Another reason for a sleeping app can be due to a failure to obtain data from Dexcom Share, check the logs to understand the reasons.
+
+
+
+## Cleanup
+
+If you experience issues during deployment you might end up with many apps. Make sure you keep the last one that was functional or [delete](#delete-an-app) all before attempting a new deployment. This will just make it easier to find which app you're trying to build. Keeping sleeping apps doesn't have any negative impact but no real advantage unless you do it on purpose.
+
+Make sure the app you're using for Nightscout is running on an Eco/Basic tier.
+
+If you're not convinced you want to delete an app, make sure to put it in maintenance mode to understand if you use it as the related Nightscout site will report offline for maintenance.
+
+
+
+### Maintenance mode
+
+Maintenance mode is useful to troubleshoot Dexcom and CareLink accounts locked and also if you need to modify several variables without having Nightscout restarting every change.
+
+You can also put your Nightscout in maintenance mode if you won't use it for an extended period of time.
+
+```{warning}
+**Putting your site in maintenance mode won't stop billing!**
+You also need to disable the web service for this.
+
+```
+
+Be aware that your MongoDB Atlas database might also go in sleep mode and you will need to [restart it manually](/troubleshoot/atlas.md#mongodb-paused).
+
+
+
+
+
+### Delete an app
+
+Deleting an Heroku app does **not** delete your Nightscout data, but you might want to write down your variables (definitely backup your connection string) if your site was functional before. Note that you can also rename an app (unless the name is already in use in heroku.com).
+
+
+
+To delete an app, select it and go to `Settings`, scroll down to `Delete App`
+
+
+
+Copy and paste your app name to confirm deletion,
+
+
+
+
+
+## Backup your site variables
+
+Having a copy of your variables is very important since some of them are vital to your site like MONGODB_URI and your access to it like API_SECRET.
+
+### Method 1 - Spreadsheet
+
+Log into [Heroku](https://dashboard.heroku.com/apps), select your app.
+Reveal your Heroku Nightscout app [Config Vars](/vendors/heroku/new_user.md#editing-config-vars-in-heroku) and copy all variables names and values in a spreadsheet.
+
+### Method 2 - Export
+
+Log into [Heroku](https://dashboard.heroku.com/apps), select your app.
+Click on the top right `More` button and select `Run console`.
+
+
+
+In the console command line type the command below, then click `Run`.
+
+```
+export `heroku config -s`
+```
+
+
+
+Wait until the command completes.
+
+
+
+Save the session: it contains all your variables and values (and a few useless things).
+
+
+
+Edit the file with a text editor and remove the first line `(bash: line 1: heroku: command not found)`.
+Using find and replace, get rid of all `declare -x`.
+Delete the following Heroku specific variables:
+
+`DYNO="run.6309"
+HOME="/app"
+MEMORY_AVAILABLE="512"
+NODE_ENV="production"
+NODE_HOME="/app/.heroku/node"
+OLDPWD
+PATH="/app/.heroku/node/bin:/app/.heroku/yarn/bin:/usr/local/bin:/usr/bin:/bin:/app/bin:/app/node_modules/.bin"
+PORT="6489"
+PS1="\\[\\033[01;34m\\]\\w\\[\\033[00m\\] \\[\\033[01;32m\\]\$ \\[\\033[00m\\]"
+PWD="/app"
+SHLVL="1"
+TERM="xterm-256color"
+WEB_CONCURRENCY="1"
+WEB_MEMORY="512"`
+
+```{warning}
+Save this file in a safe place.Call it `heroku.env` as it's your Heroku environment variables.
+```
+
+
+
+## Roll back Heroku
+
+
+
+Roll back can be really useful in case of mistakes and when awaiting bug fixes in minor releases.
+
+```{warning}
+You can only roll back to a version that was previously deployed to your Heroku app.
+```
+
+Heroku keeps history of variables modifications and previous deploys so that you can return to a previous state easily in the cases of a configuration mistake or a bad deploy (like a bugged version). When rolling back to a previous deploy keep in mind all variables modified in the mean time will return to the value they had at that time.
+
+Since the database is external to Heroku, it will not be impacted by a roll back.
+
+
+
+- Log into [Heroku](https://id.heroku.com/login).
+- Select your Nightscout app and go to `Activity`
+
+
+
+
+
+- You will see a list of events called `Activity Feed` and some indicated as possible roll-back points. Identify the last good situation and select `Roll back to here`
+
+
+
+
+
+- Identify and eventually write down the values of the variables that were changed in the meantime (arrows in the picture below) before selecting `Rollback`.
+
+
+
+
+
+Upon completion your Heroku will be returned to the state it was at the selected rollback point.
+
+You can use it like this or upgrade to the latest released version later on.
+
+
+
+- If you change your mind later you can rollback prior to your rollback and return to the starting point.
+
+
+
+
+
+## Stop using Heroku
+
+If you want to migrate your data, it is recommended that you do it **before** switching off your Heroku Nightscout.
+
+To stop using Heroku and suspend billing, you only need to switch off all apps like this:
+
+- [Log](https://id.heroku.com/login) into Heroku.
+- Select your app(s) in the dashboard.
+
+
+
+- In `Resources`, edit (pen icon) and turn off the `web` server switch.
+
+
+
+- Your Heroku Nightscout site will stop and **only the current month** will be billed.
+- You can keep your Heroku account and leave the credit card, once no app is active billing will stop.
+- Your data will not be deleted, make a copy of the `MONGODB_URI` variable if you want to reuse it with another platform, or migrate your database.
+- If you decide you will not use it anymore, once last billing has occurred, you can delete your app(s), credit card and Heroku account.
+
+
diff --git a/_sources/troubleshoot/northflank.md.txt b/_sources/troubleshoot/northflank.md.txt
new file mode 100644
index 00000000..5c95d32a
--- /dev/null
+++ b/_sources/troubleshoot/northflank.md.txt
@@ -0,0 +1,96 @@
+---
+orphan: true
+---
+
+# Troubleshoot Northflank
+
+
+
+## Site doesn't open after build
+
+`upstream connect error or disconnect/reset before headers. retried and the latest reset reason: remote connection failure, transport failure reason: delayed connect error: 111`
+
+You probably need to wait until the deploy is finished. Refresh the page after 5 minutes.
+
+
+
+## Restart
+
+a) [Log into Northflank](https://app.northflank.com/) and select your Nightscout `project`, then its `service`.
+
+
+
+
+
+b) Click `Rollout Restart` and confirm `Restart Service`.
+Wait until restart is complete with the cloud status `Running`.
+
+
+
+
+
+If your site crashes again shortly after, verify your [database is not full](/troubleshoot/atlas.md#database-full) if you use MongoDB Atlas.
+
+
+
+## Backup your site variables
+
+Having a copy of your variables is very important since some of them are vital to your site like MONGODB_URI and your access to it like API_SECRET.
+
+Open [Northflank](https://app.northflank.com/login) and login with your username or with GitHub.
+
+
+
+
+
+Select `Services ` then your Nightscout project.
+
+
+
+
+
+Select `Environment` then `Env`.
+
+
+
+
+
+Copy the contents of the `Environment variables` and paste it into a text editor.
+
+
+
+
+
+```{warning}
+Save this file in a safe place.Call it `northflank.env` as it's your Northflank environment variables.
+```
+
+
+
+## Restore your site variables
+
+You can use this method to restore Northflank variables (see above how to backup), but also to restore them from [Railway](/troubleshoot/railway.md#backup-your-site-variables) or [Heroku](/troubleshoot/heroku.md#method-2-export) if migrating (follow the platform name link to see how to export them).
+
+Open [Northflank](https://app.northflank.com/login) and login with your username or with GitHub.
+
+
+
+
+
+Select `Services ` then your Nightscout project.
+
+
+
+
+
+Select `Environment` then `Env`.
+
+
+
+
+
+Delete all contents, open your backup file (the .env you generated when doing backup) and copy/paste all in the editor area. Click `Update and restart` bottom right.
+
+
+
+
\ No newline at end of file
diff --git a/_sources/troubleshoot/railway.md.txt b/_sources/troubleshoot/railway.md.txt
new file mode 100644
index 00000000..50b33069
--- /dev/null
+++ b/_sources/troubleshoot/railway.md.txt
@@ -0,0 +1,244 @@
+# Troubleshoot Railway
+
+
+
+## Nothing here
+
+
+
+```{warning}
+The free plan has been removed Jul 3rd for new users and Aug 1st for existing users.
+```
+
+
+
+It has been running fine for the first 200/500 hours and now it's gone. Even the project disappeared in Railway.
+
+
+
+This is usually because you need a Developer plan to run your Nightscout app in Railway.
+
+
+
+## Restart your app
+
+a) Open the [Railway Dashboard](https://railway.app/dashboard) and select your project then your app.
+
+
+
+
+
+b) In your `web` deployments select the current one (top of the list) and in the three dots menu on the right, `Restart`.
+
+
+
+
+
+b) Confirm Restart. Wait a moment and check your Nightscout site state clicking the URL.
+If your site crashes again shortly after, verify your [database is not full](/troubleshoot/atlas.md#database-full) if you use MongoDB Atlas.
+
+
+
+
+
+## Reconnect GitHub to your project
+
+a) Open [Railway](https://railway.app) and click `login`. Login with GitHub.
+
+
+
+
+
+
+
+b) Select your Nightscout project.
+
+
+
+
+
+c) Select your web app.
+
+
+
+
+
+d) Select `Settings` and scroll down to `Service`.
+Disconnect your `Source Repo` with the cross at the end of the line.
+
+
+
+
+
+e) Confirm `Disconnect`.
+
+
+
+
+
+f) Select `Connect Repo`.
+
+
+
+You should be able to select your GitHub `cgm-remote-monitor` repository.
+You have now successfully reconnected your GitHub project to Railway.
+If your GitHub repository `cgm-remote-monitor` was changed (updated for example), your Railway app will automatically redeploy.
+
+
+
+If you don't see the picture above: continue below.
+
+
+
+g) If you redeployed (deleted and recreated) `cgm-remote-monitor` in GitHub select `Configure GitHub app`.
+
+
+
+
+
+h) Select your GitHub account.
+
+
+
+
+
+i) Click `Only Select repositories` and from the `Select Repositories button` choose your `cgm-remote-monitor` Nightscout project. Click then `Install & Authorize`.
+
+
+
+You have now successfully reconnected your GitHub project to Railway.
+If your GitHub repository `cgm-remote-monitor` was changed (updated for example), your Railway app will automatically redeploy.
+
+
+
+## Cleanup
+
+After several deployment attempts your Railway account might show more than one app. Since there is a 5$ limit to hobby plan before increased billing, depending on how you use it, it is important to make sure you don't have useless apps wasting CPU time and memory.
+
+Open [Railway](https://railway.app) and click `login`. Login with GitHub.
+
+
+
+
+
+If you see more than one (or two if you have a local database) projects on your dashboard, you should delete those unused.
+
+
+
+
+
+### Empty projects
+
+You can safely delete empty projects (in red in the picture above).
+
+Select your project then click on `Settings`.
+
+
+
+
+
+Click on `Danger`.
+
+
+
+
+
+Then `Delete project`.
+
+
+
+
+
+Copy and paste the project name in the box below and click `Delete`.
+
+
+
+
+
+### Databases
+
+Before deleting a database you need to check it's empty.
+
+Click twice on the database project and select `Data`.
+
+This example below is not an empty database. You need to check it's not being used by Nightscout before deleting it.
+You can see data inside: `profile`, `devicestatus`, etc...
+
+
+
+
+
+This example below is empty, you can safely delete it (like shown above for an empty project).
+There is no data inside this database. When you pull down the `Database tab`, there is only `test` and it's empty.
+
+
+
+
+
+## Backup your site variables
+
+Having a copy of your variables is very important since some of them are vital to your site like MONGODB_URI and your access to it like API_SECRET.
+
+a) Open your [Railway](https://railway.app/dashboard) dashboard and select your Nightscout project.
+
+
+
+
+
+c) Select your web app and click on `Variables`.
+
+
+
+
+
+e) Click on `RAW Editor` top right
+
+
+
+
+
+f) Click on `Copy env` bottom left and paste all into a text editor.
+
+
+
+
+
+```{warning}
+Save this file in a safe place.Call it `railway.env` as it's your Railway environment variables.
+```
+
+
+
+## Restore your site variables
+
+You can use this method to restore Railway variables (see above how to backup), but also to restore them from [Northflank](/troubleshoot/northflank.md#backup-your-site-variables) or [Heroku](/troubleshoot/heroku.md#method-2-export) if migrating (follow the platform name link to see how to export them).
+
+a) Open your [Railway](https://railway.app/dashboard) dashboard and select your Nightscout project.
+
+
+
+
+
+c) Select your web app and click on `Variables`.
+
+
+
+
+
+e) Click on `RAW Editor` top right
+
+
+
+
+
+f) Delete all contents, open your backup file (the .env you generated when doing backup) and copy/paste all in the raw editor area. Click `Update variables` bottom right.
+
+
+
+
+
+g) If you see the message `Apply _ changes` top left, click the `Deploy` button and wait for your site to update.
+
+
+
+
diff --git a/_sources/troubleshoot/render.md.txt b/_sources/troubleshoot/render.md.txt
new file mode 100644
index 00000000..18dd81a8
--- /dev/null
+++ b/_sources/troubleshoot/render.md.txt
@@ -0,0 +1,62 @@
+# Troubleshoot Render
+
+
+
+## Restart service
+
+If your site is not responding (doesn't open), you can try to restart it.
+Mind it might only have fallen asleep and would need an uptime robot to stay awake.
+
+* Sign in [Render](https://dashboard.render.com/) with GitHub
+
+
+
+* Select your web service
+
+
+
+* In the `Dashboard`, open the `Manual Deploy` drop down menu and select `Restart service`.
+
+
+
+
+
+## Backup your site variables
+
+Having a copy of your variables is very important since some of them are vital to your site like MONGODB_URI and your access to it like API_SECRET.
+
+Unfortunately there is no automated way to export your variables in Render.
+
+Copy the values in a spreadsheet or create a `render.env` file, manually, using the format:
+
+`VARIABLE="value"`
+
+
+
+## Restore your site variables
+
+You can use this method to import Render variables from [Railway](/troubleshoot/railway.md#backup-your-site-variables) or [Heroku](/troubleshoot/heroku.md#method-2-export) if migrating (follow the platform name link to see how to export them).
+
+* Log in [Render](https://dashboard.render.com/)
+
+
+
+* Select your web service
+
+
+
+* Go to `Environment`, click on `Add from .env`.
+
+ 
+
+- Delete all contents, open your backup file (the .env you generated when doing backup) and copy/paste all in the editor area. Click `Add variables` bottom right.
+
+
+
+- Scroll down the list and trash all variables that don't have a value (they're not used)
+
+
+
+- Scroll to the bottom of the list and click `Save changes`. Wait until your site redeploys with the new variables.
+
+
\ No newline at end of file
diff --git a/_sources/troubleshoot/troublehoot.md.txt b/_sources/troubleshoot/troublehoot.md.txt
new file mode 100644
index 00000000..6fc728cb
--- /dev/null
+++ b/_sources/troubleshoot/troublehoot.md.txt
@@ -0,0 +1,9 @@
+---
+orphan: true
+---
+
+
+
+
+
+
diff --git a/_sources/troubleshoot/troubleshoot.md.txt b/_sources/troubleshoot/troubleshoot.md.txt
new file mode 100644
index 00000000..56bbf312
--- /dev/null
+++ b/_sources/troubleshoot/troubleshoot.md.txt
@@ -0,0 +1,197 @@
+# Troubleshooting Nightscout
+
+
+
+## Before troubleshooting
+
+1. **Check your email (maybe you missed an important announcement)**
+
+2. **Check your internet provider / SIM credit (can all devices browse internet?)**
+
+3. **Try another browser/computer (if building your Nightscout site)**
+
+
+
+## Overall third party services
+
+Check the services you're using are available
+
+| Vendor | Check here: |
+| ---------------------------------------------------------- | ------------------------------------------------------------ |
+| **Dexcom**Dexcom US account
Dexcom non-US account | [https://status.dexcom.com/](https://status.dexcom.com/)
[https://clarity.dexcom.com/](https://clarity.dexcom.com/)
[https://clarity.dexcom.eu/](https://clarity.dexcom.eu/) | +| Carelink US account
Carelink non-US account | [https://carelink.minimed.com/](https://carelink.minimed.com/)
[https://carelink.minimed.eu/app/login](https://carelink.minimed.eu/app/login) | +| GitHub | [https://www.githubstatus.com/](https://www.githubstatus.com/) | +| Heroku | [https://status.heroku.com/](https://status.heroku.com/) | +| Railway | [https://railway.instatus.com/](https://railway.instatus.com/) | +| MongoDB Atlas | [https://status.cloud.mongodb.com/](https://status.cloud.mongodb.com/) | +| Northflank | [https://status.northflank.com/](https://status.northflank.com/) | +| Azure | [https://azure.status.microsoft/](https://azure.status.microsoft/) | +| NS10BE | [https://ns.10be.de/en/status.html](https://ns.10be.de/en/status.html) | + + + +------ + +## Application crashed + +Not knowing if it's a permanent issue, first try to restart it... + +```{tab-set} + +:::{tab-item} Heroku +[Restart all dynos](/troubleshoot/heroku.md#restart-all-dynos) +::: + +:::{tab-item} Railway +[Restart your web app](/troubleshoot/railway.md#restart-your-app) +::: + +:::{tab-item} Azure +[Restart app](/troubleshoot/azure.md#restart-app) +::: + +:::{tab-item} Northflank +[Restart](/troubleshoot/northflank.md#restart) +::: + +:::{tab-item} Fly.io +[Restart your app](/troubleshoot/fly.io.md#restart-your-app) +::: + +:::{tab-item} Render +[Restart service](/troubleshoot/render.md#restart-service) +::: + +``` + +----------- + +If it's crashing again, and you use the Atlas database, make sure i's not [full](/troubleshoot/atlas.md#database-full)... + +If your database is not full, you might have your profiles table corrupted. + +- With Atlas, just [drop](/troubleshoot/atlas/#reports-slow-loading-or-timeout) them. +- With another accessible database, use a computer app like [Studio 3T](https://studio3t.com/) to delete the profiles table. Connect using your MONGODB_URI string. + +## GitHub + +Follow [these](/troubleshoot/github) instructions. + +## Heroku + +Search your issue [there](/troubleshoot/heroku). + +[There's nothing here, yet](heroku-nothing-here) can be due to billing issues. + +An [Application error](/troubleshoot/heroku.md#application-error) means Heroku crashed. Restart it and check database size. + +## Atlas + +Issues during database creation look [there](/troubleshoot/atlas). + +The usual reason for failure at build time is a [bad connection string](/troubleshoot/atlas.md#bad-connection-string) (Atlas). + +If you encounter a [Boot Error - Unable to connect to Mongo](/troubleshoot/atlas.md#unable-to-connect-to-mongo) it might be due to a [Database Full](/troubleshoot/atlas.md#database-full) + +## Railway + +Mind you [can't deploy Railway](/vendors/railway/new_user.md#step-1-fork-cgm-remote-monitor) if you just created a new GitHub account. + +[Nothing there](/troubleshoot/railway.md#nothing-here) is usually because you forgot to subscribe to a Developer plan. + +Else go [there](/troubleshoot/railway). + +## Fly.io + +Fly.io troubleshooting is complex if you didn't save your `fly.toml` configuration. Check in your local clone of the `cgm-remote-monitor` project. If you can't find it, [recover it](recover-fly-toml) first. + +Try to redeploy your app. + +Once done, issues are most probably due to your `fly.toml` contents or variables. + + + +------ + +## Other issues + +### Reports + +[Reports slow loading or timeout](/troubleshoot/atlas.md#reports-slow-loading-or-timeout) + +### No data in Nightscout + +Check your [uploader](/uploader/setup) is configured correctly. + +Make sure your Nightscout [time zone](/nightscout/profile_editor/) is correct. + +If you use a [DIY closed loop](/nightscout/close_loop) system make sure it's setup correctly. + +### Dexcom data not showing + +See [this dedicated page](/troubleshoot/dexcom_bridge/). + +### Dexcom or CareLink data stopping after a while + +```{hint} +CareLink with mmconnect data source stopped functioning for 7xx pumps. +**Remove the `mmconnect` plugin from `ENABLE`. +``` + + + +First verify you can see your BG in Clarity. + +If you're using Heroku, check the web app is not [sleeping](/troubleshoot/heroku.md#sleeping-app). +You might need to setup an Uptime robot for Heroku Eco plan and Render. + +```{admonition} UpTime Robot +Using an uptime robot with a bad password, or other issues originating from Nightscout can lead to a locked account ([Dexcom](/troubleshoot/dexcom_bridge.md#account-lock)). +``` + + + +### Data timing issues + +#### Basal is shifted in time + +- Check the time zone is correct for your currently active profile in your Nightscout [`Profile editor`](/nightscout/profile_editor/). + +
+
+
+
+#### Data in the future
+
+- Check you don't have data in the future with the `Admin tools`. Remove them if existing.
+
+
+
+
+
+- If this isn't working, or shows no future data, check in your database (Atlas see [here](/troubleshoot/atlas.md#data-in-the-future))
+
+
+
+#### Basal / IOB / COB missing after DST
+
+- Setup again your time zone in [profile editor](/nightscout/profile_editor/) (authenticate and save).
+
+
+
+### Error code instead of a BG value
+
+Nightscout implements Dexcom error codes as listed below:
+
+| Code | Corresponding error |
+| ----- | --------------------- |
+| `?SN` | Sensor not active |
+| `?MD` | Minimal deviation |
+| `?NA` | No antenna |
+| `?NC` | Sensor not calibrated |
+| `?CD` | Counts deviation |
+| `?AD` | Absolute deviation |
+| `???` | Power deviation |
+| `?RF` | Bad RF |
+
+
\ No newline at end of file
diff --git a/_sources/update/dev_branch.md.txt b/_sources/update/dev_branch.md.txt
new file mode 100644
index 00000000..900b8c15
--- /dev/null
+++ b/_sources/update/dev_branch.md.txt
@@ -0,0 +1,241 @@
+# Deploy another version
+
+If you need to return to the previous Nightscout version, or in rare occasions, like testing a specific fix or a feature that is not released yet (i.e. not in the `master` branch), you might need to deploy another branch like `dev` in the example below.
+
+Do not deploy `dev` or a branch other than `master` unless directed to do so (except if you know why you are doing so).
+
+## Step 1: Update your repository in GitHub
+
+Select your platform below:
+
+````{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Heroku, Railway, Northflank (GitHub)
+- Click here to log in at GitHub: [https://github.com/login](https://github.com/login).
+- Enter your username or email and your password. Click `Sign in`
+
+- Select your own `cgm-remote-monitor` project (**not `nightscout/cgm-remote-monitor`**)
+
+- Your repository will open.
+
+- In the branch drop down menu (normally showing `master`) select `dev`
+
+- Click`Fetch upstream` to update it, then `Fetch and merge`
+
+- After a moment, your repository should display `This branch is up to date with nightscout:dev`
+
+- If you ran into trouble, try to [Redeploy](/update/redeploy.md) (and this is **mandatory** if you don't see `dev` in GitHub.)
+:::
+
+:::{tab-item} Google Cloud, Docker (Azure, Northflank, Railway, Render)
+You don't need to update your GitHub repository.
+:::
+
+:::{tab-item} Fly.io
+You don't need to update your GitHub repository if you deployed from [https://github.com/nightscout/cgm-remote-monitor](https://github.com/nightscout/cgm-remote-monitor).
+:::
+
+
+````
+
+
+
+## Step 2: Deploy
+
+Select your platform below:
+
+````{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Google Cloud
+[Here](https://navid200.github.io/xDrip/docs/Nightscout/Customize.html)
+:::
+
+:::{tab-item} Heroku
+- Log in Heroku [https://id.heroku.com/login](https://id.heroku.com/login)
+
+- Select your app (hidden in yellow)
+
+- Click on `Deploy`
+
+- Verify Heroku is connected to GitHub, if not, click `Connect to GitHub`
+
+- If Heroku is not connected to GitHub, scroll down and click `Connect to GitHub`, if a popup window opens and requires authorization, click `Authorize Heroku`
+
+- Verify your app `cgm-remote-monitor` is connected to GitHub
+
+- If it isn't, In `Connect to GitHub`, type `cgm-remote-monitor` and click `Search ` then click `Connect`
+
+- If you have trouble connecting your app, click `Disconnect` and reconnect it as shown above
+
+- Scroll down to the bottom of the page, select the `dev` branch and click `Deploy Branch`
+
+- Build will start and information will scroll in the log window. Do not leave the page, do not interfere and wait for completion. It might take more than 10 minutes. Interrupting the process will lead to a broken site and you'll need to restart deployment.
+
+- Wait until the deploy process completes and click `View` (if nothing happens click `Manage App` then upper right `Open App`)
+
+:::
+
+:::{tab-item} Railway (GitHub)
+- Open [Railway](https://railway.app) and click `login`. Login with GitHub.
+
+
+- Select your Nightscout project.
+
+- Select your web app.
+
+- Still in `Settings` look at `Environment`.
+- Change the `Deployment Trigger` with `dev` (it was showing `master`).
+
+- If you only see `master` in the list you need to [redeploy](/update/redeploy.md) **taking care to select all branches and not only `master`**.
+ 
+- Once `dev` selected Railway will deploy automatically.
+:::
+
+:::{tab-item} Railway (Docker)
+a) Open [Railway](https://railway.app) and click `login`. Login with GitHub.
+
+
+b) Select your Nightscout project.
+
+c) Select your Docker service.
+
+d) Click on `Settings`, disconnect the source image.
+
+e) Select `Connect image` and replace `nightscout/cgm-remote-monitor:latest` with the [version](https://hub.docker.com/r/nightscout/cgm-remote-monitor/tags) you want to deploy (for example `nightscout/cgm-remote-monitor:latest_dev`).
+
+
+f) On the top left of the screen `Deploy`.
+
+- Your site will redeploy with the latest version.
+:::
+
+:::{tab-item} Northflank (GitHub)
+- Log into Northflank: [https://app.northflank.com/login](https://app.northflank.com/login)
+- Select your Nightscout project
+
+- Select your Nightscout service
+
+- Click on the pen icon after the current branch (example below: `master`)
+
+- In the branch list, select the version you want to deploy, then click `Update Build Source`
+
+- Your site will redeploy with the selected branch
+:::
+
+:::{tab-item} Northflank (Docker)
+- Log into Northflank: [https://app.northflank.com/login](https://app.northflank.com/login)
+- Select your Nightscout project
+
+- Select your Nightscout service
+
+- In Overview, Edit deployment
+
+- In the image path, replace `nightscout/cgm-remote-monitor:latest` with the [version](https://hub.docker.com/r/nightscout/cgm-remote-monitor/tags) you want to deploy (for example `nightscout/cgm-remote-monitor:latest_dev`), then click `Update & rollout restart`
+
+- Your site will redeploy with the selected branch
+:::
+
+:::{tab-item} Azure
+- Log into Azure : [https://portal.azure.com/](https://portal.azure.com/)
+- Select your App service, your Nightscout site name (you should see it in recent resources)
+
+- If you didn't find it, it will show in App Services
+
+- In the left menu select Deployment Center, in Full Image Name and Tag change the version to:
+`nightscout/cgm-remote-monitor:latest_dev` (example for dev)
+Or whichever version (change `filter tag` find the version) in the [list](https://hub.docker.com/r/nightscout/cgm-remote-monitor/tags).
+`nightscout/cgm-remote-monitor:14.2.6` (example for 14.2.6)
+
+- Click Save (or Discard if you don't want to save).
+ Your site will redeploy if you changed the configuration. Expect a few minutes before it comes back online.
+
+:::
+
+:::{tab-item} Fly.io
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer. You also need to [install git](https://git-scm.com/downloads) if you're using a Windows computer.
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+- Log in Fly.io:
+`flyctl auth login`
+- Verify your Nightscout app name, use it to replace `example-ns` in the following lines.
+`flyctl app list`
+- Verify your app current region (three letters code) and make sure it's in the [free tier](https://fly.io/docs/reference/regions/#fly-io-regions).
+`flyctl app list`
+- Navigate to the `cgm-remote-monitor` folder from which you deployed Nightscout on your computer. Verify it contains the `fly.toml` configuration file you used to deploy your site.
+ - If you don't see this file, recover it:
+ `flyctl config save --app example-ns`
+- If you migrated from Heroku using the wizard, or if you can't find this folder on your computer, follow the next steps to recover your Fly.io configuration:
+ - Fork a copy of the Nightscout repository and change directory
+ `git clone https://github.com/nightscout/cgm-remote-monitor`
+ `cd cgm-remote-monitor`
+ - Download a default `fly.toml` configuration file
+ `flyctl config save --app example-ns`
+- Update your Nightscout repository
+`git config pull.rebase true`
+`git pull origin dev`
+- Edit your `fly.toml` configuration and search this section:
+```
+[[services]]
+ protocol = "tcp"
+ internal_port = 8080
+ processes = ["app"]
+```
+- Change the internal port value to 1337, do not change anything else, do not remove the spaces before `internal_port`.
+`internal_port = 1337`
+- Save the `fly.toml` file.
+- Deploy Nightscout:
+`flyctl launch`
+- Wait until completion, you site should now be running the latest Nightscout version.
+```
+Updating existing machines in 'example-ns' with rolling strategy
+
+-------
+ ✔ Machine 1781944ae46438 [app] update succeeded
+-------
+
+Visit your newly deployed app at https://example-ns.fly.dev/
+```
+- Don't forget to downscale the app if you haven't yet!
+`flyctl scale --app example-ns count 1`
+
+:::
+
+:::{tab-item} Render (Docker)
+- Log into Render: [https://dashboard.render.com/](https://dashboard.render.com/)
+- Select your Nightscout project
+
+- Go to `Settings` and scroll down to `Deploy`. Edit the URL of the image deployed
+
+- Change it to:
+`nightscout/cgm-remote-monitor:latest_dev` (example for dev)
+Or whichever version (change `filter tag` find the version) in the [list](https://hub.docker.com/r/nightscout/cgm-remote-monitor/tags).
+`nightscout/cgm-remote-monitor:14.2.6` (example for 14.2.6)
+
+- Click `Save changes`.
+- Your site will redeploy with the selected branch
+:::
+
+````
+
+
+
+Check your [profile time zone](/nightscout/profile_editor.md#profile-view) is correct. You're done!
+
+
+
+
+
+## How to return to the `master` release
+
+If things don't go as expected you can simply redeploy your `master` branch performing the same steps and using `master` instead of `dev`.
+
+When the dev branch gets merged into release, just follow the [classic update method](/update/update.md).
+
+
\ No newline at end of file
diff --git a/_sources/update/downgrade.md.txt b/_sources/update/downgrade.md.txt
new file mode 100644
index 00000000..aa0c5edc
--- /dev/null
+++ b/_sources/update/downgrade.md.txt
@@ -0,0 +1,53 @@
+# Downgrade Nightscout
+
+
+
+There is usually no good reason to downgrade Nightscout unless being instructed to do so.
+
+First try to deploy another version if available: see [Deploy another version](/update/dev_branch).
+
+If you use Heroku and you want to return to the previous version, see [Roll back Heroku](/troubleshoot/heroku.md#roll-back-heroku).
+
+
+
+## Deploy an old release
+
+
+
+### **Docker**
+
+You deployed a Docker container: you're not using GitHub (Azure, Northflank, Railway, Render) use [this method](/update/dev_branch).
+
+
+
+### GitHub
+
+You forked Nightscout in your own GitHub account and used it to deploy.
+
+**Experienced users only - not recommended**
+
+Deploying an archived release of Nightscout is complex and involves using Git on your computer (You need to [install git](https://git-scm.com/downloads) if you're using a Windows computer).
+
+Before starting you need to have the project `nightscout/cgm-remote-monitor` forked in your GitHub repository, with not only the master fork copied (look out for the check box!). It is recommended to [redeploy](/update/redeploy) paying attention to this step.
+
+Clone it locally (navigate to the folder where you'll want it saved locally before cloning). Replace YOUR-USERNAME by your GitHub user name.
+
+`git clone https://github.com/YOUR-USERNAME/cgm-remote-monitor`
+
+First identify the commit matching the release you want to use, look into the [released versions](https://github.com/nightscout/cgm-remote-monitor/releases).
+
+
+
+
+
+Then create a branch out of this commit (replace BRANCH by the branch name you want and indicate the COMMIT matching the one you need, in the case above b627d31):
+
+`git checkout -b BRANCH COMMIT`
+
+Push this new branch to your repository
+
+`git push --set-upstream origin BRANCH`
+
+
+
+You can now [deploy](/update/dev_branch.md#step-2-deploy) it in your web app, selecting it in the drop down menu.
diff --git a/_sources/update/redeploy.md.txt b/_sources/update/redeploy.md.txt
new file mode 100644
index 00000000..920bd8d8
--- /dev/null
+++ b/_sources/update/redeploy.md.txt
@@ -0,0 +1,13 @@
+# Redeploy with GitHub
+
+When encountering update issues with GitHub, the easiest method it to delete it and fork the project again.
+
+## Delete your own fork of cgm-remote-monitor
+
+```{include} /vendors/github/delete.md
+
+```
+
+## [Fork the Nightscout project](/troubleshoot/github.md#fork-the-nightscout-project)
+
+
diff --git a/_sources/update/upd_stack.md.txt b/_sources/update/upd_stack.md.txt
new file mode 100644
index 00000000..d2c00413
--- /dev/null
+++ b/_sources/update/upd_stack.md.txt
@@ -0,0 +1,79 @@
+# Update the Heroku stack
+
+
+
+AAPS users: mind the [compatibility matrix](../nightscout/close_loop.md#aaps)!
+
+
+
+It is good practice to maintain your Heroku stack up to date. Either when you receive an email from Heroku or when you [update your Nightscout site](/update/update) (which is also a good habit).
+
+
+
+- Log in Heroku [https://id.heroku.com/login](https://id.heroku.com/login)
+
+
+
+
+
+
+
+- Select your app
+
+
+
+
+
+- Click `Settings`
+
+
+
+
+
+- If present select `Upgrade Stack`
+
+
+
+
+
+- `Confirm` the upgrade
+
+
+
+
+
+- Now you need to deploy to upgrade the stack
+
+
+
+
+
+- Click on `Deploy`
+
+
+
+
+
+- Scroll down to the bottom of the page, select the `master` branch and click `Deploy Branch`
+
+```{hint}
+If you can't select the `master` branch or `Deploy Branch` doesn't do anything [reconnect GitHub](heroku-nogit).
+```
+
+
+
+
+
+- Build will start and information will scroll in the log window. Do not leave the page, do not interfere and wait for completion. It might take more than 10 minutes. Interrupting the process will lead to a broken site and you'll need to restart deployment.
+
+
+
+
+
+- Wait until the deploy process completes and click `View` (if nothing happens click `Manage App` then upper right `Open App`)
+
+
+
+
+
+You have upgraded your Heroku stack.
\ No newline at end of file
diff --git a/_sources/update/update.md.txt b/_sources/update/update.md.txt
new file mode 100644
index 00000000..d927b60f
--- /dev/null
+++ b/_sources/update/update.md.txt
@@ -0,0 +1,203 @@
+# Update Nightscout
+
+```{tip}
+You don't need to follow these instructions if you use a hosted service.Contact the vendor to learn more about possible updates.
+```
+
+
+
+[See here which is the current released version](https://github.com/nightscout/cgm-remote-monitor/releases) before updating.
+
+
+
+## Step 1: Update your repository in GitHub
+
+Select your current platform below:
+
+````{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Heroku, Railway, Northflank (GitHub)
+- Click here to log in at GitHub: [https://github.com/login](https://github.com/login).
+- Enter your username or email and your password. Click `Sign in`
+
+- Select your own `cgm-remote-monitor` project (**not `nightscout/cgm-remote-monitor`**)
+
+- Your repository will open. If you see `This branch is xxx commits behind nightscout:master` you need to update.
+- Select `Fetch upstream`
+
+- Select `Fetch and merge`
+
+- After a moment, your repository should display `This branch is up to date with nightscout:master`
+
+You have now updated your GitHub cgm-remote-monitor repository.
+If you ran into trouble, you can [redeploy](/update/redeploy) the project.
+:::
+
+:::{tab-item} Google Cloud, Docker (Azure, Northflank, Railway, Render)
+You don't need to update your GitHub repository.
+:::
+
+:::{tab-item} Fly.io
+You don't need to update your GitHub repository if you deployed from [https://github.com/nightscout/cgm-remote-monitor](https://github.com/nightscout/cgm-remote-monitor).
+:::
+
+
+````
+
+
+
+## Step 2: Deploy
+
+````{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Google Cloud
+Continue [here](https://navid200.github.io/xDrip/docs/Nightscout/update_nightscout.html)
+:::
+
+:::{tab-item} Heroku
+- Log in Heroku [https://id.heroku.com/login](https://id.heroku.com/login)
+
+- Select your app (hidden in yellow)
+
+- Click on `Deploy`
+
+- Verify Heroku is connected to GitHub, if not, click`Connect to GitHub`
+
+- If Heroku is not connected to GitHub, scroll down and click `Connect to GitHub`, if a popup window opens and requires authorization, click `Authorize Heroku`
+
+- Verify your app `cgm-remote-monitor` is connected to GitHub
+
+- If it isn't, In `Connect to GitHub`, type `cgm-remote-monitor` and click `Search` then click `Connect`
+
+- If you have trouble connecting your app, click `Disconnect` and reconnect it as shown above
+
+- Scroll down to the bottom of the page, select the `master` branch and click `Deploy Branch`
+
+- Build will start and information will scroll in the log window. Do not leave the page, do not interfere and wait for completion. It might take more than 10 minutes.Interrupting the process will lead to a broken site and you'll need to restart deployment.
+
+- Wait until the deploy process completes and click `View` (if nothing happens click `Manage App` then upper right `Open App`)
+
+- Your site will open and should be at the latest version.
+- Check your [profile time zone](/nightscout/profile_editor.md#profile-view) is correct. You're done!
+If you ran into trouble, try the [Redeploy](/update/redeploy.md) method
+:::
+
+:::{tab-item} Azure
+- Log into Azure : [https://portal.azure.com/](https://portal.azure.com/)
+- Select your App service, your Nightscout site name (you should see it in recent resources)
+
+- If you didn't find it, it will show in App Services
+
+- In the left menu select Deployment Center and change Continuous Deployment to **On**.
+
+- Click Save (or Discard if you don't want to update).
+ Your site will redeploy with the latest cgm-remote-monitor version.
+ Expect a few minutes before it comes back online.
+
+- You can leave Continuous Deployment On if you want upgrades to happen automatically, or turn it back to Off (and save) to control upgrades manually yourself.
+
+:::
+
+:::{tab-item} Fly.io
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer. You also need to [install git](https://git-scm.com/downloads) if you're using a Windows computer.
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+- Log in Fly.io:
+`flyctl auth login`
+- Verify your Nightscout app name, use it to replace `example-ns` in the following lines.
+`flyctl app list`
+- Verify your app current region (three letters code) and make sure it's in the [free tier](https://fly.io/docs/reference/regions/#fly-io-regions).
+`flyctl app list`
+- Navigate to the `cgm-remote-monitor` folder from which you deployed Nightscout on your computer. Verify it contains the `fly.toml` configuration file you used to deploy your site.
+ - If you don't see this file, recover it:
+ `flyctl config save --app example-ns`
+- If you migrated from Heroku using the wizard, or if you can't find this folder on your computer, follow the next steps to recover your Fly.io configuration:
+ - Fork a copy of the Nightscout repository and change directory
+ `git clone https://github.com/nightscout/cgm-remote-monitor`
+ `cd cgm-remote-monitor`
+ - Download a default `fly.toml` configuration file
+ `flyctl config save --app example-ns`
+- Update your Nightscout repository
+`git pull`
+- Edit your `fly.toml` configuration and search this section:
+```
+[[services]]
+ protocol = "tcp"
+ internal_port = 8080
+ processes = ["app"]
+```
+- Change the internal port value to 1337, do not change anything else, do not remove the spaces before `internal_port`.
+`internal_port = 1337`
+- Save the `fly.toml` file.
+- Deploy Nightscout:
+`flyctl launch`
+- Wait until completion, you site should now be running the latest Nightscout version.
+```
+Updating existing machines in 'example-ns' with rolling strategy
+
+-------
+ ✔ Machine 1781944ae46438 [app] update succeeded
+-------
+
+Visit your newly deployed app at https://example-ns.fly.dev/
+```
+- Downscale the app if you haven't yet
+`flyctl scale --app example-ns count 1`
+
+:::
+
+:::{tab-item} Railway Northflank Render (GitHub)
+Once GitHub updated, your Nightscout should automatically deploy with the latest version.
+:::
+
+:::{tab-item} Northflank (Docker)
+- Log into Northflank: [https://app.northflank.com/login](https://app.northflank.com/login)
+- Select your Nightscout project
+
+- Select your Nightscout service
+
+- In Overview, Edit deployment
+
+- In the image path, check the image is `nightscout/cgm-remote-monitor:latest` (modify if necessary), then click `Update & rollout restart`
+
+- Your site will redeploy with the latest version.
+:::
+
+:::{tab-item} Railway (Docker)
+a) Open [Railway](https://railway.app) and click `login`. Login with GitHub.
+
+
+b) Select your Nightscout project.
+
+c) Select your Docker service.
+
+d) Click on `Settings`, disconnect the source image.
+
+e) Select `Connect image` and type `nightscout/cgm-remote-monitor:latest` then press enter.
+
+
+f) Go to the `Deployment` tab and from the three dots menu of the top deployment select `Redeploy`.
+
+- Your site will redeploy with the latest version.
+:::
+
+:::{tab-item} Render (Docker)
+- Log into Render: [https://dashboard.render.com/](https://dashboard.render.com/)
+- Select your Nightscout project
+
+- Go to `Settings` and top right expand `Manual Deploy`, Select `Deploy latest reference`
+
+- Your site will redeploy with the updated Nightscout version
+:::
+
+````
+
+
+
diff --git a/_sources/uploader/setup.md.txt b/_sources/uploader/setup.md.txt
new file mode 100644
index 00000000..81845261
--- /dev/null
+++ b/_sources/uploader/setup.md.txt
@@ -0,0 +1,254 @@
+# Setup Uploaders
+
+
+
+```{hint}
+You usually should express the Nightscout URL in secure `**https://**`, not only `http://`.
+(Unless you set `INSECURE_USE_HTTP` to `true`)
+```
+
+## What is my Nightscout URL?
+
+This is the address you type in any browser to display your Nightscout web site.
+
+If you're using a hosted service, ask the vendor.
+
+````{tab-set}
+
+:::{tab-item} Select your platform ->
+
+:::
+
+:::{tab-item} Heroku
+Your `Nightscout URL` defined in Heroku by your App name, is the one that shows when you open your Nightscout site in a browser.
+It usually looks like: `https://yoursitename.herokuapp.com`
+
+
+:::
+
+:::{tab-item} Railway
+Your `Nightscout URL` is defined in Railway by your Web app name, as shown in your [Dashboard](https://railway.app/dashboard).
+It usually looks like: `https://yoursitename.up.railway.app`
+
+
+:::
+
+:::{tab-item} Northflank
+Your `Nightscout URL` is defined in Northflank by your Web app name, as shown in your project services.
+It usually looks like: `https://port-name--service-name--project-name--entity-dns-id.code.run`
+
+
+:::
+
+:::{tab-item} Azure
+Your `Nightscout URL` is defined in Azure by your Web app name, as shown in your App services.
+It usually looks like: `https://yoursitename.azurewebsites.net`
+
+
+:::
+
+:::{tab-item} Fly.io
+Your `Nightscout URL` is defined in Fly.io by the `app` variable in your `fly.toml` file.
+You can also find it in your Dashboard.
+It usually looks like: `https://yoursitename.fly.dev`
+
+
+:::
+
+:::{tab-item} Google Cloud
+Your `Nightscout URL` is defined in FreeDNS.
+You can find it in [Status - Hostname](https://navid200.github.io/xDrip/docs/Nightscout/Hostname.html).
+:::
+
+````
+
+
+
+## Dexcom
+
+You need at least one follower to use Nightscout `share` or `nightscout-connect` plugins.
+
+```{hint}
+If you use a DIY closed loop system it is recommended that you let it upload to Nightscout instead of importing data using Dexcom Share and a Nightscout plugin.
+```
+
+On your master phone, touch the Share icon, enable Sharing. If you have no follower, add one. You can also invite yourself.
+
+
+
+
+
+```{tab-set}
+
+:::{tab-item} Select Nightscout version ->
+
+:::
+
+:::{tab-item} 14 and previous
+Verify, update or add these variables:
+`BRIDGE_USER_NAME`
+`BRIDGE_PASSWORD`
+`BRIDGE_SERVER`
+
+You need to add `bridge` in the `ENABLE` variable. Do not delete other entries, just add `bridge` after a space.
+:::
+
+:::{tab-item} 15
+Verify, update or add these variables:
+`CONNECT_SOURCE` set to `dexcomshare`
+`CONNECT_SHARE_ACCOUNT_NAME`
+`CONNECT_SHARE_PASSWORD`
+`CONNECT_SHARE_REGION` (must be set to `ous` if outside of the US, else don't add this variable)
+
+You need to add `connect` in the `ENABLE` variable. Do not delete other entries, just add `connect` after a space.
+:::
+
+```
+
+
+
+```{admonition} MOST COMMON ERRORS
+:class: hint
+The most common error on initial Nightscout setups is that people incorrectly use an old account or an old password. To test your username and password, go to Dexcom's Clarity page (check [here for USA accounts](https://clarity.dexcom.com) and [here for the others](https://clarity.dexcom.eu)) and try logging in to your Dexcom account. If your account info isn't valid, or you don't see any data in your Clarity account... you need to figure out your actual credentials before moving ahead. See [here](/troubleshoot/dexcom_bridge/) for troubleshooting tips and information on your Dexcom account.
+```
+
+```{admonition} Password
+:class: note
+*Some people have had problems with their bridge connecting when their Dexcom passwords are entirely numeric. If you have connection issues in that case, try changing your password to something with a mix of numbers and letters.*
+```
+
+
+
+## Medtronic CareLink
+
+```{warning}
+The `mmconnect` plugin is **NOT** functional anymore with recent pumps (7xx).
+```
+
+You can use an Android phone with xDrip+. See [**here**](../../uploader/xdripcarelink) how to set it up.
+
+
+
+```{tab-set}
+
+:::{tab-item} Select Nightscout version ->
+
+:::
+
+:::{tab-item} 14 and previous
+Verify, update or add these variables:
+`CARELINK_USER_NAME`
+`CARELINK_PASSWORD`
+`MMCONNECT_SERVER`(must be set to `US` if inside the US, or else `EU`)
+
+You need to add `mmconnect` in the `ENABLE` variable. Do not delete other entries, just add `mmconnect` after a space.
+:::
+
+:::{tab-item} 15
+Verify, update or add these variables:
+`CONNECT_SOURCE` set to `minimedcarelink`
+`CONNECT_CARELINK_USERNAME`
+`CONNECT_CARELINK_PASSWORD`
+`CONNECT_CARELINK_REGION` (must be set to `us` if inside the US, or else `eu`)
+`CONNECT_CARELINK_PATIENT_USERNAME` must be set to the patient name if more than one in present in Carelink.
+
+You need to add `connect` in the `ENABLE` variable. Do not delete other entries, just add `connect` after a space.
+:::
+
+```
+
+
+
+## [Medtronic 600 Series with uploader](http://pazaan.github.io/600SeriesAndroidUploader/)
+
+
+
+You can also use [this QR code generator](https://nightscout.github.io/pages/configure/) and the menu item `Scan NS-Autoconfig QR Code` to copy the information.
+
+For hosted Nightscout you'll find the QR code generator in [Uploaders](https://www.t1pal.com/account/sites/my#Uploaders), select the `HTTP` tab.
+
+You might want to setup [additional fields](https://github.com/nightscout/cgm-remote-monitor/#pump-pump-monitoring) for your pump.
+
+Facebook Group [Nightscout for Medtronic](https://www.facebook.com/groups/NightscoutForMedtronic)
+
+
+
+## [xDrip+](https://jamorham.github.io/#xdrip-plus)
+
+```{admonition} Mind the syntax!
+:class: warning
+**`https://API_SECRET@my_nightscout_url/api/v1/`**
+`my_nightscout_url` will depend on where your site is hosted (see top of this page)
+You will find your `API_SECRET`in your site variables.
+```
+
+Here is how it will look like for some vendors:
+
+```html
+https://API_SECRET@yoursite.herokuapp.com/api/v1/
+https://API_SECRET@yoursite.up.railway.app/api/v1/
+https://API_SECRET@yoursite.guest.t1pal.com/api/v1/
+https://API_SECRET@yoursite.10be.de/api/v1/
+```
+
+
+
+
+
+Facebook Group [xDrip](https://www.facebook.com/groups/xDripG5)
+
+
+
+## [Glimp](https://play.google.com/store/apps/details?id=it.ct.glicemia)
+
+
+
+
+
+## [Juggluco](http://jkaltes.byethost16.com/Juggluco/mgdL/index.html)
+
+
+
+
+
+## [Diabox](https://www.bubblan.org/diabox/)
+
+
+
+
+
+## [LinkBluCon](https://www.ambrosiasys.com/our-products/linkblucon/)
+
+
+
+
+
+## [Tomato](http://tomato.cool/)
+
+
+
+
+
+## [Spike](https://spike-app.com/)
+
+Look [here](https://github.com/SpikeApp/Spike/wiki/Spike-Follower-Mode#configure-spike-master).
+
+
+
+Facebook group [Spike App](https://www.facebook.com/groups/spikeapp)
+
+
+
+## [xDrip4iOS](https://xdrip4ios.readthedocs.io/en/latest/)
+
+
+
+Facebook group [xDrip4iOS](https://www.facebook.com/groups/853994615056838/)
+
+
+
+## DIY Closed Loop
+
+See the app documentation in the [dedicated page](/nightscout/close_loop.md).
+
+
\ No newline at end of file
diff --git a/_sources/uploader/uploaders.md.txt b/_sources/uploader/uploaders.md.txt
new file mode 100644
index 00000000..eff4b725
--- /dev/null
+++ b/_sources/uploader/uploaders.md.txt
@@ -0,0 +1,115 @@
+# Supported Uploaders
+
+An **Uploader** is a mechanism or system for uploading the CGM data from your sensor to your Nightscout site. This can be either an electronic solution (usually for older devices), a simple app installed on your phone (for most newer systems) that connects to the sensor/pump and then uploads this data but also another app in the cloud acting as a "bridge" and mirroring data to Nightscout.
+
+The type of Uploader needed will depend on the type of CGM system being used. In this page, we will break the different systems down by manufacturer, then further by sensor type.
+
+Once you are clear about the type of sensor and upload system you will be using, you can find detailed configuration information for each one [here](/uploader/setup.md).
+
+
+If you're developing an uploader, you'll find the API information in your own Nightscout site at `/api-docs` and `/api3-docs`.
+
+
+
+## DIY Closed loop Systems
+
+Only your loop app should upload BG to Nightscout.
+
+See this [dedicated page](/nightscout/close_loop) for setup links.
+
+
+
+## Dexcom
+
+### Dexcom G5/G6/ONE/G7
+
+
+
+If you are using the Dexcom sensor (except ONE) connected to the Dexcom app on your phone, it will upload directly to the Dexcom servers (also still known as "Dexcom Share") and you won't need to use any extra uploader or master device.
+
+```{note}
+Dexcom Share is not available with Dexcom ONE. Use xDrip+ or xDrip4iOS.
+```
+
+For this to work, Nightscout must be configured to use the `bridge` plug-in and will then automatically pull the CGM information directly from the Dexcom servers in real-time.
+
+```{note}
+If you use a [DIY closed loop system](/nightscout/close_loop) it is recommended that you let it upload to Nightscout instead of importing data using Dexcom Share and the `bridge` plugin.
+```
+
+*Please note that at this time (end 2023), the Dexcom G5 system is effectively obsolete but some people are still using stocks of old sensors and transmitters.*
+
+If you don't want to use the official Dexcom apps, you can use **open-source software** apps for your Dexcom sensor to connect, display, alarm and also upload to Nightscout:
+
+**Android**: xDrip+ for G5, G6, ONE and G7.
+
+**iOS**:
+ Spike for G5 and older G6 transmitters (**not Firefly**)
+ xDrip4iOS for G5, G6 and ONE transmitters
+
+
+
+```{admonition} Dexcom "Firefly" Transmitters
+:class: hint
+Most of the useable transmitters that fall into this category at the present time are generally rebatteried or rechargeable/modified transmitters.
+```
+
+## Medtronic
+
+If your sensor system is able to directly upload to CareLink then Nightscout might be able to get the information directly from the cloud using the `mmconnect` (deprecated) plugin. Unfortunately, this is **not possible anymore with recent pumps (7xx series and above)**.
+
+
+
+
+
+If this isn't an option and your sensor/transmitter is connected to your pump (Medtronic 600 series pumps), then you'll need an Android phone connected with an OTG cable to your pump's connected glucose meter. The phone will need to run the [600 Series Uploader](http://pazaan.github.io/600SeriesAndroidUploader/) app.
+
+
+
+## Glucomen Day
+
+You can forward your data from GlucoLog Web using an AWS bridge documented [here](https://github.com/yaronkhazai/gmns-bridge/tree/main/guides).
+
+## Tandem t:slim X2
+
+You can synchronize your treatments one way from your Tandem Diabetes t:connect web/mobile application to Nightscout using a bridge app running via **Pipenv** or **Docker** as documented [here](https://github.com/jwoglom/tconnectsync).
+
+## Abbott Freestyle Libre
+
+### Libre 1
+
+Non Bluetooth-enabled Freestyle Libre sensors will need an additional transmitter device fixed on top of the sensor to send readings to the uploader device. In release order here are some transmitter options: [LimiTTer](https://github.com/JoernL/LimiTTer), BlueReader, Blucon, MiaoMiao, Bubble, Droplet and Atom.
+
+```{admonition} Transmitter Compatibility
+:class: warning
+The Libre environment is complex and evolves quickly. Before buying a transmitter, please join the respective Facebook groups and make sure that the transmitter you are planning to buy is compatible with your sensor type.
+```
+
+Most of the transmitters have their own proprietary apps. Nearly all of these support the uploading of data to Nightscout (LinkBluCon, Tomato, Diabox, eDroplet, ...). Again, check the transmitter manufacturer's website and the relevant Facebook support groups for information.
+
+**Open-source apps** such as **xDrip+**, **Juggluco**, **Spike** and **xDrip4iOS** also support some of the above transmitter devices.
+
+### Libre 2
+
+You can connect to the Libre 2 sensor (**EU only**) without an additional transmitter using [xDrip+](https://www.minimallooper.com/post/how-to-setup-freestyle-libre-2-and-oop2-to-use-a-native-bluetooth-connection-in-xdrip), and [xDrip4iOS](https://xdrip4ios.readthedocs.io/en/latest/connect/cgm/#libre).
+Other Libre 2 sensors can be used directly with [Juggluco](http://jkaltes.byethost16.com/Juggluco/mgdL/index.html) and Diabox.
+
+### Libre 2/3
+
+You can use the sensor connected with [Juggluco](http://jkaltes.byethost16.com/Juggluco/mgdL/index.html) or upload to Nightscout automatically from LibreView servers deploying [this](https://github.com/timoschlueter/nightscout-librelink-up) project, or use xDrip+ to perform this operation.
+
+A new plugin in Nightscout 15 (under development) will integrate the project above.
+
+## Eversense
+
+In order to get data from the Eversense CGM system, you will need to use the [ESEL](https://github.com/BernhardRo/Esel/blob/master/apk/debug/app-debug.apk) app running on an Android phone with the [modified](https://cr4ck3d3v3r53n53.club/) vendor app.
+
+
+
+## Diasend
+
+[disaend-nightscout-bridge](https://github.com/burnedikt/diasend-nightscout-bridge) synchronizes treatments (insulin boli, temp basal changes) as well as continuous glucose values (CGV) from Diasend to Nightscout. This can help CamAPS FX users to view their treatments and glucose values via Nightscout. A 30 minutes delay might occur.
+
+A new plugin in Nightscout 15 (under development) will integrate the project above.
+
+
\ No newline at end of file
diff --git a/_sources/uploader/xdripcarelink.md.txt b/_sources/uploader/xdripcarelink.md.txt
new file mode 100644
index 00000000..d393ea7c
--- /dev/null
+++ b/_sources/uploader/xdripcarelink.md.txt
@@ -0,0 +1,35 @@
+# xDrip+ for CareLink
+
+Since the `mmconnect` plugin is not functional anymore, the best solution to upload automatically your data from CareLink to Nightscout is to use xDrip+.
+
+Download xDrip+ from **[here](https://github.com/NightscoutFoundation/xDrip/releases)** (use the latest pre-release).
+Once downloaded, install xDrip+ (you can find information [here](https://xdrip.readthedocs.io/en/latest/install/install)).
+
+
+
+## Using CareLink follower
+
+You can use an Android device to act as a bridge from CareLink to Nightscout.
+It can be either the phone you use with the CareLink app, or any other phone or tablet connected to the internet. You don't need to carry it with you. It only needs to be switched on and connected.
+
+There will be a delay between your pump readings and xDrip+/Nightscout. This is due to various polling times and should be less than 10 minutes.
+
+Make sure you setup a Share Partner on your CareLink Connect app.
+
+Select [CareLink follower](https://xdrip.readthedocs.io/en/latest/install/carelinkfollow/) as the data source.
+
+Once you have data in xDrip+ you can upload them to Nightscout using Cloud Upload, [Nightscout Sync](https://xdrip.readthedocs.io/en/latest/use/cloud/#nightscout-sync-rest-api).
+
+Leave Download treatments disabled.
+
+
+
+## Using Companion app
+
+If the phone you use with the CareLink, Guardian or Minimed app is Android, you can setup xDrip+ to read its notifications and send blood glucose values to Nightscout.
+
+ Select [Companion app](https://xdrip.readthedocs.io/en/latest/install/companion/) as the data source.
+
+Once you have data in xDrip+ you can upload them to Nightscout using Cloud Upload, [Nightscout Sync](https://xdrip.readthedocs.io/en/latest/use/cloud/#nightscout-sync-rest-api).
+
+Leave Download treatments disabled.
diff --git a/_sources/vendors/NAS/synology.md.txt b/_sources/vendors/NAS/synology.md.txt
new file mode 100644
index 00000000..e9af165d
--- /dev/null
+++ b/_sources/vendors/NAS/synology.md.txt
@@ -0,0 +1,13 @@
+# Nightscout in your Synology NAS
+
+
+
+Even if this is a valid solution for knowledgeable people, there is little detailed documentation except for https://t1d.dzienia.pl/nightscout_synology_tutorial/.
+
+More links below.
+
+[Nightscout on Synology + model, initially for the technically minded only](https://docs.google.com/document/d/1WWq6f_U2BSs3A_Ij312M5OmXCH-BaIxdC6FY3NenlzY/edit)
+
+https://github.com/vanelsberg/NightScoutSynology
+
+
diff --git a/_sources/vendors/VPS/docker.md.txt b/_sources/vendors/VPS/docker.md.txt
new file mode 100644
index 00000000..93c04e11
--- /dev/null
+++ b/_sources/vendors/VPS/docker.md.txt
@@ -0,0 +1,263 @@
+# Building Nightscout with Docker
+
+
+
+```{tip}
+The most complete guide for building your site step by step is the one used for [Oracle Cloud](https://www.dropbox.com/s/5twlqrndofqno0t/0-amber-oracle.pdf).
+If you use another hosting provider, skip Oracle specific instructions and follow the flow.
+```
+
+
+
+Original documentation from [Jason](https://github.com/nightscout/nightscout-docker).
+More from [Andries](https://gist.github.com/Andries-Smit/daac75cd4c06af78cde68c5dec941705) and [Peter](https://github.com/peterleimbach/TestNightscoutDockerUbuntuServer22.04LTS) (traefik as below), [justmara](https://github.com/justmara/ns-setup) and [Ireneusz](https://github.com/ireneusz-ptak/ns-docker).
+
+If you want to deploy with CoreOS look [here](https://danielscrivano.com/blog/posts/nightscout/).
+
+A comprehensive description of the yaml file for mongo and Nightscout setup [here](https://github.com/LostOnTheLine/Nightscout_Docker-Compose).
+
+If you don't own a domain name, get a DDNS name now: see [here](/nightscout/dns).
+
+You can also use [Caddy as reverse proxy](https://github.com/Alderskog/nightscout-in-OCN).
+
+
+
+## Update your system
+
+Update your Ubuntu system (you should type this is a command every 3 or 6 months to keep it updated).
+
+```bash
+sudo apt update
+sudo apt upgrade -y
+sudo apt clean
+```
+
+You will see it's completed when the terminal stops scrolling text and you're returned to the prompt.
+
+**If you see the following message: `*** System restart required ***` you will need to reboot**. Do not skip this step: reboot and wait a minute before opening again the console.
+
+```bash
+sudo reboot
+```
+
+You must probably already have nano installed. If necessary:
+
+```bash
+sudo apt install nano -y
+```
+
+
+
+## Deploy a single instance
+
+### Step 1 - Install Docker
+
+*Note: instructions from the [vendor](https://docs.docker.com/engine/install/ubuntu/)*
+
+a) Install keys
+
+```bash
+sudo apt-get -y install ca-certificates curl gnupg lsb-release
+sudo mkdir -p /etc/apt/keyrings
+curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg --yes
+```
+
+b) Install Docker
+
+```bash
+echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
+sudo apt-get update
+sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-compose-plugin
+```
+
+
+
+### Step 2 - Configure Nightscout
+
+a) If you're running your VPS as root: Create a new user. Else go to d)
+Don't try to run Nightscout as root, it will not work.
+**Replace `mainuser`** with a name of your choice, like your name, only lowercase letters.
+
+```bash
+sudo adduser mainuser
+```
+
+You need to invent a password for your new user.
+Confirm it then just hit `Enter` for the following lines, when done key `Y` then `Enter`.
+
+ b) Make your user an administrator.
+
+**Replace `mainuser`** with your new user name.
+
+```bash
+sudo usermod -aG sudo mainuser
+```
+
+c) Enable current user and make docker startup automatically.
+**Replace `mainuser`** with your new user name.
+
+```bash
+sudo groupadd docker
+sudo usermod -aG docker mainuser
+sudo systemctl enable docker
+```
+
+d) Login to the VPS using the account we just created.
+
+!!!warning "Do not run Nightscout as root"
+ From now on use your Nightscout user.
+
+**Replace `mainuser`** with your new user name.
+
+```
+sudo -u mainuser -s
+```
+
+Log out (`Ctrl-D` or `⌘-D`) or type `logout`, and log in with with your new user.
+
+e) Customize your Docker Compose configuration file
+
+You can use the default [docker-compose.yml](https://raw.githubusercontent.com/nightscout/cgm-remote-monitor/master/docker-compose.yml) file from the Nightscout repository or download [this one](/_static/docker-compose.yml).
+
+There are few information you need to update:
+
+- Which version of Nightscout you want to deploy.
+ You can find the list here: [https://hub.docker.com/r/nightscout/cgm-remote-monitor/tags](https://hub.docker.com/r/nightscout/cgm-remote-monitor/tags) and the tag is specified in the line below (example: `latest` is the latest release).
+
+```
+image: nightscout/cgm-remote-monitor:latest
+```
+
+- You need to specify your [time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List)
+
+```
+TZ: YOUR_TIMEZONE
+```
+
+- Your Nightscout site `API_SECRET` password.
+
+```
+API_SECRET: YOUR_API_SECRET
+```
+
+*Note: now you've also seen where your Nightscout variables are defined.*
+
+- You need to update your Nightscout site URL (your DDNS name looking like `name.domain.tld`)
+
+```
+- 'traefik.http.routers.nightscout.rule=Host(`YOUR_PUBLIC_HOST_URL`)'
+```
+
+- You need to put a valid email too for important certificate emails (i.e. probably never)
+
+```
+- '--certificatesresolvers.le.acme.email=YOUR_EMAIL'
+```
+
+
+
+### Step 3 - Build and run Nightscout
+
+To start your Nightscout:
+
+```
+sudo docker compose up -d
+```
+
+Or, if you want to start it in background (once everything is working as you won't see the log):
+
+```
+nohup sudo docker compose up -d &
+```
+
+To stop it (if you didn't select `always` restart for your containers):
+
+```
+sudo docker compose down
+```
+
+Note that you need to start it if you modify your `docker-compose.yml` configuration (to validate the changes).
+
+
+
+## Update or downgrade
+
+Edit your `docker-compose.yml` configuration and change the image to whichever you want in the [community maintained images](https://hub.docker.com/r/nightscout/cgm-remote-monitor/tags).
+
+If you're using `image: nightscout/cgm-remote-monitor:latest` and you want to upgrade it to latest release, don't change anything. You can update to `cgm-remote-monitor:latest_dev` or choose an older version like `cgm-remote-monitor:14.2.6`
+
+```
+sudo docker compose down
+sudo docker compose pull
+nohup sudo docker compose up -d &
+```
+
+
+
+## Deploy multiple instances
+
+Hints from [justmara](https://github.com/justmara)
+
+Portainer configuration used in docker-compose:
+
+```
+ portainer:
+ image: portainer/portainer-ee:latest
+ container_name: portainer
+ restart: unless-stopped
+ volumes:
+ - ./portainer-data:/data
+ - /var/run/docker.sock:/var/run/docker.sock
+ labels:
+ - 'traefik.enable=true'
+ - 'traefik.http.routers.portainer.rule=Host(`portainer.
+
+
+
+b) Sign in with your Microsoft account if you have one, else use GitHub.
+
+
+
+
+
+c) Agree and click Next.
+Perform necessary authentication.
+
+
+
+
+
+## Step 2: Create your Nightscout web app
+
+a) From the top left ☰ menu or the Azure Services icons, select + Create a resource.
+
+
+
+
+
+b) Search Web app and click Create.
+
+
+
+
+
+c) Check you're still using your Free Trial or 3-Month free Trial.
+Open the list in Resource group and pick your group (the one you created in Step 2.f.).
+
+
+
+If your free trial expired, select Pay-As-You-Go. It will be free if you use free resources like the Free F1 resource (see below).
+
+
+
+d) Decide your site name (only lowercase and you can use `-` as a separator).
+It must be unique: check the tick box at the end of the line is green.
+If it isn't: you need to choose another name...
+
+
+
+
+
+e) Now select a Docker container, in Linux.
+
+Pick a place close to where you live in the Region selection.
+Make sure it is the same than the database region you selected in Step 2.g.
+
+
+
+
+
+f) Select the free F1 plan.
+
+
+
+```{admonition} Limited CPU usage
+:class: warning
+The Free F1 plan includes 60 CPU minutes per day. It usually is enough for a moderate Nightscout usage but can also be insufficient and provoke interruptions in your Nightscout site. Not recommended for FreeAPS X and OpenAPS users.
+If you want a more reliable CPU, consider another plan like Shared D1 ($).
+```
+
+
+
+g) Click Next: Database > down in the page.
+
+
+
+
+
+g) Do not change anything and click Next: Docker > down in the page.
+
+
+
+
+
+h) In Image source select **Docker Hub** instead of Quickstart.
+
+
+
+
+
+i) In Image and tag paste the following name:
+
+`nightscout/cgm-remote-monitor:latest`
+
+
+
+
+
+j) Click Review + create in the lower left of the page.
+
+
+
+
+
+k) Verify the summary information:
+Free sku
+Check the site Name is what you wanted
+then click Create.
+
+
+
+
+
+Wait for the deployment to complete. Do not interfere.
+
+
+
+
+
+Congratulations, you have created your Nightscout web app.
+
+
+
+## Step 3: Configure your Nightscout web app
+
+> Now you need to tell it where the database is and other important information
+
+a) Click Go to resource
+
+
+
+
+
+b) In the left menu select Configuration
+
+
+
+
+
+**Check which deployment you're doing now!:**
+
+```{tab-set}
+
+:::{tab-item} I'm building a new Azure site
+:::{include} /vendors/azure/new_user_a.md
+:::
+
+:::{tab-item} I'm migrating from another platform
+:::{include} /vendors/azure/new_user_b.md
+:::
+
+```
+
+j) From the menu select Overview, then Browse.
+
+
+
+It will take some time before the window opens.
+
+
+
+```{include} /nightscout/first_setup.md
+
+```
+
+
+
+## Editing Config Vars in Azure
+
+
+
+a) Log into Azure : [https://portal.azure.com/](https://portal.azure.com/)
+
+b) Select your App service, your Nightscout site name (you should see it in recent resources)
+
+
+
+If you didn't find it, it will show in App Services
+
+
+
+c) In the left menu select Environment variables
+
+
+
+### View a variable value
+
+Click the eye icon to display the hidden value
+
+
+
+### Modify a variable
+
+Identify the line with the variable you want to change and click the pen icon at the end of the line
+Click OK to save it when finished
+Remember to save modifications when done with your variables!
+
+
+
+### Delete a variable
+
+Identify the line with the variable you want to delete and click the bin icon at the end of the line
+Remember to save modifications when done with your variables!
+
+
+
+### Add a variable
+
+Select New Application Setting and type variable name and value
+Remember to save modifications when done with your variables!
+
+
+
+~~~{note}
+Multiple lines values with `\n` should be edited manually as the character `\` will be duplicated.
+Example: `LOOP_APNS_KEY`
+```
+----BEGIN PRIVATE KEY-----\nMIGTAgEAMBMGBygGSM49AwEHBHkwdwIBAQQg7c8w00t5ju7N980r\nerN8N+isnJoec+ohIEuD0teRbPmgCgYIKoZIzj0DAQehRANCAAREnRISLSiFgdn4\nLbf44yIKspXKr7GpPBVshv3ShOms2qHTdAFriXXRPmbq7eAJuFrxpYOduU1dl9vo\nouciW0je\n-----END PRIVATE KEY-----
+```
+~~~
+
+Insert the value like you've done for all the others.
+
+
+
+At the top of the Environment variables view, select Advanced edit.
+
+
+
+Scroll down the list to your variable name and delete all duplicated `\` so that there will be no more `\\n` separators but only `\n`.
+
+
+
+Click `OK` to save the modified variable.
+
+
+
+### Save your modifications
+
+When you're done modifying your variables, click Save (or Discard if you don't want to save).
+Your site will redeploy if you changed the configuration. Expect a few minutes before it comes back online.
+
+
diff --git a/_sources/vendors/azure/new_user_a.md.txt b/_sources/vendors/azure/new_user_a.md.txt
new file mode 100644
index 00000000..321d83b7
--- /dev/null
+++ b/_sources/vendors/azure/new_user_a.md.txt
@@ -0,0 +1,104 @@
+---
+orphan: true
+---
+
+c) Click + New application setting
+
+
+
+
+
+d) In Name write `MONGODB_URI`
+
+**Mind your database type!**
+
+```{tab-set}
+
+:::{tab-item} I have an Atlas/Railway/Northflank database
+In the line below, Value, paste the connection string you obtained after creating your database.
+:::
+
+:::{tab-item} I have a Cosmos database
+In the line below, Value, paste the connection string **with socketTimeoutMS**.
+:::
+
+```
+
+
+Then click OK.
+
+
+
+e) Click again + New application setting (like in c. above) and write `API_SECRET` in Name.
+`API_SECRET` will be your Nightscout site password, it needs to be at least 12 characters long and you should **NOT use spaces** if you use @ or ! symbols remember you will probably need to express them using [Percent encoding](https://en.wikipedia.org/wiki/Percent-encoding#Percent-encoding_reserved_characters) in your uploader and downloader apps. If you're not sure on how to do this, it is recommended to use only letters (uppercase + lowercase) and digits.
+
+```{warning}
+The API_SECRET is the **main password allowing full access to your Nightscout site**. Make sure it's reasonably secure (mix uppercase and lowercase letters, plus digits) and **do no not share it publicly**. If you think you exposed it by mistake, it is recommended that you **change it**.
+```
+
+
+
+Click OK.
+
+
+
+f) Click again + New application setting and write `DISPLAY_UNITS` in Name.
+Acceptable choices for the units used in Nightscout are `mg/dl` or `mmol/L` (or just `mmol`).
+
+
+
+Click OK.
+
+
+
+g) Click again + New application setting and write `ENABLE` in Name.
+If you don't use Dexcom Share to get your BG data in Nightscout, copy the line below to Value:
+
+`careportal basal dbsize rawbg iob maker cob bwp cage iage sage boluscalc pushover treatmentnotify loop pump profile food openaps bage alexa override speech cors`
+
+If you want to use Dexcom Share as a data source copy this one (it includes the keyword `bridge`):
+
+`careportal basal dbsize rawbg iob maker cob bwp cage iage sage boluscalc pushover treatmentnotify loop pump profile food openaps bage alexa override speech cors bridge`
+
+Click OK.
+
+
+
+h) If you want to use Dexcom Share to have your data in Nightscout directly, you will need to add these three variable Names:
+
+`BRIDGE_USER_NAME` Your Dexcom account username to receive CGM data from the Dexcom Share service.
+`BRIDGE_PASSWORD` Your Dexcom account password to receive CGM data from the Dexcom Share service.
+`BRIDGE_SERVER` US if your Dexcom account is in the US, or, if you are bridging from the Dexcom Share service and are anywhere *outside* the US change this to EU.
+
+!!!note
+ If you use a DIY closed loop system it is recommended that you let it upload to Nightscout instead of importing using Dexcom Share and the `bridge` plugin.
+
+
+
+
+
+**Remember to add `bridge` at the end of the `enable` variable in the list below.**
+
+
+
+```{admonition} MOST COMMON ERRORS
+:class: hint
+The most common error on initial Nightscout setups is that people incorrectly use an old account or an old password. To test your username and password, go to Dexcom's Clarity page (check [here for USA accounts](https://clarity.dexcom.com) and [here for the others](https://clarity.dexcom.eu)) and try logging in to your Dexcom account. If your account info isn't valid, or you don't see any data in your Clarity account... you need to figure out your actual credentials before moving ahead. See [here](/troubleshoot/dexcom_bridge/) for troubleshooting tips and information on your Dexcom account.
+```
+
+```{admonition} Password
+:class: note
+*Some people have had problems with their bridge connecting when their Dexcom passwords are entirely numeric. If you have connection issues in that case, try changing your password to something with a mix of numbers and letters.*
+```
+
+```{hint}
+You need to have at least one follower to use Dexcom Share. See [here](/uploader/setup.md#dexcom).
+```
+
+
+
+i) Click Save, then Continue.
+
+
+
+
\ No newline at end of file
diff --git a/_sources/vendors/azure/new_user_b.md.txt b/_sources/vendors/azure/new_user_b.md.txt
new file mode 100644
index 00000000..d616e522
--- /dev/null
+++ b/_sources/vendors/azure/new_user_b.md.txt
@@ -0,0 +1,86 @@
+---
+orphan: true
+---
+
+```{tab-set}
+
+:::{tab-item} Migrating from Heroku
+c) Open a new browser tab or window and Log in [Heroku](https://id.heroku.com/login), select your app
+
+d) Click `Settings`
+
+e) Scroll down and click `Reveal Config Vars`
+
+f) Put the two windows Heroku and Azure side by side
+
+Now for every (no, not necessarily, read until **i** and come back) variable you need to do the following:
+:::
+
+:::{tab-item} Migrating from Railway
+c) Open [Railway](https://railway.app) and click `login`. Login with GitHub.
+
+
+d) Select your Nightscout project.
+
+Select your web app.
+
+e) Click on `Variables`.
+
+Click on `RAW Editor` top right
+
+f) Put the two windows Railway and Azure side by side
+
+Now for every variable you need to do the following:
+:::
+
+```
+
+
+
+g) Click + New application setting
+
+
+
+
+
+h) In Name write the variable name from the first column in Heroku or the one in red with Railway
+Then, in the line below, Value, paste the value from the second column in Heroku or the one in green with Railway.
+
+
+
+Then click OK and go for the next one.
+
+
+
+You might not need to copy ALL the values, if you know which ones you need you can go ahead.
+If you don't really know which ones you want to copy there's only few that are strictly necessary:
+
+**`API_SECRET`**
+**`MONGODB_URI`** *Note: if you don't see `MONGODB_URI` but see `MONGO_CONNECTION` (NOT `MONGO_COLLECTION`) use its value.*
+**`DISPLAY_UNITS`**
+
+in `ENABLE` paste this:
+
+If you don't use Dexcom Share to get your BG data in Nightscout, copy the line below to Value:
+
+`careportal basal dbsize rawbg iob maker cob bwp cage iage sage boluscalc pushover treatmentnotify loop pump profile food openaps bage alexa override speech cors`
+
+If you want to use Dexcom Share as a data source copy this one (it includes the keyword `bridge`):
+
+`careportal basal dbsize rawbg iob maker cob bwp cage iage sage boluscalc pushover treatmentnotify loop pump profile food openaps bage alexa override speech cors bridge`
+
+If you have your data coming directly from Dexcom share those three:
+
+`BRIDGE_USER_NAME`
+`BRIDGE_PASSWORD`
+`BRIDGE_SERVER`
+
+
+
+
+
+i) When you're done copying, click Save, then Continue.
+
+
+
+
\ No newline at end of file
diff --git a/_sources/vendors/digitalocean/new_user.md.txt b/_sources/vendors/digitalocean/new_user.md.txt
new file mode 100644
index 00000000..462bede2
--- /dev/null
+++ b/_sources/vendors/digitalocean/new_user.md.txt
@@ -0,0 +1,8 @@
+---
+orphan: true
+---
+
+
+
+
+
diff --git a/_sources/vendors/fly.io/new_user.md.txt b/_sources/vendors/fly.io/new_user.md.txt
new file mode 100644
index 00000000..911c35b9
--- /dev/null
+++ b/_sources/vendors/fly.io/new_user.md.txt
@@ -0,0 +1,659 @@
+
+# Nightscout in Fly.io
+
+
+
+```{admonition} Too complicated? Not what you're looking for?
+:class: seealso
+Consider a hosted Nightscout service! Check for easier solutions [here](/index.md#nightscout-as-a-service).
+```
+
+
+
+```{card}
+## Fly.io
+
+^^^
+You can create your new Nightscout site in Fly.io.
+
+**Pros**:
+* Nightscout fits in the free tier
+
+**Cons**:
+* **Maintaining your site requires the use of command line instructions, not very intuitive**
+* Fly.io stores variables as secrets: you cannot read them
+* Relying on the MongoDB Atlas database
+```
+
+
+
+## Step 0: Create a database
+
+```{tab-set}
+
+:::{tab-item} I don't have a database yet
+Make sure you [create one](/nightscout/database) before starting your Nightscout web app creation with Fly.io.
+Come back here when you have a `MONGODB_URI` connection string.
+:::
+
+:::{tab-item} I already have a database
+Copy the connection string from your previous platform: [edit the variables](/nightscout/setup_variables.md#nightscout-configuration) and look for `MONGODB_URI`.
+If you don't see `MONGODB_URI` but see `MONGO_CONNECTION` (**NOT** `MONGO_COLLECTION`): use its value.
+:::
+
+```
+
+
+
+## Step 1: Create a fly.io account
+
+[Sign up](https://fly.io/app/sign-up) to Fly.io.
+
+
+
+You will need to add credit card information to get Nightscout running.
+Whenever requested, add one to prove you're a real person:
+
+
+
+
+
+
+
+Nightscout should run for free within the [allowances](https://fly.io/docs/about/pricing/#free-allowances). If you get billed, please report costs [here](https://github.com/nightscout/nightscout.github.io/issues/new) to have the documentation updated.
+
+
+
+## Step 2: Install `flyctl`
+
+```{warning}
+The web terminal feature was removed from Fly.io.
+You need a computer with flyctl.
+```
+
+Follow [these instructions](https://fly.io/docs/hands-on/install-flyctl/) to install `flyctl` on your computer.
+
+*Note for Windows: you might experience issues with Git Bash or PowerShell, try an elevated command prompt.*
+
+
+
+## Step 3: Prepare the Nightscout project
+
+Type (or copy and paste) the following command in the terminal:
+
+a) Authenticate in Fly.io:
+
+`flyctl auth login`
+
+Clone the official Nightscout repository:
+
+`git clone https://github.com/nightscout/cgm-remote-monitor`
+
+
+
+b) Navigate to the Nightscout code directory copied locally with:
+
+`cd cgm-remote-monitor`
+
+
+
+c) Deploy your site with Fly.io.
+
+`flyctl launch`
+
+
+
+
+
+To the question `Would you like to tweak these setting before proceeding?` answer `Y` (yes).
+
+A web page to your new project will open in Fly.io.
+
+ d) Type your new Nightscout site name, make sure it is valid and isn't already used by someone else.
+
+
+
+
+
+e) Select the region closest to where you live, but make sure it doesn't require a paid plan.
+
+
+
+
+
+
+
+f) In services set the port to `1337`.
+
+
+
+
+
+g) Make sure to select a `shared CPU 1x` with only `256MB` of memory to remain within the [free allowances](https://fly.io/docs/about/pricing/#free-allowances) limits.
+
+
+
+
+
+h) Don't select any database and `Confirm Settings`.
+
+
+
+
+
+i) Deployment will start. Wait until it completes.
+
+
+
+
+
+
+
+## Step 5: Set your Nightscout secrets
+
+a) Compile the information below.
+
+File all necessary fields, click on the Validate button at the bottom of the form, if no error is seen you will have all variables displayed in the text box at the bottom, click on the Copy All button.
+
+
+
+### **Mandatory variables**
+
+These three variables below must have a value.
+
+**MONGODB_URI**
+
+The MongoDB Connection String to connect to your MongoDB cluster. If you don't have this from your Mongo database, please re-read installation instructions at [Nightscout database](https://nightscout.github.io/nightscout/database) before continuing
+
+
+
+**API_SECRET**
+
+
+
+A passphrase that must be at least 12 characters long. Avoid special characters, which can cause problems in some cases
+
+**DISPLAY_UNITS**
+
+
+
+
+Preferred BG units for the site: `mg/dl` or `mmol/l` (or just `mmol`)
+
+
+
+### **Customizations**
+
+Leave default values if you don't want to change them
+
+**CUSTOM_TITLE**
+
+
+
+The display name for the Nightscout site. Appears in the upper left of the main view. Often set to the name of the CGM wearer
+
+**THEME**
+
+
+
+
+Default setting for new browser views for the color theme of the CGM graph. (`default` `colors` or `colorblindfriendly`)
+
+**ENABLE**
+
+
+
+Plugins to enable for your site. Must be a space-delimited lower-case list. Include the word `bridge` here if you are receiving data from the Dexcom Share service
+
+**SHOW_PLUGINS**
+
+
+
+Default setting for whether or not these plugins are checked (active) by default not merely enabled. Include plugins here as in the ENABLE line; space-separated and lower-case
+
+**TIME_FORMAT**
+
+
+
+
+Default setting for new browser views for the time mode. (`12` or `24`)
+
+**NIGHT_MODE**
+
+
+
+
+Default setting for new browser views for whether Night Mode should be enabled. (`on` or `off`)
+
+**BOLUS_RENDER_OVER**
+
+
+
+U value over which the bolus values are rendered on the chart if the `x U and Over` option is selected
+
+
+
+### **Dexcom Share**
+
+If you want Nightscout to import directly from Dexcom Share
+
+**BRIDGE_USER_NAME**
+
+
+
+Your Dexcom account username to receive CGM data from the Dexcom Share service. Also make sure to include `bridge` in your ENABLE line.
+
+**BRIDGE_PASSWORD**
+
+
+
+Your Dexcom account password to receive CGM data from the Dexcom Share service. Also make sure to include `bridge` in your ENABLE line
+
+**BRIDGE_SERVER**
+
+
+
+
+If you are bridging from the Dexcom Share service and are anywhere *outside* the US change this to EU. (`US` or `EU`)
+
+
+
+### **Alarms**
+
+You can customize alarms or leave them to default values
+
+**ALARM_TYPES**
+
+
+
+
+`simple` and/or `predict`v. Simple alarms trigger when BG crosses the various thresholds set below. Predict alarms use a formula that forecasts where the BG is going based on its trend. You will *not* get warnings when crossing the BG thresholds set below when using the predict type
+
+**ALARM_URGENT_HIGH**
+
+