- API stands for Application Programming Interface. OPEN API = Documented & public API.
- M2M (Machine to Machine) refers to direct communication among physical products (devices). M2M includes everything from the physical layer (wired/wireless) to the protocol and application layers.
-
Protocol is a general description of a communications layer.
- M2M Active Client is an active program (e.g. a Lua script) that communicates (controls the communication) with another device using a M2M protocol.
M2M API (Open API) refers to a passive interface for electronic communication with a remote device or software. Unless specified otherwise (e.g. in the cloud-oriented MQTT protocol), the device waits until it receives a request for a value from an active element (a master system).
M2M API / M2M Protocol specify the message format that can be used to control the device (control individual electrical sockets) or to read values from the device (electricity metering). NETIO smart sockets use M2M protocols such as XML/JSON over HTTP(s), MQTT, SNMP and so on.
In the context of NETIO products
- Passive NETIO unified Open API (NETIO smart sockets as a peripheral device)
- M2M Active Client (a program runs in the NETIO smart sockets device and communicates with other products over a LAN).
Passive NETIO unified Open API
NETIO smart socket devices support several M2M API protocols that can be used to control the device from a master system. A protocol is defined by its specification and its behavior cannot be modified outside of this specification.
>> For a list of protocols, see: NETIO M2M API Interfaces
M2M Active Client
A Lua script runs in the NETIO PowerPDU 4C smart sockets device. The communication is initiated and controlled by the NETIO device. See M2M Active Client.
Lua scripts can be modified by the customer. This makes it possible to adapt to various third-party APIs and products.
>> For a description of Lua scripts, see: NETIO Lua scripts