@Meidlmarkus It’s been a while since I worked on this. From memory, doing this over SSH has extra complexity (probably to do with the DISPLAY environment variable). Honestly, I’ve wanted to rework this to be headless for a while but haven’t had the capacity to do so.
My advice would be to try and run it locally if possible.
Also if anyone can verify that the modification to package.json is a fix, then I will merge this in: https://github.com/m-roberts/MMM-Fitbit2/pull/10/files
@En-TACT Check that you have the correct client ID, client secret, and the redirect URI.
@En-TACT I am the author. What is your setup? Are you trying to run it headlessly?
@En-TACT init.sh just runs npm install (ref), so you can try the various StackOverflow suggestions to see if they help.
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 :thinking_face:
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!
@goldyfruit said in MMM-Fitbit2:
@Vizulize It would be great it you could allow the issue creation on GitHub, this will be easier to contribute and raise issue. :)
Done!
@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 😄
@aunrea This should work - I have 2 accounts on my MagicMirror and they have worked together for some time. What are you seeing?
@Stoffbeuteluwe This should not be the case. What are the logs saying?
@aunrea The module is returning the sleep data from the web API directly, which can be found here: https://dev.fitbit.com/build/reference/web-api/sleep/
You can see in the code here that the result that is returned is “totalMinutesAsleep”:
https://github.com/m-roberts/MMM-Fitbit2/blob/master/python/get_data.py#L194
Beyond that, I am not sure why it is adding time to your records. Apologies!