[HELP-15957] [fiware-stackoverflow] Command sent to ContextBroker doesn't reach IOT Agent - 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/56776930/command-sent-to-contextbroker-doesnt-reach-iot-agent
HD-Enabler:
Orion

Description

Created question in FIWARE Q/A platform on 26-06-2019 at 18:06
Please, ANSWER this question AT https://stackoverflow.com/questions/56776930/command-sent-to-contextbroker-doesnt-reach-iot-agent

Question:
Command sent to ContextBroker doesn't reach IOT Agent

Description:
I've some problems with the commands in the IoTAgent JSON using MQTT. I follow these instructions:

POST ioat-agent:4041/iot/devices
{
"devices": [
{
"device_id": "id_lamp1",
"entity_name": "lamp1",
"entity_type": "lamp",
"attributes": [

{ "object_id": "l", "name": "luminosity", "type": "float" }

],
"commands":[

{ "object_id": "u", "name": "ping", "type": "command" }

],
"protocol": "IoTA-JSON",
"transport": "MQTT"
}
]
}

I try to send a command to the OCB. Something like that:

POST ocb:1026/v2/entities/lamp1/attrs?type=lamp
{
"ping":

{ "type": "command", "value": "Ping Request" }

}

This appears to work fine, because I received in the log:

fiware-iot-agent | time=2019-05-16T09:42:00.436Z | lvl=DEBUG | corr=da768116-77be-11e9-8e17-0242ac140004 | trans=ed164f14-ffd8-404a-8da4-53b901d103b5 | op=IoTAgentNGSI.GenericMiddlewares | srv=myhome | subsrv=/environment | msg=Body:
fiware-iot-agent | {
fiware-iot-agent | "entities": [
fiware-iot-agent |

{ fiware-iot-agent | "type": "lamp", fiware-iot-agent | "isPattern": "false", fiware-iot-agent | "id": "lamp1" fiware-iot-agent | }

fiware-iot-agent | ],
fiware-iot-agent | "attributes": [
fiware-iot-agent | "ping"
fiware-iot-agent | ]
fiware-iot-agent | }
fiware-iot-agent | | comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.457Z | lvl=DEBUG | corr=da768116-77be-11e9-8e17-0242ac140004 | trans=ed164f14-ffd8-404a-8da4-53b901d103b5 | op=IoTAgentNGSI.ContextServer | srv=myhome | subsrv=/environment | msg=Handling query from [iot-agent:4041] | comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.462Z | lvl=DEBUG | corr=da768116-77be-11e9-8e17-0242ac140004 | trans=ed164f14-ffd8-404a-8da4-53b901d103b5 | op=IoTAgentNGSI.MongoDBDeviceRegister | srv=myhome | subsrv=/environment | msg=Looking for device with name [lamp1]. | comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.481Z | lvl=DEBUG | corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | op=IoTAgentNGSI.MongoDBGroupRegister | srv=n/a | subsrv=n/a | msg=Looking for group params ["service","subservice","type"] with queryObj

{"service":"myhome","subservice":"/environment","type":"lamp"}

{"service":"myhome","subservice":"/environment","type":"lamp"}

{"name":"DEVICE_GROUP_NOT_FOUND","message":"Couldn\t find device group","code":404}

| comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.495Z | lvl=DEBUG | corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | op=IoTAgentNGSI.ContextServer | srv=n/a | subsrv=n/a | msg=Handling received set of attributes: ["ping"] | comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.496Z | lvl=DEBUG | corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | op=IoTAgentNGSI.MongoDBDeviceRegister | srv=n/a | subsrv=n/a | msg=Looking for device with name [lamp1]. | comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.506Z | lvl=ERROR | corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | op=IoTAgentNGSI.Alarms | srv=n/a | subsrv=n/a | msg=Releasing [MONGO-ALARM] | comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.509Z | lvl=DEBUG | corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | op=IoTAgentNGSI.ContextServer | srv=n/a | subsrv=n/a | msg=Query from [iot-agent:4041] handled successfully. | comp=IoTAgent
fiware-iot-agent | time=2019-05-16T09:42:00.511Z | lvl=DEBUG | corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b | op=IoTAgentNGSI.ContextServer | srv=n/a | subsrv=n/a | msg=Generated query response: {"contextResponses":[{"contextElement":{"type":"lamp","isPattern":false,"id":"lamp1","attributes":[

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

]},"statusCode":{"code":200,"reasonPhrase":"OK"}}]} | comp=IoTAgent

But I don't receive any message in the topic /1234/id_lamp1/cmd, and I don't see PENDING in the ring_status attribute of the entity of te OCB. Although when I simulate lamp1 device and publish a message in the /1234/id_lamp1/cmdexe the ring_status and ring_info change to OK and 22 respectively.

Activity

Ascending order - Click to sort in descending order

Backlog Manager created issue - 26/Jun/19 6:06 PM

Hide

Permalink

Backlog Manager added a comment - 26/Jun/19 6:06 PM

2019-06-26 18:06|CREATED monitor | # answers= 0, accepted answer= False

Show

Backlog Manager added a comment - 26/Jun/19 6:06 PM 2019-06-26 18:06|CREATED monitor | # answers= 0, accepted answer= False

Backlog Manager made changes - 26/Jun/19 6:06 PM

Field	Original Value	New Value
Component/s		FIWARE-TECH-HELP [ 10278 ]

Backlog Manager made changes - 26/Jun/19 9:06 PM

Status

Open [ 1 ]

In Progress [ 3 ]

Hide

Permalink

Backlog Manager added a comment - 26/Jun/19 9:06 PM

2019-06-26 21:06|UPDATED status: transition Answer| # answers= 1, accepted answer= False

Show

Backlog Manager added a comment - 26/Jun/19 9:06 PM 2019-06-26 21:06|UPDATED status: transition Answer| # answers= 1, accepted answer= False

Backlog Manager made changes - 27/Jun/19 12:06 AM

Status

In Progress [ 3 ]

Answered [ 10104 ]

Hide

Permalink

Backlog Manager added a comment - 27/Jun/19 12:06 AM

2019-06-27 00:06|UPDATED status: transition Answered| # answers= 1, accepted answer= False

Show

Backlog Manager added a comment - 27/Jun/19 12:06 AM 2019-06-27 00:06|UPDATED status: transition Answered| # answers= 1, accepted answer= False

Fernando Lopez made changes - 27/Jun/19 8:54 AM

Assignee

Fermín Galán [ fermin ]

Fernando Lopez made changes - 27/Jun/19 8:54 AM

