LEPU_DEVICE_NAMES
The names the Lepu/Viatom family advertises, as its own SDK matches them.
Taken from the vendor's getDeviceModel, a 732-line cascade of substring checks that is
the whole of how that SDK decides which product it is talking to. The order there matters,
because 27 of these names are a prefix of another - BP2 of BP2A, BP2T, BP2W and
three more - so a check that ran in the wrong order would bind a BP2W as a BP2 and poll it
with an opcode written for different hardware.
It is that function's vocabulary, not a catalogue of everything the vendor sells: a few
products - the ER3 and the M12 among them - are identified elsewhere in that app and never
reach this list. The first-word names below are compared against the complete first token of
the advertisement, not as an open-ended prefix: O2 must not claim O2Ring, and BabyO2
must not claim BabyO2N.
They are held here as a flat vocabulary rather than an ordered cascade, because
lepuNameMatch derives the exclusions from the list itself. Adding a name automatically
narrows every name it extends, which an ordered list would leave to whoever inserted it.
Kind: Constant or variable
Package: @ovok/native
Import
import { LEPU_DEVICE_NAMES } from '@ovok/native/bt-management';
TypeScript shape
readonly string[]
This symbol has no call parameters.
Learn the workflow
Continue with Bluetooth for the workflow context and examples.