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

[fiware-stackoverflow] IoT Agent for a JSON - Sensor sends measures already in NGSI

        Details

          Description

          Created question in FIWARE Q/A platform on 17-10-2019 at 10:10
          Please, ANSWER this question AT https://stackoverflow.com/questions/58427850/iot-agent-for-a-json-sensor-sends-measures-already-in-ngsi

          Question:
          IoT Agent for a JSON - Sensor sends measures already in NGSI

          Description:
          We have a FIWARE based architecture that uses the IoT Agent for a JSON based protocol.

          We have a sensor that sends measures, whose format is already NGSI.

          I thought the behavior of the agent was to recognize the NGSI format and manipulate the data so that the final result is correct.

          Instead, the current result is that the value on Orion becomes the full NGSI.

          e.g.

          Attribute on Orion Entity:

          "altitude": {
          "type": "number",
          "value": "12",
          "metadata": {
          "TimeInstant":

          { "type": "ISO8601", "value": "2019-10-16T09:01:40.460Z" }

          }
          }

          Send:

          {
          "altitude":

          { "value": "22" }

          }

          Result:

          "altitude": {
          "type": "number",
          "value":

          { "value": "22" }

          ,
          "metadata": {
          "TimeInstant":

          { "type": "ISO8601", "value": "2019-10-16T09:08:50.307Z" }

          }
          }

          Is it correct ?

            Activity

            Descending order - Click to sort in ascending order
            Transition Time In Source Status Execution Times Last Executer Last Execution Date
            Open Open In Progress In Progress
            		88d 9h 59m 1 Backlog Manager 13/Jan/20 9:06 PM
            In Progress In Progress Answered Answered
            		2h 59m 1 Backlog Manager 14/Jan/20 12:06 AM
            Answered Answered Closed Closed
            		37d 18h 1 Backlog Manager 20/Feb/20 6:06 PM
            fla Fernando Lopez made changes -
            Fix Version/s 2021 [ 12600 ]
            Hide
            Permalink
            backlogmanager Backlog Manager added a comment -

            2020-02-20 18:06|UPDATED status: transition Finish| # answers= 1, accepted answer= True

            Show
            backlogmanager Backlog Manager added a comment - 2020-02-20 18:06|UPDATED status: transition Finish| # answers= 1, accepted answer= True
            backlogmanager Backlog Manager made changes -
            Resolution Done [ 10000 ]
            Status Answered [ 10104 ] Closed [ 6 ]
            Hide
            Permalink
            backlogmanager Backlog Manager added a comment -

            2020-01-14 00:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False

            Show
            backlogmanager Backlog Manager added a comment - 2020-01-14 00:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False
            backlogmanager Backlog Manager made changes -
            Status In Progress [ 3 ] Answered [ 10104 ]
            Hide
            Permalink
            backlogmanager Backlog Manager added a comment -

            2020-01-13 21:06|UPDATED status: transition Answer| # answers= 1, accepted answer= False

            Show
            backlogmanager Backlog Manager added a comment - 2020-01-13 21:06|UPDATED status: transition Answer| # answers= 1, accepted answer= False
            backlogmanager Backlog Manager made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            fla Fernando Lopez made changes -
            HD-Enabler IDAS [ 10884 ]
            Description
            Created question in FIWARE Q/A platform on 17-10-2019 at 10:10
            {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/58427850/iot-agent-for-a-json-sensor-sends-measures-already-in-ngsi


            +Question:+
            IoT Agent for a JSON - Sensor sends measures already in NGSI

            +Description:+
            We have a FIWARE based architecture that uses the IoT Agent for a JSON based protocol.

            We have a sensor that sends measures, whose format is already NGSI.

            I thought the behavior of the agent was to recognize the NGSI format and manipulate the data so that the final result is correct.

            Instead, the current result is that the value on Orion becomes the full NGSI.

            e.g.

            Attribute on Orion Entity:

            "altitude": {
                "type": "number",
                "value": "12",
                "metadata": {
                    "TimeInstant": {
                        "type": "ISO8601",
                        "value": "2019-10-16T09:01:40.460Z"
                    }
                }
            }


            Send:

            {
                "altitude": {
                    "value": "22"
                  }
              }


            Result:

              "altitude": {
                    "type": "number",
                    "value": {
                        "value": "22"
                    },
                    "metadata": {
                        "TimeInstant": {
                            "type": "ISO8601",
                            "value": "2019-10-16T09:08:50.307Z"
                        }
                    }
                }


            Is it correct ?
            		 Created question in FIWARE Q/A platform on 17-10-2019 at 10:10
            {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/58427850/iot-agent-for-a-json-sensor-sends-measures-already-in-ngsi


            +Question:+
            IoT Agent for a JSON - Sensor sends measures already in NGSI

            +Description:+
            We have a FIWARE based architecture that uses the IoT Agent for a JSON based protocol.

            We have a sensor that sends measures, whose format is already NGSI.

            I thought the behavior of the agent was to recognize the NGSI format and manipulate the data so that the final result is correct.

            Instead, the current result is that the value on Orion becomes the full NGSI.

            e.g.

            Attribute on Orion Entity:

            "altitude": {
                "type": "number",
                "value": "12",
                "metadata": {
                    "TimeInstant": {
                        "type": "ISO8601",
                        "value": "2019-10-16T09:01:40.460Z"
                    }
                }
            }


            Send:

            {
                "altitude": {
                    "value": "22"
                  }
              }


            Result:

              "altitude": {
                    "type": "number",
                    "value": {
                        "value": "22"
                    },
                    "metadata": {
                        "TimeInstant": {
                            "type": "ISO8601",
                            "value": "2019-10-16T09:08:50.307Z"
                        }
                    }
                }


            Is it correct ?
            Assignee Fermín Galán [ fermin ]
            backlogmanager Backlog Manager made changes -
            Field Original Value New Value
            Component/s FIWARE-TECH-HELP [ 10278 ]
            Hide
            Permalink
            backlogmanager Backlog Manager added a comment -

            2019-10-17 12:06|CREATED monitor | # answers= 0, accepted answer= False

            Show
            backlogmanager Backlog Manager added a comment - 2019-10-17 12:06|CREATED monitor | # answers= 0, accepted answer= False
            backlogmanager Backlog Manager created issue -

              People

              • Assignee:
                fermin Fermín Galán
                Reporter:
                backlogmanager Backlog Manager
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: