nightscout / nightscout/AndroidAPS
[3.0-Beta5] Eros beeps at unexpected moments without traceable alarm/alert
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
Using Eros I heard an uexpected beep-beep (the same beepsound alert to warn when the pods expires).
The timing was strange:
Expiration reported by Pod screen: 13-11-2021 19:38
The beeps happened around (did not really log the precise timing, it can be +/- 10 minutes off):
12-11-2021 17:40
12-11-2021 18:40
12-11-2021 19:40
12-11-2021 20:40
When renewing the Pod screen after a beep there was immediate contact with the Eros, but no alarm or alert reported.
The beeping stopped as unexpected as it began, and the Eros ran 76 hrs without further issues.
I attached the log file of the relevant time period.
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 reviewing the attached AndroidAPS log for the reported beep times and compare them with the Pod screen expiration and alert state. Trace the Eros beep and alert handling paths, then reproduce or explain the unexpected beeps and add coverage or diagnostics showing that beeps correspond to a traceable alarm or alert.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100