[ https://jira.fiware.org/browse/HELP-8792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Lopez updated HELP-8792: --------------------------------- HD-Chapter: Data 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 was: 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-Enabler: Cosmos > [fiware-stackoverflow] checking command from orion to iot agent in Fiware > ------------------------------------------------------------------------- > > Key: HELP-8792 > URL: https://jira.fiware.org/browse/HELP-8792 > Project: Help-Desk > Issue Type: Monitor > Components: FIWARE-TECH-HELP > Reporter: Backlog Manager > Assignee: Francisco Romero > Labels: fiware, fiware-orion > > 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 -- This message was sent by Atlassian JIRA (v6.4.1#64016)
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy