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. Einsteigerfragen
  4. Installation
  5. ESPHome fordert neue Pillow Version

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    15
    1
    840

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

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    1.9k

ESPHome fordert neue Pillow Version

Geplant Angeheftet Gesperrt Verschoben Installation
4 Beiträge 2 Kommentatoren 56 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.
  • W Offline
    W Offline
    wibear
    schrieb am zuletzt editiert von
    #1

    Hallo Forum,
    ESPHome liefert beim Start folgende Fehler:

    2025-12-30 15:20:47.499 - info: host.raspi instance system.adapter.esphome.0 in version "0.6.2" (non-npm: DrozmotiX/ioBroker.esphome) started with pid 2521
    2025-12-30 15:20:55.782 - error: esphome.0 (2521) esphome.0 already running
    2025-12-30 15:20:55.806 - warn: esphome.0 (2521) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2025-12-30 15:20:59.035 - error: host.raspi instance system.adapter.esphome.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2025-12-30 15:20:59.036 - info: host.raspi Restart adapter system.adapter.esphome.0 because enabled
    2025-12-30 15:21:32.854 - info: host.raspi instance system.adapter.esphome.0 in version "0.6.2" (non-npm: DrozmotiX/ioBroker.esphome) started with pid 2845
    2025-12-30 15:21:57.479 - info: esphome.0 (2845) starting. Version 0.6.2 (non-npm: DrozmotiX/ioBroker.esphome) in /opt/iobroker/node_modules/iobroker.esphome, node: v22.21.0, js-controller: 7.0.7
    2025-12-30 15:21:58.859 - info: esphome.0 (2845) Try to connect to 192.168.178.166
    2025-12-30 15:22:00.987 - info: esphome.0 (2845) Native Integration of ESPHome Dashboard enabled, making environment ready
    2025-12-30 15:22:04.028 - error: esphome.0 (2845) Client 192.168.178.166 unreachable !
    2025-12-30 15:22:34.298 - error: esphome.0 (2845) Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2025.12.2 pillow==10.4.0
    ERROR: Cannot install esphome==2025.12.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
    Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
    Collecting esphome==2025.12.2
    Using cached https://www.piwheels.org/simple/esphome/esphome-2025.12.2-py3-none-any.whl (5.2 MB)
    Collecting pillow==10.4.0
    Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_aarch64.whl.metadata (9.2 kB)
    Collecting aioesphomeapi==43.2.1 (from esphome==2025.12.2)
    Using cached aioesphomeapi-43.2.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (5.2 kB)
    Requirement already satisfied: zeroconf==0.148.0 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (0.148.0)
    Requirement already satisfied: puremagic==1.30 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (1.30)
    Requirement already satisfied: ruamel.yaml==0.18.16 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (0.18.16)
    Collecting ruamel.yaml.clib==0.2.15 (from esphome==2025.12.2)
    Using cached ruamel_yaml_clib-0.2.15-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (3.5 kB)
    Requirement already satisfied: esphome-glyphsets==0.2.0 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (0.2.0)
    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 2025.12.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==2025.12.2 pillow==10.4.0
    

    Beim Versuch den Befehl "python3 -m pip install --upgrade pip" auszuführen kommt:

    /home/iobroker/.cache/autopy/venv/esphome/bin $ sudo python3 -m pip install --upgrade pip
    error: externally-managed-environment
    
    × This environment is externally managed
    ╰─> To install Python packages system-wide, try apt install
        python3-xyz, where xyz is the package you are trying to
        install.
    
        If you wish to install a non-Debian-packaged Python package,
        create a virtual environment using python3 -m venv path/to/venv.
        Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
        sure you have python3-full installed.
    

    Wie kann ich bitte das ausführen? Danke.

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • W wibear

      Hallo Forum,
      ESPHome liefert beim Start folgende Fehler:

      2025-12-30 15:20:47.499 - info: host.raspi instance system.adapter.esphome.0 in version "0.6.2" (non-npm: DrozmotiX/ioBroker.esphome) started with pid 2521
      2025-12-30 15:20:55.782 - error: esphome.0 (2521) esphome.0 already running
      2025-12-30 15:20:55.806 - warn: esphome.0 (2521) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
      2025-12-30 15:20:59.035 - error: host.raspi instance system.adapter.esphome.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
      2025-12-30 15:20:59.036 - info: host.raspi Restart adapter system.adapter.esphome.0 because enabled
      2025-12-30 15:21:32.854 - info: host.raspi instance system.adapter.esphome.0 in version "0.6.2" (non-npm: DrozmotiX/ioBroker.esphome) started with pid 2845
      2025-12-30 15:21:57.479 - info: esphome.0 (2845) starting. Version 0.6.2 (non-npm: DrozmotiX/ioBroker.esphome) in /opt/iobroker/node_modules/iobroker.esphome, node: v22.21.0, js-controller: 7.0.7
      2025-12-30 15:21:58.859 - info: esphome.0 (2845) Try to connect to 192.168.178.166
      2025-12-30 15:22:00.987 - info: esphome.0 (2845) Native Integration of ESPHome Dashboard enabled, making environment ready
      2025-12-30 15:22:04.028 - error: esphome.0 (2845) Client 192.168.178.166 unreachable !
      2025-12-30 15:22:34.298 - error: esphome.0 (2845) Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2025.12.2 pillow==10.4.0
      ERROR: Cannot install esphome==2025.12.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
      Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
      Collecting esphome==2025.12.2
      Using cached https://www.piwheels.org/simple/esphome/esphome-2025.12.2-py3-none-any.whl (5.2 MB)
      Collecting pillow==10.4.0
      Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_aarch64.whl.metadata (9.2 kB)
      Collecting aioesphomeapi==43.2.1 (from esphome==2025.12.2)
      Using cached aioesphomeapi-43.2.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (5.2 kB)
      Requirement already satisfied: zeroconf==0.148.0 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (0.148.0)
      Requirement already satisfied: puremagic==1.30 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (1.30)
      Requirement already satisfied: ruamel.yaml==0.18.16 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (0.18.16)
      Collecting ruamel.yaml.clib==0.2.15 (from esphome==2025.12.2)
      Using cached ruamel_yaml_clib-0.2.15-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (3.5 kB)
      Requirement already satisfied: esphome-glyphsets==0.2.0 in /home/iobroker/.cache/autopy/venv/esphome/lib/python3.13/site-packages (from esphome==2025.12.2) (0.2.0)
      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 2025.12.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==2025.12.2 pillow==10.4.0
      

      Beim Versuch den Befehl "python3 -m pip install --upgrade pip" auszuführen kommt:

      /home/iobroker/.cache/autopy/venv/esphome/bin $ sudo python3 -m pip install --upgrade pip
      error: externally-managed-environment
      
      × This environment is externally managed
      ╰─> To install Python packages system-wide, try apt install
          python3-xyz, where xyz is the package you are trying to
          install.
      
          If you wish to install a non-Debian-packaged Python package,
          create a virtual environment using python3 -m venv path/to/venv.
          Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
          sure you have python3-full installed.
      

      Wie kann ich bitte das ausführen? Danke.

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

      @wibear

      Am besten gar nicht.
      Das ist im aktuellen Code gefixt:

      https://github.com/DrozmotiX/ioBroker.esphome/issues/343

      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

      W 1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @wibear

        Am besten gar nicht.
        Das ist im aktuellen Code gefixt:

        https://github.com/DrozmotiX/ioBroker.esphome/issues/343

        W Offline
        W Offline
        wibear
        schrieb am zuletzt editiert von
        #3

        @Thomas-Braun sagte in ESPHome fordert neue Pillow Version:

        Am besten gar nicht.

        Soll ich also diese Fehlermeldung ignorieren?

        Thomas BraunT 1 Antwort Letzte Antwort
        0
        • W wibear

          @Thomas-Braun sagte in ESPHome fordert neue Pillow Version:

          Am besten gar nicht.

          Soll ich also diese Fehlermeldung ignorieren?

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

          @wibear

          Mit einem kommenden Update des Adapters erledigt sich das.

          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
          Antworten
          • In einem neuen Thema antworten
          Anmelden zum Antworten
          • Älteste zuerst
          • Neuste zuerst
          • Meiste Stimmen


          Support us

          ioBroker
          Community Adapters
          Donate

          858

          Online

          32.6k

          Benutzer

          82.0k

          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