[ESPHome] Beta release

marsmännchen

@pboeck
nein leider. Das rote X, ich soll pillow installieren bleibt.

Thomas Braun

sudo apt update
apt policy python3-pil python3-pil.imagetk

marsmännchen

@thomas-braun sagte in [ESPHome] Beta release:

apt policy python3-pil python3-pil.imagetk

Ergibt:

pi@achbotslave:~ $ sudo apt update
OK:1 http://archive.raspberrypi.org/debian bullseye InRelease
Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15,0 kB]
OK:3 https://packages.grafana.com/enterprise/deb stable InRelease
OK:4 https://repos.influxdata.com/debian bullseye InRelease
OK:5 https://deb.nodesource.com/node_14.x bullseye InRelease
Holen:6 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages [13,2 MB]
Es wurden 13,2 MB in 5 s geholt (2.552 kB/s).
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Aktualisierung für 34 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.

und:

pi@achbotslave:~ $ apt policy python3-pil python3-pil.imagetk
python3-pil:
  Installiert:           (keine)
  Installationskandidat: 8.1.2+dfsg-0.3
  Versionstabelle:
     8.1.2+dfsg-0.3 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
python3-pil.imagetk:
  Installiert:           (keine)
  Installationskandidat: 8.1.2+dfsg-0.3
  Versionstabelle:
     8.1.2+dfsg-0.3 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages

Als laie würd ich sagen da fehlt was?

Thomas Braun

@marsmännchen

Dann installier die beiden Pakete nach und auch die ausstehenden 34 Paketupdates.

marsmännchen

@thomas-braun
Fürchterlich der ewige Anfänger zu sein. Vielen Dank, das wars.
Ich habe :

sudo apt-get python3-pil
 sudo pip3 install pillow
sudo apt-get install python3-pil.imagetk

und danach:

sudo apt-get install libopenjp2-7-dev

Jetzt funktioniert es.

Thomas Braun

@marsmännchen sagte in [ESPHome] Beta release:

sudo pip3 install pillow

Sollte nicht erforderlich sein, bzw. ist es jetzt in zwei Pfaden installiert.
Debian hat die Eigenart, alle möglichen phython-Pakete selber zu packen und nicht pip3 zu verwenden. Im Fall von pillow halt in die beiden Pakete, die du jetzt nachinstalliert hast.

OPatrick

Hello I have also problems installing the esp Adapter.
Attached my log file. I don't know what to do..
It a new installation of rasbian. With new iobroker.
2022-01-02T18_40_22_424Z-debug.log

OPatrick

@thomas-braun bekomme eine ähnliche Meldung. Allerdings ist es eine neue Installation.
2022-01-02T18_40_22_424Z-debug.log

Thomas Braun

@opatrick

Installier die vorgesehene node-Version 14, nicht node@v12.22.8

Und wie genau versuchst du das zu installieren? KOMPLETTE Eingabezeile ist gefragt.

Keine Ahnung was ihr da immer treibt:

echad@chet:~ $ iobroker add esphome
NPM version: x.y.z
npm install iobroker.esphome@0.2.4 --loglevel error --prefix "/opt/iobroker" (System call)
host.chet install adapter esphome
upload [5] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/words.js words.js application/javascript
upload [4] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/style.css style.css text/css
upload [3] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/index_m.html index_m.html text/html
upload [2] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/img/dashboard.png img/dashboard.png image/png
upload [1] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/esphome.png esphome.png image/png
upload [0] esphome.admin /opt/iobroker/node_modules/iobroker.esphome/admin/admin.d.ts admin.d.ts video/mp2t
host.chet object system.adapter.esphome created/updated
host.chet create instance esphome
host.chet object esphome.0.info.connection created
host.chet object esphome.0.info created
host.chet object system.adapter.esphome.0.logLevel created
host.chet object system.adapter.esphome.0.sigKill created
host.chet object system.adapter.esphome.0.eventLoopLag created
host.chet object system.adapter.esphome.0.outputCount created
host.chet object system.adapter.esphome.0.inputCount created
host.chet object system.adapter.esphome.0.uptime created
host.chet object system.adapter.esphome.0.memRss created
host.chet object system.adapter.esphome.0.memHeapTotal created
host.chet object system.adapter.esphome.0.memHeapUsed created
host.chet object system.adapter.esphome.0.cputime created
host.chet object system.adapter.esphome.0.cpu created
host.chet object system.adapter.esphome.0.compactMode created
host.chet object system.adapter.esphome.0.connected created
host.chet object system.adapter.esphome.0.alive created
host.chet Set default value of esphome.0.info.connection: false
host.chet object system.adapter.esphome.0 created

OPatrick

@thomas-braun ich habe gerade auch das update auf node 14 gemacht:
Leider klappt das nicht..

pi@mospi:~ $  iobroker add esphome
NPM version: 6.14.15
npm install iobroker.esphome@0.2.4 --loglevel error --prefix "/opt/iobroker" (System call)
/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py:24: UserWarning: Distutils was imported before Setuptools, but importing Setuptools also replaces the `distutils` module in `sys.modules`. This may lead to undesirable behaviors or errors. To avoid these issues, avoid using distutils directly, ensure that setuptools is installed in the traditional way (e.g. not an editable install), and/or make sure that setuptools is always imported before distutils.
  warnings.warn(
/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py:36: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
Traceback (most recent call last):
  File "/opt/iobroker/node_modules/nopy/src/get-pip.py", line 20061, in <module>
    main()
  File "/opt/iobroker/node_modules/nopy/src/get-pip.py", line 194, in main
    bootstrap(tmpdir=tmpdir)
  File "/opt/iobroker/node_modules/nopy/src/get-pip.py", line 119, in bootstrap
    import setuptools  # noqa
  File "/usr/local/lib/python3.8/site-packages/setuptools/__init__.py", line 8, in <module>
    import _distutils_hack.override  # noqa: F401
  File "/usr/local/lib/python3.8/site-packages/_distutils_hack/override.py", line 1, in <module>
    __import__('_distutils_hack').do_override()
  File "/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py", line 73, in do_override
    ensure_local_distutils()
  File "/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py", line 61, in ensure_local_distutils
    assert '_distutils' in core.__file__, core.__file__
AssertionError: /usr/local/lib/python3.8/distutils/core.py
Error: Exited with code 1.
    at ChildProcess.<anonymous> (/opt/iobroker/node_modules/nopy/src/api.js:277:20)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.esphome@0.2.4 install: `npip install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.esphome@0.2.4 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-01-02T20_29_14_127Z-debug.log
host.mospi Cannot install iobroker.esphome@0.2.4: 1
pi@mospi:~ $ node -v
v14.18.2
pi@mospi:~ $ npm -v
6.14.15
pi@mospi:~ $

was mich stuzig mach ist folgendes:

/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py:24: UserWarning: Distutils was imported before Setuptools, but importing Setuptools also replaces the `distutils` module in `sys.modules`. This may lead to undesirable behaviors or errors. To avoid these issues, avoid using distutils directly, ensure that setuptools is installed in the traditional way (e.g. not an editable install), and/or make sure that setuptools is always imported before distutils.

  warnings.warn(

/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py:36: UserWarning: Setuptools is replacing distutils.

  warnings.warn("Setuptools is replacing distutils.")

das taucht bei dir nicht auf...

Thomas Braun

@opatrick

apt policy python3

und

sudo ln -s /usr/bin/node /usr/bin/nodejs
which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs

liefern jeweils?

OPatrick

@thomas-braun

pi@mospi:~ $ python3:
  Installiert:           3.9.2-3
  Installationskandidat: 3.9.2-3
  Versionstabelle:
 *** 3.9.2-3 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Package                          s
        100 /var/lib/dpkg/statuspython3

beim which Befehl passiert rein gar nichts keine anzeige kein Fehler..

Thomas Braun

@opatrick

Dann hast du dir python3 irgendwoher irgendwie ins System gekloppt.
Dein erschwindeltes python3.8 wieder deinstallieren und die vorgesehene Version 3.9.2-3 installieren. Dann funktioniert auch die Installation des Adapters wie bei mir.

Und bitte auch die Ausgabe auf die zweite Befehlskette noch liefern. Nicht das du dir das ähnlich schief ins System gedübelt hast.

OPatrick

@thomas-braun

which geht jetzt aber immer noch Fehler...

pi@mospi:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs
/usr/bin/node
/usr/bin/npm
pi@mospi:~ $ iobroker add esphome
NPM version: 6.14.15
npm install iobroker.esphome@0.2.4 --loglevel error --prefix "/opt/iobroker" (System call)
/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py:24: UserWarning: Distutils was imported before Setuptools, but importing Setuptools also replaces the `distutils` module in `sys.modules`. This may lead to undesirable behaviors or errors. To avoid these issues, avoid using distutils directly, ensure that setuptools is installed in the traditional way (e.g. not an editable install), and/or make sure that setuptools is always imported before distutils.
  warnings.warn(
/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py:36: UserWarning: Setuptools is replacing distutils.
  warnings.warn("Setuptools is replacing distutils.")
Traceback (most recent call last):
  File "/opt/iobroker/node_modules/nopy/src/get-pip.py", line 20061, in <module>
    main()
  File "/opt/iobroker/node_modules/nopy/src/get-pip.py", line 194, in main
    bootstrap(tmpdir=tmpdir)
  File "/opt/iobroker/node_modules/nopy/src/get-pip.py", line 119, in bootstrap
    import setuptools  # noqa
  File "/usr/local/lib/python3.8/site-packages/setuptools/__init__.py", line 8, in <module>
    import _distutils_hack.override  # noqa: F401
  File "/usr/local/lib/python3.8/site-packages/_distutils_hack/override.py", line 1, in <module>
    __import__('_distutils_hack').do_override()
  File "/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py", line 73, in do_override
    ensure_local_distutils()
  File "/usr/local/lib/python3.8/site-packages/_distutils_hack/__init__.py", line 61, in ensure_local_distutils
    assert '_distutils' in core.__file__, core.__file__
AssertionError: /usr/local/lib/python3.8/distutils/core.py
Error: Exited with code 1.
    at ChildProcess.<anonymous> (/opt/iobroker/node_modules/nopy/src/api.js:277:20)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.esphome@0.2.4 install: `npip install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.esphome@0.2.4 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-01-02T20_55_04_809Z-debug.log
host.mospi Cannot install iobroker.esphome@0.2.4: 1
pi@mospi:~ $

da scheint python immer noch verbogen zu sein.. ok wie bekomme ich das weg?

Thomas Braun

@opatrick

sudo ln -s /usr/bin/node /usr/bin/nodejs
which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs

Und wie hast du python3.8 nun ins System gekloppt? Muss ja von 'irgendwoher' manuell kommen, in den Repos liegt die Version ja nicht vor.

Thomas Braun

@OPatrick

Deine schiefe Installation ist übrigens was für einen eigenen, neuen Thread wert, das hat mit dem Beta-Testen des Adapters ja nix zu tun.

OPatrick

@thomas-braun
ja das kam leider etwas unglücklich. Weil beim aller ersten Versuch der Adapter Installation kamen zig Fehler Meldungen weil das Modul cryptography von python gefehlt usw..
Da habe ich dann wahrscheinlich python manuell installiert

jetzt habe ich es zwar manuel gelöscht.. Aber die ganzen Pfade stimmen nimmer

ein sudo und er which befehl brachten nix..


pi@mospi:/usr/local/lib $ iobroker add esphome                                                            NPM version: 6.14.15
npm install iobroker.esphome@0.2.4 --loglevel error --prefix "/opt/iobroker" (System call)
Error: Python site module exited with code 1.
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = '/opt/iobroker/node_modules/iobroker.esphome'
  program name = 'python3.8'

Thomas Braun

@opatrick sagte in [ESPHome] Beta release:

ein sudo und er which befehl brachten nix..

Konkret? Du verfrickelst dein System immer mehr...

Thomas Braun

@opatrick sagte in [ESPHome] Beta release:

jetzt habe ich es zwar manuel gelöscht.. Aber die ganzen Pfade stimmen nimmer

Noch konkreter? Ich sehe nicht was du da jetzt wie warum wo gemacht hast.

OPatrick

@thomas-braun
naja ich habe über apt-get reinstall python3 etc.. versucht die Verzeichniss links richtig zu setzten..


pi@mospi:/usr/local/lib $ which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v14.18.2
v14.18.2
6.14.15
OK:1 http://phoscon.de/apt/deconz bullseye-beta InRelease
OK:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
OK:3 http://archive.raspberrypi.org/debian bullseye InRelease
OK:4 https://deb.nodesource.com/node_14.x bullseye InRelease
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
OK:1 http://phoscon.de/apt/deconz bullseye-beta InRelease
OK:2 http://archive.raspberrypi.org/debian bullseye InRelease
OK:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
OK:4 https://deb.nodesource.com/node_14.x bullseye InRelease
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
nodejs:
  Installiert:           14.18.2-deb-1nodesource1
  Installationskandidat: 14.18.2-deb-1nodesource1
  Versionstabelle:
 *** 14.18.2-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_14.x bullseye/main armhf Packages
        100 /var/lib/dpkg/status
     12.22.5~dfsg-2~11u1 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages

das sieht gut aus aber beim
das nicht


pi@mospi:/usr/local/lib $ iobroker add esphome
NPM version: 6.14.15
npm install iobroker.esphome@0.2.4 --loglevel error --prefix "/opt/iobroker" (System call)
Error: Python site module exited with code 1.
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = '/opt/iobroker/node_modules/iobroker.esphome'
  program name = 'python3.8'
  isolated = 0
  environment = 1
  user site = 1
  import site = 1
  sys._base_executable = '/usr/local/bin/python3.8'
  sys.base_prefix = '/usr/local'
  sys.base_exec_prefix = '/usr/local'
  sys.executable = '/usr/local/bin/python3.8'
  sys.prefix = '/usr/local'
  sys.exec_prefix = '/usr/local'
  sys.path = [
    '/opt/iobroker/node_modules/iobroker.esphome',
    '/usr/local/lib/python38.zip',
    '/usr/local/lib/python3.8',
    '/usr/local/lib/lib-dynload',
  ]
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

Current thread 0x76f87040 (most recent call first):
<no Python frame>

    at ChildProcess.<anonymous> (/opt/iobroker/node_modules/nopy/src/api.js:106:16)
    at ChildProcess.emit (events.js:400:28)
    at maybeClose (internal/child_process.js:1058:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.esphome@0.2.4 install: `npip install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.esphome@0.2.4 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-01-02T21_11_14_284Z-debug.log
host.mospi Cannot install iobroker.esphome@0.2.4: 1

NEWS

[ESPHome] Beta release

Support us

875
Online

31.7k
Users

79.9k
Topics

1.3m
Posts

NEWS

[ESPHome] Beta release

Support us

875Online

31.7kUsers

79.9kTopics

1.3mPosts

875
Online

31.7k
Users

79.9k
Topics

1.3m
Posts