Warning: [ledc.output:109]: LEDC output hasn't been initialized yet!

poudou99 · March 24, 2025, 2:29am

Hi
I don’t know what I did in my yaml file but I got now the following message:
[ledc.output:109]: LEDC output hasn’t been initialized yet!
I suppose is something related to my DC motors but I do not see what it becomes wrong now since it worked before (a week ago)

here is my config:

esphome:
  name: $device_name
  friendly_name: $friendly_name

esp32:
  board: esp32dev
  framework:
    type: arduino

api:
  encryption:
    key:
    reboot_timeout: 0s

ota:
  - platform: esphome
    password:

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  ap:
    ssid: "Mcu-07-Esp32-S3-Wroom-1"
    password:

web_server:
  port: 80

logger:
  level: INFO

captive_portal:

output:

  - platform: ledc
    pin: GPIO42
    id: output_gpio_BUZ

  - platform: ledc
    pin: GPIO16
    id: output_gpio_M2a_ARG

  - platform: ledc
    pin: GPIO17
    id: output_gpio_M2b_ARG

  - platform: ledc
    pin: GPIO18
    id: output_gpio_M4a_ARD

  - platform: ledc
    pin: GPIO08
    id: output_gpio_M4b_ARD

  - platform: ledc
    pin: GPIO12
    id: output_gpio_AR_FXR

  - platform: ledc
    pin: GPIO13
    id: output_gpio_AR_FXG

  - platform: ledc
    pin: GPIO14
    id: output_gpio_AR_FXY

light:

  - platform: binary
    id:    AR_FXR
    name: "AR_FXR"
    output:   output_gpio_AR_FXR

  - platform: binary
    id:    AR_FXG
    name: "AR_FXG"    
    output:   output_gpio_AR_FXG

  - platform: binary
    id:    AR_FXY
    name: "AR_FXY"
    output:   output_gpio_AR_FXY

fan:

  - platform: hbridge
    id:    moteur2_ARG
    name: "moteur2_ARG"
    pin_a: output_gpio_M2a_ARG
    pin_b: output_gpio_M2b_ARG
    # enable_pin: motor_enable
    decay_mode: slow   
    restore_mode: ALWAYS_OFF 

  - platform: hbridge
    id:    moteur4_ARD
    name: "moteur4_ARD"
    pin_a: output_gpio_M4a_ARD
    pin_b: output_gpio_M4b_ARD
    # enable_pin: motor_enable
    decay_mode: slow   
    restore_mode: ALWAYS_OFF 

rtttl:

  output: output_gpio_BUZ
  id: buzzer

(I have eliminated things not related to my issue)

and the install log:

///////////////////////////



INFO ESPHome 2025.3.0
INFO Reading configuration /config/esphome/mcu-07-esp32-s3-wroom-1.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing mcu-07-esp32-s3-wroom-1 (board: esp32-s3-devkitc-1; framework: arduino; platform: platformio/[email protected])
--------------------------------------------------------------------------------
HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash
 - toolchain-riscv32-esp @ 8.4.0+2021r2-patch5 
 - toolchain-xtensa-esp32s3 @ 8.4.0+2021r2-patch5
