NEWS
esphome - wird dies noch gepflegt?
-
Gibt es nicht über das Stable-Repo.
Beta kurz scharf schalten.esphome github: 0.2.4 latest: 0.2.4 for 23 months stable: -.-.-
-
pi@Smartazamba:~ $ iob add esphome --host Smartazamba --debug NPM version: 9.6.7 Installing iobroker.esphome@0.2.4... (System call) npm ERR! code 1 npm ERR! path /opt/iobroker/node_modules/iobroker.esphome npm ERR! command failed npm ERR! command sh -c npip install npm ERR! No python_modules directory; installing pip locally if needed. npm ERR! pip 23.0.1 from /usr/lib/python3/dist-packages/pip (python 3.11) npm ERR! error: externally-managed-environment npm ERR! npm ERR! × This environment is externally managed npm ERR! ╰─> To install Python packages system-wide, try apt install npm ERR! python3-xyz, where xyz is the package you are trying to npm ERR! install. npm ERR! npm ERR! If you wish to install a non-Debian-packaged Python package, npm ERR! create a virtual environment using python3 -m venv path/to/venv. npm ERR! Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make npm ERR! sure you have python3-full installed. npm ERR! npm ERR! If you wish to install a non-Debian packaged Python application, npm ERR! it may be easiest to use pipx install xyz, which will manage a npm ERR! virtual environment for you. Make sure you have pipx installed. npm ERR! npm ERR! See /usr/share/doc/python3.11/README.venv for more information. npm ERR! npm ERR! note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. npm ERR! hint: See PEP 668 for the detailed specification. npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-28T08_03_31_442Z-debug-0.log host.Smartazamba Cannot install iobroker.esphome@0.2.4: 1
Den Fehler
npm ERR! × This environment is externally managed
bekomm ich auch beim Versuch der Python für das Zigbee Stick Update per SSH zu installieren.
Fehlt da noch was für Bookworm? -
@Thomas-Braun Bin jetzt mit deinem Tipp von hier etwas weiter gekommen.
pi@Smartazamba:~ $ iob add esphome --host Smartazamba --debug NPM version: 9.6.7 Installing iobroker.esphome@0.2.4... (System call) npm ERR! code 127 npm ERR! path /opt/iobroker/node_modules/iobroker.esphome npm ERR! command failed npm ERR! command sh -c npip install npm ERR! sh: 1: npip: Permission denied npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-28T08_19_07_068Z-debug-0.log host.Smartazamba Cannot install iobroker.esphome@0.2.4: 127
-
Lösche die Datei /usr/lib/python3.x/EXTERNALLY-MANAGED
oder
verwende bei pip das Argument --break-system-packages
oder
füge in ~/.config/pip/pip.conf den Text ein:[global] break-system-packages = true
-
-
@thomas-braun Puh, erstmal danke für die Hilfe.
EXTERNALLY-MANAGED ist aus den Verzeichnis entfernt.
Wie kann ich bei der Adapterinstalletion bei pip das Argument --break-system-packages anfügen?
/.config/pip/pip.conf finde ich im Homeverzeichnis meines ioBroker Nutzers nicht.
In dem Thread war schließlich nur die Neuinstallation die Lösung.Nach:
cd /opt/iobroker npm i nopy sudo -u iobroker chmod ug+x /opt/iobroker/node_modules/nopy/src/n*
Konnte ich den Adapter installieren.
Danke!
-
Du musst nur eine der drei Optionen umsetzen.
-
@thomas-braun Ich hatte doch hier schon EXTERNALLY-MANAGED entfernt.
Damit kam ich ja zu:pi@Smartazamba:~ $ iob add esphome --host Smartazamba --debug NPM version: 9.6.7 Installing iobroker.esphome@0.2.4... (System call) npm ERR! code 127 npm ERR! path /opt/iobroker/node_modules/iobroker.esphome npm ERR! command failed npm ERR! command sh -c npip install npm ERR! sh: 1: npip: Permission denied npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-28T08_19_07_068Z-debug-0.log host.Smartazamba Cannot install iobroker.esphome@0.2.4: 127
Davor war die Ausgabe folgende:
pi@Smartazamba:~ $ iob add esphome --host Smartazamba --debug NPM version: 9.6.7 Installing iobroker.esphome@0.2.4... (System call) npm ERR! code 1 npm ERR! path /opt/iobroker/node_modules/iobroker.esphome npm ERR! command failed npm ERR! command sh -c npip install npm ERR! No python_modules directory; installing pip locally if needed. npm ERR! pip 23.0.1 from /usr/lib/python3/dist-packages/pip (python 3.11) npm ERR! error: externally-managed-environment npm ERR! npm ERR! × This environment is externally managed npm ERR! ╰─> To install Python packages system-wide, try apt install npm ERR! python3-xyz, where xyz is the package you are trying to npm ERR! install. npm ERR! npm ERR! If you wish to install a non-Debian-packaged Python package, npm ERR! create a virtual environment using python3 -m venv path/to/venv. npm ERR! Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make npm ERR! sure you have python3-full installed. npm ERR! npm ERR! If you wish to install a non-Debian packaged Python application, npm ERR! it may be easiest to use pipx install xyz, which will manage a npm ERR! virtual environment for you. Make sure you have pipx installed. npm ERR! npm ERR! See /usr/share/doc/python3.11/README.venv for more information. npm ERR! npm ERR! note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. npm ERR! hint: See PEP 668 for the detailed specification. npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-28T08_03_31_442Z-debug-0.log host.Smartazamba Cannot install iobroker.esphome@0.2.4: 1
-
Ja, dann war das mit
nopy
der richtige nächste Schritt. -
Wenn es noch wichtig ist....
Es ist eine neue Version (Zur Zeit noch Beta) herausgekommen.
Diese Version hat Module aus dem Internet geladen sodass alles wieder funktioniert. (Problem mit PlatformIO)
Besten Dank @DutchmanEines ist mir noch aufgefallen, was zwar die Funktion nicht beeinträchtigt aber unschön ist.
Im Log finde ich viele Einträge, dass die Verbindung zu ioBroker mehrfach aufgebaut und einzeln abgebaut werden. (Dies ist neu - wird wohl am Beta-Stand liegen . oder?)[16:42:38][C][wifi:389]: Signal strength: -49 dB ▂▄▆█ [16:42:38][C][wifi:393]: Channel: 5 [16:42:38][C][wifi:394]: Subnet: 255.255.255.0 [16:42:38][C][wifi:395]: Gateway: 192.168.1.1 [16:42:38][C][wifi:396]: DNS1: 192.168.1.1 [16:42:38][C][wifi:397]: DNS2: 0.0.0.0 [16:42:38][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:38][C][logger:416]: Logger: [16:42:38][C][logger:417]: Level: DEBUG [16:42:38][C][logger:418]: Log Baud Rate: 0 [16:42:38][C][logger:420]: Hardware UART: UART0 [16:42:38][D][api:102]: Accepted 192.168.1.95 .... [16:42:39][D][api:102]: Accepted 192.168.1.95 [16:42:39][C][mdns:115]: mDNS: [16:42:39][C][mdns:116]: Hostname: lifepo4-48vsolar1 [16:42:39][C][ota:097]: Over-The-Air Updates: [16:42:39][C][ota:098]: Address: lifepo4-48vsolar1.local:3232 [16:42:39][C][ota:101]: Using Password. [16:42:39][D][api:102]: Accepted 192.168.1.95 [16:42:39][C][api:139]: API Server: [16:42:39][C][api:140]: Address: lifepo4-48vsolar1.local:6053 [16:42:39][C][api:142]: Using noise encryption: YES [16:42:39][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:39][W][component:214]: Component api took a long time for an operation (0.05 s). [16:42:39][W][component:215]: Components should block for at most 20-30ms. [16:42:39][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:40][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed [16:42:40][D][api:102]: Accepted 192.168.1.95 [16:42:40][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed [16:42:40][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:40][D][api:102]: Accepted 192.168.1.95 [16:42:40][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed [16:42:40][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:40][D][api:102]: Accepted 192.168.1.95 [16:42:40][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed [16:42:40][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:40][D][api:102]: Accepted 192.168.1.95 [16:42:40][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed [16:42:40][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:40][D][api:102]: Accepted 192.168.1.95 [16:42:40][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed [16:42:40][W][component:214]: Component api took a long time for an operation (0.05 s). [16:42:40][W][component:215]: Components should block for at most 20-30ms. [16:42:41][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:41][D][api:102]: Accepted 192.168.1.95 [16:42:41][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed [16:42:41][D][api.connection:1050]: ESPHome Logs 2023.10.6 (192.168.1.95): Connected successfully [16:42:41][D][api:102]: Accepted 192.168.1.95 [16:42:41][W][api.connection:103]: ESPHome Logs 2023.10.6 (192.168.1.95): Connection closed
-
Ich haabe hier die 0.41 im Einsatz und bei der passiert das bei mir auch ständig. Komischerweise aber nur mit ESPs die ich mit der neuen Version erstellt habe. Ich habe hier ältere ESPs die seit Jahren durchlaufen, da tritt das komischerweise nicht auf.
-
@wolfgangfb
Bei mir ist es 0.5.0 Beta 8. (Läuft soweit aber ganz OK) -
Hallo zusammen,
ich wollte ESPHome installieren.
pi@raspberrypi:~ $ iob add esphome --host raspberrypi --debuginstalliert ist es, aber soblad ich das Dashboard aktiviere wirde der Adapter Rot.
Was mache ich falsch? -
@tobiasp sagte in esphome - wird dies noch gepflegt?:
Was mache ich falsch?
Du zeigst kein Log davon.
-
@thomas-braun
stimmt sorryhost.raspberrypi 2024-01-13 12:29:12.798 error Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: esphome.0 2024-01-13 12:29:12.393 info terminating esphome.0 2024-01-13 12:29:11.711 warn Terminated (UNCAUGHT_EXCEPTION): Without reason esphome.0 2024-01-13 12:29:11.707 info terminating esphome.0 2024-01-13 12:29:11.662 error Exception-Code: MODULE_NOT_FOUND: Cannot find module '@mongodb-js/zstd-linux-arm-gnueabihf'Require stack:- /opt/iobroker/node_modules/@mongodb-js/zstd/index.js esphome.0 2024-01-13 12:29:11.661 error Error: Cannot find module '@mongodb-js/zstd-linux-arm-gnueabihf'Require stack:- /opt/iobroker/node_modules/@mongodb-js/zstd/index.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) at Function.Module._load (node:internal/modules/cjs/loader:975:27) at Module.require (node:internal/modules/cjs/loader:1225:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/opt/iobroker/node_modules/@mongodb-js/zstd/index.js:131:29) at Module._compile (node:internal/modules/cjs/loader:1356:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1414:10) at Module.load (node:internal/modules/cjs/loader:1197:32) at Function.Module._load (node:internal/modules/cjs/loader:1013:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:202:29) esphome.0 2024-01-13 12:29:11.660 error unhandled promise rejection: Cannot find module '@mongodb-js/zstd-linux-arm-gnueabihf'Require stack:- /opt/iobroker/node_modules/@mongodb-js/zstd/index.js esphome.0 2024-01-13 12:29:11.657 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). esphome.0 2024-01-13 12:29:11.267 info [Error caught and send to Sentry, thank you collaborating!] error: Error: Cannot find module '@mongodb-js/zstd-linux-arm-gnueabihf'Require stack:- /opt/iobroker/node_modules/@mongodb-js/zstd/index.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) at Function.Module._load (node:internal/modules/cjs/loader:975:27) at Module.require (node:internal/modules/cjs/loader:1225:19) at require (node:internal/modules/helpers:177:18) at Object.<anonymous> (/opt/iobroker/node_modules/@mongodb-js/zstd/index.js:131:29) at Module._compile (node:internal/modules/cjs/loader:1356:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1414:10) at Module.load (node:internal/modules/cjs/loader:1197:32) at Function.Module._load (node:internal/modules/cjs/loader:1013:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:202:29) esphome.0 2024-01-13 12:29:10.907 info Native Integration of ESPHome Dashboard enabled esphome.0 2024-01-13 12:29:10.417 info starting. Version 0.5.0-beta.8 in /opt/iobroker/node_modules/iobroker.esphome, node: v18.19.0, js-controller: 5.0.17
-
SuFu hätte das zutage gefördert:
https://forum.iobroker.net/topic/70320/esp-home-webinterface-wird-nicht-geladen/31
-
@thomas-braun
Oh muss mich verbessern habe mit npm i iobroker.esphome installiert, da der andere befehl nicht funktioniert hat -
Das macht man ja auch nicht mit npm...
-
@thomas-braun
wie kann ich es sonst installieren? -
iobroker add ADAPTERNAME --host HOSTNAME --debug
ist der Standardbefehl um Adapter hinzuzufügen.