Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

null argument error #5

Open
aMellifera1 opened this issue Jun 22, 2016 · 1 comment
Open

null argument error #5

aMellifera1 opened this issue Jun 22, 2016 · 1 comment

Comments

@aMellifera1
Copy link

Collin, I am trying out your module for the first time, and I have everything installed correctly it seems. The code executed all the steps including the creation of a blank csv file; however, I received the error in the attached screen shot that there was a null argument somewhere. I know there is data on the fitbit on the date I queried because I can get my day-long values from the fitbit website. Any ideas?
scrnshot

@CollinChaffin
Copy link
Owner

Hi aMellifera1,

You currently to my knowledge cannot get your intraday values at all via the Fitbit website. This error indicates if you look at the runtime exception that for some reason, the query was successful but that there was actually no HR data returned for that date.

So, my guess is, if you have not had another date return successfully yet, is that you did not properly authorize all the data TYPES as shown in the one screenshot I posted for setup. This is once you set the authorization, you must allow the oAuth workflow type to include HEARTRATE data. There simply is no easy way for me to test whether a partial oAuth approval has taken place since the return is technically a SUCCESS even though there are still restrictions on what's allowed (how can the script know what's really up there to gain access to pull down, etc.).

So, please redo the setup and if possible snap a screenshot of the oAuth approval screen allowing the data types. Note that depending on what browser you're using, I've seen different ad-blockers cause various issues with both the required popups and also partial oAuth approvals until temporarily disabled.

Try that and then let me know how it looks.

Collin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants