r/esp32

Hello everyone!

I'm trying to connect an ESP32-S3 to an Android phone using a basic 4-pin USB-C breakout board (VBUS, GND, D+, D-) wired directly to the native USB pins: GPIO 19 (D-) and GPIO 20 (D+).

​If I use a cable directly from the ESP32-S3's onboard native USB port to the phone, communication works correctly.

​But when I route through the external USB-C breakout board wired to pins 19 and 20, the phone completely ignores it. Wall chargers power the board fine through the breakout board but the phone doesn't.

​Why does the onboard native port work, but wiring directly to pins 19/20 via a breakout board fails? What am I missing about USB architecture or hardware requirements here?

​Thanks!

The main feautures for this board are:

- ESP32-S3-WROOM Module - 8 MB flash

- Button for RESET

- User Button

- User RGB LED

- expansion header

- programming header

- Power LED on 3V rail

for the mechanical side of things we will have:

- 4 x 3.2mm mounting holes

- Size 45x45mm

- 4 layer board design

I've been experimenting with small electronics projects and I'm curious how people in the ESPHome/Home Assistant community solve the physical side of DIY sensors.

The electronics are often relatively easy.

The enclosure can be the difficult part.

For example, with temperature/humidity/air-quality sensors, the enclosure can affect the measurements themselves.

So I'm curious:

What do you currently use for your ESPHome sensor enclosures?

• 3D-printed cases

• Commercial project boxes

• Repurposed containers

• Custom-built enclosures

• No enclosure 😄

• Something else?

And what problems have you encountered?

For example:

• Heat from the ESP32 affecting temperature readings

• Poor airflow

• Humidity getting trapped

• Sensor exposure vs. electronics protection

• USB/power access

• Battery replacement

• Wall mounting

• Ceiling mounting

• Difficult access to the electronics

• Enclosure size

• Appearance — something you actually want visible in your home

• Finding a case that fits your particular sensor combination

I'm particularly interested in what you've tried that didn't work well.

If you could redesign your current sensor enclosure, what would you change?

Hey, I'm building a Spotify controller with an ESP32-S3. It'll have a small display for album art and song info, a rotary encoder for volume/play-pause, two buttons for skipping tracks, and an LED ring around the knob.

I'm pretty new to this, so I'm trying to figure out what wire to buy. I'm leaning towards 22 AWG solid-core because it seems easier to work with, especially when soldering, but I've heard stranded wire is better for projects like this because it's more flexible.

I'll be testing everything on a breadboard first, then soldering it together and putting it in a 3D-printed case.

Would it be fine to use solid-core wire for most of the connections, or should I just get stranded wire? Is stranded actually that much harder to solder as a beginner?

Any advice would be appreciated. I don't want to buy a bunch of wire only to regret it later lol.

parts

• ESP32-S3 N16R8 development board
• 1.54-inch 240×240 ST7789 SPI TFT display
• EC11 rotary encoder with push button
• WS2812B 12-LED RGB ring
• 2 × 12×12mm tactile push buttons
• 330Ω resistor
• 470µF electrolytic capacitor

Edit: Somehow I've resolved this, just by changing the pin assignment and connections, even though I'd already done that.

Context: I'm running ESPhome on an ESP32-C6 supermini. It's connected to three output devices; a 360 degree servo on GPIO20, a 180 servo on GPIO19, and a single WS2811 LED on GPIO 18.

I had it all set up and working fine, until in a daft moment, I used some metal tweezers to move the LED and I think I shorted something. From that point on I couldn't get the LED to work, but both servos behaved fine. But this is where it gets weird

I assumed I blew the LED, no big I have spares. So I hooked up a new LED but nothing worked. I thought maybe I grabbed a duff second LED so I took it over to my testing bench, copied the code from my prod ESP and hooked up the LED. Everything worked fine.

Next thing I thought it could be was that I'd somehow blown the pin the LED was connected to. So I changed the pinout to GPIO15 (and then GPIO16) and connected everything up. Still nothing.

Finally I thought maybe I'd blow the the power or ground line. I'd done a continuity check on both and it was fine. But nonetheless, I hooked up the prod boards 5V and GND lines to the testing boards corresponding lines, powered the test board, and confirmed that the prod board was receiving power. So far so good. I then connected the 2nd LED to the 5V and GND lines on the prod board, but the data pin on the testing board. On accessing the test-board, I was able to confirm the LED works.

So far I've confirmed:

• 5v continuity on the prod esp
• GND continuity on the prod esp
• Continuity between the data pin and the LED
• LED works
• Code works
• Prod board works for servos and logging with no errors

What doesn't work:

• LED on original GPIO18
• LED on GPIO15 or 16

My question is—is there some kind of hardware element on an ESP board that could be damaged by shorting an attached LED that would disable it from controlling LEDs, but not affect anything else?

Here's my sanitised ESPHome Code

esphome:
  name: n26-comms-array
  friendly_name: N26 - Comms Array
  min_version: 2026.4.0
  name_add_mac_suffix: false

esp32:
  variant: esp32c6
  framework:
    type: esp-idf

# Enable logging
logger:

# Enable Home Assistant API
api:

# Allow Over-The-Air updates
ota:
  - platform: esphome

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

espnow:
  peers: 
    - ###########
  on_receive:
    - lambda: |-
        char hex[256];
        ESP_LOGD("espnow", "Data %s:", format_hex_pretty_to(hex, data, size));
    - if:
        condition:
          lambda: "return size >= 1 && data[3] == 0x11;"
        then:
        - lambda: |-
            ESP_LOGD("espnow", "Toggled");
        - button.press: rotate_dish_left
    - if:
        condition:
          lambda: "return size >= 1 && data[3] == 0x22;"
        then:
        - lambda: |-
            ESP_LOGD("espnow", "Faulty Lights 1");
        - button.press: rotate_dish_right
    - if:
        condition:
          lambda: "return size >= 1 && data[3] == 0x33;"
        then:
        - lambda: |-
            ESP_LOGD("espnow", "Faulty Lights 2");
        - button.press: pan_dish_up
    - if:
        condition:
          lambda: "return size >= 1 && data[3] == 0x44;"
        then:
        - lambda: |-
            ESP_LOGD("espnow", "Faulty Lights 1");
        - button.press: pan_dish_down
    - if:
        condition:
          lambda: "return size >= 1 && data[3] == 0x55;"
        then:
        - lambda: |-
            ESP_LOGD("espnow", "Faulty Lights 2");
        - button.press: connection_sweep

servo:
  - id: rotation
    output: pwm_output_1
    min_level: 3%
    idle_level: 7.5%
    max_level: 12.5%
    transition_length: 1s
    
  - id: pan
    output: pwm_output_2
    min_level: 3%
    idle_level: 7.5%
    max_level: 12.5%
    transition_length: 2s

output:
  - platform: ledc
    id: pwm_output_1
    pin: GPIO20
    frequency: 50Hz
    
  - platform: ledc
    id: pwm_output_2
    pin: GPIO19
    frequency: 50Hz

number:
  - platform: template
    id: pan_position
    name: "Pan Position"
    min_value: -1
    max_value: 1
    initial_value: 0
    step: 0.01
    restore_value: false
    optimistic: true
    on_value:
      then:
        - servo.write: 
            id: pan
            level: !lambda "return x;"
  - platform: template
    id: pan_increment
    name: "Pan Increment"
    min_value: 0.00
    max_value: 1
    initial_value: 0.05
    step: 0.05
    restore_value: false
    optimistic: true

switch:
  - platform: template
    id: sweep_mode
    optimistic: true
    on_turn_on:
      then:
        - light.control:
            id: uplink
            state: on
            effect: "Scanning"
            red: 50%
            blue: 0%
            green: 0%
        - servo.write: 
            id: rotation
            level: -0.16
        - while: 
            condition:
              lambda: 'return id(sweep_mode).state;'
            then:
            - servo.write:
                id: pan
                level: 1
            - delay: 2000ms
            - servo.write:
                id: pan
                level: -1
            - delay: 2000ms

    on_turn_off:
      then:
      - servo.detach: 
          id: pan
      - servo.write:
          id: rotation
          level: 0
      - servo.detach: 
          id: rotation
      - light.turn_off: 
          id: uplink

script:
  - id: rotate_left
    then:
      - servo.write:
          id: rotation
          level: -16.0%
      - delay: 500ms
      - servo.write:
          id: rotation
          level: 0%        
  - id: rotate_right
    then:
      - servo.write:
          id: rotation
          level: 16.0%
      - delay: 500ms
      - servo.write:
          id: rotation
          level: 0%
  - id: pan_up
    then:
      - if: 
          condition:
            lambda: 'return (id(pan_position).state - id(pan_increment).state) > -1.0;'
          then: 
            - number.set: 
                id: pan_position
                value: !lambda "return id(pan_position).state - id(pan_increment).state;"
          else: 
            - number.set: 
                id: pan_position
                value: -1.0

  - id: pan_down
    then:
      - if: 
          condition:
            lambda: 'return (id(pan_position).state + id(pan_increment).state) < 1.0;'
          then: 
            - number.set: 
                id: pan_position
                value: !lambda "return id(pan_position).state + id(pan_increment).state;"
          else: 
            - number.set: 
                id: pan_position
                value: 1.0
light:
  - platform: esp32_rmt_led_strip
    channel_colors: GRB
    pin: GPIO18
    num_leds: 1
    chipset: WS2811
    rmt_symbols: 96
    id: uplink
    name: "Uplink"
    effects: 
      - pulse:
          name: "Scanning"
          transition_length: 1s
          update_interval: 1s
          min_brightness: 0%
          max_brightness: 50%
      - flicker:
          name: "Data Transmision"
          alpha: 50%
          intensity: 100%

button:
  - platform: template
    id: rotate_dish_left
    name: "Rotate Left"
    on_press:
      then:
        - script.execute: rotate_left
  - platform: template
    id: rotate_dish_right
    name: "Rotate Right"
    on_press:
      then:
        - script.execute: rotate_right
  - platform: template
    id: pan_dish_up
    name: "Pan Up"
    on_press:
      then:
        - script.execute: pan_up
  - platform: template
    id: pan_dish_down
    name: "Pan Down"
    on_press:
      then:
        - script.execute: pan_down
  - platform: template
    id: home_dish
    name: "Home Dish Position"
    on_press:
      then:
      - servo.write:
          id: pan
          level: 0.0%
      - number.set: 
          id: pan_position
          value: 0.00
  - platform: template
    id: scanning
    name: "Scanning"
    on_press:
      then:
        - light.control:
            id: uplink
            state: on
            effect: "Scanning"
            red: 50%
            blue: 0%
            green: 0%

            
  - platform: template
    id: transmitting
    name: "Transmitting"
    on_press:
      then:
        - light.control:
            id: uplink
            state: on
            effect: "Data Transmision"
            red: 0%
            blue: 0%
            green: 50%

  - platform: template
    id: connection_sweep
    name: "Connection Sweep"
    on_press:
      then:
        - switch.toggle: 
            id: sweep_mode

Translucent print to show onboard led which follows album art