Open ukmoose opened 8 years ago
This is being deprecated as we speak. Are there any plans to update the code for this node?
Well that 6 months flew by... will see what I can do.
Just wondering if there's any joy with this? Being a relatively recent joiner of the Fitbit dev community I can't use OAuth 1.0 and would love to be able to use the node
Anything coming? Just getting started with node red and fitbit ... this killed about 2 hours of my time before I finally figured out that the node is oauth 1.0a and not 2.0 :( ... guess I really should have read closer.
I just got my new fitbit today for a project on node-red. Just realized that this node no longer is compatible. Any plans to update this node?
Is there any way gents to extract data from my fitbit using node red , node red is still using oauth 1.0 which is no longer supported by fitbit
Seems to be possible using HTTP GET requests...
https://dev.fitbit.com/docs/activity/#get-daily-activity-summary
Unfortunately too much uni work to be able to look into it properly but let us know if you find something!
On 1 May 2017 at 11:49, amarzouk1977 notifications@github.com wrote:
Is there any way gents to extract data from my fitbit using node red , node red is still using oauth 1.0 which is no longer supported by fitbit
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/node-red/node-red-web-nodes/issues/130#issuecomment-298317983, or mute the thread https://github.com/notifications/unsubscribe-auth/ASq5MGtpClktd8gghHDR4YdrdcNo8bruks5r1bilgaJpZM4GNY-6 .
I've just received 8 identical Emails from fitbit ( I guess they really wanted to tell me!) to let me know that they are moving from OAuth1.0 to OAuth2.0
"Applications should upgrade to OAuth 2.0 by March 14, 2016. OAuth 1.0a support will be removed from the Fitbit Web API six months from now on April 12, 2016. Documentation for using OAuth 2.0 with the Fitbit Web API is available at https://dev.fitbit.com/docs/oauth2 ."