firecrest/firmware/waveshare-thermostat.yaml
pyr0ball 12b56e3153 fix: route logger through UART0 instead of USB_SERIAL_JTAG
Waveshare's board wires log output through the same UART USB-C port
used for flashing. ESPHome's default hardware_uart for ESP32-S3 is
USB_SERIAL_JTAG, which is a separate physical port on this board,
so log output was going nowhere the flashing tool could see it.
2026-07-11 22:11:14 -07:00

50 lines
1.2 KiB
YAML

substitutions:
name: firecrest
friendly_name: "Firecrest Thermostat"
esphome:
name: ${name}
friendly_name: ${friendly_name}
platformio_options:
board_build.flash_mode: dio
esp32:
board: esp32-s3-devkitc-1
variant: esp32s3
flash_size: 16MB
framework:
type: esp-idf
sdkconfig_options:
CONFIG_ESP32S3_DATA_CACHE_64KB: y
CONFIG_ESP32S3_INSTRUCTION_CACHE_32KB: y
psram:
mode: octal
speed: 80MHz
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
ap:
ssid: "${friendly_name} Fallback"
password: "thermostat1234"
api:
encryption:
key: !secret ha_api_key
ota:
- platform: esphome
password: !secret ota_password
logger:
level: DEBUG
hardware_uart: UART0 # this board's "UART" USB-C port (used for flashing) also does log printing
# per Waveshare's docs — ESPHome defaults S3 boards to USB_SERIAL_JTAG,
# a different physical port, which is why logs went silent
packages:
display: !include components/display.yaml
sensors: !include components/sensors.yaml
relays: !include components/relays.yaml
climate: !include components/climate.yaml