Create a specific client that makes things even easier for the user when programming with Arduino. We need to make things easy for people to experiment the best way they can.

Configure Zeroconf (e.g. Apple Bonjour) - MQTT Wiki

The Arduino client reconnect using Mosquitto, but it does not using Mosca. We could try to write to knolleary and ask to check it out to understand what's missing.

After the Redis configuration the /get definition is not working. Most probably the /get channel with Mosca (or Ascoltatori) is defined as a Buffer(hex).

We need to understand how to fix this problem to make things correctly work as right now we "hack" this problem by defining a MQTT

// NORMAL FLOW (using Ascoltatori)
publish(req, '/get/')
var publish = function(req, mode) {
  payload = { message: req.body };
  payload.message = new Buffer(payload.message, 'hex');
  var topic = 'devices/' + req.params.id + mode;
  debug('[API REQ] Publishing topic', topic, req.body, payload.toString());

  ascoltatore.publish(topic, req.body, function() {
    console.log('[API REQ] Message published to the topic', topic, req.body);
  });
}

// HACK
var client = mqtt.createClient(port, host, { username: req.params.id, password: req.get('X-Physical-Secret') });
client.on('connect', function() {
   client.publish('devices/' + req.params.id + '/get', JSON.stringify(req.body));
   client.end();
})

One further note (obvious) is that the MQTT client (pass through Mosca) works just fine. If I pass through Ascoltatori it doesn't set properly the payload. We need to understand how Mosca uses ascoltatori to store the Redis messages.

It's almost mandatory to add versioning to this part of the system as it could change quite a lot. And once the devices are out we can't change them all.

I'll send a PR with the Dockerfile

We need to offer to Lelylan a solution to easily simulate an MQTT device. We could offer something on Lelylan Node so that a client is open and closed after the supscribed notification is received.

URI - nodes.lelylan.com/mqtt/simulations/:id
FLOW - When a message is sent to the simulation URI, then a client is initialized. It listen for the message he subscribed for, receive it, update it and makes a PUT request to update the device properties in Lelylan.

Find out a way to log the published message from MQTT to the physical device. Right now we have the logs when the physical device sends data to Lelylan, but not when is Lelylan to send it. This is really important to investigate eventual problems.

The deploy of mqtt is made as root but it should be as deploy user.
The code that should make this possible is the following one, but it does not work.

app.on('ready', function() {
  debug('MQTT Server listening on port', process.env.NODE_PORT)

  if (process.getuid() === 0)
    require('fs').stat(__filename, function(err, stats) {
      if (err) return console.log(err)
      process.setuid(stats.uid);
    });
});

Add a one page presentation site where you describe what this project is, how we built it and why. Add all the info we could need before the project lunch. Before, we could write some tech articles on our blog.

Getting errors while installing on Mac OS 10.11
node -v v5.1.1
node-gyp -v v3.0.3

Error log - mqtt-log.txt

Any hints are greatly appreciated! Thanks.

Add examples (at least) for the following languages.

• Node.js
• Arduino

hi all,
I'm using this link which is good but the problem is when I want to use 3 brokers in the cluster and when the 3 broker connect to proxy (even without clustering ) the brokers are kept open and shut down by there owns ( one broker at a time)
what is the problem, please help

Ask vivien more info about dotcloud and try to use doker to deploy and make MQTT solutions scale.

• Load testing
• Test all functionalities