Hi all,
I am from Europe and I finally started getting coverage for dexcom cgm.
As fun as it is, several days and a couple of sensor later, I can't get that bloody thing to work in any way.
I have tried pretty much all possible options - apps (dexcom, xdrip, BYOD), all the settings.
I still have some hope that maybe BYOD could be the solution. But here's the issue - it does not currently support specifically Dexcom One. I imagine that implementation of it should not be complicated, as the product is basically the same.
Does anyone know if there's any hope for this, or should I be looking for alternatives altogether, as I am getting very tired with this? :)
Thanks!

keep the syntax as easy as possible

AAPS version 3.0.0.1 release and higher
Driver: Omnipod EROS

Problem description:
The Omnipod EROS driver has a bug that can lead to a situation where users get stuck with a pod registration that can not be "forcefully" discarded. Several users reported running into this problem as a result of Pod failure.

Work around used for not losing Objectives is importing 3.0 settings in AAPS version 2.8.1, discard the Pod and then export preferences that can be imported by AAPS 3.0

Proposed work around
Until the actual bug is solved, but also in general, I think the EROS driver should have a way to "wipe" the Pod state in case of "emergencies". Up to AAPS version 2.8 this could be done by editing the unencrypted preference file.
As of version 3.0 this is no longer an option.

How about an option to clear Pod state when running in developer mode?
This way users have an "escape" option to get out of situations where there is Pod state without option to Discard.
For AAPS 2.8 editing the preference file was used as a last resort

The weight requirements in Profile helper do not give any indication on what units are required KG/Grams/pounds etc

*Release notes for 3.0:
-bg data quality checks/constraints added

*a description of the data quality icons and what this means is missing, see https://www.facebook.com/groups/AndroidAPSUsers/permalink/3130354490519280/
@MilosKozak please help with a good wording for the documentation!

• https://androidaps.readthedocs.io/en/latest/Getting-Started/Screenshots.html
  section H - Buttons
  „ Buttons for insulin, carbs and Calculator are ‘always on’.“
  thats incorrect. when connection to pump lost, insulin button is invisible. recommendation to switch to virtual pump

it's available since release 3.0 as stated in the docs but no documentation about how to setup available in the docs

Please PR on the branch rework-project.

Hi,
Any admin can change the phrase that Libre 3 does not work with the US version.

I tested it on 10/1/2023, and it's working as expected.

I followed the same steps and was able to broadcast the values from xDrip to AAPS.
Libre 3

I don't speak Spanish, but as far as I can see, in 'Compilanda la APK', you can read how to update the akp and in 'actualiza......' you can read how to compile the akp

I'd like to propose to adjust the description of the SMB settings starting from here (https://androidaps.readthedocs.io/en/latest/Usage/Open-APS-features.html#enable-smb).

1. Change the order of how the settings are listed to reflect the order on the AAPS screen and the priority of how AAPS handles them
2. Highlight that "Enable SMB with high temp targets" has the highest priority
3. Highlight that you can either set "Enable SMB always" or use one or multiple of "Enable SMB with COB", "Enable SMB with temp targets", "Enable SMB after carbs"

PasswordReset file must be without spaces:

https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/update3_0.html#reset-master-password

https://androidaps.readthedocs.io/en/latest/Getting-Started/FAQ.html#how-to-reset-the-password-in-aaps-v3-x

This one is correct
https://androidaps.readthedocs.io/en/latest/Installing-AndroidAPS/update3_0.html#reset-master-password

@maheini
Hi Martin,

please check this and give feedback ideally via PR. The Link Checker Action reports two 404 errors in Libre3.md.

=> The Link is not working anymore. Can you please update or remove the link?!
"(There are several apps to find out if the smartphone is rooted, one of them is e.g. root-checker.org)"

=> The Juggluco App is not available in the Playstore anymore. I thought there was already an update but I can't find it. Can you please check this and update or delete the link/description?
"Now install the Juggluco App from the Playstore (version 4.0.1 or higher). With the help of this app, the blood sugar readings can be sent directly to Xdrip and AndroidAPS. For this purpose, the active sensor (which is registered on Libreview) is used within Juggluco. This also explains why a Libreview account is mandatory.Now install the Juggluco App from the Playstore (version 4.0.1 or higher). With the help of this app, the blood sugar readings can be sent directly to Xdrip and AndroidAPS. For this purpose, the active sensor (which is registered on Libreview) is used within Juggluco. This also explains why a Libreview account is mandatory."

