Web interface/dashboard do not show device configs

[Saentist]

The problem

After update to latest DEV version no more device configs show in web ui.

all config files are in place even new device add disappear immediately.

Which version of ESPHome has the issue?

2024.6.0-dev

What type of installation are you using?

Home Assistant Add-on

Which version of Home Assistant has the issue?

2024.5.3

What platform are you using?

ESP8266

Board

No response

Component causing the issue

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[Saentist]

2024.6.0-dev20240518 Same situation

s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[15:03:21] INFO: Configuring timezone (Europe/Sofia)...
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
cont-init: info: running /etc/cont-init.d/30-esphome-fork.sh
cont-init: info: /etc/cont-init.d/30-esphome-fork.sh exited 0
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
[15:03:22] INFO: Waiting for ESPHome dashboard to come up...
[15:03:22] INFO: Starting ESPHome dashboard...
2024-05-18 15:03:24,088 INFO Starting dashboard web server on unix socket /var/run/esphome.sock and configuration dir /config/esphome...
[15:03:24] INFO: Starting NGINX...
[15:03:24] 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-05-18 15:05:33,374 INFO 200 GET /devices (0.0.0.0) 3.12ms
2024-05-18 15:06:21,047 INFO 304 GET / (0.0.0.0) 47.08ms
2024-05-18 15:06:21,208 INFO 304 GET /devices (0.0.0.0) 2.70ms
2024-05-18 15:06:26,217 INFO 304 GET /devices (0.0.0.0) 20.10ms
2024-05-18 15:06:31,206 INFO 304 GET /devices (0.0.0.0) 1.98ms
2024-05-18 15:06:36,370 INFO 304 GET /devices (0.0.0.0) 1.93ms
2024-05-18 15:06:42,372 INFO 304 GET /devices (0.0.0.0) 2.31ms
2024-05-18 15:06:48,361 INFO 304 GET /devices (0.0.0.0) 1.45ms
2024-05-18 15:06:54,246 INFO 304 GET /devices (0.0.0.0) 1.45ms
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
[15:07:22] 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
[15:07:22] 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
-----------------------------------------------------------

 Add-on: ESPHome (dev)
 Development version of ESPHome add-on
-----------------------------------------------------------
 Add-on version: 2024.6.0-dev20240518
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.3  (amd64 / qemux86-64)
 Home Assistant Core: 2024.5.4
 Home Assistant Supervisor: 2024.05.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
[15:07:29] INFO: Configuring timezone (Europe/Sofia)...
s6-rc: info: service fix-attrs successfully started
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
cont-init: info: running /etc/cont-init.d/30-esphome-fork.sh
cont-init: info: /etc/cont-init.d/30-esphome-fork.sh exited 0
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
[15:07:31] INFO: Waiting for ESPHome dashboard to come up...
[15:07:31] INFO: Starting ESPHome dashboard...
2024-05-18 15:07:33,069 INFO Starting dashboard web server on unix socket /var/run/esphome.sock and configuration dir /config/esphome...
[15:07:33] INFO: Starting NGINX...
[15:07:34] 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

[ThomasFTL]

All actual updates are running. ESPhome 2024.5.0 Home Assistant AddOn Home Assistant 2024.5.4

The Webpage show no content. Only the headers of the tables for the data and logs and the footer to change sheme are shown. I see no data and no logs. But Home Assistant gets all data and logs. Attached is a screenshot of what the websites look like after the update.

[Saentist]

@ThomasFTL this is Issue is for managment webUI For device WebUI check if your browser don't block web content

https://esphome.io/_static/webserver-v1.min.css
https://esphome.io/_static/webserver-v1.min.js

https://esphome.io/components/web_server.html

[ThomasFTL]

@Saentist thats work. I test with Mozilla, Chrome and Edge. The code of the css file and the js file are displayed as text. But, when I call the ESP's IP, I get the two empty tables. If I display the ESP logs in HA under ESP home, this display works.

[Saentist]

@ThomasFTL create NEW issue and post YAML config file of device

[ThomasFTL]

@Saentist I have around 10 ESP home devices that have been working flawlessly for over 2 years. Since the last update to ESP home, the websites of all ESPs no longer work. I see only the frame.

[Saentist]

@ThomasFTL I have same problem with devices /events do not return visual data

[Saentist]

devices-list.ts:253 Uncaught (in promise) TypeError: i.toLocaleLowerCase is not a function
    at devices-list.ts:253:4
    at Array.sort (<anonymous>)
    at devices-list.ts:249:8
    at r (polling-collection.ts:40:29)

this is a repeating message with browser is not happy with it.

[ThomasFTL]

Update from 2024.5.0 to 2024.5.1: The same problem. No improvement.

[olonsoft]

Just compiled and updated a device to v2024.5.1 and I have the same error as @ThomasFTL shows in his screenshot. Chrome shows this error in console:

www.js:3 Uncaught (in promise) Error: invalid template strings array
    at Ct (www.js:3:335)
    at Mt (www.js:3:1057)
    at new H (www.js:3:1221)
    at T._$AC (www.js:3:4731)
    at T.g (www.js:3:4433)
    at T._$AI (www.js:3:4089)
    at qt (www.js:3:7409)
    at yt.update (www.js:3:7811)
    at yt.performUpdate (www.js:1:6064)
    at yt.scheduleUpdate (www.js:1:5716)

[ThomasFTL]

I have one ESP 32 Cam-Projekt. Thats work. But all ESP 8266 have the Problem with the Web-Interface.

[ThomasFTL]

Why are ESP32, IDF, Libretiny and Pico W components also compiled with an esp12e? Are they also integrated by the linker?

[vvrein]

Faced the same issue. As bad and quick fix - webserver v1 may be used, still works:

web_server:
  port: 80
  version: 1
  css_url: https://esphome.io/_static/webserver-v1.min.css
  js_url: https://esphome.io/_static/webserver-v1.min.js

[randybb]

guys, this issue is about the dashboard, for the web_server problem is opened another issue

[vvrein]

Another fix is here (for esphome devices, not dashboard) https://github.com/esphome/issues/issues/5793#issuecomment-2120983660

[Saentist]

If disabled caching on devices, web interface is show without problem. but strange message appear. Could not allocate memory for JSON document! Requested 512 bytes, largest free heap block: 512 bytes

[ssieb]

~Fixed with https://github.com/esphome/esphome/pull/6797~ Wrong issue.

[Saentist]

@ssieb cannot confirm, still blank dashboard devices list.

Uncaught (in promise) TypeError: i.toLocaleLowerCase is not a function
    at devices-list.ts:253:4
    at Array.sort (<anonymous>)
    at devices-list.ts:249:8
    at r (polling-collection.ts:40:29)

The resource http://10.244.21.87:8123/api/hassio_ingress/-J94cKKnPBFYq23v4xZUvlsJ9eTbwTncftyvBEf4MAs/static/fonts/material-icons/MaterialIcons-Regular.woff2?hash=570eb838 
was preloaded using link preload but not used within a few seconds from the window's load event. 
Please make sure it has an appropriate `as` value and it is preloaded intentionally.

[ssieb]

Sorry, this got overrun with people from the other issue and I missed that.

[Saentist]

2024.6.0-dev20240528 still not devices

[Saentist]

2024.6.0-dev20240529 nothing

[ssieb]

There's no need to keep posting like that unless you think there was something submitted that might change it. This is something very specific to your install since no one else is seeing this. Maybe try re-installing the add-on.

[Saentist]

@ssieb any steps for debugging? I use HAOS so nothing specific can be different from others with same setup.

[ssieb]

It looks like what happens when a proxy doesn't pass websockets. Check the browser network log and see if there are any errors.

[Saentist]

It looks like what happens when a proxy doesn't pass websockets. Check the browser network log and see if there are any errors.

I try different browsers same situation, no devices show, even if create new it disappear after wizard finish. I see websocket messages attaching HAR file from browser log 192.168.1.12.har.zip

devices-list.ts:255 Uncaught (in promise) TypeError: n.toLocaleLowerCase is not a function
    at devices-list.ts:255:30
    at Array.sort (<anonymous>)
    at devices-list.ts:249:8
    at r (polling-collection.ts:40:29)

any second this error appear.

[ssieb]

I don't see any issues in the HAR file. All the devices are there and things seem to be working. I don't know why only you would be getting that error.

[ssieb]

I don't see any issues in the HAR file. All the devices are there and things seem to be working.

[Saentist]

@ssieb Dashboard do not show devices, page generator have something wrong I guess.

[sql-aus-hh]

I am having the same issue. Two different computers, It seems to work if reload the integration, but just for one refresh (F5), then ESPhome-screen keeps empty

[sql-aus-hh]

If you open the "issue" tab in Chrome you will receive the following hint... but I don't know if this is the reason:

[Saentist]

@sql-aus-hh can you share what addons are also installed, maby is some conflicting one

[Saentist]

Is any one else have this problem? Any debugging suggestions are welcome.

[Saentist]

Update Installed ESP home on another virtual pc and ESPHome dashboard again stop to show device.

[JovanVuceljic]

Saw comment in this issue that bad yaml can cause the issue. Did ssh into root/homeassistant/esphome and removed the latest edited one by one until the UI showed up. HA addon for ssh can be used for this. I did Terminal & SSH.

[Saentist]

Saw comment in this issue that bad yaml can cause the issue. Did ssh into root/homeassistant/esphome and removed the latest edited one by one until the UI showed up. HA addon for ssh can be used for this. I did Terminal & SSH.

it import it from devices very bad situation better to see from where error come not to guess.