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
When executed command WIFI.STA from terminal when the wifi mode is already in STA, the esp8266 module goes offline and there is no trigger that can bring the chip again online except the hard boot. I am not sure if some kind of checks needs to be performed before executing WIFI.STA.
Another issue is with the command WIFI.OFF, I am not sure why someone wants to make WIFI.OFF, because once the command is executed there is no turning back, the esp8266 module become offline and there is no way we can perform WIFI.ON.
Steps to reproduce
When the module is in STA mode execute the WIFI.STA command from the terminal.
Build tools used
No response
Any relevant log output (when available)
No response
Decoded stack trace (when available)
No response
The text was updated successfully, but these errors were encountered:
Both are intentional. WIFI.STA meant to mimic WIFI.AP, but it is true that the is no external thing to change it unlike the AP with the button action.
Same goes for WIFI.OFF - it is meant to turn modem off,hence the name. I am not sure what kind of check would you propose to delay / stop action from happening?
Device
ESP8266
Version
1.16.0-dev
Bug description
Wi-Fi module WIFI.OFF & WIFI.STA command
When executed command WIFI.STA from terminal when the wifi mode is already in STA, the esp8266 module goes offline and there is no trigger that can bring the chip again online except the hard boot. I am not sure if some kind of checks needs to be performed before executing WIFI.STA.
Another issue is with the command WIFI.OFF, I am not sure why someone wants to make WIFI.OFF, because once the command is executed there is no turning back, the esp8266 module become offline and there is no way we can perform WIFI.ON.
Steps to reproduce
When the module is in STA mode execute the WIFI.STA command from the terminal.
Build tools used
No response
Any relevant log output (when available)
No response
Decoded stack trace (when available)
No response
The text was updated successfully, but these errors were encountered: