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

Amazfit Neo/PineTime reports incorrect number of steps in log #352

Open
jmlich opened this issue Mar 24, 2024 · 1 comment
Open

Amazfit Neo/PineTime reports incorrect number of steps in log #352

jmlich opened this issue Mar 24, 2024 · 1 comment

Comments

@jmlich
Copy link
Contributor

jmlich commented Mar 24, 2024

I was checking Amazfit Neo if it shows stored data properly, but it seems there is some glitch (I was sleeping around midnight).
@kirbylife

Also, PineTime doesn't store samples properly. It shows smaller numbers than expected.
In contrary, Amazfit Neo stores huge numbers. btw heart rate monitoring was turned on most of the time. Additionally, some pattern in data can be observed.

phablet@ubuntu-phablet:~$ sqlite3 /home/phablet/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi
SQLite version 3.31.1 2020-01-27 19:55:54
Enter ".help" for usage hints.
sqlite> SELECT timestamp_dt, steps FROM mi_band_activity WHERE timestamp_dt > date('now') ORDER BY timestamp_dt ASC LIMIT 50;
2024-03-24T00:00:00|165
2024-03-24T00:01:00|0
2024-03-24T00:02:00|165
2024-03-24T00:03:00|0
2024-03-24T00:04:00|165
2024-03-24T00:05:00|0
2024-03-24T00:06:00|167
2024-03-24T00:07:00|0
2024-03-24T00:08:00|167
2024-03-24T00:09:00|0
2024-03-24T00:10:00|174
2024-03-24T00:11:00|0
2024-03-24T00:12:00|179
2024-03-24T00:13:00|0
2024-03-24T00:14:00|188
2024-03-24T00:15:00|0
2024-03-24T00:16:00|191
2024-03-24T00:17:00|0
2024-03-24T00:18:00|199
2024-03-24T00:19:00|0
2024-03-24T00:20:00|209
2024-03-24T00:21:00|0
2024-03-24T00:22:00|212
2024-03-24T00:23:00|0
2024-03-24T00:24:00|212
2024-03-24T00:25:00|0
2024-03-24T00:26:00|218
2024-03-24T00:27:00|0
2024-03-24T00:28:00|219
2024-03-24T00:29:00|0
2024-03-24T00:30:00|218
2024-03-24T00:31:00|0
2024-03-24T00:32:00|191
2024-03-24T00:33:00|0
2024-03-24T00:34:00|167
2024-03-24T00:35:00|0
2024-03-24T00:36:00|161
2024-03-24T00:37:00|0
2024-03-24T00:38:00|165
2024-03-24T00:39:00|0
2024-03-24T00:40:00|165
2024-03-24T00:41:00|0
2024-03-24T00:42:00|165
2024-03-24T00:43:00|0
2024-03-24T00:44:00|165
2024-03-24T00:45:00|0
2024-03-24T00:46:00|167
2024-03-24T00:47:00|0
2024-03-24T00:48:00|167
2024-03-24T00:49:00|0

In my case it is usually expected values are 3000-9000 in this period of time.

sqlite> SELECT date(timestamp_dt), device_id, sum(steps) FROM mi_band_activity WHERE timestamp_dt > datetime('now', '-7 days')  GROUP BY date(timestamp_dt), device_id ;
2024-03-18|3863507743|348
2024-03-19|3863507743|728
2024-03-20|3863507743|846
2024-03-21|3863507743|922
2024-03-22|1400944805|42963
2024-03-23|1400944805|75017
2024-03-24|1400944805|43252
@kirbylife
Copy link

I'll take a look regarding the problem with the Neo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants