Created question in FIWARE Q/A platform on 06-03-2017 at 20:03
Please, ANSWER this question AT http://stackoverflow.com/questions/42633821/fiware-orion-context-broker-and-iotagentul-command-issue

Question:
Fiware Orion context broker and iotagentUL command issue

Description:
I'm a Fiware user and i deployed an orion context broker GE , cepheus GE and an iotagent-ul instances in different VMs on cloud. I have registered a device in the iot agent specifying a command attribute in the register request and its corresponding entity was created in the context broker on the registration process.
Now when i register a device with its attributes and the command attribute
with its name and type , the device is registered on the iot agent and its entity is also created in the context broker . But the strange thing that happens is that the command attribute is only translated into its special attributes which are the commandName_info and commandName_status but the command attribute itself is not shown among them in the registration
result in the iot agent logs .In addition, when i do an update operation on the command attribute in the Orion context broker , the attribute is not recognized and the update fails as the command attribute is missing in the entitiy itself . And the registration process is as follows:

this is the registration request that i send :

(curl v -H 'content-type: application/json' -H 'fiware-service: ourservicename' -H 'fiware-servicepath: /ourservicpath' -X POST 'http://iotagentULaddress:8080/iot/devices' -d @ ) << EOF

{
"`devices`": [
{
"device_id": "controller12",
"entity_name": "labcontroller12",
"entity_type": "Controller",
"isPattern" :"false",
"protocol": "IoTA-UL",
"timezone": "Egypt/Cairo",
"endpoint": "http://iotagentULaddress:8080",
"attributes": [

],
"commands": [

]
}]
}
EOF

And this is the registration result in the iot agent's logs showing the registered entity and how it is created in the context broker:

time=2017-03-06T18:10:56.335Z | lvl=DEBUG | corr=dee16709-4b99-4336-b23a-722878a8b628 | trans=dee16709-4b99-4336-b23a-722878a8b628 | op=IoTAgentNGSI.ContextServer | srv=n/a | subsrv=n/a | msg=Successfully subscribed to the following topics:
["/+/+/attrs/+","/+/+/attrs","/+/+/cmdexe"]

{
"devices": [
{
"device_id": "controller12",
"entity_name": "labcontroller12",
"entity_type": "Controller",
"isPattern": "false",
"protocol": "IoTA-UL",
"timezone": "Egypt/Cairo",
"endpoint": "http://217.172.12.190:8080",
"attributes": [

],
"commands": [

]
}
]
}

{
"url": "http://147.27.60.58:1026/NGSI9/registerContext",
"method": "POST",
"json": {
"contextRegistrations": [
{
"entities": [

],
"attributes": [

],
"providingApplication": "http://localhost:4061"
}
],
"duration": "P1Y"
},
"headers":

}

It's now clear that the command attribute is not created but only its special attributes that describe the command state itself but there's no command to be updated .
So , Is my registration request composed correctly to suit the iotagen-ul instance especially for its interpretation for the command ? and how could i verify the registration correctness ? and i just want to know where the problem could lie exactly . and thanks so much.