Uploaded image for project: 'Help-Coaches-Desk'
  1. Help-Coaches-Desk
  2. HELC-1322

FIWARE.Request.Coach.SOUL-FI.Receiving data from broker

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Component/s: SOUL-FI
    • Labels:
      None

      Description

      Hey

      We've have been trying to get some live data into our broker from this
      datasource (
      https://data.lab.fiware.org/dataset/mobile-sensors/resource/34ca77f3-66b2-417b-8a8e-9c6378a7a57f)
      using the Orion "federation" (subscribeContext / notifyContext, as
      described here:
      http://fiware-orion.readthedocs.org/en/develop/user/federation/index.html).

      So far, our attempts haven't been successful - our broker isn't getting any
      update fromthe orion.lab.fiware.org broker, but there are no error messages
      so I'm at a loss. Here are the key commands I ran:

      1) Generated an Auth token

      bash token_script.sh

      Username: myemail
      Password:

      Token: ume0SjyZ8tMUTi3PKf2SY7T1Ob4d5x

      2) Subscribed to a specific attribute change on a specific entity

      (curl http://orion.lab.fiware.org:1026/v1/subscribeContext -s -S --header
      'Content-Type: application/json' \
      --header 'Accept: application/json' --header "X-Auth-Token:
      ume0SjyZ8tMUTi3PKf2SY7T1Ob4d5x" d @ | python -mjson.tool) <<EOF
      {
      "entities": [

      { "type": "santander:device", "isPattern": "false", "id": "urn:x-iot:smartsantander:u7jcfa:mobile:fa3028" }

      ],
      "reference": "http://52.30.75.227:1026/v1/notifyContext",
      "duration": "P1M",
      "notifyConditions": [

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

      ],
      "throttling": "PT5S"
      }
      EOF

      I then received the following server response:

      {
      "subscribeResponse":

      { "duration": "P1M", "subscriptionId": "56d319e2b2b4e112955efed1", "throttling": "PT5S" }

      }

      So I believe this means my query was correct?

      However, since then, the TimeInstant field has been updated, and our
      Broker hasn't been notified at all (looking at the log). I have also done
      some queries to check that my subscription exists
      (/v1/updateContextSubscriptions, changing the duration) and some other
      queryContext with the same type/id to make sure the attribute
      TimeInstant exists,
      that the selector is correct and that the values are changing.

      Our broker is publicly available (you can check it with
      http://52.30.75.227:1026/v1/contextEntities), so I'm not sure what else I
      can do.

      Thank you for your time.

      Guillaume

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-soulfi-coaching@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-soulfi-coaching mailing list
      Fiware-soulfi-coaching@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-soulfi-coaching
      [Created via e-mail received from: Sholi Loewenthal <sholi@humanityonline.org>]

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open In Progress In Progress
          1d 15h 1 Sergio Garcia Gomez 18/Mar/16 10:40 AM
          In Progress In Progress Answered Answered
          26d 22h 50m 1 Sergio Garcia Gomez 14/Apr/16 10:30 AM
          Answered Answered Closed Closed
          1s 1 Sergio Garcia Gomez 14/Apr/16 10:30 AM

            People

            • Assignee:
              sergg Sergio Garcia Gomez
              Reporter:
              fw.ext.user FW External User
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: