Pimatic not receives MQTT data from ESP8266 running Tasmota

---

Hi

so I am working since a couple of month with Pimatic to run a terrarium. My new idea was to built an ESP8266-based weather station. On the later I installed Tasmota, that is sending MQTT messages to the Pi. After some connection problems in the beginning, it seems that it is actually really sending to Mosquitto running on the pi as MQTT-Broker.

However, my problem is now that it seems as I would have an error in Pimatic - as it is not showing the data (Temperature and Humidity for the beginning.

In the Tasmota Console it looks like this:
18:11:15 MQT: tele/Wetterstation/STATE = {“Time”:“2020-11-01T18:11:15”,“Uptime”:“0T00:42:09”,“UptimeSec”:2529,“Heap”:25,“SleepMode”:“Dynamic”,“Sleep”:50,“LoadAvg”:19,“MqttCount”:1,“POWER”:“ON”,“Wifi”:{“AP”:1,“SSId”:“CXNK006666C7”,“BSSId”:“48:77:46:21:BC:13”,“Channel”:11,“RSSI”:64,“Signal”:-68,“LinkCount”:1,“Downtime”:“0T00:00:03”}}
18:11:15 MQT: tele/Wetterstation/SENSOR = {“Time”:“2020-11-01T18:11:15”,“AM2301”:{“Temperature”:22.9,“Humidity”:59.2,“DewPoint”:14.5},“TempUnit”:“C”}

In the Pimatic config I added this:
{
“brokerId”: “192.168.1.68”,
“attributes”: [
{
“name”: “AM2301.Temperature”,
“topic”: “tele/Wetterstation/SENSOR”,
“type”: “string”,
“messageMap”: {},
“unit”: “C”
},
{
“name”: “AM2301.Humidity”,
“topic”: “tele/Wetterstation/SENSOR”,
“type”: “string”,
“unit”: “%”,
“messageMap”: {}
}
],
“xAttributeOptions”: [],
“id”: “wetterstation”,
“name”: “Wetterstation”,
“class”: “MqttSensor”
}

Is there anybody of you finding a mistake?
best
stefan

Hi, what are the mqtt plugin settings?

Hi bertreb,

the plugin settings are as followed:

and maybe there is the mistake - I do have set by accident a password, aren’t I?

{
“plugin”: “mqtt”,
“active”: true,
“brokers”: [
{
“brokerId”: “192.168.1.68”,
“host”: “168.192.1.68”,
“port”: 1883,
“password”: “default”,
“username”: “default”
}
]

These settings can work. Mostly for the brokerId a name is used, but this string can work also.
If you need a username/password depends on how you configured your mqtt broker?

@stefan85 So I just deleted the two lines with password an username but nothing changed…

these are the settings from mosquitto.conf: (wouldn’t it be a good idea to set a password there?)

user mosquitto
max_queued_messages 200
message_size_limit 0
allow_zero_length_clientid true
allow_duplicate_messages false

listener 1883
autosave_interval 900
autosave_on_changes false
persistence true
persistence_file mosquitto.db
allow_anonymous true

@stefan85

so thanks to your help: there is at least one mistake - user mosquitto … I will change this in Pimatic … and then have a look

Try leaving out username and password (deselect the two options).
Edit: when there a username, there’s probably also as password
What did you use in Tasmota for the mqtt broker parameters? you can use the same in Pimatic

@bertreb maybe there is a password - however I haven’t set any this afternoon and I couldn’t find anything about a standard password. I will try to set one… because just adding user doesn’t changed anything…

Edit: I deleted from the mosquitto config file the username and also from the configuration of the Pimatic plugin.
however doesn’t change anything…

also I searched through the folders and couldn’t find something about a password… or password file.

Its not complex to set a username / password.
In commandline mode the command: sudo nano /etc/mosquitto/mosquitto.conf and replace :

allow_anonymous true

by

password_file /etc/mosquitto/passwd
allow_anonymous false

Save the file (^O) and exit nano (^X)
create the passwd file with the command:

mosquitto_passwd -c /etc/mosquitto/passwd username

The username can be changed to what you want
You will be asked for a password
Restart mosquitto with: service mosquitto restart

So i have set a password.
And by this I tested the procedure a bit… After setting the password both - the tamota and Pimatic produced so errors - the access was denied…
After adding the username and password the errors are gone…

AND while writing these lines the temperature appeared…

Thank you very much!!!

btw. do you know (by chance;)) how to control from Pimatic via Tasmota one of these standard relais-modules like for example this one

You control these kind of modules via gpio.
The pimatic-gpio plugin can do this.
If you want to use mqtt you need to put for example arduino in between. The arduino does the relay control and the interface to mqtt.
Thats a lot more work with the same result. The only reason could be if the relay board is not close enough to the rpi to use the gpio communication.

I allread control some relais boards directly from the rpi via gpios… however the weather station is installed at a small hut in our garden and the idea was to control the light and maybe a small radiator to protect two plants when it might become very cold in a winters night.
I thought, that the gpios of the esp8266 boards can also be turned up and down?
like shown here https://i1.wp.com/randomnerdtutorials.com/wp-content/uploads/2019/05/ESP8266-ESP-12E-chip-pinout-gpio-pin.png?ssl=1

Yes, you can use an esp8266 with gpio control and a mqtt interface. If you use the arduino mqtt client example, you can add easily gpio control

If found that I can in the configuration just add a relay and thereby turn on and off an led. I used an LED instead since the principal is the same.
The LED is also controllable by http://<ip>/cm?cmnd=Power%20On or …Off
Now I just need to find out what I need to do in Pimatic - but this might also not be so difficult …
Lets try

If thats possible you can use pimatic-shell-execute and use a shell-switch device.
You can put http… requests in de commands for on and off

so in the end it was quit easy… I did it this way:

 { "brokerId": "IP...",
  "topic": "cmnd/Wetterstation/POWER1",
  "id": "wetterstationledschalter",
  "name": "WetterstationLEDSchalter",
  "class": "MqttSwitch",
  "onMessage": "On",
  "offMessage": "Off"
}

afterwards I pined a switch to the Pimatic page of interest and now I am able to switch on and off… just I like to receive something like a “yes it has successfully turned on” message …

Ok thats even better.