Fitbit

[cambor]

@achilles Thanks for getting back to me. Yes that step worked and now I have figured out I was in the wrong directory when running sudo pip install -r python/fitbit/requirements.txt. I was trying to do that step out of sequence before following the preceding steps in the Setup instructions.

I am facing another issue now though: I’ve added the example config to my config but when I try to run the MagicMirror it throws an error
“Please create a config file…If you get this message while your config is already created, you config file probably contains an error…”

I saw there was issues with the brackets after “config” in line 4 of the example config file and people have suggested replacing the [ with { and again on line 19 ] with } but it still doesn’t work.

Now I see some people are saying there are issues with the fitbit API (https://github.com/SVendittelli/MMM-fitbit/issues/15) but those comments are from January so I’d be interested to hear about how you got yours working so recently and if you can see where I might be going wrong.

Thanks a lot!

[Achilles]

Every time I have got that error, it has been because I have something wrong with the syntax: Curly braces incorrect, double quotes where there should be single quotes, comma missing, etc. Does every open bracket or curly brace have a corresponding closing bracket or curly brace?

[bhepler]

@cambor - Easiest thing to do is to copy the example config.js.sample file to config.js and modify it incrementally. After each modification to the file, you can reload the mirror and make sure you haven’t introduced an error.

If you like, you can post the MMM-fitbit section of your config.js here and we’ll see if we spot anything. Be sure to use the markdown features of the forum to aid in troubleshooting.

[Achilles]

Has anyone’s Fitbit module stopped working recently? For some reason, mine is not displaying anything anymore–just 0s. This started about a week ago…

[bhepler]

@achilles - That happened to me about three weeks ago. I had to get back on the mirror and run the setupAccess.py script to authorize with fitbit.com again. After that it started working again. You’ll probably find an indication of what’s up in the pm2 logs.

Fitbit is weird in that they insist that you use their website to authenticate. You can’t get an API key for you app. Your app must incorporate a means to go to their website to use their interface and then return.

[Achilles]

@bhepler - At the risk of sounding stupid, you have to go back and run through the commands again and get to setupAcess.py to get Fitbit to work again?

[bhepler]

@achilles - Almost. You just have to run the setupAccess.py again. So get onto your Pi directly, open up a terminal window, stop your MagicMirror process, and run the sudo python setupAccess.py or whatever the command is. It will open up a browser window with the FitBit login page. Log in with your credentials, wait for the confirmation screen and then close the browser.

Restart your MagicMirror process and it should start pulling from the FitBit service.

[Achilles]

@bhepler Thanks! That helped. I guess this means I can look forward to doing this every month or so?

[bhepler]

@achilles - I don’t actually know. Mine was up for months with no issue. It may be that a prolonged period without the module refreshing the tokens is the determining factor. It may even be something on Fitbit’s end expired all of the tokens.

[mmille40]

This module looks great, unfortunately the installation is giving me the most difficulties from any module so far, I’m completely new to anything coding so I’m learning as I go. My first problem was trying to install the python-shell dependency. I get this message in my terminal:

pi@matt:~ $ npm install python-shell
npm WARN saveError ENOENT: no such file or directory, open ‘/home/pi/package.json’
npm WARN enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’
npm WARN pi No description
npm WARN pi No repository field.
npm WARN pi No README data
npm WARN pi No license field.

• python-shell@1.0.4
  updated 1 package in 2.932s

What am I doing wrong here?