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