Time to execute esp_wifi_scan_start about esp32-wifi-manager

[alexanderturner]

Digging a bit deeper into this to force the IDF functions event-drivenness with a new arg in wifi_manager_event_handler and passing false to the blocking attribute. It appears to be an issue with esp-idf blocking the thread when running the scan. Perhaps there should be a timer arg for the wifi scan instead of it being called every time jquery call it.

[tonyp7]

Helo Alex,

You can indeed set it to false but this brings a whole lot of new issues with thread synchronization. However, it is true blocking the thread is not ideal.

The whole architecture of the manager is hindered by the events being only triggered by a bitfield.

I am currently re-writing the app so that it uses a RTOS queue as primary thread sync instead. This a major rewrite so bear with me; I do not wish to commit broken code to the repository for now!

[tonyp7]

This is fixed in branch 2.0

[tonyp7]

Fixed in latest master trunk -- scans are now non blocking

[alexanderturner]

Thanks for this Tony! I should have jumped in with a PR sooner but awesome to see this being actively maintained. I had set the blocking field to false and actioned the update task on in the event handler but whilst it's now 'non blocking' it's still blocking the thread for similar time when it's executing the scan (which is pretty frequently when the jquery script is running).

I'm working on project which could benefit from RTOS queues - are you keeping that effort in a working branch?

[tonyp7]

I merged my dev branch into the master so you can simply get the master :)

Queue process starts here:

esp32-wifi-manager/wifi_manager/main/wifi_manager.c

Line 730 in 1a710da

xStatus = xQueueReceive( wifi_manager_queue, &msg, portMAX_DELAY );

[alexanderturner]

Ah awesome :) Thanks. Would be awesome to have a build status for master :)