Dependency Graph
|-- AsyncTCP-esphome @ 2.1.4
|-- WiFi @ 2.0.0
|-- FS @ 2.0.0
|-- Update @ 2.0.0
|-- ESPAsyncWebServer-esphome @ 3.3.0
|-- DNSServer @ 2.0.0
|-- ESPmDNS @ 2.0.0
|-- ArduinoJson @ 6.18.5
|-- noise-c @ 0.1.6
Compiling .pioenvs/mcu-07-esp32-s3-wroom-1/src/main.cpp.o
Linking .pioenvs/mcu-07-esp32-s3-wroom-1/firmware.elf
RAM:   [=         ]  12.7% (used 41772 bytes from 327680 bytes)
Flash: [=====     ]  53.6% (used 983445 bytes from 1835008 bytes)
Building .pioenvs/mcu-07-esp32-s3-wroom-1/firmware.bin
Creating esp32s3 image...
Successfully created esp32s3 image.
esp32_create_combined_bin([".pioenvs/mcu-07-esp32-s3-wroom-1/firmware.bin"], [".pioenvs/mcu-07-esp32-s3-wroom-1/firmware.elf"])
SHA digest in image updated
Wrote 0x100320 bytes to file /data/build/mcu-07-esp32-s3-wroom-1/.pioenvs/mcu-07-esp32-s3-wroom-1/firmware.factory.bin, ready to flash to offset 0x0
esp32_copy_ota_bin([".pioenvs/mcu-07-esp32-s3-wroom-1/firmware.bin"], [".pioenvs/mcu-07-esp32-s3-wroom-1/firmware.elf"])
========================= [SUCCESS] Took 53.64 seconds =========================
INFO Successfully compiled program.
INFO Connecting to 192.168.1.217 port 3232...
INFO Connected to 192.168.1.217
INFO Uploading /data/build/mcu-07-esp32-s3-wroom-1/.pioenvs/mcu-07-esp32-s3-wroom-1/firmware.bin (983840 bytes)
Uploading: [============================================================] 100% Done...


INFO Upload took 6.16 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.1.217 using esphome API
INFO Successfully connected to mcu-07-esp32-s3-wroom-1 @ 192.168.1.217 in 7.144s
INFO Successful handshake with mcu-07-esp32-s3-wroom-1 @ 192.168.1.217 in 0.071s
[01:31:40][I][app:100]: ESPHome version 2025.3.0 compiled on Mar 24 2025, 01:30:42
[01:31:41][W][ledc.output:109]: LEDC output hasn't been initialized yet!

Where did I go wrong?

(I am new here, sorry if I forgotten something in the description of my problem)

poudou99 · March 24, 2025, 6:12am

I have forgotten to say that I had changed the mcu from esp32_wroom_32e to esp32_s3_wroom_1. Don’t know if it is linked

Karosm · March 24, 2025, 7:04am

You should change your board definition for S3
board: esp32-s3-devkitc-1

poudou99 · March 24, 2025, 10:35am

In fact, I did that.
But I made a wrong copy-paste of the intro part of the yaml file coming from the previous MCU

it is reported here

HARDWARE: ESP32S3 240MHz, 320KB RAM, 8MB Flash

Thx

Karosm · March 24, 2025, 10:41am

So what is not working?

poudou99 · March 24, 2025, 10:45am

When I made a Google search with the text of my warning I found this answer:

ledc_output.cpp
ESPHome
https://esphome.io › api › ledc__...
84 // Configure the time with fallback in case of error. 85 int ... 109 ESP_LOGW(TAG, "LEDC output hasn't been initialized yet!"); 110 return ...

from site: ESPHome: /opt/build/esphome/esphome/components/ledc/ledc_output.cpp Source File

in the ledc_output.cpp file we can see at line 107

 void LEDCOutput::write_state(float state) {
   if (!initialized_) {
     ESP_LOGW(TAG, "LEDC output hasn't been initialized yet!");
     return;
   }

For the moment, I did not found how this it is taken into account

poudou99 · March 24, 2025, 3:43pm

No it does not

Karosm · March 24, 2025, 4:12pm

C’mon what doesn’t work, what’s the misbehavior?

poudou99 · March 24, 2025, 5:04pm

Sorry for being unclear, English isn’t my natural language (I’m a French speaker).

When my script was installed on the ESP32-Wroom-32E, I could manage 4 DC motors (with 2 L298Ns), 2 LEDs, 1 buzzer, 2 ultrasonic sensors to measure the distance of a toy car I had built for my grandson with Lego…
Everything worked fine.

When I changed the microcontroller (ESP32-S3-Wroom-1), I migrated the YAML script (adapting the GPIOs to the new board) and installed it. At this point:

I got the warning message “[W][ledc.output:109]: The LEDC output has not yet been initialized!” repeated every second
the microcontroller is very slow: the buzzer, LEDs, integrated circuits, etc. are not working or are extremely slow. No motors are running properly, even at idle.

I suspect something related to the frequency of the GPIOs to set (and count speed parameter). But I do not know determine the frequency value (I am not electronical this doesn’t ring in my ears)

The motors are Lego Power Functions M motors, I would have 5 levels of speed (0%, 25%, 50%, 75% and 100%)

Karosm · March 24, 2025, 5:20pm

Neither mine.

I wonder how all this is powered. Hopefully not from Esp32.

What you get on your Esphome log while it’s running “slow”? I mean runtime log.

poudou99 · March 24, 2025, 6:25pm

The motors are powered by 9V external baterries.
For one L298N (2 motors) I have the following wiring:

pin 12v ← terminal + of the 9V external battery (DC power Source)
pin gnd ← terminal - of the 9V external battery (DC power Source)
pin gnd ← GND of the ESP
pin 5V ← 5V of the ESP
IN1 ← GPIO pin a of motor 1
IN2 ← GPIO pin b of motor 1
IN3 ← GPIO pin a of motor 2
IN4 ← GPIO pin b of motor 2
OUT1 → wire C1 of motor 1
OUT2 → wire C2 of motor 1
OUT3 → wire C1 of motor 2
OUT4 → wire C2 of motor 2

The Ground of the battery and of the ESP are connected together
Jumpers ENA & ENA are installed
The 5V Jumper is installed

Give me a moment I will post a picture.

Here is the log:

======================== [SUCCESS] Took 206.44 seconds ========================
INFO Successfully compiled program.
INFO Connecting to 192.168.1.217 port 3232...
INFO Connected to 192.168.1.217
INFO Uploading /data/build/mcu-07-esp32-s3-wroom-1/.pioenvs/mcu-07-esp32-s3-wroom-1/firmware.bin (994912 bytes)
Uploading: [============================================================] 100% Done...


INFO Upload took 6.27 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
INFO Starting log output from 192.168.1.217 using esphome API
INFO Successfully connected to mcu-07-esp32-s3-wroom-1 @ 192.168.1.217 in 7.122s
INFO Successful handshake with mcu-07-esp32-s3-wroom-1 @ 192.168.1.217 in 0.066s
[11:52:43][I][app:100]: ESPHome version 2025.3.1 compiled on Mar 24 2025, 11:50:51
[11:52:43][C][wifi:600]: WiFi:
[11:52:43][C][wifi:428]:   Local MAC: 3C:84:27:F1:AA:E0
[11:52:43][C][wifi:433]:   SSID: [redacted]
[11:52:43][C][wifi:436]:   IP Address: 192.168.1.217
[11:52:43][C][wifi:440]:   BSSID: [redacted]
[11:52:43][C][wifi:441]:   Hostname: 'mcu-07-esp32-s3-wroom-1'
[11:52:43][C][wifi:443]:   Signal strength: -43 dB ▂▄▆█
[11:52:43][C][wifi:447]:   Channel: 1
[11:52:43][C][wifi:448]:   Subnet: 255.255.255.0
[11:52:43][C][wifi:449]:   Gateway: 192.168.1.1
[11:52:43][C][wifi:450]:   DNS1: 192.168.1.1
[11:52:43][C][wifi:451]:   DNS2: 0.0.0.0
[11:52:43][C][logger:177]: Logger:
[11:52:43][C][logger:178]:   Max Level: DEBUG
[11:52:43][C][logger:179]:   Initial Level: DEBUG
[11:52:43][C][logger:181]:   Log Baud Rate: 115200
[11:52:43][C][logger:182]:   Hardware UART: USB_CDC
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO42
[11:52:43][C][ledc.output:182]:   LEDC Channel: 0
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO16
[11:52:43][C][ledc.output:182]:   LEDC Channel: 1
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO17
[11:52:43][C][ledc.output:182]:   LEDC Channel: 2
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO18
[11:52:43][C][ledc.output:182]:   LEDC Channel: 3
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO8
[11:52:43][C][ledc.output:182]:   LEDC Channel: 4
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO21
[11:52:43][C][ledc.output:182]:   LEDC Channel: 5
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO20
[11:52:43][C][ledc.output:182]:   LEDC Channel: 6
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO19
[11:52:43][C][ledc.output:182]:   LEDC Channel: 7
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 14
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO12
[11:52:43][C][ledc.output:182]:   LEDC Channel: 8
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 9
[11:52:43][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO13
[11:52:43][C][ledc.output:182]:   LEDC Channel: 9
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 9
[11:52:43][C][ledc.output:180]: LEDC Output:
[11:52:43][C][ledc.output:181]:   Pin GPIO14
[11:52:43][C][ledc.output:182]:   LEDC Channel: 10
[11:52:43][C][ledc.output:183]:   PWM Frequency: 1000.0 Hz
[11:52:43][C][ledc.output:184]:   Phase angle: 0.0°
[11:52:43][C][ledc.output:185]:   Bit depth: 9
[11:52:43][C][template.sensor:022]: Template Sensor 'US_dst_max_HA'
[11:52:43][C][template.sensor:022]:   State Class: ''
[11:52:43][C][template.sensor:022]:   Unit of Measurement: ''
[11:52:43][C][template.sensor:022]:   Accuracy Decimals: 1
[11:52:43][C][template.sensor:023]:   Update Interval: 60.0s
[11:52:43][C][template.sensor:022]: Template Sensor 'US_dst_min_HA'
[11:52:43][C][template.sensor:022]:   State Class: ''
[11:52:43][C][template.sensor:022]:   Unit of Measurement: ''
[11:52:43][C][template.sensor:022]:   Accuracy Decimals: 1
[11:52:43][C][template.sensor:023]:   Update Interval: 60.0s
[11:52:43][C][template.sensor:022]: Template Sensor 'AV_US_dst_raw_HA'
[11:52:43][C][template.sensor:022]:   State Class: ''
[11:52:43][C][template.sensor:022]:   Unit of Measurement: ''
[11:52:43][C][template.sensor:022]:   Accuracy Decimals: 1
[11:52:43][C][template.sensor:023]:   Update Interval: 0.2s
[11:52:43][C][template.sensor:022]: Template Sensor 'AR_US_dst_raw_HA'
[11:52:43][C][template.sensor:022]:   State Class: ''
[11:52:43][C][template.sensor:022]:   Unit of Measurement: ''
[11:52:43][C][template.sensor:022]:   Accuracy Decimals: 1
[11:52:43][C][template.sensor:023]:   Update Interval: 0.5s
[11:52:43][C][uptime.sensor:033]: Uptime Sensor 'esp_uptime_sec'
[11:52:43][C][uptime.sensor:033]:   Device Class: 'duration'
[11:52:43][C][uptime.sensor:033]:   State Class: 'total_increasing'
[11:52:43][C][uptime.sensor:033]:   Unit of Measurement: 's'
[11:52:43][C][uptime.sensor:033]:   Accuracy Decimals: 0
[11:52:43][C][uptime.sensor:033]:   Icon: 'mdi:timer-outline'
[11:52:43][C][uptime.sensor:034]:   Type: Seconds
[11:52:43][C][template.text_sensor:020]: Template Sensor 'esp_uptime_day'
[11:52:43][C][template.text_sensor:020]:   Icon: 'mdi:clock-start'
[11:52:43][C][template.sensor:022]: Template Sensor 'AV_US_dst_cur_HA'
[11:52:43][C][template.sensor:022]:   State Class: ''
[11:52:43][C][template.sensor:022]:   Unit of Measurement: ''
[11:52:43][C][template.sensor:022]:   Accuracy Decimals: 1
[11:52:43][C][template.sensor:023]:   Update Interval: 0.5s
[11:52:43][C][template.sensor:022]: Template Sensor 'AR_US_dst_cur_HA'
[11:52:43][C][template.sensor:022]:   State Class: ''
[11:52:43][C][template.sensor:022]:   Unit of Measurement: ''
[11:52:43][C][template.sensor:022]:   Accuracy Decimals: 1
[11:52:43][C][template.sensor:023]:   Update Interval: 0.5s
[11:52:43][C][light:092]: Light 'AV_FXR'
[11:52:43][C][light:092]: Light 'AV_FXG'
[11:52:43][C][light:092]: Light 'AV_FXY'
[11:52:43][C][light:092]: Light 'AR_FXR'
[11:52:43][C][light:092]: Light 'AR_FXG'
[11:52:43][C][light:092]: Light 'AR_FXY'
[11:52:43][C][rtttl:030]: Rtttl:
[11:52:43][C][rtttl:031]:   Gain: 0.600000
[11:52:43][C][fan.hbridge:043]: H-Bridge Fan 'moteur2_ARG'
[11:52:43][C][fan.hbridge:192]:   Speed: YES
[11:52:43][C][fan.hbridge:193]:   Speed count: 100
[11:52:43][C][fan.hbridge:199]:   Direction: YES
[11:52:43][C][fan.hbridge:045]:   Decay Mode: Slow
[11:52:43][C][fan.hbridge:043]: H-Bridge Fan 'moteur4_ARD'
[11:52:43][C][fan.hbridge:192]:   Speed: YES
[11:52:43][C][fan.hbridge:193]:   Speed count: 100
[11:52:43][C][fan.hbridge:199]:   Direction: YES
[11:52:43][C][fan.hbridge:045]:   Decay Mode: Slow
[11:52:43][C][ultrasonic.sensor:045]: Ultrasonic Sensor 'AV_US_dst_raw'
[11:52:43][C][ultrasonic.sensor:045]:   State Class: 'measurement'
[11:52:43][C][ultrasonic.sensor:045]:   Unit of Measurement: 'm'
[11:52:43][C][ultrasonic.sensor:045]:   Accuracy Decimals: 2
[11:52:43][C][ultrasonic.sensor:045]:   Icon: 'mdi:arrow-expand-vertical'
[11:52:43][C][ultrasonic.sensor:046]:   Echo Pin: GPIO40
[11:52:43][C][ultrasonic.sensor:047]:   Trigger Pin: GPIO41
[11:52:43][C][ultrasonic.sensor:048]:   Pulse time: 10 µs
[11:52:43][C][ultrasonic.sensor:049]:   Timeout: 11661 µs
[11:52:43][C][ultrasonic.sensor:050]:   Update Interval: 0.2s
[11:52:43][C][ultrasonic.sensor:045]: Ultrasonic Sensor 'AR_US_dst_raw'
[11:52:43][C][ultrasonic.sensor:045]:   State Class: 'measurement'
[11:52:43][C][ultrasonic.sensor:045]:   Unit of Measurement: 'm'
[11:52:43][C][ultrasonic.sensor:045]:   Accuracy Decimals: 2
[11:52:43][C][ultrasonic.sensor:045]:   Icon: 'mdi:arrow-expand-vertical'
[11:52:43][C][ultrasonic.sensor:046]:   Echo Pin: GPIO15
[11:52:43][C][ultrasonic.sensor:047]:   Trigger Pin: GPIO7
[11:52:43][C][ultrasonic.sensor:048]:   Pulse time: 10 µs
[11:52:43][C][ultrasonic.sensor:049]:   Timeout: 11661 µs
[11:52:43][C][ultrasonic.sensor:050]:   Update Interval: 0.2s
[11:52:43][C][status:034]: Status Binary Sensor 'esp_statut'
[11:52:43][C][status:034]:   Device Class: 'connectivity'
[11:52:43][C][wifi_info:014]: WifiInfo Mac Address 'esp_mac_wifi_adresss'
[11:52:44][C][captive_portal:089]: Captive Portal:
[11:52:44][C][web_server:285]: Web Server:
[11:52:44][C][web_server:286]:   Address: mcu-07-esp32-s3-wroom-1.local:80
[11:52:44][C][mdns:116]: mDNS:
[11:52:44][C][mdns:117]:   Hostname: mcu-07-esp32-s3-wroom-1
[11:52:44][C][esphome.ota:073]: Over-The-Air updates:
[11:52:44][C][esphome.ota:074]:   Address: mcu-07-esp32-s3-wroom-1.local:3232
[11:52:44][C][esphome.ota:075]:   Version: 2
[11:52:44][C][esphome.ota:078]:   Password configured
[11:52:44][C][safe_mode:018]: Safe Mode:
[11:52:44][C][safe_mode:020]:   Boot considered successful after 60 seconds
[11:52:44][C][safe_mode:021]:   Invoke after 10 boot attempts
[11:52:44][C][safe_mode:023]:   Remain in safe mode for 300 seconds
[11:52:44][C][api:140]: API Server:
[11:52:44][C][api:141]:   Address: mcu-07-esp32-s3-wroom-1.local:6053
[11:52:44][C][api:143]:   Using noise encryption: YES
[11:52:44][C][wifi_signal.sensor:010]: WiFi Signal 'esp_signal_wifi'
[11:52:44][C][wifi_signal.sensor:010]:   Device Class: 'signal_strength'
[11:52:44][C][wifi_signal.sensor:010]:   State Class: 'measurement'
[11:52:44][C][wifi_signal.sensor:010]:   Unit of Measurement: 'dBm'
[11:52:44][C][wifi_signal.sensor:010]:   Accuracy Decimals: 0
11:52:44][C][wifi_info:010]: WifiInfo IPAddress 'esp_ip_address'
[11:52:44][C][homeassistant.text_sensor:023]: Homeassistant Text Sensor 'rtttl_alarm_AV'
[11:52:44][C][homeassistant.text_sensor:024]:   Entity ID: 'input_text.mcu_07_esp32_s3_wroom_1_rtttl_alarm_av'
[11:52:44][C][homeassistant.text_sensor:023]: Homeassistant Text Sensor 'rtttl_alarm_AR'
[11:52:44][C][homeassistant.text_sensor:024]:   Entity ID: 'input_text.mcu_07_esp32_s3_wroom_1_rtttl_alarm_ar'
[11:52:44][C][homeassistant.text_sensor:023]: Homeassistant Text Sensor 'rtttl_song'
[11:52:44][C][homeassistant.text_sensor:024]:   Entity ID: 'input_text.mcu_07_esp32_s3_wroom_1_rtttl_song'
[11:52:44][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:44][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:45][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:45][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:45][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:46][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:46][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:46][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[11:52:47][W][ledc.output:109]: LEDC output hasn't been initialized yet!
  ....

Karosm · March 24, 2025, 6:34pm

That’s not runtime log.

Jumper on place or removed (L298)?

poudou99 · March 24, 2025, 7:00pm

The last lines of the report is the “runtime log” (I suppose this - if not, where I can find it?)

The 5V jumper is on place

Karosm · March 24, 2025, 7:17pm

So you are powering Esp from battery through L298N?

poudou99 · March 24, 2025, 7:35pm

poudou99 · March 24, 2025, 7:46pm

here is the log I have downloaded with the “Log” button:

INFO ESPHome 2025.3.1
INFO Reading configuration /config/esphome/mcu-07-esp32-s3-wroom-1.yaml...
INFO Starting log output from 192.168.1.217 using esphome API
INFO Successfully connected to mcu-07-esp32-s3-wroom-1 @ 192.168.1.217 in 0.049s
INFO Successful handshake with mcu-07-esp32-s3-wroom-1 @ 192.168.1.217 in 0.075s
[20:45:57][I][app:100]: ESPHome version 2025.3.1 compiled on Mar 24 2025, 20:43:34
[20:45:57][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:45:58][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:45:58][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:45:58][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:45:59][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:45:59][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:00][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:00][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:00][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:01][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:01][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:01][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:02][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:02][W][ledc.output:109]: LEDC output hasn't been initialized yet!
[20:46:03][W][ledc.output:109]: LEDC output hasn't been initialized yet!

Karosm · March 24, 2025, 7:51pm

So the jumper IS “removed” (on side). And Esp is powering L298. OK.
I don’t see that 6LR61 battery is reliable power source for Esp especially if Esp powers other components. It’s not capable of sourcing lot of current, even less if it’s not in full charge.

I’m not saying that is your problem here though.
Did you find the runtime logs?

poudou99 · March 24, 2025, 8:04pm

During my tests I use a AC/DC converter and I see the same issue (the warning message):

poudou99 · March 24, 2025, 8:06pm

I have posted the results above

Karosm · March 24, 2025, 8:46pm

This is confusing.
You wrote the board is working, but extremely slow.
So what the log prints when the board is working?