HD-Enabler		Orion [ 10875 ]
Description	Created question in FIWARE Q/A platform on 26-06-2019 at 18:06 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/56776930/command-sent-to-contextbroker-doesnt-reach-iot-agent +Question:+ Command sent to ContextBroker doesn't reach IOT Agent +Description:+ I've some problems with the commands in the IoTAgent JSON using MQTT. I follow these instructions: POST ioat-agent:4041/iot/devices { "devices": [ { "device_id": "id_lamp1", "entity_name": "lamp1", "entity_type": "lamp", "attributes": [ { "object_id": "l", "name": "luminosity", "type": "float" } ], "commands":[ { "object_id": "u", "name": "ping", "type": "command" } ], "protocol": "IoTA-JSON", "transport": "MQTT" } ] } I try to send a command to the OCB. Something like that: POST ocb:1026/v2/entities/lamp1/attrs?type=lamp { "ping":{ "type": "command", "value": "Ping Request" } } This appears to work fine, because I received in the log: fiware-iot-agent \| time=2019-05-16T09:42:00.436Z \| lvl=DEBUG \| corr=da768116-77be-11e9-8e17-0242ac140004 \| trans=ed164f14-ffd8-404a-8da4-53b901d103b5 \| op=IoTAgentNGSI.GenericMiddlewares \| srv=myhome \| subsrv=/environment \| msg=Body: fiware-iot-agent \| { fiware-iot-agent \| "entities": [ fiware-iot-agent \| { fiware-iot-agent \| "type": "lamp", fiware-iot-agent \| "isPattern": "false", fiware-iot-agent \| "id": "lamp1" fiware-iot-agent \| } fiware-iot-agent \| ], fiware-iot-agent \| "attributes": [ fiware-iot-agent \| "ping" fiware-iot-agent \| ] fiware-iot-agent \| } fiware-iot-agent \| \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.457Z \| lvl=DEBUG \| corr=da768116-77be-11e9-8e17-0242ac140004 \| trans=ed164f14-ffd8-404a-8da4-53b901d103b5 \| op=IoTAgentNGSI.ContextServer \| srv=myhome \| subsrv=/environment \| msg=Handling query from [iot-agent:4041] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.462Z \| lvl=DEBUG \| corr=da768116-77be-11e9-8e17-0242ac140004 \| trans=ed164f14-ffd8-404a-8da4-53b901d103b5 \| op=IoTAgentNGSI.MongoDBDeviceRegister \| srv=myhome \| subsrv=/environment \| msg=Looking for device with name [lamp1]. \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.481Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.MongoDBGroupRegister \| srv=n/a \| subsrv=n/a \| msg=Looking for group params ["service","subservice","type"] with queryObj {"service":"myhome","subservice":"/environment","type":"lamp"} \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.489Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.MongoDBGroupRegister \| srv=n/a \| subsrv=n/a \| msg=Device group for fields [["service","subservice","type"]] not found: [{"service":"myhome","subservice":"/environment","type":"lamp"}] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.491Z \| lvl=ERROR \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.Alarms \| srv=n/a \| subsrv=n/a \| msg=Raising [MONGO-ALARM]: {"name":"DEVICE_GROUP_NOT_FOUND","message":"Couldn\t find device group","code":404} \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.495Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.ContextServer \| srv=n/a \| subsrv=n/a \| msg=Handling received set of attributes: ["ping"] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.496Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.MongoDBDeviceRegister \| srv=n/a \| subsrv=n/a \| msg=Looking for device with name [lamp1]. \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.506Z \| lvl=ERROR \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.Alarms \| srv=n/a \| subsrv=n/a \| msg=Releasing [MONGO-ALARM] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.509Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.ContextServer \| srv=n/a \| subsrv=n/a \| msg=Query from [iot-agent:4041] handled successfully. \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.511Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.ContextServer \| srv=n/a \| subsrv=n/a \| msg=Generated query response: {"contextResponses":[{"contextElement":{"type":"lamp","isPattern":false,"id":"lamp1","attributes":[{"name":"ping","type":"command","value":""}]},"statusCode":{"code":200,"reasonPhrase":"OK"}}]} \| comp=IoTAgent But I don't receive any message in the topic /1234/id_lamp1/cmd, and I don't see PENDING in the ring_status attribute of the entity of te OCB. Although when I simulate lamp1 device and publish a message in the /1234/id_lamp1/cmdexe the ring_status and ring_info change to OK and 22 respectively.	Created question in FIWARE Q/A platform on 26-06-2019 at 18:06 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/56776930/command-sent-to-contextbroker-doesnt-reach-iot-agent +Question:+ Command sent to ContextBroker doesn't reach IOT Agent +Description:+ I've some problems with the commands in the IoTAgent JSON using MQTT. I follow these instructions: POST ioat-agent:4041/iot/devices { "devices": [ { "device_id": "id_lamp1", "entity_name": "lamp1", "entity_type": "lamp", "attributes": [ { "object_id": "l", "name": "luminosity", "type": "float" } ], "commands":[ { "object_id": "u", "name": "ping", "type": "command" } ], "protocol": "IoTA-JSON", "transport": "MQTT" } ] } I try to send a command to the OCB. Something like that: POST ocb:1026/v2/entities/lamp1/attrs?type=lamp { "ping":{ "type": "command", "value": "Ping Request" } } This appears to work fine, because I received in the log: fiware-iot-agent \| time=2019-05-16T09:42:00.436Z \| lvl=DEBUG \| corr=da768116-77be-11e9-8e17-0242ac140004 \| trans=ed164f14-ffd8-404a-8da4-53b901d103b5 \| op=IoTAgentNGSI.GenericMiddlewares \| srv=myhome \| subsrv=/environment \| msg=Body: fiware-iot-agent \| { fiware-iot-agent \| "entities": [ fiware-iot-agent \| { fiware-iot-agent \| "type": "lamp", fiware-iot-agent \| "isPattern": "false", fiware-iot-agent \| "id": "lamp1" fiware-iot-agent \| } fiware-iot-agent \| ], fiware-iot-agent \| "attributes": [ fiware-iot-agent \| "ping" fiware-iot-agent \| ] fiware-iot-agent \| } fiware-iot-agent \| \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.457Z \| lvl=DEBUG \| corr=da768116-77be-11e9-8e17-0242ac140004 \| trans=ed164f14-ffd8-404a-8da4-53b901d103b5 \| op=IoTAgentNGSI.ContextServer \| srv=myhome \| subsrv=/environment \| msg=Handling query from [iot-agent:4041] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.462Z \| lvl=DEBUG \| corr=da768116-77be-11e9-8e17-0242ac140004 \| trans=ed164f14-ffd8-404a-8da4-53b901d103b5 \| op=IoTAgentNGSI.MongoDBDeviceRegister \| srv=myhome \| subsrv=/environment \| msg=Looking for device with name [lamp1]. \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.481Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.MongoDBGroupRegister \| srv=n/a \| subsrv=n/a \| msg=Looking for group params ["service","subservice","type"] with queryObj {"service":"myhome","subservice":"/environment","type":"lamp"} \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.489Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.MongoDBGroupRegister \| srv=n/a \| subsrv=n/a \| msg=Device group for fields [["service","subservice","type"]] not found: [{"service":"myhome","subservice":"/environment","type":"lamp"}] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.491Z \| lvl=ERROR \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.Alarms \| srv=n/a \| subsrv=n/a \| msg=Raising [MONGO-ALARM]: {"name":"DEVICE_GROUP_NOT_FOUND","message":"Couldn\t find device group","code":404} \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.495Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.ContextServer \| srv=n/a \| subsrv=n/a \| msg=Handling received set of attributes: ["ping"] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.496Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.MongoDBDeviceRegister \| srv=n/a \| subsrv=n/a \| msg=Looking for device with name [lamp1]. \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.506Z \| lvl=ERROR \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.Alarms \| srv=n/a \| subsrv=n/a \| msg=Releasing [MONGO-ALARM] \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.509Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.ContextServer \| srv=n/a \| subsrv=n/a \| msg=Query from [iot-agent:4041] handled successfully. \| comp=IoTAgent fiware-iot-agent \| time=2019-05-16T09:42:00.511Z \| lvl=DEBUG \| corr=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| trans=3273f192-1cdc-42dc-80b1-9e0cab5a8a2b \| op=IoTAgentNGSI.ContextServer \| srv=n/a \| subsrv=n/a \| msg=Generated query response: {"contextResponses":[{"contextElement":{"type":"lamp","isPattern":false,"id":"lamp1","attributes":[{"name":"ping","type":"command","value":""}]},"statusCode":{"code":200,"reasonPhrase":"OK"}}]} \| comp=IoTAgent But I don't receive any message in the topic /1234/id_lamp1/cmd, and I don't see PENDING in the ring_status attribute of the entity of te OCB. Although when I simulate lamp1 device and publish a message in the /1234/id_lamp1/cmdexe the ring_status and ring_info change to OK and 22 respectively.

Fernando Lopez made changes - 27/Jun/19 8:54 AM

Resolution		Done [ 10000 ]
Status	Answered [ 10104 ]	Closed [ 6 ]

Fernando Lopez made changes - 27/May/21 10:52 AM

Fix Version/s

2021 [ 12600 ]

Transition

Time In Source Status

Execution Times

Last Executer

Last Execution Date

Open

In Progress

Backlog Manager

26/Jun/19 9:06 PM

In Progress

Answered

Backlog Manager

27/Jun/19 12:06 AM

Answered

Closed

8h 48m

Fernando Lopez

27/Jun/19 8:54 AM

People

Assignee:

Fermín Galán

Reporter:

Backlog Manager

Votes:

0 Vote for this issue

Watchers:

1 Start watching this issue

Dates

Created:

26/Jun/19 6:06 PM

Updated:

27/May/21 10:52 AM

Resolved:

27/Jun/19 8:54 AM

Agile

View on Board