I want to get icons and formatting sorted before I add it publicly. However, you can try it here: https://github.com/m-roberts/MMM-Fitbit2
Also, I need to handle credentials from the config, as currently they are hard-coded into files that are used by the Python Fitbit library. This needs to be handled from the config directly, to support multiple Fitbit accounts on one setup.
MMM-Fitbit2 builds upon MMM-Fitbit (which appears to be abandoned), and displays (even more of) your Fitbit data!
It is allows you to display the following data (progress tracked against goal unless mentioned)
This project was a fairly significant re-write, with its long-term vision of being able to display data just as complicated as on the official Fitbit dashboard, where possible. See the README for more information!
This module is currently in need of testing - I am withholding adding it to the Wiki page until it has been used by multiple people for at least a few days without issues.
Worth considering increasing your swap file size while you try to determine the cause. That will start using file system space as memory.
Change CONF_SWAPSIZE=100 to #CONF_SWAPSIZE=100in /etc/dphys-swapfile and reboot.
Then you can check on the swap size used, and see if it’s a memory leak that just keeps on growing, or something else.
@Fr8Trayne I’ve got the following currently supported data:
I need icons for water, food and weight, and some assistance with formatting before I will post it publicly. Perhaps I will create a new forum post for this.
@mattx38 As the client secret a password, it is blocked from printing. Just paste the secret into your terminal and press enter - it will work.
This is separate to what @bhepler raised re: SSH. Actually, you can run all of the commands over SSH, but you will need to log in to your Fitbit account in a browser on the Pi in order to generate your access tokens. Alternatively, you can run the script on another machine, generate the tokens and then transfer them onto the Pi (if you have no way to do things on your Pi’s display).
@johntech Huh? This is referring to RAM memory, not hard drive space. I was writing to explain how you can extend the swap by using filesystem space to prevent the system crashing from running out of RAM.
Sorry if there was any confusion - I actually manage a Raspberry Pi operating system, so am very familiar with the tools and techniques available.
I have posted the module here. I am looking for testers!
@mkufner24 I have explained what I am doing to retrieve sleep data in an earlier post. Beyond that, I’m not sure!
I’m glad to hear you’re enjoying the module though 
I haven’t tried this and I haven’t looked at the code in a while, but I think you can just comment out this line to hide the progress bars:
@richmp95 - last I checked, this still works. Why does it need ‘reviving’?
If you would like to have extra features, I am open to suggestions and contributions.
@jjw Running init.sh inside the MMM-Fitbit2 folder should take care of installing the dependencies for you.
@jjw A quick Google search for this error suggests to me that it is related to your node/npm versions, but I can’t offer any more input than that I’m afraid!
@sdetweil It is defined as 0.5.0 in the dependencies.
To be honest, the Python should be rewritten in JS anyway. Perhaps I will get around to doing that in the near future 
Then this issue goes away!
@davidgeo
This is currently not exposed to the user via the config.json (that feature is tracked here).
However, you can change this option to “US” in your installed module directory.
For more information about how units are handled by the Fitbit API, check out the unit system information detailed here.
@goldyfruit said in MMM-Fitbit2:
@mkufner24 Same, sleep time is inaccurate.
Unfortunately, this is what is returned from the Fitbit API. If you can figure out how to produce the data you want from what is returned from the API, then I am happy to take a look!