ESPeasy MQTT import long topic

[kazmid]

Good morning everyone,
Thank you for the opportunity to join the community.

I am trying to use ESPEasy with SUPLA devices.

What is SUPLA?
Polish project supported by the ZAMEL company that produces modules for roller shutters, gates, lighting, energy meters, etc.
https://github.com/SUPLA

Unfortunately, there is no connector for Supla in ESPEasy.

I want to use ESPEasy as a Daschboard https://github.com/chromoxdor/easyfetch Many thanks to the author great job.

The supla topic is long and unfortunately it cannot be used in the ESPEasy MQTT import plugin https://espeasy.readthedocs.io/en/lates ... /P037.html. Is there any option to enter longer topics?

Example

Code: Select all

supla/d53ad63a3b9541e364d7d0e3178dc6f5/devices/23624/channels/76321/state

Thank you in advance for your help

[Ath]

Is it correct that all your topics have the same prefix, this "supla/d53ad63a3b9541e364d7d0e3178dc6f5/" part?

In that case you can put that in the 'Prefix for all topics' input field, and put the rest of the topic, "devices/23624/channels/76321/state" in the MQTT Topic fields for the channels you want to receive.

[kazmid]

Hi Ath,

Is it correct that all your topics have the same prefix, this "supla/d53ad63a3b9541e364d7d0e3178dc6f5/" part?

Yes, even if they will be as a prefix to topic

Code: Select all

supla/f63ed63e3b9541a363d7d0e3178dc7d3/devices/23624/channels/76329/state/humidity

It's too long

there is no space for 4 letters

[Ath]

Hmm, and I assume there is no way of shortening those topics, possibly by using some kind of alias?

The topics have been limited in size, because of limited resources in these small controllers.
I have been working on extending the storage space reserved for these so called Custom settings, and I'll see if this can be applied to the MQTT Import plugin too.

[kazmid]

Unfortunately, the SUPLA manufacturer does not allow you to change the topic in the module configuration.

It would be great if we could increase the number of characters in these fields.

Unless there is some other way to import data and actions on entities from another provider

[TD-er]

You could use some wildcards in your topic when subscribing it it.
Just assuming they have set the access control such that you can only read topics based on your user ID?

So the subscribe topic could be something like this:

Code: Select all

supla/#/devices/23624/channels/76329/state/humidity

[kazmid]

TD-er
Thanks for the tip. I'll check tomorrow and let you know if it helped.

[kazmid]

Hi All,
It was configured as follows:

Code: Select all

Prefix for all topics: supla/f65ad63e3b9741a363d5d0e3178dc7d3/

Code: Select all

MQTT Topic 1: devices/22845/channels/73274/set/on

Mapping

Code: Select all

Name = false Value = 0

Code: Select all

Name = true Value = 1

How to make a switch out of it?

Unfortunately using # doesn't work.

[Ath]

In Tools/Advanced the Rules should be enabled (first checkbox)
Then, in rules, you can add an event handler for the taskname#value1 to do anything with the mapped value, like:

Code: Select all

on MQTTImport#Value1 do
  if %eventvalue1%=0
    // Handle false state, f.e. switch a GPIO or (re)set a PWM output
  else
    // Handle true state, f.e. switch a GPIO or (re)set a PWM output
  endif
endon

If only a GPIO state has to be changed, the you can use the eventvalue directly:

Code: Select all

on MQTTImport#Value1 do
  GPIO,4,%eventvalue1% // To invert, change %eventvalue1% to !%eventvalue1%
endon

[kazmid]

Hi Ath,
Ok, I will check.