Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. ESPHome - Dashboard will nicht

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.8k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    893

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

ESPHome - Dashboard will nicht

Geplant Angeheftet Gesperrt Verschoben Ungelöst Error/Bug
8 Beiträge 2 Kommentatoren 31 Aufrufe 2 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • D3ltoroxpD Online
    D3ltoroxpD Online
    D3ltoroxp
    schrieb zuletzt editiert von D3ltoroxp
    #1

    Hallo zusammen,

    ich wollte mir ESPHome installieren, da ich einen Bluetooth Proxy habe.
    Ich wollte das Dashboard aktiveren und starten, aber in der Log kommt folgendes.

    Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.1.2 pillow==10.4.0 ERROR: Cannot install esphome==2026.1.2 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 25.3 [notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts Collecting esphome==2026.1.2 Using cached esphome-2026.1.2-py3-none-any.whl.metadata (3.6 kB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_x86_64.whl.metadata (9.2 kB) Collecting cryptography==45.0.1 (from esphome==2026.1.2) Using cached cryptography-45.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.1.2) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB) Collecting PyYAML==6.0.3 (from esphome==2026.1.2) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.1.2) Using cached paho-mqtt-1.6.1.tar.gz (99 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting colorama==0.4.6 (from esphome==2026.1.2) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB) Collecting icmplib==3.0.4 (from esphome==2026.1.2) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB) Collecting tornado==6.5.4 (from esphome==2026.1.2) Using cached tornado-6.5.4-cp39-abi3-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.1.2) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB) Collecting tzdata>=2021.1 (from esphome==2026.1.2) Using cached tzdata-2025.3-py2.py3-none-any.whl.metadata (1.4 kB) Collecting pyserial==3.5 (from esphome==2026.1.2) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB) Collecting platformio==6.1.18 (from esphome==2026.1.2) Using cached platformio-6.1.18-py3-none-any.whl.metadata (7.1 kB) Collecting esptool==5.1.0 (from esphome==2026.1.2) Using cached esptool-5.1.0.tar.gz (383 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting click==8.1.7 (from esphome==2026.1.2) Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB) Collecting esphome-dashboard==20260110.0 (from esphome==2026.1.2) Using cached esphome_dashboard-20260110.0-py3-none-any.whl.metadata (1.2 kB) Collecting aioesphomeapi==43.13.0 (from esphome==2026.1.2) Using cached aioesphomeapi-43.13.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.1.2) Using cached zeroconf-0.148.0-cp313-cp313-manylinux_2_36_x86_64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.1.2) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.1.2) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.1.2) Using cached ruamel_yaml_clib-0.2.15-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (3.5 kB) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.1.2) Using cached esphome_glyphsets-0.2.0-py3-none-any.whl.metadata (3.9 kB) INFO: pip is looking at multiple versions of esphome to determine which version is compatible with other requirements. This could take a while. The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.1.2 depends on pillow==11.3.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip to attempt to solve the dependency conflict | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.1.2 pillow==10.4.0 ERROR: Cannot install esphome==2026.1.2 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 25.3 [notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts Collecting esphome==2026.1.2 Using cached esphome-2026.1.2-py3-none-any.whl.metadata (3.6 kB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_x86_64.whl.metadata (9.2 kB) Collecting cryptography==45.0.1 (from esphome==2026.1.2) Using cached cryptography-45.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.1.2) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB) Collecting PyYAML==6.0.3 (from esphome==2026.1.2) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.1.2) Using cached paho-mqtt-1.6.1.tar.gz (99 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting colorama==0.4.6 (from esphome==2026.1.2) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB) Collecting icmplib==3.0.4 (from esphome==2026.1.2) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB) Collecting tornado==6.5.4 (from esphome==2026.1.2) Using cached tornado-6.5.4-cp39-abi3-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.1.2) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB) Collecting tzdata>=2021.1 (from esphome==2026.1.2) Using cached tzdata-2025.3-py2.py3-none-any.whl.metadata (1.4 kB) Collecting pyserial==3.5 (from esphome==2026.1.2) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB) Collecting platformio==6.1.18 (from esphome==2026.1.2) Using cached platformio-6.1.18-py3-none-any.whl.metadata (7.1 kB) Collecting esptool==5.1.0 (from esphome==2026.1.2) Using cached esptool-5.1.0.tar.gz (383 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting click==8.1.7 (from esphome==2026.1.2) Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB) Collecting esphome-dashboard==20260110.0 (from esphome==2026.1.2) Using cached esphome_dashboard-20260110.0-py3-none-any.whl.metadata (1.2 kB) Collecting aioesphomeapi==43.13.0 (from esphome==2026.1.2) Using cached aioesphomeapi-43.13.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.1.2) Using cached zeroconf-0.148.0-cp313-cp313-manylinux_2_36_x86_64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.1.2) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.1.2) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.1.2) Using cached ruamel_yaml_clib-0.2.15-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (3.5 kB) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.1.2) Using cached esphome_glyphsets-0.2.0-py3-none-any.whl.metadata (3.9 kB) INFO: pip is looking at multiple versions of esphome to determine which version is compatible with other requirements. This could take a while. The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.1.2 depends on pillow==11.3.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip to attempt to solve the dependency conflict at makeError (file:///opt/iobroker/node_modules/autopy/node_modules/execa/lib/error.js:60:11) at handlePromise (file:///opt/iobroker/node_modules/autopy/node_modules/execa/index.js:124:26) at processTicksAndRejections (node:internal/process/task_queues:105:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/src/index.ts:257:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:180:16) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:66:4)
    

    Ich denke mal das hier ist das Problem richtig ?

    rror: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.1.2 pillow==10.4.0 ERROR: Cannot install esphome==2026.1.2 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 25.3 [notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip
    

    Muss ich das genau so in diesem Pfad ausführen /home/iobroker/.cache/autopy/venv/esphome/bin/python3 ? Oder einfach auf dem ioB Host ?

    Da kommen ja noch einige Fehler mehr, aber das scheint er installiert zu haben oder ?

    EDIT::

    Also das hab ich jetzt mal mit sudo ausgeführt, ohne ging es nicht.

    /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip
    

    Der erste Fehler ist weg.

    Aber es gibt noch Probleme mit der dependencies, bei esphome and pillow. Wie ich das aber lösen soll, keine Ahnung.

    -- Ich hab jetzt einfach manuell erst pillow==10.4.0 installiert. Danach den Adapter noch mal neu gestartet. Keine Fehler mehr, Dashboard ist verfügbar. Ob das so der richtige und saubere Weg ist weiß ich nicht. Falls nicht und man hätte das anders lösen sollen, ich hab ein Backup erstellt, ich kann es zurückspielen.

    Hab das alles im angegebenen Pfad installiert, hoffe das war richtig und hätte ich nicht global machen müssen.

    Grüße,
    D3ltoro

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • D3ltoroxpD D3ltoroxp

      Hallo zusammen,

      ich wollte mir ESPHome installieren, da ich einen Bluetooth Proxy habe.
      Ich wollte das Dashboard aktiveren und starten, aber in der Log kommt folgendes.

      Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.1.2 pillow==10.4.0 ERROR: Cannot install esphome==2026.1.2 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 25.3 [notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts Collecting esphome==2026.1.2 Using cached esphome-2026.1.2-py3-none-any.whl.metadata (3.6 kB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_x86_64.whl.metadata (9.2 kB) Collecting cryptography==45.0.1 (from esphome==2026.1.2) Using cached cryptography-45.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.1.2) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB) Collecting PyYAML==6.0.3 (from esphome==2026.1.2) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.1.2) Using cached paho-mqtt-1.6.1.tar.gz (99 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting colorama==0.4.6 (from esphome==2026.1.2) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB) Collecting icmplib==3.0.4 (from esphome==2026.1.2) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB) Collecting tornado==6.5.4 (from esphome==2026.1.2) Using cached tornado-6.5.4-cp39-abi3-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.1.2) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB) Collecting tzdata>=2021.1 (from esphome==2026.1.2) Using cached tzdata-2025.3-py2.py3-none-any.whl.metadata (1.4 kB) Collecting pyserial==3.5 (from esphome==2026.1.2) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB) Collecting platformio==6.1.18 (from esphome==2026.1.2) Using cached platformio-6.1.18-py3-none-any.whl.metadata (7.1 kB) Collecting esptool==5.1.0 (from esphome==2026.1.2) Using cached esptool-5.1.0.tar.gz (383 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting click==8.1.7 (from esphome==2026.1.2) Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB) Collecting esphome-dashboard==20260110.0 (from esphome==2026.1.2) Using cached esphome_dashboard-20260110.0-py3-none-any.whl.metadata (1.2 kB) Collecting aioesphomeapi==43.13.0 (from esphome==2026.1.2) Using cached aioesphomeapi-43.13.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.1.2) Using cached zeroconf-0.148.0-cp313-cp313-manylinux_2_36_x86_64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.1.2) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.1.2) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.1.2) Using cached ruamel_yaml_clib-0.2.15-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (3.5 kB) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.1.2) Using cached esphome_glyphsets-0.2.0-py3-none-any.whl.metadata (3.9 kB) INFO: pip is looking at multiple versions of esphome to determine which version is compatible with other requirements. This could take a while. The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.1.2 depends on pillow==11.3.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip to attempt to solve the dependency conflict | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.1.2 pillow==10.4.0 ERROR: Cannot install esphome==2026.1.2 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 25.3 [notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts Collecting esphome==2026.1.2 Using cached esphome-2026.1.2-py3-none-any.whl.metadata (3.6 kB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_x86_64.whl.metadata (9.2 kB) Collecting cryptography==45.0.1 (from esphome==2026.1.2) Using cached cryptography-45.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.1.2) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB) Collecting PyYAML==6.0.3 (from esphome==2026.1.2) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.1.2) Using cached paho-mqtt-1.6.1.tar.gz (99 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting colorama==0.4.6 (from esphome==2026.1.2) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB) Collecting icmplib==3.0.4 (from esphome==2026.1.2) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB) Collecting tornado==6.5.4 (from esphome==2026.1.2) Using cached tornado-6.5.4-cp39-abi3-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.1.2) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB) Collecting tzdata>=2021.1 (from esphome==2026.1.2) Using cached tzdata-2025.3-py2.py3-none-any.whl.metadata (1.4 kB) Collecting pyserial==3.5 (from esphome==2026.1.2) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB) Collecting platformio==6.1.18 (from esphome==2026.1.2) Using cached platformio-6.1.18-py3-none-any.whl.metadata (7.1 kB) Collecting esptool==5.1.0 (from esphome==2026.1.2) Using cached esptool-5.1.0.tar.gz (383 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Collecting click==8.1.7 (from esphome==2026.1.2) Using cached click-8.1.7-py3-none-any.whl.metadata (3.0 kB) Collecting esphome-dashboard==20260110.0 (from esphome==2026.1.2) Using cached esphome_dashboard-20260110.0-py3-none-any.whl.metadata (1.2 kB) Collecting aioesphomeapi==43.13.0 (from esphome==2026.1.2) Using cached aioesphomeapi-43.13.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.1.2) Using cached zeroconf-0.148.0-cp313-cp313-manylinux_2_36_x86_64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.1.2) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.1.2) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.1.2) Using cached ruamel_yaml_clib-0.2.15-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (3.5 kB) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.1.2) Using cached esphome_glyphsets-0.2.0-py3-none-any.whl.metadata (3.9 kB) INFO: pip is looking at multiple versions of esphome to determine which version is compatible with other requirements. This could take a while. The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.1.2 depends on pillow==11.3.0 To fix this you could try to: 1. loosen the range of package versions you've specified 2. remove package versions to allow pip to attempt to solve the dependency conflict at makeError (file:///opt/iobroker/node_modules/autopy/node_modules/execa/lib/error.js:60:11) at handlePromise (file:///opt/iobroker/node_modules/autopy/node_modules/execa/index.js:124:26) at processTicksAndRejections (node:internal/process/task_queues:105:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/src/index.ts:257:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:180:16) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:66:4)
      

      Ich denke mal das hier ist das Problem richtig ?

      rror: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.1.2 pillow==10.4.0 ERROR: Cannot install esphome==2026.1.2 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 25.3 [notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip
      

      Muss ich das genau so in diesem Pfad ausführen /home/iobroker/.cache/autopy/venv/esphome/bin/python3 ? Oder einfach auf dem ioB Host ?

      Da kommen ja noch einige Fehler mehr, aber das scheint er installiert zu haben oder ?

      EDIT::

      Also das hab ich jetzt mal mit sudo ausgeführt, ohne ging es nicht.

      /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pip
      

      Der erste Fehler ist weg.

      Aber es gibt noch Probleme mit der dependencies, bei esphome and pillow. Wie ich das aber lösen soll, keine Ahnung.

      -- Ich hab jetzt einfach manuell erst pillow==10.4.0 installiert. Danach den Adapter noch mal neu gestartet. Keine Fehler mehr, Dashboard ist verfügbar. Ob das so der richtige und saubere Weg ist weiß ich nicht. Falls nicht und man hätte das anders lösen sollen, ich hab ein Backup erstellt, ich kann es zurückspielen.

      Hab das alles im angegebenen Pfad installiert, hoffe das war richtig und hätte ich nicht global machen müssen.

      Grüße,
      D3ltoro

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb zuletzt editiert von Thomas Braun
      #2

      @D3ltoroxp sagte in ESPHome - Dashboard will nicht:

      Der Knackpunkt ist:

      The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.1.2 depends on pillow==11.3.0
      To fix this you could try to:

      1. loosen the range of package versions you've specified
      2. remove package versions to allow pip to attempt to solve the dependency conflict |
        Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.1.2 pillow==10.4.0
        ERROR: Cannot install esphome==2026.1.2 and pillow==10.4.0 because these package versions have conflicting dependencies.

      esphome braucht also pillow==11.3.0, dein System baut aber 10.4.0.
      Da müssten die Abhängigkeiten gerichtet werden.

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      1 Antwort Letzte Antwort
      0
      • D3ltoroxpD Online
        D3ltoroxpD Online
        D3ltoroxp
        schrieb zuletzt editiert von D3ltoroxp
        #3

        Hast du das in der Log gefunden, mit dem pillow 11.3 ?
        Müsste das im Adapter korrigiert werden, der stößt ja die Installation an, wenn ich das richtig verstehe.
        Es läuft nun, aber ich könnte ja pillow manuell noch auf die neuste Version updaten oder ?
        Ist das dann was ich alles händisch gemacht habe, pfusch, oder kann man das nur so machen, aktuell ?

        EDIT:
        Habs mal manuell probiert .

        Requirement already satisfied: pillow==11.3.0 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (11.3.0)
        WARNING: Ignoring invalid distribution ~illow (/home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages)
        WARNING: Ignoring invalid distribution ~illow (/home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages)
        
        

        Indem Fall hat er es wohl schon selber auf diese Version angehoben.

        Thomas BraunT 1 Antwort Letzte Antwort
        0
        • D3ltoroxpD D3ltoroxp

          Hast du das in der Log gefunden, mit dem pillow 11.3 ?
          Müsste das im Adapter korrigiert werden, der stößt ja die Installation an, wenn ich das richtig verstehe.
          Es läuft nun, aber ich könnte ja pillow manuell noch auf die neuste Version updaten oder ?
          Ist das dann was ich alles händisch gemacht habe, pfusch, oder kann man das nur so machen, aktuell ?

          EDIT:
          Habs mal manuell probiert .

          Requirement already satisfied: pillow==11.3.0 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (11.3.0)
          WARNING: Ignoring invalid distribution ~illow (/home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages)
          WARNING: Ignoring invalid distribution ~illow (/home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages)
          
          

          Indem Fall hat er es wohl schon selber auf diese Version angehoben.

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb zuletzt editiert von
          #4

          @D3ltoroxp sagte in ESPHome - Dashboard will nicht:

          Hast du das in der Log gefunden, mit dem pillow 11.3 ?

          Ja, steht doch auch in dem Zitat drin...

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          1 Antwort Letzte Antwort
          0
          • D3ltoroxpD Online
            D3ltoroxpD Online
            D3ltoroxp
            schrieb zuletzt editiert von
            #5

            Ach ziemlich weit untern, vor lauter gar nicht gesehen. So dann sollte doch jetzt alles passend. Das DB läuft.
            Weg denke ich mal war auch richtig. Warum der Adapter das nicht selber gemacht hat ? Muss man das wahrscheinlich anpassen, mit den Dependances ?

            Thomas BraunT 1 Antwort Letzte Antwort
            0
            • D3ltoroxpD D3ltoroxp

              Ach ziemlich weit untern, vor lauter gar nicht gesehen. So dann sollte doch jetzt alles passend. Das DB läuft.
              Weg denke ich mal war auch richtig. Warum der Adapter das nicht selber gemacht hat ? Muss man das wahrscheinlich anpassen, mit den Dependances ?

              Thomas BraunT Online
              Thomas BraunT Online
              Thomas Braun
              Most Active
              schrieb zuletzt editiert von Thomas Braun
              #6

              @D3ltoroxp sagte in ESPHome - Dashboard will nicht:

              Muss man das wahrscheinlich anpassen, mit den Dependances ?

              Ja, ein Paketmaintainer muss da die Dependency anpassen.
              Ich kenne python/pip nicht besonders gut, aber die Dinger (sei es apt, npm oder was auch sonst) funktionieren alle ähnlich. Ein Paket bringt eine Wunschliste mit, welche anderen Pakete in welcher Version installiert sein müssen, damit es funktioniert. Du hast aber unerfüllbare Konstellationen da. Mach mal ein Issue auf, vielleicht kann man da was im iobroker-Adapter schon anpassen.

              Linux-Werkzeugkasten:
              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
              NodeJS Fixer Skript:
              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

              1 Antwort Letzte Antwort
              1
              • D3ltoroxpD Online
                D3ltoroxpD Online
                D3ltoroxp
                schrieb zuletzt editiert von
                #7

                Unter github beim ESPHome Adapter ?

                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • D3ltoroxpD D3ltoroxp

                  Unter github beim ESPHome Adapter ?

                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb zuletzt editiert von
                  #8

                  @D3ltoroxp

                  Ja.

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  1 Antwort Letzte Antwort
                  0
                  Antworten
                  • In einem neuen Thema antworten
                  Anmelden zum Antworten
                  • Älteste zuerst
                  • Neuste zuerst
                  • Meiste Stimmen


                  Support us

                  ioBroker
                  Community Adapters
                  Donate

                  524

                  Online

                  32.6k

                  Benutzer

                  82.1k

                  Themen

                  1.3m

                  Beiträge
                  Community
                  Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                  ioBroker Community 2014-2025
                  logo
                  • Anmelden

                  • Du hast noch kein Konto? Registrieren

                  • Anmelden oder registrieren, um zu suchen
                  • Erster Beitrag
                    Letzter Beitrag
                  0
                  • Home
                  • Aktuell
                  • Tags
                  • Ungelesen 0
                  • Kategorien
                  • Unreplied
                  • Beliebt
                  • GitHub
                  • Docu
                  • Hilfe