1. Home
  2. TC2.7 - IOT protocol Telemetry

TC2.7 - IOT protocol Telemetry

Test Case Title

TC2.7 - IOT protocol Telemetry

Goal
  • The Telemetry protocol is based on the fact that any changes in the IOT Device are communicated to the IOT Broker

Prerequisites

Using a PC or Mobile with a web browser. You need a Snap4City account. Sensors and actuators for reading

The following functionalities are available only for a specific Snap4City account with specific privileges.

Expected successful result

Generation of a flow for monitoring values of  devices registered in the Orion

Steps

 

See Supported Protocols for the full list of supported protocols.

The Telemetry protocol is based on the fact that any changes in the IOT Device are communicated to the IOT Broker.

In terms of flows

  • Flow: IOT device →  IOT Broker →  Snap4City Application (as NodeRED processes) put in execution with some Dashboard to provide the evidence of the data arrival
    • Import for testing the flow  "TC2.7 (a) - IOT protocol Telemetry" with the steps described in TC2.13 (on cloud) or import it from a file (if you have not an IOT Application on cloud)
    • Once the flow is deployed you can open the NodeRED dashboard (how to open the view here) to watch the example.

Now you can import the flow "TC2.7 (b) - IOT protocol Telemetry" with the steps described in TC2.13 (on cloud) or import it from a file (if you have not an IOT Application on cloud).

  • The imported stream if deployed notifies an authentication error because the nodes corresponding to the Fiware Orion do not have all the data to work.

To be able to test the flow you have to register a new device (also virtual) on the site following the TC 2.11. Once registered you can download the certificates of the device (private key and certificate) and the authority certificate (download here) and insert them in the configuration of the node.

Or, if it is easier for you, you can copy the K1 and K2 values. In addition to these data that guarantee the security of the data exchanged with the Context Broker, you must also enter the name and type of the device you have just registered.

 

A first flow that monitors the value of the temperature of a sensor registered on the Context Broker. The values are reported in a chart.

The second flow is used for changing the value of the sensor on Orion.

 We remarks that thanks to the flows generated by the Iot Directory block, it is possible to read data from different context brokers and to keep track of the amount of data and generated data by means of the event_log module. Moreover, by means of the Iot Directory block it is possible to send commands to different IoT devices and to keep track of the amount of notifications and commands that are sent to actuators and sensors.

  • Share