@aunrea For now, to get Imperial measurements, remove this line:
https://github.com/m-roberts/MMM-Fitbit2/blob/master/python/get_data.py#L96

@Arno-Strasbourg
Seems like it’s possible to get a low-resolution status of device battery levels from the Fitbit API.
It also seems as though the Python library supports this endpoint.

However, because it returns a list of devices, targeting the right one may prove to be a little more complicated.
Not much good if the battery level relates to a second tracker that you aren’t actually wearing!
I could possibly do it based on the device with "type": "TRACKER" that has the most recent "lastSyncTime", but I will need to think about it.

@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).

Hi all (notably, @chsp) - turns out that there was a bug if you had selected the “weight” resource and did not have any weight data for the last 30 days. I have pushed a fix for this, so hopefully you don’t end up with “Loading…” any more!

@johntech no worries! “Memory” is often confused in this context. Hope you learned something 😁

@Fr8Trayne Are you SSH’d in to your machine? You need to be on the machine locally, so that the browser can open, and you can log in to Fitbit in the browser.

This is all great feedback though - thanks for being patient!

@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.

@Fr8Trayne It’s a password entry step - it won’t show up in the terminal. Perhaps that is not clear enough, or just isn’t necessary! Just paste and hit ENTER to continue.

@sdetweil Ok, I see what you’re saying. I’ve added it to the extending functionality GitHub project board. Seems quite minor though.

Progress % is from 0-100. You have a start point, an end point, and are between the 2. “9% over” and “2% under” are not records of progress.

If I recorded 9% over as 109%, and rounded to 100%, it would indicate that your progress towards your target resting heart rate (RHR) is 100%. 2% under would mean that you are at 98% “complete”.

They may be percentages, but progress is absolute, and your calculations are relative. It would make more sense to keep the RHR data and create a better representation of it (e.g. a histogram - which is what Fitbit actually does).