This Case addresses the condition in which the IOT Device is already registered to an IOT broker (an Orion one), and thus the IOT Device data for its configuration can obtained by us from the IOT Orion Broker in almost automatic manner.
Please remind that this case supposes that the IOT Device has been already registered on an IOT Broker, i.e. the “orionFinland” ContextBroker as https://ngsi.fvh.fi or the “Antwerp” ContextBroker as http://ext-api-gw-p.antwerpen.be/imec/smartzone/v1 or the "Antwerp2" ContextBroker as https://ext-api-gw-p.antwerpen.be/digipolis/aovmma/v1/entities. The IOT Orion Broker can connect JSON, MQTT, Lightweight M2M, LoraWAN, OPC, SigFOX, etc. see FiWare https://www.fiware.org/ Snap4City is compatible with all the above protocols via IOT Orion Broker and via IOT Applications as well many others see table of protocols https://www.snap4city.org/drupal/node/65
- Click on left main menu “IOT Directory and Devices” --> “IOT Device”
- Since the IOT Device is not yet present on the Platform, you can add it by clicking the Button “New Device”
3) Once clicked the New Device Button a pop up appear as in the following figure in whcih several details are requested and can be filled if necessary. Not all of them may be necessary but are presented to you to verify. They are: IOT Broker, Info, Position and Values. let us now to proceed in order.
Tab “IoT Broker”
-
ContextBroker: you can select the “orionFinland” ContextBroker as https://ngsi.fvh.fi or the "Antwerp" ContextBroker as http://ext-api-gw-p.antwerpen.be/imec/smartzone/v1 or the "Antwerp2" ContextBroker as https://ext-api-gw-p.antwerpen.be/digipolis/aovmma/v1/entities (please note that the name reported for the IOT Brokers are the conventional names assigned by Snap4City as their NickNames). Depending on your selection, the followign data are automatically filled out:
-
Kind: it can be a sensor or an actuator (usually, it is a sensor)
-
Protocol: it depends on the configuration of the device (usually it is nsgi)
-
Format: it depends on the configuration of the device (it usually json)
-
For example, for the Helsinki Orion Broker:
Tab “Info”
- name: specify the name of the device (which should be exactly the one specified in the IoT Broker) and click the “check” button (all the other fields are disabled). The system will retrieve the device information and also the information related with the sensors/actuators directly from the IoT Broker (IOT Orion Broker) to fill them into the current form. At this point you can complete the missing information and conclude the insertion of the device.
For example, for a "AirQualityObserved" device named “373773207E330108”:
Position and values tabs
These forms will be populate automatically accordling the information retrieved from the IoT Broker
- When all the information has been inserted, it’s needed to press the Button “Confirm” to terminate the registration of the device
- Then, after about 10 minutes, the IOT Device and corresponding data will be accessible, and you will find them into the list of your data in the Data Inspector view, for Dashboards, etc., go in the Data Inspector to search your data by GPS location, name, nature as you like.
To check if the device has been correctly added to the Platform, it’s possible to search the device by its name.
-
To check if the sensor’s values has been correctly configured on the Platform, the user has to press, from the left main menu, the button called “Data Inspector”
-
Here the user needs to insert in the search box the name of the device. The list of the sensor’s values related to the registered device has to appear in the filtered list (the refresh of this list is scheduled every 10 minutes, so in case the device does not appear immediately, wait a maximum interval of time of 10 minutes.)
