Difference between revisions of "MQTT"

From wiki.netio-products.com
Jump to navigation Jump to search
(Created page with "NETIO products supporting MQTT protocol in several ways. All of them are standard MQTT from broker perspective. Difference is in payload structure and device behaviour. - S...")
 
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
NETIO products supporting MQTT protocol in several ways. All of them are standard MQTT from broker perspective. Difference is in payload structure and device behaviour.  
+
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.  
  
−
- Standard Power Ca
+
<b>MQTT implementations</b>
 +
<br>
 +
1) [https://www.netio-products.com/en/glossary/mqtt Standard <b>NETIO MQTT M2M API</b>] for [https://www.netio-products.com/en/glossary/netio-4x NETIO 4 / 4All / 4C] devices <br>
 +
2) [https://wiki.netio-products.com/index.php?title=MQTT-flex NETIO <b>MQTT-flex</b>] <br>
 +
3) NETIO <b>Lua MQTT</b><br>
 +
<p></p>
  
−
There is a lot of approaches in integration of MQTT in devices and systems. One vendor prefer one topic with structured data payload, the another one prefer tree topic structure with simple value in data payload. MQTT-flex is a standard [https://en.wikipedia.org/wiki/MQTT MQTT] with specific configuration approach. The goal of MQTT-flex is to give a user opportunity to integrate NETIO device with any system with different data approach.
+
= 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 <b>AN26</b>: MS Azure getting data from NETIO 4x (Lua MQTT) Active client - power measuring and output control  from cloud service
 +
 
 +
Download the Protocol description in <b>PDF</b>: [https://www.netio-products.com/en/download#open-api NETIO MQTT M2M API]
 +
 
 +
Check the example: [https://www.netio-products.com/en/application-notes/an12-mqtt-control-of-netio-smart-sockets-using-the-hivemq-broker <b>AN12</b>: The first steps with MQTT we recommnend AN12 MQTT control of NETIO smart sockets using the HiveMQ broker]
 +
 
 +
===Supported devices:===
 +
* [https://www.netio-products.com/en/device/netio-4all NETIO 4All] <br>
 +
* [https://www.netio-products.com/en/device/netio-4 NETIO 4] <br>
 +
* [https://www.netio-products.com/en/device/powerpdu-4c PowerPDU 4C] <br>
 +
 
 +
 
 +
= NETIO Lua MQTT =
 +
MQTT implementation based on <b>Lua Active Client</b> 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:===
 +
* [https://www.netio-products.com/en/device/netio-4all NETIO 4All] <br>
 +
* [https://www.netio-products.com/en/device/netio-4 NETIO 4] <br>
 +
* [https://www.netio-products.com/en/device/powerpdu-4c PowerPDU 4C] <br>
 +
 
 +
 
 +
Check the <b>AN35</b>: 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:===
 +
* [https://www.netio-products.com/en/device/powercable-rest-101x PowerCable REST 101x] <br>
 +
* [https://www.netio-products.com/en/device/powercable-mqtt-101x PowerCable MQTT 101x] <br>
 +
* [https://www.netio-products.com/en/device/powerpdu-4ps PowerPDU 4PS] <br>
 +
* [https://www.netio-products.com/en/device/powerpdu-4ks PowerPDU 4KS] <br>
 +
* [https://www.netio-products.com/en/device/powerpdu-8qs PowerPDU 8QS] <br>
 +
* [https://www.netio-products.com/en/device/powerdin-4pz PowerDIN 4PZ] <br>
 +
* [https://www.netio-products.com/en/device/powerbox-3px PowerBOX 3Px] <br>
 +
* [https://www.netio-products.com/en/device/powerbox-4kx PowerBOX 4Kx] <br>

Latest revision as of 14:41, 16 June 2022

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 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:


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:

Retrieved from "https://wiki.netio-products.com/index.php?title=MQTT&oldid=944"