MQTT is a machine-to-machine (M2M)/"Internet of Things" connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium. For example, it has been used in sensors communicating to a broker via satellite link, over occasional dial-up connections with healthcare providers, and in a range of home automation and small device scenarios. It is also ideal for mobile applications because of its small size, low power usage, minimised data packets, and efficient distribution of information to one or many receivers (more...)

News RSS feed

Places to talk about MQTT

July 4th, 2012 - No Comments

There are a number of mailing lists and discussion groups and spaces for MQTT now, so I thought it might be useful to quickly summarise the main ones – and clarify what they are for.

Users of all of the lists are generally very friendly and can help you to navigate between them, but I just thought it would be useful to explain the “main purpose” of each group. Discussions are not limited to mailing lists and happen on Twitter, in IRC, and across the web. We try to follow as many of them as possible! There’s an additional list on the Community page.

For more about MQTT and the relationship to Eclipse, check our wiki page MQTT at Eclipse. For more on mosquitto, check out that project’s excellent website!

MQTT Service Hook added to Github

May 3rd, 2012 - 5 Comments

Thanks to a pull-request from friend of MQTT @zer0c00l, GitHub now has the ability to publish an MQTT message whenever a repository has a change pushed to it.

To get your repository publishing, find your way to its admin page.

From there, under the Service Hooks tab, select the MqttPub hook in the list to bring up the configuration options.

The options speak for themselves, but there are some handy notes provided to help you figure it out. Be sure to check the ‘active’ box before hitting Update Settings.

With that done, you should start to get messages published whenever something is committed to the repository. The message itself is a json blob that contains all of the information about the commit that you could possible want.

You can read more about the contents of the blob on GitHub’s Post-Receive Hooks help page.

Initial Eclipse Paho contributions completed

March 29th, 2012 - No Comments

At EclipseCon 2012 in Reston, VA this week, it was announced that both of the initial code contributions for Eclipse Paho are now available in the Eclipse code repositories. These comprise the source code for the production-level C and Java clients, which are currently shipped by IBM with WebSphere MQ.

What is Eclipse Paho? There’s a page on the wiki about this, but in brief, it’s part of a broader machine-to-machine (M2M) initiative at the Eclipse Foundation. Code is licensed under the Eclipse Public License (EPL).

For more on Paho, take a look at the project page and project wiki at Eclipse, which include links to the core paho-dev mailing list, Bugzilla, and the code repository where the C and Java clients can be found. Binary downloads will follow in future. There is also a public test broker instance at An update on progress on the Paho project has been posted on Slideshare.

Other news at EclipseCon included demonstrations by Sierra Wireless of an end-to-end application using the Eclipse Koneki Lua Development Tools receiving data from Arduino sensors, via an MQTT broker to an Android application; a demonstration of the Eclipse-based test tooling for MQTT which Eurotech will be donating to the Paho project in the coming months; and an initial offer of the existing third-party Lua client to the Paho project. It’s exciting to see this kind of momentum behind this industry initiative, and the opening up of the MQTT client code.

Oh, and what does the word “paho” actually¬†mean? Simple. It’s the Maori word for “broadcast”. So, tell everyone!