-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full documentation of this API #13
Comments
Can we share which documentation references (links) have you been using so far, please? |
So, as far as I understand, your goal is to build a system that acts as an IOT Agent. In that case, I'd recommend you to use the IOTA Lib. Note that library implements the IOTA-CB interface (northbound) so you will get "for free" all that stuf about registrations and There is a document on How to build and IOTA using the library in the library repository itself and probably more tutorials and documentation about it (not sure... I'm CCing @jason-fox in the case he knows more references on this). |
A simple custom IoT Agent with working commands is described in this tutorial: https://github.com/FIWARE/tutorials.Custom-IoT-Agent/tree/master There is an up-and-coming webinar on customizing IoT Agents scheduled for the beginning of March 2021: https://www.fiware.org/community/fiware-webinars/ |
Thanks for this hints. |
For NGSI-v2 you will use the The IoT Agent is then listening on For NGSI-LD using Orion-LD an actuation example using registration is described here: https://github.com/FIWARE/tutorials.LD-Subscriptions-Registrations/tree/master#forwarded-update The final definition of NGSI-LD actuations within the ETSI specification is still being discussed. |
I still need further help. Here is my simple example:
For regsitering a context-provider/iot-agent I used this:
The resulting document within the
Know I query for this entity |
Which CB version are you using? How are you starting it (i.e. |
I'm using the docker image |
Could you upgrade to Once you do that, please repeat your test and provide the trace associated to the |
The log entry for the forwarded POST is:
This response is from the IoT Agent (based on Node-Red). In the log you can see that the response ist from another url (//op/query). Do you have any explanation where this additional slash comes from? There isn't any in the registration document. I also tried (with success) a |
Workaround: So I think the context-broker isn't able to query a context-provider on it's root url. You have to add a path. |
The URL used by Orion to forward requests are:
Is this different from what you have observed in your tests? |
As you can see in the example above I POSTed a registration with the root url (http://iot-agent:8080) for my iot agent. The agent is listening on http://iot-agent:1880/op/query and http://iot-agent:1880/op/query for POST request. I tested this. |
What about if you use (Just to fully consider all the possible cases of a potential bug in the CB) |
Same result with or without trailing slash: response is 404 (Cannot POST //op/query) |
I have created an issue in Orion Context Broker repository with the specific issue: telefonicaid/fiware-orion#3768 Apart from that, anything else pending? Or can this issue (#13) be closed? |
Please extend the documentation https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json#/Registrations/Create%20Registration to show all possible property payload. |
That swagger document is out of my scope, but maybe @jason-fox could move this to the people in charge of that document. |
Our goal is to build up a context driven IoT platform for energy management.
For this I'm trying to understand the NGSIv2 API for a couple of days now. But this is very difficult. Every example I can find (including the step by step guide) lacks some important points.
The main problem (for now) is that I have to register serveral devices, which are able to execute
commands
. Until now I haven't found any description/example how to do this.What I've understand so far is:
context-provider
iot-agents
(transform data from/tocontext-broker
and device)iot-agents
have to provide the REST endpoints/v2/op/update
and/v2/op/query
/v2/registration
endpoint of thecontext-broker
to self register... and there isn't any description of the registration payload. I don't know how to notify the
context-broker
about: "Hey CB. I'm device...
. I'm able to execute these commands: ...."Can you please update your documentation/examples.
The text was updated successfully, but these errors were encountered: