New plugin pimatic-mqtt

---

I have these devices

16:09:54.252 [pimatic-mqtt] subscribe: kenocontrol/env/sun/inSky
16:09:54.259 [pimatic-mqtt] subscribe: kenocontrol/env/sun/azimuth
16:09:54.263 [pimatic-mqtt] subscribe: kenocontrol/env/sun/altitude
16:09:54.275 [pimatic] New device "Sonnenposition"...
16:09:54.333 [pimatic-mqtt] subscribe: kenocontrol/rf24/lichtsensor/light
16:09:54.341 [pimatic-mqtt] subscribe: kenocontrol/rf24/lichtsensor/status
16:09:54.346 [pimatic] New device "Lichtsensor"...
16:09:54.393 [pimatic-mqtt] subscribe: kenocontrol/env/windspeed
16:09:54.398 [pimatic] New device "Windsensor"...
16:09:54.481 [pimatic] New device "Schlafzimmer Tür"...
16:09:54.533 [pimatic-mqtt] subscribe: kenocontrol/rf24/schlafzimmer/temp
16:09:54.537 [pimatic-mqtt] subscribe: kenocontrol/rf24/schlafzimmer/hum
16:09:54.542 [pimatic] New device "Schlafzimmer Temp."...
16:09:54.607 [pimatic-mqtt] subscribe: kenocontrol/rf24/badezimmer/temp
16:09:54.611 [pimatic-mqtt] subscribe: kenocontrol/rf24/badezimmer/hum
16:09:54.616 [pimatic] New device "Badezimmer Temp."...
16:09:54.664 [pimatic-mqtt] subscribe: kenocontrol/rf24/kind_nord/temp
16:09:54.669 [pimatic-mqtt] subscribe: kenocontrol/rf24/kind_nord/hum
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at MqttClient.EventEmitter.addListener (events.js:160:15)
    at new MqttSensor (/home/pi/pimatic-app/node_modules/pimatic-mqtt/devices/mqtt-sensor.coffee:18:26)
    at Object.createCallback (/home/pi/pimatic-app/node_modules/pimatic-mqtt/mqtt.coffee:86:20)
    at DeviceManager._loadDevice (/home/pi/pimatic-app/node_modules/pimatic/lib/devices.coffee:1228:26)
    at /home/pi/pimatic-app/node_modules/pimatic/lib/devices.coffee:1253:16
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:507:31)
    at Promise._settlePromiseAt (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:581:18)
    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:697:14)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/main/async.js:123:16)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/main/async.js:133:10)
    at Async.drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/main/async.js:15:14)
    at process._tickDomainCallback (node.js:459:13)
16:09:55.789 [pimatic] New device "Kind Nord Temp."...
16:09:55.844 [pimatic-mqtt] subscribe: kenocontrol/rf24/kind_sued/temp
16:09:55.850 [pimatic-mqtt] subscribe: kenocontrol/rf24/kind_sued/hum
16:09:55.855 [pimatic] New device "Kind Süd Temp."...

Hi @kenci, I replicated this error. Can I ask what OS you’re using?

@wutu

"Raspbian GNU/Linux 8 (jessie)"
Linux home 4.1.19-v7+ #853 SMP Wed Mar 9 18:09:16 GMT 2016 armv7l GNU/Linux

new version of pimatic-mqtt - 0.8.8

@jfoucher thanks for adding TLS support
changes for compatibility with version 9

@kenci
casually I managed to replicate the error with Pimatic 8 and Debian Jessie. I do not have much time, but still look at it.

@wutu
what means

Cannot find module './predicates_and_actions/mqtt_action

?
mqtt is installed

21:42:26.623 [pimatic] info: Loading plugin: "pimatic-mqtt" (0.8.8)

@wutu

same error

error [pimatic]: Cannot find module './predicates_and_actions/mqtt_action

and my devices wont work anymore

    {
      "class": "MqttSwitch",
      "id": "switch_az",
      "name": "Arbeitszimmer",
      "topic": "/switch_az/gpio/2",
      "stateTopic": "/switch_az/Switch_az/Switch",
      "onMessage": "0",
      "offMessage": "1"
    }

@wutu maybe @sweetpi could give you a hint about this issue?

