Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing temperature data when the sensor log interval is too small (1, 2 or 3 minutes) #289

Open
marthakeezy opened this issue Jan 31, 2024 · 5 comments
Labels
Bug Something is borken Discussion This issue needs further discussion Priority: Must Have The product will not work without this

Comments

@marthakeezy
Copy link

Describe the bug

When changing the default log interval for a sensor to 1, 2 or 3 minutes, and leaving it running for a bit, some logs will be missing. I have tested 1 type of interval a day, and the shorter the interval is, the more logs are missing. 4 and 5 minutes do not have any issues.

To Reproduce
Steps to reproduce the behavior:

  1. Connect your sensors to the CCA and leave it running for a night. Make sure to change the default interval to 1 or 2 or 3 minutes.
  2. Once some time has passed, open your omSupply and go under Cold Chain -> Monitoring -> Log
  3. Depending on the interval you set, you will see some records are missing
  4. For example, if you are testing with 2 sensors, there should be 2 entires per interval - Sensor one at 01:01:01; Sensor 2 01:01:01, Sensor 1 02:01:01; Sensor 2 02:01:01 etc

Expected behavior

No logs should be missing even when the intervals are close to each other, e.g. 1 minute

Smartphone (please complete the following information):

  • Device: Samsung Galaxy Tab A8
  • OS: Android 13
  • Version: omSupply 1.6.00 and CCA 0.5.6

Additional context
I noticed, that when testing with 2 or 3 minutes, usually only one log is missing. For example, if the last log was at 23:45:01, and there is one missing at 23:48:01, then the next displayed will be 23:51:01. When testing with a 1 minute interval, more than 1 entry at a time can be missing. For example, if the last entry was at 15:01:00, then the missing ones can be 15:02:00, 15:03:00 and 15:04:00. The most I noticed was 4 entries missing at a time, which means the sensor was logging information every 4 minutes instead of 1 minute (sorry, many letters here!).

Also, because there is no way to export omSupply log records, I went through the data manually and compiled it all in a spreadsheet here: https://docs.google.com/spreadsheets/d/10oj-YuxQUUXJkZvTMpSQ9megC66YlUt59ZHEl2Z5NFE/edit#gid=1418206080

@marthakeezy marthakeezy changed the title Missing when the sensor log interval is too small (1, 2 or 3 minutes) Missing temperature data when the sensor log interval is too small (1, 2 or 3 minutes) Jan 31, 2024
@adamdewey
Copy link
Collaborator

Nice spot @marthakeezy !

@adamdewey
Copy link
Collaborator

Possibly related to #270 ?

@fergie-nz fergie-nz added Bug Something is borken Discussion This issue needs further discussion labels Feb 18, 2024
@AnushaUp
Copy link

@adamdewey @marthakeezy I've seen this and too frequently for 1 minute interval.

Image

@marthakeezy
Copy link
Author

@AnushaUp nice one! Yes, for 1 minute interval I got the results of 142 records missing in 4 hours. Sometimes the sensor would miss 4 records before logging in next one.

@mark-prins mark-prins added the Priority: Must Have The product will not work without this label Mar 4, 2024
@mark-prins
Copy link
Contributor

To look at after advertising packets is done.
Export on omSupply?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is borken Discussion This issue needs further discussion Priority: Must Have The product will not work without this
Projects
None yet
Development

No branches or pull requests

5 participants