Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Enabler:IDAS
Description
To Whom It May Concern,
I have a question about the implementation of a Context Provider in my Fiware service. In particular, I wanted to know how to create a graphic interface through the context provider. For example, is possible create a custom context provider with different data than those included in your examples (https://fiware-tutorials.readthedocs.io/en/latest/iot-agent/index.html)?
My aim is to have a webservice interface that is able to show in real time the data collected from an IoT network.
Thanking you in advance...
Yours faithfully,
Giovanni
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Giovanni.VAGLICA@ec.europa.eu]
The graphical interface provided in the FIWARE tutorials has only been created to provide dummy data into a series of tutorial exercises.
It is used to show how to connect an series of devices using UltraLight over HTTP or MQTT - it is not really designed to be extended or to be
used to display data from a real device - though you could extending that way if you wish.
To connect a series of real devices to the context broker you will need to use an IoT Agent - IoT Agents exist for a series of common protocols
and the one you need to pick will be dependent on the array of device you have - for example a rain-gauge may be very constrained in power
And may be transmitting using LoRaWAN whereas a camera could have a constant power source and may even do image processing on the
Edge.
The full list of available IoT Agents can be found on the FIWARE website: https://www.fiware.org/developers/catalogue/ - you can also
Create your own (based on the Nodejs library) if you are using another protocol.
Having got the data into the context broker, there are several ways you could display the data graphically.
You could use WireCloud or Knowage to create a graphical interface and potentially control your device via button widgets and so-on - more details can be found in the academy courses:
https://edu.fiware.org/course/search.php?search=Wirecloud
https://edu.fiware.org/course/search.php?search=Knowage
To display a graph of historical results you have a choice between Quantum Leap and STH-Comet - Quantum Leap plays nicely with time-based database
And third-party graphical tools like Grafana.
Alternatively you could control the devices by sending NSGI calls programmatically - this is described in the Tutorials, and the code is available within the Tutorials repos
Accessing Context Data
Effectively you would then be modifying the code of the tutorial to do as you require, but it would be a lot of work.
Unless I really needed the extra flexibility, if I were creating a smart application monitoring tool/controller, I wouldn’t be writing it from scratch using nodejs though,
I would definitely look to see if Knowage or Wirecloud offer the functionality you need first before attempting to write my own stuff - there really is no
Need to re-invent the wheel here when the Visualization Generic Enablers already exist for that purpose.