Details
-
Type:
Monitor
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:Data
-
HD-Enabler:Cosmos
Description
Created question in FIWARE Q/A platform on 11-02-2017 at 23:02
Please, ANSWER this question AT https://stackoverflow.com/questions/42182084/checking-command-from-orion-to-iot-agent-in-fiware
Question:
checking command from orion to iot agent in Fiware
Description:
I've used the FIWARE Orion Context Broker and IoTAgent-UL in my project. I've registered a virual device by sending a Json message carrying the device attributes, the command attributes, device endpoint address and the used protocol (UL2.0).
If I update the command attribute of the device entity in Orion Context Broker, how can i check that the command is sent to the IoTAgent successfully before it is forwarded to the device virtual device itself?
Moreover, can I make the IP address of a Raspberrypi the endpoint itself and assign a port to a device connected to the Raspberrypi? And how could this be done?
Finally, in case I have no physical device could I consider the IoTAgent's address an endpoint to check whether any update on the command attribute in the context broker will be forwarded to that endpoint?
Thanks
Activity
| Field | Original Value | New Value |
|---|---|---|
| Component/s | FIWARE-TECH-HELP [ 10278 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
2017-05-22 18:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False
| Status | In Progress [ 3 ] | Answered [ 10104 ] |
2017-05-22 21:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False
| Assignee | Francisco Romero [ frb ] |
| HD-Enabler | Cosmos [ 10872 ] | |
| Description |
Created question in FIWARE Q/A platform on 11-02-2017 at 23:02 {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/42182084/checking-command-from-orion-to-iot-agent-in-fiware +Question:+ checking command from orion to iot agent in Fiware +Description:+ I've used the FIWARE Orion Context Broker and IoTAgent-UL in my project. I've registered a virual device by sending a Json message carrying the device attributes, the command attributes, device endpoint address and the used protocol (UL2.0). If I update the command attribute of the device entity in Orion Context Broker, how can i check that the command is sent to the IoTAgent successfully before it is forwarded to the device virtual device itself? Moreover, can I make the IP address of a Raspberrypi the endpoint itself and assign a port to a device connected to the Raspberrypi? And how could this be done? Finally, in case I have no physical device could I consider the IoTAgent's address an endpoint to check whether any update on the command attribute in the context broker will be forwarded to that endpoint? Thanks |
Created question in FIWARE Q/A platform on 11-02-2017 at 23:02
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/42182084/checking-command-from-orion-to-iot-agent-in-fiware +Question:+ checking command from orion to iot agent in Fiware +Description:+ I've used the FIWARE Orion Context Broker and IoTAgent-UL in my project. I've registered a virual device by sending a Json message carrying the device attributes, the command attributes, device endpoint address and the used protocol (UL2.0). If I update the command attribute of the device entity in Orion Context Broker, how can i check that the command is sent to the IoTAgent successfully before it is forwarded to the device virtual device itself? Moreover, can I make the IP address of a Raspberrypi the endpoint itself and assign a port to a device connected to the Raspberrypi? And how could this be done? Finally, in case I have no physical device could I consider the IoTAgent's address an endpoint to check whether any update on the command attribute in the context broker will be forwarded to that endpoint? Thanks |
| HD-Chapter | Data [ 10838 ] |
| Resolution | Done [ 10000 ] | |
| Status | Answered [ 10104 ] | Closed [ 6 ] |
| Fix Version/s | 2021 [ 12600 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
2h 58m | 1 | Backlog Manager | 22/May/17 6:04 PM | |||||
|
2h 59m | 1 | Backlog Manager | 22/May/17 9:04 PM | |||||
|
5d 22h 42m | 1 | Fernando Lopez | 28/May/17 7:46 PM |
2017-05-22 15:07|CREATED monitor | # answers= 1, accepted answer= False