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

[Fiware-tech-help] iotagent-json [IMPACT Growth]

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Dismissed
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      To whom it may concern,

      We are trying to use the iotagent-json to connect the messages coming from
      our devices to the Context Broker.
      We have created a simple device for testing using curl. The object is:

      curl -X POST -H "Fiware-Service: myHome" -H "Fiware-ServicePath:
      /environment" -H "Content-Type: application/json" -H "Cache-Control:
      no-cache" -d '{
      "devices": [
      {
      "device_id": "zz153",
      "entity_name": "zz153",
      "entity_type": "collar",
      "attributes": [

      { "object_id": "f_activity", "name": "f_activity", "type": "int" }

      ,

      { "object_id": "la", "name": "latitude", "type": "String"}

      ,

      { "object_id": "lo", "name": "longitude", "type": "String"}

      ,
      { "name": "location", "type": "geo:point", "expression":
      "$

      {latitude}

      , $

      {longitude}

      "}
      ]
      }
      ]
      }

      To publish a message we use the following call:
      mosquitto_pub -t /1234/zz153/attrs -m
      '

      {"f_activity":0,"la":"40.4","lo":"-3.4"}

      '

      The problem arises when we get the information from the Context Broker
      where fields are empty.

      {
      "id": "zz153",
      "type": "collar",
      "TimeInstant": {
      "type": "ISO8601",
      "value": " ",
      "metadata": {}
      },
      "f_activity": {
      "type": "int",
      "value": " ",
      "metadata": {}
      },
      "latitude": {
      "type": "String",
      "value": " ",
      "metadata": {}
      },
      "location": {
      "type": "geo:point",
      "value": "0, 0",
      "metadata": {}
      },
      "longitude": {
      "type": "String",
      "value": " ",
      "metadata": {}
      }
      }

      We think the issue is in the type of the attributes because if we follow
      the sample from the tutorial, it works. However, we have tried several
      combinations with no success.

      Thanks

      Un saludo / Best Regards

      Ignacio Gómez Maqueda

      Director Técnico / CTO

      Calle Federico Cantero Villamil 2-B, Desp. 6.

      28935 Móstoles. Madrid
      Tel.: +34 644 35 06 13
      www.digitanimal.com <http://www.digitanimal.com/>

      AVISO LEGAL
      Esta información es privada y confidencial y está dirigida únicamente a su
      destinatario. Si usted no es el destinatario original de este mensaje y por
      este medio pudo acceder a dicha información por favor elimine el mensaje.
      La distribución o copia de este mensaje está estrictamente prohibida. La
      transmisión de e-mails no garantiza que el correo electrónico sea seguro o
      libre de error. Por consiguiente, no manifestamos que esta información sea
      completa o precisa. Toda información está sujeta a alterarse sin previo
      aviso.

      __________________________________________________________________________________________

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

      Fiware-tech-help mailing list
      Fiware-tech-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-tech-help

      [Created via e-mail received from: Ignacio Gomez Maqueda <imaqueda@sensowave.com>]

        Activity

        Hide
        josegato Jose Gato Luis added a comment -

        The issue has been emailed:

        • Time sent: 24/May/18 11:29 AM
        • To: fernando.mendez.external@atos.net
        • with subject: *(HELP-14115) [Fiware-tech-help] iotagent-json [IMPACT Growth] *

        From FIWARE JIRA - Main Help Desk ----

        -------------------------------------------------------------------------------
        Comments:

        ------------------------
        Issue id: HELP-14115
        Description:
        To whom it may concern,

        We are trying to use the iotagent-json to connect the messages coming from
        our devices to the Context Broker.
        We have created a simple device for testing using curl. The object is:

        curl -X POST -H "Fiware-Service: myHome" -H "Fiware-ServicePath:
        /environment" -H "Content-Type: application/json" -H "Cache-Control:
        no-cache" -d '{
        "devices": [
        {
        "device_id": "zz153",
        "entity_name": "zz153",
        "entity_type": "collar",
        "attributes": [

        { "object_id": "f_activity", "name": "f_activity", "type": "int" }

        ,

        { "object_id": "la", "name": "latitude", "type": "String"}

        ,

        { "object_id": "lo", "name": "longitude", "type": "String"}

        ,
        { "name": "location", "type": "geo:point", "expression":
        "$

        {latitude}

        , $

        {longitude}

        "}
        ]
        }
        ]
        }

        To publish a message we use the following call:
        mosquitto_pub -t /1234/zz153/attrs -m
        '

        {"f_activity":0,"la":"40.4","lo":"-3.4"}

        '

        The problem arises when we get the information from the Context Broker
        where fields are empty.

        {
        "id": "zz153",
        "type": "collar",
        "TimeInstant": {
        "type": "ISO8601",
        "value": " ",
        "metadata": {}
        },
        "f_activity": {
        "type": "int",
        "value": " ",
        "metadata": {}
        },
        "latitude": {
        "type": "String",
        "value": " ",
        "metadata": {}
        },
        "location": {
        "type": "geo:point",
        "value": "0, 0",
        "metadata": {}
        },
        "longitude": {
        "type": "String",
        "value": " ",
        "metadata": {}
        }
        }

        We think the issue is in the type of the attributes because if we follow
        the sample from the tutorial, it works. However, we have tried several
        combinations with no success.

        Thanks

        Un saludo / Best Regards

        Ignacio Gómez Maqueda

        Director Técnico / CTO

        Calle Federico Cantero Villamil 2-B, Desp. 6.

        28935 Móstoles. Madrid
        Tel.: +34 644 35 06 13
        www.digitanimal.com <http://www.digitanimal.com/>

        AVISO LEGAL
        Esta información es privada y confidencial y está dirigida únicamente a su
        destinatario. Si usted no es el destinatario original de este mensaje y por
        este medio pudo acceder a dicha información por favor elimine el mensaje.
        La distribución o copia de este mensaje está estrictamente prohibida. La
        transmisión de e-mails no garantiza que el correo electrónico sea seguro o
        libre de error. Por consiguiente, no manifestamos que esta información sea
        completa o precisa. Toda información está sujeta a alterarse sin previo
        aviso.

        __________________________________________________________________________________________

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

        Fiware-tech-help mailing list
        Fiware-tech-help@lists.fiware.org
        https://lists.fiware.org/listinfo/fiware-tech-help

        [Created via e-mail received from: Ignacio Gomez Maqueda <imaqueda@sensowave.com>]

        FIWARE Chapter:
        FIWARE GEri:

        Status: Open

        ---------------------
        This email was generated by FIWARE JIRA following an email received into the Main Help Desk.

        Show
        josegato Jose Gato Luis added a comment - The issue has been emailed: Time sent: 24/May/18 11:29 AM To: fernando.mendez.external@atos.net with subject: *( HELP-14115 ) [Fiware-tech-help] iotagent-json [IMPACT Growth] * From FIWARE JIRA - Main Help Desk ---- ------------------------------------------------------------------------------- Comments: ------------------------ Issue id: HELP-14115 Description: To whom it may concern, We are trying to use the iotagent-json to connect the messages coming from our devices to the Context Broker. We have created a simple device for testing using curl. The object is: curl -X POST -H "Fiware-Service: myHome" -H "Fiware-ServicePath: /environment" -H "Content-Type: application/json" -H "Cache-Control: no-cache" -d '{ "devices": [ { "device_id": "zz153", "entity_name": "zz153", "entity_type": "collar", "attributes": [ { "object_id": "f_activity", "name": "f_activity", "type": "int" } , { "object_id": "la", "name": "latitude", "type": "String"} , { "object_id": "lo", "name": "longitude", "type": "String"} , { "name": "location", "type": "geo:point", "expression": "$ {latitude} , $ {longitude} "} ] } ] } To publish a message we use the following call: mosquitto_pub -t /1234/zz153/attrs -m ' {"f_activity":0,"la":"40.4","lo":"-3.4"} ' The problem arises when we get the information from the Context Broker where fields are empty. { "id": "zz153", "type": "collar", "TimeInstant": { "type": "ISO8601", "value": " ", "metadata": {} }, "f_activity": { "type": "int", "value": " ", "metadata": {} }, "latitude": { "type": "String", "value": " ", "metadata": {} }, "location": { "type": "geo:point", "value": "0, 0", "metadata": {} }, "longitude": { "type": "String", "value": " ", "metadata": {} } } We think the issue is in the type of the attributes because if we follow the sample from the tutorial, it works. However, we have tried several combinations with no success. Thanks Un saludo / Best Regards Ignacio Gómez Maqueda Director Técnico / CTO Calle Federico Cantero Villamil 2-B, Desp. 6. 28935 Móstoles. Madrid Tel.: +34 644 35 06 13 www.digitanimal.com < http://www.digitanimal.com/ > AVISO LEGAL Esta información es privada y confidencial y está dirigida únicamente a su destinatario. Si usted no es el destinatario original de este mensaje y por este medio pudo acceder a dicha información por favor elimine el mensaje. La distribución o copia de este mensaje está estrictamente prohibida. La transmisión de e-mails no garantiza que el correo electrónico sea seguro o libre de error. Por consiguiente, no manifestamos que esta información sea completa o precisa. Toda información está sujeta a alterarse sin previo aviso. __________________________________________________________________________________________ You can get more information about our cookies and privacy policies on the following links: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE Fiware-tech-help mailing list Fiware-tech-help@lists.fiware.org https://lists.fiware.org/listinfo/fiware-tech-help [Created via e-mail received from: Ignacio Gomez Maqueda <imaqueda@sensowave.com>] FIWARE Chapter: FIWARE GEri: Status: Open --------------------- This email was generated by FIWARE JIRA following an email received into the Main Help Desk.
        Hide
        josegato Jose Gato Luis added a comment -

        Please, could you open the issue in the proper github for easy to follow up

        https://github.com/telefonicaid/iotagent-json

        Show
        josegato Jose Gato Luis added a comment - Please, could you open the issue in the proper github for easy to follow up https://github.com/telefonicaid/iotagent-json
        Hide
        josegato Jose Gato Luis added a comment -

        No news responses from the user, so we cannot progress.

        Show
        josegato Jose Gato Luis added a comment - No news responses from the user, so we cannot progress.

          People

          • Assignee:
            josegato Jose Gato Luis
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: