[Backlogmanager] [FIWARE-JIRA] (HELP-16239) [fiware-stackoverflow] IoT Agent for a JSON - Sensor sends measures already in NGSI

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Thu Oct 17 12:28:00 CEST 2019


     [ https://jira.fiware.org/browse/HELP-16239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez reassigned HELP-16239:
-------------------------------------

       Assignee: Fermín Galán
    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 ?


  was:

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 ?


     HD-Enabler: IDAS

> [fiware-stackoverflow] IoT Agent for a JSON - Sensor sends measures already in NGSI
> -----------------------------------------------------------------------------------
>
>                 Key: HELP-16239
>                 URL: https://jira.fiware.org/browse/HELP-16239
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Fermín Galán
>              Labels: fiware, iot, json
>
> 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 ?



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)


More information about the Backlogmanager mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy