increasing the supervision timeout helps when wifi is stable with wifi powersave set to WIFI_PS_MIN_MODEM

I am working on a project where we are using an Esp32-S3
We have a Mqtt connection and a Ble Connection running constantly

After setting the Wifi powersaving settings to WIFI_PS_MIN_MODEM the wifi connection seems stable over night.
The Nimble Ble connection drops about 9 times over night, with a ...

Problems disappear when using a matter sample from the esp-matter repository.

The esp-matter docker build image"espressif/esp-matter:latest" is also much more convenient to build the projects, although it is much larger than the connectedhomeip build image "ghcr.io/project-chip/chip-build-esp32:35 ...

Just adding some more information. I enabled more logging for OpenThread but I am still not getting any hints about the crash.

Building with Connectedhomeip commit https://github.com/project-chip/connectedhomeip/commit/209c90bb55b3ffe689a9b91e506e269119285a61

Building the example project examples ...

Hi there,

I am trying to enable OpenThread in the Matter-bridge build example. When I disable OpenThread the Matter sample works without issue.
However when I do that, the system crashes and I do not get any hints to why it is happening.
The backtrace seem to be corrupted and the LoadProhibited ...

It seems I'm not the only one.
There is a feature request on github, see: https://github.com/espressif/esp-idf/issues/10766

There are soo many mqtt clients that work with the esp32 and esp-idf. That isn't a real problem.
A MQTT-Broker implementation is something that is hard to find. Especially for esp-idf, I've only found one

I need to accept MQTT connections from devices on the localnetwork and bridge that to our ...

Hello everyone,

It's been some time since I last visited this forum. Glad to be back =)

Currently, I'm diving into a new project centered around ESP32, and I find myself in need of an MQTT-Broker that works with esp-idf. However, I am unable to find a compatible option.

If anyone knows of a ...

It has to do with the bootmode of the board. See:
https://github.com/espressif/esptool/wiki/ESP32-Boot-Mode-Selection#automatic-bootloader
esptool.py can automatically enter the bootloader on many boards by using the RTS and DTR modem status lines to toggle GPIO0 and EN automatically ...

probably that data is encrypted in blocks of 16bytes. When the warning comes up it is encrypting something that is not a multiple of 16bytes, here you have a remainder of 4 bytes. this is why a random padding is added with a length of 12 bytes ( 4bytes data + 12 bytes padding = 1 block of 16bytes).