Hi,
I'd like to address some minor issues regarding the NSClient app:

1) Naming confusion
It should be made clear whether the NSClient module (of AAPS) is meant or the NSClient app.

2) Download location of NSClient app
Can't be found in the doc.

3) Difference between NSClient and NSClient2 apk
I've found on Gitter:
Only difference is the app name. This way you can install the app twice on the same phone. You can follow 2 different persons/nightscouts with it.

4) NSClient app related to AAPS
A few sentences would be great about it pointing out the key differences: stripped down AAPS, etc.

We are using a system of Dexcom G6, Accu-Chek Combo, Nightscout, xDrip+, AAPS and NSClient app for a few months. Until now NSClient app seems to be the best way to follow somebody, as it can display all info including current insulin activity, and allows some interaction (profile, TT). Taking this into account, the app is not "advertised" enough. I've randomly came across the download location, and had to try NSClient and NSClient2, as I didn't know the diff.

Best regards

// and great appreciation for all the work done

The new Hebrew version of site is LTR which makes the text nigh unreadable. It needs to be adapted to RTL.
Thanks!

Hi All,

I have created a new automated build system for AndroidAPS.

I have also clone your repo and created a remote branch, modifing the building / updating APK instructions.

I would like to push my branch, raise a pull request and try to get the changes merged. However I am unable to do this. Could someone grant me access to push my branch please.

Here is a link to the documentation so you can see what I am linking to:
AndroidAPS Automated Build System

This has been tried and tested by a number of users but will continue to grow as experience of supporting users is gained.

Section https://androidaps.readthedocs.io/en/latest/Hardware/DexcomG6.html#new-transmitter-with-running-sensor mentions YouTube video https://youtu.be/AAhBVsc6NZo . Opening the video shows 'This video is no longer available'. Does anyone have saved the source video?

Is it possible to restrict the search results to a definied language? At present I get results for the topic in every language. So the result list is long.

Add instructions to add Git to the PATH variable.
Currently these are missing and only described for Android Studio, but the gradle build system need the PATH variable set.

https://androidaps.readthedocs.io/en/latest/EN/Installing-AndroidAPS/Nightscout.html#manual-nightscout-setup is pointing to Nightscout.info with mLab database add-on. That doesn't work anymore since it was removed beginning of this month. Please update to http://nightscout.github.io/nightscout/new_user/ or any preferred method.

Issue

Based on technical analysis #999, we could state that the quality of the multi-lingual documentation is poor with over a 1000 broken links and build warning. Despite the many people who have contributed wither their best effort and valuable time in translating the texts, but it resulted in broken mark-up, links and unreachable documentation.

“As a (potential) user I do not trust my live to a medical product that does not have quality documentation!”

The documentation is the first point of interaction for a new user. And the user will assume the there is a relation to the quality of the documentation and the quality of the product. And if he or she does not understand the product, will not start using it.

What should we do? I am sorry to raise the question. Should we continue this way?

Our question is: the effort of the translator’s and maintainers, should it be spent on average to low quality (translated) documentation, or should it focus on have 1 documentation language in excellent quality? Translations are less important these days as more machine translations tools are available and with reasonable to great quality! (What do you think?)

We should either facilitate an easy translatable documentation flow while maintaining the technical quality or drop some languages and make the view documentation languages shine.
My suggestion before we give up translations; use markdown instead of restructure text:

• Most issues (build warnings) in the translation are caused by crowdin (machine suggested) translations to break the mark up.
• Links to anchors are broken, /Sample-Setup.html#required-components as the heading Required Components is translated it will always break all the link to the anchor.

To give translated documentation another shot. -My suggestion is do 2 actions;

• convert the restructured text to markdown and use untranslated header anchors.
• Language independent anchors

convert to markdown

Pro Markdown

• Supported by crowdin (rst is not)
• Links are harder to break. (not space sensitive)
• No accidental translation of the rst directive
• MD is easier to understand by users (rst is less common and more technical). google trends
• md is less technical. rst is more technical a documentation language for programming languages. We don’t use any of the advanced features.

Cons Markdown

• Migrating files is an effort. Converter
• Some pending translations might get lost in the migration.
• Some rst feature are missing. work around

Are we missing some pros and cons… let us know.

Migration Actions:

