[HELP-9085] [fiware-stackoverflow] Fiware IotAgent: can't send command to a device - JIRA

Details

Type: Monitor
Status: Closed
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: 2021
Component/s: FIWARE-TECH-HELP
Labels:
- fiware
- fiware-orion

Source URL:
https://stackoverflow.com/questions/34004222/fiware-iotagent-cant-send-command-to-a-device
HD-Enabler:
IDAS

Description

Created question in FIWARE Q/A platform on 30-11-2015 at 18:11
Please, ANSWER this question AT https://stackoverflow.com/questions/34004222/fiware-iotagent-cant-send-command-to-a-device

Question:
Fiware IotAgent: can't send command to a device

Description:
I approvisionned my device like this in the IoT agent:

curl -X POST http://192.168.1.110:80/iot/devices \
-i \
-H "Content-Type: application/json" \
-H "Fiware-Service: egmsmartcity" \
-H "Fiware-ServicePath: /egmsmartcitypath" \
-d ' { "devices": [ { "device_id": "test",
"entity_name": "sensors:test",
"entity_type": "sensors",
"protocol": "PDI-IoTA-MQTT-UltraLight",
"timezone": "Europe/Paris",
"endpoint": "notUsed",
"commands": [

{ "name": "ping", "type": "command", "value": ""}

] } ] }'

It is successufl registered in the context Broker:

GET on: http://192.168.1.77:1026/v1/contextEntities/sensors:test

with headers:

Accept: application/json
Fiware-Service: egmsmartcity
Fiware-ServicePath: /egmsmartcitypath

I got the following response:

{
contextElement: {
type: "sensors"
isPattern: "false"
id: "sensors:test"
attributes: [1]
0: {
name: "TimeInstant"
type: "ISO8601"
value: "2015-11-30T16:53:45.556269Z"
}-
-
}-
statusCode: {
code: "200"
reasonPhrase: "OK"
}-
}

and then when I try to update the command like this:

curl -X POST http://192.168.1.77:1026/v1/updateContext \
-i \
-H "Content-Type: application/json" \
-H "Fiware-Service: egmsmartcity" \
-H "Fiware-ServicePath: /egmsmartcitypath" \
-d ' {"updateAction":"UPDATE","contextElements":[{"id":"sensors:test","type":"sensors","isPattern":"false","attributes":[

{"name":"ping","type":"command","value":"22" }

]} ]}'

I got this response:

HTTP/1.1 200 OK
Content-Length: 157
Content-Type: application/xml
Date: Mon, 30 Nov 2015 17:05:11 GMT

<updateContextResponse>
<errorCode>
<code>404</code>
<reasonPhrase>No context element found</reasonPhrase>
</errorCode>
</updateContextResponse>

why is it returning "No context element found" ? What have I missed ?
Thanks in advance for your help!

[Updates]
I tried a simple get on "/iot/devices"
Here is the log in the Iot Agent lg file:

In case the operation was successuful, from localhost

HTTP Version: 1.1
Resource requested: /iot/devices
Resource delivered: /iot/devices
Query string
Content length: 0
Headers: Fiware-ServicePath: /egmsmartcitypath
Fiware-Service: egmsmartcity
User-Agent: curl/7.29.0
Host: localhost
Content-Type: application/json
Accept: /

{ service: "egmsmartcity", service_path: "/egmsmartcitypath" }

{ service: "egmsmartcity", service_path: "/egmsmartcitypath" }

limit=20 offset=0 options=-2147483648
time=2015-12-02T10:41:41,517.546CET | lvl=DEBUG | comp=iota:IoTAgent-MQTT-UL20 | op=find | file=[140373934458624:collection.cc:718] | msg=before getConnection
time=2015-12-02T10:41:41,517.553CET | lvl=DEBUG | comp=iota:IoTAgent-MQTT-UL20 | op=find | file=[140373934458624:collection.cc:723] | msg=before query
time=2015-12-02T10:41:41,517.737CET | lvl=DEBUG | comp=iota:IoTAgent-MQTT-UL20 | op=create_response | file=[140373934458624:admin_service.cc:1309] | msg=create_response: 200 { "count": 2,"devices": [

{ "device_id" : "sensorTmp" }

,

{ "device_id" : "test" }

]}
time=2015-12-02T10:41:41,517.766CET | lvl= INFO | comp=iota:IoTAgent-MQTT-UL20 | op=devices | file=[140373934458624:admin_service.cc:718] | msg=iota::AdminService::devices method:GET trace_message:/iot-754c76a3-b95a-4aac-976a-08ab37119c05-34 code: 200 response:{ "count": 2,"devices": [

{ "device_id" : "sensorTmp" }

,

{ "device_id" : "test" }

]}
time=2015-12-02T10:41:41,517.902CET | lvl=DEBUG | comp=iota:IoTAgent-MQTT-UL20 | op=finish | file=[140373934458624:rest_handle.cc:567] | msg=finish connection 2

In case the operation was not successuful, from Rest client

HTTP Version: 1.1
Resource requested: /iot/devices/
Resource delivered: /iot/devices/
Query string
Content length: 0
Headers: Fiware-ServicePath: /egmsmartcitypath
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.86 Safari/537.36
Fiware-Service: egmsmartcity
Connection: keep-alive
Host: 192.168.1.110
Accept-Language: fr-FR,fr;q=0.8,en-US;q=0.6,en;q=0.4
Accept-Encoding: gzip, deflate, sdch
Accept: /
Content-Type: application/json

Seems like the iot agent finish the opration before teminating the request handling

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Backlog Manager added a comment - 22/May/17 3:16 PM

2017-05-22 15:17|CREATED monitor | # answers= 1, accepted answer= True

Show

Backlog Manager added a comment - 22/May/17 3:16 PM 2017-05-22 15:17|CREATED monitor | # answers= 1, accepted answer= True

Hide

Permalink

Backlog Manager added a comment - 22/May/17 6:10 PM

2017-05-22 18:11|UPDATED status: transition Answer| # answers= 1, accepted answer= True

Show

Backlog Manager added a comment - 22/May/17 6:10 PM 2017-05-22 18:11|UPDATED status: transition Answer| # answers= 1, accepted answer= True

Hide

Permalink

Backlog Manager added a comment - 22/May/17 9:10 PM

2017-05-22 21:12|UPDATED status: transition Finish| # answers= 1, accepted answer= True

Show

Backlog Manager added a comment - 22/May/17 9:10 PM 2017-05-22 21:12|UPDATED status: transition Finish| # answers= 1, accepted answer= True

[fiware-stackoverflow] Fiware IotAgent: can't send command to a device

Details

Description

Activity

People

Dates

Agile