nightscout / nightscout/AndroidAPS
[Enhancement Request] Automation - make steps count for longer periods available
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
I'm loving the inclusion of Steps Count in the automation conditions. Thank you, @tdrkDev !
But I'm hoping that the measurement duration could be increased beyond the current 3-hour maximum period.
My most obvious use case would be that if I have had an active day, I want to be able to set a weaker profile overnight.
This would be required regardless of whether the exercise had occurred in the last 3 hours or not.
The most important extra addition for me would be the total step count for current calendar day, if possible.
Ideal would be to choose between 5m, 10m, 15m, 30m, 60m, 3h, 6h, 12h, 24hr, or calendar day (starting from midnight). If for some reason you don't have access to the calendar day step count, then 18hr would be a workable subsitute.
Thank you for considering!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Steps Count automation condition and its current duration choices. Determine how longer periods, especially the current calendar day, are represented, then verify that automation can select the requested durations and that the resulting step counts are correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100