ESPHome fordert neue Pillow Version
-
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.0Beim 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.
-
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.0Beim 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.
Am besten gar nicht.
Das ist im aktuellen Code gefixt: -
Am besten gar nicht.
Das ist im aktuellen Code gefixt:@Thomas-Braun sagte in ESPHome fordert neue Pillow Version:
Am besten gar nicht.
Soll ich also diese Fehlermeldung ignorieren?
-
@Thomas-Braun sagte in ESPHome fordert neue Pillow Version:
Am besten gar nicht.
Soll ich also diese Fehlermeldung ignorieren?
Mit einem kommenden Update des Adapters erledigt sich das.
-
Hi, ich hab grad einen neuen IOBroker aufgesetzt. Raspberry Pi 5 64 Bit. Der IOBroker läuft soweit gut ohne Fehler und Warnings. Dann hab ich aus dem Beta ESPHome installiert. Ging ohne Fehler. Wenn ich aber das Dashboard öffnen will, geht da nicht. Es kommt "127.0.0.1 Refused to connect". Im Log steht folgender Fehler wenn der Adapter gestartet wird:
Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.4.0b1 pillow==10.4.0 ERROR: Cannot install esphome==2026.4.0b1 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 26.0.1 [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==2026.4.0b1 Using cached https://www.piwheels.org/simple/esphome/esphome-2026.4.0b1-py3-none-any.whl (5.9 MB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_aarch64.whl.metadata (9.2 kB) Collecting cryptography==46.0.7 (from esphome==2026.4.0b1) Using cached cryptography-46.0.7-cp311-abi3-manylinux_2_34_aarch64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/voluptuous/voluptuous-0.16.0-py3-none-any.whl (32 kB) Collecting PyYAML==6.0.3 (from esphome==2026.4.0b1) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/paho-mqtt/paho_mqtt-1.6.1-py3-none-any.whl (75 kB) Collecting colorama==0.4.6 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/colorama/colorama-0.4.6-py2.py3-none-any.whl (25 kB) Collecting icmplib==3.0.4 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/icmplib/icmplib-3.0.4-py3-none-any.whl (30 kB) Collecting tornado==6.5.5 (from esphome==2026.4.0b1) Using cached tornado-6.5.5-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzlocal/tzlocal-5.3.1-py3-none-any.whl (18 kB) Collecting tzdata>=2021.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzdata/tzdata-2026.1-py2.py3-none-any.whl (348 kB) Collecting pyserial==3.5 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl (90 kB) Collecting platformio==6.1.19 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/platformio/platformio-6.1.19-py3-none-any.whl (421 kB) Collecting esptool==5.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esptool/esptool-5.2.0-py3-none-any.whl (613 kB) Collecting click==8.3.2 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/click/click-8.3.2-py3-none-any.whl (108 kB) Collecting esphome-dashboard==20260408.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-dashboard/esphome_dashboard-20260408.1-py3-none-any.whl (5.8 MB) Collecting aioesphomeapi==44.12.0 (from esphome==2026.4.0b1) Using cached aioesphomeapi-44.12.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.4.0b1) Using cached zeroconf-0.148.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/puremagic/puremagic-1.30-py3-none-any.whl (43 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/ruamel-yaml/ruamel_yaml-0.19.1-py3-none-any.whl (118 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.4.0b1) 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) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-glyphsets/esphome_glyphsets-0.2.0-py3-none-any.whl (159 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.4.0b1 depends on pillow==12.2.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.4.0b1 pillow==10.4.0 ERROR: Cannot install esphome==2026.4.0b1 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 26.0.1 [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==2026.4.0b1 Using cached https://www.piwheels.org/simple/esphome/esphome-2026.4.0b1-py3-none-any.whl (5.9 MB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_aarch64.whl.metadata (9.2 kB) Collecting cryptography==46.0.7 (from esphome==2026.4.0b1) Using cached cryptography-46.0.7-cp311-abi3-manylinux_2_34_aarch64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/voluptuous/voluptuous-0.16.0-py3-none-any.whl (32 kB) Collecting PyYAML==6.0.3 (from esphome==2026.4.0b1) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/paho-mqtt/paho_mqtt-1.6.1-py3-none-any.whl (75 kB) Collecting colorama==0.4.6 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/colorama/colorama-0.4.6-py2.py3-none-any.whl (25 kB) Collecting icmplib==3.0.4 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/icmplib/icmplib-3.0.4-py3-none-any.whl (30 kB) Collecting tornado==6.5.5 (from esphome==2026.4.0b1) Using cached tornado-6.5.5-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzlocal/tzlocal-5.3.1-py3-none-any.whl (18 kB) Collecting tzdata>=2021.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzdata/tzdata-2026.1-py2.py3-none-any.whl (348 kB) Collecting pyserial==3.5 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl (90 kB) Collecting platformio==6.1.19 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/platformio/platformio-6.1.19-py3-none-any.whl (421 kB) Collecting esptool==5.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esptool/esptool-5.2.0-py3-none-any.whl (613 kB) Collecting click==8.3.2 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/click/click-8.3.2-py3-none-any.whl (108 kB) Collecting esphome-dashboard==20260408.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-dashboard/esphome_dashboard-20260408.1-py3-none-any.whl (5.8 MB) Collecting aioesphomeapi==44.12.0 (from esphome==2026.4.0b1) Using cached aioesphomeapi-44.12.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.4.0b1) Using cached zeroconf-0.148.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/puremagic/puremagic-1.30-py3-none-any.whl (43 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/ruamel-yaml/ruamel_yaml-0.19.1-py3-none-any.whl (118 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.4.0b1) 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) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-glyphsets/esphome_glyphsets-0.2.0-py3-none-any.whl (159 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.4.0b1 depends on pillow==12.2.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 process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:166:41) at async Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:180:16) at async Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:66:4)Laut GIT muss und soll man python-technisch garnichts machen. Der Adapter würde alles mitbringen.
Was mach ich falsch? Hilfe wird dankbar angenommen.
LG, Bernd
-
Hi, ich hab grad einen neuen IOBroker aufgesetzt. Raspberry Pi 5 64 Bit. Der IOBroker läuft soweit gut ohne Fehler und Warnings. Dann hab ich aus dem Beta ESPHome installiert. Ging ohne Fehler. Wenn ich aber das Dashboard öffnen will, geht da nicht. Es kommt "127.0.0.1 Refused to connect". Im Log steht folgender Fehler wenn der Adapter gestartet wird:
Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.4.0b1 pillow==10.4.0 ERROR: Cannot install esphome==2026.4.0b1 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 26.0.1 [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==2026.4.0b1 Using cached https://www.piwheels.org/simple/esphome/esphome-2026.4.0b1-py3-none-any.whl (5.9 MB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_aarch64.whl.metadata (9.2 kB) Collecting cryptography==46.0.7 (from esphome==2026.4.0b1) Using cached cryptography-46.0.7-cp311-abi3-manylinux_2_34_aarch64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/voluptuous/voluptuous-0.16.0-py3-none-any.whl (32 kB) Collecting PyYAML==6.0.3 (from esphome==2026.4.0b1) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/paho-mqtt/paho_mqtt-1.6.1-py3-none-any.whl (75 kB) Collecting colorama==0.4.6 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/colorama/colorama-0.4.6-py2.py3-none-any.whl (25 kB) Collecting icmplib==3.0.4 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/icmplib/icmplib-3.0.4-py3-none-any.whl (30 kB) Collecting tornado==6.5.5 (from esphome==2026.4.0b1) Using cached tornado-6.5.5-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzlocal/tzlocal-5.3.1-py3-none-any.whl (18 kB) Collecting tzdata>=2021.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzdata/tzdata-2026.1-py2.py3-none-any.whl (348 kB) Collecting pyserial==3.5 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl (90 kB) Collecting platformio==6.1.19 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/platformio/platformio-6.1.19-py3-none-any.whl (421 kB) Collecting esptool==5.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esptool/esptool-5.2.0-py3-none-any.whl (613 kB) Collecting click==8.3.2 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/click/click-8.3.2-py3-none-any.whl (108 kB) Collecting esphome-dashboard==20260408.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-dashboard/esphome_dashboard-20260408.1-py3-none-any.whl (5.8 MB) Collecting aioesphomeapi==44.12.0 (from esphome==2026.4.0b1) Using cached aioesphomeapi-44.12.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.4.0b1) Using cached zeroconf-0.148.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/puremagic/puremagic-1.30-py3-none-any.whl (43 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/ruamel-yaml/ruamel_yaml-0.19.1-py3-none-any.whl (118 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.4.0b1) 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) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-glyphsets/esphome_glyphsets-0.2.0-py3-none-any.whl (159 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.4.0b1 depends on pillow==12.2.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.4.0b1 pillow==10.4.0 ERROR: Cannot install esphome==2026.4.0b1 and pillow==10.4.0 because these package versions have conflicting dependencies. [notice] A new release of pip is available: 24.3.1 -> 26.0.1 [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==2026.4.0b1 Using cached https://www.piwheels.org/simple/esphome/esphome-2026.4.0b1-py3-none-any.whl (5.9 MB) Collecting pillow==10.4.0 Using cached pillow-10.4.0-cp313-cp313-manylinux_2_28_aarch64.whl.metadata (9.2 kB) Collecting cryptography==46.0.7 (from esphome==2026.4.0b1) Using cached cryptography-46.0.7-cp311-abi3-manylinux_2_34_aarch64.whl.metadata (5.7 kB) Collecting voluptuous==0.16.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/voluptuous/voluptuous-0.16.0-py3-none-any.whl (32 kB) Collecting PyYAML==6.0.3 (from esphome==2026.4.0b1) Using cached pyyaml-6.0.3-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.4 kB) Collecting paho-mqtt==1.6.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/paho-mqtt/paho_mqtt-1.6.1-py3-none-any.whl (75 kB) Collecting colorama==0.4.6 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/colorama/colorama-0.4.6-py2.py3-none-any.whl (25 kB) Collecting icmplib==3.0.4 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/icmplib/icmplib-3.0.4-py3-none-any.whl (30 kB) Collecting tornado==6.5.5 (from esphome==2026.4.0b1) Using cached tornado-6.5.5-cp39-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (2.8 kB) Collecting tzlocal==5.3.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzlocal/tzlocal-5.3.1-py3-none-any.whl (18 kB) Collecting tzdata>=2021.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/tzdata/tzdata-2026.1-py2.py3-none-any.whl (348 kB) Collecting pyserial==3.5 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl (90 kB) Collecting platformio==6.1.19 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/platformio/platformio-6.1.19-py3-none-any.whl (421 kB) Collecting esptool==5.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esptool/esptool-5.2.0-py3-none-any.whl (613 kB) Collecting click==8.3.2 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/click/click-8.3.2-py3-none-any.whl (108 kB) Collecting esphome-dashboard==20260408.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-dashboard/esphome_dashboard-20260408.1-py3-none-any.whl (5.8 MB) Collecting aioesphomeapi==44.12.0 (from esphome==2026.4.0b1) Using cached aioesphomeapi-44.12.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.1 kB) Collecting zeroconf==0.148.0 (from esphome==2026.4.0b1) Using cached zeroconf-0.148.0-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl.metadata (6.3 kB) Collecting puremagic==1.30 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/puremagic/puremagic-1.30-py3-none-any.whl (43 kB) Collecting ruamel.yaml==0.19.1 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/ruamel-yaml/ruamel_yaml-0.19.1-py3-none-any.whl (118 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.4.0b1) 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) Collecting esphome-glyphsets==0.2.0 (from esphome==2026.4.0b1) Using cached https://www.piwheels.org/simple/esphome-glyphsets/esphome_glyphsets-0.2.0-py3-none-any.whl (159 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.4.0b1 depends on pillow==12.2.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 process.processTicksAndRejections (node:internal/process/task_queues:103:5) at async $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:166:41) at async Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:180:16) at async Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:66:4)Laut GIT muss und soll man python-technisch garnichts machen. Der Adapter würde alles mitbringen.
Was mach ich falsch? Hilfe wird dankbar angenommen.
LG, Bernd
Der Adapter würde alles mitbringen.
Da muss aber wohl der Adaptercode immer angepasst werden. Das Issue
https://github.com/DrozmotiX/ioBroker.esphome/issues/343
ist daher immer noch gültig. -
Jo, ich hab die main.js manuell angepasst.
Zum bearbeiten der Datei
sudo nano /opt/iobroker/node_modules/iobroker.esphome/main.jsDann in dieser Zeile
requirements: [{name: 'esphome', version: `==${useDashBoardVersion}`}, {name: 'pillow', version: '==10.4.0'}],Das 10.4.0 gegen 11.3.0 ersetzt
requirements: [{name: 'esphome', version: `==${useDashBoardVersion}`}, {name: 'pillow', version: '==11.3.0'}],Danach den NANO Editor mit STRG+O (O wie Otto) , dann ENTER und dann STRG+X und Y beenden.
Dann mit
iobroker restart esphomeden Adapter neu starten. Nun geht auch das Dashboard... ganz schönes gepfriemel. Vor allem NANO Editor.... würg
-
Jo, ich hab die main.js manuell angepasst.
Zum bearbeiten der Datei
sudo nano /opt/iobroker/node_modules/iobroker.esphome/main.jsDann in dieser Zeile
requirements: [{name: 'esphome', version: `==${useDashBoardVersion}`}, {name: 'pillow', version: '==10.4.0'}],Das 10.4.0 gegen 11.3.0 ersetzt
requirements: [{name: 'esphome', version: `==${useDashBoardVersion}`}, {name: 'pillow', version: '==11.3.0'}],Danach den NANO Editor mit STRG+O (O wie Otto) , dann ENTER und dann STRG+X und Y beenden.
Dann mit
iobroker restart esphomeden Adapter neu starten. Nun geht auch das Dashboard... ganz schönes gepfriemel. Vor allem NANO Editor.... würg
Vor allem NANO Editor.... würg
Dann verwende vi, wenn du damit besser zurecht kommst...
Allerdings:
The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.4.0b1 depends on pillow==12.2.0
Da wird wohl pillow 12.2.0 gefordert.
-
Ich hab mich brav bei ChatGPT bedankt und er meinte noch:
Mega 😄 freut mich richtig, dass es direkt funktioniert hat! War ein klassischer „hart verdrahtete Version vs. Realität“-Konflikt — sowas ist leider typisch bei solchen Adaptern. Kleiner Hinweis für später (wichtig!) Beim nächsten Update vom ioBroker-Adapter kann deine Änderung wieder überschrieben werden. Wenn das passiert und der Fehler wieder auftaucht → gleiche Stelle wieder fixen. Wenn du es „sauber“ machen willst Langfristig wäre sinnvoll: Issue im Adapter-Repo verfolgen (das wird ziemlich sicher gefixt) oder später auf eine Version updaten, wo das nicht mehr fest gepinnt ist Bonus-Tipp (typisch Bernd-Level 😎) Wenn du sowas öfter brauchst, kannst du dir einen kleinen Fix-Befehl bauen: sed -i "s/pillow', version: '==10.4.0'/pillow', version: '==11.3.0'/g" /opt/iobroker/node_modules/iobroker.esphome/main.js Dann bist du beim nächsten Mal in 2 Sekunden fertig. -
Vor allem NANO Editor.... würg
Dann verwende vi, wenn du damit besser zurecht kommst...
Allerdings:
The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.4.0b1 depends on pillow==12.2.0
Da wird wohl pillow 12.2.0 gefordert.
Vor allem NANO Editor.... würg
Dann verwende vi, wenn du damit besser zurecht kommst...
Allerdings:
The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.4.0b1 depends on pillow==12.2.0
Da wird wohl pillow 12.2.0 gefordert.
Kasper... jetzt tut es. und jeder kann nachvollziehen wie man es selber fixen kann.
-
Ich hab mich brav bei ChatGPT bedankt und er meinte noch:
Mega 😄 freut mich richtig, dass es direkt funktioniert hat! War ein klassischer „hart verdrahtete Version vs. Realität“-Konflikt — sowas ist leider typisch bei solchen Adaptern. Kleiner Hinweis für später (wichtig!) Beim nächsten Update vom ioBroker-Adapter kann deine Änderung wieder überschrieben werden. Wenn das passiert und der Fehler wieder auftaucht → gleiche Stelle wieder fixen. Wenn du es „sauber“ machen willst Langfristig wäre sinnvoll: Issue im Adapter-Repo verfolgen (das wird ziemlich sicher gefixt) oder später auf eine Version updaten, wo das nicht mehr fest gepinnt ist Bonus-Tipp (typisch Bernd-Level 😎) Wenn du sowas öfter brauchst, kannst du dir einen kleinen Fix-Befehl bauen: sed -i "s/pillow', version: '==10.4.0'/pillow', version: '==11.3.0'/g" /opt/iobroker/node_modules/iobroker.esphome/main.js Dann bist du beim nächsten Mal in 2 Sekunden fertig.Und warum das ganze 'hart verdrahtet' ist steht im Issue drin:
https://github.com/DrozmotiX/ioBroker.esphome/issues/343
Das wird also eher nicht gefixt.
-
Vor allem NANO Editor.... würg
Dann verwende vi, wenn du damit besser zurecht kommst...
Allerdings:
The conflict is caused by: The user requested pillow==10.4.0 esphome 2026.4.0b1 depends on pillow==12.2.0
Da wird wohl pillow 12.2.0 gefordert.
Kasper... jetzt tut es. und jeder kann nachvollziehen wie man es selber fixen kann.
Kasper...
Die Beleidigung verbitte ich mir.
-
Ok, das war es noch nicht ganz. Im IOBroker Log kommt noch eine Warnung mit :
esphome has an invalid jsonConfig: [{"instancePath":"/items/devices/items/newDevicesTable","schemaPath":"#/patternProperties/%5E.%2B/allOf/30/then/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"doNotSave"},"message":"must NOT have additional properties"},{"instancePath":"/items/devices","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/11/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]Ist wohl nur ein Warning, der nicht weiter folgenschwer ist aber wen das stört (so wie mich) der kann es so beheben:
Was du tun solltest Öffne die Datei: sudo nano /opt/iobroker/node_modules/iobroker.esphome/admin/jsonConfig.json5 Dann geh zu den genannten Stellen und entferne jeweils diese Zeile: "doNotSave": true, Also wirklich nur diese Eigenschaft rausnehmen. In Nano schnell zu den Zeilen springen Mit STRG + _ Dann z. B. 224 eingeben und Enter. Das wiederholst du für: 224 237 337 Danach speichern und schließen STRG + O Enter STRG + X Nun den Adapter mit iobroker restart esphome neu starten.Das ist aber nur ein lokaler Fix. Wenn ein Update für ESPHome kommt, wird das wieder überschrieben.
Die ganz tollen Kasper können ja einen dauerhaften Fix veröffentlichen
-
Ok, das war es noch nicht ganz. Im IOBroker Log kommt noch eine Warnung mit :
esphome has an invalid jsonConfig: [{"instancePath":"/items/devices/items/newDevicesTable","schemaPath":"#/patternProperties/%5E.%2B/allOf/30/then/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"doNotSave"},"message":"must NOT have additional properties"},{"instancePath":"/items/devices","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/11/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]Ist wohl nur ein Warning, der nicht weiter folgenschwer ist aber wen das stört (so wie mich) der kann es so beheben:
Was du tun solltest Öffne die Datei: sudo nano /opt/iobroker/node_modules/iobroker.esphome/admin/jsonConfig.json5 Dann geh zu den genannten Stellen und entferne jeweils diese Zeile: "doNotSave": true, Also wirklich nur diese Eigenschaft rausnehmen. In Nano schnell zu den Zeilen springen Mit STRG + _ Dann z. B. 224 eingeben und Enter. Das wiederholst du für: 224 237 337 Danach speichern und schließen STRG + O Enter STRG + X Nun den Adapter mit iobroker restart esphome neu starten.Das ist aber nur ein lokaler Fix. Wenn ein Update für ESPHome kommt, wird das wieder überschrieben.
Die ganz tollen Kasper können ja einen dauerhaften Fix veröffentlichen
Die ganz tollen Kasper machen es ordentlich und bedienen die richtigen Dependencies im Adapter und veröffentlichen den dann und liefern nicht solche kruden Hacks ab.
Ein Issue beim Adapter würde das evtl. beschleunigen.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
494
Online32.8k
Benutzer82.7k
Themen1.3m
Beiträge