Active zone minutes in my clock face?

[Geest]

The Fitbit app recently introduced 'active zone minutes' which I like a lot and would like to include in my clock face.

However, I can only find activeMinutes in the User-activity section of the Device API.

Where do I find the 'active zone minutes'?

[Geest]

Just saw that the Today app (by swiping up on the Versa) shows the active zone minutes so there should be a way to read them in the Device API. But I can't find it in the documentation.

[MarioDings]

 Don’t understand . I don’t see active “zone” minutes anywhere.(versa 2). I know they exist. I think it’s the same.  Maybe that active zone only starts after 10 minutes and is only available on a few (older) devices.

whats your definition or suggestion?

[Gondwana]

I think AZM is a new feature which is still being rolled out.

[unagisan]

Looking for this as well. Looks like the phone app will only track Active Zone Minutes while my Fitbit will only display Active Minutes.

[BarryCope]

My App started tracking “Active Zone Minutes” instead of active minutes a week ago. For my Ionic, the only clock face that I have seen that tracks Zone minutes is the Moment clock face, which switched automatically from active to zone minutes. I wish there were more Ionic clock faces that tracked zone minutes, since that seems to be the new standard. 

[JonFitbit · Accepted solution]

Active Zone Minutes is replacing Active Minutes. SDK 4.2 will allow you to utilise AZM in your clocks and apps. All details will be in the announcement for SDK 4.2 which is coming very soon!

[unagisan]

@JonFitbit why would you guys release the new firmware that forces the new feature when you don't even have support for displaying it on the device?

[JonFitbit]

Not sure I follow? Active Minutes still exists, but AZM is the new replacement. AZM is only displayed on devices that have support for it, i.e. 4.2

We can't release the SDK until the firmware rollout reaches 100% availability.  There's always a brief period while the staged firmware rollout is in progress where some devices don't have the update.

[MarioDings]

Found this in the help:

[MarioDings]

This afternoon I received a new update for Versa 2 with the new active zones.

I’m very curious . 🙂

[Giampi71]

@JonFitbit 

I have a different opinion: you should release the SDK ahead of firmware rollout to give time to the developers to update/developer their app in time of the new release.

The same for Sense/Versa 3 that when they will be available won't have clockfaces/apps to make use of the new features.

[oldftbtusr]

Found a fitbit clock called Simple that shows azm on the Versa 2.

[PatTheDog]

I think that clock face is made by Fitbit themselves. Presumably they already are developing with the 4.2 SDK. Over on the Versa forum there was message from a support rep that the 4.2 rollout is complete, so my guess is we'll see 4.2 SDK very soon.

[unagisan]

Most of the clock faces are made by third-party developers. Hence the reason it's impossible for clock faces to display Active Zone Minutes. Makes zero sense to force the firmware update before releasing the SDK. But my Fitbit Ionic has since died (after a week) and Fitbit is refusing to replace it so I'm out of this argument I suppose. 

[Boxit379]

I just used activeMinutes and it showed active zone minutes too.

[Boxit379]

This one? https://gallery.fitbit.com/details/6555426c-6798-40fb-b13b-d3b98f5956c2

If it's the one you're talking about, I actually made it myself 🙂

I didn't need to change any code to make it work, activeMinutes still gets your active zone minutes.

[Geest]

How do you do that?
My clock face also shows activeMinutes and in most cases this is a
different number than the Active zone minutes in the Fitbit app since they
use different formulas to calculate.

[PatTheDog]

@Boxit379 I was actually thinking of this one https://gallery.fitbit.com/details/0000145c-0000-4000-8000-000000f17b17 

Anyway, I'll give activeMinutes a try and see what I get 🙂

[PatTheDog]

Hmm, the Today app on my Versa is showing 105 Active Zone Minutes, but local.activeMinutes just returned 100.

Looks like we just need to sit tight until the 4.2 SDK is released.