ESP Home Fehlermeldung
-
Auch bei mir funktioniert das Dashboard nicht, wobei ich da echt nicht mehr durchblicke, vor lauter Adapter löschen und neu runterziehen und installieren habe ich jetzt den Überblickt verloren.
Folgendes habe ich gemacht:
-alles was mit Adapter "esphom..." entfernt
-auf Beta-Rep umgestellt und aktualisiert
-nun Adapter esphome 0.7.0 hinzugefügt
"Edit: wieder auf stabel-rep umgestellt"
-in den Adaptereinstellungen folgendes angepasst:
aber mit keinerlei Browser auch nicht von anderen Rechner ist das Dasboard in irgend einer Version zu erreichen. Ich mag mich nicht erinnern, dass man da noch irgendwas ausserhalb von Iobroker installieren musste?
In der Übersicht wird die Kachel "Esphome" wieder angezeigt inkl. dem Link, dieser fürt aber zu "seiten-Ladefehler".
An welcher Stellschraube muss ich noch drehen? Irgendwann muss ich dann einfach auch meine yaml und ESP wieder rein kriegen, 2stk von 8 hat er gefunden, aber vom Rest fehlt jede Spur.
Weiss jemand, ob man das ESPhome auch ausserhalb Iobroker und ohne das ganze HomeAssist installieren kann? denn dann würde ich mir das ganze hier sparen und einfach einen weiteren LXC-Container machen und die Werte nur noch per MQTT einlesen?
-
Auch bei mir funktioniert das Dashboard nicht, wobei ich da echt nicht mehr durchblicke, vor lauter Adapter löschen und neu runterziehen und installieren habe ich jetzt den Überblickt verloren.
Folgendes habe ich gemacht:
-alles was mit Adapter "esphom..." entfernt
-auf Beta-Rep umgestellt und aktualisiert
-nun Adapter esphome 0.7.0 hinzugefügt
"Edit: wieder auf stabel-rep umgestellt"
-in den Adaptereinstellungen folgendes angepasst:aber mit keinerlei Browser auch nicht von anderen Rechner ist das Dasboard in irgend einer Version zu erreichen. Ich mag mich nicht erinnern, dass man da noch irgendwas ausserhalb von Iobroker installieren musste?
In der Übersicht wird die Kachel "Esphome" wieder angezeigt inkl. dem Link, dieser fürt aber zu "seiten-Ladefehler".
An welcher Stellschraube muss ich noch drehen? Irgendwann muss ich dann einfach auch meine yaml und ESP wieder rein kriegen, 2stk von 8 hat er gefunden, aber vom Rest fehlt jede Spur.
Weiss jemand, ob man das ESPhome auch ausserhalb Iobroker und ohne das ganze HomeAssist installieren kann? denn dann würde ich mir das ganze hier sparen und einfach einen weiteren LXC-Container machen und die Werte nur noch per MQTT einlesen?
und die Werte nur noch per MQTT einlesen?
Das funktioniert nach meinem Empfinden jetzt bereits. Wenn der ESP konfiguriert ist und sich am MqTT Broker verbindet, kann die gesamte ESPHOME Integration in IOB zerschossen sein. Das ist meine aktuelle Notlösung für Dinge die in der IOB Integration nicht mehr funktionieren. Nutze sie über Mqtt und dieser Funktion konnten dann auch Störungen der gesamten Integration nichts anhaben.
Bekommst dann natürlich eine Herausforderung wenn Du etwas konfigurieren möchtest.
-
und die Werte nur noch per MQTT einlesen?
Das funktioniert nach meinem Empfinden jetzt bereits. Wenn der ESP konfiguriert ist und sich am MqTT Broker verbindet, kann die gesamte ESPHOME Integration in IOB zerschossen sein. Das ist meine aktuelle Notlösung für Dinge die in der IOB Integration nicht mehr funktionieren. Nutze sie über Mqtt und dieser Funktion konnten dann auch Störungen der gesamten Integration nichts anhaben.
Bekommst dann natürlich eine Herausforderung wenn Du etwas konfigurieren möchtest.
-
Auch bei mir funktioniert das Dashboard nicht, wobei ich da echt nicht mehr durchblicke, vor lauter Adapter löschen und neu runterziehen und installieren habe ich jetzt den Überblickt verloren.
Folgendes habe ich gemacht:
-alles was mit Adapter "esphom..." entfernt
-auf Beta-Rep umgestellt und aktualisiert
-nun Adapter esphome 0.7.0 hinzugefügt
"Edit: wieder auf stabel-rep umgestellt"
-in den Adaptereinstellungen folgendes angepasst:aber mit keinerlei Browser auch nicht von anderen Rechner ist das Dasboard in irgend einer Version zu erreichen. Ich mag mich nicht erinnern, dass man da noch irgendwas ausserhalb von Iobroker installieren musste?
In der Übersicht wird die Kachel "Esphome" wieder angezeigt inkl. dem Link, dieser fürt aber zu "seiten-Ladefehler".
An welcher Stellschraube muss ich noch drehen? Irgendwann muss ich dann einfach auch meine yaml und ESP wieder rein kriegen, 2stk von 8 hat er gefunden, aber vom Rest fehlt jede Spur.
Weiss jemand, ob man das ESPhome auch ausserhalb Iobroker und ohne das ganze HomeAssist installieren kann? denn dann würde ich mir das ganze hier sparen und einfach einen weiteren LXC-Container machen und die Werte nur noch per MQTT einlesen?
Da war ja schon was installiert. Aber Neuinstallationen eines zuvor gar nicht installierten Adapters funktionieren nicht aus npm, wenn nicht gleichzeitig das Beta-Repo auch scharf ist.
Ok, danke für die Info.
Dieter hatte ja bereits was installiert, daher hätte es ja dann funktionieren müssen, aber egal.Noch als Hinweis: Aktuelle Versionen von npm führen solche Skripte erstmal nicht mehr aus. Das wird noch interessant werden.
Sorry, hab mich vielleicht schlecht ausgedrückt. Ist kein Migrationsskript im sinne von npm postinstall script. Sondern ganz normaler Adapter Code, der beim Adapterstart läuft und sich dann im native merkt, dass er schonmal ausgeführt wurde.
-
Auch bei mir funktioniert das Dashboard nicht, wobei ich da echt nicht mehr durchblicke, vor lauter Adapter löschen und neu runterziehen und installieren habe ich jetzt den Überblickt verloren.
Folgendes habe ich gemacht:
-alles was mit Adapter "esphom..." entfernt
-auf Beta-Rep umgestellt und aktualisiert
-nun Adapter esphome 0.7.0 hinzugefügt
"Edit: wieder auf stabel-rep umgestellt"
-in den Adaptereinstellungen folgendes angepasst:aber mit keinerlei Browser auch nicht von anderen Rechner ist das Dasboard in irgend einer Version zu erreichen. Ich mag mich nicht erinnern, dass man da noch irgendwas ausserhalb von Iobroker installieren musste?
In der Übersicht wird die Kachel "Esphome" wieder angezeigt inkl. dem Link, dieser fürt aber zu "seiten-Ladefehler".
An welcher Stellschraube muss ich noch drehen? Irgendwann muss ich dann einfach auch meine yaml und ESP wieder rein kriegen, 2stk von 8 hat er gefunden, aber vom Rest fehlt jede Spur.
Weiss jemand, ob man das ESPhome auch ausserhalb Iobroker und ohne das ganze HomeAssist installieren kann? denn dann würde ich mir das ganze hier sparen und einfach einen weiteren LXC-Container machen und die Werte nur noch per MQTT einlesen?
Folgendes habe ich gemacht:
Adapter Einstellungen schauen soweit schon mal gut aus, wenn du den iobroker admin per http://192.168.130.10:8082 aufrufst?
Ich mag mich nicht erinnern, dass man da noch irgendwas ausserhalb von Iobroker installieren musste?
Ganz früher war mal python Installation am System notwendig. Eventuell kannst dich an das noch erinnern. Aber schon lange nicht mehr notwendig, macht jetzt der Adapter alles automatisch.
-alles was mit Adapter "esphom..." entfernt
Also auch die Adapterinstanz gelöscht? Dann sind vermutlich die yamls weg. (Liegen in den normalen iobroker-data des adapters - Weis aber nicht genau wie iobroker handling hier aussieht. ob / wann beim Adapter löschen das auch geleert wird.)
Weiss jemand, ob man das ESPhome auch ausserhalb Iobroker und ohne das ganze HomeAssist installieren kann? denn dann würde ich mir das ganze hier sparen und einfach einen weiteren LXC-Container machen und die Werte nur noch per MQTT einlesen?
Einfach das "esphome" python Paket verwenden. Aber genau das macht der Adapter auch.
Alternativ sollts das auch als fertigen docker container geben.Aber wie Thomas schon schrieb, bitte mal logs.
-
Da war ja schon was installiert. Aber Neuinstallationen eines zuvor gar nicht installierten Adapters funktionieren nicht aus npm, wenn nicht gleichzeitig das Beta-Repo auch scharf ist.
Ok, danke für die Info.
Dieter hatte ja bereits was installiert, daher hätte es ja dann funktionieren müssen, aber egal.Noch als Hinweis: Aktuelle Versionen von npm führen solche Skripte erstmal nicht mehr aus. Das wird noch interessant werden.
Sorry, hab mich vielleicht schlecht ausgedrückt. Ist kein Migrationsskript im sinne von npm postinstall script. Sondern ganz normaler Adapter Code, der beim Adapterstart läuft und sich dann im native merkt, dass er schonmal ausgeführt wurde.
Also ich habe jetzt einfach so als Versuch mal rasch ein neuer Container mit Debian 13 erstellt und alles aktualisiert, danach mit dem curl den Iobroker installiert und gleich anschliessend via Beta-Repo den esp-Adapter 0.7.0 reingezogen.
Diese Meldungen wurden angezeigt:
$ iobroker add esphome auto --host iobversuch --debug Installing iobroker.esphome@0.7.0... (System call) npm warn skipping integrity check for git dependency ssh://git@github.com/SimonFischer04/autopy.git npm warn deprecated @mongodb-js/zstd@1.2.2: 1.x versions of this package are deprecated, please use 2.x instead npm warn deprecated @mongodb-js/zstd-linux-x64-gnu@1.2.2: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. added 119 packages in 17s128 packages are looking for funding run `npm fund` for details host.iobversuch install adapter esphome upload [18] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [17] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [11] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/connectionIssue.png img/connectionIssue.png image/png upload [9] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/dashboard.png img/dashboard.png image/png upload [8] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/deviceTabEmpty.png img/deviceTabEmpty.png image/png upload [6] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/flashFromThisComputer.png img/flashFromThisComputer.png image/png upload [1] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/tsconfig.json tsconfig.json application/json upload [0] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/words.js words.js application/javascript host.iobversuch object system.adapter.esphome.0 created Process exited with code 0Danach im Adapter folgendes eingestellt:
Aber das Dashboard geht immer noch nicht.
Kann es sein, dass in dem Paket nicht mehr alles dabei ist?
-
Also ich habe jetzt einfach so als Versuch mal rasch ein neuer Container mit Debian 13 erstellt und alles aktualisiert, danach mit dem curl den Iobroker installiert und gleich anschliessend via Beta-Repo den esp-Adapter 0.7.0 reingezogen.
Diese Meldungen wurden angezeigt:
$ iobroker add esphome auto --host iobversuch --debug Installing iobroker.esphome@0.7.0... (System call) npm warn skipping integrity check for git dependency ssh://git@github.com/SimonFischer04/autopy.git npm warn deprecated @mongodb-js/zstd@1.2.2: 1.x versions of this package are deprecated, please use 2.x instead npm warn deprecated @mongodb-js/zstd-linux-x64-gnu@1.2.2: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. added 119 packages in 17s128 packages are looking for funding run `npm fund` for details host.iobversuch install adapter esphome upload [18] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/i18n/pl/translations.json i18n/pl/translations.json application/json upload [17] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/i18n/pt/translations.json i18n/pt/translations.json application/json upload [11] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/connectionIssue.png img/connectionIssue.png image/png upload [9] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/dashboard.png img/dashboard.png image/png upload [8] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/deviceTabEmpty.png img/deviceTabEmpty.png image/png upload [6] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/flashFromThisComputer.png img/flashFromThisComputer.png image/png upload [1] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/tsconfig.json tsconfig.json application/json upload [0] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/words.js words.js application/javascript host.iobversuch object system.adapter.esphome.0 created Process exited with code 0Danach im Adapter folgendes eingestellt:
Aber das Dashboard geht immer noch nicht.
Kann es sein, dass in dem Paket nicht mehr alles dabei ist?
Danach im Adapter folgendes eingestellt
Siehe
bitte mal in den Adapter Einstellungen erstmal auf Dashboard version 2026.6.5 und pillow 12.3.0 gehen, scheint so als hätte esphome mal wieder was kaputt gemacht ...
Hab das ganze extra selber nochmal auf Testsystem getestet. Ja, mit latest ists auch kaputt. Aber nach Dashboard version 2026.6.5 und pillow 12.3.0 geht alles.
-
Vermute mal das Problem liegt an derem neuen device-builder ui, warum die neuen Versionen aktuell nicht mehr funktionieren.
Daher, wie du in deiner anderen Instanz korrekt gesetzt hast, erstmal auf 2026.6.5 bleiben.PS: Bei dem Thema würd dir dein externer extra lxc vermutlich auch nichts helfen. Wenn esphome da was kaputt macht und du auto-update an hast wird der sehr sicher genau gleich kaputt sein ...
-
Vermute mal das Problem liegt an derem neuen device-builder ui, warum die neuen Versionen aktuell nicht mehr funktionieren.
Daher, wie du in deiner anderen Instanz korrekt gesetzt hast, erstmal auf 2026.6.5 bleiben.PS: Bei dem Thema würd dir dein externer extra lxc vermutlich auch nichts helfen. Wenn esphome da was kaputt macht und du auto-update an hast wird der sehr sicher genau gleich kaputt sein ...
-
Auf der Testinstallation funktioniert es jetzt nach dem Einstellen der beiden Werte:
und zwar direkt aus über den link mit der Kachel wie auch mit einem anderen PC.
Dann kommt jetzt das "scharfe System" dran.
-
Das mit dem sepraten LXC nur für esphom, war einfach mal eine Idee, ich schätze es auch wenn alles beisammen ist und ich nicht zu viel verschiedene Systeme warten muss.
Also nochmals alles was ESP betrift auf dem scharfen System gelöscht, auf Beta-Rep gestellt und eine neu Instanz erstellt. Folgende Meldungen kammen dabei:
$ iobroker add esphome auto --host iobroker --debug Installing iobroker.esphome@0.7.0... (System call) npm warn skipping integrity check for git dependency ssh://git@github.com/SimonFischer04/autopy.git added 98 packages in 37s 244 packages are looking for funding run `npm fund` for details host.iobroker install adapter esphome upload [26] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/admin.d.ts admin.d.ts video/mp2t upload [8] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/deviceTabEmpty.png img/deviceTabEmpty.png image/png upload [0] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/words.js words.js application/javascript Updating objects from io-package.json for adapter "esphome" with version "0.7.0" host.iobroker object system.adapter.esphome.0.connected created host.iobroker Set default value of esphome.0.info.connection: false host.iobroker object system.adapter.esphome.0 created Process exited with code 0und in der Config wieder eingestellt:
Fazit: Dashboard nicht erreichbar
Ausgabe von iob diag:
========== Start marking the full check here =========== ```bash Script v.2026-06-06 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker Icon name: computer-container Chassis: container ☐ Virtualization: lxc Kernel: Linux 7.0.14-6-pve Architecture: x86-64 OS is similar to: model name : 12th Gen Intel(R) Core(TM) i5-12400 Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64bit System was installed 632 days ago (on 2024-10-31). Systemuptime and Load: 16:13:13 up 50 min, 0 users, load average: 0.09, 0.15, 0.14 CPU threads : 8 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Sun 2026-07-26 16:13:13 CEST Universal time: Sun 2026-07-26 14:13:13 UTC RTC time: n/a Time zone: Europe/Zurich (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': andi HOME=/home/andi GROUPS=andi sudo users iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev redis bluetooth *** DISPLAY-SERVER SETUP *** Display-Server: Unknown Display-Manager: Not found Desktop: Session: Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 12G 4.2G 7.1G 2.8M 1.3G 8.4G Swap: 8.6G 0B 8.6G Total: 21G 4.2G 15G Active iob-Instances: 38 12000 M total memory 3993 M used memory 4168 M active memory 849 M inactive memory 6776 M free memory 0 M buffer memory 1232 M swap cache 8191 M total swap 0 M used swap 8191 M free swap *** top - Table Of Processes *** top - 16:13:13 up 50 min, 0 users, load average: 0.09, 0.15, 0.14 Tasks: 68 total, 1 running, 67 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 1.2 sy, 0.0 ni, 98.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 12000.0 total, 6775.9 free, 3993.5 used, 1233.1 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 8006.5 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * sys-kernel-config.mount loaded failed failed Kernel Configuration File System Legend: LOAD -> Reflects whether the unit definition was properly loaded. ACTIVE -> The high-level unit activation state, i.e. generalization of SUB. SUB -> The low-level unit activation state, values depend on unit type. 2 loaded units listed. *** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--110--disk--0 ext4 196G 38G 149G 20% / none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 14G 0 14G 0% /dev/tty tmpfs tmpfs 16G 0 16G 0% /dev/shm tmpfs tmpfs 6.2G 136K 6.2G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 16G 2.6M 16G 1% /tmp Messages concerning filesystems in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--110--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 4.2G /var/ 3.4G /var/lib 3.0G /var/lib/mysql 2.8G /var/lib/mysql/iobroker 495M /var/log Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 58.3M in the file system. /opt/iobroker/backups: 9.8G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 8.2G /opt/iobroker/iobroker-data/ 5.6G /opt/iobroker/iobroker-data/history 1.3G /opt/iobroker/iobroker-data/files 999M /opt/iobroker/iobroker-data/esphome.0/.esphome 999M /opt/iobroker/iobroker-data/esphome.0 The five largest files in iobroker-data are: 92M /opt/iobroker/iobroker-data/objects.json.broken 87M /opt/iobroker/iobroker-data/objects.jsonl 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 32M /opt/iobroker/iobroker-data/states.jsonl 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' No nvbackup.json found. *** NodeJS-Installation *** /usr/bin/nodejs v22.23.1 /usr/bin/node v22.23.1 /usr/bin/npm 10.9.8 /usr/bin/npx 10.9.8 ✓ Node.js installation is correct nodejs: Installed: 22.23.1-1nodesource1 Candidate: 22.23.1-1nodesource1 Version table: *** 22.23.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.23.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.3-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 20.19.2+dfsg-1+deb13u2 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 500 http://security.debian.org trixie-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: No known Vulnerabilities detected! *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Hosts: iobroker iobroker (version: 7.2.2, hostname: iobroker , alive, uptime: 3001) Core adapters versions js-controller: 7.2.2 admin: 7.8.23 javascript: 9.0.18 nodejs modules from github: 2 | `-- autopy@1.1.1 (git+ssh://git@github.com/SimonFischer04/autopy.git#fbe016f35e13e335e1c44783a1e7273bbb2a08c1) +-- iobroker.time-switch@2.2.2 (git+ssh://git@github.com/walli545/ioBroker.time-switch.git#45b5addb484d270dcac6d1bfdb1a9f86b444d80e) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.alias-manager.0 : alias-manager : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.bestway.0 : bestway : iobroker - enabled + system.adapter.cloud.0 : cloud : iobroker - enabled + system.adapter.device-reminder.0 : device-reminder : iobroker - enabled system.adapter.devices.0 : devices : iobroker - disabled + system.adapter.discord.0 : discord : iobroker - enabled + system.adapter.discovery.0 : discovery : iobroker - enabled + system.adapter.echarts.0 : echarts : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled + system.adapter.enocean.0 : enocean : iobroker - enabled + system.adapter.esphome.0 : esphome : iobroker - enabled system.adapter.flot.0 : flot : iobroker - disabled + system.adapter.fronius.0 : fronius : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled system.adapter.icons-material-png.0 : icons-material-png : iobroker - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : iobroker - disabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.modbus.1 : modbus : iobroker - enabled system.adapter.modbus.2 : modbus : iobroker - disabled + system.adapter.modbus.4 : modbus : iobroker - enabled + system.adapter.modbus.5 : modbus : iobroker - enabled + system.adapter.modbus.6 : modbus : iobroker - enabled + system.adapter.modbus.7 : modbus : iobroker - enabled system.adapter.modbus.8 : modbus : iobroker - disabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 system.adapter.octoprint.0 : octoprint : iobroker - disabled system.adapter.octoprint.1 : octoprint : iobroker - disabled + system.adapter.operating-hours.0 : operating-hours : iobroker - enabled system.adapter.pid.0 : pid : iobroker - disabled system.adapter.proxmox.0 : proxmox : iobroker - disabled, port: 8006 + system.adapter.pvforecast.0 : pvforecast : iobroker - enabled + system.adapter.schedule-switcher.0 : schedule-switcher : iobroker - enabled system.adapter.shelly.0 : shelly : iobroker - disabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.shelly.2 : shelly : iobroker - disabled, port: 1888, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled + system.adapter.sql.0 : sql : iobroker - enabled, port: 3306 + system.adapter.statistics.0 : statistics : iobroker - enabled + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.time-switch.0 : time-switch : iobroker - enabled system.adapter.unifi.0 : unifi : iobroker - disabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : iobroker - disabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : iobroker - disabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: iobroker - disabled + system.adapter.vis-2.0 : vis-2 : iobroker - enabled system.adapter.vis-colorpicker.0 : vis-colorpicker : iobroker - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : iobroker - disabled system.adapter.vis-icontwo.0 : vis-icontwo : iobroker - disabled system.adapter.vis-inventwo.0 : vis-inventwo : iobroker - enabled system.adapter.vis-justgage.0 : vis-justgage : iobroker - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : iobroker - disabled system.adapter.vis-players.0 : vis-players : iobroker - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : iobroker - disabled system.adapter.vis-weather.0 : vis-weather : iobroker - disabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wiobrowser.0 : wiobrowser : iobroker - enabled, port: 5000 + system.adapter.wireless-mbus.1 : wireless-mbus : iobroker - enabled + system.adapter.wled.0 : wled : iobroker - enabled + system.adapter.ws.0 : ws : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.yr.0 : yr : iobroker - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sql.0 : sql : iobroker - enabled, port: 3306 + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wiobrowser.0 : wiobrowser : iobroker - enabled, port: 5000 + system.adapter.ws.0 : ws : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Stable (default) Upgrade policy: none Installed ioBroker-Adapters ┌─────────┬─────────────────────────────────────────┬──────────────────────────┬──────────┬────────────────┐ │ (index) │ id │ name │ version │ upgrade policy │ ├─────────┼─────────────────────────────────────────┼──────────────────────────┼──────────┼────────────────┤ │ 0 │ 'system.adapter.admin' │ 'admin' │ '7.8.23' │ 'none' │ │ 1 │ 'system.adapter.alias-manager' │ 'alias-manager' │ '2.1.0' │ 'none' │ │ 2 │ 'system.adapter.backitup' │ 'backitup' │ '3.3.17' │ 'none' │ │ 3 │ 'system.adapter.bestway' │ 'bestway' │ '0.0.5' │ 'none' │ │ 4 │ 'system.adapter.cloud' │ 'cloud' │ '6.0.1' │ 'none' │ │ 5 │ 'system.adapter.device-reminder' │ 'device-reminder' │ '3.0.0' │ 'none' │ │ 6 │ 'system.adapter.devices' │ 'devices' │ '1.2.14' │ 'none' │ │ 7 │ 'system.adapter.discord' │ 'discord' │ '2.6.1' │ 'none' │ │ 8 │ 'system.adapter.discovery' │ 'discovery' │ '5.0.0' │ 'none' │ │ 9 │ 'system.adapter.echarts' │ 'echarts' │ '3.1.0' │ 'none' │ │ 10 │ 'system.adapter.email' │ 'email' │ '2.0.4' │ 'none' │ │ 11 │ 'system.adapter.enocean' │ 'enocean' │ '0.9.4' │ 'none' │ │ 12 │ 'system.adapter.esphome' │ 'esphome' │ '0.7.0' │ 'none' │ │ 13 │ 'system.adapter.flot' │ 'flot' │ '1.12.0' │ 'none' │ │ 14 │ 'system.adapter.fronius' │ 'fronius' │ '2.2.0' │ 'none' │ │ 15 │ 'system.adapter.history' │ 'history' │ '4.0.0' │ 'none' │ │ 16 │ 'system.adapter.icons-material-png' │ 'icons-material-png' │ '0.1.0' │ 'none' │ │ 17 │ 'system.adapter.icons-mfd-svg' │ 'icons-mfd-svg' │ '1.2.0' │ 'none' │ │ 18 │ 'system.adapter.javascript' │ 'javascript' │ '9.0.18' │ 'none' │ │ 19 │ 'system.adapter.modbus' │ 'modbus' │ '8.0.3' │ 'none' │ │ 20 │ 'system.adapter.mqtt' │ 'mqtt' │ '6.1.4' │ 'none' │ │ 21 │ 'system.adapter.node-red' │ 'node-red' │ '6.0.7' │ 'none' │ │ 22 │ 'system.adapter.octoprint' │ 'octoprint' │ '5.1.0' │ 'none' │ │ 23 │ 'system.adapter.operating-hours' │ 'operating-hours' │ '1.5.1' │ 'none' │ │ 24 │ 'system.adapter.pid' │ 'pid' │ '1.1.3' │ 'none' │ │ 25 │ 'system.adapter.proxmox' │ 'proxmox' │ '2.6.1' │ 'none' │ │ 26 │ 'system.adapter.pvforecast' │ 'pvforecast' │ '6.1.0' │ 'none' │ │ 27 │ 'system.adapter.schedule-switcher' │ 'schedule-switcher' │ '0.2.0' │ 'none' │ │ 28 │ 'system.adapter.shelly' │ 'shelly' │ '10.6.1' │ 'none' │ │ 29 │ 'system.adapter.socketio' │ 'socketio' │ '7.1.3' │ 'none' │ │ 30 │ 'system.adapter.sourceanalytix' │ 'sourceanalytix' │ '0.4.14' │ 'none' │ │ 31 │ 'system.adapter.sql' │ 'sql' │ '3.0.1' │ 'none' │ │ 32 │ 'system.adapter.statistics' │ 'statistics' │ '5.0.0' │ 'none' │ │ 33 │ 'system.adapter.telegram' │ 'telegram' │ '4.1.0' │ 'none' │ │ 34 │ 'system.adapter.time-switch' │ 'time-switch' │ '2.2.2' │ 'none' │ │ 35 │ 'system.adapter.unifi' │ 'unifi' │ '0.7.0' │ 'none' │ │ 36 │ 'system.adapter.vis' │ 'vis' │ '1.5.6' │ 'none' │ │ 37 │ 'system.adapter.vis-2' │ 'vis-2' │ '2.13.8' │ 'none' │ │ 38 │ 'system.adapter.vis-2-widgets-energy' │ 'vis-2-widgets-energy' │ '1.0.2' │ 'none' │ │ 39 │ 'system.adapter.vis-2-widgets-gauges' │ 'vis-2-widgets-gauges' │ '2.0.2' │ 'none' │ │ 40 │ 'system.adapter.vis-2-widgets-material' │ 'vis-2-widgets-material' │ '1.6.1' │ 'none' │ │ 41 │ 'system.adapter.vis-colorpicker' │ 'vis-colorpicker' │ '2.1.0' │ 'none' │ │ 42 │ 'system.adapter.vis-hqwidgets' │ 'vis-hqwidgets' │ '1.6.1' │ 'none' │ │ 43 │ 'system.adapter.vis-icontwo' │ 'vis-icontwo' │ '2.11.6' │ 'none' │ │ 44 │ 'system.adapter.vis-inventwo' │ 'vis-inventwo' │ '4.1.1' │ 'none' │ │ 45 │ 'system.adapter.vis-justgage' │ 'vis-justgage' │ '2.1.7' │ 'none' │ │ 46 │ 'system.adapter.vis-materialdesign' │ 'vis-materialdesign' │ '0.5.9' │ 'none' │ │ 47 │ 'system.adapter.vis-players' │ 'vis-players' │ '0.1.6' │ 'none' │ │ 48 │ 'system.adapter.vis-timeandweather' │ 'vis-timeandweather' │ '1.2.2' │ 'none' │ │ 49 │ 'system.adapter.vis-weather' │ 'vis-weather' │ '2.5.13' │ 'none' │ │ 50 │ 'system.adapter.web' │ 'web' │ '8.0.0' │ 'none' │ │ 51 │ 'system.adapter.wiobrowser' │ 'wiobrowser' │ '2.0.2' │ 'none' │ │ 52 │ 'system.adapter.wireless-mbus' │ 'wireless-mbus' │ '0.10.2' │ 'none' │ │ 53 │ 'system.adapter.wled' │ 'wled' │ '0.7.3' │ 'none' │ │ 54 │ 'system.adapter.ws' │ 'ws' │ '4.1.0' │ 'none' │ │ 55 │ 'system.adapter.yr' │ 'yr' │ '5.3.0' │ 'none' │ └─────────┴─────────────────────────────────────────┴──────────────────────────┴──────────┴────────────────┘ ioBroker-Adapter Versions and update status Used repository: Stable (default) Adapter "admin" : 7.8.23 , installed 7.8.23 Adapter "alias-manager": 2.1.0 , installed 2.1.0 Adapter "backitup" : 3.3.17 , installed 3.3.17 Adapter "bestway" : 0.0.4 , installed 0.0.5 Adapter "cloud" : 6.0.1 , installed 6.0.1 Adapter "device-reminder": 3.1.2 , installed 3.0.0 [Updatable] Adapter "devices" : 1.2.14 , installed 1.2.14 Adapter "discord" : 2.6.1 , installed 2.6.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "echarts" : 3.1.0 , installed 3.1.0 Adapter "email" : 2.0.4 , installed 2.0.4 Adapter "fronius" : 2.2.0 , installed 2.2.0 Adapter "history" : 4.0.0 , installed 4.0.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.2.2 , installed 7.2.2 Adapter "modbus" : 8.0.3 , installed 8.0.3 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "node-red" : 6.0.7 , installed 6.0.7 Adapter "octoprint" : 5.1.0 , installed 5.1.0 Adapter "operating-hours": 1.5.1 , installed 1.5.1 Adapter "pid" : 1.1.3 , installed 1.1.3 Adapter "proxmox" : 2.6.1 , installed 2.6.1 Adapter "pvforecast" : 6.1.0 , installed 6.1.0 Adapter "schedule-switcher": 0.2.0, installed 0.2.0 Adapter "shelly" : 10.6.1 , installed 10.6.1 Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "statistics" : 5.0.0 , installed 5.0.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.13.8 , installed 2.13.8 Adapter "vis-2-widgets-energy": 1.0.2, installed 1.0.2 Adapter "vis-2-widgets-gauges": 2.0.2, installed 2.0.2 Adapter "vis-2-widgets-material": 1.6.1, installed 1.6.1 Adapter "vis-colorpicker": 2.1.0 , installed 2.1.0 Adapter "vis-hqwidgets": 1.6.1 , installed 1.6.1 Adapter "vis-icontwo" : 2.11.6 , installed 2.11.6 Adapter "vis-inventwo" : 4.1.1 , installed 4.1.1 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-players" : 0.1.6 , installed 0.1.6 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vis-weather" : 2.5.13 , installed 2.5.13 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "wiobrowser" : 2.0.2 , installed 2.0.2 Adapter "wireless-mbus": 0.10.2 , installed 0.10.2 Adapter "wled" : 0.7.3 , installed 0.7.3 Adapter "ws" : 4.1.0 , installed 4.1.0 Adapter "yr" : 5.3.0 , installed 5.3.0 Objects and States Please stand by - This may take a while Objects: 17205 States: 60107 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org trixie-security InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess udp UNCONN 0 0 0.0.0.0:bootpc 0.0.0.0:* users:(("dhclient",pid=114,fd=7)) udp UNCONN 0 0 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=149,fd=5),("systemd",pid=1,fd=36)) udp UNCONN 0 0 192.168.130.10:ntp 0.0.0.0:* users:(("ntpd",pid=234,fd=19)) udp UNCONN 0 0 127.0.0.1:ntp 0.0.0.0:* users:(("ntpd",pid=234,fd=18)) udp UNCONN 0 0 0.0.0.0:ntp 0.0.0.0:* users:(("ntpd",pid=234,fd=17)) udp UNCONN 0 0 0.0.0.0:mdns 0.0.0.0:* users:(("io.esphome.0",pid=1946,fd=35)) udp UNCONN 0 0 0.0.0.0:mdns 0.0.0.0:* users:(("io.wled.0",pid=1137,fd=22)) udp UNCONN 0 0 [::]:sunrpc [::]:* users:(("rpcbind",pid=149,fd=7),("systemd",pid=1,fd=38)) udp UNCONN 0 0 [fe80::be24:11ff:fe09:4aff]%eth0:ntp [::]:* users:(("ntpd",pid=234,fd=22)) udp UNCONN 0 0 [::1]:ntp [::]:* users:(("ntpd",pid=234,fd=20)) udp UNCONN 0 0 [::]:ntp [::]:* users:(("ntpd",pid=234,fd=16)) tcp LISTEN 0 100 127.0.0.1:smtp 0.0.0.0:* users:(("master",pid=435,fd=13)) tcp LISTEN 0 511 127.0.0.1:redis 0.0.0.0:* users:(("redis-server",pid=216,fd=8)) tcp LISTEN 0 4096 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=149,fd=4),("systemd",pid=1,fd=35)) tcp LISTEN 0 511 0.0.0.0:502 0.0.0.0:* users:(("io.modbus.1",pid=906,fd=30)) tcp LISTEN 0 511 0.0.0.0:1884 0.0.0.0:* users:(("io.mqtt.0",pid=889,fd=35)) tcp LISTEN 0 511 0.0.0.0:1880 0.0.0.0:* users:(("node-red",pid=618,fd=24)) tcp LISTEN 0 511 0.0.0.0:1882 0.0.0.0:* users:(("io.shelly.1",pid=733,fd=50)) tcp LISTEN 0 511 0.0.0.0:1883 0.0.0.0:* users:(("io.mqtt.1",pid=749,fd=35)) tcp LISTEN 0 511 *:8084 *:* users:(("io.ws.0",pid=1069,fd=34)) tcp LISTEN 0 511 *:tproxy *:* users:(("io.admin.0",pid=487,fd=39)) tcp LISTEN 0 511 *:8082 *:* users:(("io.web.0",pid=1103,fd=35)) tcp LISTEN 0 100 [::1]:smtp [::]:* users:(("master",pid=435,fd=14)) tcp LISTEN 0 4096 *:mysql *:* users:(("mariadbd",pid=313,fd=5),("systemd",pid=1,fd=59)) tcp LISTEN 0 511 [::1]:redis [::]:* users:(("redis-server",pid=216,fd=9)) tcp LISTEN 0 4096 [::]:sunrpc [::]:* users:(("rpcbind",pid=149,fd=6),("systemd",pid=1,fd=37)) tcp LISTEN 0 4096 *:ssh *:* users:(("sshd",pid=250,fd=3),("systemd",pid=1,fd=65)) *** Log File - Last 25 Lines *** Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 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 processTicksAndRejections (node:internal/process/task_queues:103:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:197:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:280:34) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:73:13) 2026-07-26 16:10:59.530 - info: esphome.0 (1946) New ESPHome Device discovered: heizung.local on 192.168.130.130 2026-07-26 16:10:59.530 - info: esphome.0 (1946) New ESPHome Device discovered: co2sensor.local on 192.168.130.132 2026-07-26 16:11:37.357 - debug: bestway.0 (1254) {"did":"0PEGsasaDg9C1LadNvpBjO","updated_at":1785075060,"attr":{"E19":0,"E18":0,"E32":0,"E31":0,"E30":0,"E11":0,"E10":0,"E13":0,"E12":0,"E15":0,"E14":0,"E17":0,"E16":0,"word5":190,"word4":0,"word7":33,"word6":0,"word1":0,"word0":0,"E29":0,"word2":491,"option6":10244,"ver":1126,"E22":0,"jet":0,"E23":0,"power":1,"Tnow":33,"option7":10260,"option4":0,"option5":27175,"option2":0,"option3":30,"option0":59940,"option1":59940,"E24":0,"E25":0,"E26":0,"E27":0,"E20":0,"E21":0,"E08":0,"E09":0,"E06":0,"E07":0,"E04":0,"E05":0,"E02":0,"E03":0,"E01":0,"bit7":1,"heat":3,"Tunit":1,"wave":0,"word3":0,"Tset":36,"filter":2,"E28":0,"bit6":1,"bit5":0,"bit4":0,"bit3":0,"bit2":1}} ============= Mark until here for C&P ============= iob diag has finished.und ja ich arbeite daran alle die github Adapter zu entfernen. Auch ein reboot des ganze LXC hat bisher zu keine Resultat geführt. Eigentlich habe ich nirgends "auto-update" an, nur habe ich vor kurzen im Debian 13 ein upgrade gefahren, aber das scheint ja nicht das Problem zu sein, den im Test-LXC ist ja auch theoretisch das gleiche Debian drin.
-
Das mit dem sepraten LXC nur für esphom, war einfach mal eine Idee, ich schätze es auch wenn alles beisammen ist und ich nicht zu viel verschiedene Systeme warten muss.
Also nochmals alles was ESP betrift auf dem scharfen System gelöscht, auf Beta-Rep gestellt und eine neu Instanz erstellt. Folgende Meldungen kammen dabei:
$ iobroker add esphome auto --host iobroker --debug Installing iobroker.esphome@0.7.0... (System call) npm warn skipping integrity check for git dependency ssh://git@github.com/SimonFischer04/autopy.git added 98 packages in 37s 244 packages are looking for funding run `npm fund` for details host.iobroker install adapter esphome upload [26] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/admin.d.ts admin.d.ts video/mp2t upload [8] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/deviceTabEmpty.png img/deviceTabEmpty.png image/png upload [0] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/words.js words.js application/javascript Updating objects from io-package.json for adapter "esphome" with version "0.7.0" host.iobroker object system.adapter.esphome.0.connected created host.iobroker Set default value of esphome.0.info.connection: false host.iobroker object system.adapter.esphome.0 created Process exited with code 0und in der Config wieder eingestellt:
Fazit: Dashboard nicht erreichbar
Ausgabe von iob diag:
========== Start marking the full check here =========== ```bash Script v.2026-06-06 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker Icon name: computer-container Chassis: container ☐ Virtualization: lxc Kernel: Linux 7.0.14-6-pve Architecture: x86-64 OS is similar to: model name : 12th Gen Intel(R) Core(TM) i5-12400 Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64bit System was installed 632 days ago (on 2024-10-31). Systemuptime and Load: 16:13:13 up 50 min, 0 users, load average: 0.09, 0.15, 0.14 CPU threads : 8 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Sun 2026-07-26 16:13:13 CEST Universal time: Sun 2026-07-26 14:13:13 UTC RTC time: n/a Time zone: Europe/Zurich (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': andi HOME=/home/andi GROUPS=andi sudo users iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev redis bluetooth *** DISPLAY-SERVER SETUP *** Display-Server: Unknown Display-Manager: Not found Desktop: Session: Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 12G 4.2G 7.1G 2.8M 1.3G 8.4G Swap: 8.6G 0B 8.6G Total: 21G 4.2G 15G Active iob-Instances: 38 12000 M total memory 3993 M used memory 4168 M active memory 849 M inactive memory 6776 M free memory 0 M buffer memory 1232 M swap cache 8191 M total swap 0 M used swap 8191 M free swap *** top - Table Of Processes *** top - 16:13:13 up 50 min, 0 users, load average: 0.09, 0.15, 0.14 Tasks: 68 total, 1 running, 67 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 1.2 sy, 0.0 ni, 98.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 12000.0 total, 6775.9 free, 3993.5 used, 1233.1 buff/cache MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 8006.5 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * sys-kernel-config.mount loaded failed failed Kernel Configuration File System Legend: LOAD -> Reflects whether the unit definition was properly loaded. ACTIVE -> The high-level unit activation state, i.e. generalization of SUB. SUB -> The low-level unit activation state, values depend on unit type. 2 loaded units listed. *** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--110--disk--0 ext4 196G 38G 149G 20% / none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 14G 0 14G 0% /dev/tty tmpfs tmpfs 16G 0 16G 0% /dev/shm tmpfs tmpfs 6.2G 136K 6.2G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 16G 2.6M 16G 1% /tmp Messages concerning filesystems in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--110--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 4.2G /var/ 3.4G /var/lib 3.0G /var/lib/mysql 2.8G /var/lib/mysql/iobroker 495M /var/log Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 58.3M in the file system. /opt/iobroker/backups: 9.8G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 8.2G /opt/iobroker/iobroker-data/ 5.6G /opt/iobroker/iobroker-data/history 1.3G /opt/iobroker/iobroker-data/files 999M /opt/iobroker/iobroker-data/esphome.0/.esphome 999M /opt/iobroker/iobroker-data/esphome.0 The five largest files in iobroker-data are: 92M /opt/iobroker/iobroker-data/objects.json.broken 87M /opt/iobroker/iobroker-data/objects.jsonl 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 32M /opt/iobroker/iobroker-data/states.jsonl 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' No nvbackup.json found. *** NodeJS-Installation *** /usr/bin/nodejs v22.23.1 /usr/bin/node v22.23.1 /usr/bin/npm 10.9.8 /usr/bin/npx 10.9.8 ✓ Node.js installation is correct nodejs: Installed: 22.23.1-1nodesource1 Candidate: 22.23.1-1nodesource1 Version table: *** 22.23.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.23.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.3-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.2-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.22.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.21.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 20.19.2+dfsg-1+deb13u2 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 500 http://security.debian.org trixie-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: No known Vulnerabilities detected! *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Hosts: iobroker iobroker (version: 7.2.2, hostname: iobroker , alive, uptime: 3001) Core adapters versions js-controller: 7.2.2 admin: 7.8.23 javascript: 9.0.18 nodejs modules from github: 2 | `-- autopy@1.1.1 (git+ssh://git@github.com/SimonFischer04/autopy.git#fbe016f35e13e335e1c44783a1e7273bbb2a08c1) +-- iobroker.time-switch@2.2.2 (git+ssh://git@github.com/walli545/ioBroker.time-switch.git#45b5addb484d270dcac6d1bfdb1a9f86b444d80e) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.alias-manager.0 : alias-manager : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.bestway.0 : bestway : iobroker - enabled + system.adapter.cloud.0 : cloud : iobroker - enabled + system.adapter.device-reminder.0 : device-reminder : iobroker - enabled system.adapter.devices.0 : devices : iobroker - disabled + system.adapter.discord.0 : discord : iobroker - enabled + system.adapter.discovery.0 : discovery : iobroker - enabled + system.adapter.echarts.0 : echarts : iobroker - enabled + system.adapter.email.0 : email : iobroker - enabled + system.adapter.enocean.0 : enocean : iobroker - enabled + system.adapter.esphome.0 : esphome : iobroker - enabled system.adapter.flot.0 : flot : iobroker - disabled + system.adapter.fronius.0 : fronius : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled system.adapter.icons-material-png.0 : icons-material-png : iobroker - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : iobroker - disabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.modbus.1 : modbus : iobroker - enabled system.adapter.modbus.2 : modbus : iobroker - disabled + system.adapter.modbus.4 : modbus : iobroker - enabled + system.adapter.modbus.5 : modbus : iobroker - enabled + system.adapter.modbus.6 : modbus : iobroker - enabled + system.adapter.modbus.7 : modbus : iobroker - enabled system.adapter.modbus.8 : modbus : iobroker - disabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 system.adapter.octoprint.0 : octoprint : iobroker - disabled system.adapter.octoprint.1 : octoprint : iobroker - disabled + system.adapter.operating-hours.0 : operating-hours : iobroker - enabled system.adapter.pid.0 : pid : iobroker - disabled system.adapter.proxmox.0 : proxmox : iobroker - disabled, port: 8006 + system.adapter.pvforecast.0 : pvforecast : iobroker - enabled + system.adapter.schedule-switcher.0 : schedule-switcher : iobroker - enabled system.adapter.shelly.0 : shelly : iobroker - disabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.shelly.2 : shelly : iobroker - disabled, port: 1888, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled + system.adapter.sql.0 : sql : iobroker - enabled, port: 3306 + system.adapter.statistics.0 : statistics : iobroker - enabled + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.time-switch.0 : time-switch : iobroker - enabled system.adapter.unifi.0 : unifi : iobroker - disabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : iobroker - disabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : iobroker - disabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: iobroker - disabled + system.adapter.vis-2.0 : vis-2 : iobroker - enabled system.adapter.vis-colorpicker.0 : vis-colorpicker : iobroker - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : iobroker - disabled system.adapter.vis-icontwo.0 : vis-icontwo : iobroker - disabled system.adapter.vis-inventwo.0 : vis-inventwo : iobroker - enabled system.adapter.vis-justgage.0 : vis-justgage : iobroker - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : iobroker - disabled system.adapter.vis-players.0 : vis-players : iobroker - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : iobroker - disabled system.adapter.vis-weather.0 : vis-weather : iobroker - disabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wiobrowser.0 : wiobrowser : iobroker - enabled, port: 5000 + system.adapter.wireless-mbus.1 : wireless-mbus : iobroker - enabled + system.adapter.wled.0 : wled : iobroker - enabled + system.adapter.ws.0 : ws : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin system.adapter.yr.0 : yr : iobroker - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sql.0 : sql : iobroker - enabled, port: 3306 + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wiobrowser.0 : wiobrowser : iobroker - enabled, port: 5000 + system.adapter.ws.0 : ws : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Stable (default) Upgrade policy: none Installed ioBroker-Adapters ┌─────────┬─────────────────────────────────────────┬──────────────────────────┬──────────┬────────────────┐ │ (index) │ id │ name │ version │ upgrade policy │ ├─────────┼─────────────────────────────────────────┼──────────────────────────┼──────────┼────────────────┤ │ 0 │ 'system.adapter.admin' │ 'admin' │ '7.8.23' │ 'none' │ │ 1 │ 'system.adapter.alias-manager' │ 'alias-manager' │ '2.1.0' │ 'none' │ │ 2 │ 'system.adapter.backitup' │ 'backitup' │ '3.3.17' │ 'none' │ │ 3 │ 'system.adapter.bestway' │ 'bestway' │ '0.0.5' │ 'none' │ │ 4 │ 'system.adapter.cloud' │ 'cloud' │ '6.0.1' │ 'none' │ │ 5 │ 'system.adapter.device-reminder' │ 'device-reminder' │ '3.0.0' │ 'none' │ │ 6 │ 'system.adapter.devices' │ 'devices' │ '1.2.14' │ 'none' │ │ 7 │ 'system.adapter.discord' │ 'discord' │ '2.6.1' │ 'none' │ │ 8 │ 'system.adapter.discovery' │ 'discovery' │ '5.0.0' │ 'none' │ │ 9 │ 'system.adapter.echarts' │ 'echarts' │ '3.1.0' │ 'none' │ │ 10 │ 'system.adapter.email' │ 'email' │ '2.0.4' │ 'none' │ │ 11 │ 'system.adapter.enocean' │ 'enocean' │ '0.9.4' │ 'none' │ │ 12 │ 'system.adapter.esphome' │ 'esphome' │ '0.7.0' │ 'none' │ │ 13 │ 'system.adapter.flot' │ 'flot' │ '1.12.0' │ 'none' │ │ 14 │ 'system.adapter.fronius' │ 'fronius' │ '2.2.0' │ 'none' │ │ 15 │ 'system.adapter.history' │ 'history' │ '4.0.0' │ 'none' │ │ 16 │ 'system.adapter.icons-material-png' │ 'icons-material-png' │ '0.1.0' │ 'none' │ │ 17 │ 'system.adapter.icons-mfd-svg' │ 'icons-mfd-svg' │ '1.2.0' │ 'none' │ │ 18 │ 'system.adapter.javascript' │ 'javascript' │ '9.0.18' │ 'none' │ │ 19 │ 'system.adapter.modbus' │ 'modbus' │ '8.0.3' │ 'none' │ │ 20 │ 'system.adapter.mqtt' │ 'mqtt' │ '6.1.4' │ 'none' │ │ 21 │ 'system.adapter.node-red' │ 'node-red' │ '6.0.7' │ 'none' │ │ 22 │ 'system.adapter.octoprint' │ 'octoprint' │ '5.1.0' │ 'none' │ │ 23 │ 'system.adapter.operating-hours' │ 'operating-hours' │ '1.5.1' │ 'none' │ │ 24 │ 'system.adapter.pid' │ 'pid' │ '1.1.3' │ 'none' │ │ 25 │ 'system.adapter.proxmox' │ 'proxmox' │ '2.6.1' │ 'none' │ │ 26 │ 'system.adapter.pvforecast' │ 'pvforecast' │ '6.1.0' │ 'none' │ │ 27 │ 'system.adapter.schedule-switcher' │ 'schedule-switcher' │ '0.2.0' │ 'none' │ │ 28 │ 'system.adapter.shelly' │ 'shelly' │ '10.6.1' │ 'none' │ │ 29 │ 'system.adapter.socketio' │ 'socketio' │ '7.1.3' │ 'none' │ │ 30 │ 'system.adapter.sourceanalytix' │ 'sourceanalytix' │ '0.4.14' │ 'none' │ │ 31 │ 'system.adapter.sql' │ 'sql' │ '3.0.1' │ 'none' │ │ 32 │ 'system.adapter.statistics' │ 'statistics' │ '5.0.0' │ 'none' │ │ 33 │ 'system.adapter.telegram' │ 'telegram' │ '4.1.0' │ 'none' │ │ 34 │ 'system.adapter.time-switch' │ 'time-switch' │ '2.2.2' │ 'none' │ │ 35 │ 'system.adapter.unifi' │ 'unifi' │ '0.7.0' │ 'none' │ │ 36 │ 'system.adapter.vis' │ 'vis' │ '1.5.6' │ 'none' │ │ 37 │ 'system.adapter.vis-2' │ 'vis-2' │ '2.13.8' │ 'none' │ │ 38 │ 'system.adapter.vis-2-widgets-energy' │ 'vis-2-widgets-energy' │ '1.0.2' │ 'none' │ │ 39 │ 'system.adapter.vis-2-widgets-gauges' │ 'vis-2-widgets-gauges' │ '2.0.2' │ 'none' │ │ 40 │ 'system.adapter.vis-2-widgets-material' │ 'vis-2-widgets-material' │ '1.6.1' │ 'none' │ │ 41 │ 'system.adapter.vis-colorpicker' │ 'vis-colorpicker' │ '2.1.0' │ 'none' │ │ 42 │ 'system.adapter.vis-hqwidgets' │ 'vis-hqwidgets' │ '1.6.1' │ 'none' │ │ 43 │ 'system.adapter.vis-icontwo' │ 'vis-icontwo' │ '2.11.6' │ 'none' │ │ 44 │ 'system.adapter.vis-inventwo' │ 'vis-inventwo' │ '4.1.1' │ 'none' │ │ 45 │ 'system.adapter.vis-justgage' │ 'vis-justgage' │ '2.1.7' │ 'none' │ │ 46 │ 'system.adapter.vis-materialdesign' │ 'vis-materialdesign' │ '0.5.9' │ 'none' │ │ 47 │ 'system.adapter.vis-players' │ 'vis-players' │ '0.1.6' │ 'none' │ │ 48 │ 'system.adapter.vis-timeandweather' │ 'vis-timeandweather' │ '1.2.2' │ 'none' │ │ 49 │ 'system.adapter.vis-weather' │ 'vis-weather' │ '2.5.13' │ 'none' │ │ 50 │ 'system.adapter.web' │ 'web' │ '8.0.0' │ 'none' │ │ 51 │ 'system.adapter.wiobrowser' │ 'wiobrowser' │ '2.0.2' │ 'none' │ │ 52 │ 'system.adapter.wireless-mbus' │ 'wireless-mbus' │ '0.10.2' │ 'none' │ │ 53 │ 'system.adapter.wled' │ 'wled' │ '0.7.3' │ 'none' │ │ 54 │ 'system.adapter.ws' │ 'ws' │ '4.1.0' │ 'none' │ │ 55 │ 'system.adapter.yr' │ 'yr' │ '5.3.0' │ 'none' │ └─────────┴─────────────────────────────────────────┴──────────────────────────┴──────────┴────────────────┘ ioBroker-Adapter Versions and update status Used repository: Stable (default) Adapter "admin" : 7.8.23 , installed 7.8.23 Adapter "alias-manager": 2.1.0 , installed 2.1.0 Adapter "backitup" : 3.3.17 , installed 3.3.17 Adapter "bestway" : 0.0.4 , installed 0.0.5 Adapter "cloud" : 6.0.1 , installed 6.0.1 Adapter "device-reminder": 3.1.2 , installed 3.0.0 [Updatable] Adapter "devices" : 1.2.14 , installed 1.2.14 Adapter "discord" : 2.6.1 , installed 2.6.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "echarts" : 3.1.0 , installed 3.1.0 Adapter "email" : 2.0.4 , installed 2.0.4 Adapter "fronius" : 2.2.0 , installed 2.2.0 Adapter "history" : 4.0.0 , installed 4.0.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.2.2 , installed 7.2.2 Adapter "modbus" : 8.0.3 , installed 8.0.3 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "node-red" : 6.0.7 , installed 6.0.7 Adapter "octoprint" : 5.1.0 , installed 5.1.0 Adapter "operating-hours": 1.5.1 , installed 1.5.1 Adapter "pid" : 1.1.3 , installed 1.1.3 Adapter "proxmox" : 2.6.1 , installed 2.6.1 Adapter "pvforecast" : 6.1.0 , installed 6.1.0 Adapter "schedule-switcher": 0.2.0, installed 0.2.0 Adapter "shelly" : 10.6.1 , installed 10.6.1 Adapter "socketio" : 7.1.3 , installed 7.1.3 Adapter "sql" : 3.0.1 , installed 3.0.1 Adapter "statistics" : 5.0.0 , installed 5.0.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "unifi" : 0.7.0 , installed 0.7.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.13.8 , installed 2.13.8 Adapter "vis-2-widgets-energy": 1.0.2, installed 1.0.2 Adapter "vis-2-widgets-gauges": 2.0.2, installed 2.0.2 Adapter "vis-2-widgets-material": 1.6.1, installed 1.6.1 Adapter "vis-colorpicker": 2.1.0 , installed 2.1.0 Adapter "vis-hqwidgets": 1.6.1 , installed 1.6.1 Adapter "vis-icontwo" : 2.11.6 , installed 2.11.6 Adapter "vis-inventwo" : 4.1.1 , installed 4.1.1 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-players" : 0.1.6 , installed 0.1.6 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vis-weather" : 2.5.13 , installed 2.5.13 Adapter "web" : 8.0.0 , installed 8.0.0 Adapter "wiobrowser" : 2.0.2 , installed 2.0.2 Adapter "wireless-mbus": 0.10.2 , installed 0.10.2 Adapter "wled" : 0.7.3 , installed 0.7.3 Adapter "ws" : 4.1.0 , installed 4.1.0 Adapter "yr" : 5.3.0 , installed 5.3.0 Objects and States Please stand by - This may take a while Objects: 17205 States: 60107 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org trixie-security InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Listening Ports *** Netid State Recv-Q Send-Q Local Address:Port Peer Address:PortProcess udp UNCONN 0 0 0.0.0.0:bootpc 0.0.0.0:* users:(("dhclient",pid=114,fd=7)) udp UNCONN 0 0 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=149,fd=5),("systemd",pid=1,fd=36)) udp UNCONN 0 0 192.168.130.10:ntp 0.0.0.0:* users:(("ntpd",pid=234,fd=19)) udp UNCONN 0 0 127.0.0.1:ntp 0.0.0.0:* users:(("ntpd",pid=234,fd=18)) udp UNCONN 0 0 0.0.0.0:ntp 0.0.0.0:* users:(("ntpd",pid=234,fd=17)) udp UNCONN 0 0 0.0.0.0:mdns 0.0.0.0:* users:(("io.esphome.0",pid=1946,fd=35)) udp UNCONN 0 0 0.0.0.0:mdns 0.0.0.0:* users:(("io.wled.0",pid=1137,fd=22)) udp UNCONN 0 0 [::]:sunrpc [::]:* users:(("rpcbind",pid=149,fd=7),("systemd",pid=1,fd=38)) udp UNCONN 0 0 [fe80::be24:11ff:fe09:4aff]%eth0:ntp [::]:* users:(("ntpd",pid=234,fd=22)) udp UNCONN 0 0 [::1]:ntp [::]:* users:(("ntpd",pid=234,fd=20)) udp UNCONN 0 0 [::]:ntp [::]:* users:(("ntpd",pid=234,fd=16)) tcp LISTEN 0 100 127.0.0.1:smtp 0.0.0.0:* users:(("master",pid=435,fd=13)) tcp LISTEN 0 511 127.0.0.1:redis 0.0.0.0:* users:(("redis-server",pid=216,fd=8)) tcp LISTEN 0 4096 0.0.0.0:sunrpc 0.0.0.0:* users:(("rpcbind",pid=149,fd=4),("systemd",pid=1,fd=35)) tcp LISTEN 0 511 0.0.0.0:502 0.0.0.0:* users:(("io.modbus.1",pid=906,fd=30)) tcp LISTEN 0 511 0.0.0.0:1884 0.0.0.0:* users:(("io.mqtt.0",pid=889,fd=35)) tcp LISTEN 0 511 0.0.0.0:1880 0.0.0.0:* users:(("node-red",pid=618,fd=24)) tcp LISTEN 0 511 0.0.0.0:1882 0.0.0.0:* users:(("io.shelly.1",pid=733,fd=50)) tcp LISTEN 0 511 0.0.0.0:1883 0.0.0.0:* users:(("io.mqtt.1",pid=749,fd=35)) tcp LISTEN 0 511 *:8084 *:* users:(("io.ws.0",pid=1069,fd=34)) tcp LISTEN 0 511 *:tproxy *:* users:(("io.admin.0",pid=487,fd=39)) tcp LISTEN 0 511 *:8082 *:* users:(("io.web.0",pid=1103,fd=35)) tcp LISTEN 0 100 [::1]:smtp [::]:* users:(("master",pid=435,fd=14)) tcp LISTEN 0 4096 *:mysql *:* users:(("mariadbd",pid=313,fd=5),("systemd",pid=1,fd=59)) tcp LISTEN 0 511 [::1]:redis [::]:* users:(("redis-server",pid=216,fd=9)) tcp LISTEN 0 4096 [::]:sunrpc [::]:* users:(("rpcbind",pid=149,fd=6),("systemd",pid=1,fd=37)) tcp LISTEN 0 4096 *:ssh *:* users:(("sshd",pid=250,fd=3),("systemd",pid=1,fd=65)) *** Log File - Last 25 Lines *** Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB) Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 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 processTicksAndRejections (node:internal/process/task_queues:103:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:197:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:280:34) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:73:13) 2026-07-26 16:10:59.530 - info: esphome.0 (1946) New ESPHome Device discovered: heizung.local on 192.168.130.130 2026-07-26 16:10:59.530 - info: esphome.0 (1946) New ESPHome Device discovered: co2sensor.local on 192.168.130.132 2026-07-26 16:11:37.357 - debug: bestway.0 (1254) {"did":"0PEGsasaDg9C1LadNvpBjO","updated_at":1785075060,"attr":{"E19":0,"E18":0,"E32":0,"E31":0,"E30":0,"E11":0,"E10":0,"E13":0,"E12":0,"E15":0,"E14":0,"E17":0,"E16":0,"word5":190,"word4":0,"word7":33,"word6":0,"word1":0,"word0":0,"E29":0,"word2":491,"option6":10244,"ver":1126,"E22":0,"jet":0,"E23":0,"power":1,"Tnow":33,"option7":10260,"option4":0,"option5":27175,"option2":0,"option3":30,"option0":59940,"option1":59940,"E24":0,"E25":0,"E26":0,"E27":0,"E20":0,"E21":0,"E08":0,"E09":0,"E06":0,"E07":0,"E04":0,"E05":0,"E02":0,"E03":0,"E01":0,"bit7":1,"heat":3,"Tunit":1,"wave":0,"word3":0,"Tset":36,"filter":2,"E28":0,"bit6":1,"bit5":0,"bit4":0,"bit3":0,"bit2":1}} ============= Mark until here for C&P ============= iob diag has finished.und ja ich arbeite daran alle die github Adapter zu entfernen. Auch ein reboot des ganze LXC hat bisher zu keine Resultat geführt. Eigentlich habe ich nirgends "auto-update" an, nur habe ich vor kurzen im Debian 13 ein upgrade gefahren, aber das scheint ja nicht das Problem zu sein, den im Test-LXC ist ja auch theoretisch das gleiche Debian drin.
-
- also das mit dem Cache clear hat leider nichts gebracht.
- hier den Versuch des Log-Auszugs: (wieso das heutige Log erst um 16.50 beginnt ist mir etwas schleierhaft)
esphome.0 2026-07-26 16:50:11.138 error Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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:103:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:197:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:280:34) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:73:13) esphome.0 2026-07-26 16:50:07.712 info Native Integration of ESPHome Dashboard enabled, making environment ready esphome.0 2026-07-26 16:50:07.712 debug Using Pillow version: 12.3.0 esphome.0 2026-07-26 16:50:07.712 debug Fetched 20 Pillow versions from PyPI, newest: 12.3.0Es hat da ein riesiger Errorblock drin wo es um das Dashboard geht, aber ich verstehe diesen Output schlicht nicht.
esphome.0 2026-07-26 16:50:11.138 error Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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:103:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:197:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:280:34) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:73:13) -
- also das mit dem Cache clear hat leider nichts gebracht.
- hier den Versuch des Log-Auszugs: (wieso das heutige Log erst um 16.50 beginnt ist mir etwas schleierhaft)
esphome.0 2026-07-26 16:50:11.138 error Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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:103:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:197:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:280:34) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:73:13) esphome.0 2026-07-26 16:50:07.712 info Native Integration of ESPHome Dashboard enabled, making environment ready esphome.0 2026-07-26 16:50:07.712 debug Using Pillow version: 12.3.0 esphome.0 2026-07-26 16:50:07.712 debug Fetched 20 Pillow versions from PyPI, newest: 12.3.0Es hat da ein riesiger Errorblock drin wo es um das Dashboard geht, aber ich verstehe diesen Output schlicht nicht.
esphome.0 2026-07-26 16:50:11.138 error Fatal error starting ESPHomeDashboard | Error: Command failed with exit code 1: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install esphome==2026.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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.6.5 pillow==12.3.0ERROR: Cannot install esphome==2026.6.5 and pillow==12.3.0 because these package versions have conflicting dependencies.[notice] A new release of pip is available: 24.3.1 -> 26.1.2[notice] To update, run: /home/iobroker/.cache/autopy/venv/esphome/bin/python3 -m pip install --upgrade pipERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflictsCollecting esphome==2026.6.5 Using cached esphome-2026.6.5-py3-none-any.whl.metadata (3.9 kB)Collecting pillow==12.3.0 Using cached pillow-12.3.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl.metadata (9.1 kB)Collecting cryptography==48.0.1 (from esphome==2026.6.5) Using cached cryptography-48.0.1-cp311-abi3-manylinux_2_34_x86_64.whl.metadata (4.3 kB)Collecting voluptuous==0.16.0 (from esphome==2026.6.5) Using cached voluptuous-0.16.0-py3-none-any.whl.metadata (20 kB)Collecting PyYAML==6.0.3 (from esphome==2026.6.5) 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.6.5) Using cached paho_mqtt-1.6.1-py3-none-any.whlCollecting colorama==0.4.6 (from esphome==2026.6.5) Using cached colorama-0.4.6-py2.py3-none-any.whl.metadata (17 kB)Collecting icmplib==3.0.4 (from esphome==2026.6.5) Using cached icmplib-3.0.4-py3-none-any.whl.metadata (19 kB)Collecting tornado==6.5.7 (from esphome==2026.6.5) Using cached tornado-6.5.7-cp39-abi3-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl.metadata (2.8 kB)Collecting tzlocal==5.3.1 (from esphome==2026.6.5) Using cached tzlocal-5.3.1-py3-none-any.whl.metadata (7.6 kB)Collecting tzdata>=2026.2 (from esphome==2026.6.5) Using cached tzdata-2026.3-py2.py3-none-any.whl.metadata (1.4 kB)Collecting pyserial==3.5 (from esphome==2026.6.5) Using cached pyserial-3.5-py2.py3-none-any.whl.metadata (1.6 kB)Collecting platformio==6.1.19 (from esphome==2026.6.5) Using cached platformio-6.1.19-py3-none-any.whl.metadata (7.2 kB)Collecting esptool==5.3.0 (from esphome==2026.6.5) Using cached esptool-5.3.0.tar.gz (487 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.3.3 (from esphome==2026.6.5) Using cached click-8.3.3-py3-none-any.whl.metadata (2.6 kB)Collecting esphome-dashboard==20260425.0 (from esphome==2026.6.5) Using cached esphome_dashboard-20260425.0-py3-none-any.whl.metadata (1.2 kB)Collecting aioesphomeapi==45.3.1 (from esphome==2026.6.5) Using cached aioesphomeapi-45.3.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.1 kB)Collecting zeroconf==0.150.0 (from esphome==2026.6.5) Using cached zeroconf-0.150.0-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl.metadata (6.6 kB)Collecting puremagic==1.30 (from esphome==2026.6.5) Using cached puremagic-1.30-py3-none-any.whl.metadata (5.8 kB)Collecting ruamel.yaml==0.19.1 (from esphome==2026.6.5) Using cached ruamel_yaml-0.19.1-py3-none-any.whl.metadata (16 kB)Collecting ruamel.yaml.clib==0.2.15 (from esphome==2026.6.5) 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.6.5) 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==12.3.0 esphome 2026.6.5 depends on pillow==12.2.0To fix this you could try to:1. loosen the range of package versions you've specified2. 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:103:5) at $df9eabe9bda49ea8$export$e522f41234ab669a (file:///opt/iobroker/node_modules/autopy/dist/index.js:197:13) at Esphome.espHomeDashboard (/opt/iobroker/node_modules/iobroker.esphome/main.js:280:34) at Esphome.onReady (/opt/iobroker/node_modules/iobroker.esphome/main.js:73:13) -
@Dieter_P
Das ist mir schon klar und habe ich auch teilweise so in Betrieb. Aber das erstellen der yaml via Dashboard ist eben sehr einfach. Der Weg via VisualCode geht auch, ist aber eben doch aufwendiger.Online
andibr
schrieb vor 7 Stunden zuletzt editiert von
#68@Dieter_P
Das ist mir schon klar und habe ich auch teilweise so in Betrieb. Aber das erstellen der yaml via Dashboard ist eben sehr einfach. Der Weg via VisualCode geht auch, ist aber eben doch aufwendiger.Wenn Du auf die ESPHome Integration verzichten möchtest und sorgfältig mit den Keys umgehst. Warum sollte eine Konfiguration mittels HA und Verwendung über einen IOB gekoppelten Mqtt Broker nicht funktionieren?
Ich finde es zwar unfair gegenüber dem Aufwand, Support und Hilfe den @simonf04 investiert, aber irgendwann ist leider bei jedem eine Schmerzgrenze erreicht. Ganz klar, so eine Setup werde ich nicht betreiben, eher werfe ich ESPHome raus. Aber langfristig darf man gerne fragen was noch wirklich pragmatisch funktioniert oder eher für Frust sorgt. Ich hab noch Hoffnung über den neu angekündigten Release im Stable Repo..
-
Online
andibr
schrieb vor 7 Stunden zuletzt editiert von
#68@Dieter_P
Das ist mir schon klar und habe ich auch teilweise so in Betrieb. Aber das erstellen der yaml via Dashboard ist eben sehr einfach. Der Weg via VisualCode geht auch, ist aber eben doch aufwendiger.Wenn Du auf die ESPHome Integration verzichten möchtest und sorgfältig mit den Keys umgehst. Warum sollte eine Konfiguration mittels HA und Verwendung über einen IOB gekoppelten Mqtt Broker nicht funktionieren?
Ich finde es zwar unfair gegenüber dem Aufwand, Support und Hilfe den @simonf04 investiert, aber irgendwann ist leider bei jedem eine Schmerzgrenze erreicht. Ganz klar, so eine Setup werde ich nicht betreiben, eher werfe ich ESPHome raus. Aber langfristig darf man gerne fragen was noch wirklich pragmatisch funktioniert oder eher für Frust sorgt. Ich hab noch Hoffnung über den neu angekündigten Release im Stable Repo..
Ich hab noch Hoffnung über den neu angekündigten Release im Stable Repo..
Disclaimer: die v1 die hoffentlich bald (wenn rafa auch etwas Zeit findet) im Stable laden wird, wird maximal die Version in den Settings fixieren (sollte das Problem aber auch erstmal beheben, dass es "einfach kaputt geht" ohne das man dran herumspielt).
Github actions, ... die das ganze dann automatisch checken und gleich Alarm schlagen, wenn esphome da mal wieder was kaputt gemacht hat wird erst in v2 kommen.
PS: falls wer interressiert ist, Status / letzte Vorbereitungen passieren hier noch: https://github.com/DrozmotiX/ioBroker.esphome/pull/462
-
Online
andibr
schrieb vor 7 Stunden zuletzt editiert von
#68@Dieter_P
Das ist mir schon klar und habe ich auch teilweise so in Betrieb. Aber das erstellen der yaml via Dashboard ist eben sehr einfach. Der Weg via VisualCode geht auch, ist aber eben doch aufwendiger.Wenn Du auf die ESPHome Integration verzichten möchtest und sorgfältig mit den Keys umgehst. Warum sollte eine Konfiguration mittels HA und Verwendung über einen IOB gekoppelten Mqtt Broker nicht funktionieren?
Ich finde es zwar unfair gegenüber dem Aufwand, Support und Hilfe den @simonf04 investiert, aber irgendwann ist leider bei jedem eine Schmerzgrenze erreicht. Ganz klar, so eine Setup werde ich nicht betreiben, eher werfe ich ESPHome raus. Aber langfristig darf man gerne fragen was noch wirklich pragmatisch funktioniert oder eher für Frust sorgt. Ich hab noch Hoffnung über den neu angekündigten Release im Stable Repo..
IOB gekoppelten Mqtt Broker nicht funktionieren
Muss nichtmal soweit gehen. Man kann auch z.B. nur das dashboard extern betreiben und nur zum flashen verweden.
Zur iobroker API / Verbindungsproblemen hab ich schon lange nichts mehr mitbekommen.
Meist zickt nur das Dashboard etwas herum. Leider bauen die HA Leute da gerne wild herum (und ziehen dann HA mit den changes nach). Stellen das dashboard zwar separat bereit, scheint aber so als wären denen externe Integrationen die das Dashboard auch verwenden wollen egal - oft auf keine gescheite Info wenn sie breaking changes machen ... -
IOB gekoppelten Mqtt Broker nicht funktionieren
Muss nichtmal soweit gehen. Man kann auch z.B. nur das dashboard extern betreiben und nur zum flashen verweden.
Zur iobroker API / Verbindungsproblemen hab ich schon lange nichts mehr mitbekommen.
Meist zickt nur das Dashboard etwas herum. Leider bauen die HA Leute da gerne wild herum (und ziehen dann HA mit den changes nach). Stellen das dashboard zwar separat bereit, scheint aber so als wären denen externe Integrationen die das Dashboard auch verwenden wollen egal - oft auf keine gescheite Info wenn sie breaking changes machen ...Ich denke ich wurde etwas falsch verstanden? Ich schätze die Arbeit die hier geleistet wird sehr und möchte mich auch einfach mal ganz herzlich bei allen beteiligten bedanken. Ohne diesen Einsatz hätten wir keinen Iobroker der soviele Möglichkeiten bietet.
Wie schon geschrieben, es ging mir auch nie darum das Dasboard als eigenständige Sache zu haben, es war einfach nur ein Gedankenexperiment als möglichen Ansatz.
Ich betreibe mehrere ESP die mir primär Temperaturfühler zusammen sammeln, und das funktioniert sowohl via MQTT via auch direkt mit dem Adapter in der Regel sehr gut. Die MQTT Einbindung stamt aus alter Zeit, und betrifft 2stk die eher kritisches WLAN habe. Sprich die sind zuhinterst im Betonkeller und habe bereits Antennen verlängerung bekommen.Ich werde anschliessend mal die Version umstellen und berichten ob das Dashboard wieder gestartet hat.
Viele Dank und Gruss AndiNachtrag:
Ich habe jetzt auf Pillow 12.2. umgestellt und nach etwas warten funktioniert das Dashboard plötzlich wieder.esphome.0 2026-07-27 09:34:40.176 debug espHomeDashboard_Process {"_events":{"exit":[null,null],"error":[null,null]},"_eventsCount":3,"_closesNeeded":3,"_closesGot":0,"connected":false,"signalCode":null,"exitCode":null,"killed":false,"spawnfile":"esphome","_handle":{"pid":4441},"spawnargs":["esphome","dashboard","--port",6052,"/opt/iobroker/iobroker-data/esphome.0"],"pid":4441,"stdin":{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null,"readable":false},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},"stdout":{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},"stderr":{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},"stdio":[{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null,"readable":false},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null}]} esphome.0 2026-07-27 09:34:40.174 info Starting ESPHome Dashboard esphome.0 2026-07-27 09:34:33.829 info Native Integration of ESPHome Dashboard enabled, making environment ready esphome.0 2026-07-27 09:34:33.829 debug Using Pillow version: 12.Auch alle meine yaml sind wieder da ohne das ich sie importieren musste. Das ist wunderbar. Sobald ich wieder auf 12.3.0 umstelle geschieht folgendes:
esphome.0 2026-07-27 09:42:19.372 silly redis message expired/evicted __keyevent@0__:expired:io.system.adapter.esphome.0.eventLoopLag esphome.0 2026-07-27 09:42:13.273 debug [ESPHome - Console] 2026-07-27 09:42:13,273 INFO Started dashboard event loop esphome.0 2026-07-27 09:42:13.273 debug [ESPHome - Console] 2026-07-27 09:42:13,273 INFO 101 GET /events (192.168.130.28) 0.27ms esphome.0 2026-07-27 09:42:13.068 info New ESPHome Device discovered: co2sensor.local on 192.168.130.132 esphome.0 2026-07-27 09:42:13.068 debug ESPHome Device found on 192.168.130.132 | {"port":6053,"network":"wifi","board":"d1_mini","platform":"ESP8266","mac":"8caab577f32b","version":"2024.10.3","host":"co2sensor.local","address":"192.168.130.132"} esphome.0 2026-07-27 09:42:12.989 info New ESPHome Device discovered: heizung.local on 192.168.130.130 esphome.0 2026-07-27 09:42:12.989 debug ESPHome Device found on 192.168.130.130 | {"port":6053,"network":"wifi","board":"d1_mini","platform":"ESP8266","mac":"f4cfa2e3fbff","version":"2024.10.3","host":"heizung.local","address":"192.168.130.130"} esphome.0 2026-07-27 09:42:12.956 debug [ESPHome - Console] 2026-07-27 09:42:12,955 INFO 304 GET / (192.168.130.28) 4.03ms esphome.0 2026-07-27 09:42:08.064 info [ESPHome - Console] 2026-07-27 09:42:08,064 INFO Starting dashboard web server on http://0.0.0.0:6052 and configuration dir /opt/iobroker/iobroker-data/esphome.0... esphome.0 2026-07-27 09:42:07.947 debug espHomeDashboard_Process {"_events":{"exit":[null,null],"error":[null,null]},"_eventsCount":3,"_closesNeeded":3,"_closesGot":0,"connected":false,"signalCode":null,"exitCode":null,"killed":false,"spawnfile":"esphome","_handle":{"pid":4557},"spawnargs":["esphome","dashboard","--port",6052,"/opt/iobroker/iobroker-data/esphome.0"],"pid":4557,"stdin":{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null,"readable":false},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},"stdout":{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},"stderr":{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},"stdio":[{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null,"readable":false},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null},{"connecting":false,"_hadError":false,"_parent":null,"_host":null,"_closeAfterHandlingError":false,"_events":{},"_readableState":{"highWaterMark":65536,"buffer":[],"bufferIndex":0,"length":0,"pipes":[],"awaitDrainWriters":null},"_writableState":{"highWaterMark":65536,"length":0,"corked":0,"writelen":0,"bufferedIndex":0,"pendingcb":0},"allowHalfOpen":false,"_eventsCount":2,"_sockname":null,"_pendingData":null,"_pendingEncoding":"","server":null,"_server":null}]} esphome.0 2026-07-27 09:42:07.944 info Starting ESPHome Dashboard esphome.0 2026-07-27 09:42:07.712 info Native Integration of ESPHome Dashboard enabled, making environment ready esphome.0 2026-07-27 09:42:07.712 debug Using Pillow version: 12.3.0 esphome.0 2026-07-27 09:42:07.712 debug Fetched 20 Pillow versions from PyPI, newest: 12.3.0 esphome.0 2026-07-27 09:42:07.711 debug Create_state called for : _ESPHomeDashboard.newestPillowVersion with value : 12.3.0 esphome.0 2026-07-27 09:42:07.709 debug Create_state called for : _ESPHomeDashboard.pillowVersionCache with value : ["12.3.0","12.2.0","12.1.1","12.1.0","12.0.0","11.3.0","11.2.1","11.1.0","11.0.0","10.4.0","10.3.0","10.2.0","10.1.0","10.0.1","10.0.0","9.5.0","9.4.0","9.3.0","9.2.0","9.1.1"] esphome.0 2026-07-27 09:42:07.476 debug Create_state called for : _ESPHomeDashboard.selectedVersion with value : 2026.6.5 esphome.0 2026-07-27 09:42:07.474 debug Create_state called for : _ESPHomeDashboard.newestVersion with value : 2026.7.2Ich verstehe es gerade gar nicht mehr, jetzt läuft es mit der 12.3.0 auch?
Vieleicht versteht ihr was da verändert wurde?
Gruss Andi
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
405
Online33.0k
Benutzer83.5k
Themen1.3m
Beiträge