Empty ESPHome window, missing devices

ESPHome
1

Issue Summary I tried to solve it with chatgpt, but there is no solution.

The ESPHome add-on for Home Assistant is experiencing a critical issue where the main dashboard is empty, and devices are not displayed. Despite the devices being functional and accessible through other interfaces, they disappear from the ESPHome main window after refreshing or navigating away. The issue persists across all browsers and the mobile app.

Error Logs

  • Error messages indicate connection failures to the ESPHome API for various devices (e.g., “Can’t connect to ESPHome API for [device]”).
  • The dashboard logs show frequent HTTP GET requests to /devices, returning a status of 304 (Not Modified), which suggests the server is reachable but not returning any device data.

Attempts to Resolve the Issue

  1. Cleared browser cache and cookies multiple times, including using incognito mode.
  2. Disabled browser extensions, such as ad blockers, that might interfere with the interface.
  3. Checked logs for the ESPHome add-on and Home Assistant, observing no significant errors beyond the connection issues.
  4. Reinstalled the ESPHome add-on to reset its state, which temporarily restored visibility but only until the page was refreshed.
  5. Tried accessing the ESPHome interface directly on port 6052, which did not open, indicating a possible port issue.
  6. Attempted to modify configuration settings, including enabling “Use ping for status” and “Home Assistant Dashboard Integration.”
  7. Proposed changing the web interface port to see if that resolves the connectivity issue, but specific configuration steps have yet to be executed.

Current Status

Despite these efforts, the problem remains unresolved, and the ESPHome dashboard continues to display an empty interface with no visible devices.

2

AFAIK ESPHome add-on dashboard actually show list of YAML files located in /config/esphome directory.
Then it tries to resolve names from YAML files by mDNS and check connectivity to devices.

Do You have YAML files in right place ?
What is done or happened before issue was noticed first time ?

3

There was an update to a new version. Rolling back to the previous one does not help.
2024-10-27 20-14-35 Studio Code Server – Home Assistant – Chromium

4

Found very few similar issues on GitHub.
Can You try to more YAML files somewhere else and move back to /config/esphome directory one by one while checking dashboard ?

5

I wonder about file naming. I note all the filenames start with digits not letters. I have never seen that before.

6

Just tried to create f.e. 12.yaml - see no issues in 2024.10.2.
File was discovered & added to dasboard immediately.

7

There goes that idea…

8

Perhaps look in the addon logs.

Also versions? (They are given in the log)

Also look in your browser log.

And stop replying on chatgpt, and certainly using it to write your post is frowned on.

9

What exactly to look for in the logs? GPT did not find an obvious answer there, I gave him all the logs. The Home Assistant and ESPHome versions are the latest, ESPHome was installed regular and beta. The mobile app has exactly the same error.

10

Post the log. Stop wittering on about Chatgpt.

11

Server log, ESPHome beta section

Summary

2024-10-27 19:57:02,989 INFO 304 GET /devices (0.0.0.0) 2.29ms
2024-10-27 19:57:08,998 INFO 304 GET /devices (0.0.0.0) 3.42ms
2024-10-27 20:57:18,036 INFO 304 GET / (0.0.0.0) 1.56ms
2024-10-27 20:57:18,113 INFO 304 GET /devices (0.0.0.0) 2.91ms
2024-10-27 23:41:48,181 INFO 200 GET / (0.0.0.0) 1.87ms
2024-10-27 23:41:48,230 INFO 200 GET /static/fonts/material-icons/material-icons.css?hash=ead4c276 (0.0.0.0) 9.02ms
2024-10-27 23:41:48,235 INFO 200 GET /static/css/esphome-2.css?hash=b92d56a2 (0.0.0.0) 3.03ms
2024-10-27 23:41:48,236 INFO 200 GET /static/fonts/material-icons/MaterialIcons-Regular.woff2?hash=570eb838 (0.0.0.0) 3.96ms
2024-10-27 23:41:48,243 INFO 200 GET /static/js/esphome/index-Coj9zNoA.js (0.0.0.0) 9.51ms
2024-10-27 23:41:48,330 INFO 200 GET /static/images/logo-text.svg (0.0.0.0) 1.22ms
2024-10-27 23:41:48,332 INFO 200 GET /devices (0.0.0.0) 24.23ms
2024-10-27 23:41:48,338 INFO 200 GET /static/fonts/material-icons/MaterialIcons-Regular.woff2 (0.0.0.0) 1.18ms
2024-10-27 23:41:48,348 INFO 200 GET /static/js/esphome/c.BvfXFcuf.js (0.0.0.0) 35.67ms
2024-10-27 23:41:48,547 INFO 200 GET /static/js/esphome/c.Cxavpvjx.js (0.0.0.0) 2.77ms
2024-10-27 23:41:48,549 INFO 200 GET /static/js/esphome/c.0kl3f7I_.js (0.0.0.0) 1.56ms
2024-10-27 23:41:53,312 INFO 304 GET /devices (0.0.0.0) 2.02ms

some other errors

Summary

2024-10-28 00:05:50,721 INFO 304 GET / (0.0.0.0) 0.78ms
2024-10-28 00:05:50,787 INFO 304 GET /devices (0.0.0.0) 2.25ms
2024-10-28 00:05:53,647 INFO 304 GET /devices (0.0.0.0) 2.05ms
2024-10-28 00:05:55,795 INFO 304 GET /devices (0.0.0.0) 1.79ms
2024-10-28 00:05:58,797 INFO 200 GET /edit?configuration=secrets.yaml (0.0.0.0) 1.66ms
2024-10-28 00:05:58,856 INFO 200 GET /static/js/esphome/monaco-editor/esm/vs/editor/editor.worker.js (0.0.0.0) 1.24ms
2024-10-28 00:05:58,873 INFO 101 GET /ace (0.0.0.0) 0.74ms
2024-10-28 00:05:58,891 INFO Running command ‘esphome --dashboard -q vscode --ace /config/esphome’
2024-10-28 00:05:59,655 INFO 304 GET /devices (0.0.0.0) 2.42ms
2024-10-28 00:06:05,648 INFO 304 GET /devices (0.0.0.0) 2.12ms
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service discovery: stopping
s6-rc: info: service discovery successfully stopped
s6-rc: info: service nginx: stopping
[00:06:11] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service esphome: stopping
s6-rc: info: service init-nginx successfully stopped
[00:06:11] INFO: Service ESPHome dashboard exited with code 256 (by signal 15)
s6-rc: info: service esphome successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-timezone: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-timezone successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

12
13

Turn off? I rebooted the server several times. Do I need to turn it off?

Summary

2024-10-28_00-44-21

A little later.
It’s very strange, but now everything works.
I deleted some test configurations, and turned off the server again. And everything works. Thanks to everyone for the help.

Summary

2024-10-28
2024-10-281441×491 17.7 KB