ESP no reporting to HS

I have an ESO32 bard that is showing data from my Dallas temp sensors in the ESP log file but available in home assistant. I have removed and reinstall the add on, I have reflags the board and had yaml fie review and no one can tell what is wrong. It has to be the add on or Home Assistant.

Share your ESP device config.

1 Like

And the logs from the addon.

Have you added the esp device in the HA devices and services page here Open your Home Assistant instance and show your integrations.

1 Like

See below:

ESP Yaml

esphome:
name: esphome-web-f55644
friendly_name: Motor_More

esp32:
board: esp32dev
framework:
type: arduino

Enable logging

logger:

Enable Home Assistant API

api:
encryption:
key: “kfAXRiKPCpJN3opeEDZg9CUNHFbP6jF7VWS0ZbNlY/g=”

ota:

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

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

ap:
ssid: “Esphome-Web-F55644”
password: “LeF2rnDwfznd”

captive_portal:

dallas:

  • pin: GPIO25
    update_interval: “10s”

sensor:

  • platform: dallas
    address: 0xf90b2356cdbd3e28
    name: “Temperature 1”
    id: temperature_1_celsius

  • platform: dallas
    address: 0x4e0b2358b675d328
    name: “Temperature 2”

  • platform: dallas
    address: 0x050b2356b2a2bf28
    name: “Temperature 3”

  • platform: dallas
    address: 0x443c7de381c5a828
    name: “Temperature 4”

  • platform: template
    name: “Temperature 1 in Fahrenheit”
    lambda: |-
    return (id(temperature_1_celsius).state * 9.0/5.0) + 32.0;
    update_interval: 10s

Log File

