Well it would be much cleaner interface, where can i find sources for esp-now and how can i modify it?. In my case i have quite a few peers but those are configured and saved to nvs/flash. So there is no point of keeping such list dynamic /in memory.

why not allow a Send with key as parameter instead of managing peer list. This way user of the API can decide how to manage peers. In my case i could use NVS to store all the peer info as it only need to send messages occasionally.

Then why there is limit of number of nodes, is it to help with broadcast to all nodes? I don't understand why there is limit of peers especially if I don't need it to receive message.

i am building application that will have one master and many salves those will need to synchronize with master after every few min. I read esp-now has 20 peer node max limit, two questions i have 1. Do i have to add node to my peer list to send message? can i just send message without adding to peer...

hi, examples i see uses wifi to discover master/salve. Once I have discovered master and salve and save it to flash (spf) etc Can I turnoff wifi if I don't need it as I only need to use esp-now. considering esp-now using some part of wifi can I turn off some parts off that help me save power and may...

hi, i want to have multiple nodes those need to be in sync with time. I plan to designate one as root node that will sync time with ntp or gps and rest of the nodes will sync time with root.

How can i do it and is esp mesh available in arduino or i have to work with c/c++

Thanks
Sajjad