New plugin pimatic-mqtt

---

@thrusty said in New plugin pimatic-mqtt:

Can I send mqtt-commands to ws2812 control from pimatic to a ESPEasy-device?

Yes. I use 8x ws2812 ledbar with ESPEasy like notification device.

For example my rule for low coal level warning:

    {
      "id": "coal-low-level-defcon-2",
      "name": "Coal Low Level Defcon 2",
      "rule": "when every 10 seconds and if $coal-level-simple-truncated-mean.coal-level-simple-truncated-mean > 50 and if $coal-level-simple-truncated-mean.coal-level-simple-truncated-mean < 65 then publish mqtt message \"neopixel,8,40,0,40\" on topic \"mh/gf/lab/wd1mini-9/cmd\" and after 2 seconds publish mqtt message \"neopixel,8,0,0,0\" on topic \"mh/gf/lab/wd1mini-9/cmd\"",
      "active": true,
      "logging": false
    }

@wutu
Thats sounds very nice.
In the moment I have only sonoffs with tasmota, that is also easy to use.
But I will test ESPEasy now.
Do you use a device from pimatic-mqtt-plugin?

I will also use ws2812 ledbar for indication any status.

@thrusty said in New plugin pimatic-mqtt:

Do you use a device from pimatic-mqtt-plugin?

I use rules only, but you can use switch, dimmer etc.

MqttSwitch for all leds on strip

    {
      "topic": "mh/gf/lab/wd1mini-9/cmd",
      "id": "mqtt-switch",
      "name": "MQTT Switch",
      "class": "MqttSwitch",
      "onMessage": "neopixelall,255,255,255",
      "offMessage": "neopixelall,0,0,0"
    }

Dimmer for second LED

    {
      "topic": "mh/gf/lab/wd1mini-9/cmd",
      "id": "mqtt-slider",
      "name": "MQTT Slider",
      "class": "MqttDimmer",
      "resolution": 256,
      "message": "neopixel,2,value,value,value"
    }

@wutu thanks for sharing.
Now I have espeasy on the nodemcu. mqtt is running on the nodemcu. Now I will see the way to send and receive mqtt notifications on pimatic. 😊
On tasmota is the way easy at a internal console.
But I will read and test it.

Hi wutu,
can you remember to an error we discussed in the near past:

Unhandled rejection Error: Expected variable sonnensensor.temp_high to have a numeric value.
    at /home/pi/pimatic-app/node_modules/pimatic/lib/variables-ast-builder.coffee:111:17
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:396:17)

Is there a chance that you will handle it?

Hey!

Wonderful plugin!

I have a question regarding using data from a sensor device in a rule.
I’ve set up a sensor (mqtt_temp) which grabs data from topic “Temp/Bad/ctrl” (bad_ctrl). I’d like to have a rule, that triggers, whenever the value changes. Only operators that i can see / that work are “equals, =>, >, etc…”.
Is there a way to react to ANY change, not matter what it is?

Like
When bad_ctrl of mqtt_temp changes then do …

Thanks in advance,
Greetings, Chris

This might work.
{variable} changes or updated

When
$variable changes
Then
bla bla

@incmve that was my first approach, but as far as i understand, there’s no variable provided by this device … at least there’s none suggested when creating a new rule …

Hi all.
@sirhc Thx, I’m glad you like the plugin.

@sirhc said in New plugin pimatic-mqtt:

that was my first approach, but as far as i understand, there’s no variable provided by this device … at least there’s none suggested when creating a new rule …

This is very strange. Can you send a config device?

@OrTiN Can you please create issues? I do not remember it exactly.

@wutu

 { "attributes": [
    {
      "name": "badctrl",
      "topic": "Temperatur/Bad/ctrl",
      "type": "string",
      "messageMap": {}
    }
  ],
  "xAttributeOptions": [],
  "id": "mqtt_temp",
  "name": "Thermostat Temp",
  "class": "MqttSensor"
}, `

I’ve used the graphical frontend to create. If i send messages to topic “Temperatur/Bad/ctrl” the device gets updated and displays the corresponding value.

@sirhc This rule works for me.

    {
      "id": "variable-change-test",
      "name": "variable change test",
      "rule": "when $mqtt_temp.badctrl changes then log \"the variable has been changed\"",
      "active": true,
      "logging": true
    }

@wutu i deleted the device and set it up freshly. Even if the config section now absolutely is the same for this device, now i get “$mqtt_temp.badctrl” suggested when trying to create that rule …
I don’t get the error, but now it seems to work. Thanks a lot

@wutu
Thanks, your tips has helped me. However, unfortunately, I still lack something around this is aimed at reaching.
Like it looks the required Plugin does not exist in the proficient product. Which Plugin do I need for it? How can I install it?
I mean with it Plugin for espeasy and how to install it?

@thrusty said in New plugin pimatic-mqtt:

I mean with it Plugin for espeasy and how to install it?

Hi, One option is MQTT. Although older, but mostly valid: https://forum.pimatic.org/topic/1367/espeasy-with-pimatic-over-mqtt

@wutu
Hello, I’m afraid you misunderstood me. I mean the plugin for ESPEasy. So in ESPEasy. If I define a device as Neopixel Basic, then I cannot choose a controller for it. This option is only available with Neopixel Candel.

@thrusty said in New plugin pimatic-mqtt:

If I define a device as Neopixel Basic, then I cannot choose a controller for it. This option is only available with Neopixel Candel.

Which ESPEasy version do you use? Neopixel works well in version 2.x.x (mega branch).

@wutu Hello, I have downloaded this firmware version: Build: 20000 - Mega

As already written I can select the controller under the Neopixel Candle Plugin.

If I want to make the settings for the Neopixel Basic Plugin, I don’t have the possibility to choose a controller.

No possibility to select the controller.

Is there anything else to look out for?

@thrusty said in New plugin pimatic-mqtt:

If I want to make the settings for the Neopixel Basic Plugin, I don’t have the possibility to choose a controller.

This device did not send any data to the controller. It’s not a sensor. Only through the controller listens to the commands.

Oh, I didn’t know that.

What should the topic look like then?
Maybe like this: /ESP_Easy/neo/

And what next?
Like this for example?

{
      "brokerId": "192.168.178.22",
      "topic": "/ESP_Easy/neo/",
      "onMessage": "neopixelall,200,200,200",
      "offMessage": "neopixelall,0,0,0",
      "echo": {
        "additionalNames": []
      },

@thrusty said in New plugin pimatic-mqtt:

And what next?

You can try with command:
mosquitto_pub -t /ESP_Easy/neo -m 'neopixelall,10,10,10'

Like this for example?

Yep