Please help to raise the issue on github with all relevant details.

Hi,
Currently, we do not support FTM with MESH. However, given MESH is dependent on SoftAP + STA functionality we may consider adding it for MESH. For your use-case though, are you assuming multi-hop support ("to measure the distance between the smart watch and each node in the MESH network") ?

Hi Axelin, v3.x never supported TLS v1.2. Regarding disabling TLS v1.2, we faced the same choices as yours when we encountered the interop issues, but we favoured keeping TLS v1.2 disabled to maintain the behaviour consistent with v3.3. It is common for us to try new features on branches that are no...

Hi Axelin,
We witnessed a few interoperability issues when TLS 1.2 was enabled, so we kept it disable by default. We are in process of fixing those issues and will soon enable this by default.

Hi SomeCallMeTim,
Apologies for late reply! Yes, we will have support for both client and SoftAP. This is work in progress and we intend to finish this in 2 months duration from now.

Hi xanthome, The high RTT is mostly because of WiFi power-save. You can try measuring the RTT by either disabling power save or sending/receiving UDP data at faster rate (timegap between two packets< 50ms) so that wifi does not go into power-save. The power-save mechanism for WiFi can be disabled by...

Thank you for raising the issue and apologies for the late response! We acknowledge that the issue exists and we will fix it soon. For better response, you can raise such issues on github in future.

Glad that it is working for you! Feel free to provide any feedback.

@Oromis, Thank you for trying this feature! However, I am unable to reproduce the issue on 3.1.1. Can you check- 1) It is a clean build after enabling the macro (CONFIG_MP_BLOB_SUPPORT). 2) There is enough space on NVS partition (There should be 1 sector empty even after accounting for all the data ...