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...)
January 22nd, 2014 - No Comments
EclipseCon 2014, coming up in March, has a strong focus on the Internet of Things.
As part of EclipseCon, the Eclipse Foundation is delighted to host an interoperability testing day for MQTT developers and vendors. The goal is to have representation from a wide range of MQTT brokers, clients, and MQTT-enabled devices. If you work with MQTT, take a look at the Eventbrite page to sign up for the interoperability testing, and check the Eclipse Paho wiki page for more infomation. If you are building APIs or devices on top of MQTT, this is a great way of interacting with the community, broadening awareness of your project or product, and making sure that things work smoothly for you users and customers!
Feel free to contact the Eclipse Paho team via their mailing list, if you have any questions.
January 10th, 2014 - 1 Comment
A significant milestone has been reached in efforts to standardise MQTT. The OASIS MQTT Technical Committee have approved a Committee Specification Draft which is now open for a 30-day public review.
The public review starts 13 January 2014 at 00:00 GMT and ends 11 February 2014 at 23:59 GMT.
This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.
More details are available in the announcement.
December 2nd, 2013 - 3 Comments
The nomenclature of “MQTT-S” (sensors? security? sausages?) has been confusing to some people, so recently there was a discussion about renaming the protocol to MQTT-SN.
The new name would be MQTT-SN, standing for exactly the same long name, MQTT for Sensor Networks. Some people had assumed that the S in MQTT-S stood for secure, so we hope this change will avoid that confusion.
As part of this change, the copy of the specification now available from the mqtt.org Documentation page now reflects that name change, and links to all previous versions of the specification have been permanently redirected. This is still version 1.2 of the specification, updated to reflect the changed name. MQTT for Sensor Networks is aimed at embedded devices on non-TCP/IP networks, whereas MQTT itself explicitly expects a TCP/IP stack.
So, how can you get started with MQTT-SN? Here’s the exciting part – Really Small Message Broker and Mosquitto are coming together in a new Eclipse project, called Eclipse Mosquitto (here’s the project proposal). The RSMB source code is now available at Eclipse, and it has built-in MQTT-SN support… Ian Craggs shares a very quick getting started guide on his blog. It turns out that Nicholas Humfrey’s tools for MQTT-SN work well with RSMB as well!