Getting started with esp32s3 & ds18b20 problems

ESPHome
1

I’m having problem getting started with esp32s3 & ds18b20. I installed ESPHome on my HA. I can communicate with the esp & successfully load the file.
The module does not go online nor does it recognize the temp sensors. Not sure the problem is the yaml file or the port I connected to. I have checked wiring & included the pull up resistor.
Here is the yaml.

esphome:
name: boiler-monitor
friendly_name: Boiler monitor

esp32:
board: esp32-s3-devkitc-1
framework:
type: arduino

Enable logging

logger:

Enable Home Assistant API

api:
encryption:
key: “xa32At5wY5COydNv6kVtjtQfDuQaWkyRImT6986k4iI=”

ota:

  • platform: esphome
    password: “b9337d078b9434f14eb22bb9ae56231b”

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

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: “Boiler-Monitor Fallback Hotspot”
password: “boQ55o8rfu55”

captive_portal:

one_wire:
platform: gpio
pin: GPIO17

Example configuration entry

sensor:

  • platform: dallas_temp
    address:
    name: temperature
    update_interval: 120s
2

Please post you code with tags, so it’s readable…

code-tags
code-tags1742×350 53.9 KB

3

Sorry, I’m not clear on how you would like the code posted.

4

oops, it was in another place on toolbar.
Here is code.

esphome:
  name: boiler-monitor
  friendly_name: Boiler Monitor

esp32:
  board: esp32-s3-devkitc-1
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: key exists removed for web

ota:
  - platform: esphome
    password: "cb7a98963d234e8dad5b28c9dd1ebaba"

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

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Boiler-Monitor Fallback Hotspot"
    password: "J5Go1PwUpoRr"

captive_portal:
5

Configuration of one_wire and dallas_sensor. On first link there is info how to get sensor address.

one_wire:
  - platform: gpio
    pin: GPIOXX

sensor:
  - platform: dallas_temp
    address: 0x1234567812345628
    name: temperature
    update_interval: 120s
6

Per the above, for my temp probes scattered around the house, I’ve always included the address.

That said, the dallas_sensor lists the address as optional i.e. it’s required if you have more than one sensor on the bus. So you might want to remove the address field entirely and see if it works

Failing that, the address lookup is easy enough per the one_wire code

7

It looks like I am not getting that far. I deleted the device and started again with the file not including the dallas sensor. The result is that the device remains offline. I see no fallback hotspot in my router…

8

So post your actual yaml and the log when compiling.
Are you sure about your board and pin(s) used?

9

I don’t see anything wrong with your code but here’s a basic yaml I use to onboard a new device. Outside of wifi I don’t bother with api & ota keys/passwords.

substitutions:
  name: "esp32usbc"
  friendly_name: "esp32usbc"

esphome:
  name: ${name}
  friendly_name: ${friendly_name}

esp32:
  board: esp32dev
  framework:
    type: arduino

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  fast_connect: true
  power_save_mode: none
  reboot_timeout: 15min

# Enable logging
logger:
  level: VERBOSE
  baud_rate: 115200

# Enable Home Assistant API
api: {}

ota:
  - platform: esphome

safe_mode:
  #disabled: true

sensor:
  - platform: wifi_signal
    name: "WiFi Signal"
    update_interval: 5s
    state_class: ''
10

We have a winner.

After much head scratching and experimentation I used “web esphome.io” and did a first install, then moved the device over to HA to add the sensor files.
A couple of items in the first config were different.
Under esp32: type: it was not “Arduino” but “esp-idf”
And I did connect with the “UART” port rather than the “USB” but both seemed to communicate and write the files.

Thanks for your help.

1 Like