Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8258

[fiware-stackoverflow] checking command from orion to iot agent in Fiware

    Details

      Description

      Created question in FIWARE Q/A platform on 11-02-2017 at 23:02
      Please, ANSWER this question AT http://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 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).
      Now when i update the command attribute of the device entity in the 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.

      -and 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 .

      -in case i have no physical device could i consider the iot agent's address an endpoint to check whether any update on the command attribute in the context broker will be forwarded to that endpoint ( iotagent in this case) .

      Thanks

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open In Progress In Progress
          29d 14h 58m 1 Miguel Carrillo 13/Mar/17 3:03 PM
          In Progress In Progress Answered Answered
          1s 1 Miguel Carrillo 13/Mar/17 3:03 PM
          Answered Answered Closed Closed
          1s 1 Miguel Carrillo 13/Mar/17 3:03 PM

            People

            • Assignee:
              mcp Miguel Carrillo
              Reporter:
              backlogmanager Backlog Manager
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: