M2M API: Machine to machine comunication, such as XML, MQTT, …
M2M (Machine 2 Machine) – or M2M Protocol – refers to direct electronic communication among machines, devices and systems. For example a program in a PC communicating with smart sockets that measure the immediate current, without human intervention.
  • API stands for Application Programming Interface.
  • 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 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

We distinguish between two types of communication. Passive M2M API (NETIO smart sockets as a peripheral device) and M2M Active Client (a program runs in the NETIO smart sockets device and communicates with other products over a LAN).

 

Passive M2M API

Passive M2M API refers to the fact that NETIO 4x smart socket devices support 13 or more 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 4x 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

 

 

Ask for a price or technical parameters

For device testing use name/password demo/demo