platformio sample cleanup

[netmindz]

Remove bespoke boards from platformio-override.sample.ini as these are not maintained

Summary by CodeRabbit

• Chores
  • Removed configuration support for legacy and specialized microcontroller boards from the sample configuration file, streamlining setup options.
  • Minor improvements to configuration comments and descriptions for enhanced clarity.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Removes multiple legacy and specialized board environment configurations from platformio_override.sample.ini, including heltec_wifi_kit_8, esp8285 variants, anavi_miracle_controller, MY9291, and codm-controller boards. Also applies minor comment adjustments to remaining environment sections.

Changes

Cohort / File(s)	Change Summary
Configuration cleanup platformio_override.sample.ini	Deletes environment blocks for legacy and specialized boards (heltec_wifi_kit_8, esp8285_4CH_MagicHome, esp8285_H801, anavi_miracle_controller, MY9291, codm-controller variants, EleksTube-IPS, and others). Minor comment line reordering in anavi_miracle_controller section and updated descriptive header for esp32dev_V4_dio80 ESP32 IDF V4.4.x configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Review should focus on verifying which environment blocks were intentionally removed and ensuring no active/required board configurations were accidentally deleted
• Confirm minor comment adjustments don't alter functional configuration intent

Suggested reviewers

• softhack007

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'platformio sample cleanup' accurately reflects the main change of removing unmaintained board environments from platformio_override.sample.ini.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bb6114e and 4724dbc.

📒 Files selected for processing (1)

• platformio_override.sample.ini (1 hunks)

🧰 Additional context used

🧠 Learnings (7)

📓 Common learnings

Learnt from: softhack007
Repo: wled/WLED PR: 5107
File: boards/adafruit_matrixportal_esp32s3.json:1-66
Timestamp: 2025-11-22T20:33:14.840Z
Learning: In WLED, board JSON files in the boards/ directory may reference partition files that don't exist or have slightly different names than actual files in tools/. This is intentional because platformio.ini or platformio_override.sample.ini explicitly override the partition file using the board_build.partitions setting, which takes precedence over the board JSON partition reference. This pattern exists in multiple local board definitions and should not be flagged as an issue.

Learnt from: CR
Repo: wled/WLED PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-10-05T15:24:05.545Z
Learning: Applies to platformio.ini : Use platformio.ini as the single source of truth for hardware build targets and settings

📚 Learning: 2025-10-05T15:24:05.545Z

Learnt from: CR
Repo: wled/WLED PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-10-05T15:24:05.545Z
Learning: Applies to platformio.ini : Use platformio.ini as the single source of truth for hardware build targets and settings

Applied to files:

• platformio_override.sample.ini

📚 Learning: 2025-11-22T20:33:14.840Z

Learnt from: softhack007
Repo: wled/WLED PR: 5107
File: boards/adafruit_matrixportal_esp32s3.json:1-66
Timestamp: 2025-11-22T20:33:14.840Z
Learning: In WLED, board JSON files in the boards/ directory may reference partition files that don't exist or have slightly different names than actual files in tools/. This is intentional because platformio.ini or platformio_override.sample.ini explicitly override the partition file using the board_build.partitions setting, which takes precedence over the board JSON partition reference. This pattern exists in multiple local board definitions and should not be flagged as an issue.

Applied to files:

• platformio_override.sample.ini

📚 Learning: 2025-02-19T12:43:34.199Z

Learnt from: blazoncek
Repo: wled/WLED PR: 4482
File: wled00/udp.cpp:147-149
Timestamp: 2025-02-19T12:43:34.199Z
Learning: ESP8266 and ESP32 platforms have different maximum segment name lengths in WLED, which can cause truncation when syncing segment names between devices. This platform difference affects the user experience when using the segment name sync feature.

Applied to files:

• platformio_override.sample.ini

📚 Learning: 2025-10-05T15:24:05.545Z

Learnt from: CR
Repo: wled/WLED PR: 0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-10-05T15:24:05.545Z
Learning: Build at least one hardware environment locally (e.g., `pio run -e esp32dev`) before marking work complete

Applied to files:

• platformio_override.sample.ini

📚 Learning: 2025-09-02T02:27:39.220Z

Learnt from: willmmiles
Repo: wled/WLED PR: 4890
File: lib/NeoESP32RmtHI/src/NeoEsp32RmtHI.S:8-16
Timestamp: 2025-09-02T02:27:39.220Z
Learning: The ESP32 macro is defined when compiling code on all ESP32 variants (ESP32, ESP32-S2, ESP32-S3, ESP32-C3, etc.) in the Arduino framework, providing consistent library compatibility across the entire ESP32 family. For target-specific detection, CONFIG_IDF_TARGET_* macros should be used instead.

Applied to files:

• platformio_override.sample.ini

📚 Learning: 2025-07-06T16:15:24.051Z

Learnt from: Jason2866
Repo: wled/WLED PR: 4167
File: platformio.ini:427-430
Timestamp: 2025-07-06T16:15:24.051Z
Learning: In espressif Arduino framework, `-fno-lto` is set as a standard default in the `platformio-build.py` script. Therefore, using `-fno-lto` in `build_unflags` is not only valid but necessary to remove this default setting before enabling LTO with `-flto=auto` or `-flto=4` in `build_flags`.

Applied to files:

• platformio_override.sample.ini

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (14)

• GitHub Check: wled_build / Build Environments (esp32dev)
• GitHub Check: wled_build / Build Environments (nodemcuv2_compat)
• GitHub Check: wled_build / Build Environments (esp32s3dev_16MB_opi)
• GitHub Check: wled_build / Build Environments (esp32S3_wroom2)
• GitHub Check: wled_build / Build Environments (esp32_eth)
• GitHub Check: wled_build / Build Environments (esp32s3_4M_qspi)
• GitHub Check: wled_build / Build Environments (esp32s3dev_8MB_opi)
• GitHub Check: wled_build / Build Environments (esp32c3dev)
• GitHub Check: wled_build / Build Environments (esp32dev_debug)
• GitHub Check: wled_build / Build Environments (esp32c3dev_qio)
• GitHub Check: wled_build / Build Environments (usermods)
• GitHub Check: wled_build / Build Environments (lolin_s2_mini)
• GitHub Check: wled_build / Build Environments (nodemcuv2_160)
• GitHub Check: wled_build / Build Environments (esp32_wrover)

🔇 Additional comments (1)

platformio_override.sample.ini (1)

245-256: All verification checks passed. No stray references to removed boards remain, platformio.ini exists and is properly configured, and the extends chain for esp32dev_V4_dio80 correctly points to the valid esp32_idf_V4 base environment. The comment change at line 246 ("ESP32 env using ESP-IDF V4.4.x") accurately describes the environment configuration and does not mask any behavioral changes. The configuration cleanup is complete and the file is in a valid state.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[netmindz]

I've left Athom for now as I know these are in common use and I don't know the current state of play with regards to their firmware

[willmmiles]

This is a usermod example that's in the wrong place - probably a bad merge moved the header comment. I think it should get moved to the EleksTube_IPS usermod readme (and we should do the same with the RF433 example too)