You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears the WiFi modes require some steps to switch on and off which have to be taken in a very specific order.
It would be nice to have some generic commands/options to switch WiFi mode.
This would make it a lot easier to create some reliable "going to sleep" actions.
Things to consider:
Controlling (and keeping state?) of DHCP server(s) (client for STA and server for AP)
Keeping last known mode (AP/STA/AP+STA)
Keeping last known connection parameters (BSSID/channel) to allow quick reconnect
Calling some callback function for cleaning up existing connections.
Flushing data in buffers.
Considering some timeout to flush buffers
Where to keep these stored settings (RTC memory?)
As a counter part operation, it would be nice to have the WiFi.mode(WIFI_RESUME) option.
This would allow to collect the stored values (or initiate some default steps when those are not available or corrupt) and resume WiFi operations.
Using this can make the ESP a lot more energy efficient since you only need to have WiFi connection when you need to send data.
Great for battery operated nodes or nodes where heat may quickly become an issue.
Also there is this FW api we don't so far know/use (not present in official user_interface.h but described in latest api reference datasheet).
These symbols are present in our current firmware.
They will be useful when waking up from WIFI_SHUTDOWN.
The text was updated successfully, but these errors were encountered:
As discussed here: #6172 (comment)
It appears the WiFi modes require some steps to switch on and off which have to be taken in a very specific order.
It would be nice to have some generic commands/options to switch WiFi mode.
This would make it a lot easier to create some reliable "going to sleep" actions.
Things to consider:
As a counter part operation, it would be nice to have the
WiFi.mode(WIFI_RESUME)
option.This would allow to collect the stored values (or initiate some default steps when those are not available or corrupt) and resume WiFi operations.
Using this can make the ESP a lot more energy efficient since you only need to have WiFi connection when you need to send data.
Great for battery operated nodes or nodes where heat may quickly become an issue.
As noted by @d-a-v
The text was updated successfully, but these errors were encountered: