CoAP instead of MQTT

[GatCode]

Hello, is there a way to use Tasmota with CoAP instead of MQTT? This would be way more lightweight (UDP, not always connected,…). If not, is this a feature that might be integrated in the future? Thanks!

[sfromis]

MQTT is already really lightweight, having an an open connection is not "heavy", not the extra flows needed for HTTP. In general, chances of big changes depend a lot on "someone" willing to do the work and submit a PR with a feature fitting well with the code base. Much of what Tasmota does is event-based, a better fit for MQTT than for CoAP.

[GatCode]

Yes, it‘s lightweight but not as much as CoAP. An open connection is not ideal if you think about battery operated nodes. Also why is it necessary to use TCP - UDP is good enough. Don‘t get me wrong, I like MQTT but I think Tasmota could benefit from CoAP, especially since CoAP also supports resource observing.

[ascillato]

The question is, how inclusive does Tasmota want to be?

Hi, I understand the hook you want to make, but as Tasmota is not a sponsored project, the real question is Who wants to code it and share it?
Tasmota is open to new Pull Requests and new features. The search you have to make is to find someone willing to spend time working on this feature and sharing it.

Tasmota project has a code of conduct that enforces inclusion and forbids discrimination.

[ascillato]

For new potential users. Buying, configuring and maintaining an extra raspberry pi, even if they are IT personnel. Is an added complication.

Yes, but you can use a cloud MQTT server if you want without the need of extra hardware. The extra hardware is for maintaining all your information locally.

[sfromis]

Since the Berry language available with Tasmota on ESP32 has recently been enhanced with support for UDP, this should make it quite a bit easier for someone convinced of CoAP benefits to start playing around with making it work for them.

[dooblem]

The MQTT broker is a significant Single Point Of Failure. This is wat I don't like about MQTT.
I'm looking for ideas for tasmota to communicate with a shelly, in a reliable way. The shelly includes CoAP (a variant named coiot).
Using MQTT is not an option for me as I don't want to depend on another PC or rpi.
I will probably fall back on using HTTP, even it's an heavy protocol.

[Noschvie]

The MQTT broker is a significant Single Point Of Failure. This is wat I don't like about MQTT.

why not running the MQTT Broker in a Kubernetes Cluster ?
I know it's a overkill ... :-)

[s-hadinger]

There are no plans to support CoAP. You are free to propose a PR to support this protocol. Although I'm not seeing a wide adoption of CoAP within the hobbyist community.

[wjohn007]

@dooblem

I developed the Berry-UdpBroker for the reasons you already mentioned.
Maybe this is a solution or at least an inspiration.

[dooblem]

Hello @wjohn007 ,
Yes it could be. Unfortunately the device I'm working on currently is an esp8266. My understanding is that its less powerfull than the esp32, so Tasmota comes without Berry support with it.
Anyway I will probably fall back using plain HTTP requests.