Installed version 2025.9.3 and updated ESPHome device builder to 2025.9.1 and the ESPHome Device Builder shows error when trying to access it
The add-on seems to not be ready, it might still be starting. Do you want to try again? (also seeing 502: Bad Gateway error on the background of the dialog box)
Is this a bug or have my install gone bad?
Versions
Installation method - Home Assistant OS
Core - 2025.9.3
Supervisor - 2025.09.0
Operating System - 16.2
Frontend - 20250903.5
ESPHome Device Builder - Current version: 2025.9.1
Error log for ESPHome Device Builder
[20:24:52] INFO: Starting ESPHome dashboard...
Traceback (most recent call last):
File "/usr/local/bin/esphome", line 4, in <module>
from esphome.__main__ import main
File "/esphome/esphome/__main__.py", line 16, in <module>
from esphome import const, writer, yaml_util
File "/esphome/esphome/writer.py", line 7, in <module>
from esphome import loader
File "/esphome/esphome/loader.py", line 16, in <module>
import esphome.core.config
File "/esphome/esphome/core/config.py", line 7, in <module>
from esphome import automation, core
File "/esphome/esphome/automation.py", line 1, in <module>
import esphome.codegen as cg
File "/esphome/esphome/codegen.py", line 11, in <module>
from esphome.cpp_generator import ( # noqa: F401
File "/esphome/esphome/cpp_generator.py", line 25, in <module>
from esphome.yaml_util import ESPHomeDataBase
File "/esphome/esphome/yaml_util.py", line 16, in <module>
from yaml import SafeLoader as PurePythonLoader
ImportError: cannot import name 'SafeLoader' from 'yaml' (/usr/local/lib/python3.12/site-packages/yaml/__init__.py)
[20:24:52] INFO: Service ESPHome dashboard exited with code 1 (by signal 0)
Same here - does anyone know what was the last working version so I can roll back without experimenting? (I hadn’t updated for a while and have already rolled back from 2025.10.x due to bluetooth issues, rather not experiment further.)
Despite various up/downgrades this issue persists for me. In fact I think it might have been a rollback (for completely separate reasons) that triggered it. Anyway, the container dies after a few mins with this in the logs:
[17:30:10] INFO: Service ESPHome dashboard exited with code 1 (by signal 0)
[17:30:13] INFO: Starting ESPHome dashboard...
Error processing line 1 of /usr/local/lib/python3.12/site-packages/__editable__.esphome-2025.10.5.pth:
Fatal Python error: init_import_site: Failed to import the site module
Python runtime state: initialized
Traceback (most recent call last):
File "<frozen site>", line 206, in addpackage
File "<string>", line 1, in <module>
File "/usr/local/lib/python3.12/site-packages/__editable___esphome_2025_10_5_finder.py", line 5, in <module>
from importlib.util import spec_from_file_location
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "<frozen importlib._bootstrap>", line 1176, in exec_module
File "<frozen importlib.util>", line 168, in <module>
AttributeError: module 'types' has no attribute 'ModuleType'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "<frozen importlib._bootstrap>", line 1176, in exec_module
File "<frozen site>", line 636, in <module>
File "<frozen site>", line 623, in main
File "<frozen site>", line 405, in addsitepackages
File "<frozen site>", line 247, in addsitedir
File "<frozen site>", line 217, in addpackage
AttributeError: module 'traceback' has no attribute 'format_exception'
[17:30:13] INFO: Service ESPHome dashboard exited with code 1 (by signal 0)
I had a problem with the new release of docker ce, that portainer was also having some problems in certain areas, seem to stem from some API change. Could it be related?
As I can confirm now after writing this the portainer add-on is not starting either
I can confirm downgrading docker make it work, but I’m not really qualified to say how to do it, not sure my method was the right way