ESP8266 and ESP32 WiFi capabilities in IOT Protocols - Step-by-Step Execution

Process Flow - ESP8266 and ESP32 WiFi capabilities

Power On ESP Module

↓

Initialize WiFi Driver

↓

Set WiFi Mode: Station/AP/Both

↓

Scan for Networks (Station Mode)

↓

Connect to WiFi Network (Station Mode)

↓

Start Access Point (AP Mode)

↓

Obtain IP Address

↓

Send/Receive Data over WiFi

↓

Disconnect or Power Off

This flow shows how ESP8266/ESP32 modules power on, initialize WiFi, set mode, connect or create networks, and communicate.

Execution Sample

IOT Protocols

WiFi.mode(WIFI_STA);
WiFi.begin("MySSID", "MyPassword");
while (WiFi.status() != WL_CONNECTED) {
  delay(500);
}
Serial.println(WiFi.localIP());

This code sets ESP to station mode, connects to WiFi, waits until connected, then prints the IP address.

Process Table

Step	Action	WiFi Mode	Connection Status	IP Address	Output
1	Set WiFi mode to Station	Station	Disconnected	0.0.0.0
2	Start connection to 'MySSID'	Station	Connecting	0.0.0.0
3	Wait 500ms and check status	Station	Connecting	0.0.0.0
4	Wait 500ms and check status	Station	Connected	192.168.1.100
5	Print local IP address	Station	Connected	192.168.1.100	192.168.1.100
6	End of process	Station	Connected	192.168.1.100

💡 WiFi.status() returns WL_CONNECTED, so loop exits and IP is printed.

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
WiFi Mode	Undefined	Station	Station	Station
Connection Status	Disconnected	Connecting	Connected	Connected
IP Address	0.0.0.0	0.0.0.0	192.168.1.100	192.168.1.100

Key Moments - 3 Insights

Why does the IP address stay 0.0.0.0 during connection attempts?

Because the ESP module has not yet connected to the WiFi network, so it has not obtained an IP address. See execution_table steps 2 and 3.

What happens if WiFi.status() never returns WL_CONNECTED?

The loop will keep waiting indefinitely, so the program will not proceed to print the IP. This is why checking connection status is important.

Can ESP modules act as both WiFi station and access point at the same time?

Yes, ESP32 and ESP8266 support dual mode (Station + AP). This is set by WiFi.mode(WIFI_AP_STA).

Visual Quiz - 3 Questions

Look at the execution_table at step 4. What is the connection status?

A Disconnected

B Connected

C Connecting

D Failed

💡 Hint

Check the 'Connection Status' column at step 4 in the execution_table.

At which step does the ESP module obtain its IP address?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'IP Address' column in the execution_table to see when it changes from 0.0.0.0.

If WiFi.mode was set to WIFI_AP instead of WIFI_STA, what would change in the execution?

A The module would connect to an existing WiFi network.

B The module would do both connect and create networks simultaneously.

C The module would create its own WiFi network for others to join.

D The module would disable WiFi.

💡 Hint

Recall the meaning of WIFI_AP mode from the concept_flow section.

Concept Snapshot

ESP8266/ESP32 WiFi flow:
1. Power on and initialize WiFi driver
2. Set mode: Station (connect), AP (create), or both
3. Connect to WiFi or start AP
4. Wait for connection and get IP
5. Use WiFi for data
Use WiFi.status() to check connection state.

Full Transcript

This visual execution shows how ESP8266 and ESP32 modules handle WiFi. First, the module powers on and initializes the WiFi driver. Then, it sets the WiFi mode to Station to connect to an existing network. The code attempts to connect to the network named 'MySSID' with a password. It waits in a loop checking the connection status every 500 milliseconds. Initially, the connection status is 'Disconnected' and the IP address is 0.0.0.0. After some time, the status changes to 'Connected' and the module obtains an IP address, for example, 192.168.1.100. Finally, the IP address is printed. The variable tracker shows how WiFi mode, connection status, and IP address change step by step. Key moments clarify why the IP is initially zero and what happens if connection never succeeds. The quiz tests understanding of connection status, IP assignment timing, and WiFi modes. This step-by-step trace helps beginners see how ESP modules manage WiFi connections.

Practice

1. What is the main purpose of the WiFi.begin() function on ESP8266 and ESP32 devices?

easy

A. To start connecting the device to a WiFi network

B. To disconnect the device from the WiFi network

C. To check the current WiFi connection status

D. To get the device's IP address

Solution

1. Step 1: Understand the function purpose

   WiFi.begin() is used to initiate the connection process to a WiFi network by providing the network credentials.

2. Step 2: Differentiate from other functions

   WiFi.status() checks connection status, WiFi.localIP() gets IP, and disconnecting uses WiFi.disconnect().

3. Final Answer:

   To start connecting the device to a WiFi network -> Option A

4. Quick Check:

   WiFi.begin() starts connection [OK]

Hint: Remember: begin means start connection [OK]

Common Mistakes:

• Confusing WiFi.begin() with WiFi.status()
• Thinking WiFi.begin() returns IP address
• Mixing up connect and disconnect functions

2. Which of the following is the correct way to check if the ESP32 is connected to WiFi?

easy

A. if (WiFi.connected()) { ... }

