Difference between revisions of "MQTT"
| Line 4: | Line 4: | ||
<br> | <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> | 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) NETIO <b>MQTT-flex</b> <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> | 3) NETIO <b>Lua MQTT</b><br> | ||
<p></p> | <p></p> | ||
| Line 19: | Line 19: | ||
<b>Supported devices:</b> | <b>Supported devices:</b> | ||
<br> | <br> | ||
| − | + | * [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> | |
| Line 29: | Line 29: | ||
<b>Supported devices:</b> | <b>Supported devices:</b> | ||
<br> | <br> | ||
| − | + | * [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> | |
| Line 43: | Line 43: | ||
More details about MQTT-flex: https://wiki.netio-products.com/index.php?title=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-mqtt-101x PowerCable MQTT 101x] <br> | ||
| + | * PowerCable OEM (DevKit) <br> | ||
| + | * PowerPDU 4PS <br> | ||
| + | * PowerDIN 4PZ <br> | ||
| + | * PowerBOX 3Px <br> | ||
Revision as of 02:08, 29 November 2019
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:
- PowerCable MQTT 101x
- PowerCable OEM (DevKit)
- PowerPDU 4PS
- PowerDIN 4PZ
- PowerBOX 3Px
