Difference between revisions of "MQTT"
| Line 16: | Line 16: | ||
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] | 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] | ||
| + | |||
| + | <b>Supported devices:</b> | ||
| + | <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> | ||
= NETIO Lua MQTT = | = 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. | 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. | ||
| + | |||
| + | <b>Supported devices:</b> | ||
| + | <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> | ||
| + | |||
Check the <b>AN35</b>: Lua MQTT - first steps using HiveMQ broker. Lua Active client | Check the <b>AN35</b>: Lua MQTT - first steps using HiveMQ broker. Lua Active client | ||
Revision as of 00:15, 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 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
