Sorry for not being clear

I want a way to give a smartphone authorization to interact with the mesh network, so that unauthorized devices wont be able to do anything

And I must be able to revoke authorization too

Is there a recomended way to implement authorization for requests to the mesh devices?

Anyone connected to the same wifi network can discover the root node, query mesh information and start sending packets to the nodes

Ok, just found out that I have to name the files as *.cpp if I want to use c++ stuff. This seems obvious, but I used to code on esp-idf on PlatformIO and I could use c++ libraries and language features on .c files. I thought esp-idf build system compiled everything as c++ by default. Also, it's woth...

Just to make sure it's not an error on my project, I did a copy of the development_kit/light sample project and simply added a #include <map> to the light_example.c file, and then make -j4 flash, I got this output: $ make -j4 flash Toolchain path: /opt/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc Toolc...

I'm trying to compile a code that uses stl <map> but I'm getting this error:
fatal error: map: No such file or directory

I'm using latest esp-mdf

Will code from unused components be present on the final image?
For me it's ok if they're compiled but do not consume space on device.

Also, is this a good architecture? Would be better to have actual separated projects?

Does esp mesh support a leaf node to stream data to the internet?

Example: a leaf node to transmit live audio to a smartphone via internet?

My project will consist in a familly of many different device types for home automation based on esp mesh My idea is to have a single project where main app code will do the common things (set up esp mesh, etc), and the functionality for specific device type will be in components. Is this a good way...

Is there any sample code showing how to interact with mesh devices from outside?

I'm newbie to esp32, but what you want is teoritically possible if (1) you could have low level access to android wifi interface and (2) you mimic esp-mesh protocol.

I don't think (1) is possible and (2) seems to be undocumented