Device control

IoT Open has full support for controlling and managing devices in the field. IoT Opens interface is called DeviceX / FunctionX (DevX / FuncX) which makes it easy to integrate devices from different manufacturers and different protocols. As the main data carrier, MQTT is used out to the edge where it either goes all the way to the unit or terminates in a CPE / Gateway that translates to the respective unit's protocol. This translation can also be done centrally depending on which protocol the device uses. Units can also be controlled locally at the edge. Local governance, local services and rules in edge can also work offline. Presence-controlled street lighting can thus work even if there is a temporary problem with the connection between the edge and the platform.

DevX / FuncX control

DevX / FuncX saves all devices and functions. A function is someone who can be measured, displayed and / or controlled, for example a temperature, carbon dioxide content, door position, detected vehicle, switch, voltage, ground humidity, fire warning etc. Each function can belong to a unit, but it is not a requirement. A device represents hardware and can have several functions. Examples of units can be a multisensor, smoke alarm, vehicle unit, etc. Arbitrary metadata can be stored on both functions and devices. For example, a function may have properties such as name, type, device, format string, icon, etc. A device can have a serial number, socket side, BIM identification (GUID), manufacturer, model, software version, etc. Only a few of the parameters are mandatory and it is possible to define your own parameters. For example, metadata on a device can be latitude / longitude, free text, vendor information, or other applicable information. Some documented parameters are handled by the platform, while those that the platform does not know are only relevant for integration with other systems.

Among the parameters are which topics on the MQTT bus are used to read and control the function, respectively. Some functions, such as temperature, only have a topic for reading, while a switch or a thermostat have topics for both reading and control.

Via the MQTT bus and the platform's API, devices can be controlled with a delay of typically parts of a second.