Pebble lies ...

A cautionary tale about relying on technology ...
Yesterday I was updating my Cronometer diary, and noticed that a short walk had given me back almost 700 calories. That seemed a bit high, so I investigated.

I have my Cronometer account being feed by my Apple Health app, which is in turn fed by my Pebble 2 smart watch. More specifically, the watch is feeding caloric data to Health, which then updates Cronometer with my "active" calories (calories burned in excess of my resting caloric burn).

Digging deeper, I saw that Health's idea of what my BMR (base metabolic rate, or resting energy) seemed a bit off. Since it should be based off of my height, weight, and age, I looked to see how it was actually figuring it. Turns out the Pebble feeds it that data, so the Pebble had to be off.

Long story short, the Pebble was convinced that I was 5'11" and weighed 165 lbs. It wouldn't let me change it, either. Apparently I had some sort of a feedback loop going on, because both Pebble and Cronometer were reading from AND writing to Health my height and weight data. I think Pebble just gave up and went with the default, because both Health and Cron were correct.

I was less than thrilled with this revelation ...

I've since updated who can read and write what, essentially providing a one directional flow of height/weight data from Cron (which is where I update such things) to Health, and finally to Pebble. Not in the other direction.

Naturally, this means that my meticulous tracking for the past two weeks has been off, which might explain the lowly half-pound loss last week, but at least the habit is forming ...

Right ...?

... damnit