ESP8266 and ESP32 WiFi capabilities in IOT Protocols - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

WiFi Scan Result Count on ESP8266

What is the output of this ESP8266 Arduino code snippet that scans for WiFi networks and prints the number of networks found?

IOT Protocols

int n = WiFi.scanNetworks();
Serial.println(n);

A Compilation error due to missing WiFi library

B Prints the SSID of the first network found

C Prints zero always regardless of networks

D Prints the number of WiFi networks found (e.g., 5)

💡 Hint

The scanNetworks() function returns the count of networks found.

The scanNetworks() function returns an integer count of detected WiFi networks. The Serial.println prints this number.

🧠 Conceptual

intermediate

Difference in WiFi Modes between ESP8266 and ESP32

Which statement correctly describes a key difference in WiFi modes supported by ESP8266 and ESP32?

A ESP32 supports both station and access point modes simultaneously; ESP8266 does not support simultaneous modes.

B Both ESP8266 and ESP32 support station and access point modes simultaneously.

C ESP8266 supports only station mode; ESP32 supports only access point mode.

D ESP32 supports only station mode; ESP8266 supports both modes simultaneously.

💡 Hint

Check if both chips can act as client and hotspot at the same time.

Both ESP8266 and ESP32 support simultaneous station and access point modes, allowing them to connect to WiFi and create a hotspot at once.

❓ Troubleshoot

advanced

Troubleshooting ESP32 WiFi Connection Failures

An ESP32 device fails to connect to a WPA2 WiFi network. Which of the following is the most likely cause?

A Incorrect WiFi SSID or password entered in the code

B ESP32 does not support WPA2 security

C ESP32 requires a wired Ethernet connection for WPA2

D WiFi antenna is disabled by default on ESP32

💡 Hint

Check credentials carefully when connection fails.

ESP32 supports WPA2 security. Connection failures are often due to wrong SSID or password.

✅ Best Practice

advanced

Best Practice for Power Saving in ESP8266 WiFi

Which option is the best practice to reduce power consumption when using WiFi on ESP8266?

A Disable WiFi and use Bluetooth instead

B Keep WiFi always on to maintain connection stability

C Use WiFi sleep mode and disconnect when not transmitting data

D Increase WiFi transmit power to maximum

💡 Hint

Power saving involves reducing active WiFi time.

Using WiFi sleep mode and disconnecting when idle reduces power consumption significantly on ESP8266.

🔀 Workflow

expert

Correct Sequence to Initialize WiFi on ESP32

What is the correct order of steps to initialize WiFi in station mode on ESP32 using Arduino framework?

A 3,1,2,4

B 1,3,2,4

C 3,2,1,4

D 2,1,3,4

💡 Hint

Start serial first, then set mode, then connect, then wait.

Serial communication must start first to see output. Then set WiFi mode, begin connection, and wait for status.

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