SELECT TIMESTAMP, DEVICE_ID, RAW_INTENSITY, STEPS, RAW_KIND, HEART_RATE, SLEEP,DEEP_SLEEP, REM_SLEEP FROM HUAMI_EXTENDED_ACTIVITY_SAMPLE WHERE TIMESTAMP >= 1736119950000 ORDER BY TIMESTAMP ASC;
If I take the WHERE out, I get results back but the timestamps are in seconds, not milliseconds.
The time bound used in that query was originally in seconds, but it was changed in b9b587806015ec1f19f0055f00d5896391feea35 along with a bunch of other Huami tables.
Checking the DB associated with my Bip 3, the table's empty.
I think, having found that one of the other tables was ms, I probably assumed they all were.
Activity
07-Jul-25 14:55
Poking around shows that the issue is this query
If I take the
WHERE
out, I get results back but the timestamps are in seconds, not milliseconds.07-Jul-25 14:58
The time bound used in that query was originally in seconds, but it was changed in b9b587806015ec1f19f0055f00d5896391feea35 along with a bunch of other Huami tables.
Checking the DB associated with my Bip 3, the table's empty.
I think, having found that one of the other tables was
ms
, I probably assumed they all were.07-Jul-25 15:01
This is fixed by