Change device - IoTAgentUL

The IoTAs (and the IoTA library in general) expose the northern provisioning interface for device creation. The basic idea is that you expose the device in IoTA (directly or through IoTA Manager), the entity is automatically created in the Context Broker. This nohr initialization interface allows fetching, deleting, and updating too.

Speaking of which, the southern interface of IoTAs is only for taking action and executing commands from devices. That way, if a new attribute comes into play and you provide values ​​for that new attribute via IoTA, the new attribute won't be added to the Context Broker; just that information will be deleted.

To receive new attribute data, you will first need to use the aforementioned IoTA init interface, specifically the update device operation , to provide such a new attribute; which will automatically add a new attribute to the entity at the context broker level. Here, the values ​​of the new attribute sent to the IoTA will be updated in the Context Broker.

Such an update request looks like this:

PUT http://iota_host:iota_port/iot/devices/<dev_id>?protocol=<protocol_type>
Fiware-Service: <service>
Fiware-ServicePath: <subservice>

{
   "entity_type": <entity_type>,
   "attributes": [ <new_active_attrs_if_any> ],
   "lazy": [ <new_lazy_attrs_if_any> ],
   "commands": [ <new_commands_if_any> ],
   "statis_attributes": [ <new_static_attrs_if_any> ]
}

      

        
        
        
      

    

Unfortunately, pre-existing attributes cannot be removed yet.