10-21-2017 02:03
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
10-21-2017 02:03
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I need my calories goal for my watchface and I tried to call it with userActivity.goals.calories.
I always get the value 25377, but (in my case) it should be 3029. The other values (distance, steps, elevationGain, active Minutes) from userActivity.goals are correct.
Where is my mistake? Any ideas?
Thans in advance!
Answered! Go to the Best Answer.

Accepted Solutions
11-14-2017 13:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


11-14-2017 13:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Sorry, the fix didn't make it into the build, but it's definitely in the next one.

10-21-2017 11:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


10-21-2017 11:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Is the goal definitely configured in your account, and have you done a sync since setting it?

10-21-2017 12:10
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
10-21-2017 12:10
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
have definitely synced several times after setting it.

10-22-2017 16:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
10-22-2017 16:01
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I see similar behavior. My goal is set to 2500 (and synced):
var goal = userActivity.goals["calories"] console.log("cals " + goal)
[5:38:08 PM]cals 19789
I sync'd it to 3029 and see this:
[5:58:10 PM]cals 23976

10-22-2017 21:10 - edited 10-22-2017 21:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

10-22-2017 21:10 - edited 10-22-2017 21:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I was just trying to implement a goal setting on my watchface and encountered this also.
After some experimenting I found that dividing the goal by 8.8776 and rounding to the nearest whole number solved the issue for me.
I'm not sure where 8.8776 comes from...
In your case, it looks like 7.1955 would be what you would use. Something whacky is definitely going on.

10-27-2017 08:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
10-27-2017 08:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Any news on this???
IMHO, this must be somehow related to my code, since the goals are handled correctly in the original Fitbit watchfaces, but not in my watchface.
My code is available at https://gitlab.com/private-software/fitbit-clearbeam-watchface/

11-06-2017 08:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

11-06-2017 08:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I am getting the same issue. My goal via phone is 3140; my watch thinks it's 21,287.
Also it thinks my goal is 100 floors!

11-06-2017 08:58
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


11-06-2017 08:58
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Some of the goals are being returned with the wrong unit type, it's fixed in the forthcoming update.
11-06-2017 09:03
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

11-06-2017 09:03
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Great! I've commented my bodged fixes and will revise once they are fixed on your end!

11-12-2017 12:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
11-12-2017 12:49
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I've updated to the latest version, but this issue is still present.
What are the submitted unit types? I thought it could be kJ instead of kcal for the calories, but the conversion is not correct. In my case:
3029 [kcal] x 4,184 [kJ/kcal]= 12673,3 [kJ] and not 25377 [whatever?]...
My elevation goal is 10, but the device gives 100.
In consideration of publishing our watchfaces, this is quite dissatisfying...

11-14-2017 13:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


11-14-2017 13:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Sorry, the fix didn't make it into the build, but it's definitely in the next one.

