nightscout / nightscout/AndroidAPS

Feature Request: Add Total Daily Dose (TDD) as a Condition in Automation Events

Open
#4,209 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Kotlin
Stars
1.2k
Forks
6.4k
Avg merge
2d 7h
Merged PRs (30d)
19

Description

Currently, AndroidAPS’ Automation-Event editor does not offer Total Daily Dose (TDD) as a trigger condition. I maintain three separate basal profiles—strong, normal and weak—because my insulin sensitivity varies widely throughout the day. Even with UAM and DynISF managing dynamic adjustments, I still need to manually switch profiles when my TDD changes:

  • When my TDD rises above a certain threshold, I must activate the strong profile.
  • When my TDD falls below a certain level, I switch to the weak profile.

Requested Feature:
Expose TDD in the “Condition” dropdown so that users can create rules of the form:

If Total Daily Dose IS_GREATER_THAN 40 U → Switch to Strong Profile  
If Total Daily Dose IS_LESS_THAN 20 U   → Switch to Weak Profile

By allowing DynISF to start from basals already adjusted for the current TDD, the system could automatically select the most appropriate profile and better accommodate large swings in individual insulin sensitivity.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the AndroidAPS Automation-Event editor and its Condition dropdown, then trace how existing numeric conditions and profile-switch actions are represented. Done means users can select TDD, compare it with a threshold in insulin units, and use the result to switch profiles.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.