Vibration normalisation

[Guy_]

Using Nudge, Nudge-max or Bump.

Is there an established or anyone using an algorithm to generate a normalised vibration sensation across all watches from the same program?

Ie. Simulate the same level of intensity/duration to compensate for hardware/firmware differences.

Currently the Versa always produces a consistent and detectable vibration and is by far the best, and the one to emulate on the others, because

The Versa 2 seems also consistent, but somewhat more feeble.

The Versa 3 / Sense barely produce any vibration, even on the Strong setting, not only that, it gets progressively worse as the battery level decreases.

[Guy_]

Has anyone had any success with this calling of Vibration on OS 5?

The available patterns from the documentation are:

"alert"
"bump"
"confirmation"
"confirmation-max"
"nudge"
"nudge-max"
"ping"
"ring"

The calling structure seems to be

vibration.start(Name, Repeat, Time, Strength, Ramp);

where:

Name (A pattern name),
Repeat (0-6, 7=infinite),
Time (ms) (5ms granularity),
Strength (1-7, 0=off),
Ramp "yes" to ramp to next point

[JonFitbit]

It's just the name.

import { vibration } from "haptics";
vibration.start("ring");

https://dev.fitbit.com/build/reference/device-api/haptics/

[Guy_]

Thanks Jon, but it's not enough to detect the vibration, and it's only for use in issuing an alert.

[Guy_ · Accepted solution]

This throws some light on the reason for the poor vibration.