• Sync/upload translations from GitHub
• Gradual migration, one file at the time (and all its translations).
• Approve pending translations.
• Merge translation branch into master
• Fix build warning and link warning in rts files
• Use Pandocs to convert to markdown (no wrap)
• Fix heading level, and page title
• Use standard formatter
• Commit and merge into master
• Upload new files with translation to crowdin.

Fix heading anchors

Page URLs are not translated. However all heading anchors are auto-generated which is awesome, however if you work with translations, anchors changed with the heading is translated.

For language independent anchors in markdown we can leverage eval_rst

```eval_rst
.. _settings-aaps:
```
  
## Settings in AAPS (English) / ## Instellingen in AAPS (Dutch)

TODO check alternative MyST syntax, seems simpler (heading_id)=

Actions:

• After migration to markdown
• Add the manual anchor
• Let crowdin propagate the added link into the translated files
• The old anchors will stay available.
• Clean up translated anchors (one at the time :( )
• Consider removing the auto generated headings....

Please share your thoughts on links, quality, md vs rst and translations…

Crowdin don't understand them and corrupts the translations.

In the documentation, when dealing with maxIoB the example used as a starting point says : max daily basal...
This can be understood as total daily basal ...
Could be rephrased with something like max hourly basal rate...
Issue also raised in OpenAPS

This is something that tricked me when going through the objective 3.
If you set a 90 % profile, the example states that the ISF is devided by 0.9, which is not a 10 % increase last time I checked...
And the example image in the docs is also wrong (2.2/0.9 != 2.4) its more like 2.44444. (yes you have 2 digits on some numbers). but an 10 % increase would be: 2.2+0.22=2.42.

Yes it's close to a 10 % increase, but lots of us are engineers, and we will have a hard time with this question since you'd have to answer wrong to get it right! Probably more than me that had to check the source-code to get this right ;)

To prove the point, lets take something larger: if you set a profile switch of 60 % (not even sure its posible) and an ISF of 10.
10/0.6 = 16,6667, but a 40 % increase of 10 is 14.0!

Or am I misinterpreting this on some way?

I find the surreptitious advertising for mevita.de in the image of the basal rate profile inappropriate and would like to suggest to remove the image, or to remove the link.

this page please - https://androidaps.readthedocs.io/en/latest/Hardware/Eversense.html

Please PR on the branch rework-project.

I did not understand the explanation of the prediction lines under "section e".
At https://androidaps-altguide.readthedocs.io/en/latest/pages/Screenshots.html?highlight=section%20e I find this better explained.
Would it be OK to add this description here?

The URL for the git-download is just for Windows users. So I suggest:

• mention that it is just for windows

• or use https://git-scm.com/download/ instead of https://git-scm.com/download/win for anyone.

• or use the URLs for Windows AND MacOS, Linux-Users should know how to do it

• I would mention that also step 3 (Path to get executable) is an example for windows as (git).exe is for windows, so MacOS-users with just few knowledge might not know why .exe is written there

• also in the first sentence: "Let Studio know where is git.exe located: File - Settings" 'git.exe' is mentioned, which is just for Windows, not MacOS/Linux

File:
https://github.com/openaps/AndroidAPSdocs/blob/master/docs/EN/Installing-AndroidAPS/git-install.rst

xDrip+ can now also collect from the G7 directy, this works even for AAPS master. However xDrip+ does also not provide smoothing so a warning should be given and dev or beta1 recommended for smoothing (same as with patched G7 app)

xDrip+ reference:
https://navid200.github.io/xDrip/docs/Dexcom/G7.html

Discussion on discord:
https://discord.com/channels/629952586895851530/1114551522668322857

Is this ☝️ statement correct?

It seems to be contradictory with section below:

So is it prediction of BG or IOB?

Screenshot to visualise the problem, when TBR at 0% BG should rather rise not fall, right?

(from NS with OpenAPS mode)

Few suggestions to improve the form:

1. from: "Smartphone Brand & Model"
   to: "Smartphone Brand & Model & Provider: ie Samsung S22+ Tmobile"

2)in CGM choices add: G7
in CGM software add: BYODA-DIAKEM (G7 only)

3. in AAPS version: allow to enter the complete string so we can specify which version of dev specifically like "3.2.0-dev-i"

4. consider adding a question about "AAPS client display on watch Brand, Model,: Samsung GalaxyWatch4"

