ESPEasy with Pimatic over MQTT

---

Here, a simple instruction.

Download and flash ESPEasy. I use github version. Use Arduino IDE 1.6.5 and ESP8266 core 2.0.0. For 512K and 1M version set SPIFFS to 64K. For 4M version set 3M.

Configure ESPEasy:

Check the settings template, sometimes when you change the protocol disappears. Tools > Advanced.

For Actuators (Output) you do not need to configure device on ESP Just call topic /sysname/GPIO/0 with payload 1 or 1.00.

Install Mosquitto broker.
For Deb wheezy:

wget http://repo.mosquitto.org/debian/mosquitto-repo.gpg.key
sudo apt-key add mosquitto-repo.gpg.key
cd /etc/apt/sources.list.d/
sudo wget http://repo.mosquitto.org/debian/mosquitto-wheezy.list
apt-get update
apt-get install mosquitto
sudo /etc/init.d/mosquitto start

Install plug-in pimatic-mqtt
In your plugins section of pimatic’s config.json file add:

{
  "plugin": "mqtt"
}

Add device to devices section:

    {
      "class": "MqttSensor",
      "id": "esp01",
      "name": "ESP-01",
      "mqtturl": "mqtt://localhost",
      "attributes": [
        {
          "name": "dht-11-temperature",
          "topic": "/esp01/dht11/temperature",
          "type": "number",
          "unit": "°C",
          "acronym": "DHT-11-Temperature"
        },
        {
          "name": "dht-11-humidity",
          "topic": "/esp01/dht11/humidity",
          "type": "number",
          "unit": "%",
          "acronym": "DHT-11-Humidity"
        },
        {
          "name": "ds-temperature",
          "topic": "/esp01/ds18b20/temperature",
          "type": "number",
          "unit": "°C",
          "acronym": "DS-Temperature"
        },
        {
          "name": "uptime",
          "topic": "/esp01/system/uptime",
          "type": "number",
          "unit": "minute",
          "acronym": "Uptime"
        },
        {
          "name": "freeram",
          "topic": "/esp01/system/freeram",
          "type": "number",
          "unit": "B",
          "acronym": "FreeRAM"
        }
      ]
    }

And here’s the result:

For testing i use MQTT.fx

@wutu
WOW! Thx for this interesting ESP devlopment!!
Really nice, seeing the community working on such great projects!
Keep it on!!

Good news indeed! Looks great, thanks for the efforts, I guess a lot of people would like to use this

I would also like to highlight the script user @kenci.
As he writes on github: "You could use a script which connects to the websocket of pimatic. If anything is received, publish it to MQTT. I wrote a script for this behavior."
Good job

Modified code for blocking(through device id) sending the topic drawn from Broker over pimatic-mqtt-simple.

socket.on('deviceAttributeChanged', function(attrEvent) {
  _name = attrEvent.attributeName.toLowerCase().replace(" ", "_");
  _id = attrEvent.deviceId.toLowerCase();
  // Here is a primitive filter through Device id
  if(!(_id == 'mosquitto' || _id == 'esp01')) {
    _value = attrEvent.value.toString();
    mqttClient.publish('homematic/'+_id+'/'+_name, _value);
  }
});

@leader21 I did it not develop, for now. it’s just configuration.

@wutu Normally you should send all changed attributes to the MQTT server. Filtering should be done when you subscribe to. So, create a client which connects to the MQTT server and subscribe to for example homematic/esp01/#

On this client you got only devices named esp01 which attributes has changed. On homematic/# you receive all changed attributes from pimatic. So, you should be flexible to choose what you need.

@kenci Yes , I understand it .
But in the case subscribing to $SYS/broker/clients/connected (etc), pimatic unnecessary (by me) reporting back to the broker.

The same happens if pimatic subscribe to topic /esp01/system/freeram. Your script then sends the data to the topic homematic/esp01/freeram back to the broker (unnecessary traffic).

But with MQTT it’s just getting started, so it is possible that I missed something.

@wutu Sorry but i don’t understand you. You have to setup a server, for example Mosquitto. So my script connects to the websocket of pimatic a listen for changed attribute of all devices. If you turn on your lamp, my script receives this event and will publish it to MQTT server in this format: homematic(or whateveryouwant)/lamp/state

In my script all whitespaces are replaced by underscore, because i have used whitespaces for device names. All names have been converted to lowercase, because of simplicity.

Now you want to listen only for events of your lamp then subscribe to your MQTT with following: homematic/lamp/state or subscribe to all presence events with this homematic/+/presence or subscribe to all state events with this homematic/+/state. With the last you get all events of devices that supports the state attribute. I hope you understand me

hello,

i have here a esp, how must i connect this device with the arduino and how can i flash them?

@kenci I’m talking about cases where subscribing via pimatic-mqtt-simple to the topic /esp01/system/freeram.

Subsequently, it looks like this:

esp01 send: /esp01/system/freeram->25415.00
pimatic recieve this data over pimatic-mqqt-simple
and you script sending: homematic/esp01/freeram->25415.00

I find it somewhat illogical. Toipc homematic/esp01/freeram. This topic is unnecessary, by me.

@noxx You do not need Arduino, only ESP and Pimatic (with pimatic-mqqt-simple)!
How to flash ESPEasy to ESP can be found here.

Arduino is the word here because it is used Arduino IDE for flash ESP8266 board.

but, for flashing must i connect the ESP01 with a Arduino, in my case, with a UNO, or?
or must i connect the ESP with the Raspberry? or need i a FTDI FT232-Seriell-USB?

You need a FTDI cable (USB to serial)

ok, i havent it…

must buy one

And it must be a 3.3V version or switchable 5V/3.3V.

Or over TX/RX. But without logic level converter I would not go into it

You can use an arduino to flash the ESP, havent tested it with a UNO http://yaab-arduino.blogspot.nl/2015/12/flashing-esp8266-firmware-arduino.html
A nano can be used as well but the easiest wasy is an FTDI cable

hello

what means this error from the arduino v1.6.7 ?

exit status 1
no matching function for call to ‘PubSubClient::PubSubClient(const char [1])’

Use 1.6.5

ok, thx…

1.6.5 seems ok, but Arduino dont upload the complete ino file.
I guess that’s at 90 percent circuit.
Blue LED stopps blinking.

Arduino software shows
upload xxxx …
…

i have a ESP01 Black Edition with 1MB.

What error do you get?

@ noxx

try that: http://www.esp8266.nu/index.php/Tutorial_ESPEasy_Firmware_Upload

i play a little bit with espeasy, but i get now values…

{
  "class": "MqttSimpleSensor",
  "id": "espeasy1",
  "name": "ESP01_01",
  "mqtturl": "mqtt://192.168.1.81",
  "attributes": [
    {
      "name": "uptime",
      "topic": "/espeasy1/system/esp01uptime",
      "type": "number",
      "unit": "minute",
      "acronym": "Uptime"
    },
    {
      "name": "freeram",
      "topic": "/espeasy1/system/esp01ram",
      "type": "number",
      "unit": "B",
      "acronym": "FreeRAM"
    }
  ]
}

ESPeasy:
http://www.bilder-upload.eu/show.php?file=8ecdc2-1455990079.png