B. if (WiFi.begin() == true) { ... }

C. if (WiFi.localIP() != 0) { ... }

D. if (WiFi.status() == WL_CONNECTED) { ... }

Solution

1. Step 1: Identify the correct status check method

   The function WiFi.status() returns the connection status, and WL_CONNECTED means connected.

2. Step 2: Evaluate other options

   WiFi.connected() does not exist, WiFi.begin() starts connection but doesn't return boolean, and WiFi.localIP() returns IP object, not a number.

3. Final Answer:

   if (WiFi.status() == WL_CONNECTED) { ... } -> Option D

4. Quick Check:

   WiFi.status() == WL_CONNECTED checks connection [OK]

Hint: Use WiFi.status() to check connection status [OK]

Common Mistakes:

• Using WiFi.begin() to check connection
• Assuming WiFi.connected() exists
• Comparing IP address directly to zero

3. Given this code snippet on an ESP8266 device:

WiFi.begin("MySSID", "MyPass");
while (WiFi.status() != WL_CONNECTED) {
  delay(500);
}
Serial.println(WiFi.localIP());

What will be printed if the device successfully connects to the WiFi?

medium

A. WL_CONNECTED

B. The SSID of the WiFi network

C. The IP address assigned to the device

D. An error message

Solution

1. Step 1: Understand the code flow

   The code waits until WiFi.status() returns WL_CONNECTED, meaning connection is successful.

2. Step 2: Identify the output of WiFi.localIP()

   This function returns the device's IP address on the network, which is printed by Serial.println().

3. Final Answer:

   The IP address assigned to the device -> Option C

4. Quick Check:

   WiFi.localIP() prints IP address [OK]

Hint: WiFi.localIP() shows device IP after connection [OK]

Common Mistakes:

• Expecting SSID instead of IP
• Thinking WiFi.status() prints status automatically
• Confusing connection status with output

4. You wrote this code to connect ESP32 to WiFi:

WiFi.begin("HomeNetwork", "password123");
if (WiFi.status() = WL_CONNECTED) {
  Serial.println("Connected!");
}

Why does this code fail to print "Connected!" even when WiFi is connected?

medium

A. Because Serial.println() cannot print strings

B. Because the assignment operator '=' is used instead of '==' in the if condition

C. Because WiFi.status() returns a string, not a constant

D. Because WiFi.begin() must be called inside the if statement

Solution

1. Step 1: Identify the error in the if condition

   The code uses '=' which assigns value instead of '==' which compares values. This causes a logic error.

2. Step 2: Understand the impact on execution

   Because of assignment, the condition does not properly check connection status, so "Connected!" is never printed.

3. Final Answer:

   Because the assignment operator '=' is used instead of '==' in the if condition -> Option B

4. Quick Check:

   Use '==' to compare in if conditions [OK]

Hint: Use '==' for comparison, not '=' [OK]

Common Mistakes:

• Using '=' instead of '==' in conditions
• Calling WiFi.begin() inside if statement
• Misunderstanding Serial.println() capabilities

5. You want your ESP32 to connect to WiFi and print its IP address only after a successful connection, but also retry connection up to 5 times with 1 second delay each. Which code snippet correctly implements this?

hard

A. int retries = 0;
WiFi.begin("SSID", "pass");
while (WiFi.status() != WL_CONNECTED && retries < 5) {
delay(1000);
retries++;
}
if (WiFi.status() == WL_CONNECTED) {
Serial.println(WiFi.localIP());
}

B. WiFi.begin("SSID", "pass");
for (int i = 0; i < 5; i++) {
if (WiFi.status() == WL_CONNECTED) {
Serial.println(WiFi.localIP());
break;
}
delay(1000);
}

C. WiFi.begin("SSID", "pass");
while (WiFi.status() != WL_CONNECTED) {
delay(1000);
}
Serial.println(WiFi.localIP());

D. WiFi.begin("SSID", "pass");
int retries = 0;
while (retries < 5) {
if (WiFi.status() == WL_CONNECTED) {
Serial.println(WiFi.localIP());
break;
}
retries++;
delay(1000);
}

Solution

1. Step 1: Analyze retry logic with condition and counter

   int retries = 0; WiFi.begin("SSID", "pass"); while (WiFi.status() != WL_CONNECTED && retries < 5) { delay(1000); retries++; } if (WiFi.status() == WL_CONNECTED) { Serial.println(WiFi.localIP()); } uses a while loop that checks connection status and retries count, delaying 1 second each time, stopping after 5 tries or success.

2. Step 2: Confirm printing IP only after successful connection

   int retries = 0; WiFi.begin("SSID", "pass"); while (WiFi.status() != WL_CONNECTED && retries < 5) { delay(1000); retries++; } if (WiFi.status() == WL_CONNECTED) { Serial.println(WiFi.localIP()); } prints IP only if WiFi.status() == WL_CONNECTED after retry loop, meeting requirements.

3. Final Answer:

   Option A correctly implements retry with delay and prints IP after connection -> Option A

4. Quick Check:

   Retry loop with condition and counter works best [OK]

Hint: Use while loop with counter for retries [OK]

Common Mistakes:

• Not limiting retries causing infinite loops
• Printing IP before confirming connection
• Using for loop without checking connection inside