nightscout / nightscout/AndroidAPS

SMS - bugs

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

Nobody has claimed this yet.

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

Description

Image

Summary

There are two issues with SMS command responses:

  1. BG returns inconsistent / incorrect glucose-related data
  2. Pump is unable to retrieve pump status and always fails

Actual behavior

1. Incorrect / inconsistent BG reporting

When sending the BG SMS command multiple times, the returned values are inconsistent between requests.

Examples from the attached screenshot:

  • First response:
    • BG: 115, Delta: 6.0 MGDL, IOB: 0,23U (Bolus: 0,54U Baza: -0,31U), COB: 0g
  • Later response:
    • IOB: 0,15U (Bolus: 0,38U Baza: -0,23U), COB: --g

The problem is that repeated BG requests return different and sometimes incomplete values, including one response with missing BG and invalid COB: --g.

2. Pump status cannot be read

When sending the Pump SMS command, the response is:

Odczyt statusu nie powiodl sie

This happens repeatedly and pump status cannot be retrieved at all.

Expected behavior

  • BG should return consistent and valid current glucose-related data for each request
  • Pump should return the current pump status instead of failing

Steps to reproduce

  1. Open the SMS conversation used for AndroidAPS remote commands
  2. Send BG
  3. Send Pump
  4. Repeat both commands several times
  5. Observe:
    • inconsistent / incomplete BG output
    • pump status read failure every time

Frequency

  • BG inconsistency: reproducible across repeated requests
  • Pump status failure: happens every time

Impact

  • Remote BG reporting cannot be trusted
  • Remote pump status monitoring is unavailable

Screenshot

Attached: screenshot showing inconsistent BG responses and repeated Pump status read failures.

Environment

  • AndroidAPS version: 3.4.X.X
  • Pump: Equil
  • Remote control method: SMS commands
  • Android 15

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 tracing the Android SMS command handlers for BG and Pump, then reproduce both commands repeatedly in the reported AndroidAPS 3.4.X.X, Equil, and Android 15 environment. Done means BG responses consistently contain valid glucose-related values and Pump returns the current pump status instead of failing.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.