I was responding to this. The question is more like “why do esphome use an older version of platformio that doesn’t have the board file for seeed_xiao_esp32s3” But given that the version that esphome uses doesn’t include that board file, esphome cannot simply add it.
Thank You very much for sharing. More than a year, but still useful.
I’ve also noticed that the recent ESPHome updates seem to add the Seeed Xiao ESP32S3 entry in the ‘boards.py’ file.
Susan
Waking up this old thread, but how do I deal with this warning about Arduino framework
?
I get odd behavior with my esp32 S3 baords, and wonder if that is related.
INFO ESPHome 2025.6.2
INFO Reading configuration /config/esphome/bar-motion-gate.yaml...
WARNING The selected Arduino framework version is not the recommended one. If there are connectivity or build issues please remove the manual version.
WARNING The selected Arduino framework version is not the recommended one. If there are connectivity or build issues please remove the manual version.
INFO Generating C++ source...
INFO Compiling app...
If I comment the framework out it won’t compile. What works (and generates the warnings) is this:
esp32:
# board: esp32-s3-devkitc-1
board: seeed_xiao_esp32s3
variant: esp32s3
framework:
type: arduino
# https://community.home-assistant.io/t/seeed-xiao-esp32s3-sense-board-name-not-recognised/587023/36
version: latest
platform_version: 6.5.0
But I can also compile with board: esp32-s3-devkitc-1
.
I don’t have great luck with these boards. I have four of them. I want to use them because of their small size.
I set up one with both an ADC pressure sensor and an I2C compass board and there was all sorts of noise on the ADC line that I could see on an oscilloscope. I removed the I2C component and the ADC pressure sensor worked fine w/o noise. Moved it to an esp8266 and it works fine.
Then yesterday I move a PIR sensor from an ESP8266 to the ESP32S3 and it randomly detects motion, so another issue reading input. (I put the PIR sensor under a ceramic mug to hide it from any motion over night and it detected motion many times.) So, I’m not clear if it’s the esp32S3 board or something in esphome.
Anyone else see weird behavior like this?
A rather standard config for the PIR sensor, I think:
binary_sensor:
- platform: gpio
pin:
number: GPIO09
mode:
input: True
pulldown: True
name: "Motion Sensor"
device_class: motion
AllI use is:
esp32:
board: seeed_xiao_esp32s3
framework:
type: arduino
Perhaps specifying too much is getting the framework (or whatever) confused.
Susan
(BTW - I think the noise issues is getting a bit away from the theme of this topic - perhaps start a new topic and you will get more assistance)
When I try that I get:
UnknownBoard: Unknown board ID 'seeed_xiao_esp32s3'
I’m running 2025.6.3 of ESPHome device builder.
I had set these boards aside since I had problems with them. Looking at previous configs I see I was using the following. Unfortunately, I didn’t note why I added all those platformio_options
:
esphome:
name: ${name}
friendly_name: ${friendly_name}
min_version: 2024.6.0
name_add_mac_suffix: false
platformio_options:
build_flags: -DBOARD_HAS_PSRAM
board_build.arduino.memory_type: qio_opi
board_build.f_flash: 80000000L
board_build.flash_mode: dio
esp32:
board: esp32-s3-devkitc-1
framework:
type: arduino
I’ve been wondering if the odd behavior I was seeing was just due to the esphome config I was using.
See my previous post at Seeed Xiao ESP32S3 Sense board name not recognised - #9 by AussieSusan where I show what else needs to be done to have the board recognised.
Susan