Feature Request: MQTT Broker + Client Implementation on ESP32 about umqttbroker HOT 10 OPEN

Just a clarification. There can be more devices as long as they are not all connected. If you had information only going one way you could have a device connect, send data, then disconnect. And as long as you don't have too many simultaneous events that cause an overload then it should work.

from umqttbroker.

ESP32 is on my agenda, but currently I am really busy with my other life. This porting is mainly an issue for task and TCP conection handling.

The broker will clearly benefit from the additional RAM.

from umqttbroker.

The broker will clearly benefit from the additional RAM.

That was my thought. I also read that the maximum number of sockets for the ESP32 is 16. If that were the case for the uBroker, it would be able to handle everything I could want to connect.

I wish I had the knowledge to move this forward. My abilities are mainly on hardware design.

from umqttbroker.

@RudyFiero by 16 sockets did you mean 16 clients that the broker would be able to handle at a time on ESP32?

from umqttbroker.

Generally speaking, yes. A client uses a socket.

A network socket is an internal endpoint for sending or receiving data within a node on a computer network.

There are trade-offs. If the message sizes are large then memory can become a limiting factor.

from umqttbroker.

Hello Martin and other devs, I need to use your lib on a ESP32 device and I can try to port the lib. Could you give us any clue about what is causing the crash ?

from umqttbroker.

Three things have to be ported: tasking, TCP connections and IP-addresses:

• the lib uses NONOS SDK's task concept (an internal non-preemtive task, that is actiavted by events). This has to be ported to FreeRTOS task - probably a minor issue.
• the lib uses the "espconn"-routines for network interfacing. On the ESP32 this has been changed to sockets. This is a major issue to change.
• On the ESP8266 all addresses are IPv4 32-bit values. A proper ESP32 implementation should be able to handle IPv6, at least it should be aware of the proper types.

from umqttbroker.

Do you think it will be any easier to port it on Olimex ESP32-POE? We can make use of Ethernet PHY instead of WiFi.

from umqttbroker.

Guess, this doesn't make a major difference for the issues mentioned before.

from umqttbroker.

Hi @martin-ger !

Any news for this feature?

Best regards.

from umqttbroker.