Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Data
-
HD-Enabler:Orion
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": [
],
"reference": "http://52.30.75.227:1026/v1/notifyContext",
"duration": "P1M",
"notifyConditions": [
],
"throttling": "PT5S"
}
EOF
I then received the following server response:
{
"subscribeResponse":
}
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
- relates to
-
HELC-1322 FIWARE.Request.Coach.SOUL-FI.Receiving data from broker
- Closed
Activity
Assignee | Fermín Galán [ fermin ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Summary | [Fiware-soulfi-coaching] Receiving data from broker | FIWARE.Request.Tech.Receiving data from broker |
Sender Email | sholi@humanityonline.org |
HD-Enabler | Orion [ 10875 ] |
HD-Chapter | Data [ 10838 ] |
Summary | FIWARE.Request.Tech.Receiving data from broker | FIWARE.Request.Tech.Data.OrionContextBroker.Receiving data from broker |
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
5d 2h 34m | 1 | Fermín Galán | 22/Mar/16 12:46 PM | |||||
|
1s | 1 | Fermín Galán | 22/Mar/16 12:46 PM | |||||
|
1s | 1 | Fermín Galán | 22/Mar/16 12:46 PM |
The issue has been emailed:
HELP-6159) [Fiware-soulfi-coaching] Receiving data from broker *Hi,
We provide support on Orion Context Broker through StackOverflow http://stackoverflow.com. This way, all the Q&A about the FIWARE platform become available in a public and searchable knowledge base like StackOverflow, which is quite popular among developers.
In that sense, could you ask your question using that platform, please? Use the “fiware-orion” tag (this is important: using this tag in your question is the only way our support staff realizes a new question on Orion has been posted). Any further interaction will be carried out through answers and comments to your question.
In your case, you can "ofuscate" sensible information (such as IPs and subscriptionsID) in the SOF post. (I have the information in the JIRA issue, in the case I need it).
Thanks!
Best regards,
------
Fermín