OMNA Lightweight M2M (LWM2M) Object & Resource Registry
OMNA can provide you with an unique Object or/and Resource Identifier: (Object ID) or (ResourceID)

OMA has developed an editor for creating LwM2M Object and Resources.

– The editor can be accessed here here.

– The XML schema used by the editor can be found here.

ObjectID Registry

ObjectID and class of Object is used to provide the format for the Object URN.

Generic Object URN Identifier; it is formated as: urn:oma:lwm2m:{oma,ext,x}:{ObjectID}

Examples:

urn:oma:lwm2m:oma:2; (Access Control Object)

urn:oma:lwm2m:oma:3; (Device Object)

ObjectID Registration Steps

1. Request the pre-registration of one or more ObjectsIDs.

Within 48 hours from receiving a pre-registration request OMNA will send you an email containing the pre-allocated ObjectID(s). You have 7 days to submit the related ObjectID file. If after this period of time OMNA has not received the registration form, the pre-allocated range of ObjectsIDs will return to OMNA for future allocation.

2. Submit the Object DDF file after receiving the pre-allocated ObjectsID.

This form should only be used after OMNA has sent you a notification with the pre-allocated ObjectIDs. OMNA will review the Object DDF file submitted. If there is no issues with the ObjectID(s) OMNA will extract from the submitted file the relevant content as displayed on the tables below.

LWM2M Editor Tool

1. LWM2M Editor Tool – The eLwM2M Tool is an editor provided by OMA to construct Objects & Resources for LightweightM2M Enabler. Guidelines

ObjectID Classes
Category Object ID Range Description
oma-label 0 – 1023 Objects defined by the Open Mobile Alliance
reserved I 1024 – 2047 Reserved for future use
ext-label 2048 – 10240 Objects defined by a 3rd party SDO
x-label 10241 – 32768 Objects defined by a vendor or individual such an object may be either private (no DDF or Specification made available) or public. These objects are optionally private this is indicated at the time to submission.
 

oma-label – Objects produced by OMA
Object ID URN Object Name Object DDF File Object Technical Specification Description
0 urn:oma:lwm2m:oma:0 LWM2M Security LWM2M_Security-

v1_0.xml
OMA-TS-LightweightM2M V1.0 It provides the keying material of a LWM2M Client appropriate to access a specified LWM2M Server. One Object Instance SHOULD address a LWM2M Bootstrap Server. These LWM2M Object Resources MUST only be changed by a LWM2M Bootstrap Server or Bootstrap from Smartcardand MUST NOT be accessible by any other LWM2M Server.
1 urn:oma:lwm2m:oma:1 LWM2M Server LWM2M_Server-

v1_0.xml
OMA-TS-LightweightM2M V1.0 It provides the data related to a LWM2M Server. A Bootstrap Server has no such an Object Instance associated to it.
2 urn:oma:lwm2m:oma:2 Access Control LWM2M_Access_

Control-

v1_0.xml
OMA-TS-LightweightM2M V1.0 It is used to check whether the LWM2M Server has access right for performing a operation.
3 urn:oma:lwm2m:oma:3 Device LWM2M_Device-

v1_0.xml
OMA-TS-LightweightM2M V1.0 It provides a range of device related information which can be queried by the LWM2M Server, and a device reboot and factory reset function.
4 urn:oma:lwm2m:oma:4 Connectivity Monitoring LWM2M_Connectivity_

Monitoring-

v1_0.xml
OMA-TS-LightweightM2M V1.0 It enables monitoring of parameters related to network connectivity. In this general connectivity Object, the Resources are limited to the most general cases common to most network bearers. It is recommended to read the description, which refers to relevant standard development organizations (e.g. 3GPP, IEEE). The goal of the Connectivity Monitoring Object is to carry information reflecting the more up to date values of the current connection for monitoring purposes. Resources such as Link Quality, Radio Signal Strenght, Cell ID are retrieved during connected mode at least for cellular networks.
5 urn:oma:lwm2m:oma:5 Firmware LWM2M_Firmware_

Update-

v1_0.xml
OMA-TS-LightweightM2M V1.0 It enables management of firmware which is to be updated. This Object includes installing firmware package, updating firmware, and performing actions after updating firmware.
6 urn:oma:lwm2m:oma:6 Location LWM2M_Location-

v1_0.xml
OMA-TS-LightweightM2M V1.0 It provides a range of device related information which can be queried by the LWM2M Server, and a device reboot and factory reset function.
7 urn:oma:lwm2m:oma:7 Connectivity Statistics LWM2M_Connectivity_

Statistics-

v1_0.xml
OMA-TS-LightweightM2M V1.0 This LWM2M Objects enables client to collect statistical information and enables the LWM2M Server to retrieve these information, set the collection duration and reset the statistical parameters.
8 urn:oma:lwm2m:oma:8 Lock and Wipe x OMA-TS-LWM2M LockWipe V1.0 This LWM2M objects provides the resources needed to perform the lock and wipe operations
9 urn:oma:lwm2m:oma:9 Sofware Management x OMA-TS-SWMGMT V1.0 This LWM2M objects provides the resources needed to perform software management on the device. Each software component is managed via a dedicated Software Management Object instance
10 urn:oma:lwm2m:oma:10 Cellular connectivity x OMA-TS-LWM2M_

ConnMgmt-

V1_0
It specifies resources to enable a device to connect to a 3GPP or 3GPP2 bearer, including GPRS/EDGE, UMTS, LTE, SMS. For cellular connectivity, this object focuses on Packet Switched (PS) connectivity and doesn’t aim to provide comprehensive Circuit Switched (CS) connectivity management.
11 urn:oma:lwm2m:oma:11 APN connection profile x OMA-TS-LWM2M_

ConnMgmt-

V1_0
It specifies resources to enable a device to connect to an APN.
12 urn:oma:lwm2m:oma:12 WLAN connectivity x OMA-TS-LWM2M_

ConnMgmt-

V1_0

It specifies resources to enable a device to connect to a WLAN bearer.

13 urn:oma:lwm2m:oma:13 Bearer selection x OMA-TS-LWM2M_

ConnMgmt-

V1_0
It specifies resources to enable a device to choose a communications bearer on which to connect.
14 urn:oma:lwm2m:oma:14 Software Component x OMA-TS-LWM2M_SwMgmt-V1_0 The LWM2M software management object enables remote software management in M2M devices
15 urn:oma:lwm2m:oma:15 DevCapMgmt x OMA-TS-LWM2M_ DevCapMgmt- V1_0 It manages the device capabilities of a device e.g. sensors, communication, etc.
16 urn:oma:lwm2m:oma:16 Porfolio LWM2M_Portfolio-v1_0.xml OMA-TS-LWM2M_PortfolioObj-V1_0 Extends data storage of other LWM2M Object Instances in M2M devices, as well as to provide security services for applications associated with this data extension.
17 urn:oma:lwm2m:oma:17 Communications characteristics  
18 urn:oma:lwm2m:oma:18 Non-Access Stratum (NAS) configuration Non-Access Stratum NAS configuration-V1_0.xml  
 

Ext label – Objects produced by 3rd Party SDOs
ID URN Name Owner DDF File Technical Specification Multiple Instances? Description
2048 urn:oma:lwm2m: ext:2048 CmdhPolicy OneM2M X Management Enablement (OMA) Yes
2049 urn:oma:lwm2m: ext:2049 ActiveCmdhPolicy OneM2M X Management Enablement (OMA) No
2050 urn:oma:lwm2m: ext:2050 CmdhDefaults OneM2M X Management Enablement (OMA) Yes
2051 urn:oma:lwm2m: ext:2051 CmdhDefEcValues OneM2M X Management Enablement (OMA) Yes
2052 urn:oma:lwm2m: ext:2052 cmdhDefEcParamsValues OneM2M X Management Enablement (OMA) Yes
2053 urn:oma:lwm2m: ext:2053 CmdhLimits OneM2M X Management Enablement (OMA) Yes
2054 urn:oma:lwm2m: ext:2054 CmdhNetworkAccessRules OneM2M X Management Enablement (OMA) Yes
2055 urn:oma:lwm2m: ext:2055 CmdhNwAccessRule OneM2M X Management Enablement (OMA) Yes
2056 urn:oma:lwm2m: ext:2056 CmdhBuffer OneM2M X Management Enablement (OMA) Yes
3200 urn:oma:lwm2m: ext:3200 Digital IPSO Alliance 3200.xml SmartOject Guideline Yes This IPSO object is a generic object that can be used with any kind of digital input interface. Specific objects for a given range of sensors are described later in the document, enabling to identify the type of sensors directly from its Object ID. This object may be used as a generic object if a dedicated one does not exist.
3201 urn:oma:lwm2m: ext:3201 Digital Output IPSO Alliance 3201.xml SmartOject Guideline Yes This IPSO object is a generic object that can be used with any kind of digital output interface. Specific object for a given range of sensors is described later in the document, enabling to identify the type of sensors directly from its Object ID. This object may be used as a generic object if a dedicated one does not exist.
3202 urn:oma:lwm2m: ext:3202 Analogue Input IPSO Alliance 3202.xml SmartOject Guideline Yes This IPSO object is a generic object that can be used with any kind of analogue input interface. Specific object for a given range of sensors is described later in the document, enabling to identify the type of sensors directly from its Object ID. This object may be used as a generic object if a dedicated one does not exist.
3203 urn:oma:lwm2m: ext:3203 Analogue Output IPSO Alliance 3203.xml SmartOject Guideline Yes This IPSO object is a generic object that can be used with any kind of analogue input interface. Specific object for a given range of sensors is described later in the document, enabling to identify the type of sensors directly from its Object ID. This object may be used as a generic object if a dedicated one does not exist.
3300 urn:oma:lwm2m: ext:3300 Generic Sensor IPSO Alliance 3300.xml SmartOject Guideline Yes This IPSO object allow the description of a generic sensor. It is based on the description of a value and a unit according to the UCUM specification. Thus, any type of value defined within this specification can be reporting using this object. Specific object for a given range of sensors is described later in the document, enabling to identify the type of sensors directly from its Object ID. This object may be used as a generic object if a dedicated one does not exist.
3301 urn:oma:lwm2m: ext:3301 Illuminance Sensor IPSO Alliance 3301.xml SmartOject Guideline Yes This IPSO object should be used over a luminosity sensor to report a remote luminosity measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the luminosity sensor. The unit used here is Lux (ucum:lx).
3302 urn:oma:lwm2m: ext:3302 Presence Sensor IPSO Alliance 3302.xml SmartOject Guideline Yes This IPSO object should be used over a presence sensor to report a remote presence detection. It also provides resources to manage a counter, the type of sensor used (e.g the technology of the probe), and configuration for the delay between busy and clear detection state.
3303 urn:oma:lwm2m: ext:3303 Temperature Sensor IPSO Alliance 3303.xml SmartOject Guideline Yes This IPSO object should be used over a temperature sensor to report a remote temperature measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the temperature sensor. The unit used here is degree Celsius (ucum:Cel).
3304 urn:oma:lwm2m: ext:3304 Humidity Sensor IPSO Alliance 3304.xml SmartOject Guideline Yes This IPSO object should be used over a humidity sensor to report a remote humidity measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the humidity sensor. The unit used here is relative humidity as a percentage (ucum:%).
3305 urn:oma:lwm2m: ext:3305 Power Measurement IPSO Alliance 3305.xml SmartOject Guideline Yes This IPSO object should be used over a power measurement sensor to report a remote power measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range for both active and reactive power. Il also provides resources for cumulative energy, calibration, and the power factor.
3306 urn:oma:lwm2m: ext:3306 Actuation IPSO Alliance 3306.xml SmartOject Guideline Yes This IPSO object is dedicated to remote actuation such as ON/OFF action or dimming. A multistate output can also be described as a string. This is useful to send pilot wire orders for instance. It also provides a resource to reflect the time that the device has been switched on.
3308 urn:oma:lwm2m: ext:3308 Set Point IPSO Alliance 3308.xml SmartOject Guideline Yes This IPSO object should be used to set a desired value to a controller, such as a thermostat. This object enables a setpoint to be expressed units defined in the UCUM specification, to match an associated sensor or measurement value. A special resource is added to set the colour of an object.
3310 urn:oma:lwm2m: ext:3310 Load Control IPSO Alliance 3310.xml SmartOject Guideline Yes This Object is used for demand-response load control and other load control in automation application (not limited to power).
3311 urn:oma:lwm2m: ext:3311 Light Control IPSO Alliance 3311.xml SmartOject Guideline Yes This Object is used to control a light source, such as a LED or other light. It allows a light to be turned on or off and its dimmer setting to be control as a % between 0 and 100.
3312 urn:oma:lwm2m: ext:3312 Power Control IPSO Alliance 3312.xml SmartOject Guideline Yes This Object is used to control a power source, such as a Smart Plug. It allows a power relay to be turned on or off and its dimmer setting to be control as a % between 0 and 100.
3313 urn:oma:lwm2m: ext:3313 Accelerometer IPSO Alliance 3313.xml SmartOject Guideline Yes This IPSO object can be used to represent a 1-3 axis accelerometer.
3314 urn:oma:lwm2m: ext:3314 Magnetometer IPSO Alliance 3314.xml SmartOject Guideline Yes This IPSO object can be used to represent a 1-3 axis magnetometer with optional compass direction.
3315 urn:oma:lwm2m: ext:3315 Barometer IPSO Alliance 3315.xml SmartOject Guideline Yes This IPSO object should be used with an air pressure sensor to report a remote barometer measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the barometer sensor.
3316 urn:oma:lwm2m: ext:3316 Voltage IPSO Alliance 3316.xml Yes This IPSO object should be used with voltmeter sensor to report measured voltage between two points. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is volts (ucum: V).
3317 urn:oma:lwm2m: ext:3317 Current IPSO Alliance 3317.xml Yes This IPSO object should be used with an ammeter to report measured electric current in amperes. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is volts (ucum: A).
3318 urn:oma:lwm2m: ext:3318 Frequency IPSO Alliance 3318.xml Yes This IPSO object should be used to report frequency measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is volts (ucum: Hz).
3319 urn:oma:lwm2m: ext:3319 Depth IPSO Alliance 3319.xml Yes This IPSO object should be used to report depth measurements. It can, for example, be used to describe a generic rain gauge that measures the accumulated rainfall in millimetres (mm) or in fathoms (fth).
3320 urn:oma:lwm2m: ext:3320 Percentage IPSO Alliance 3320.xml Yes This IPSO object should can be used to report measurements relative to a 0-100% scale. For example it could be used to measure the level of a liquid in a vessel or container in units of %.
3321 urn:oma:lwm2m: ext:3321 Altitude IPSO Alliance 3321.xml Yes This IPSO object should be used with an altitude sensor to report altitude above sea level in meters. Note that Altitude can be calculated from the measured pressure given the local sea level pressure. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor. An example measurement unit is meters (ucum: m).
3322 urn:oma:lwm2m: ext:3322 Load IPSO Alliance 3322.xml Yes This IPSO object should be used with a load sensor (as in a scale) to report the applied weight or force. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3323 urn:oma:lwm2m: ext:3323 Pressure IPSO Alliance 3323.xml Yes This IPSO object should be used to report pressure measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3324 urn:oma:lwm2m: ext:3324 Loudness IPSO Alliance 3324.xml Yes This IPSO object should be used to report loudness or noise level measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3325 urn:oma:lwm2m: ext:3325 Concentration IPSO Alliance 3325.xml Yes This IPSO object should be used to the particle concentration measurement of a medium. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3326 urn:oma:lwm2m: ext:3326 Acidity IPSO Alliance 3326.xml Yes This IPSO object should be used to report an acidity measurement of a liquid. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3327 urn:oma:lwm2m: ext:3327 Conductivity IPSO Alliance 3327.xml Yes This IPSO object should be used to report a measurement of the electric conductivity of a medium or sample. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3328 urn:oma:lwm2m: ext:3328 Power IPSO Alliance 3328.xml Yes This IPSO object should be used to report power measurements. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3329 urn:oma:lwm2m: ext:3329 Power Factor IPSO Alliance 3329.xml Yes This IPSO object should be used to report a measurement or calculation of the power factor of a reactive electrical load.
3330 urn:oma:lwm2m: ext:3330 Distance IPSO Alliance 3330.xml Yes This IPSO object should be used to report a distance measurement. It also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.
3331 urn:oma:lwm2m: ext:3331 Energy IPSO Alliance 3331.xml Yes This IPSO object should be used to report energy consumption (Cumulative Power) of an electrical load.
3332 urn:oma:lwm2m: ext:3332 Direction IPSO Alliance 3332.xml Yes This IPSO object is used to report the direction indicated by a compass, wind vane, or other directional indicator. The units of measure is plane angle degrees (ucum:deg).
3333 urn:oma:lwm2m: ext:3333 Time IPSO Alliance 3333.xml Yes This IPSO object is used to report the current time in seconds since January 1, 1970 UTC. There is also a fractional time counter that has a range of less than one second.
3334 urn:oma:lwm2m: ext:3334 Gyrometer IPSO Alliance 3334.xml Yes This IPSO Object is used to report the current reading of a gyrometer sensor in 3 axes. It provides tracking of the minimum and maximum angular rate in all 3 axes.
3335 urn:oma:lwm2m: ext:3335 Color IPSO Alliance 3335.xml Yes This IPSO object should be used to report the measured value of a colour sensor in some colour space described by the units resource.
3336 urn:oma:lwm2m: ext:3336 GPS Location IPSO Alliance 3336.xml Yes This IPSO object represents GPS coordinates. This object is compatible with the LWM2M management object for location, but uses reusable resources.
3337 urn:oma:lwm2m: ext:3337 Positioner IPSO Alliance 3337.xml Yes This IPSO object should be used with a generic position actuator from 0 to 100%.
3338 urn:oma:lwm2m: ext:3338 Buzzer IPSO Alliance 3338.xml Yes This IPSO object should be used to actuate an audible alarm such as a buzzer, beeper, or vibration alarm.
3339 urn:oma:lwm2m: ext:3339 Audio Clip IPSO Alliance 3339.xml Yes This IPSO object should be used for a speaker that plays a pre-recorded audio clip or an audio output that is sent elsewhere.
3340 urn:oma:lwm2m: ext:3340 Timer IPSO Alliance 3340.xml Yes This IPSO object is used to time events and actions, using patterns common to industrial timers. A POST to the trigger resource or On/Off input state change starts the timing operation, and the timer remaining time shows zero when the operation is complete.
3341 urn:oma:lwm2m: ext:3341 Addressable Text Display IPSO Alliance 3341.xml Yes This IPSO object is used to send text to a text-only or text mode graphics display.
3342 urn:oma:lwm2m: ext:3342 On/Off Switch IPSO Alliance 3342.xml Yes This IPSO object should be used with an On/Off switch to report the state of the switch.
3343 urn:oma:lwm2m: ext:3343 Lever Control IPSO Alliance 3343.xml Yes This IPSO object should be used with a dimmer or level control to report the state of the control.
3344 urn:oma:lwm2m: ext:3344 Up/Down Control IPSO Alliance 3344.xml Yes This IPSO object is used to report the state of an up/down control element like a pair of push buttons or a rotary encoder.
3345 urn:oma:lwm2m: ext:3345 Multiple Axis Joystick IPSO Alliance 3345.xml Yes This IPSO object can be used to report the position of a shuttle or joystick control. A digital input is provided to report the state of an associated push button.
3346 urn:oma:lwm2m: ext:3346 Rate IPSO Alliance 3346.xml Yes This object type should be used to report a rate measurement,
3347 urn:oma:lwm2m: ext:3347 Push Button IPSO Alliance 3347.xml Yes This IPSO object is used to report the state of a momentary action push button control and to count the number of times the control has been operated since the last observation.
3348 urn:oma:lwm2m: ext:3348 Multistate Selector IPSO Alliance 3348.xml Yes This IPSO object is used to represent the state of a multistate selector switch with a number of fixed positions.
 

x-label – Objects defined by vendors or individuals
Object ID URN Object Name Company* Object DDF File* Object Technical Specification* Description
10241 urn:oma:lwm2m:x:10241 HostDeviceInfo AT&T x x This LWM2M Object provides a range of host device related information which can be queried by the LWM2M Server. The host device is any integrated device with an embedded cellular radio module
10242 urn:oma:lwm2m:x:10242 3-PhasePM Odins 3-PhasePM.xml x This Object provides the information to represent a generic 3-Phase Power Meter
10243 urn:oma:lwm2m:x:10243 singlePhasePM Odins singlePhasePM.xml x This Object provides the information to represent a generic Single-Phase Power Meter
10244 urn:oma:lwm2m:x:10244 VehicleControlUnit Works System VehicleControlUnit.xml x This Object provides the information to represent a generic VCU (vehicle control unit)
10245 urn:oma:lwm2m:x:10245 Relay Management Vodafone Group Services Ltd x x This LWM2M Object provides a range of eNB related measurements and parameters of which several are changeable. Furthermore, it includes Resources to enable/disable the eNB.
10246 urn:oma:lwm2m:x:10246 CrowdBox Measurements Vodafone Group Services Ltd x x This LWM2M Object provides CrowdBox-related measurements such as serving cell parameters, backhaul timing advance, and neighbour cell reports.
10247 urn:oma:lwm2m:x:10247 Neighbour Cell Report Vodafone Group Services Ltd x x This LWM2M Object provides the neighbour cell report. The CrowdBox Measurements Object and the Connected UE Report Object have both Objlnk Resources pointing to this Object
10248 urn:oma:lwm2m:x:10248 Connected UE Measurements Vodafone Group Services Ltd x x This LWM2M Object provides a range of measurements of connected UEs and provides an Object link to the Connected UE report.
10249 urn:oma:lwm2m:x:10249 Connected UE Report Vodafone Group Services Ltd x x This LWM2M Object provides a range of information related to the connected UEs.
 

Note: * Optional fields, as some vendors may prefer to keep their Objects private

ResourceID Registry

ResourceID. LWM2M Objects are composed of resources. Each resource is uniquely identified by a ResourceID.

Resources can either be specific to each Object with meaning only when used in that Object; or a reusable resources can be registered, assigning an ID from an OMNA range.

ResourceID Registration Steps

1. Request the pre-registration of one or more ResourceID(s).

Within 48 hours from receiving an pre-registration request OMNA will send you an email containing the pre-allocated ResourceID(s). You have 7 days to submit the related ObjectID file. If after this period of time OMNA has not received the registration form, the pre-allocated range of ObjectsIDs will return to OMNA for future allocation.

2. Submit the Object DDF file, after receiving the pre-allocated RessourceID(s). The DDF file contains among other information the ResourcesID(s)

This form should only be used after OMNA has sent you a notification with the pre-allocated ResourceID(s). OMNA will review the content of the Object DDF file that contains the ResourceID(s). If there is no issues with the ResourceID(s) OMNA will extract from the submitted file the content to display on the table below.

 

ResourceID Classes
Category ResourceID Range Description
0 – 2047 Defined by the Object specification
Reusable Resource ID 2048 – 32768 Registered by an Object Specification, with the Resource ID assigned by OMNA. Defined in any Object specification. Resources from thisResource ID range can be re-used in any Object
Reserved Resource ID 32769 – Range or Resource IDs reserved for future use
 

Reusable Resource ID assigned by OMNA
Resource ID Resource Name Access Type/ Operations Multiple Instances Mandatory Type Range/ Enumeration Units Description
4000 ObjectInstanceHandle R Objlnk The object link is used to refer an Instance of a given Object. An Object link value is composed of two concatenated 16-bits unsigned integers following the Network Byte Order convention. The Most Significant Halfword is an ObjectID, the Least Significant Hafword is an ObjectInstance ID.An Object Link referencing no Object Instance will contain the concatenation of 2 MAX-ID values (null link
4001 ObjectVersion R Single Optional String LWM2M Object versioning label.
5500 Digital Input State R Boolean x The current state of a digital input.
5501 Digital Input Counter R Integer x The cumulative value of active state detected.
5502 Digital Input Polarity R,W Boolean x The polarity of a digital input as a Boolean (0 = Normal, 1= Reversed)
5503 Digital Input Debounce Period R,W Integer ms The debounce period in ms.
5504 Digital Input Edge Selection R,W Integer The edge selection as an integer (1 = Falling edge, 2 = Rising edge, 3 = Both Rising and Falling edge)
5505 Digital Input Counter Reset E Opaque Reset the Counter value
5550 Digital Output State R,W Boolean The current state of a digital output.
5551 Digital Output Polarity R,W Boolean The polarity of a digital input as a Boolean (0 = Normal, 1= Reversed)
5600 Analog Input Current Value R Float 0-5 V The current state of the analogue input.
5601 Min Measured Value R Float Defined by “Units” resource. The minimum value measured by the sensor since it is ON or Reset
5602 Max Measured Value R Float Defined by “Units” resource. The maximum value measured by the sensor since it is ON or Reset
5603 Min Range Value R Float Defined by “Units” resource. The minimum value that can be measured by the sensor
5604 Max Range Value R Float Defined by “Units” resource. The maximum value that can be measured by the sensor
5605 Reset Min and Max Measured Values E Opaque Reset the Min and Max Measured Values to Current Value
5650 Analog Output Current Value R,W Float 0-5 V The current state of the analogue output.
5700 Sensor Value R Float Defined by “Units” resource. If present, the value of the sensor.
5701 Sensor Units R String If present, the type of sensor defined as the UCUM Unit Definition e.g. “Cel” for Temperature in Celcius.
5702 X Value R Float Defined by “Units” resource. The measured value along the X axis.
5703 Y Value R Float Defined by “Units” resource. The measured value along the Y axis.
5704 Z Value R Float Defined by “Units” resource. The measured value along the Z axis.
5705 Compass Direction R Float 0 -360 deg. The compass direction indicated by the calibrated magnetic field
5706 Colour R,W String Defined by “Units” resource. A string representing a value in some color space
5750 Application Type R,W String The Application type of the device, for example “Motion Closure”.
5751 Sensor Type R String The type of the sensor (for instance PIR type)
5800 Instantaneous active power R Float W The current active power
5801 Min Measured active power R Float W The minimum active power measured by the sensor since it is ON
5802 Max Measured active power R Float W The maximum active power measured by the sensor since it is ON
5803 Min Range active power R Float W The minimum active power that can be measured by the sensor
5804 Max Range active power R Float W The maximum active power that can be measured by the sensor
5805 Cumulative active power R Float Wh The cumulative active power since the last cumulative energy reset or device start
5806 Active Power Calibration W Float W Request an active power calibration by writing the value of a calibrated load.
5810 Instantaneous reactive power R Float var The current reactive power
5811 Min Measured reactive power R Float var The minimum reactive power measured by the sensor since it is ON
5812 Max Measured reactive power R Float var The maximum reactive power measured by the sensor since it is ON
5813 Min Range reactive power R Float var The minimum active power that can be measured by the sensor
5814 Max Range reactive power R Float var The maximum reactive power that can be measured by the sensor
5815 Cumulative reactive power R Float varh The cumulative reactive power since the last cumulative energy reset or device start
5816 Reactive Power Calibration W Float var Request a reactive power calibration by writing the value of a calibrated load.
5820 Power factor R Float If applicable, the power factor of the current consumption.
5821 Current Calibration R,W Float Read or Write the current calibration coefficient
5822 Reset Cumulative energy E Opaque Reset both cumulative active/reactive power
5823 Event Identifier R,W String The event identifier as a string.
5824 Start Time R,W Time Time when the load control event will start started.
5825 Duration In Min R,W Integer min The duration of the load control event.
5826 Critical Level R,W Integer 0-3 The criticality of the event. The device receiving the event will react in an appropriate fashion for the device.
5827 Avg Load AdjPct R,W Integer 0-100 % Defines the maximum energy usage of the receiving device, as a percentage of the device’s normal maximum energy usage.
5828 Duty Cycle R,W Integer 0-100 % Defines the duty cycle for the load control event, i.e, what percentage of time the receiving device is allowed to be on.
5850 On/Off R,W Boolean This resource represents an on/off actuator, which can be controlled, the setting of which is a Boolean value (1,0) where 1 is on and 0 is off.
5851 Dimmer R,W Integer 0-100 % This resource represents a dimmer setting, which has an Integer value between 0 and 100 as a percentage.
5852 On time R,W Integer s The time in seconds that the device has been turned on. Writing a value of 0 resets the counter.
5853 Muti-state Output R,W String A string describing a state for multiple level output such as Pilot Wire
5900 Set Point Value R,W Float Defined by “Units” resource. The setpoint value.
5903 Busy to Clear delay R,W Integer ms Delay from the detection state to the clear state in ms
5904 Clear to Busy delay R,W Integer ms Delay from the clear state to the busy state in ms
5905 Host Device Manufacturer R Single Optional String Human readable host device manufacturer name
5906 Host Device Model Number R Single Optional String A host device model identifier (manufacturer specified string)
5907 Host Device Unique ID R Single Optional String The host device unique ID is assigned by AT&T as the “Device ID” in the onboarding tool and will be stored in
5908 Host Device Software Version R Single Optional String Current software version of the host device. (manufacturer specified string).