lightweightm2m-iotagent
lightweightm2m-iotagent copied to clipboard
telefonicaid
IoT Agent accepting COAP requests. Designed to be a bridge between the OMA Lightweight M2M protocol and the NGSI interface.
In order to support some devices I need, I've registered a new ObjectID in LWM2M, which is available here: http://technical.openmobilealliance.org/Technical/technical-information/omna/lightweight-m2m-lwm2m-object-registry (urn:oma:lwm2m:x:10242 3-PhasePM) First of all, if I run the downloadOmaRegistry.js...
Current command execution features make the Context Provider calls to command attributes trigger "Execute" calls in the client successfully, but the IoTAgent is not correctly changing the Command status and...
Some decisions were taken concerning OMA Registry mapping that may be subjected to further discussion: - All the attributes are registered as passive. - The resource name in the DDF...
can this prototype of the iot-agent communicates without any problem with the latest version of the iot-discovery? The ContextBroker, in case of correct operation, uses this status statement: .... "statusCode":...
There are currently some differences between both objects, mainly concerning the LWM2M Mappings.
The IoT Agent currently gives support for OMA Registry object types, and the resources defined specifically for those types in their DDFs. For the third party objects, a list of...
Currently, the IoT Agent does not check COAP query parameters have supported characters, and this cause late errors unconnected with the user input. Add an early check in the user...
Metadata
Owner
Metadata
IoT Agent accepting COAP requests. Designed to be a bridge between the OMA Lightweight M2M protocol and the NGSI interface.