Appearance
Devices and what they report
Which hardware Omaya decodes out of the box, what each model measures, and the standard reading names to use when you teach it a new one.
Read out of the platform
This page is generated from the code that runs your instance, so it cannot drift from what the platform actually does.
A model in this list needs no configuration: add the device, pick the model, and its packets are decoded. A model that is not in this list is not a dead end — Sensor onboarding (/admin/manage/device/onboarding) walks you through teaching Omaya a new one from its own live packets, and the reading names in the last section are the vocabulary that page expects.
What each model reports
Kind is how Omaya treats the device: a tag moves with a person or an asset and is positioned; a sensor sits still and reports readings; a beacon only advertises so other things can be positioned against it; a tracker carries its own GPS; an actuator is switched rather than read.
| Vendor | Model | Slug | Kind | Reports |
|---|---|---|---|---|
| Minew | MSR01-A | minew_msr01a | sensor | people_count, radar_position |
| Minew | MSR01-B | minew_msr01b | sensor | enter_exit |
| Minew | MWC01 | minew_mwc01 | tag | presence, battery, button_press, motion_trigger |
| Minew | S1 | minew_s1 | sensor | presence, battery, temperature, humidity |
| Minew | E7 | minew_e7 | beacon | presence, battery |
| Minew | MS50-SF | minew_ms50sf | sensor | presence, battery |
| Minew | MTB02 Paper-battery Asset Tag | minew_mtb02 | tag | presence, battery |
| Minew | E8 Beacon | minew_e8 | beacon | presence, battery |
| Minew | i7 Beacon | minew_i7 | beacon | presence, battery |
| Minew | Beacon (other / generic) | minew_beacon | beacon | presence, battery |
| Dusun | BGX | dusun_bgx | beacon | presence, battery |
| Dusun | DSB-F1 | dusun_dsb_f1 | sensor | presence, battery |
| Dusun | DSB-D50B | dusun_dsb_d50b | beacon | presence, battery |
| Kontakt | ID14 Beacon | kontakt_id14 | beacon | presence, battery |
| Kontakt | Tough Beacon 2 | kontakt_tm | beacon | presence, battery |
| Kontakt | Bracelet Tag S18-3 | kontakt_us | tag | presence, battery |
| Milesight | WL-101 | milesight_wl | sensor | presence, battery |
| Milesight | VS133 Counter | milesight_vs133 | sensor | people_count |
| Milesight | TS201 Temp/Humidity | milesight_ts201 | sensor | temperature, humidity, battery |
| Mikrotik | TG-BT5-IN | mikrotik_tbt5in | tag | presence, battery |
| Mikrotik | TG-BT5-HL | mikrotik_tbt5hl | tag | presence, battery |
| Mikrotik | TG-BT5-Mini | mikrotik_tbt5mi | tag | presence, battery |
| Moko Smart | LW001-BG Pro | moko_lw001 | tracker | gps, battery |
| Moko Smart | LW004-PB | moko_lw004 | tracker | gps, battery |
| Moko Smart | MK-B5 | moko_mkb5 | beacon | presence, battery |
| Moko Smart | SO2R | moko_so2r | sensor | distance, battery |
| Moko Smart | H4 Pro | moko_h4pro | sensor | temperature, humidity |
| Moko Smart | B2 Button | moko_b2 | tag | presence, battery, button_press |
| Moko Smart | BeaconX Pro BXP-C | moko_bxp_c | beacon | battery |
| Moko Smart | BeaconX Pro BXP-D | moko_bxp_d | beacon | battery, button_press |
| Moko Smart | BeaconX Pro BXP-DH | moko_bxp_dh | sensor | battery, temperature, humidity |
| Moko Smart | H2 BeaconX Pro | moko_h2 | beacon | battery |
| Moko Smart | H5 BeaconX Pro | moko_h5 | sensor | battery, temperature, humidity |
| Moko Smart | BeaconX (other / generic) | moko_beaconx | beacon | battery |
| Aqara | Presence MultiSensor FP300 | aqara_fp300 | sensor | presence, temperature, humidity, illuminance, battery |
| Aqara | Motion Sensor P1 | aqara_p1 | sensor | presence, battery |
| Aqara | Wall Switch AK059 | aqara_ak059 | actuator | — |
| Home Assistant | Home Assistant (Generic) | home_assistant | — | presence, battery, temperature, humidity, illuminance, co2, energy_kwh, power_w |
| External | External people counter (API) | external_counter | sensor | people_count |
| Other | Other / Generic | other | — | — |
A dash under Reports means the model declares nothing. Such a device is still registered, positioned and tracked — it just contributes no readings, either because there is nothing to read (an actuator is switched, not measured) or because it is a generic entry standing in for hardware nobody has identified yet: aqara_ak059, other.
Some device types are created by apps rather than chosen by hand, so they are not in the picker above but you will see them on device records: toilet_supply (sensor), toilet_occupancy (sensor), toilet_stall (sensor), toilet_safety (sensor), staff_badge (tag).
The capability names
Every name that appears in the Reports column above, and how many models declare it. Most of these are descriptive — they tell you what to expect from a model, and the device page shows them as chips. Two do real work: people_count and radar_position are how Omaya knows a device can count people in a zone, which is what makes that zone report an occupancy figure from the sensor rather than from the BLE tags it can see.
| Capability | Models |
|---|---|
battery | 33 |
button_press | 3 |
co2 | 1 |
distance | 1 |
energy_kwh | 1 |
enter_exit | 1 |
gps | 2 |
humidity | 7 |
illuminance | 2 |
motion_trigger | 1 |
people_count | 3 |
power_w | 1 |
presence | 23 |
radar_position | 1 |
temperature | 7 |
Standard reading names for a custom decoder
When you teach Omaya a device it does not know — through Sensor onboarding, or by writing a decoder spec by hand — each field you pull out of the payload is given one of these names. Use the standard name and the reading lands in the right report with the right unit; invent your own and it is stored, but nothing knows what to do with it.
| Reading | Unit | Stored as |
|---|---|---|
battery_percent | % | battery |
button_pressed | — | button_press |
co2 | ppm | sensor |
current_a | A | energy |
distance_mm | mm | distance |
energy_kwh | kWh | energy |
humidity | % | sensor |
illuminance | lux | sensor |
noise_dba | dBA | sensor |
occupied | — | presence |
people_count | people | people_count |
power_w | W | energy |
pressure | hPa | sensor |
temperature | °C | sensor |
voltage_v | V | energy |
Field types
How to read the bytes a reading comes from. be/le is byte order — big-endian first, which is the common case for BLE manufacturer data; check the datasheet when a value comes out absurdly large.
uint8 · int8 · uint16_be · uint16_le · int16_be · int16_le · uint24_be · uint24_le · int24_be · int24_le · uint32_be · uint32_le · int32_be · int32_le · float32_be · float32_le · bool · bit · bits · hex · ascii