Create Matter over Thread demo for M5Stack Core S3

[Copilot]

This PR implements a complete Matter over Thread light demo for the M5Stack Core S3 as requested in the issue. The demo creates an On/Off Light device (type 0x100) that can be commissioned and controlled via Matter controllers like Google Home and Home Assistant.

Key Features

• ESP-IDF Project Structure: Uses ESP-IDF toolkit as requested, not Arduino framework
• Matter Over Thread: Implements Thread networking using M5Stack H2 Gateway module
• Visual Feedback: Displays light state on Core S3 screen with colored rectangles:
  • Light grey rectangle when OFF
  • Blue rectangle when ON
• Bluetooth Commissioning: Supports standard Matter commissioning workflow
• Hardware Integration: Custom device HAL for M5Stack Core S3 hardware

Project Structure

m5stack/matter/light/
├── CMakeLists.txt              # ESP-IDF build configuration
├── main/
│   ├── app_main.cpp            # Matter application entry point
│   ├── app_driver.cpp          # Matter attribute handlers
│   └── display_driver.cpp      # M5Stack display control
├── device_hal/m5stack_cores3/  # Hardware abstraction layer
├── sdkconfig.defaults          # Matter and Thread configuration
└── README.md                   # Comprehensive setup guide

Technical Implementation

• Device Type: On/Off Light (0x100) as specified
• Network: Thread with channel 15 configuration
• Display: 320x240 LCD with centered 100x80 rectangle
• Memory: Optimized for ESP32-S3 with SPIRAM support
• OTA: Partition table configured for firmware updates

Usage

1. Build with ESP-IDF v5.1+ and ESP Matter library
2. Flash to M5Stack Core S3 with H2 Gateway module
3. Commission via Bluetooth using Matter controller
4. Control on/off state - rectangle changes color accordingly

The project includes comprehensive documentation for setup, building, and troubleshooting.

Fixes #3.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.registry.nm1.platformio.org
  • Triggering command: /usr/bin/python3 /home/REDACTED/.local/bin/pio run --environment m5stack-core2 (dns block)
  • Triggering command: /usr/bin/python3 /home/REDACTED/.local/bin/pio boards (dns block)
• api.registry.platformio.org
  • Triggering command: /usr/bin/python3 /home/REDACTED/.local/bin/pio run --environment m5stack-core2 (dns block)
  • Triggering command: /usr/bin/python3 /home/REDACTED/.local/bin/pio boards (dns block)
• collector.platformio.org
  • Triggering command: /usr/bin/python3 /home/REDACTED/.local/bin/pio run --environment m5stack-core2 (dns block)
  • Triggering command: /usr/bin/python3 /home/REDACTED/.local/bin/pio boards (dns block)
• dl.espressif.com
  • Triggering command: curl -s REDACTED (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[sgryphon]

Okay, I added the firewall allow list. Are you able to do what you wanted now?