Add WiFi-on/off build presets and binary size compare workflow

[Stargazer2026]

Motivation

• Provide a reproducible, side-by-side build workflow to produce WiFi-enabled and WiFi-forced-off firmware so the measurable binary-size delta can be used as an objective argument for upstream changes.

Description

• Add two sample PlatformIO override environments to platformio_override.sample.ini: slwf09_eth_wifi_on and slwf09_eth_wifi_off, where the latter adds -D WLED_FORCE_WIFI_OFF while keeping all other flags identical.
• Add tools/compare_wifioff_size.sh, a small automation script that builds both environments, locates both firmware.bin artifacts, prints their sizes and byte delta, and emits SHA256 checksums for traceability.
• Include usage instructions in the sample override section so maintainers can copy to platformio_override.ini and run the compare script easily.

Testing

• Ran a shell syntax check with bash -n tools/compare_wifioff_size.sh, which passed.
• Executed ./tools/compare_wifioff_size.sh slwf09_eth_wifi_on slwf09_eth_wifi_off after creating a temporary platformio_override.ini; environment resolution and PlatformIO invocation worked, but the full build could not complete due to an external network/proxy error (PlatformIO failed to download platform packages with HTTP 403), so firmware artifacts were not produced in this environment.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 503a709f28

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Register websocket callbacks before WiFi-off early return

When WLED_FORCE_WIFI_OFF is enabled, initConnection() returns before reaching ws.onEvent(wsEvent), and this is the only websocket callback registration in the repo (wled00/wled.cpp). In that configuration (notably Ethernet-only builds with websockets enabled), websocket clients can connect but incoming websocket events are never handled, which breaks the live UI/control path that relies on wsEvent.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Preserve connection startup flow in WiFi-off setup path

The WLED_FORCE_WIFI_OFF branch skips the startup findWiFi(true) call, but handleConnection() still has an early guard that returns while wifiConfigured && multiWiFi.size() > 1 && WiFi.scanComplete() < 0. On devices with multiple saved SSIDs, scanComplete() can stay in the negative "no scan complete" state, so the loop keeps returning before initConnection()/interface initialization runs, causing startup networking services to stall even if Ethernet is present.

Useful? React with 👍 / 👎.