INFO ESPHome 2023.12.9
INFO Reading configuration /config/esphome/esphome-web-f55644.yaml…
INFO Starting log output from 192.168.2.177 using esphome API
INFO Successfully connected to esphome-web-f55644 @ 192.168.2.177 in 0.054s
INFO Successful handshake with esphome-web-f55644 @ 192.168.2.177 in 0.134s
[08:53:10][I][app:102]: ESPHome version 2023.12.9 compiled on Feb 9 2024, 07:54:58
[08:53:10][C][wifi:573]: WiFi:
[08:53:10][C][wifi:405]: Local MAC: A0:B7:65:F5:56:44
[08:53:11][C][wifi:410]: SSID: ‘Rockboat 2.4’[redacted]
[08:53:11][C][wifi:411]: IP Address: 192.168.2.177
[08:53:11][C][wifi:413]: BSSID: F8:5E:3C:39:69:8A[redacted]
[08:53:11][C][wifi:414]: Hostname: ‘esphome-web-f55644’
[08:53:11][C][wifi:416]: Signal strength: -57 dB ▂▄▆█
[08:53:11][C][wifi:420]: Channel: 11
[08:53:11][C][wifi:421]: Subnet: 255.255.255.0
[08:53:11][C][wifi:422]: Gateway: 192.168.2.1
[08:53:11][C][wifi:423]: DNS1: 192.168.2.1
[08:53:11][C][wifi:424]: DNS2: 0.0.0.0
[08:53:11][C][logger:439]: Logger:
[08:53:11][C][logger:440]: Level: DEBUG
[08:53:11][C][logger:441]: Log Baud Rate: 115200
[08:53:11][C][logger:443]: Hardware UART: UART0
[08:53:11][C][template.sensor:022]: Template Sensor ‘Temperature 1 in Fahrenheit’
[08:53:11][C][template.sensor:022]: State Class: ‘’
[08:53:11][C][template.sensor:022]: Unit of Measurement: ‘’
[08:53:11][C][template.sensor:022]: Accuracy Decimals: 1
[08:53:11][C][template.sensor:023]: Update Interval: 10.0s
[08:53:11][C][dallas.sensor:075]: DallasComponent:
[08:53:11][C][dallas.sensor:076]: Pin: GPIO25
[08:53:11][C][dallas.sensor:077]: Update Interval: 10.0s
[08:53:11][D][dallas.sensor:082]: Found sensors:
[08:53:11][D][dallas.sensor:084]: 0xf90b2356cdbd3e28
[08:53:11][D][dallas.sensor:084]: 0x4e0b2358b675d328
[08:53:11][D][dallas.sensor:084]: 0x050b2356b2a2bf28
[08:53:11][C][dallas.sensor:089]: Device ‘Temperature 1’
[08:53:11][C][dallas.sensor:089]: Device Class: ‘temperature’
[08:53:11][C][dallas.sensor:089]: State Class: ‘measurement’
[08:53:11][C][dallas.sensor:089]: Unit of Measurement: ‘°C’
[08:53:11][C][dallas.sensor:089]: Accuracy Decimals: 1
[08:53:11][C][dallas.sensor:097]: Address: 0xf90b2356cdbd3e28
[08:53:11][C][dallas.sensor:098]: Resolution: 12
[08:53:11][C][dallas.sensor:089]: Device ‘Temperature 2’
[08:53:11][C][dallas.sensor:089]: Device Class: ‘temperature’
[08:53:11][C][dallas.sensor:089]: State Class: ‘measurement’
[08:53:11][C][dallas.sensor:089]: Unit of Measurement: ‘°C’
[08:53:11][C][dallas.sensor:089]: Accuracy Decimals: 1
[08:53:11][C][dallas.sensor:097]: Address: 0x4e0b2358b675d328
[08:53:11][C][dallas.sensor:098]: Resolution: 12
[08:53:11][C][dallas.sensor:089]: Device ‘Temperature 3’
[08:53:11][C][dallas.sensor:089]: Device Class: ‘temperature’
[08:53:11][C][dallas.sensor:089]: State Class: ‘measurement’
[08:53:11][C][dallas.sensor:089]: Unit of Measurement: ‘°C’
[08:53:11][C][dallas.sensor:089]: Accuracy Decimals: 1
[08:53:11][C][dallas.sensor:097]: Address: 0x050b2356b2a2bf28
[08:53:11][C][dallas.sensor:098]: Resolution: 12
[08:53:11][C][dallas.sensor:089]: Device ‘Temperature 4’
[08:53:11][C][dallas.sensor:089]: Device Class: ‘temperature’
[08:53:11][C][dallas.sensor:089]: State Class: ‘measurement’
[08:53:11][C][dallas.sensor:089]: Unit of Measurement: ‘°C’
[08:53:11][C][dallas.sensor:089]: Accuracy Decimals: 1
[08:53:11][C][dallas.sensor:097]: Address: 0x443c7de381c5a828
[08:53:11][C][dallas.sensor:098]: Resolution: 12
[08:53:11][C][captive_portal:088]: Captive Portal:
[08:53:11][C][mdns:115]: mDNS:
[08:53:11][C][mdns:116]: Hostname: esphome-web-f55644
[08:53:11][C][ota:097]: Over-The-Air Updates:
[08:53:11][C][ota:098]: Address: esphome-web-f55644.local:3232
[08:53:11][C][api:139]: API Server:
[08:53:11][C][api:140]: Address: esphome-web-f55644.local:6053
[08:53:11][C][api:142]: Using noise encryption: YES
[08:53:16][D][sensor:094]: ‘Temperature 1 in Fahrenheit’: Sending state 64.62500 with 1 decimals of accuracy
[08:53:16][D][dallas.sensor:143]: ‘Temperature 1’: Got Temperature=18.1°C
[08:53:16][D][sensor:094]: ‘Temperature 1’: Sending state 18.12500 °C with 1 decimals of accuracy
[08:53:16][D][dallas.sensor:143]: ‘Temperature 2’: Got Temperature=18.6°C
[08:53:16][D][sensor:094]: ‘Temperature 2’: Sending state 18.56250 °C with 1 decimals of accuracy
[08:53:16][D][dallas.sensor:143]: ‘Temperature 3’: Got Temperature=18.2°C
[08:53:16][D][sensor:094]: ‘Temperature 3’: Sending state 18.18750 °C with 1 decimals of accuracy
[08:53:16][W][dallas.sensor:261]: ‘Temperature 4’ - Scratch pad checksum invalid!

Please see point 11 here: How to help us help you - or How to ask a good question

1 Like

Did you add that particular esphome node to HA yet (via integration)? :thinking:

The add-on is only to create, edit and show logs from nodes but doesn’t integrate them with Home Assistant! Check the getting started guide (Connecting your device to Home Assistant):bulb:

Add-on: ESPHome
ESPHome add-on for intelligently managing all your ESP8266/ESP32 devices

