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

[fiware-stackoverflow] Orion JSON Bad Request

    Details

      Description

      Created question in FIWARE Q/A platform on 11-01-2016 at 21:01
      Please, ANSWER this question AT https://stackoverflow.com/questions/34730683/orion-json-bad-request

      Question:
      Orion JSON Bad Request

      Description:
      I'm currently trying to subscribe Orion and Cosmos. All data sent to Orion is being updated without any issue. But, when posting to http://xxx.xxx.xx.xx:1026/v1/subscribeContext I'm getting the following error:

      {
      "subscribeError": {
      "errorCode":

      { "code": "400", "reasonPhrase": "Bad Request", "details": "JSON Parse Error" }

      }
      }

      This is the json string I'm sending:

      {
      "entities": [

      { "type": "Location", "isPattern": "false", "id": "Device-1" }

      ],
      "reference": "http://52.31.144.170:5050/notify",
      "duration": "PT10S",
      "notifyConditions": [

      { "type": "ONCHANGE", "condValues": [ "position" ] }

      ],
      "attributes": [
      "position"
      ]
      }

      The entity updating OK in Orion is:

      {
      "type": "Location",
      "isPattern": "false",
      "id": "Device-1",
      "attributes": [
      {
      "name": "position",
      "type": "coords",
      "value": "24,21",
      "metadatas": [

      { "name": "location", "type": "string", "value": "WGS84" }

      ]
      },

      { "name": "id", "type": "device", "value": "1" }

      ]
      }

      I've tried with many different examples from readthedocs, and other responses in StackOverflow unsuccessfully.

      Which is the correct format? Should I call /subscribeContext before or after updating Orion with /contextEntities?

      Orion Context Broker version is 0.26.1.

      Thank you in advance.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 15:09|CREATED monitor | # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 15:09|CREATED monitor | # answers= 1, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 18:07|UPDATED status: transition Answer| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 18:07|UPDATED status: transition Answer| # answers= 1, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2017-05-22 21:07|UPDATED status: transition Answered| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2017-05-22 21:07|UPDATED status: transition Answered| # answers= 1, accepted answer= False

          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: