This LwM2M Object 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 Smartcard and MUST NOT be accessible by any other LwM2M Server.oma-labelLWM2M Security0https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/0-1_0.xml1Test WGhttp://www.openmobilealliance.org/release/LightweightM2M/V1_0_2-20180209-A/OMA-TS-LightweightM2M-V1_0_2-20180209-A.pdf1urn:oma:lwm2m:oma:01.0This LwM2M Object 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 Smartcard and MUST NOT be accessible by any other LwM2M Server.oma-labelLWM2M Security0https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/0-1_1.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:0:1.11.1This LwM2M Object 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 Smartcard and MUST NOT be accessible by any other LwM2M Server.oma-labelLWM2M Security0https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:0:1.21.2This LwM2M Objects provides the data related to a LwM2M Server. A Bootstrap-Server has no such an Object Instance associated to it.oma-labelLwM2M Server1https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/1-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_0_2-20180209-A/OMA-TS-LightweightM2M-V1_0_2-20180209-A.pdf1urn:oma:lwm2m:oma:11.0This LwM2M Objects provides the data related to a LwM2M Server. A Bootstrap-Server has no such an Object Instance associated to it.oma-labelLwM2M Server1https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/1-1_1.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:1:1.11.1This LwM2M Objects provides the data related to a LwM2M Server. A Bootstrap-Server has no such an Object Instance associated to it.oma-labelLwM2M Server1https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/1.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:1:1.21.2Access Control Object is used to check whether the LwM2M Server has access right for performing an operation.oma-labelLwM2M Access Control2https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/2-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:21.0Access Control Object is used to check whether the LwM2M Server has access right for performing an operation.oma-labelLwM2M Access Control2https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:2:1.11.1This LwM2M Object provides a range of device related information which can be queried by the LwM2M Server, and a device reboot and factory reset function.oma-labelDevice3https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1-20180710-A/OMA-TS-LightweightM2M_Core-V1_1-20180710-A.pdf1urn:oma:lwm2m:oma:31.0This LwM2M Object provides a range of device related information which can be queried by the LwM2M Server, and a device reboot and factory reset function.oma-labelDevice3https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3-1_1.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:3:1.11.1This LwM2M Object provides a range of device related information which can be queried by the LwM2M Server, and a device reboot and factory reset function.oma-labelDevice3https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:3:1.21.2This LwM2M Object 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 Strength, Cell ID are retrieved during connected mode at least for cellular networks.oma-labelConnectivity Monitoring4https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/4-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_0_2-20180209-A/OMA-TS-LightweightM2M-V1_0_2-20180209-A.pdf1urn:oma:lwm2m:oma:41.0This LwM2M Object 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 Strength, Cell ID are retrieved during connected mode at least for cellular networks.oma-labelConnectivity Monitoring4https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/4-1_1.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1-20180710-A/OMA-TS-LightweightM2M_Core-V1_1-20180710-A.pdf1urn:oma:lwm2m:oma:4:1.11.1This LwM2M Object 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 Strength, Cell ID are retrieved during connected mode at least for cellular networks.oma-labelConnectivity Monitoring4https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/4-1_2.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:4:1.21.2This LwM2M Object 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 Strength, Cell ID are retrieved during connected mode at least for cellular networks.oma-labelConnectivity Monitoring4https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/4.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2_1-20221209-A/OMA-TS-LightweightM2M_Core-V1_2_1-20221209-A.pdf1urn:oma:lwm2m:oma:4:1.31.3This LwM2M Object enables management of firmware which is to be updated. This Object includes installing a firmware package, updating firmware, and performing actions after updating firmware. The firmware update MAY require to reboot the device; it will depend on a number of factors, such as the operating system architecture and the extent of the updated software. The envisioned functionality is to allow a LwM2M Client to connect to any LwM2M Server to obtain a firmware image using the object and resource structure defined in this section experiencing communication security protection using TLS/DTLS. There are, however, other design decisions that need to be taken into account to allow a manufacturer of a device to securely install firmware on a device. Examples for such design decisions are how to manage the firmware update repository at the server side (which may include user interface considerations), the techniques to provide additional application layer security protection of the firmware image, how many versions of firmware images to store on the device, and how to execute the firmware update process considering the hardware specific details of a given IoT hardware product. These aspects are considered to be outside the scope of this version of the specification. A LwM2M Server may also instruct a LwM2M Client to fetch a firmware image from a dedicated server (instead of pushing firmware images to the LwM2M Client). The Package URI resource is contained in the Firmware object and can be used for this purpose. A LwM2M Client MUST support block-wise transfer [CoAP_Blockwise] if it implements the Firmware Update object. A LwM2M Server MUST support block-wise transfer. Other protocols, such as HTTP/HTTPs, MAY also be used for downloading firmware updates (via the Package URI resource). For constrained devices it is, however, RECOMMENDED to use CoAP for firmware downloads to avoid the need for additional protocol implementations.oma-labelFirmware Update5https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/5-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:51.0This LwM2M Object enables management of firmware which is to be updated. This Object includes installing a firmware package, updating firmware, and performing actions after updating firmware. The firmware update MAY require to reboot the device; it will depend on a number of factors, such as the operating system architecture and the extent of the updated software. The envisioned functionality is to allow a LwM2M Client to connect to any LwM2M Server to obtain a firmware image using the object and resource structure defined in this section experiencing communication security protection using TLS/DTLS. There are, however, other design decisions that need to be taken into account to allow a manufacturer of a device to securely install firmware on a device. Examples for such design decisions are how to manage the firmware update repository at the server side (which may include user interface considerations), the techniques to provide additional application layer security protection of the firmware image, how many versions of firmware images to store on the device, and how to execute the firmware update process considering the hardware specific details of a given IoT hardware product. These aspects are considered to be outside the scope of this version of the specification. A LwM2M Server may also instruct a LwM2M Client to fetch a firmware image from a dedicated server (instead of pushing firmware images to the LwM2M Client). The Package URI resource is contained in the Firmware object and can be used for this purpose. A LwM2M Client MUST support block-wise transfer [CoAP_Blockwise] if it implements the Firmware Update object. A LwM2M Server MUST support block-wise transfer. Other protocols, such as HTTP/HTTPs, MAY also be used for downloading firmware updates (via the Package URI resource). For constrained devices it is, however, RECOMMENDED to use CoAP for firmware downloads to avoid the need for additional protocol implementations.oma-labelFirmware Update5https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/5-1_1.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:5:1.11.1This LwM2M Object enables management of firmware which is to be updated. This Object includes installing a firmware package, updating firmware, and performing actions after updating firmware. The firmware update MAY require to reboot the device; it will depend on a number of factors, such as the operating system architecture and the extent of the updated software. The envisioned functionality is to allow a LwM2M Client to connect to any LwM2M Server to obtain a firmware image using the object and resource structure defined in this section experiencing communication security protection using TLS/DTLS. There are, however, other design decisions that need to be taken into account to allow a manufacturer of a device to securely install firmware on a device. Examples for such design decisions are how to manage the firmware update repository at the server side (which may include user interface considerations), the techniques to provide additional application layer security protection of the firmware image, how many versions of firmware images to store on the device, and how to execute the firmware update process considering the hardware specific details of a given IoT hardware product. These aspects are considered to be outside the scope of this version of the specification. A LwM2M Server may also instruct a LwM2M Client to fetch a firmware image from a dedicated server (instead of pushing firmware images to the LwM2M Client). The Package URI resource is contained in the Firmware object and can be used for this purpose. A LwM2M Client MUST support block-wise transfer [CoAP_Blockwise] if it implements the Firmware Update object. A LwM2M Server MUST support block-wise transfer. Other protocols, such as HTTP/HTTPs, MAY also be used for downloading firmware updates (via the Package URI resource). For constrained devices it is, however, RECOMMENDED to use CoAP for firmware downloads to avoid the need for additional protocol implementations.oma-labelFirmware Update5https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/5.xml1OMA0urn:oma:lwm2m:oma:5:1.21.2This LwM2M Object provides a range of location telemetry related information which can be queried by the LwM2M Server.oma-labelLocation6https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/6.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:61.0This 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.oma-labelConnectivity Statistics7https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/7.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:71.0This LWM2M objects provides the resources needed to perform the lock and wipe operations.oma-labelLock and Wipe8https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/8.xml1OMAhttps://www.openmobilealliance.org/release/LWM2M_LOCKWIPE/V1_0_4-20240312-A/OMA-TS-LWM2M_LockWipe-V1_0_4-20240312-A.pdf1urn:oma:lwm2m:oma:81.0This 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.oma-labelLWM2M Software Management9https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/9.xml1OMAhttps://www.openmobilealliance.org/release/LWM2M_SWMGMT/V1_0_3-20240312-A/OMA-TS-LWM2M_SwMgmt-V1_0_3-20240312-A.pdf1urn:oma:lwm2m:oma:91.0This object specifies resources to enable a device to connect to a 3GPP or 3GPP2 bearer, including GPRS/EDGE, UMTS, LTE, NB-IoT, SMS. For cellular connectivity, this object focuses on Packet Switched (PS) connectivity and doesn't aim to provide comprehensive Circuit Switched (CS) connectivity management.oma-labelLWM2M Cellular Connectivity10https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10-1_0.xml1OMA0urn:oma:lwm2m:oma:101.0This object specifies resources to enable a device to connect to a 3GPP or 3GPP2 bearer, including GPRS/EDGE, UMTS, LTE, NB-IoT, SMS. For cellular connectivity, this object focuses on Packet Switched (PS) connectivity and doesn't aim to provide comprehensive Circuit Switched (CS) connectivity management.oma-labelLWM2M Cellular Connectivity10https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10.xml1OMA0urn:oma:lwm2m:oma:10:1.11.1This object specifies resources to enable a device to connect to an APN.oma-labelLWM2M APN Connection Profile11https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/11-1_0.xml1OMA0urn:oma:lwm2m:oma:111.0This object specifies resources to enable a device to connect to an APN.oma-labelLWM2M APN Connection Profile11https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/11.xml1OMA0urn:oma:lwm2m:oma:11:1.11.1This object specifies resources to enable a device to connect to a WLAN bearer.oma-labelWLAN connectivity12https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/12-1_0.xml1OMA0urn:oma:lwm2m:oma:121.0This object specifies resources to enable a device to connect to a WLAN bearer.oma-labelWLAN connectivity12https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/12.xml1OMA0urn:oma:lwm2m:oma:12:1.11.1This object specifies resources to enable a device to choose a PLMN/network on which to attach/register and what type of bearer to then connect. This object allows via remote bearer and network configuration to overwrite automatic network and bearer selection e.g. as supported by the UICC. An equivalent example for overwriting automatic selection is a user doing manual network and bearer selection on a smart phone.oma-labelLWM2M Bearer Selection13https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/13-1_0.xml1OMA0urn:oma:lwm2m:oma:131.0This object specifies resources to enable a device to choose a PLMN/network on which to attach/register and what type of bearer to then connect. This object allows via remote bearer and network configuration to overwrite automatic network and bearer selection e.g. as supported by the UICC. An equivalent example for overwriting automatic selection is a user doing manual network and bearer selection on a smart phone.oma-labelLWM2M Bearer Selection13https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/13.xml1OMA0urn:oma:lwm2m:oma:13:1.11.1If some Objects are not supported after software update, the LwM2M Client MUST delete all the Object Instances of the Objects that are not supported.oma-labelLWM2M Software Component14https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/14.xml1OMAhttps://www.openmobilealliance.org/release/LWM2M_SWMGMT/V1_0_3-20240312-A/OMA-TS-LWM2M_SwMgmt-V1_0_3-20240312-A.pdf1urn:oma:lwm2m:oma:141.0This LWM2M Object is dedicated to manage the device capabilities of a device e.g. sensors, communication, etc.oma-labelDevCapMgmt15https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/15-1_0.xml1OMAhttps://www.openmobilealliance.org/release/LWM2M_DevCapMgmt/V1_0_3-20200616-A/OMA-TS-LWM2M_DevCapMgmt-V1_0_3-20200616-A.pdf1urn:oma:lwm2m:oma:151.0This LWM2M Object is dedicated to manage the device capabilities of a device e.g. sensors, communication, etc.oma-labelDevCapMgmt15https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/15.xml1OMAhttps://www.openmobilealliance.org/release/LWM2M_DevCapMgmt/V2_0_1-20240312-A/OMA-TS-LWM2M_DevCapMgmt-V2_0_1-20240312-A.pdf1urn:oma:lwm2m:oma:15:2.02.0The Portfolio Object allows to extend the data storage capability of other Object Instances in the LwM2M system, as well as the services which may be used to authenticate and to protect privacy of data contained in those extensions. In addition, a service of data encryption is also definedoma-labelPortfolio16https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/16.xml1OMAhttp://www.openmobilealliance.org/release/LWM2M_PortfolioObj/V1_0_1-20200616-A/OMA-TS-LWM2M_PortfolioObj-V1_0_1-20200616-A.pdf1urn:oma:lwm2m:oma:161.0This object enables configuration of various generic communications parameters.oma-labelCommunications Characteristics170OMA0urn:oma:lwm2m:oma:171.0This object provides Non-Access Stratum (NAS) configuration and is derived from 3GPP TS 24.368.oma-labelNon-Access Stratum (NAS) Configuration180OMA0urn:oma:lwm2m:oma:181.0This LwM2M Objects provides the application service data related to a LwM2M Server, eg. Water meter data. There are several methods to create instance to indicate the message direction based on the negotiation between Application and LwM2M. The Client and Server should negotiate the instance(s) used to exchange the data. For example: - Using a single instance for both directions communication, from Client to Server and from Server to Client. - Using an instance for communication from Client to Server and another one for communication from Server to Client - Using several instancesoma-labelBinaryAppDataContainer19https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/19.xml1OMAhttps://www.openmobilealliance.org/release/LwM2M_APPDATA/V1_0_2-20240312-A/OMA-TS-LWM2M_BinaryAppDataContainer-V1_0_2-20240312-A.pdf1urn:oma:lwm2m:oma:191.0The Event Log Object is a single Instance Object defined for logging data in a straightforward and generic way. The Resources of that Object are based on the OMA LwM2M set of reusable Resources dedicated to logging event activity.oma-labelEvent Log20https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/20-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LwM2M_EventLog/V1_0_1-20200616-A/OMA-TS-LWM2M_EventLog-V1_0_1-20200616-A.pdf1urn:oma:lwm2m:oma:201.0The Event Log Object is a multiple Instances Object defined for logging data in a straightforward and generic way. The Resources of that Object are based on the OMA LwM2M set of reusable Resources dedicated to logging event activity.oma-labelEvent Log20https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/20-2_0.xml1OMAhttp://www.openmobilealliance.org/release/LwM2M_EventLog/V2_0-20230131-A/OMA-TS-LWM2M_EventLog-V2_0-20230131-A.pdf1urn:oma:lwm2m:oma:20:2.02.0The Event Log Object is a multiple Instances Object defined for logging data in a straightforward and generic way. The Resources of that Object are based on the OMA LwM2M set of reusable Resources dedicated to logging event activity.oma-labelEvent Log20https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/20-2_1.xml1OMAhttps://www.openmobilealliance.org/release/LwM2M_EventLog/V2_1-20240123-A/OMA-TS-LWM2M_EventLog-V2_1-20240123-A.pdf1urn:oma:lwm2m:oma:20:2.12.1The Event Log Object is a multiple Instances Object defined for logging data in a straightforward and generic way. The Resources of that Object are based on the OMA LwM2M set of reusable Resources dedicated to logging event activity.oma-labelEvent Log20https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/20.xml1OMAhttps://www.openmobilealliance.org/release/LwM2M_EventLog/V3_0-20250714-A/OMA-TS-LWM2M_EventLog-V3_0-20250714-A.pdf1urn:oma:lwm2m:oma:20:3.03.0This LwM2M Object provides the keying material and related information of a LwM2M Client appropriate to access a specified LwM2M Server using OSCORE. One Object Instance MAY address a LwM2M Bootstrap-Server. These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server. Instances of this Object are linked from Instances of Object 0 using the OSCORE Security Mode Resource of Object 0. Instances of this Object MUST NOT be linked from more than one Instance of Object 0.oma-labelLWM2M OSCORE21https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/21-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_1_1-20190617-A/OMA-TS-LightweightM2M_Core-V1_1_1-20190617-A.pdf1urn:oma:lwm2m:oma:211.0This LwM2M Object provides the keying material and related information of a LwM2M Client appropriate to access a specified LwM2M Server using OSCORE. One Object Instance MAY address a LwM2M Bootstrap-Server. These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server. Instances of this Object are linked from Instances of Object 0 using the OSCORE Security Mode Resource of Object 0. Instances of this Object MUST NOT be linked from more than one Instance of Object 0.oma-labelLWM2M OSCORE21https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/21-1_1.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:21:1.11.1This LwM2M Object provides the keying material and related information of a LwM2M Client appropriate to access a specified LwM2M Server using OSCORE. One Object Instance MAY address a LwM2M Bootstrap-Server. These LwM2M Object Resources MUST only be changed by a LwM2M Bootstrap-Server or Bootstrap from Smartcard and MUST NOT be accessible by any other LwM2M Server. Instances of this Object are linked from Instances of Object 0 using the OSCORE Security Mode Resource of Object 0. Instances of this Object MUST NOT be linked from more than one Instance of Object 0.oma-labelLWM2M OSCORE21https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/21.xml1OMA0urn:oma:lwm2m:oma:21:2.02.0The Virtual Observe Notify Object provides a main function to notify multiple resources to a LwM2M Server in one notification message whether the resources are in one object/object instance or across multiple objects. The Virtual Observe Notify Object also provides some functions to implement more efficient multi-resource report.oma-labelVirtual Observe Notify22https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/22-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LwM2M_VON/V1_0-20190711-A/OMA-TS-LWM2M_VirtualObserveNotify-V1_0-20190711-A.pdf1urn:oma:lwm2m:oma:221.0The Virtual Observe Notify Object provides a main function to notify multiple resources to a LwM2M Server in one notification message whether the resources are in one object/object instance or across multiple objects. The Virtual Observe Notify Object also provides some functions to implement more efficient multi-resource report.oma-labelVirtual Observe Notify22https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/22.xml1OMAhttps://www.openmobilealliance.org/documents/guidelines/OMA-Guidelines-LwM2M_VirtualObserveNotify-V1_1-20211130-A.pdf1urn:oma:lwm2m:oma:22:1.11.1This Object provides the keying material and related information for use with COSE.oma-labelLwM2M COSE23https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/23.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:231.0This object defines configuration parameters for an MQTT client to interact with a MQTT server.oma-labelMQTT Server24https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/24.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:241.0This object is used by a LwM2M Gateway to maintain the devices connected to the gateway.oma-labelLwM2M Gateway25https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/25-1_0.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:251.0This object is used by a LwM2M Gateway to maintain the IoT Devices connected to the LwM2M Gateway.oma-labelLwM2M Gateway25https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/25.xml1OMAhttps://www.openmobilealliance.org/release/LwM2M_Gateway/V1_1_1-20240312-A/OMA-TS-LWM2M_Gateway-V1_1_1-20240312-A.pdf1urn:oma:lwm2m:oma:25:2.02.0This object is used by a LwM2M Gateway to maintain the routing table.oma-labelLwM2M Gateway Routing26https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/26.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:261.0This is a device management object that should be used for 5G-NR capable devices.oma-label5GNR Connectivity27https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/27.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:271.0This is a device management object that should be used for capturing the RF capabilities of the device.oma-labelDevice RF Capabilities28https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/28.xml1OMAhttp://www.openmobilealliance.org/release/LightweightM2M/V1_2-20201110-A/OMA-TS-LightweightM2M_Core-V1_2-20201110-A.pdf1urn:oma:lwm2m:oma:281.0This object is used to configure the CoAP transmission parameters (RFC7252) and other parameters that affect CoAP transmission.oma-labelCoAP Config500https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/500.xml1OMA0urn:oma:lwm2m:oma:5001.0This object is used to configure the cellular band used by the device as well as to change the band. It is intended to be used on LTE bands, as in NB-IoT and LTE Cat M1 frequency bands.oma-labelLTE-MTC Band Config501https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/501.xml1OMA0urn:oma:lwm2m:oma:5011.0This is an alarm that should be raised if the sensor detects a higher than threshold CO level.oma-labelCO Detector502https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/502.xml1OMA0urn:oma:lwm2m:oma:5021.0This is an alarm that should be raised if the sensor(s) detect fire, based on the values reported from Temperature, Humidity, Smoke (CO2).oma-labelFire Alarm503https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/503.xml1OMA0urn:oma:lwm2m:oma:5031.0This is a device management object that should be used for Remote SIM Provisioning according to GSMA standardsoma-labelRemote SIM Provisioning504https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/504.xml1OMA0urn:oma:lwm2m:oma:5041.0This is a device management object that should be used for Remote SIM Provisioning from a LwM2M server.oma-labelLwM2M SIM Provisioning505https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/505.xml1OMA0urn:oma:lwm2m:oma:5051.0This device management object contains the elements of a nuSIM profile package according to nuSIM Technical Specification NTS.01.oma-labelnuSIM Profile507https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/507.xml1OMA0urn:oma:lwm2m:oma:5071.0This device management object represents a nuSIM integrated SIM according to NTS.01 - nuSIM Integrated SIM Specification.oma-labelnuSIM508https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/508.xml1OMA0urn:oma:lwm2m:oma:5081.0This object contains measurement metadata for sensor objects. The corresponding sensor is identified with an object link. If the LwM2M Client provides measurement quality information both inside the sensor objects and in the Measurement Metadata object, it MUST ensure that identical data is reported in corresponding object instances. The LwM2M Server SHOULD use the data from the Measurement Metadata object if both are available. The LwM2M Client also MUST ensure that no two Measurement Metadata object instances link to the same sensor object instance. If the LwM2M Server receives such non-conforming data, the Measurement Metadata object instance with largest Instance ID SHOULD be used.oma-labelMeasurement Metadata509https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/509.xml1OMA0urn:oma:lwm2m:oma:5091.0This object contains description for vendor specific measurement quality reason codes provided in a Measurement Metadata (509) object. Instances of this object define the mapping of vendor specific reason codes to reason description in the scope of an individual device.oma-labelVendor Specific Measurement Quality Reason510https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/510.xml1OMA0urn:oma:lwm2m:oma:5101.0This Object enables collecting a set of Resource values from other Objects into a single Resource representation.oma-labelCompact Composite511https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/511.xml1OMA0urn:oma:lwm2m:oma:5111.0TBDoma-labelTBD5120OMA0urn:oma:lwm2m:oma:5121.0This object can be used to provision and configure AI Model capabilities. A new AI model is provisioned using the Model, Model URI, and/or Model Description resources. The Input and Input labels resources can be used to configure where the model reads the input data and the Output and Output labels resources are used to configure where the model writes the output data. When output of one model is used as input of another model, the models are chained together. Input and Output transform resources can be used to transform data before reading or writing.oma-labelAI Model Configuration513https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/513.xml1OMA0urn:oma:lwm2m:oma:5131.0The OMA Cabinet Controller Status shall provide electrical measurements related to street lines.oma-labelCabinet Controller Status600https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/600.xml1OMA0urn:oma:lwm2m:oma:6001.0The OMA Cabinet Controller Manager shall provide settings and alarms for corresponding Cabinet Controllers.oma-labelCabinet Controller Manager601https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/601.xml1OMA0urn:oma:lwm2m:oma:6011.0The OMA Computational Performance object provides attributes to monitor the load on various aspects of the system.oma-labelComputational Performance602https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/602.xml1OMA0urn:oma:lwm2m:oma:6021.0This Object provides links to a set of rules associated with a specific CSE that governs the behavior of that CSE regarding rejecting, buffering and sending request or response messages via the Mcc reference point.ext-labelCmdhPolicy2048https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2048.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20481.0This Object provides a link to the currently active set of CMDH policiesext-labelActiveCmdhPolicy2049https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2049.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20491.0Defines which CMDH related parameters will be used by default.ext-labelCmdhDefaults2050https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2050.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20501.0This Object represents default set of values for the Event Category parameter of an incoming request or response message.ext-labelCmdhDefEcValues2051https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2051.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20511.0This Object represents a specific set of default values for the CMDH related parameters Request Expiration Timestamp, Result Expiration Timestamp, Operational Execution Time, Result Persistence and Delivery Aggregation that are applicable for a given Event Category if these parameters are not specified in the message.ext-labelCmdhEcDefParamValues2052https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2052.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20521.0This Object represents limits for CMDH related parameter values.ext-labelCmdhLimits2053https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2053.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20531.0This Object defines the usage of underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE.ext-labelCmdhNetworkAccessRules2054https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2054.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20541.0This Object defines limits in usage of specific underlying networks for forwarding information to other CSEs during processing of CMDH-related requests in a CSE.ext-labelCmdhNwAccessRule2055https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2055.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20551.0This Object defines limits in usage of buffers for temporarily storing information that needs to be forwarded to other CSEs during processing of CMDH-related requests in a CSE.ext-labelCmdhBuffer2056https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2056.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20561.0This Object defines set of parameters which can be referenced by a specific Instance of the CmdhNwAccessRule Object (ID: 2055)ext-labelCmdhBackOffParametersSet2057https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/2057.xml1oneM2Mhttp://www.onem2m.org/images/files/deliverables/TS-0005-Management_Enablement_(OMA)-V1_0_1.pdf1urn:oma:lwm2m:ext:20571.0Generic digital input for non-specific sensorsext-labelDigital Input3200https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3200-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:32001.0Generic digital input for non-specific sensorsext-labelDigital Input3200https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3200.xml1IPSO Alliance0urn:oma:lwm2m:ext:3200:1.11.1>Generic digital output for non-specific actuatorsext-labelDigital Output3201https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3201-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:32011.0Generic digital output for non-specific actuatorsext-labelDigital Output3201https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3201.xml1IPSO Alliance0urn:oma:lwm2m:ext:3201:1.11.1Generic analog input for non-specific sensorsext-labelAnalog Input3202https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3202-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:32021.0Generic analog input for non-specific sensorsext-labelAnalog Input3202https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3202.xml1IPSO Alliance0urn:oma:lwm2m:ext:3202:1.11.1This IPSO object is a generic object that can be used with any kind of analog output interface.ext-labelAnalog Output3203https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3203-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:32031.0This IPSO object is a generic object that can be used with any kind of analog output interface.ext-labelAnalog Output3203https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3203.xml1IPSO Alliance0urn:oma:lwm2m:ext:3203:1.11.1This IPSO object allows the description of a generic sensor. It is based on the description of a value and a unit according to the SenML specification. Thus, any type of value defined within this specification can be reported using this object. This object may be used as a generic object if a dedicated one does not exist.ext-labelGeneric Sensor3300https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3300-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33001.0This IPSO object allows the description of a generic sensor. It is based on the description of a value and a unit according to the SenML specification. Thus, any type of value defined within this specification can be reported using this object. This object may be used as a generic object if a dedicated one does not exist.ext-labelGeneric Sensor3300https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3300.xml1IPSO Alliance0urn:oma:lwm2m:ext:3300:1.11.1Illuminance sensor, example units = lxext-labelIlluminance3301https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3301-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33011.0Illuminance sensor, example units = lxext-labelIlluminance3301https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3301.xml1IPSO Alliance0urn:oma:lwm2m:ext:3301:1.11.1Presence sensor with digital sensing, optional delay parametersext-labelPresence3302https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3302-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33021.0Presence sensor with digital sensing, optional delay parametersext-labelPresence3302https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3302.xml1IPSO Alliance0urn:oma:lwm2m:ext:3302:1.11.1This IPSO object should be used with a temperature sensor to report a temperature measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the temperature sensor. An example measurement unit is degrees Celsius.ext-labelTemperature3303https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3303-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33031.0This IPSO object should be used with a temperature sensor to report a temperature measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the temperature sensor. An example measurement unit is degrees Celsius.ext-labelTemperature3303https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3303.xml1IPSO Alliance0urn:oma:lwm2m:ext:3303:1.11.1This IPSO object should be used with a humidity sensor to report a humidity measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the humidity sensor. An example measurement unit is relative humidity as a percentage.ext-labelHumidity3304https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3304-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33041.0This IPSO object should be used with a humidity sensor to report a humidity measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the humidity sensor. An example measurement unit is relative humidity as a percentage.ext-labelHumidity3304https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3304.xml1IPSO Alliance0urn:oma:lwm2m:ext:3304:1.11.1This 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. It also provides resources for cumulative energy, calibration, and the power factor.ext-labelPower Measurement3305https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3305-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33051.0This 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. It also provides resources for cumulative energy, calibration, and the power factor.ext-labelPower Measurement3305https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3305.xml1IPSO Alliance0urn:oma:lwm2m:ext:3305:1.11.1This IPSO object is dedicated to remote actuation such as ON/OFF action or dimming. A multi-state 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.ext-labelActuation3306https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3306-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33061.0This IPSO object is dedicated to remote actuation such as ON/OFF action or dimming. A multi-state 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.ext-labelActuation3306https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3306.xml1IPSO Alliance0urn:oma:lwm2m:ext:3306:1.11.1This IPSO object should be used to set a desired value to a controller, such as a thermostat. A special resource is added to set the colour of an object.ext-labelSet Point3308https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3308-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33081.0This IPSO object should be used to set a desired value to a controller, such as a thermostat. A special resource is added to set the colour of an object.ext-labelSet Point3308https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3308.xml1IPSO Alliance0urn:oma:lwm2m:ext:3308:1.11.1This Object is used for demand-response load control and other load control in automation application (not limited to power).ext-labelLoad Control3310https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3310-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33101.0This Object is used for demand-response load control and other load control in automation application (not limited to power).ext-labelLoad Control3310https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3310.xml1IPSO Alliance0urn:oma:lwm2m:ext:3310:1.11.1This 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. An optional colour setting enables a string to be used to indicate the desired colour.ext-labelLight Control3311https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3311.xml1IPSO Alliance0urn:oma:lwm2m:ext:33111.0This 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.ext-labelPower Control3312https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3312-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33121.0This 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.ext-labelPower Control3312https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3312.xml1IPSO Alliance0urn:oma:lwm2m:ext:3312:1.11.1This IPSO object can be used to represent a 1-3 axis accelerometer.ext-labelAccelerometer3313https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3313-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33131.0This IPSO object can be used to represent a 1-3 axis accelerometer.ext-labelAccelerometer3313https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3313.xml1IPSO Alliance0urn:oma:lwm2m:ext:3313:1.11.1This IPSO object can be used to represent a 1-3 axis magnetometer with optional compass direction.ext-labelMagnetometer3314https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3314-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33141.0This IPSO object can be used to represent a 1-3 axis magnetometer with optional compass direction.ext-labelMagnetometer3314https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3314.xml1IPSO Alliance0urn:oma:lwm2m:ext:3314:1.11.1This IPSO object should be used with an air pressure sensor to report a barometer measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the barometer sensor. An example measurement unit is pascals.ext-labelBarometer3315https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3315-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33151.0This IPSO object should be used with an air pressure sensor to report a barometer measurement. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the barometer sensor. An example measurement unit is pascals.ext-labelBarometer3315https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3315.xml1IPSO Alliance0urn:oma:lwm2m:ext:3315:1.11.1This 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.ext-labelVoltage3316https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3316-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33161.0This 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.ext-labelVoltage3316https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3316.xml1IPSO Alliance0urn:oma:lwm2m:ext:3316:1.11.1This 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 ampere.ext-labelCurrent3317https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3317-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33171.0This 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 ampere.ext-labelCurrent3317https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3317.xml1IPSO Alliance0urn:oma:lwm2m:ext:3317:1.11.1This 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 hertz.ext-labelFrequency3318https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3318-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33181.0This 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 hertz.ext-labelFrequency3318https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3318.xml1IPSO Alliance0urn:oma:lwm2m:ext:3318:1.11.1This 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).ext-labelDepth3319https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3319-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33191.0This 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).ext-labelDepth3319https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3319.xml1IPSO Alliance0urn:oma:lwm2m:ext:3319:1.11.1This 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 %.ext-labelPercentage3320https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3320-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33201.0This 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 %.ext-labelPercentage3320https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3320.xml1IPSO Alliance0urn:oma:lwm2m:ext:3320:1.11.1This 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.ext-labelAltitude3321https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3321-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33211.0This 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.ext-labelAltitude3321https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3321.xml1IPSO Alliance0urn:oma:lwm2m:ext:3321:1.11.1This 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. An example measurement unit is kilograms.ext-labelLoad3322https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3322-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33221.0This 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. An example measurement unit is kilograms.ext-labelLoad3322https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3322.xml1IPSO Alliance0urn:oma:lwm2m:ext:3322:1.11.1This 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. An example measurement unit is pascals.ext-labelPressure3323https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3323-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33231.0This 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. An example measurement unit is pascals.ext-labelPressure3323https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3323.xml1IPSO Alliance0urn:oma:lwm2m:ext:3323:1.11.1This 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. An example measurement unit is decibels.ext-labelLoudness3324https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3324-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33241.0This 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. An example measurement unit is decibels.ext-labelLoudness3324https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3324.xml1IPSO Alliance0urn:oma:lwm2m:ext:3324:1.11.1This 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. An example measurement unit is parts per million.ext-labelConcentration3325https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3325-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33251.0This 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. An example measurement unit is parts per million.ext-labelConcentration3325https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3325.xml1IPSO Alliance0urn:oma:lwm2m:ext:3325:1.11.1This 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. An example measurement unit is pH.ext-labelAcidity3326https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3326-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33261.0This 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. An example measurement unit is pH.ext-labelAcidity3326https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3326.xml1IPSO Alliance0urn:oma:lwm2m:ext:3326:1.11.1This 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. An example measurement unit is Siemens.ext-labelConductivity3327https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3327-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33271.0This 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. An example measurement unit is Siemens.ext-labelConductivity3327https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3327.xml1IPSO Alliance0urn:oma:lwm2m:ext:3327:1.11.1This 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.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. An example measurement unit is Watts. This object may be used for either real power or apparent power measurements.ext-labelPower3328https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3328-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33281.0This 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. An example measurement unit is Watts. This object may be used for either real power or apparent power measurements.ext-labelPower3328https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3328.xml1IPSO Alliance0urn:oma:lwm2m:ext:3328:1.11.1This IPSO object should be used to report a measurement or calculation of the power factor of a reactive electrical load. Power Factor is normally the ratio of non-reactive power to total power. This object also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.ext-labelPower Factor3329https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3329-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33291.0This IPSO object should be used to report a measurement or calculation of the power factor of a reactive electrical load. Power Factor is normally the ratio of non-reactive power to total power. This object also provides resources for minimum and maximum measured values, as well as the minimum and maximum range that can be measured by the sensor.ext-labelPower Factor3329https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3329.xml1IPSO Alliance0urn:oma:lwm2m:ext:3329:1.11.1This 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. An example measurement unit is Meters.ext-labelDistance3330https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3330-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33301.0This 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. An example measurement unit is Meters.ext-labelDistance3330https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3330.xml1IPSO Alliance0urn:oma:lwm2m:ext:3330:1.11.1This IPSO object should be used to report energy consumption (Cumulative Power) of an electrical load. An example measurement unit is Watt Hours.ext-labelEnergy3331https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3331-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33311.0This IPSO object should be used to report energy consumption (Cumulative Power) of an electrical load. An example measurement unit is Watt Hours.ext-labelEnergy3331https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3331.xml1IPSO Alliance0urn:oma:lwm2m:ext:3331:1.11.1This 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.ext-labelDirection3332https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3332-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33321.0This 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.ext-labelDirection3332https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3332.xml1IPSO Alliance0urn:oma:lwm2m:ext:3332:1.11.1This 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.ext-labelTime3333https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3333-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33331.0This 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.ext-labelTime3333https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3333.xml1IPSO Alliance0urn:oma:lwm2m:ext:3333:1.11.1This 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. An example unit of measure is radians per second.ext-labelGyrometer3334https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3334-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33341.0This 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. An example unit of measure is radians per second.ext-labelGyrometer3334https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3334.xml1IPSO Alliance0urn:oma:lwm2m:ext:3334:1.11.1This IPSO object should be used to report the measured value of a colour sensor in some colour space described by the units resource.ext-labelColour3335https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3335-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33351.0This IPSO object should be used to report the measured value of a colour sensor in some colour space described by the units resource.ext-labelColour3335https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3335.xml1IPSO Alliance0urn:oma:lwm2m:ext:3335:1.11.1This IPSO object represents GPS coordinates. This object is compatible with the LWM2M management object for location, but uses reusable resources.ext-labelLocation3336https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3336-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33361.0This IPSO object represents GPS coordinates. This object is compatible with the LWM2M management object for location, but uses reusable resources.ext-labelLocation3336https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3336-1_1.xml1IPSO Alliance0urn:oma:lwm2m:ext:3336:1.11.1This IPSO object represents GPS coordinates. This object is compatible with the LwM2M management object for location, but uses reusable resources.ext-labelLocation3336https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3336.xml1IPSO Alliance0urn:oma:lwm2m:ext:3336:2.02.0This IPSO object should be used with a generic position actuator with range from 0 to 100%. This object optionally allows setting the transition time for an operation that changes the position of the actuator, and for reading the remaining time of the currently active transition.ext-labelPositioner3337https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3337-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33371.0This IPSO object should be used with a generic position actuator with range from 0 to 100%. This object optionally allows setting the transition time for an operation that changes the position of the actuator, and for reading the remaining time of the currently active transition.ext-labelPositioner3337https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3337.xml1IPSO Alliance0urn:oma:lwm2m:ext:3337:1.11.1This IPSO object should be used to actuate an audible alarm such as a buzzer, beeper, or vibration alarm. There is a dimmer control for setting the relative loudness of the alarm, and an optional duration control to limit the length of time the alarm sounds when turned on. Each time "true" is written to the On/Off resource, the alarm will sound again for the configured duration. If no duration is programmed or the setting is "false", writing a "true" to the On/Off resource will result in the alarm sounding continuously until a "false" is written to the On/Off resource.ext-labelBuzzer3338https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3338-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33381.0This IPSO object should be used to actuate an audible alarm such as a buzzer, beeper, or vibration alarm. There is a dimmer control for setting the relative level of the alarm, and an optional duration control to limit the length of time the alarm sounds when turned on. Each time "true" is written to the On/Off resource, the alarm will sound again for the configured duration. If no duration is programmed or the setting is "false", writing a "true" to the On/Off resource will result in the alarm sounding continuously until a "false" is written to the On/Off resource.ext-labelBuzzer3338https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3338.xml1IPSO Alliance0urn:oma:lwm2m:ext:3338:1.11.1This IPSO object should be used for a speaker that plays a pre-recorded audio clip or an audio output that is sent elsewhere. For example, an elevator which announces the floor of the building. A resource is provided to store the clip, a dimmer resource controls the relative sound level of the playback, and a duration resource limits the maximum playback time. After the duration time is reached, any remaining samples in the clip are ignored, and the clip player will be ready to play another clip.ext-labelAudio Clip3339https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3339.xml1IPSO Alliance0urn:oma:lwm2m:ext:33391.0This IPSO object is used to time events and actions, using patterns common to industrial timers. A write 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. The patterns supported are One-Shot (mode 1), On-Time or Interval (mode 2), Time delay on pick-up or TDPU (mode 3), and Time Delay on Drop-Out or TDDO (mode 4). Mode 0 disables the timer, so the output follows the input with no delay. A counter is provided to count occurrences of the timer output changing from 0 to 1. Writing a value of zero resets the counter. The Digital Input State resource reports the state of the timer output.ext-labelTimer3340https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3340.xml1IPSO Alliance0urn:oma:lwm2m:ext:33401.0This IPSO object is used to send text to a text-only or text mode graphics display. Writing a string of text to the text resource causes it to be displayed at the selected X and Y locations on the display. If X or Y are set to a value greater than the size of the display, the position "wraps around" to the modulus of the setting and the display size. Likewise, if the text string overflows the display size, the text "wraps around" and displays on the next line down or, if the last line has been written, wraps around to the top of the display. Brightness and Contrast controls are provided to allow control of various display types including STN and DSTN type LCD character displays. Writing an empty payload to the Clear Display resource causes the display to be erased.ext-labelAddressable Text Display3341https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3341.xml1IPSO Alliance0urn:oma:lwm2m:ext:33411.0This IPSO object should be used with an On/Off switch to report the state of the switch.ext-labelOn/Off switch3342https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3342-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33421.0This IPSO object should be used with an On/Off switch to report the state of the switch.ext-labelOn/Off switch3342https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3342.xml1IPSO Alliance0urn:oma:lwm2m:ext:3342:1.11.1This IPSO object should be used with a dimmer or level control to report the state of the control.ext-labelDimmer3343https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3343.xml1IPSO Alliance0urn:oma:lwm2m:ext:33431.0This IPSO object is used to report the state of an up/down control element like a pair of push buttons or a rotary encoder. Counters for increase and decrease operations are provided for counting pulses from a quadrature encoder.ext-labelUp/Down Control3344https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3344.xml1IPSO Alliance0urn:oma:lwm2m:ext:33441.0This 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.ext-labelMultiple Axis Joystick3345https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3345.xml1IPSO Alliance0urn:oma:lwm2m:ext:33451.0This object type should be used to report a rate measurement, for example the speed of a vehicle, or the rotational speed of a drive shaft. 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 per second (m/s).ext-labelRate3346https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3346-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33461.0This object type should be used to report a rate measurement, for example the speed of a vehicle, or the rotational speed of a drive shaft. 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 per second (m/s).ext-labelRate3346https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3346.xml1IPSO Alliance0urn:oma:lwm2m:ext:3346:1.11.1This 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.ext-labelPush button3347https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3347-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33471.0This 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.ext-labelPush button3347https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3347.xml1IPSO Alliance0urn:oma:lwm2m:ext:3347:1.11.1This IPSO object is used to represent the state of a Multi-state selector switch with a number of fixed positions.ext-labelMulti-state Selector3348https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3348-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33481.0This IPSO object is used to represent the state of a Multi-state selector switch with a number of fixed positions.ext-labelMulti-state Selector3348https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3348.xml1IPSO Alliance0urn:oma:lwm2m:ext:3348:1.11.1Summarize several digital inputs to one value by mapping each bit to a digital input.ext-labelBitmap3349https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3349-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33491.0Summarize several digital inputs to one value by mapping each bit to a digital input.ext-labelBitmap3349https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3349.xml1IPSO Alliance0urn:oma:lwm2m:ext:3349:1.11.1An ascending timer that counts how long time has passed since the timer was started after reset.ext-labelStopwatch3350https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3350-1_0.xml1IPSO Alliance0urn:oma:lwm2m:ext:33501.0An ascending timer that counts how long time has passed since the timer was started after reset.ext-labelStopwatch3350https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3350.xml1IPSO Alliance0urn:oma:lwm2m:ext:3350:1.11.1One time event sent by the device at power up.ext-labelpowerupLog3351https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3351.xml1GSMA0urn:oma:lwm2m:ext:33511.0List of all PLMNs found during the initial search/scanext-labelplmnSearchEvent3352https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3352.xml1GSMA0urn:oma:lwm2m:ext:33521.0serving cell information that the RRC decides to camp onext-labelscellID3353https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3353.xml1GSMA0urn:oma:lwm2m:ext:33531.0cell reselection event informationext-labelcellReselectionEvent3354https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3354.xml1GSMA0urn:oma:lwm2m:ext:33541.0handover event informationext-labelhandoverEvent3355https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3355.xml1GSMA0urn:oma:lwm2m:ext:33551.0Radio Link Failure Eventext-labelradioLinkFailureEvent3356https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3356.xml1GSMA0urn:oma:lwm2m:ext:33561.0Current RRC state change information, including the event that triggered the state changeext-labelrrcStateChangeEvent3357https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3357.xml1GSMA0urn:oma:lwm2m:ext:33571.0RRC timer expiry event informationext-labelrrcTimerExpiryEvent3358https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3358.xml1GSMA0urn:oma:lwm2m:ext:33581.0Cell blacklist informationext-labelcellBlacklistEvent3359https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3359.xml1GSMA0urn:oma:lwm2m:ext:33591.0ESM context informationext-labelesmContextInfo3360https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3360.xml1GSMA0urn:oma:lwm2m:ext:33601.0EMM context informationext-labelemmStateValue3361https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3361.xml1GSMA0urn:oma:lwm2m:ext:33611.0NAS EMM timer expiry informationext-labelnasEmmTimerExpiryEvent3362https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3362.xml1GSMA0urn:oma:lwm2m:ext:33621.0NAS ESM timer expiry informationext-labelnasEsmExpiryEvent3363https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3363.xml1GSMA0urn:oma:lwm2m:ext:33631.0Triggered at EMM failure - failure cause is loggedext-labelemmFailureCauseEvent3364https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3364.xml1GSMA0urn:oma:lwm2m:ext:33641.0RACH Latency & delay informationext-labelrachLatency_delay3365https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3365.xml1GSMA0urn:oma:lwm2m:ext:33651.0RACH information. Logged at RACH TXext-labelmacRachAttemptEvent3366https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3366.xml1GSMA0urn:oma:lwm2m:ext:33661.0RACH Information - reason for initiating RACHext-labelmacRachAttemptReasonEvent3367https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3367.xml1GSMA0urn:oma:lwm2m:ext:33671.0MAC timer expiry informationext-labelmacTimerStatusEvent3368https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3368.xml1GSMA0urn:oma:lwm2m:ext:33681.0Timing advance informationext-labelmacTimingAdvanceEvent3369https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3369.xml1GSMA0urn:oma:lwm2m:ext:33691.0Serving Cell Measurementext-labelServingCellMeasurement3370https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3370.xml1GSMA0urn:oma:lwm2m:ext:33701.0Neighbor Cell Measurementsext-labelNeighborCellMeasurements3371https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3371.xml1GSMA0urn:oma:lwm2m:ext:33711.0Timing Advance Informationext-labelTimingAdvance3372https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3372.xml1GSMA0urn:oma:lwm2m:ext:33721.0TX power headroom informationext-labeltxPowerHeadroomEvent3373https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3373.xml1GSMA0urn:oma:lwm2m:ext:33731.0Radio Link monitoring information maintained by RRCext-labelradioLinkMonitoring3374https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3374.xml1GSMA0urn:oma:lwm2m:ext:33741.0Paging DRX informationext-labelPagingDRX3375https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3375.xml1GSMA0urn:oma:lwm2m:ext:33751.0TX Power backoff informationext-labeltxPowerBackOffEvent3376https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3376.xml1GSMA0urn:oma:lwm2m:ext:33761.0RACH message 3 report informationext-labelMessage3Report3377https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3377.xml1GSMA0urn:oma:lwm2m:ext:33771.0Serving cell PBCH decoding informationext-labelPbchDecodingResults3378https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3378.xml1GSMA0urn:oma:lwm2m:ext:33781.0PUCCH TX power control informationext-labelpucchPowerControl3379https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3379.xml1GSMA0urn:oma:lwm2m:ext:33791.0PRACH report information. Deprecated by v2.0.ext-labelPrachReport3380https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3380-1_0.xml1GSMA0urn:oma:lwm2m:ext:33801.0PRACH report informationext-labelPrachReport3380https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3380.xml1GSMA0urn:oma:lwm2m:ext:3380:2.02.0VoLTE call statusext-labelVolteCallEvent3381https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3381.xml1GSMA0urn:oma:lwm2m:ext:33811.0SIP Registration statusext-labelSipRegistrationEvent3382https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3382.xml1GSMA0urn:oma:lwm2m:ext:33821.0SIP Publish statusext-labelsipPublishEvent3383https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3383.xml1GSMA0urn:oma:lwm2m:ext:33831.0SIP Subscription statusext-labelsipSubscriptionEvent3384https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3384.xml1GSMA0urn:oma:lwm2m:ext:33841.0VoLTE call status changeext-labelvolteCallStateChangeEvent3385https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3385.xml1GSMA0urn:oma:lwm2m:ext:33851.0Log is generated at the receiving end of RTP flow when newReceivedSequenceNumber - lastReceivedSequenceNumber > 1ext-labelVoLTErtpPacketLoss3386https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3386.xml1GSMA0urn:oma:lwm2m:ext:33861.0The 'oA Basic Control' represents a common basic interface for a Control Function. This allows to have vendor specific (executing) control functions using diverse object numbers to be interfaced for the basic functionality in a common way. The object provides the basic functionality required for an OpenAIS control object.ext-labeloA Basic Control3387https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3387.xml1OpenAIS0urn:oma:lwm2m:ext:33871.0The 'oA Device' represents the OpenAIS specific parameters of a Device that are necessary in addition to the LWM2M Device.ext-labeloA Device3388https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3388.xml1OpenAIS0urn:oma:lwm2m:ext:33881.0The 'oA Group' represents a group. It contains an application group ID, a security group ID and a list of multicast and unicast IP addresses that are used in the group. \nAdditionally it contains a list of all members of the group.ext-labeloA Group3389https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3389.xml1OpenAIS0urn:oma:lwm2m:ext:33891.0The 'oA Logical Colour Light Point Actuator' represents the logical part of an actuator model for a colour light point. The corresponding physical device is a light channel and associated gear (e.g. LED driver).\nThe Object (module) supports several interactions that include absolute and relative colour setting. Several device configuration parameters are mapped, which relate to behaviour or describe device limitations.ext-labeloA Logical Colour Light-Point Actuator3390https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3390.xml1OpenAIS0urn:oma:lwm2m:ext:33901.0The 'oA Logical Colour_Temperature Light Point Actuator' represents the logical part of an actuator model for a tunable white light point. The corresponding physical device is a light channel and associated gear (e.g. LED driver).\nThe Object (module) supports several interactions that include absolute and relative colour temperature setting. Several device configuration parameters are mapped, which relate to behaviour or describe device limitations. Note that the overall intensity is not controlled by this object, it remains controlled by a logical light point object to ease dimming action across tuneable, coloured and non coloured lights. Please note also, that the corresponding executing object does not need to be restricted to tuneable white operation.ext-labeloA Logical Colour Temperature Light-Point Actuator3391https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3391.xml1OpenAIS0urn:oma:lwm2m:ext:33911.0The 'oA Logical Illuminance Sensor' represents the logical part of an illuminance sensor. The corresponding physical device is a sensor that detects illuminance in its detection area.ext-labeloA Logical Illuminance Sensor3392https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3392.xml1OpenAIS0urn:oma:lwm2m:ext:33921.0The 'oA Logical Light Point Actuator' represents the logical part of an actuator model for a dimmable light point. The corresponding physical device is a light channel and associated gear (e.g. LED driver).\nThe Object (module) supports several interactions that include basic On/Off as well as Up/Down dimming. Several device configuration parameters are mapped, which relate to behaviour or describe device limitations. For multi-channel luminaires where the configuration per channel may vary significantly (e.g. different max/min values), multiple instances of this Object should be used.ext-labeloA Logical Light-Point Actuator3393https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3393.xml1OpenAIS0urn:oma:lwm2m:ext:33931.0The 'oA Logical Presence Sensor' represents the logical part of a presence sensor. The corresponding physical device is a sensor that detects presence in its detection area. \nThe Object supports two states 'presence' and 'absence'.ext-labeloA Logical Presence Sensor3394https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3394.xml1OpenAIS0urn:oma:lwm2m:ext:33941.0The 'oA Logical Push-Button Sensor' represents the logical part of a standard, normally open, push-button input. The corresponding physical device is a button with a spring that returns the button to the un-pushed state once it is released.\nThe Object supports several events such as 'click', 'hold', 'double-click' and 'release'. It also indicates if the button is 'stuck'. For physical devices with multiple push-button inputs, an instance of this Object is required to map each input.ext-labeloA Logical Push-Button Sensor3395https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3395.xml1OpenAIS0urn:oma:lwm2m:ext:33951.0The 'oA_Physical_Colour_Light-Point_Actuator' represents a physical colour light-point actuator. It is necessary to map at least on Logical Light Point Actuator to control the intensity and one Logical Colour Light-Point to control the colour to the Physical Colour Light-Point.ext-labeloA Physical Colour Light-Point Actuator3396https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3396.xml1OpenAIS0urn:oma:lwm2m:ext:33961.0The 'oA_Physical_Colour_Temperature_Light-Point_Actuator' represents a physical tunable white light-point actuator. It is necessary to map at least on Logical Light Point Actuator to control the intensity and one Logical Colour Temperature Light-Point to control the colour temperature to the Physical Colour Temperature Light Point.ext-labeloA Physical Colour Temperature Light-Point Actuator3397https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3397.xml1OpenAIS0urn:oma:lwm2m:ext:33971.0The 'oA_Physical_Illuminance_Sensor' represents the physical part of an illuminance sensor. All logical illuminance sensors (object instances of 'oA Illuminance Sensor') are mapped to one physical illuminance sensor.ext-labeloA Physical Illuminance Sensor3398https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3398.xml1OpenAIS0urn:oma:lwm2m:ext:33981.0The 'oA_Physical_Light-Point_Actuator' represents a physical light-point actuator. All logical light-point actuators (object instances of 'oA Light-Point Actuator') are mapped to one physical light-point actuator.ext-labeloA Physical Light-Point Actuator3399https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3399.xml1OpenAIS0urn:oma:lwm2m:ext:33991.0The 'oA_Physical_Presence_Sensor' represents the physical part of a presence sensor. All logical presence sensors (object instances of 'oA Presence Sensor') are mapped to one physical presence sensor.ext-labeloA Physical Presence Sensor3400https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3400.xml1OpenAIS0urn:oma:lwm2m:ext:34001.0The 'oA_Physical_Push-Button_Sensor' represents the physical part of a push-button sensor. All logical push-button sensors (object instances of 'oA Push-Button Sensor') are mapped to one physical push-button sensor.ext-labeloA Physical Push-Button Sensor3401https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3401.xml1OpenAIS0urn:oma:lwm2m:ext:34011.0The 'oA Receiving Object' provides a resource for sensors/actuators to report their status message to. It is used with control objects as logical object that forwards the sensor and status data to the executing object.\nIt is also used to receive the 'go bootstrap' message, using the Struct-ID 255, in OOTB mode.ext-labeloA Receiving Object3402https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3402.xml1OpenAIS0urn:oma:lwm2m:ext:34021.0The 'oA Reporting Object' packs several status messages available at the node into a single, size optimized message, as e.g. used with data collect or BMS interfacing.ext-labeloA Reporting Object3403https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3403.xml1OpenAIS0urn:oma:lwm2m:ext:34031.0The 'oA Scene' represents a scene model. The scene holds defined values for each actuator in one group.ext-labeloA Scene3404https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3404.xml1OpenAIS0urn:oma:lwm2m:ext:34041.0The 'OGC Security' provides the appropriate keying material for a specific OGC Application group in the context of OGC. The keying material will be provided by a key distribution server, and must not be readable by any instance outside the local node.ext-labeloA OGC-Security3405https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3405.xml1OpenAIS0urn:oma:lwm2m:ext:34051.0The 'oA Status_Report_Structure' describes the content of the status reports. Its ID is always the first byte, the following bytes are defined by Keys.ext-labeloA Status Report Structure3406https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3406.xml1OpenAIS0urn:oma:lwm2m:ext:34061.0This is an alarm that should be raised if the meter detects CO2 concentration above a pre-configured threshold.ext-labelSmoke Alarm3407https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3407.xml1IoT Connectivity Alliance0urn:oma:lwm2m:ext:34071.0Describe the status of a manhole cover.ext-labelManhole Cover3408https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3408.xml1IoT Connectivity Alliance0urn:oma:lwm2m:ext:34081.0The uCIFI device extension is an extension to the standard Lightweight M2M device (object ID 3) using the resource called "ExtDevInfo" (resource ID 22).ext-labelDevice Extension3410https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3410-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34101.0The uCIFI device extension is an extension to the standard Lightweight M2M device (object ID 3) using the resource called "ExtDevInfo" (resource ID 22).ext-labelDevice Extension3410https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3410.xml1uCIFI0urn:oma:lwm2m:ext:3410:2.02.0The uCIFI battery object provides attributes to monitor battery level and activity.ext-labelBattery3411https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3411-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34111.0The uCIFI battery object provides attributes to monitor battery level and activity.ext-labelBattery3411https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3411.xml1uCIFI0urn:oma:lwm2m:ext:3411:1.11.1The uCIFI communication object provides attributes related to the communication on the LPWAN network, including multicast grouping.ext-labelLPWAN Communication3412https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3412-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34121.0The uCIFI communication object provides attributes related to the communication on the LPWAN network, including multicast grouping.ext-labelLPWAN Communication3412https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3412.xml1uCIFI0urn:oma:lwm2m:ext:3412:1.11.1The uCIFI generic actuator may be used for any actuator but not to replace Outdoor Lamp Controllers nor for an Irrigation Valves which have a specific device type in the uCIFI data model.ext-labeluCIFI Generic Actuator3413https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3413-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34131.0The uCIFI generic actuator may be used for any actuator but not to replace Outdoor Lamp Controllers nor for an Irrigation Valves which have a specific device type in the uCIFI data model.ext-labeluCIFI Generic Actuator3413https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3413.xml1uCIFI0urn:oma:lwm2m:ext:3413:1.11.1The uCIFI data bridge object may be used to transport data from a 3rd party device, operating a proprietary network or protocol, over a LwM2M compliant network.ext-labeluCIFI data bridge3414https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3414-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34141.0The uCIFI data bridge object may be used to transport data from a 3rd party device, operating a proprietary network or protocol, over a LwM2M compliant network.ext-labeluCIFI data bridge3414https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3414.xml1uCIFI0urn:oma:lwm2m:ext:3414:2.02.0The uCIFI time synchronization object enables a device to sync-up its internal clock with a remote NTP server.ext-labelTime synchronization3415https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3415-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34151.0The uCIFI time synchronization object enables a device to sync-up its internal clock with a remote NTP server.ext-labelTime synchronization3415https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3415.xml1uCIFI0urn:oma:lwm2m:ext:3415:2.02.0The uCIFI outdoor lamp controller object provides attributes to control, command and monitor outdoor luminaires in streets, in tunnels, on roads and for illumination of park and gardens.ext-labelOutdoor lamp controller3416https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3416-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34161.0The uCIFI outdoor lamp controller object provides attributes to control, command and monitor outdoor luminaires in streets, in tunnels, on roads and for illumination of park and gardens.ext-labelOutdoor lamp controller3416https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3416-2_0.xml1uCIFI0urn:oma:lwm2m:ext:3416:2.02.0The uCIFI outdoor lamp controller object provides attributes to control, command and monitor outdoor luminaires in streets, in tunnels, on roads and for illumination of park and gardens.ext-labelOutdoor lamp controller3416https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3416.xml1uCIFI0urn:oma:lwm2m:ext:3416:3.03.0The uCIFI luminaire asset is an object that enables outdoor lighting control software to configure outdoor lamp controllers. It also enables outdoor lamp controllers to send Zhaga D4i or DALI attributes read from the control gears, to centrally managed outdoor lighting control software or asset management systems.ext-labelLuminaire asset3417https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3417.xml1uCIFI0urn:oma:lwm2m:ext:34171.0The uCIFI electrical monitor object provides attributes related to the analysis of electrical consumption in an outdoor luminaire or in a streetlight cabinet. It also identifies electrical anomalies.ext-labelElectrical monitor3418https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3418-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34181.0The uCIFI electrical monitor object provides attributes related to the analysis of electrical consumption in an outdoor luminaire or in a streetlight cabinet. It also identifies electrical anomalies.ext-labelElectrical monitor3418https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3418-2_0.xml1uCIFI0urn:oma:lwm2m:ext:3418:2.02.0The uCIFI electrical monitor object provides attributes related to the analysis of electrical consumption in an outdoor luminaire or in a streetlight cabinet. It also identifies electrical anomalies.ext-labelElectrical monitor3418https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3418.xml1uCIFI0urn:oma:lwm2m:ext:3418:2.12.1A uCIFI photocell object is used for lighting control, particularly to identify when light should be switched ON/OFF.ext-labelPhotocell3419https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3419-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34191.0A uCIFI photocell object is used for lighting control, particularly to identify when light should be switched ON/OFF.ext-labelPhotocell3419https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3419.xml1uCIFI0urn:oma:lwm2m:ext:3419:1.11.1The uCIFI LED color light enables to control light colors of a LED luminaire.ext-labelLED color light3420https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3420.xml1uCIFI0urn:oma:lwm2m:ext:34201.0The uCIFI single-phase electrical meter measures the electrical consumption of loads on one electrical line, such as electrical cabinets in city infrastructures, street lighting networks, homes and buildings.ext-labelSingle-phase electrical meter3421https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3421-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34211.0The uCIFI single-phase electrical meter measures the electrical consumption of loads on one electrical line, such as electrical cabinets in city infrastructures, street lighting networks, homes and buildings.ext-labelSingle-phase electrical meter3421https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3421.xml1uCIFI0urn:oma:lwm2m:ext:3421:2.02.0The uCIFI three-phase electrical meter complement gathers all the measures, events, threshold and other resources required to create a full three-phase electrical meter together with three additional uCIFI single-phase electrical meters.ext-labelThree-phase electrical meter complement3422https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3422.xml1uCIFI0urn:oma:lwm2m:ext:34221.0The uCIFI gas meter measures the volume of gas that was distributed through the gas meter, in pulse count and/or in m3. It also detects anomalies in the gas meter.ext-labelGas meter3423https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3423-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34231.0The uCIFI gas meter measures the volume of gas that was distributed through the gas meter, in pulse count and/or in m3. It also detects anomalies in the gas meter.ext-labelGas meter3423https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3423.xml1uCIFI0urn:oma:lwm2m:ext:3423:1.11.1The uCIFI water meter measures water volume that was distributed through a water meter, in pulse count as well as in m3. It also detects anomalies in the water meter.ext-labelWater meter3424https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3424-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34241.0The uCIFI water meter measures water volume that was distributed through a water meter, in pulse count as well as in m3. It also detects anomalies in the water meter.ext-labelWater meter3424https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3424.xml1uCIFI0urn:oma:lwm2m:ext:3424:1.11.1The uCIFI irrigation valve provides a way to control and monitor an irrigation valve.ext-labelIrrigation valve3425https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3425-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34251.0The uCIFI irrigation valve provides a way to control and monitor an irrigation valve.ext-labelIrrigation valve3425https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3425.xml1uCIFI0urn:oma:lwm2m:ext:3425:1.11.1The uCIFI water quality sensor measures the quality of the water in the drinkable water distribution network, in water tanks or in lakes and rivers.ext-labelWater quality sensor3426https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3426-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34261.0The uCIFI water quality sensor measures the quality of the water in the drinkable water distribution network, in water tanks or in lakes and rivers.ext-labelWater quality sensor3426https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3426.xml1uCIFI0urn:oma:lwm2m:ext:3426:1.11.1The uCIFI water pressure monitoring sensor measures water pressure and help identify water leaks in water distribution pipelines.ext-labelPressure monitoring sensor3427https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3427-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34271.0The uCIFI water pressure monitoring sensor measures water pressure and help identify water leaks in water distribution pipelines.ext-labelPressure monitoring sensor3427https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3427.xml1uCIFI0urn:oma:lwm2m:ext:3427:1.11.1The uCIFI air quality sensor reports measurement required to calculate Air Quality Index (AIQ. It also provides resources for average calculation as per the IQ index calculation.ext-labelAir quality3428https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3428-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34281.0The uCIFI air quality sensor reports measurement required to calculate Air Quality Index (AIQ. It also provides resources for average calculation as per the IQ index calculation.ext-labelAir quality3428https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3428.xml1uCIFI0urn:oma:lwm2m:ext:3428:2.02.0The uCIFI tilt sensor provides the angle between the object's internal vertical and the perpendicular to the earth.ext-labelTilt sensor3429https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3429-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34291.0The uCIFI tilt sensor provides the angle between the object's internal vertical and the perpendicular to the earth.ext-labelTilt sensor3429https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3429-1_1.xml1uCIFI0urn:oma:lwm2m:ext:3429:1.11.1The uCIFI tilt sensor provides the angle between the object's internal vertical and the perpendicular to the earth.ext-labelTilt sensor3429https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3429.xml1uCIFI0urn:oma:lwm2m:ext:3429:1.21.2More than a positioning object, the uCIFI global navigation satellite system object provides all the information required to calculate a position/location.ext-labelGlobal Navigation Satellite System3430https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3430-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34301.0More than a positioning object, the uCIFI global navigation satellite system object provides all the information required to calculate a position/location.ext-labelGlobal Navigation Satellite System3430https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3430.xml1uCIFI0urn:oma:lwm2m:ext:3430:2.02.0The uCIFI parking sensor provides actual and cumulated occupancy duration as well as forbidden parking detection.ext-labelParking Sensor3431https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3431-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34311.0The uCIFI parking sensor provides actual and cumulated occupancy duration as well as forbidden parking detection.ext-labelParking Sensor3431https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3431-1_1.xml1uCIFI0urn:oma:lwm2m:ext:3431:1.11.1The uCIFI parking sensor provides actual and cumulated occupancy duration as well as forbidden parking detection.ext-labelParking Sensor3431https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3431.xml1uCIFI0urn:oma:lwm2m:ext:3431:1.21.2The uCIFI traffic counter provides vehicle counting and traffic analysis data. A traffic counting device may implement multiple instances of this traffic counter object, each of them being in charge of counting different categories of vehicles (e.g. bikes, cars, trucks).ext-labelTraffic Counter3432https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3432-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34321.0The uCIFI traffic counter provides vehicle counting and traffic analysis data. A traffic counting device may implement multiple instances of this traffic counter object, each of them being in charge of counting different categories of vehicles (e.g. bikes, cars, trucks).ext-labelTraffic Counter3432https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3432-2_0.xml1uCIFI0urn:oma:lwm2m:ext:3432:2.02.0The uCIFI traffic counter provides vehicle counting and traffic analysis data. A traffic counting device may implement multiple instances of this traffic counter object, each of them being in charge of counting different categories of vehicles (e.g. bikes, cars, trucks).ext-labelTraffic Counter3432https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3432.xml1uCIFI0urn:oma:lwm2m:ext:3432:2.12.1The uCIFI noise sensor reports a noise measurement in decibel. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the noise sensor and some specific alarms resulting from noise analysis by the device.ext-labelNoise sensor3433https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3433-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34331.0The uCIFI noise sensor reports a noise measurement in decibel. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the noise sensor and some specific alarms resulting from noise analysis by the device.ext-labelNoise sensor3433https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3433.xml1uCIFI0urn:oma:lwm2m:ext:3433:1.11.1The uCIFI people counter provides people counting information using Bluetooth beacon or any other method.ext-labelPeople counter3434https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3434-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34341.0The uCIFI people counter provides people counting information using Bluetooth beacon or any other method.ext-labelPeople counter3434https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3434.xml1uCIFI0urn:oma:lwm2m:ext:3434:1.11.1The uCIFI filling level sensor measures how full and/or how empty a container (e.g. waste, fuel) is and reports it either in percentage or in centimeters. The filling level sensor may be complemented with a temperature sensor to compose a waste filling sensor that can also identify waste container fire.ext-labelFilling level3435https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3435-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34351.0The uCIFI filling level sensor measures how full and/or how empty a container (e.g. waste, fuel) is and reports it either in percentage or in centimeters. The filling level sensor may be complemented with a temperature sensor to compose a waste filling sensor that can also identify waste container fire.ext-labelFilling level3435https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3435.xml1uCIFI0urn:oma:lwm2m:ext:3435:2.02.0The uCIFI edge computing manager object defines the capability of a device to run scripts on the device itself.ext-labelEdge computing manager3436https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3436.xml1uCIFI0urn:oma:lwm2m:ext:34361.0The uCIFI edge computing scripts object defines a particular script to be executed by a device under a time or any other condition set by a "Edge Computing Time Condition" or "Edge Computing Generic Condition" object.ext-labelEdge computing script3437https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3437.xml1uCIFI0urn:oma:lwm2m:ext:34371.0The uCIFI edge computing time condition object defines the day/time (defined as a CRON rule) at which a particular script should be executed by a device.ext-labelEdge computing time condition3438https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3438.xml1uCIFI0urn:oma:lwm2m:ext:34381.0The uCIFI edge computing generic condition object defines a vendor-specific condition (e.g. when a resource or an object is equal to a particular value) at which a particular script should be executed by the device.ext-labelEdge computing generic condition3439https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3439.xml1uCIFI0urn:oma:lwm2m:ext:34391.0This object is for use in interoperability tests of the LwM2M v1.0 technical specification. It contains resources for each available datatype.ext-labelLwM2M v1.0 Test Object3441https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3441.xml1Eclipse Foundation0urn:oma:lwm2m:ext:34411.0This object aims to make easier to do interoperability tests about LWM2M v1.1. It contains resources for each available datatype.ext-labelLwM2M v1.1 Test Object3442https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3442.xml1Eclipse Foundation0urn:oma:lwm2m:ext:34421.0The interface between eIM and IPA as described in GSMA SGP.32.ext-labeleSIM IoT3443https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3443.xml1GSMA0urn:oma:lwm2m:ext:34431.0The uCIFI Stream Gauge measures the elevation of the water level surface and/or volumetric discharge.ext-labelStream Gauge3445https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3445-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34451.0The uCIFI Stream Gauge measures the elevation of the water level surface and/or volumetric discharge.ext-labelStream Gauge3445https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3445.xml1uCIFI0urn:oma:lwm2m:ext:3445:1.11.1The uCIFI rain gauge is a device that measures the quantity of rain fall.ext-labelRain Gauge3446https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3446-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34461.0The uCIFI rain gauge is a device that measures the quantity of rain fall.ext-labelRain Gauge3446https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3446.xml1uCIFI0urn:oma:lwm2m:ext:3446:1.11.1The uCIFI LPWAN Mesh Connectivity object enables monitoring and management of parameters related with the operation of 802.15.4-based LPWAN devices.ext-labelLPWAN Mesh Connectivity3447https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3447.xml1uCIFI0urn:oma:lwm2m:ext:34471.0The uCIFI LPWAN Mesh Statistics object enables the client to collect statistical information specifically tailored to monitor performance of 805.15.4 mesh networks. The object encompasses resources that provide visibility over both MAC layer and Network Layer statistics, the applicability of which is dependent on the specific 802.15.4 technology.ext-labelLPWAN Mesh Statistics3448https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3448.xml1uCIFI0urn:oma:lwm2m:ext:34481.0The uCIFI anemometer is a sensor used to record speed and direction of wind. It is designed following the IPSO object reference.ext-labelAnemometer3449https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3449-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34491.0The uCIFI anemometer is a sensor used to record speed and direction of wind. It is designed following the IPSO object reference.ext-labelAnemometer3449https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3449.xml1uCIFI0urn:oma:lwm2m:ext:3449:1.11.1The uCIFI Wet Bulb Globe Temperature is a temperature sensor that extends the standard IPSO Temperature object reference and can be used to record apparent temperature based on WBGT calculation. The measure comes from applying specific formula that take into account environmental measurements, such as temperature, humidity, wind speed, radiation.ext-labelWet Bulb Globe Temperature3450https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3450.xml1uCIFI0urn:oma:lwm2m:ext:34501.0The uCIFI Roll Over Sensor is used to measure the roll component of displacement and can be useful in safety application, by complementing the existing IPSO Direction and uCIFI Tilt sensors.ext-labelRoll over sensor3451https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3451.xml1uCIFI0urn:oma:lwm2m:ext:34511.0Summary of the mapping between the various functions, eventual inputs and the target actuators, spanning multiple days or years.ext-labelProgram Scheduler3452https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3452.xml1uCIFI0urn:oma:lwm2m:ext:34521.0Allows to specify when to execute a particular function.ext-labelCalendar Rule3453https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3453.xml1uCIFI0urn:oma:lwm2m:ext:34531.0Describes the behavior that controls the associated target based on time or sensor status.ext-labelProgram Function3454https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3454.xml1uCIFI0urn:oma:lwm2m:ext:34541.0The uCIFI Input Filter can be used to fine tune the sensor evaluation, in order to provide hold functionality or custom filtering. To be used in conjunction with a Program Scheduler.ext-labelInput Filter3455https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/3455-1_0.xml1uCIFI0urn:oma:lwm2m:ext:34551.0The uCIFI Input Filter can be used to fine tune the sensor evaluation, in order to provide hold functionality or custom filtering. To be used in conjunction with a Program Scheduler.ext-labelInput Filter3455https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3455.xml1uCIFI0urn:oma:lwm2m:ext:3455:2.02.0The uCIFI Output Filter can be used to fine tune the output commands in order, for example, to achieve a prolonged fade. To be used in conjunction with a Program Scheduler.ext-labelOutput Filter3456https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3456.xml1uCIFI0urn:oma:lwm2m:ext:34561.0The uCIFI Program Manager describes the scheduling capabilities of the device, referring to Program Schedulers, Program Functions, Calendar Rules and Filters.ext-labelProgram Manager3457https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3457.xml1uCIFI0urn:oma:lwm2m:ext:34571.0The uCIFI Program Monitor exports some useful information related to program execution.ext-labelProgram Monitor3458https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3458.xml1uCIFI0urn:oma:lwm2m:ext:34581.0The uCIFI Distributed Sensor Group allows to configure a device to publish or subscribe to device-to-device communication.ext-labelDistributed Sensor Group3459https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3459.xml1uCIFI0urn:oma:lwm2m:ext:34591.0The uCIFI Distributed Sensor Message provides the format of data being exchanged within the Distributed Sensor Group communication.ext-labelDistributed Sensor Message3460https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3460.xml1uCIFI0urn:oma:lwm2m:ext:34601.0This object is used to notify the user about the capabilities supported by the device in respect to Distributed Sensot Group functionality.ext-labelSensor Group Device Capabilities3461https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3461.xml1uCIFI0urn:oma:lwm2m:ext:34611.0The uCIFI Test Object can be used to simply simulate external stimulus, anomalous conditions, or any kind of alarm.ext-labeluCIFI Test Object3463https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3463.xml1uCIFI0urn:oma:lwm2m:ext:34631.0A virtual sensor may hold any kind of value to be read or written by the user and being possibly used elsewhereext-labeluCIFI Virtual Sensor3464https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3464.xml1uCIFI0urn:oma:lwm2m:ext:34641.0Reservation from 3465 to 3480ext-labelTBD34650TBD0urn:oma:lwm2m:ext:34651.0Reservation from 3465 to 3480ext-labelTBD34800TBD0urn:oma:lwm2m:ext:34801.0Reservation from 3500 to 3599ext-labelTBD35000TBD0urn:oma:lwm2m:ext:35001.0Reservation from 3500 to 3599ext-labelTBD35990TBD0urn:oma:lwm2m:ext:35991.0This LwM2M Object provides a bi-directional messaging facility for applications. Distinct resources are defined for Client to Server messaging and Server to Client messaging.ext-labelAppMessaging3600https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3600.xml1GEISA0urn:oma:lwm2m:ext:36001.0This LwM2M Object provides a facility for monitoring resource utilization of a GEISA edge environment.ext-labelHostMonitoring3601https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3601.xml1GEISA0urn:oma:lwm2m:ext:36011.0This LwM2M Object provides facilities for service flow level accounting and throttling per application.ext-labelAppAccounting3602https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/3602.xml1GEISA0urn:oma:lwm2m:ext:36021.0Reservation for 3603ext-labelTBD36030TBD0urn:oma:lwm2m:ext:36031.0Reservation from 3604 to 3614ext-labelTBD36040TBD0urn:oma:lwm2m:ext:36041.0Reservation from 3604 to 3614ext-labelTBD36140TBD0urn:oma:lwm2m:ext:36141.0This 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.x-labelHostDeviceInfo10241https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10241.xml1AT&T0urn:oma:lwm2m:x:102411.0This Object provides the information to represent a generic 3-Phase Power Meter.x-label3-Phase Power Meter10242https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10242.xml1Odins0urn:oma:lwm2m:x:102421.0This Object provides the information to represent a generic Single-Phase Power Meter.x-labelSingle-Phase Power Meter10243https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10243-1_0.xml1Odins0urn:oma:lwm2m:x:102431.0This Object provides the information to represent a generic Single-Phase Power Meter.x-labelSingle-Phase Power Meter10243https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10243.xml1Odins0urn:oma:lwm2m:x:10243:2.02.0This Object provides the information to represent a generic VCU(vehicle control unit).x-labelVehicleControlUnit10244https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10244.xml1Works System0urn:oma:lwm2m:x:102441.0This 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.x-labelRelay Management10245https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10245.xml1Vodafone Group Services Ltd0urn:oma:lwm2m:x:102451.0This LWM2M Object provides CrowdBox-related measurements such as serving cell parameters, backhaul timing advance, and neighbour cell reports.x-labelCrowdBox Measurements10246https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10246.xml1Vodafone Group Services Ltd0urn:oma:lwm2m:x:102461.0This 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.x-labelNeighbour Cell Report10247https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10247.xml1Vodafone Group Services Ltd0urn:oma:lwm2m:x:102471.0This LWM2M Object provides a range of measurements of connected UEs and provides an Object link to the Connected UE report.x-labelConnected UE Measurements10248https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10248.xml1Vodafone Group Services Ltd0urn:oma:lwm2m:x:102481.0This LWM2M Object provides a range of information related to the connected UEs.x-labelConnected UE Report10249https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10249.xml1Vodafone Group Services Ltd0urn:oma:lwm2m:x:102491.0This LWM2M Object is used for reporting application data of a device.x-labelApp Data Container10250https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10250.xml1Huawei Technologies Co., Ltd.0urn:oma:lwm2m:x:102501.0Used to execute an AT command on a cellular modemx-labelAT Command10251https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10251.xml1Cisco0urn:oma:lwm2m:x:102511.0This object provides a range of information related to updating packages on a devicex-labelManifest10252https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10252.xml1ARM Limited0urn:oma:lwm2m:x:102521.0This LWM2M Object is used for reporting data, but in a confidential wayx-labelConfidential Data10253https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10253.xml1Lab R&D Atos Pessac0urn:oma:lwm2m:x:102531.0This LWM2M Object provides a representation of a current loop sensor, which indicates the value emitted by a current source.x-labelCurrent Loop Input10254https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10254.xml1World-Direct eBusiness0urn:oma:lwm2m:x:10254:1.01.0This object provides a range of information related to device metadatax-labelDevice Metadata10255https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10255.xml1ARM Limited0urn:oma:lwm2m:x:102551.0This LWM2M Object provides ECID signal measurements of a device.x-labelECID-Signal Measurement Information10256https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10256.xml1Huawei Technologies0urn:oma:lwm2m:x:102561.0This Object provides the information to represent a generic (district) heat or cooling meterx-labelHeat / Cooling meter10257https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10257.xml1Comsel System Ltd0urn:oma:lwm2m:x:102571.0This LWM2M Object provides a representation of a current loop source, which may be used to carry control signals.x-labelCurrent Loop Output10258https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10258.xml1World-Direct eBusiness0urn:oma:lwm2m:x:102581.0This object provides read access to log buffers as well as limited configuration of logging services.x-labelSystem Log10259https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10259.xml1Casa Systems0urn:oma:lwm2m:x:102591.0This object allows manipulation of Runtime Database variables. Object deprecated with version 2.0 due to incorrect Type/Operation combination.x-labelRuntime Database10260https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10260-1_0.xml1Casa Systems0urn:oma:lwm2m:x:102601.0This object allows manipulation of Runtime Database variables.x-labelRDB10260https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10260.xml1Casa Systems0urn:oma:lwm2m:x:10260:2.02.0The Interval Data Delivery object provides an optimised means for managing the delivery of interval data from multiple Interval Data Object instances.x-labelInterval Data Delivery10262https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10262.xml1South East Water Corporation0urn:oma:lwm2m:x:102621.0The Event Data Delivery object provides a simple means for managing the delivery of event data from multiple Event Data Object instances.x-labelEvent Data Delivery10263https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10263.xml1South East Water Corporation0urn:oma:lwm2m:x:102631.0The Delivery Schedule object provides a means for controlling the periodic delivery of interval and event data to the LwM2M server.x-labelDelivery Schedule10264https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10264.xml1South East Water Corporation0urn:oma:lwm2m:x:102641.0The leakage detection configuration object provides a means for configuring the timing and sampling frequency of a vibration based network leak detectorx-labelLeakage Detection Configuration10265https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10265.xml1South East Water Corporation0urn:oma:lwm2m:x:102651.0Measures the flow of water in regular intervalsx-labelWater Flow Readings10266https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10266.xml1South East Water Corporation0urn:oma:lwm2m:x:102661.0Measures the maximum flow rate and its time stamp for specified periodx-labelDaily Maximum Flow Rate Readings10267https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10267.xml1South East Water Corporation0urn:oma:lwm2m:x:102671.0Periodic temperature measurementsx-labelTemperature Readings10268https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10268.xml1South East Water Corporation0urn:oma:lwm2m:x:102681.0Periodic pressure measurementsx-labelPressure Readings10269https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10269.xml1South East Water Corporation0urn:oma:lwm2m:x:102691.0Periodic battery level measurementsx-labelBattery Level Readings10270https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10270.xml1South East Water Corporation0urn:oma:lwm2m:x:102701.0Measures the total duration that the meter was activating its radio for packet transmission or receipt for the period. Used to monitor for excess poower usage over time.x-labelCommunications Activity Time Readings10271https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10271.xml1South East Water Corporation0urn:oma:lwm2m:x:102711.0A binary flag indicating continual usage (e.g. greater than 5 L/h for 24 hours and the flow never returning to zero at any time).x-labelWater Meter Customer Leakage Alarm10272https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10272.xml1South East Water Corporation0urn:oma:lwm2m:x:102721.0An alarm indicating reverse flow through the pipe. Also supports delivery of the approximate volume of water flowing in the reverse direction in the preceding period.x-labelWater Meter Reverse Flow Alarm10273https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10273.xml1South East Water Corporation0urn:oma:lwm2m:x:102731.0An alarm when meter detects there is no liquid in the pipex-labelWater Meter Empty Pipe Alarm10274https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10274.xml1South East Water Corporation0urn:oma:lwm2m:x:102741.0Detects interference from strong magnetic field or other electrical sources. If this is not relevant for ultrasonic meters then the tamper alarm may be used to indicate someone attempting to open the physical enclosure or other options the manufacturer may present.x-labelWater Meter Tamper Alarm10275https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10275.xml1South East Water Corporation0urn:oma:lwm2m:x:102751.0Where supported by the meter this is an alarm that should be raised if the meter detects pressure above a pre-configured threshold.x-labelWater Meter High Pressure Alarm10276https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10276.xml1South East Water Corporation0urn:oma:lwm2m:x:102761.0Where supported by the meter this is an alarm that should be raised if the meter detects pressure below a pre-configured threshold.x-labelWater Meter Low Pressure Alarm10277https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10277.xml1South East Water Corporation0urn:oma:lwm2m:x:102771.0Where supported by the meter this is an alarm that should be raised if the meter detects temperature above a pre-configured threshold. When the temperature drops below the clear threshold, the alarm should be cleared.x-labelHigh Temperature Alarm10278https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10278.xml1South East Water Corporation0urn:oma:lwm2m:x:102781.0Where supported by the meter this is an alarm that should be raised if the meter detects temperature below a pre-configured threshold. When the temperature rises above the clear threshold, the alarm should be clearedx-labelLow Temperature Alarm10279https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10279.xml1South East Water Corporation0urn:oma:lwm2m:x:102791.0All meters must support the following default configuration. This alarm will be based on the frequency output of the vibration sensor/accelerometer on the SEW Daughter board. When a frequency is identified that has the characteristics of an upstream network leak, and its amplitude is above the defined threshold, the meter will report this as a network leak alarm.x-labelWater Network Leak Alarm10280https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10280.xml1South East Water Corporation0urn:oma:lwm2m:x:102801.0This Alarm is raised when the battery voltage drops below a defined levelx-labelLow Battery Alarm10281https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10281.xml1South East Water Corporation0urn:oma:lwm2m:x:102811.0This binary status should indicate that the meter MCU can no longer communicate with a daughter boardx-labelDaughter Board Failure Alarm10282https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10282.xml1South East Water Corporation0urn:oma:lwm2m:x:102821.0This event records the fact that the device has rebootedx-labelDevice Reboot Event10283https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10283.xml1South East Water Corporation0urn:oma:lwm2m:x:102831.0This alarm records the fact that a significant (e.g. >5mins) time adjustment was required on the devicex-labelTime Synchronisation Event10284https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10284.xml1South East Water Corporation0urn:oma:lwm2m:x:102841.0Where supported by the device this is an alarm that should be raised if the device detects presence above a pre-configured threshold.x-labelPresence Alarm10285https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10285.xml1South East Water Corporation0urn:oma:lwm2m:x:102851.0This LWM2M Object is used to download the firmware package of a device's application.x-labelApp Fota Container10286https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10286.xml1Huawei0urn:oma:lwm2m:x:102861.0Periodic current measurements that are logged into CBOR structure payloadx-labelCurrent Logging10288https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10288.xml1South East Water Corporation0urn:oma:lwm2m:x:102881.0Periodic voltage measurements that are logged into CBOR structure payloadx-labelVoltage Logging10290https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10290.xml1South East Water Corporation0urn:oma:lwm2m:x:102901.0Object for sampling high frequency values (in this case Voltage readings) in order to aggregate them and summarize them (Avg, Max, Min) and to then time-stamp and log these aggregates for packaging and transmission to the server. This allows for efficient data transfer of high frequency data, without the need to send huge amounts of raw data over the air.x-labelVoltage Transient10291https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10291.xml1South East Water Corporation0urn:oma:lwm2m:x:102911.0Object for measuring high frequency pressure readings and summarizing/logging them at defined intervals. This way, the raw data does not need to be sent over the air, and instead just the Average , Maximum and Minimum values for the intervalx-labelPressure Transient10292https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10292.xml1South East Water Corporation0urn:oma:lwm2m:x:102921.0This 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.x-labelHostDevice10299https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10299.xml1Verizon Wireless0urn:oma:lwm2m:x:102991.0Use this meta object to provide one or more locations hosting XML data model definitions for reusable or private and vendor-specific devices, such as those in the range 26241-42768.x-labelLWM2M Meta Object10300https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10300.xml1TAU0urn:oma:lwm2m:x:103001.0The AT&T Connectivity Extension Object will be used to gather information describing the UE and the operating state of the UE. The AT&T Connectivity Extension Object is an open and standard object used by AT&T.x-labelAT&T Connectivity Extension10308https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10308-1_0.xml1AT&T0urn:oma:lwm2m:x:103081.0The AT&T Connectivity Extension Object will be used to gather information describing the UE and the operating state of the UE. The AT&T Connectivity Extension Object is an open and standard object used by AT&T.x-labelAT&T Connectivity Extension10308https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10308.xml1AT&T0urn:oma:lwm2m:x:10308:2.02.0This LwM2M Object provides the keying material of our technology product-ShareParkingLock.x-labelShareparkinglot10309https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10309.xml1XiangYiIOT Technologies0urn:oma:lwm2m:x:103091.0This Object is used to report solar irradiance (SI), i.e. power per unit area received from the Sun in the form of electromagnetic radiation, on a planar surface measured by a pyranometer or similar instrument. A pyranometer measures solar irradiance from the hemisphere above within a wavelength range 0.3 um to 3 um. For example, the application of solar radiation measurement can be meterological networks and solar energy applications.x-labelSolar Radiation10311https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10311-1_0.xml1Vaisala0urn:oma:lwm2m:x:103111.0This Object is used to report solar irradiance (SI), i.e. power per unit area received from the Sun in the form of electromagnetic radiation, on a planar surface measured by a pyranometer or similar instrument. A pyranometer measures solar irradiance from the hemisphere above within a wavelength range 0.3 um to 3 um. For example, the application of solar radiation measurement can be meterological networks and solar energy applications.x-labelSolar Radiation10311https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10311.xml1Vaisala0urn:oma:lwm2m:x:10311:1.11.1Object to periodically log readings from any gas sensor (eg H2S, VOCx, methane etc)x-labelGas Readings10313https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10313.xml1South East Water0urn:oma:lwm2m:x:103131.0This object should be used to report the concentration of particulates, for example a measurement of a particulates air quality sensor. It also provides resources for minimum/maximum measured values and the minimum/maximum range that can be measured by the particulate sensor. An example measurement unit is microgrammes per cubic metre ug/m3.x-labelParticulates10314https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10314.xml1OpenLX SP Ltd0urn:oma:lwm2m:x:103141.0This LWM2M Object includes robot information and links to the location object.x-labelRobot10315https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10315.xml1CloudMinds0urn:oma:lwm2m:x:103151.0This LWM2M Object includes RCU(Robotic Control Unit) information and the link to RCU APPs.x-labelRCU10316https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10316.xml1CloudMinds0urn:oma:lwm2m:x:103161.0This LWM2M Object includes RCU(Robotic Control Unit) PM information(counter and guage).x-labelRCU PM10318https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10318.xml1CloudMinds0urn:oma:lwm2m:x:103181.0This LWM2M Object includes all operations on RCUs.x-labelRCU Control10319https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10319.xml1CloudMinds0urn:oma:lwm2m:x:103191.0This LWM2M Object includes CCU(Central Control Unit) information and the link to CCU APPs.x-labelCCU10320https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10320.xml1CloudMinds0urn:oma:lwm2m:x:103201.0This LWM2M Object includes CCU PM(counter and gauge).x-labelCCU PM10322https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10322.xml1CloudMinds0urn:oma:lwm2m:x:103221.0This LWM2M Object includes all operations on CCUs.x-labelCCU Control10323https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10323.xml1CloudMinds0urn:oma:lwm2m:x:103231.0This LWM2M Object includes ECU(End Control Unit) information.x-labelECU10324https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10324.xml1CloudMinds0urn:oma:lwm2m:x:103241.0This LWM2M Object includes PM(counter and gauge) supported by all robots.x-labelRobot PM10326https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10326.xml1CloudMinds0urn:oma:lwm2m:x:103261.0This LWM2M Object includes the Compressor information.x-labelCompressor10327https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10327.xml1CloudMinds0urn:oma:lwm2m:x:103271.0This LWM2M Object includes all PM items belongs to a specific SCA.x-labelSCA PM10328https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10328.xml1CloudMinds0urn:oma:lwm2m:x:103281.0This LWM2M Object includes all operations on robots.x-labelRobot Control10329https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10329.xml1CloudMind0urn:oma:lwm2m:x:103291.0This LWM2M Object includes network status related information.x-labelNetwork Info10330https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10330.xml1CloudMinds0urn:oma:lwm2m:x:103301.0This LWM2M Object includes robot service related information.x-labelRobot Service Info10331https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10331.xml1CloudMinds0urn:oma:lwm2m:x:103311.0This LWM2M Object includes robot selfcheck result.x-labelRobot Selfcheck Info10332https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10332.xml1CloudMinds0urn:oma:lwm2m:x:103321.0Here defines all items needed in PM Threshold management.x-labelPM Threshold10333https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10333.xml1CloudMinds0urn:oma:lwm2m:x:103331.0Here lists all items of an alarm reported by the robot.x-labelRobot Alarm10334https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10334.xml1CloudMinds0urn:oma:lwm2m:x:103341.0Here lists all items of an event reported by the robot.x-labelEvent10335https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10335.xml1CloudMinds0urn:oma:lwm2m:x:103351.0This LWM2M Object includes MIC array information.x-labelMIC10336https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10336.xml1CloudMinds0urn:oma:lwm2m:x:103361.0This LWM2M Object includes SCA information.x-labelSCA10337https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10337.xml1CloudMinds0urn:oma:lwm2m:x:103371.0This LWM2M Object includes speaker information.x-labelSpeaker10338https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10338.xml1CloudMinds0urn:oma:lwm2m:x:103381.0This LWM2M Object includes Tripod Head information.x-labelTripod Head10339https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10339.xml1CloudMinds0urn:oma:lwm2m:x:103391.0This LWM2M Object includes camera information.x-labelCamera10340https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10340.xml1CloudMinds0urn:oma:lwm2m:x:103401.0This LWM2M Object includes GPS information.x-labelGPS10341https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10341.xml1CloudMinds0urn:oma:lwm2m:x:103411.0This LWM2M Object includes IMU(Inertial Measurement Unit) information.x-labelIMU10342https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10342.xml1CloudMinds0urn:oma:lwm2m:x:103421.0This LWM2M Object includes LiDAR information.x-labelLiDAR10343https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10343.xml1CloudMinds0urn:oma:lwm2m:x:103431.0This LWM2M Object includes arm information.x-labelArm10344https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10344.xml1CloudMinds0urn:oma:lwm2m:x:103441.0This LWM2M Object includes leg information.x-labelLeg10345https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10345.xml1CloudMinds0urn:oma:lwm2m:x:103451.0This LWM2M Object includes Servomotor information.x-labelServomotor10346https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10346.xml1CloudMinds0urn:oma:lwm2m:x:103461.0This LWM2M Object includes robot screen information.x-labelScreen10347https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10347.xml1CloudMinds0urn:oma:lwm2m:x:103471.0This LWM2M Object includes wheel information.x-labelWheel10348https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10348.xml1CloudMinds0urn:oma:lwm2m:x:103481.0This LWM2M Object includes chassis information.x-labelChassis10349https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10349.xml1CloudMinds0urn:oma:lwm2m:x:103491.0This LWM2M Object includes light information.x-labelLight10350https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10350.xml1CloudMinds0urn:oma:lwm2m:x:103501.0This LWM2M Object includes the door information.x-labelDoor10351https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10351.xml1CloudMinds0urn:oma:lwm2m:x:103511.0This LWM2M Object includes the Thermal Imager information.x-labelThermal Imager10352https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10352.xml1CloudMinds0urn:oma:lwm2m:x:103521.0This LWM2M Object includes Warning Light information.x-labelWarning Light10353https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10353.xml1CoudMinds0urn:oma:lwm2m:x:103531.0This LWM2M Object includes the APP information.x-labelAPP10354https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10354.xml1CloudMinds0urn:oma:lwm2m:x:103541.0This LWM2M Object contains the referrence to all general info objects of the robot.x-labelGeneral Info10355https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10355.xml1CloudMinds0urn:oma:lwm2m:x:103551.0This LWM2M Object contains the referrence to all objects containing service info.x-labelService Info10356https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10356.xml1CoudMinds0urn:oma:lwm2m:x:103561.0This LWM2M Object contains the referrence to all PM objects.x-labelPM10357https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10357.xml1CloudMinds0urn:oma:lwm2m:x:103571.0This LWM2M Object includes all PM items belongs to Fans.x-labelFan PM10358https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10358.xml1CloudMinds0urn:oma:lwm2m:x:103581.0This LWM2M Object includes the Lock information.x-labelLock10359https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10359.xml1CloudMinds0urn:oma:lwm2m:x:103591.0This LWM2M Object includes Ultrasonic Sensor information.x-labelUltrasonic Sensor10360https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10360.xml1CloudMinds0urn:oma:lwm2m:x:103601.0This LWM2M Object includes Collision Sensor information.x-labelCollision Sensor10361https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10361.xml1CloudMinds0urn:oma:lwm2m:x:103611.0This LWM2M Object includes Drop Sensor information.x-labelDrop Sensor10362https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10362.xml1CloudMinds0urn:oma:lwm2m:x:103621.0This LWM2M Object includes Temperature Sensor information.x-labelTemperature Sensor10363https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10363.xml1CloudMinds0urn:oma:lwm2m:x:103631.0This LWM2M Object includes Humidity Sensor information.x-labelHumidity Sensor10364https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10364.xml1CloudMinds0urn:oma:lwm2m:x:103641.0This LWM2M Object includes Gas-Dust information.x-labelGas-Dust Sensor10365https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10365.xml1CloudMinds0urn:oma:lwm2m:x:103651.0This LWM2M Object includes Fan information.x-labelFan10366https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10366.xml1CloudMinds0urn:oma:lwm2m:x:103661.0This LWM2M Object includes SpringMotor information.x-labelSpringMotor10368https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10368.xml1CloudMinds0urn:oma:lwm2m:x:103681.0This LWM2M Object includes MCU information.x-labelMCU10369https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10369.xml1CloudMinds0urn:oma:lwm2m:x:103691.0This object provides features allowing to monitor Reboot and Reset Factory operation from LWM2M Device object.x-labelReboot Status10371https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10371.xml1Sierra Wireless0urn:oma:lwm2m:x:103711.0This LwM2M Object is used to configure a Modbus protocol connection.x-labelModbus Connection10374https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10374.xml1AVSystem0urn:oma:lwm2m:x:103741.0This LwM2M Object represents a set of Modbus registers and acts as an interface to read and write their values.x-labelModbus Register Cluster10375https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10375.xml1AVSystem0urn:oma:lwm2m:x:103751.0Generic interface to set up periodic activity like hourly sensor reading/load activation and mechanism to retrieve the periodic data.x-labelPeriodic Activity10376https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10376.xml1George Kent Malaysia0urn:oma:lwm2m:x:103761.0Generic interface to set up data monitoring like sensor/log data and mechanism to receive alerts.x-labelData Monitoring10377https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10377.xml1George Kent Malaysia0urn:oma:lwm2m:x:103771.0This is used for UE to obtain information about suitable Edge Application Server in Edge Data Network, and to support service continuity for the UE to minimize service interruption.x-labelEdge Application Server Configuration10378https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10378.xml1Ericsson0urn:oma:lwm2m:x:103781.0The Event Profile object manages capture of Events and Alarms based on related Event Codes. The Event Profile object also acts as an efficient aggregator for Events and Alarms, that can help to optimize their delivery. Note: this object does not intent to manage deliveries of Events and Alarms.x-labelEvent Profile10379https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10379.xml1Itron0urn:oma:lwm2m:x:103791.0Reservation from 10379 to 10478x-labelTBD104780Itron0urn:oma:lwm2m:x:104781.0This LwM2M Object enables monitoring of available network bearers (or Radio Access Technologies - RATs) of cellular networks. Each instance of this Object holds information related to one network bearer incl. the associated PLMN. An object instance should be created for every RAT available for a PLMN, and for every PLMN visible to the device. The Object also allows steering the device towards a particular PLMN, or, to a particular PLMN+RAT combination.x-labelCellular Network and Bearer Control10479https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10479.xml1Vodafone0urn:oma:lwm2m:x:104791.0Reservation 10480x-labelTBD104800TBD0urn:oma:lwm2m:x:104801.0This Object supports triggering a network speed test and records the results. Furthermore, it allows to configure the server address of the server used for the speed test.x-labelNetwork Speed Test10481https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10481-1_0.xml1Vodafone0urn:oma:lwm2m:x:104811.0This Object supports triggering a network speed test and records the results. Furthermore, it allows to configure the server address of the server used for the speed test.x-labelNetwork Speed Test10481https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10481.xml1Vodafone0urn:oma:lwm2m:x:10481:2.02.0This LWM2M object is used between IoT Platform and Edge IoT Device Manager for control command and data exchangex-labelDYM IoT edge commands and data protocols10482https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10482.xml1DYM Labs0urn:oma:lwm2m:x:104821.0This LWM2M object is used to describe and modify Thread network configurationsx-labelThread Network10483https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10483.xml1HydroQuebec0urn:oma:lwm2m:x:104831.0This LwM2M Object enables commissioning (commissioner joiner add) of Thread devices on the Network. The target device must be have the "commissioner" and "joiner router" roles. Ex: "Border Router"x-labelThread Commissioning (joiner add)10484https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10484.xml1HydroQuebec0urn:oma:lwm2m:x:104841.0This LwM2M Object provides diagnostic information about Thread neighborsx-labelThread Neighbor Information10485https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10485.xml1HydroQuebec0urn:oma:lwm2m:x:104851.0This LwM2M Object provides access to issuing custom CLI commands to Thread devicesx-labelThread CLI Command10486https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10486.xml1HydroQuebec0urn:oma:lwm2m:x:104861.0Periodic water level measurementsx-labelWater Level Readings10487https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10487.xml1South East Water Corporation0urn:oma:lwm2m:x:104871.0Periodic tilt measurementsx-labelTilt Readings10488https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10488.xml1South East Water Corporation0urn:oma:lwm2m:x:104881.0Periodic trend (rate of change) measurementsx-labelTrend Readings10489https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10489.xml1South East Water Corporation0urn:oma:lwm2m:x:104891.0This alarm is raised when the water level in a tank, manhole, etc. exceeds the specified thresholdx-labelWater Level Alarm10490https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10490.xml1South East Water Corporation0urn:oma:lwm2m:x:104901.0This alarm is raised when the tilt/inclination of the device exceeds the specified thresholdx-labelTilt Alarm10491https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10491.xml1South East Water Corporation0urn:oma:lwm2m:x:104911.0This alarm is raised when the trend (rate of change) of a sensor input exceeds a specified threshold.x-labelTrend Alarm10492https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10492.xml1South East Water Corporation0urn:oma:lwm2m:x:104921.0This object provides site specific configuration for devices operating in a sewer manhole.x-labelManhole10493https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10493.xml1South East Water Corporation0urn:oma:lwm2m:x:104931.0The autosen Periodic Sensor Sampler object can be used to sample one or more sensor value(s) at periodic intervalsx-labelPeriodic Sensor Sampler10494https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10494-1_0.xml1autosen0urn:oma:lwm2m:x:104941.0The autosen Periodic Sensor Sampler object can be used to sample one or more sensor value(s) at periodic intervalsx-labelPeriodic Sensor Sampler10494https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10494.xml1autosen0urn:oma:lwm2m:x:10494:1.11.1The autosen Periodic Sensor Upload object can be used to upload sampled sensor data at periodic intervalsx-labelPeriodic Sensor Upload10495https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/version_history/10495-1_0.xml1autosen0urn:oma:lwm2m:x:104951.0The autosen Periodic Sensor Upload object can be used to upload sampled sensor data at periodic intervalsx-labelPeriodic Sensor Upload10495https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10495.xml1autosen0urn:oma:lwm2m:x:10495:1.11.1The autosen Sensor Alarm object can be used to set alarm conditions for sampled sensor data. If condition is true, an action could be triggered e.g. upload immediatelyx-labelSensor Alarm10496https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10496.xml1autosen0urn:oma:lwm2m:x:104961.0This object reports device specific fault codesx-labelFault Code10497https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10497.xml1South East Water Corporation0urn:oma:lwm2m:x:104971.0This LWM2M object provides water discharge events for a water tank monitoring device.x-labelDischarge10498https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10498.xml1South East Water Corporation0urn:oma:lwm2m:x:104981.0This alarm is raised when the water level fails to change within a given period of time after a discharge event is started.x-labelDischarge Alarm10499https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10499.xml1South East Water Corporation0urn:oma:lwm2m:x:104991.0This alarm is raised when the valve state fails to change after a given period of time. This alarm only applies to valves with the status feedback feature.x-labelValve Alarm10500https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10500.xml1South East Water Corporation0urn:oma:lwm2m:x:105001.0This event is recorded when a discharge event starts and stops.x-labelDischarge Status10501https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10501.xml1South East Water Corporation0urn:oma:lwm2m:x:105011.0This object provides site specific configuration for devices operating in a water tank.x-labelWater Tank10502https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10502.xml1South East Water Corporation0urn:oma:lwm2m:x:105021.0Reservation 10503x-labelTBD105030TBD0urn:oma:lwm2m:x:105031.0Reservation 10504x-labelTBD105040TBD0urn:oma:lwm2m:x:105041.0Reservation 10505x-labelTBD105050TBD0urn:oma:lwm2m:x:105051.0Reservation 10506x-labelTBD105060TBD0urn:oma:lwm2m:x:105061.0Periodic electrical conductivity measurementsx-labelElectrical Conductivity Readings10507https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10507.xml1South East Water Corporation0urn:oma:lwm2m:x:105071.0This alarm is raised when the electrical conductivity of the device exceeds the specified thresholdx-labelElectrical Conductivity Alarm10508https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10508.xml1South East Water Corporation0urn:oma:lwm2m:x:105081.0This object provides timing and sampling frequency configuration for a vibration-based leakage detectorx-labelLeakage Detection Configuration10509https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10509.xml1South East Water Corporation0urn:oma:lwm2m:x:105091.0Reservation 10510x-labelTBD105100TBD0urn:oma:lwm2m:x:105101.0Provides standardized diagnostic information about the current cellular connection, including serving cell identifiers, PLMN details, signal quality metrics, and SIM/eSIM parameters to support interoperability and troubleshooting.x-labelCellular Connectivity Diagnostics10511https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10511.xml1AVSystem0urn:oma:lwm2m:x:105111.0This LwM2M Object provides comprehensive management and monitoring of Starlink Gen3 satellite internet terminals. It enables remote access to telemetry, configuration, and control of Starlink dishes, including obstruction monitoring, alignment tracking, speed testing, and performance metrics. The object interfaces with the Starlink terminal via gRPC protocol (default endpoint: 192.168.100.1:9200).x-labelStarlink Terminal10512https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10512.xml1Walt Technologies0urn:oma:lwm2m:x:105121.0This LwM2M Object provides core router configuration and management capabilities for OpenWRT-based routers. It enables remote management of network parameters including LAN/WAN configuration, DHCP server settings, DNS configuration, and firewall controls. The object supports common router functions essential for IoT gateway deployments.x-labelRouter Management10513https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10513.xml1Walt Technologies0urn:oma:lwm2m:x:105131.0This LwM2M Object provides management and monitoring of Ethernet network interfaces on OpenWRT-based routers. It supports multiple instances for managing different physical Ethernet ports (WAN, LAN, etc.), providing real-time statistics on link status, speed, duplex mode, and traffic counters. Essential for monitoring router connectivity and network performance.x-labelEthernet Interface10514https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10514.xml1Walt Technologies0urn:oma:lwm2m:x:105141.0This LwM2M Object provides control and monitoring of GPIO (General Purpose Input/Output) pins on embedded devices. It supports management of LEDs, buttons, and general-purpose GPIO pins commonly found on OpenWRT routers. Multiple instances allow control of different GPIO resources, enabling remote status indication, user input monitoring, and custom hardware interfacing.x-labelGPIO Control10515https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10515.xml1Walt Technologies0urn:oma:lwm2m:x:105151.0This LwM2M Object provides monitoring and control of USB ports on embedded devices and routers. It supports multiple instances for managing different USB ports, providing information about connected devices, power management, and port status. Useful for OpenWRT routers with USB ports for storage, modems, or other peripherals.x-labelUSB Management10516https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10516.xml1Walt Technologies0urn:oma:lwm2m:x:105161.0This LwM2M Object provides management and monitoring of storage devices on embedded systems and routers. It supports multiple instances for managing different storage devices including internal NAND/NVMe, SD cards, and USB storage. Enables remote monitoring of storage capacity, usage, and basic management operations like mount/unmount and formatting.x-labelStorage Management10517https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10517.xml1Walt Technologies0urn:oma:lwm2m:x:105171.0This LwM2M Object provides comprehensive system monitoring for embedded Linux devices and routers. It reports CPU usage, memory statistics, thermal status, and system load metrics. Essential for remote monitoring of device health, performance, and resource utilization on OpenWRT-based routers and IoT gateways.x-labelSystem Monitor10518https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10518.xml1Walt Technologies0urn:oma:lwm2m:x:105181.0This LwM2M Object provides monitoring and management of hardware watchdog timers commonly found in embedded systems and IoT devices. The watchdog is a hardware timer that must be periodically reset ("petted") to prevent system reboot. This object enables remote configuration and monitoring of watchdog behavior, particularly useful for OpenWRT-based routers and similar embedded Linux devices.x-labelHardware Watchdog10519https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10519.xml1Walt Technologies0urn:oma:lwm2m:x:105191.0This LwM2M Object provides comprehensive management and monitoring of MIKROBUS sockets and Click boards. MIKROBUS is a standard for add-on boards that defines a specific pinout with SPI, I2C, UART, PWM, GPIO, and analog interfaces. This object enables remote configuration of interfaces, GPIO control, Click board detection, and power management. Supports multiple instances for managing multiple MIKROBUS sockets on a device.x-labelMIKROBUS10520https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10520.xml1Walt Technologies0urn:oma:lwm2m:x:105201.0This LwM2M Object provides management of firewall rules for OpenWRT-based routers. It enables remote configuration of iptables/nftables firewall rules including port filtering, IP address filtering, protocol filtering, and zone-based firewall management. Each instance represents a single firewall rule that can be created, modified, enabled/disabled, or deleted remotely. The object integrates with OpenWRT's UCI configuration system and supports both IPv4 and IPv6 rules.x-labelFirewall Config10521https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10521.xml1Walt Technologies0urn:oma:lwm2m:x:105211.0This LwM2M Object provides monitoring and control of Power over Ethernet (PoE) functionality on devices that support IEEE 802.3af/at/bt standards. It enables remote monitoring of PoE power input including voltage, current, and power consumption. For Powered Devices (PD), it provides visibility into the power being received. The object supports detection of PoE standard in use (af, at, bt), power class negotiation, and power cycling for recovery scenarios.x-labelPoE Management10522https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10522.xml1Walt Technologies0urn:oma:lwm2m:x:105221.0Controls buffering behaviour of the send scheduler.x-labelSend Scheduler Control10523https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10523.xml1EDF R&D0urn:oma:lwm2m:x:10523:1.01.0Defines per-resource sampling rules used by the send scheduler.x-labelSend Scheduler Sampling Rules10524https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10524.xml1EDF R&D0urn:oma:lwm2m:x:10524:1.01.0Multi-WAN failover configuration. Priority-based WAN selection, failover triggers, and load balancing policies.x-labelWAN Failover Policy105250Walt Technologies0urn:oma:lwm2m:x:105251.0WAN connection health monitoring with ping/HTTP checks, latency tracking, and automatic failover triggers.x-labelMulti-WAN Health Check105260Walt Technologies0urn:oma:lwm2m:x:105261.0Connected WiFi client tracking and management. Client statistics, signal strength, bandwidth usage, and access control.x-labelWiFi Client Management105270Walt Technologies0urn:oma:lwm2m:x:105271.0WiFi channel selection and optimization. Interference monitoring, automatic channel selection, and DFS management.x-labelWiFi Channel Optimization105280Walt Technologies0urn:oma:lwm2m:x:105281.0Matter protocol bridge functionality. Enables LwM2M-managed gateways to expose devices to Matter fabric ecosystems.x-labelMatter Bridge105290Walt Technologies0urn:oma:lwm2m:x:105291.0Individual Matter device representation. Device information, commissioning status, and endpoint management.x-labelMatter Device105300Walt Technologies0urn:oma:lwm2m:x:105301.0Thread mesh network management. Border router configuration, network formation, and mesh topology monitoring.x-labelThread Network105310Walt Technologies0urn:oma:lwm2m:x:105311.0Zigbee network coordinator management. Network formation, device joining, EZSP/Z-Stack support, and mesh orchestration.x-labelZigbee Coordinator105320Walt Technologies0urn:oma:lwm2m:x:105321.0Individual Zigbee device representation. Device info, status monitoring, ZCL attribute access, and device management.x-labelZigbee Device105330Walt Technologies0urn:oma:lwm2m:x:105331.0Zigbee group management for collective device control. Group membership, scene management, and ZCL group commands.x-labelZigbee Group105340Walt Technologies0urn:oma:lwm2m:x:105341.0LAN network configuration. DHCP server settings, IP ranges, DNS relay, and client lease management.x-labelLAN Configuration105350Walt Technologies0urn:oma:lwm2m:x:105351.0IP routing table management. Static routes, default gateway, policy-based routing, and route metrics.x-labelRouting Table105360Walt Technologies0urn:oma:lwm2m:x:105361.0VPN tunnel configuration. OpenVPN, WireGuard, IPsec support with connection management and status monitoring.x-labelVPN Configuration105370Walt Technologies0urn:oma:lwm2m:x:105371.0This alarm is raised when acceleration is detected by e.g. an accelerometerx-labelAcceleration Tamper Alarm105380South East Water Corporation0urn:oma:lwm2m:x:105381.0Modem firmware update object.x-labelModem Firmware Update10539https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/10539.xml1South East Water Corporation0urn:oma:lwm2m:x:105391.0This LwM2M Object provides the information to connect to an MQTT Broker i.e. URI, configuration, and keying material.x-labelMQTT Broker18830https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/18830.xml1IoTerop0urn:oma:lwm2m:x:188301.0This LwM2M Object is used to configure data reporting over MQTT.x-labelMQTT Publication18831https://raw.githubusercontent.com/OpenMobileAlliance/lwm2m-registry/prod/18831.xml1IoTerop0urn:oma:lwm2m:x:188311.0