MQTT-Debugging

[Sandro Kock]

Hi everyone,

I am Sandro from, Göttingen Germany. Currently, I am working on a MQTT-Debugging application for Chrome as part of this year Google Summer of Code. The application is similar to Copper, the Firefox Add-on that allows CoAP developers to debug their CoAP-applications. 

At the moment, I am working on the UI and like to get some feedback from the MQTT-community. At first, the application is based on the following concepts: 

• You can have multiple environments for different debugging scenarios 

• Environments can have multiple connections to different brokers

• Connections can have multiple subscriptions to different topics

• Subscriptions can have multiple conditions that trigger events/notifications if these conditions are fulfilled

• A condition can be for example if you only expect values from »0…10« on a certain topic but receive »100«, a »ERROR/WARNING« notification would be displayed to point out an error

• On the other hand sometimes you like to quickly simulate/test some behavior, e.g. for every 10th temperature reading, the average of these needs to be published under a different topic, which could be done be a »custom trigger«

• Manually publishing to a topic will also be possible 

To test the UI-concepts I would like to ask for two or three volunteers, with whom I could simulate certain situations and observe how well these tasks are carried out.  If someone is interested, please contact me directly and we can discuss everything off the mailing list. 

The current source is available at [1], but you need to compile the »SCSS« files to »CSS« first to actually see the UI. For those who just like to see the UI, it is available at [2].

Besides, I like to discuss the name of the application. Currently, my favourite is »MQTTinspect« or »MQTTinspector«, but I have several other ideas at [3]. Feel free to add your idea to the list or highlight/comment the ones you like. 

Thanks for your help,

Sandro

P.S. sorry for every on the PAHO mailing list to receive this twice 

[1] https://github.com/sandro-k/mqtt-chrome

[2] http://mqtt.madein-hamburg.de/ideas/

[3] https://docs.google.com/document/d/1rW8-LAd_MTeSdFNzeKr1sH-Q-PJvpfyBrTjVftBNNNg/edit?usp=sharing

[Sandro Kock]

Hey everyone,

you might remember the MQTT-Debugging App I am working on for this years Google  Summer of Code [1]. The App is shaping up and I would like to present you to some of the things that are the outcome of my work.

 -- Short version --

The current beta is available at [2] and can be used at [3], pleas uses Chrome 36 or later

 -- Longer version --

I decided to use Polymer [4] aka. Webcomponents to modularize the application. Basically with Polymer custom HTLM-Elements can be created to utilize any user-defined behavior. These elements can be but don’t have to be visible. For e.g. a simple Ajax request can be made via <core-ajax auto url="http://www.eclipse.org/paho"></core-ajax> to fetch the resource available at `url`. In the same fashion I created an <mqtt-connection> element that can be used to create a mqtt connection to any mqtt broker supporting websockets. As basis the mqtt-connection element uses Mows (Mqtt.js over WebSockets) [5]. If there is any interest within the community I am going to release the mqtt elements separately so that they can be used independently in any WebApplication.

If you have any questions, feedback or bugs feel free to contact me directly or just open an issue at [2]. 

Have a nice Weekend,

Sandro

[1] http://mqtt.madein-hamburg.de/ideas/

[2] https://github.com/sandro-k/mqtt-chrome

[3] http://mqtt.madein-hamburg.de/beta0.1/

[4] http://www.polymer-project.org/

[5] https://github.com/mcollina/mows