HI there,

I wondered about the status of reverse engineering the Insight protocol. Is there any news or plan?

Kind regards

Is it ok to add links to the wiki, do we have to be careful about the Content, is there anything in the docs, that says 'we do not guarantee for the Content in the links'?

The main content of this Wiki is licensed under "GNU AFFERO GENERAL PUBLIC LICENSE - Version 3, 19 November 2007".

When creating this repository there has happened that MIT-License was set. This means we would have to ask all (unknown) authors of the old wiki. IMHO the easiest way would be to go back to the original license.

@danamlewis , @typ1-brods , @jotomo , @scottleibrand , @Lillycgm , @roppenheimer, you have been doing edits in the meantime. Are you ok with going back to the original license?

I.E. https://androidaps.readthedocs.io/en/latest/DE/benutzung/setups.html
@typ1-brods

Hi, there is a dead link in this section which should be pointing to more info about AMA in the OpenAPS documentation

https://androidaps.readthedocs.io/en/latest/Usage/Open-APS-features.html#advanced-meal-assist-ama

The dead link:
https://openaps.readthedocs.io/en/latest/docs/walkthrough/phase-4/advanced-features#advanced-meal-assist-or-ama

Some quick googling returned this, is that the content that is missing? :

https://newer-docs.readthedocs.io/en/latest/docs/walkthrough/phase-4/advanced-features.html#advanced-meal-assist-or-ama

Referencing this thread in the AndroidAPS FB group...
https://www.facebook.com/groups/AndroidAPSUsers/permalink/2616961101858624/

The AAPS documentation (right now) indicates that NSClient is intended to be used for remote monitoring and downloads all data (IOB/COB included) that is uploaded to NS by the master phone.

It appears that this is not actually the current behavior of the NSClient app, which performs its own IOB/COB calculations based on the settings configured in the app. If these settings differ from the master phone (or OpenAPS rig, in my case) in any way, then the results of the calculations performed by the NSClient app will produce different results from the master phone, potentially leading to a life threatening situation if a remote caregiver treats based on data displayed in the NSClient app.

These two screenshots show the mismatch in IOB.

These two screenshots illustrate the mismatch in COB (as reported by the OpenAPS rig) and the COB reported by NSClient.

Phone used for "Sample setup" is no longer supported (S7 is running Android-Version 8.0)

See: Sample setup: Samsung S7, Dana RS, Dexcom G6 and Sony Smartwatch
https://androidaps.readthedocs.io/en/latest/Getting-Started/Sample-Setup.html#sample-setup-samsung-s7-dana-rs-dexcom-g6-and-sony-smartwatch

AAPS version 3.0

Users need a way to archive objectives achieved, independently to preferences.

As is now, restoring objectives can only be done by way of importing an old settings file.
Preferences from the old settings file are most likely outdated and will overwrite current settings.

nightscout/AndroidAPS#2549

Has been merged into dev, which changes the view of the pod history by adding the total amount insulin delivered

Note: This amount is the amount that is in the reservoir on POD connection, so when a bolus is issued, it's the ammount before the bolus was issued.

Question: If I where to pick this up which branch to target?

In the latest version of the docs maxSMBBasalMinutes is descriped as followed:

This is an important safety setting. This value determines how much SMB can be given based on the amount of basal insulin in a given time, when it is not covered by COBs.

https://androidaps.readthedocs.io/en/latest/EN/Usage/Open-APS-features.html

According to
https://github.com/MilosKozak/AndroidAPS/blob/08730dfc9a73fa9317a162a41c66a7bc9d2bb387/app/src/main/assets/OpenAPSSMB/determine-basal.js#L1048-L1054

maxSMBBasalMinutes is only used if mealInsulinReq >= iob_data.iob.
Otherwise maxBolus seems to be calculated with the hardcoded value 30.

This means to me if all COBs are covered with Insulin, SMBs can't be bigger than maxSMBBasalMinutes = 30 regardless of what value is set in maxSMBBasalMinutes.

The icons in the English versions are already hard to see:
https://androidaps.readthedocs.io/en/latest/Configuration/OmnipodEros.html#icons

The German page does not display the Icons at all:
https://androidaps.readthedocs.io/de/latest/Configuration/OmnipodEros.html#symbole

Tested with Desktop Mozilla FF.
Using a mobile phone, the icons are NOT visible in English as well!