#MQTTBox ####Developers helper program to create and test MQTT connectivity protocol. Supercharge your MQTT workflow with MQTTBox for Web and Chrome! Build, test, and document your MQTT connectivity protocol.

######Web app is available HERE! ###### Chrome app is available HERE!

####MQTTBox features include:

• Connect to multiple mqtt brokers with TCP or Web Sockets protocols
• Connect with wide range of mqtt client connection settings
• Publish/Subscribe to multiple topics at same time
• Supports Single Level(+) and Multilevel(#) subscription to topics
• Copy/Republish payloads
• History of published/subscribed messages for each topic
• Reconnect client to broker

Please report Feature Requests, Enhancements or Bugs to [email protected] or on Github

##Getting Started Make sure you have Node.js installed and follow below steps to build and execute.

• git clone [email protected]:workswithweb/MQTTBox.git

• cd MQTTBox

• npm install

Thats it !!! Your project is setup. Execute below commands in your current folder (MQTTBox) as per your app requirements.

######Web App Builds

• gulp build - Generates build folder with all compiled static web assets in your current directory (MQTTBox). You can deploy build in you web/app server.

• gulp - Live development mode. Use while development to see live reload of your web app when changes done in code.

######Chrome App Builds

By default, build folder generated is for web app. If you want to generate Chrome app build, follow below steps.

• Change variable AppConstants.CLIENT_TYPE in src/app/utils/AppConstants.js to AppConstants.CHROME_APP (by default it is AppConstants.WEB_APP to generate web app.)

• Need to generate custom build of mqtt.js to support TCP with chrome-net (detail documentation in progress for this step)

• Execute gulp build or gulp as mentioned above. This should generate build folder.

• Copy chrome specific assets from chrome folder into build folder. This should have all assets in build folder to upload to chrome store.

NOTE: Web App supports only Websockets because of browser limitations.