adamvr / mqtt-growl

A growl based mqtt monitor, written in node.js javascript.

mqtt-growl

A simple little app that subscribes to a given list of mqtt topics on the specified broker and generates a growl notification whenever a message arrives

dependencies

• mqtt.js
• node-growl
• optimist

todo

Notifications on growl servers other than localhost

known problems

Tends to crash on very busy mqtt brokers (such as test.mosquitto.org). This is likely due to node-growl spawning too many processes. The stop gap solution is the -d parameter, which allows node-growl to spawn a process only every x milliseconds.

mqtt-growl's Issues

Connects but never growls?

I've been trying this in node 0.8.8 against m2m.eclipse.org - it appears to connect and ping, but as messages are published on the topic it is listening on, no Growl notifications appear.

Crashes if too many publishes occur

node-growl spawns a new growlnotify process for each notification and if we get a whole heap of publishes it tends to hit the process limit.

child_process.js:477
    throw errnoException(errno, 'spawn');
    ^
Error: spawn EMFILE
    at errnoException (child_process.js:514:11)
    at ChildProcess.spawn (child_process.js:477:11)
    at child_process.js:375:9
    at Object.execFile (child_process.js:285:15)
    at child_process.js:252:18
    at growl (/usr/local/lib/node_modules/mqtt-growl/node_modules/growl/lib/growl.js:187:3)
    at Connection.<anonymous> (/usr/local/lib/node_modules/mqtt-growl/mqtt-growl:64:9)
    at Connection.emit (events.js:67:17)
    at Connection.parse (/usr/local/lib/node_modules/mqtt-growl/node_modules/mqttjs/lib/connection.js:108:9)
    at Socket.emit (events.js:67:17)

Consider migrating to something that has a persistent connection to the growl server or throttle node-growl somehow.

Suggestions:

https://github.com/betamos/Node-Growler