MQTT

NETIO products supporting MQTT protocol in several ways. All of them are standard MQTT from broker perspective, the payload structure and device behaviour can be different.

MQTT implementations
1) Standard NETIO MQTT M2M API for NETIO 4 / 4All / 4C devices
2) NETIO MQTT-flex
3) NETIO Lua MQTT

Standard NETIO MQTT M2M API

A bit chatty implementation of the MQTT protocol for NETIO 4x devices. Easy to setup, all MQTT structures are fixed. There is also JSON based version of the payload for MS Azure implementation. Check the NETIO AN26: MS Azure getting data from NETIO 4x (Lua MQTT) Active client - power measuring and output control from cloud service

Download the Protocol description in PDF: NETIO MQTT M2M API

Check the example: AN12: The first steps with MQTT we recommnend AN12 MQTT control of NETIO smart sockets using the HiveMQ broker

Supported devices:

• NETIO 4All
  
• NETIO 4
  
• PowerPDU 4C
  

NETIO Lua MQTT

MQTT implementation based on Lua Active Client scripts. It's not as good as MQTT-flex but you can create you own data structure and data sending conditions in the Lua scripts on the NETIO 4x devices.

Supported devices:

• NETIO 4All
  
• NETIO 4
  
• PowerPDU 4C
  

Check the AN35: Lua MQTT - first steps using HiveMQ broker. Lua Active client

NETIO-flex

The MQTT-flex version of the MQTT protocol can be configured in detail thanks to the “flex” extension.

https://www.netio-products.com/en/glossary/mqtt-flex

More details about MQTT-flex: https://wiki.netio-products.com/index.php?title=MQTT-flex

Supported devices:

• PowerCable REST 101x
  
• PowerCable MQTT 101x
  
• PowerPDU 4PS
  
• PowerPDU 4KS
  
• PowerPDU 8QS
  
• PowerDIN 4PZ
  
• PowerBOX 3Px
  
• PowerBOX 4Kx