Interface to the internet of Things
Connecting IoT devices or “things” involves the need to overcome a common set of problems arising in the different layers of the communication model. Using sensor data or acting upon them requires interaction with a heterogeneous environment of devices running different protocols (due to the lack of globally accepted standards), dispersed and accessible through multiple wireless technologies.
To learn more about the Interface to the internet of Things, check out the documentation
What are IoT Agents?
The IoT Agent (IDAS) component is an implementation of the Backend Device Management GE, according to the FIWARE reference architecture. You are here because you need to connect objects to gather data or interact with them, typical IoT use case scenario . If so, you need to use one of the existing IoT Agents that are part of IDAS.
You need this component if you plan to connect IoT devices/gateways to FIWARE-based ecosystems. IoT Agents translate IoT-specific protocols into the NGSI context information protocol, that is the FIWARE standard data exchange model. You do not need this component if your devices or gateways natively support the NGSI API.
FIWARE-Ready IoT devices are able demonstrate the ability of the IoT solutions to seamless interoperate with FIWARE platforms. Any IoT device which is able to connect to the context broker (either directly or via an IoT Agent) is able to undergo a certification and testing process and can be added to the FIWARE marketplace and labelled as a FIWARE-Ready IoT Device.
Why Use IoT Agents?
By using an IoT Agent , your devices will be represented in a FIWARE platform as NGSI entities in a Context Broker. This means that you can query or subscribe to changes of device parameters status by querying or subscribing to the corresponding NGSI entity attributes at the ContextBroker.
Additionally, you will be able trigger commands to your actuation devices by updating specific command-related attributes in the associated NGSI entities representation at the Context Broker. This way, all hardware interactions with IoT devices can be handled by the Context Broker, using a homogeneous NGSI interface.
IoT Agent Framework Library
Library for developing your own IoT Agent.
The IoT Agent Framework Library project is part of FIWARE and but is not rated as a standalone component. It is used in the following IoT Agents:
IoT Agent for JSON
The IoT Agent for JSON project is part of FIWARE and has been rated as follows:
IoT Agent for Ultralight
The IoT Agent for the Ultralight project is part of FIWARE and has been rated as follows:
IoT Agent for LoRaWaN
IoT Agent for the LoRaWAN protocol (with CayenneLpp and CBOR data models)
The IoT Agent for LoRaWAN project is part of FIWARE and has been rated as follows:
IoT Agent for LightWeight Machine2Machine
IoT Agent accepting COAP requests.
The IoT Agent for LightWeight Machine2Machine project is part of FIWARE and has been rated as follows:
🌱 IoT Agent for OPC UA (Incubated)
IoT Agent accepting data from OPC UA devices.
The IoT Agent for OPC-UA project is part of FIWARE and has been rated as follows:
🆕 IoT Agent for Sigfox (Incubated)
IoT Agent for the Sigfox protocol.
The IoT Agent for Sigfox project is a new component within FIWARE and will be rated in the current release
🌱 Open MTC (Incubated)
A reference implementation of the oneM2M standard, for conducting applied research and developing innovative M2M and IoT applications. It offers an NGSI interface for connection to the Orion Context Broker
The Open MTC project is part of FIWARE and has been rated as follows: