OMA LwM2M Registry Capability Classification
Introduction
This page classifies every resource in the OMA LwM2M Registry against the semantic capabilities defined in Stage 2, so you can see directly which capabilities OMA can supply today and where the gaps are.
It is resource-by-resource evidence supporting the OMA Semantic Capability Assessment, which answers the assessment questions capability by capability and documents the assessment baseline and scope. For where this fits in the methodology, see the Methodology Overview.
Status: The classifications in the tables below are a working analysis, not a finalized SIG position. Entries flagged
Candidate Capability, and object range 3410–3429, have not yet had a group review pass. The Confidence column records the classifier's confidence in each call; its scoring scale is not yet documented. Treat this as a draft for discussion, not a settled answer.
Objects Semantic Capability
Every object-specific resource in the OMA LwM2M Registry, classified against the semantic capabilities, with a confidence score and a note explaining the call. Working analysis — not yet reviewed by the group.
LwM2M Registry Capability Mapping
2752 items
Object ID197 values
- 1024251
- 1024318
- 1024432
- 102549
- 1025718
- 102586
- 102624
- 102634
- 102646
- 102657
- 1026615
- 1026715
- 1026815
- 1026915
- 1027015
- 1027115
- 1027215
- 1027315
- 1027415
- 1027515
- 1027615
- 1027715
- 1027815
- 1027915
- 1028015
- 1028115
- 1028215
- 1028315
- 1028415
- 1028525
- 1028815
- 1029015
- 1029116
- 1029216
- 103098
- 1031113
- 1031316
- 103148
- 1037612
- 1037714
- 1037910
- 1048715
- 1048815
- 1048915
- 1049017
- 1049115
- 1049217
- 104934
- 104947
- 104956
- 104964
- 104979
- 104984
- 1049917
- 1050017
- 1050117
- 1050213
- 1050715
- 1050817
- 1050920
- 1053815
- 1053910
- 323
- 320010
- 32015
- 320212
- 32036
- 330013
- 330112
- 330211
- 330312
- 330412
- 330523
- 33067
- 33086
- 33109
- 33118
- 33128
- 331311
- 331410
- 331512
- 331613
- 331713
- 331813
- 331913
- 332013
- 332113
- 332213
- 332313
- 332413
- 332513
- 332613
- 332713
- 332813
- 332913
- 333013
- 33318
- 33329
- 33335
- 333418
- 33357
- 333610
- 333711
- 33387
- 33395
- 334011
- 33419
- 33427
- 33434
- 33445
- 33456
- 334613
- 33475
- 33484
- 33496
- 33508
- 338717
- 338813
- 33896
- 339025
- 339121
- 339215
- 339322
- 339413
- 339513
- 339622
- 339725
- 33986
- 339919
- 34004
- 34017
- 34024
- 34037
- 34047
- 34055
- 34064
- 34075
- 34083
- 341015
- 341116
- 341229
- 341310
- 341415
- 34155
- 341666
- 341714
- 341841
- 34195
- 34201
- 342162
- 342246
- 342315
- 342417
- 34258
- 342618
- 342713
- 342828
- 342917
- 343041
- 343114
- 343227
- 343312
- 343412
- 343527
- 34365
- 34377
- 34383
- 34393
- 344521
- 344612
- 344737
- 344833
- 344916
- 345017
- 34518
- 345210
- 34536
- 345410
- 34557
- 34564
- 345717
- 34589
- 345926
- 34607
- 346111
- 34644
- 414
- 50216
- 50338
- 5094
- 5103
- 67
- 60043
- 60141
- 60213
- 60714
- 79
Object195 values
- 3-Phase Power Meter51
- Acceleration Tamper Alarm15
- Accelerometer11
- Acidity13
- Actuation7
- Addressable Text Display9
- Air quality28
- Altitude13
- Analog Input12
- Analog Output6
- Anemometer16
- Audio Clip5
- Barometer12
- Battery16
- Battery Level Readings15
- Bitmap6
- Buzzer7
- CO Detector16
- Cabinet Controller Manager41
- Cabinet Controller Status43
- Calendar Rule6
- Colour7
- Communications Activity Time Readings15
- Computational Performance13
- Concentration13
- Conductivity13
- Connectivity Monitoring14
- Connectivity Statistics9
- Current13
- Current Logging15
- Current Loop Input9
- Current Loop Output6
- Daily Maximum Flow Rate Readings15
- Data Monitoring14
- Daughter Board Failure Alarm15
- Delivery Schedule6
- Depth13
- Device23
- Device Extension15
- Device Reboot Event15
- Digital Input10
- Digital Output5
- Dimmer4
- Direction9
- Discharge4
- Discharge Alarm17
- Discharge Status17
- Distance13
- Distributed Sensor Group26
- Distributed Sensor Message7
- Edge computing generic condition3
- Edge computing manager5
- Edge computing script7
- Edge computing time condition3
- Electrical Conductivity Alarm17
- Electrical Conductivity Readings15
- Electrical monitor41
- Energy8
- Event Data Delivery4
- Event Profile10
- Fault Code9
- Filling level27
- Fire Alarm38
- Frequency13
- Gas Readings16
- Gas meter15
- Generic Sensor13
- Global Navigation Satellite System41
- Gyrometer18
- Heat / Cooling meter18
- High Temperature Alarm15
- Humidity12
- Illuminance12
- Input Filter7
- Interval Data Delivery4
- Irrigation valve8
- LED color light1
- LPWAN Communication29
- LPWAN Mesh Connectivity37
- LPWAN Mesh Statistics33
- Leakage Detection Configuration27
- Light Control8
- Load13
- Load Control9
- Location17
- Loudness13
- Low Battery Alarm15
- Low Temperature Alarm15
- Luminaire asset14
- Magnetometer10
- Manhole4
- Manhole Cover3
- Measurement Metadata4
- Modem Firmware Update10
- Multi-state Selector4
- Multiple Axis Joystick6
- Noise sensor12
- On/Off switch7
- Outdoor lamp controller66
- Output Filter4
- Parking Sensor14
- Particulates8
- People counter12
- Percentage13
- Periodic Activity12
- Periodic Sensor Sampler7
- Periodic Sensor Upload6
- Photocell5
- Positioner11
- Power13
- Power Control8
- Power Factor13
- Power Measurement23
- Presence11
- Presence Alarm25
- Pressure13
- Pressure Readings15
- Pressure Transient16
- Pressure monitoring sensor13
- Program Function10
- Program Manager17
- Program Monitor9
- Program Scheduler10
- Push button5
- Radar Sensor14
- Rain Gauge12
- Rate13
- Roll over sensor8
- Sensor Alarm4
- Sensor Group Device Capabilities11
- Set Point6
- Shareparkinglot8
- Single-Phase Power Meter18
- Single-phase electrical meter62
- Smoke Alarm5
- Solar Radiation13
- Stopwatch8
- Stream Gauge21
- Temperature12
- Temperature Readings15
- Three-phase electrical meter complement46
- Tilt Alarm15
- Tilt Readings15
- Tilt sensor17
- Time5
- Time Synchronisation Event15
- Time synchronization5
- Timer11
- Traffic Counter27
- Trend Alarm17
- Trend Readings15
- Up/Down Control5
- Valve Alarm17
- VehicleControlUnit32
- Vendor Specific Measurement Quality Reason3
- Voltage13
- Voltage Logging15
- Voltage Transient16
- Water Flow Readings15
- Water Level Alarm17
- Water Level Readings15
- Water Meter Customer Leakage Alarm15
- Water Meter Empty Pipe Alarm15
- Water Meter High Pressure Alarm15
- Water Meter Low Pressure Alarm15
- Water Meter Reverse Flow Alarm15
- Water Meter Tamper Alarm15
- Water Network Leak Alarm15
- Water Tank13
- Water meter17
- Water quality sensor18
- Wet Bulb Globe Temperature17
- oA Basic Control17
- oA Device13
- oA Group6
- oA Logical Colour Light-Point Actuator25
- oA Logical Colour Temperature Light-Point Actuator21
- oA Logical Illuminance Sensor15
- oA Logical Light-Point Actuator22
- oA Logical Presence Sensor13
- oA Logical Push-Button Sensor13
- oA OGC-Security5
- oA Physical Colour Light-Point Actuator22
- oA Physical Colour Temperature Light-Point Actuator25
- oA Physical Illuminance Sensor6
- oA Physical Light-Point Actuator19
- oA Physical Presence Sensor4
- oA Physical Push-Button Sensor7
- oA Receiving Object4
- oA Reporting Object7
- oA Scene7
- oA Status Report Structure4
- uCIFI Generic Actuator10
- uCIFI Virtual Sensor4
- uCIFI data bridge15
Semantic Category5 values
- Domain Semantics547
- Interpretation Semantics262
- Observation Semantics774
- Operational Semantics724
- Unclassified445
Semantic Capability16 values
- Asset Management Context511
- Candidate Capability245
- Fallback Behaviour82
- Infrastructure Output312
- Measurement Quality230
- Network Operability131
- Not Applicable200
- Observation Method116
- Observation Point37
- Observation Scope15
- Operational Context13
- Physical Context4
- Provenance15
- Resource Consumption90
- Service Outcome145
- Temporal Semantics606
Companion Capabilities8 values
- Measurement Quality10
- No Companion Capabilities2421
- Observation Method139
- Observation Point40
- Observation Scope35
- Operational Context4
- Provenance3
- Temporal Semantics110
Confidence3 values
- high1065
- low388
- medium1299
| Description | Companion Capabilities | Note | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| 502 | CO Detector | OMA | 1 | CO Detected | 0 = false (CO NOT detected), 1 = true (CO Detected) | object-specific | Domain Semantics | Service Outcome | No Companion Capabilities | medium | gas-hazard presence is a real-world safety effect the municipality cares about; borderline vs treating it as the sensor's own detection state |
| 502 | CO Detector | OMA | 2 | Ambient CO Value | CO value (in ppm) received for the area. | object-specific | Domain Semantics | Service Outcome | Observation Scope | medium | area-level air-quality reading experienced by people |
| 502 | CO Detector | OMA | 3 | CO Value | Last or Current Measured CO Value (in ppm) from the Sensor. | object-specific | Domain Semantics | Service Outcome | Observation Point | medium | sensor-specific reading of the same hazard quantity as Ambient CO Value |
| 503 | Fire Alarm | OMA | 2 | Ambient Temperature | Temperature for the area. | object-specific | Domain Semantics | Service Outcome | Observation Scope | medium | area-level environmental condition relevant to safety |
| 503 | Fire Alarm | OMA | 3 | Temperature Value | Last or Current Measured Temperature Value from the Sensor. The value 65534 indicates that the Sensor data is not available. | object-specific | Domain Semantics | Service Outcome | Observation Point | medium | sensor-specific reading of the same hazard-relevant quantity as Ambient Temperature |
| 503 | Fire Alarm | OMA | 15 | Ambient Relative Humidity | Relative humidity for the area. | object-specific | Domain Semantics | Service Outcome | Observation Scope | medium | area-level environmental condition |
| 503 | Fire Alarm | OMA | 16 | Humidity Value | Last or Current Measured Humidity Value from the Sensor. The value 0 indicates that the Sensor data is not available. | object-specific | Domain Semantics | Service Outcome | Observation Point | medium | sensor-specific reading of the same quantity as Ambient Relative Humidity |
| 503 | Fire Alarm | OMA | 25 | CO2 Alarm State | 0 = False (CO2 alarm threshold not exceeded), 1 = True (CO2 alarm threshold exceeded). | object-specific | Domain Semantics | Service Outcome | No Companion Capabilities | medium | hazard state affecting occupant safety |
| 503 | Fire Alarm | OMA | 26 | Ambient CO2 Value | CO2 value for the area. | object-specific | Domain Semantics | Service Outcome | Observation Scope | medium | area-level air-quality reading |
| 503 | Fire Alarm | OMA | 27 | CO2 Value | Last or Current Measured CO2 Value from the sensor. The value 0 indicates that the Sensor data is not available. | object-specific | Domain Semantics | Service Outcome | Observation Point | medium | sensor-specific reading of the same quantity as Ambient CO2 Value |
Showing 1 to 10 out of 2752 items
Common Resources Capability Reference
OMA's reusable Common.xml resources (IDs 4000–6057), assessed separately from object-specific resources above.
Some classify consistently regardless of host object; others are context-dependent — their capability depends on
what the containing object measures. Working analysis — not yet reviewed by the group.
OMA LwM2M Common Resources
178 items
Stability3 values
- context-dependent34
- stable110
- unused34
Category5 values
- Domain Semantics14
- Interpretation Semantics9
- Observation Semantics42
- Operational Semantics13
- Unclassified100
Capability13 values
- Asset Management Context12
- Candidate Capability19
- Infrastructure Output10
- Measurement Quality5
- Network Operability1
- Not Applicable13
- Observation Method2
- Observation Point5
- Operational Context4
- Resource Consumption2
- Service Outcome2
- Temporal Semantics35
- Unclassified68
Submitter10 values
- ATT4
- AVSystem3
- GSMA9
- IPSO102
- IoT Connectivity Alliance5
- OMA17
- OpenLX SP Ltd1
- South East Water1
- South East Water Corporation32
- Vaisala4
| Used By | Description | |||||||
|---|---|---|---|---|---|---|---|---|
| 4000 | ObjectInstanceHandle | unused | Unclassified | Unclassified | No Objects | OMA | The object link is used to refer an Instance of a given Object. An Object link value is composed of two concatenated 16-bit unsigned integers following the Network Byte Order convention. The Most Significant Halfword is an Object ID, the Least Significant Halfword is an Object Instance ID. An Object Link referencing no Object Instance will contain the concatenation of 2 MAX-ID values. | |
| 4001 | ObjectVersion | stable | Operational Semantics | Asset Management Context | 3387, 3388, 3389, 3390, 3391, 3392, 3393, 3394, 3395, 3396, 3397, 3398, 3399, 3400, 3401, 3402, 3403, 3404, 3405, 3406 | OMA | LWM2M Object versioning label. | |
| 4010 | LogClass | unused | Unclassified | Unclassified | No Objects | OMA | Define the Log Event Class: 0: generic (default) 1: system 2: security 3: event 4: trace 5: panic 6: charging [7-99]: reserved [100-255]: vendor specific | |
| 4011 | LogStart | unused | Unclassified | Unclassified | No Objects | OMA | Actions:a) Start data collection(DC)b) LogStatus is set to 0 (running)c) DC is emptied (default) or extended according arg'0' value Arguments definitions are described in the table below. | |
| 4012 | LogStop | unused | Unclassified | Unclassified | No Objects | OMA | Actions: a) Stop data collection(DC) b) 1st LSB of LogStatus is set to "1"(stopped) c) DC is kept (default) or emptied according arg'0' value Arguments definitions are described in the table below. | |
| 4013 | LogStatus | unused | Unclassified | Unclassified | No Objects | OMA | Data Collection process status: Each bit of this Resource Instance value defines specific status: 1st LSB 0=running, 1=stopped 2nd LSB 1=LogData contains Valid Data 0=LogData doesn't contain Valid Data 3rd LSB 1=Error occurred during Data Collection 0=No error [4th -7th ] LSB:reserved 8th LSB: vendor specific. | |
| 4014 | LogData | unused | Unclassified | Unclassified | No Objects | OMA | Read Access on that Resource returns the Data Collection associated to the current Object Instance. | |
| 4015 | LogDataFormat | unused | Unclassified | Unclassified | No Objects | OMA | when set by the Server, this Resource indicates to the Client, what is the Server preferred data format to use when the LogData Resource is returned . when retrieved by the Server, this Resource indicates which specific data format is used when the LogData Resource is returned to the Server 0 or Resource not present : no specific data format (sequence of bytes) 1 : OMA-LwM2M TLV format (only container for logs; does not define any semantics for the logs themselve) 2 : OMA-LwM2M JSON format (only container for logs; does not define any semantics for the logs themselve) 3 : OMA-LwM2M CBOR format (only container for logs; does not define any semantics for the logs themselve) 4 : Syslog Format(RFC5424) 5 : Common Log Format(RFC6872) [6..99] reserved [100..255] vendor specific data format | |
| 4016 | LogDataIncremental | unused | Unclassified | Unclassified | No Objects | OMA | Log data collected since the last Send operation described for the LogDataIncremental Minimum Send Interval resource, or since that interval has been set to a positive value if the first Send operation has not yet been performed. The data shall have the same format as the LogData resource, but its collection and emptying is independent from it and from the LogStart/LogStop logic. This resource may only be included in a Send operation payload. Attempting to access it via the Device Management and Service Enablement Interface shall result in generating the Method Not Allowed error. | |
| 4017 | LogDataIncrementalMinimumSendInterval | unused | Unclassified | Unclassified | No Objects | OMA | Minimum number of seconds between consecutive Send operations containing the LogDataIncremental resource. If this resource is zero or not present, then LogDataIncremental shall never be sent in a Send operation. If set to a positive number, a Send operation containing the LogDataIncremental resource shall be performed after the specified number of seconds since the previous one or when a new log information is generated, whichever happens later, and the data collection shall be atomically emptied upon successful delivery. If the LwM2M client is connected to multiple servers, this resource SHOULD be handled independently for each server. |
Showing 1 to 10 out of 178 items