Add-on version: 2023.12.9
You are running the latest version of this add-on.
System: Home Assistant OS 11.5 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.2.1
Home Assistant Supervisor: 2024.01.1

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[23:51:42] INFO: Configuring timezone (America/New_York)…
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service esphome: starting
s6-rc: info: service esphome successfully started
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service discovery: starting
[23:51:48] INFO: Waiting for ESPHome dashboard to come up…
[23:51:48] INFO: Starting ESPHome dashboard…
2024-02-10 23:51:52,552 INFO Starting dashboard web server on unix socket /var/run/esphome.sock and configuration dir /config/esphome…
[23:51:52] INFO: Starting NGINX…
[23:51:53] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-02-10 23:52:34,866 INFO 200 GET /devices (0.0.0.0) 4.46ms
2024-02-11 00:02:38,575 INFO 200 GET / (0.0.0.0) 29.10ms
2024-02-11 00:02:38,669 INFO 200 GET /static/fonts/material-icons/material-icons.css?hash=ead4c276 (0.0.0.0) 32.52ms
2024-02-11 00:02:38,675 INFO 200 GET /static/fonts/material-icons/MaterialIcons-Regular.woff2?hash=570eb838 (0.0.0.0) 3.56ms
2024-02-11 00:02:38,681 INFO 200 GET /static/css/esphome-2.css?hash=c222cb3b (0.0.0.0) 2.56ms
2024-02-11 00:02:38,710 INFO 200 GET /static/js/esphome/index-6rBAfUo5.js (0.0.0.0) 26.54ms
2024-02-11 00:02:38,795 INFO 200 GET /static/images/logo-text.svg (0.0.0.0) 4.56ms
2024-02-11 00:02:38,806 INFO 200 GET /devices (0.0.0.0) 7.17ms
2024-02-11 00:02:38,936 INFO 200 GET /static/fonts/material-icons/MaterialIcons-Regular.woff2 (0.0.0.0) 2.40ms
2024-02-11 00:02:38,950 INFO 200 GET /static/js/esphome/c.AMCPNCIe.js (0.0.0.0) 142.46ms
2024-02-11 00:02:39,399 INFO 200 GET /static/js/esphome/c.nnnnLD37.js (0.0.0.0) 14.87ms
2024-02-11 00:02:39,405 INFO 200 GET /static/js/esphome/c.S1FZv1in.js (0.0.0.0) 19.90ms
2024-02-11 00:02:43,815 INFO 304 GET /devices (0.0.0.0) 3.53ms
2024-02-11 00:02:48,808 INFO 304 GET /devices (0.0.0.0) 3.67ms
2024-02-11 00:02:49,045 INFO 200 GET /static/js/esphome/c.0zY80UF0.js (0.0.0.0) 6.32ms
2024-02-11 00:02:49,079 INFO 200 GET /static/js/esphome/c.Wn2Ip-c5.js (0.0.0.0) 7.90ms
2024-02-11 00:02:49,088 INFO 200 GET /static/js/esphome/c.KwoaAax2.js (0.0.0.0) 5.63ms
2024-02-11 00:02:49,091 INFO 200 GET /static/js/esphome/c.2nnJSTC_.js (0.0.0.0) 7.37ms
2024-02-11 00:02:49,097 INFO 200 GET /static/js/esphome/c.FPOvDxJr.js (0.0.0.0) 3.61ms
2024-02-11 00:02:49,158 INFO 200 GET /static/js/esphome/c.99tCFNxa.js (0.0.0.0) 3.63ms
2024-02-11 00:02:49,164 INFO 200 GET /static/js/esphome/c.EMzq3JuT.js (0.0.0.0) 2.71ms
2024-02-11 00:02:49,199 INFO 200 GET /secret_keys (0.0.0.0) 4.03ms
2024-02-11 00:02:53,832 INFO 304 GET /devices (0.0.0.0) 2.24ms
2024-02-11 00:02:58,825 INFO 304 GET /devices (0.0.0.0) 3.40ms
2024-02-11 00:03:03,821 INFO 304 GET /devices (0.0.0.0) 2.87ms
2024-02-11 00:03:08,815 INFO 304 GET /devices (0.0.0.0) 2.58ms
2024-02-11 00:03:13,832 INFO 304 GET /devices (0.0.0.0) 3.47ms
2024-02-11 00:03:14,143 INFO 200 GET /static/js/esphome/c.VPeQYmPp.js (0.0.0.0) 3.65ms
2024-02-11 00:03:14,164 INFO 200 GET /static/js/esphome/c.nIEdC0BA.js (0.0.0.0) 4.21ms
2024-02-11 00:03:14,170 INFO 200 GET /static/js/esphome/c.bcXJSIrw.js (0.0.0.0) 3.95ms
2024-02-11 00:03:16,112 INFO 200 GET /static/js/esphome/c.g39gNE03.js (0.0.0.0) 3.31ms
2024-02-11 00:03:16,155 INFO 101 GET /logs (0.0.0.0) 1.61ms
2024-02-11 00:03:16,159 INFO Running command ‘esphome --dashboard logs /config/esphome/esphome-web-f55644.yaml --device 192.168.2.177’
2024-02-11 00:03:18,807 INFO 304 GET /devices (0.0.0.0) 2.55ms
2024-02-11 00:03:23,817 INFO 304 GET /devices (0.0.0.0) 2.52ms
2024-02-11 00:03:28,984 INFO 304 GET /devices (0.0.0.0) 1.63ms
2024-02-11 00:03:34,033 INFO 304 GET /devices (0.0.0.0) 2.29ms

When installing the intagration wear do I find the host information?

You can ether go with the IP address or the hostname you posted already :point_down:

Got it Big thanks!