An introduction to MQTT

Posted May 11, 2018 7:24 UTC (Fri) by Cyberax (✭ supporter ✭, #52523)
In reply to: An introduction to MQTT by mbolivar
Parent article: An introduction to MQTT

I checked the protocol and it looks like it can run over other media types. Is there any ZigBee based implementation in progress?

As for cloud brokers, I would avoid them as plague. I want my automation working even if my house is offline and on generator power.

An introduction to MQTT

Posted May 11, 2018 10:39 UTC (Fri) by zdzichu (subscriber, #17118) [Link] (2 responses)

That would be MQTT-SN: http://mqtt.org/new/wp-content/uploads/2009/06/MQTT-SN_sp...

I believe you originally meant that plain MQTT requires TCP/IP, “WiFi” being a mental shortcut.

An introduction to MQTT

Posted May 11, 2018 20:56 UTC (Fri) by smurf (subscriber, #17840) [Link] (1 responses)

Does MQTT-SN have any real-world use?

While it's easy to wrap MQTT messages (or MQTT-SN messages) in Zwave, Zigbee, KNX, 1wire, Bluetooth, or whatever other packetized protocol one might think of using, that's not very useful if the goal is to control "real" devices that use native Zigbee or 1wire or … messages. So an application-level gateway is required anyway.

Devices that can use TCP/IP natively, on the other hand, typically don't require MQTT-SN. The overhead of TCP/IP is large enough that using standard MQTT doesn't add any substantial overhead.

An introduction to MQTT

Posted May 12, 2018 9:48 UTC (Sat) by kbee (subscriber, #4468) [Link]

RIOT includes an MQTT-SN implementation, emCute, which runs over UDP [1,2]. RIOT also includes implementations of CoAP, which is an IETF-developed, HTTP-like protocol for constrained devices that includes extensions for publish-subscribe [3].

[1] http://doc.riot-os.org/group__net__emcute.html
[2] https://github.com/RIOT-OS/RIOT/tree/master/examples/emcu...
[3] http://coap.technology/