Fitbit

[kckndrgn]

@chengstark,
Possibly the internet connection was lost during a refresh, this will cause the tokens to get out of date.
I stop MM, re-run the “setupAccess.py” script using credentials from the file, then re-start MM and all is fine, until the next time I have an internet hiccup.

[chengstark]

@kckndrgn thanks, will try

[Vendittelli]

I have released a fix for the .ini files problem in the latest version on GitHub. You’ll need to delete your tokens.ini and credentials.ini files and remake them (as well as performing a git pull) for the fix to be effective.

[darrene]

For some reason, I’m getting calories displayed, but nothing else. @Vendittelli, does the module have any additional debugging or logging that I can turn on to look through? - I’m not getting any issues in dev mode or in the terminal - it seems that’s the only data I get. When I look in the dev console, I see:

writing steps (data/goal): 0/10000
Writing floors (data/goal): 0/10
writing calories out (data/goal): 1664/2930
writing distance (data/goal) 0/5
writing activeminutes (data/goal): 0/30
writing sleep (data/goal): 0/480

When I clear down my tokens.ini and re-run the setupaccess.py, I can see the scope information for the token results includes u’social’, u’settings’, u’profile’, u’sleep’, u’activity’, u’heartrate’, u’weight’, u’nutrition’, u’location’
if that’s helpful…
As a slight aside: @olliewarren411, would you mind sharing your ‘vertical-layout’ css? I’m still trying to get my head around cascading style sheets!

[Vendittelli]

@darrene That is weird. The module is pretty unadvanced so I don’t have proper debugging, unfortunately. The scope looks correct, are you sure you have synced your Fitbit today? It would explain why calories are displayed as they are calculated automatically so you don’t need to sync them.

[darrene]

Thanks for the quick reply @Vendittelli - that could be the answer. I didn’r realise the calories were calculated like that - as you say, it’d certainly explain it.

I’ll have a look into it. If it comes to it, I’ll recreate the app - I seem to remember there are a list of tick boxes for the fitibit attributes and on the pi browser, it was really difficult to tell whether or not they were ticked!

[moshinh]

I am having the same issue Greppie had at some point.

Next thing is, that setupAccess.py doesnt work or I did not understood how it does. The script start a server at port 8080 but if fitbit redirects to it I get an error that the page is not accessible. However I copied the token from url an put it into tokens.ini. There’s only an access token and no refresh token, right?

I am having this same problem, I get a 404 error on the attempt to get my tokens. I was able to pull the token from the URL, but have no way to get the refresh. Please help, im so close! Thanks for all of your effort.

When I click the autogenerated authorization URL, I am redirected to http://127.0.0.1:8080/ and throw this 404 error.

404 Not Found

Missing parameters: state

Traceback (most recent call last):
File “/usr/local/lib/python2.7/dist-packages/cherrypy/_cprequest.py”, line 670, in respond
response.body = self.handler()
File “/usr/local/lib/python2.7/dist-packages/cherrypy/lib/encoding.py”, line 217, in call
self.body = self.oldhandler(*args, **kwargs)
File “/usr/local/lib/python2.7/dist-packages/cherrypy/_cpdispatch.py”, line 67, in call
raise sys.exc_info()[1]
HTTPError: (404, ‘Missing parameters: state’)

This is what I see when I run setupAccess.py

Is this part normal?

CherryPy Checker:
The Application mounted at ‘’ has an empty config.

Full output:

pi@mirror:~/MagicMirror/modules/MMM-fitbit/python $ sudo python setupAccess.py
Get credentials from credentials.ini? (Y/N)
n
Would you like to enter them manually now? (Y/N)
y
Enter client id:
227WT7
Enter client secret:
9fe3da42b609603a67e7730aad3ca96a
[25/Oct/2016:11:20:26] ENGINE Listening for SIGHUP.
[25/Oct/2016:11:20:26] ENGINE Listening for SIGTERM.
[25/Oct/2016:11:20:26] ENGINE Listening for SIGUSR1.
[25/Oct/2016:11:20:26] ENGINE Bus STARTING
CherryPy Checker:
The Application mounted at ‘’ has an empty config.

[25/Oct/2016:11:20:26] ENGINE Started monitor thread ‘Autoreloader’.
[25/Oct/2016:11:20:26] ENGINE Started monitor thread ‘_TimeoutMonitor’.
[25/Oct/2016:11:20:27] ENGINE Serving on http://127.0.0.1:8080
[25/Oct/2016:11:20:27] ENGINE Bus STARTED
127.0.0.1 - - [25/Oct/2016:11:20:40] “GET / HTTP/1.1” 404 1206 “” “Mozilla/5.0 (X11; Linux armv7l) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.91 Safari/537.36”

[frog]

I have the same issue but I think the problem is earlier in the install

Well I’m having an even earlier problem in installing the dependencies:

pi@Mirror1:~/MagicMirror/modules/MMM-fitbit $ npm install python-shell

returns:

/home/pi/MagicMirror/modules
└── python-shell@0.4.0 

npm WARN enoent ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/package.json'
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/MagicMirror/modules/node_modules/node_helper/package.json'
npm WARN modules No description
npm WARN modules No repository field.
npm WARN modules No README data
npm WARN modules No license field.

The python-shell is clearly not installing.

[tismepaulo]

I’m also having the same issues as @moshinh and @frog during installation. Has anyone been able to get this working?

[frog]

@tismepaulo Actually, I got it working by firstly not using ssh and running this directly on the display using a terminal and secondly not using sudo. Populated the tokens.ini with the results from the results of the script - and changed the access of the tokens.ini file to 666 - re-ran again the setupAccess.py and it said all was good.

having said that - while I get the authorisation page from Fitbit, I got zero values on the MM. The fitbit account page says that I have access, but initially no data comes through… Next thing I did was running getData.py (in the python directory) I do get a good response:

{"message": "credentials.ini exists", "type": "status"}
{"message": "Reading from credentials.ini", "type": "status"}
{"message": "Read of credentials.ini successful.", "type": "status"}
{"message": "credentials.ini exists", "type": "status"}
{"message": "Reading from credentials.ini", "type": "status"}
{"message": "Read of credentials.ini successful.", "type": "status"}
{"message": "tokens.ini exists", "type": "status"}
{"message": "Reading from tokens.ini", "type": "status"}
{"message": "Read of tokens.ini successful.", "type": "status"}
{"message": "Making API call", "type": "status"}
{"message": "API call okay", "type": "status"}
{"message": "Tokens valid", "type": "status"}
{"values": {"data": 4684, "goal": 10000}, "resource": "steps", "type": "data"}
{"values": {"data": 0, "goal": 1}, "resource": "floors", "type": "data"}

So I think it is at least reflecting accurately now what the fitbit site is showing for steps, but is incorrect for distance - still showing 0 (maybe because I’m using KM not miles?)