A few weeks ago, my Fitbit (one of my new favorite devices) died.
Not died, as in bricked; my battery died.
That was a bit surprising, as I am signed up for low battery notifications. Turns out, I did get a notice – in an email. Problem was, I wasn’t checking my email that day.1
The next day, I went back to the Fitbit website to sign-up for SMS notifications; unfortunately, Fitbit doesn’t provide a low battery notification via SMS.
So, I built my own, using a handful of AWS services (Lambda, SNS, API Gateway, and DynamoDB) and exposed Fitbit APIs.
So far, it works well. After subscribing to the service, I got an introductory note telling my my battery status. A few hours later, I received a second notice – letting me know that my battery was low.
I’ve made the service available on the site – http://darianbjohnson.com/send-fitbit-low-battery-notification-via-sms/. Feel free to test out the service (you can opt out any time my removing access through your Fitbit account).
I’ll share the code and my logic in a later post. Maybe the Fitbit engineers will read this and incorporate SMS functionality in their devices.
Related Posts
- Working Demo
- Part 1 – Overview
- Part 2 – Authentication Flow (coming Fri, Feb 19)
- Part 3 – Notification Flow (coming Mon, Feb 22)