-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Sensor Data is lost when CCA is running in the background #288
Comments
Logged into omSupply after the weekend and noticed some of the logs were not refreshed → went into the CCA, noticed the time stamp of the last collected reading was 2 days ago for one sensor and 6 hours ago for another sensor. Logged back into omSupply → the logs were there. Switched to CCA, and waited for a few minutes for the time stamp to get updated. I don’t think the issue is in missing data, but in the way the apps get updated to reflect that data. E.g. the data is there and if you give it a few minutes you will see it, but instead the app is not updating as the data gets collected. |
Would like to have a developer recreate the scenario |
This happened to me last night. Lost a few hour's worth of data for 3 sensors. Interestingly the data cuts out about the same time for all 3 sensors but doesn't come back at the same time, they all differ slightly: Data is missing from CCA: Interesting the data is still there on the sensors (thanks @jmbrunskill !): (Ignore the date, it's not stored absolutely on the sensor) |
Sensor dropped off readings: Debug logs: sensor logs: |
Describe the bug
Running CCA in the background overnight - when opened Grafana → CCA → omSupply, discovered one of the sensors lost ~ 10 hours worth of data. See the yellow disrupted line below.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No data is missing, there should be an entry for each log interval, should be able to leave CCA running in the background
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: