Read the statement by Michael Teeuw here.
Fitbit
-
@Hellangel1987
Glad to hear you got it working.I’m just trying to get the module to refresh more often. Not sure how to go about it.
You probably could get your weight data in too, you’d need to contact the creator of the module for that.
-
@olliewarren411 said in Fitbit:
Yes, you can change the refresh interval. In the script MMM-fitbit.js you’ll see
start: function() { Log.info('Starting module: ' + this.name); this.sendSocketNotification('SET CREDS',this.config.credentials) this.sendSocketNotification('GET DATA', 'intial'); this.fadeSpeed = 500; // Schedule update interval. var self = this; setInterval(function() { self.updateData(); }, 60*60*1000); },
change the 60 x 60 x 1000 to an interval of your choosing. Just be careful to to refresh too often as you’ll get emails from FB telling you that you are pulling too much data. I think (and I’d have to check tonight) that I have mine set to 15 x 60 x 1000.
-
Thanks! works perfect. I’ve copied your set up so it refreshes the data every 15 mins.
-
I was getting invalid redirect_uri during the setup process. (sudo python setupAccess.py)
But now It’s working for me, great module !
-
Anyway to get around having to run the setupAccess.py everyday/every other day to keep the tokens fresh?
Since I have to stop the MM from running, run the script to get new token, start MM again, it gets kind of annoying. I also run my Pi w/o keyboard/mouse so when I need to refresh the tokens I have to connect them.
I thought about adding a cron job to stop the MM, run the script and start MM, thoughts? Since the script leaves a browser window open, can the cron job kill it or is there a way to have the python script close the window when done?TIA
-
dont know exactly but im also interested in your cronjob solution, can you inform us about your steps ? im tired getting every day that setupaccess working :(
-
@Hellangel1987 said in Fitbit:
dont know exactly but im also interested in your cronjob solution, can you inform us about your steps ? im tired getting every day that setupaccess working :(
I haven’t done it, yet, just thinking about it since it was mentioned. I think I’ve narrowed down the issue though:
{"message": {"401": {"errors": [{"message": "Access token expired: eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiI0NU5QMzUiLCJhdWQiOiIyMjdRVjkiLCJpc3MiOiJGaXRiaXQiLCJ0eXAiOiJhY2Nlc3NfdG9rZW4iLCJzY29wZXMiOiJ3aHIgd3BybyB3bnV0IHdzbGUgd3dlaSB3c29jIHdhY3Qgd3NldCB3bG9jIiwiZXhwIjoxNDcxNzAxNjYzLCJpYXQiOjE0NzE2NzI4NjN9.VvLWtyYYvVShgrWC4UOVMXfdv0uiy7Nic-WDj7RMiKA. Visit https://dev.fitbit.com/docs/oauth2 for more information on the Fitbit Web API authorization process.", "errorType": "expired_token"}], "success": false}}, "type": "error"} {"message": "Getting a new access token", "type": "status"} {"message": "Error getting new access token", "type": "error"} {"message": {"400": {"errors": [{"message": "Refresh token invalid: 4292cf037821b9441122e432bdd92a238fac61028dfbd6be982d2e6b73474c32. Visit https://dev.fitbit.com/docs/oauth2 for more information on the Fitbit Web API authorization process.", "errorType": "invalid_grant"}], "success": false}}, "type": "error"}
First got an “expired” token notice, then the process tries to get a new token (possibly using the “refresh” token, I’m not sure at this point). But refresh tokens are valid for one use only, so it’s like the updated token is getting updated in the token.ini file.
-
Also interested with the cron mechanism, the module could execute the setupAccess process once a day and trigger a reload on the gui ?
I’m using vnc to connect remotely on the RPI since i don’t have mouse/keyboards connected.
-
3 days of syncing without an issue. Not sure what changed, I did pull the latest dev code for MM but made no changes to the fitbit module.
(of course now that I’ve said this, it will error out during the day :) ) -
Had my first issues in a while last night. The problem was that my router lost internet connection and when it was restored the tokens were expired. I ran the setupAccess.py and got new tokens.
Seems that there should be a better way to reset the module on restart, like if the tokens are expired, the go get new ones.