@kenci said:

@wutu Can you help me with this. I got this when i restart pimatic

> (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
> Trace
>     at MqttClient.EventEmitter.addListener (events.js:160:15)
>     at new MqttSensor (/home/pi/pimatic/node_modules/pimatic-mqtt/devices/mqtt-sensor.coffee:17:26)
>     at Object.createCallback (/home/pi/pimatic/node_modules/pimatic-mqtt/mqtt.coffee:84:20)
>     at DeviceManager._loadDevice (/home/pi/pimatic/node_modules/pimatic/lib/devices.coffee:1161:26)
>     at Runner_SQLite3.<anonymous> (/home/pi/pimatic/node_modules/pimatic/lib/devices.coffee:1186:16)
>     at Runner_SQLite3.tryCatcher (/home/pi/pimatic/node_modules/pimatic/node_modules/bluebird/js/main/util.js:26:23)
>     at Promise._settlePromiseFromHandler (/home/pi/pimatic/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:507:31)
>     at Promise._settlePromiseAt (/home/pi/pimatic/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:581:18)
>     at Promise._settlePromises (/home/pi/pimatic/node_modules/pimatic/node_modules/bluebird/js/main/promise.js:697:14)
>     at Async._drainQueue (/home/pi/pimatic/node_modules/pimatic/node_modules/bluebird/js/main/async.js:123:16)
>     at Async._drainQueues (/home/pi/pimatic/node_modules/pimatic/node_modules/bluebird/js/main/async.js:133:10)
>     at Async.drainQueues (/home/pi/pimatic/node_modules/pimatic/node_modules/bluebird/js/main/async.js:15:14)
>     at process._tickDomainCallback (node.js:459:13)

@kenci said:

@wutu maybe @sweetpi could give you a hint about this issue?

“predicates_and_actions” is not packaged as it is not included in “files” as part of package.json. I have filed a pull request which should fix the issue.

@kenci said:

warning: possible EventEmitter memory leak detected.

For background see http://stackoverflow.com/questions/15581978/nodejs-how-to-debug-eventemitter-memory-leak-detected-11-listeners-added

Don’t increase emitter.setMaxListeners() as suggested in the warning message!!! Most likely the issue is the same even listener callback is registered over and over again. It should be easy to find, otherwise the addEventListener() hook may be helpful (see stackoverfow article) to trace the problem.

Big apology for all, that’s what happens when waiting for you girlfriend in underwear

@mwittig thx for pr, and a tip with EventEmitter.

released version 0.8.9

@wutu i am confused. You was waiting for what!?

@kenci When I have free time

@kenci

noooo, don’t ask… i think we should’nt know that…

new version of pimatic-mqtt - 0.8.12
QoS and retain flag
stateTopic for dimmer and buttons device

Could you please add a possibility to add an options object to a rule

like:

if blah then publish mqtt message "cool message" on topic "cool/topic" with options "\{\"retain\":true\}"

@SaxnPaule said in New plugin pimatic-mqtt:

Could you please add a possibility to add an options object to a rule

like:

if blah then publish mqtt message "cool message" on topic "cool/topic" with options "\{\"retain\":true\}"

Yes, sure. I just gotta find a little time.

new version of pimatic-mqtt - 0.8.13

fix division for MqttSensor
add cleanSession and queueQoSZero, remove null msg

@SaxnPaule

new version of pimatic-mqtt - 0.8.15
adding qos and retain flag for action

Nice, thank you.

Unfortunately there seems to be an error in the newest version.

The content of most of my messages have one or more cryptic signs at the end:

{"weight":{"value":"2965", "unit":"g"}}��

My rule:

if every 1 second then publish mqtt message \"\\{\\\"weight\\\":\\{\\\"value\\\":\\\"$loadcell.weight\\\", \\\"unit\\\":\\\"g\\\"\\}\\}\" on topic \"My/Cool/Topic\" retain: true

It doesn’t matter whether qos is set or not.
If I remove the qos parameter from your CoffeeScript file (line 19), everything works as expected.

@mqttclient.publish(strTopic, strMessage, {qos:numQoS, retain:retFlag}) 

@mqttclient.publish(strTopic, strMessage, {retain:retFlag})