iotcreators.com web
    • Login
    • Search
    • forum.iotcreators.com
    • docs.iotcreators.com
    • Tags
    • Popular
    • Recent
    • Register

    NB-IOT gps Postman issue

    Archive
    2
    3
    1440
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tonibco last edited by

      Hi all.
      I don’t manage to see gps data within Postman interface by the ‘nbIOT_gps’ sample. Is it about the format code?
      However, I am able to see it into my serial console.
      That’s what I got on my Postman interface.0_1507012203717_Gps.jpg

      1 Reply Last reply Reply Quote 0
      • T
        Tonibco last edited by Tonibco

        Now, using the Sodaq_Nb-iot_All_sensor sketch from Sodaq library, I got the following data into the Postman interface ( serial console got proper upcoming data).

        0_1507036598332_all_sensors_data.jpg

        If I decode that data from Base64, the result doesn’t make any sense.

        Thank you

        ericbarten 1 Reply Last reply Reply Quote 0
        • ericbarten
          ericbarten iotcreators.com team @Tonibco last edited by

          Hi @tonibco in the sketch you mentioned you can find the definition of HEX bytes that you have sent. These HEX values corespond to the base64 decoded HEX values.

          • device decoding:

          “sense”: [
          {
          “asset”: “my_temperature”,
          “value”: {
          “byte”: 0,
          “bytelength”: 2,
          “type”: “integer”,
          “calculation”: “val / 100”
          }

          So the first HEX number is the temperature * 100

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post