06-06-2024 05:20
06-06-2024 05:20
I am creating a Fitbit app that detects user motion like: stationary, running, walking, driving, etc. and updates the UI as per the motion type like CoreMotion for Watch OS, SO how can I get the user motion type in Fitbit, is there any inbuilt package for this like we have CoreMotion in Watch OS?
06-06-2024 06:17
06-06-2024 06:17
Hello @surajNEPAL and welcome to the Community. I moved your post to one of the developer forums, where I think you might get more help. There’s a 50-50 chance that I chose the right one.
Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.
06-07-2024 05:07
06-07-2024 05:07
Hi @surajNEPAL - there is an accelerometer API which you can use to detect movement. The Versa and Sense also have a Gyroscope API
Fitbit Versa 3 and Fitbit Sense have embedded GPS receivers which is documented here
Many have a barometer which can give you other sensor information.
The main link for sensors is here
By combining information you may be able to work out the type of activity, as there is no feature I have seen to get the activity type information in real time which is probably what you are looking for. If not have a look in the Web forum
Author | ch, passion for improvement.
06-09-2024 19:38
06-09-2024 19:38
can you help me to calculate the motion type based on the 3 axes ( x,y, and z) of the accelerometer sensor, or there is already mathematical equations or methods to covert these 3 values into motion type?
06-09-2024 20:39
06-09-2024 20:39
@surajNEPAL - haven't seen any published information if you want to emulate what the OS does to determine activities.
Factors like similar change over time, heart rate change, dominant wrist setting, personal details (height, weight, age) how results repeat, duration of cycles, position dependence, etc. may be involved in evaluating activitiy type.
You may derive some activities by trial and error that work for you consistently but it is likely to be quite a complex undertaking and eventually even battery draining in operation if done at the app level without access to internal system resources.
Author | ch, passion for improvement.