Fixed "Invalid mbox" error in SimpleTime example

[kinoh]

Description of Change

As stated in #8661, we have to call WiFi.mode before networking.

Tests scenarios

I've tested my Pull Request on arduino-esp32 v2.0.14 with ESP32-DevKitC-32E Board.

Related links

• assertion "Invalid mbox" failed #8661

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Warnings

⚠️

Some issues found for the commit messages in this PR: the commit message "fix: changes the code to actually connect to the WiFi in roder to get time and date": summary appears to be too long the commit message "fix: removing call to WiFi.begin() at the end of the sketch. It must be called at first.": summary appears to be too long summary should not end with a period (full stop) Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).

	Messages
📖	You might consider squashing your 4 commits (simplifying branch history).

👋 Hello kinoh, we appreciate your contribution to this project!

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 835d7fa

[SuGlider]

@kinoh - Thanks for the PR! Indeed it is necessary to connect to the network in order to get the time/date information.
WiFi.mode() avoids it from crashing, but it doesn't make it work.
WiFi.begin() will avoid the error and also make it work.

[SuGlider]

@me-no-dev - This should also be merged to the release/v2.x branch.

[P-R-O-C-H-Y]

@SuGlider is it ok now to call Wifi.begin() twice in the example?

[SuGlider]

@SuGlider is it ok now to call Wifi.begin() twice in the example?

You are right, it is also called latter. I must call it at first and then use IDF calls.

[vortigont]

Does mentioned issue (invalid mbox) really affects this ntp example? It is related to TCP socket, but NTP does not use TCP at all.
What this change is definitely breaks is NTPoDHCP feature, because dhcp client option should be set before acquiring IP address as stated in comment below.

arduino-esp32/libraries/ESP32/examples/Time/SimpleTime/SimpleTime.ino

Lines 45 to 53 in 50ef6f4

	/**
	* NTP server address could be acquired via DHCP,
	*
	* NOTE: This call should be made BEFORE esp32 acquires IP address via DHCP,
	* otherwise SNTP option 42 would be rejected by default.
	* NOTE: configTime() function call if made AFTER DHCP-client run
	* will OVERRIDE acquired NTP server address
	*/
	esp_sntp_servermode_dhcp(1); // (optional)