vote_log

On 13 November, the vote_log feature was implimented. This is primarily used for debugging

What it does

Each fitbit will store a local file called voteLog.txt which stores an integer value of the number of votes given since cozie was installed. Everytime a vote is given, this file is read, incremented by one, and sent to Influx with the variable name vote_log.

How you can use it

If there is something causing data-loss, then the vote_log variable will be a sure way to identify it. Each vote should increment vote_log by 1 in the influx database. If there is data loss, then we should see patterns such as 1, 2, 4, 5, meaning that vote 3 was lost.

Suspicions of data loss

There are some suspicions of data loss occuring:

1. Power Saving modes of phones are causing the a blockage in the external API calls causing the data to get stuck on the phone and then lost

2. The data is being transferred from the watch to another device. If someone, lets say PJ was logged into the fitbit app as [email protected]. PJ then gives his watch to another participant, say cresh05, and onboards her with the login [email protected]. If PJ doesn't log-out of his fitbit app, everytime PJ comes close to cresh05, then the fitbit may connect to PJ's fitbit app, transfer the data there, causing a data loss to cresh05.