We are pleased to present below all posts tagged with 'MQTT'. If you still can't find what you are looking for, try using the search box.
My M2Mqtt open source library has finally come to version 3.0 with two important news ! In the first place, the operations of publish, subscribe and unsubscribe have become completely asynchronous. Until the previous version , the corresponding methods were synchronous even if the library raised related events on published message and subscription / unsubscription occurred. In particular , in the Publish() method the exchange of messages with the broker was run to ensure the required QoS ( PUBACK for QoS 1 , PUBREC , PUBREL and PUBCOMP for QoS2 ) while in the Subscribe() and Unsubscribe() methods handled the acknowledge ( SUBACK and UNSUBACK ). Now , these methods not bother to put a message in a queue and immediately return the message id itself , which is why there is a "breaking change" on the Subscribe() method that does not return the array with the "granted" QoS level. This array is still provided at the end of the asynchronous operation in the event args object of the corresponding event. I tal ...
On Saturday 15th of February was staged the second edition of Microsoft Embedded Conference which was held at the Holiday Inn in Naples and organized by the DotNetCampania community (I am a member of it), TinyCLR.it and Embedded101, this community that is a reference on Windows Embedded of which, I’m a "board of directors" member since November 2013. Also this year there was a good turnout of attendees even though it was Saturday, because the main topic was the Internet of Things and M2M Communication of which we hear persistently in the last period as the business of the future for the big network. At 8:00, the team was ready for the preparations and organization in order to accommodate very well the attendees and ensure that the event will start on time. As with all events, we started with the keynote of our president Michele Aponte, who presented the community and to whom I have given ...
New release for my M2Mqtt library, MQTT client available for any platform based on .Net Framework (from the desktop to the micro via the compact), now at version 2.4.0.0 and as always is available on CodePlex and Nuget. Bug Fix : message identifier no longer cross-broker This time the update contains, among other things, an important bug fixes on the message identifier generation for PUBLISH, SUBSCRIBE and UNSUBSCRIBE messages provided by the MQTT protocol. In previous versions, the generation of this identifier was encapsulated in the base class of the hierarchy of messages, the MqttMsgBase, highlighting the anomaly of a message identifier increasing cross-broker, which was used the same variable (static) for the generation also if the client was instantiated multiple times in our application to connect to multiple different brokers. Obviously, the protocol provides that the identifier is bound to the client-broker pair, namely that it is unique for each connection to the broker. .Net Compact Framework 3 ...
This time again with great pleasure, my M2Mqtt library (MQTT client for all versions of the. Net Framework) is mentioned in the "fardware friday post" on the blog Coding4Fun on Channel9 at the following link !
The post highlights the main latest features, support for security through SSL / TLS protocol and event management asynchronously. It is also highlighted my demo on the use of the MQTT client with 2lemetry platform.
The satisfaction is double in knowing that my work is attracting a lot of interest and that the library is increasingly being used. Obviously, this leads me to improve it and in fact approaching many surprises and improvements!
Now you can find numerous online platforms that offer the service of "device to the cloud," in order to acquire data from remote devices, save and expose them to other devices: one of these is 2lemetry. It provides a RESTful interface over HTTP and an MQTT interface that we are going to use with the M2Mqtt client library. First you need to register online : At the end of the registration, you can log in to your account page and view some information, including the most important one is the "domain", which will be the root of all topics on which we are going to publish or receive messages via MQTT. At this point we can move immediately to develop a simple application by choosing between all platforms supported by the M2Mqtt library (.NET Framework, .Net Compact Framework or. Net Micro Framework). In a real case, we use the Netduino Plus board with a temperature sensor (usually the TMP102 already widely used in previous posts and where the driver can be found in uPLibrary) to send the data collected onlin ...
I made a bug fix on my Library M2Mqtt (MQTT client) that allows you to better manage the case where the client does not transmit anything for a time equal to the "keep alive period " and the keep alive thread, whose task is to ping the broker to keep the connection alive, does not receive anything within the timeout period (ex. broker shutdown, network disconnection, ...).
The update is already available on CodePlex and Nuget !
After releasing the new version of my M2Mqtt library with support for SSL / TLS with server-side authentication, the time has come to show you an example of use. Choose and install the broker: Mosquitto First we have to choose an MQTT broker among those available but unfortunately no one is developed using the .Net Framework . Discarding more complex solutions , especially with regard to the installation and configuration , such as IBM Websphere , we can take into account to brokers like RabbitMQ , HiveMQ or Mosquitto. In this case , my choice was Mosquitto that we can download from the official web site for various operating systems based on Linux , as well as there is a convenient installer for the Windows environment . In fact, for Windows there are two installation modes: the first uses an installer in which the broker is compiled natively while in the second case is based on the Cygwin provides a Linux-like environment for Windows. It 'obvious that the first mode is the most simple and immediate . Afte ...
I just updated only on CodePlex (for now) M2Mqtt library (version 2.1.0.0), adding the automatic detection of any IPv6 address to connect. To determine the address class (AddressFamily), I implemented the '"Extension Method" GetAddressFamily() for the IPAddress class through the static class IPAddressUtility, necessary only because the. NET Micro Framework does not itself provide the property AddressFamily the IPAddress class. In fact, in the case of full / compact. Net Framework is returned that property while in the case of. NET Micro Framework is done by a simple search of the ":" character (separator in IPv6 addresses). 1: public static AddressFamily GetAddressFamily(this IPAddress ipAddress) 2: { 3: #if (!MF_FRAMEWORK_VERSION_V4_2 && !MF_FRAMEWORK_VERSION_V4_3) 4: return ipAddress.AddressFamily; 5: #else 6: return (ipAddress.ToString().IndexOf(':') != -1) ? 7: AddressFamily.InterNetworkV6 : AddressFamily.InterNetwork; 8: #endif ...
The MQTT client, which I released on CodePlex that can be used with all versions of the. Net Framework specially with NET Micro Framework, was published with a blog post on Coding4Fun on Channel9 by Greg Duncan.
I let it go longer than expected but finally I did ... as they say ... better late than never!
All my projects on CodePlex have been updated to support the latest versions of. NET Micro Framework, the 4.2 and 4.3, but above all Visual Studio 2012!
I’m speaking about :
I hope I have done something pleasing for those who have used them until now.