3 ms·

My needs were relatively simple in that I needed a system to route quick, short messages without much client overhead. I'd previously done this with XMPP (using

My needs were relatively simple in that I needed a system to route quick, short messages without much client overhead. I'd previously done this with XMPP (using Python) which worked well, but the protocol offered way too many options. Also, trying to find a decent client for my iPad was a nightmare. I switched over to MQTT which is more suited to the role in my case and works as intended.

p4bl0 5y ago
MQTT looks interesting, do you have links to simple implementation of the protocol? I often find simple (even if partial) implementations of protocol a better documentation than the complete specifications.
- Jtsummers 5y ago
  https://mqtt.org/software/ https://mqtt.org/software/ There are a bunch of implementations there.
  - kitd 5y ago
    And once you have your MQTT server running, you can install NodeRed alongside it for a complete "low-code" IoT solution. https://nodered.org/ https://nodered.org/ https://cookbook.nodered.org/mqtt/connect-to-broker https://cookbook.nodered.org/mqtt/connect-to-broker
- PaulHoule 5y ago
  I use https://en.wikipedia.org/wiki/RabbitMQ https://en.wikipedia.org/wiki/RabbitMQ to run the IoT stuff in my house. Mostly I access it through AQMP but it supports MQTT also. An asyncio-driven python script takes events from the outside world and systems that have an cloud component like SmartThings and posts them to RabbitMQ. Other scripts listen for events, make things happen, log data to arangodb, etc. On paper XMPP supports M2M applications but it's not a great fit compared to other protocols.
MattJ100 5y ago
Yeah, if your needs are simple enough and your clients are small, MQTT is a good choice. Two or three XMPP servers even have built-in MQTT bridges for supporting very lightweight clients. From what I've seen, XMPP is used in IoT more for the federation aspect rather than as the "last mile" to the sensors/devices. Cases where you need interoperability and security across different sites/organizations. In any case, the Modern XMPP project (this article) currently only focuses on XMPP for the IM use-case.

p4bl0 5y ago

MQTT looks interesting, do you have links to simple implementation of the protocol? I often find simple (even if partial) implementations of protocol a better documentation than the complete specifications.

Jtsummers 5y ago
https://mqtt.org/software/ https://mqtt.org/software/ There are a bunch of implementations there.
- kitd 5y ago
  And once you have your MQTT server running, you can install NodeRed alongside it for a complete "low-code" IoT solution. https://nodered.org/ https://nodered.org/ https://cookbook.nodered.org/mqtt/connect-to-broker https://cookbook.nodered.org/mqtt/connect-to-broker
PaulHoule 5y ago
I use https://en.wikipedia.org/wiki/RabbitMQ https://en.wikipedia.org/wiki/RabbitMQ to run the IoT stuff in my house. Mostly I access it through AQMP but it supports MQTT also. An asyncio-driven python script takes events from the outside world and systems that have an cloud component like SmartThings and posts them to RabbitMQ. Other scripts listen for events, make things happen, log data to arangodb, etc. On paper XMPP supports M2M applications but it's not a great fit compared to other protocols.

MattJ100 5y ago

Yeah, if your needs are simple enough and your clients are small, MQTT is a good choice. Two or three XMPP servers even have built-in MQTT bridges for supporting very lightweight clients. From what I've seen, XMPP is used in IoT more for the federation aspect rather than as the "last mile" to the sensors/devices. Cases where you need interoperability and security across different sites/organizations. In any case, the Modern XMPP project (this article) currently only focuses on XMPP for the IM use-case.