SVE-42 Test Event Postponed. For more information click HERE.

Members Meeting Postponed. For more information click HERE.


HOME   >   LWM2M   >   RESOURCES   >   REGISTRY   >   RESOURCES

Resources

To register OMA LwM2M Resources, please raise a GitHub issue at OMA LwM2M Registry - README file.

ResourceID Classes

Category Resource ID Range Description Operations
Common Resources 0 - 2047 Common resource defined inside Objects. Inside of an Object the resourceIDs must be unique but it can be reused in different Objects. -- --
Reusable Resources 2048 - 26240 Resources registered by companies, standards organisations or alliances. Note: ResourceID is finally allocated by OMNA Staff. Private registrations are not allowed
Private Resources 26241 - 32768 Private resource range, no registration is necessary and open to re-use. -- --

OMNA LwM2M Resources

OMA LwM2M Registry (Resources)

Show:
Submitter
  • ATT4
  • AVSystem3
  • GSMA9
  • IPSO102
  • IoT Connectivity Alliance5
  • OMA16
  • OpenLX SP Ltd1
  • South East Water1
  • South East Water Corporation32
  • Vaisala4
Name
  • Active Power Calibration1
  • Alarm Auto Clear1
  • Alarm Clear1
  • Alarm Clear Operator1
  • Alarm Clear Threshold1
  • Alarm Maximum Event Count1
  • Alarm Maximum Event Period1
  • Alarm Realtime1
  • Alarm Set Operator1
  • Alarm Set Threshold1
  • Alarm State1
  • Alarm loudness1
  • Altitude1
  • Analog Input Current Value1
  • Analog Output Current Value1
  • Application Type1
  • Averaging Time Period1
  • Avg Load AdjPct1
  • BandIndicator1
  • Battery Percentage1
  • Bitmap Input1
  • Bitmap Input Reset1
  • Busy to Clear delay1
  • Calibrate Coefficient1
  • Calibrate Offset1
  • Calibration Offset2
  • CellID1
  • Clear Display1
  • Clear to Busy delay1
  • Clip1
  • Colour1
  • Compass Direction1
  • Contrast1
  • Counter1
  • Criticality Level1
  • Cumulative Time1
  • Cumulative active power1
  • Cumulative reactive power1
  • Current Calibration1
  • Current Position1
  • Current Time1
  • Decrease Input State1
  • Delay Duration1
  • Detected CO2 percentage1
  • Digital Input Counter1
  • Digital Input Counter Reset1
  • Digital Input Debounce1
  • Digital Input Edge Selection1
  • Digital Input Polarity1
  • Digital Input State1
  • Digital Output Polarity1
  • Digital Output State1
  • Digital State1
  • Dimmer1
  • Down Counter1
  • Duration1
  • Duration In Min1
  • Duty Cycle1
  • Element Description1
  • Event Code1
  • Event Identifier1
  • Event Type1
  • Fractional Time1
  • Fractional Timestamp1
  • Host Device Manufacturer1
  • Host Device Model Number1
  • Host Device Software Version1
  • Host Device Unique ID1
  • Increase Input State1
  • Instantaneous active power1
  • Instantaneous reactive power1
  • Interval Change Configuration1
  • Interval Collection Start Time1
  • Interval Delivery Midnight Aligned1
  • Interval Historical Read1
  • Interval Historical Read Payload1
  • Interval Period1
  • Interval Start Offset1
  • Interval UTC Offset1
  • Last Delivered Interval1
  • Latest Delivered Event Time1
  • Latest Payload2
  • Latest Recorded Event Time1
  • Latest Recorded Interval1
  • Latitude1
  • Level1
  • LogClass1
  • LogData1
  • LogDataFormat1
  • LogDataIncremental1
  • LogDataIncrementalMinimumSendInterval1
  • LogStart1
  • LogStatus1
  • LogStop1
  • Longitude1
  • Max Limit1
  • Max Measured Value1
  • Max Measured active power1
  • Max Measured reactive power1
  • Max Range Value1
  • Max Range active power1
  • Max Range reactive power1
  • Max X Coordinate1
  • Max X Value1
  • Max Y Coordinate1
  • Max Y Value1
  • Max Z Value1
  • Measured Particle Size1
  • Measurement Quality Indicator1
  • Measurement Quality Level1
  • Min Limit1
  • Min Measured Value1
  • Min Measured active power1
  • Min Measured reactive power1
  • Min Range Value1
  • Min Range active power1
  • Min Range reactive power1
  • Min X Value1
  • Min Y Value1
  • Min Z Value1
  • Minimum Off-time1
  • Multi-state Input1
  • Multi-state Output1
  • Numeric Latitude1
  • Numeric Longitude1
  • Numeric Uncertainty1
  • ObjectInstanceHandle1
  • ObjectVersion1
  • Off Time1
  • Oldest Recorded Interval1
  • On time1
  • On/Off1
  • Power factor1
  • RSSI1
  • Reactive Power Calibration1
  • Remaining Time1
  • Reset Cumulative energy1
  • Reset Min and Max Measured Values1
  • Sample Frequency1
  • Sensor Type1
  • Sensor Units1
  • Sensor Value1
  • Sensor Warm-up Time1
  • Set Point Value1
  • Smoke Sensor State1
  • Start1
  • Start Time1
  • Status1
  • Stop1
  • TBD6
  • Text1
  • Timer Mode1
  • Timestamp1
  • Transition Time1
  • Trigger1
  • Uncertainty1
  • Up Counter1
  • Velocity1
  • X Coordinate1
  • X Value1
  • Y Coordinate1
  • Y Value1
  • Z Value1
  • dlEarfcn1
  • pci1
  • plmnID1
  • rsrp1
  • rsrq1
  • subFrameNumber1
  • sysFrameNumber1
Operations
  • 7
  • E15
  • R91
  • RW62
  • W2
Type
  • Boolean13
  • Float62
  • Integer46
  • Objlnk1
  • Opaque7
  • String17
  • Time9
  • Undefined21
  • Unsigned Integer1
Description
4000ObjectInstanceHandleRObjlnkOMAThe 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.
4001ObjectVersionRStringOMALWM2M Object versioning label.
4010LogClassRWInteger255OMA 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
4011LogStartEOMAActions: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.
4012LogStopEOMAActions: 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.
4013LogStatusRInteger8-BitsOMAData 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.
4014LogDataROpaqueOMARead Access on that Resource returns the Data Collection associated to the current Object Instance.
4015LogDataFormatRWInteger255OMA 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 format2 : OMA-LwM2M JSON format3: OMA-LwM2M CBOR format[4..99] reserved [100..255] vendor specific data format
4016LogDataIncremental OpaqueOMALog 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.
4017LogDataIncrementalMinimumSendIntervalRWUnsigned IntegerOMAMinimum 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 177 items