Page 1 of 1

MQTT complicated in espeasy

Posted: 20 May 2020, 08:22
by TungstenE2
Hi all,

why is setting up MQTT on ESPeasy so complicated compared to Tasmota?

In Tasmota I was done in 2 Min.
In ESPeasy there are several MQTT options in Protocol with several settings.

I choose HomeAssistant MQTT, but even after several attemts I am only able to retrieve data in FHEM as MQTT2_device,
but having same Topic structure as in Tasmota or sending MQTT commands to ESPeasy is just not working for me, after several attempts.

Any advice how to solve this?

Tasmota:
/SmartHome/Steckdosen/%topic%/%prefix%/
/SmartHome/Steckdosen/Sonoff-S20-01/tele/STATE:.* { json2nameValue($EVENT) }

ESPeasy:
/SmartHome/%tskname%/%valname%/
ESP_Easy5:/SmartHome/Klimaanlage/settings/:.* { json2nameValue($EVENT) }

e.g.: Why does ESPeasy set the CID in front of the topic?
Why does ESPeays use different namings? I thought 'topic' is a standard convention in MQTT naming?

Never really paid attention, but now I find 'tskname' for the devices in the list of devices also confusing. Task in List of Devices should be renamed to ID
and %tskname% should be %devicename%.

thx

Re: MQTT complicated in espeasy

Posted: 20 May 2020, 10:29
by grovkillen
I totally agree with the confusion. The naming convention goes way back from the early days of this FW. We will have a look at that in due time.

Re: MQTT complicated in espeasy

Posted: 20 May 2020, 10:47
by TungstenE2

Re: MQTT complicated in espeasy

Posted: 20 May 2020, 10:58
by grovkillen
Thanks