Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Probleme mit Installation von ESP Home@0.2.4

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Probleme mit Installation von ESP Home@0.2.4

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tontechniker @Thomas Braun last edited by

      @thomas-braun

      pi@raspberrypi:~ $ sudo apt full-upgrade
      Paketlisten werden gelesen… Fertig
      Abhängigkeitsbaum wird aufgebaut… Fertig
      Statusinformationen werden eingelesen… Fertig
      Paketaktualisierung (Upgrade) wird berechnet… Fertig
      Die folgenden Pakete werden aktualisiert (Upgrade):
        libntfs-3g883 ntfs-3g
      2 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
      Es müssen 547 kB an Archiven heruntergeladen werden.
      Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
      Möchten Sie fortfahren? [J/n] j
      Holen:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf ntfs-3g armhf 1:2017.3.23AR.3-4+deb11u2 [379 kB]
      Holen:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libntfs-3g883 armhf 1:2017.3.23AR.3-4+deb11u2 [168 kB]
      Es wurden 547 kB in 1 s geholt (794 kB/s).
      Changelogs werden gelesen... Fertig
      (Lese Datenbank ... 53788 Dateien und Verzeichnisse sind derzeit installiert.)
      Vorbereitung zum Entpacken von .../ntfs-3g_1%3a2017.3.23AR.3-4+deb11u2_armhf.deb ...
      Entpacken von ntfs-3g (1:2017.3.23AR.3-4+deb11u2) über (1:2017.3.23AR.3-4+deb11u1) ...
      Vorbereitung zum Entpacken von .../libntfs-3g883_1%3a2017.3.23AR.3-4+deb11u2_armhf.deb ...
      Entpacken von libntfs-3g883 (1:2017.3.23AR.3-4+deb11u2) über (1:2017.3.23AR.3-4+deb11u1) ...
      libntfs-3g883 (1:2017.3.23AR.3-4+deb11u2) wird eingerichtet ...
      ntfs-3g (1:2017.3.23AR.3-4+deb11u2) wird eingerichtet ...
      Trigger für libc-bin (2.31-13+rpt2+rpi1+deb11u2) werden verarbeitet ...
      Trigger für man-db (2.9.4-2) werden verarbeitet ...
      Trigger für initramfs-tools (0.140) werden verarbeitet ...
      pi@raspberrypi:~ $
      
      1 Reply Last reply Reply Quote 0
      • T
        Tontechniker @Thomas Braun last edited by Tontechniker

        @thomas-braun

        $ iobroker add esphome --host raspberrypi
        
        NPM version: 6.14.17
        
        Installing iobroker.esphome@0.2.4... (System call)
        
        > iobroker.esphome@0.2.4 install /opt/iobroker/node_modules/iobroker.esphome> npip install
        
        No python_modules directory; installing pip locally if needed.
        
        Successfully completed pip check.
        
        Collecting esphome>=2021.8
        
        Using cached esphome-2022.5.1-py2.py3-none-any.whl (2.3 MB)
        
        Collecting tornado>=3.2
        
        Using cached tornado-6.1.tar.gz (497 kB)
        
        Preparing metadata (setup.py): started
        
        Preparing metadata (setup.py): finished with status 'done'
        
        Collecting tzlocal==4.2
        
        Using cached tzlocal-4.2-py3-none-any.whl (19 kB)
        
        Collecting aioesphomeapi==10.8.2
        
        Using cached aioesphomeapi-10.8.2-py2.py3-none-any.whl (49 kB)
        
        Collecting pyserial==3.5
        
        Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
        
        Collecting voluptuous==0.13.1
        
        Using cached voluptuous-0.13.1-py3-none-any.whl (29 kB)
        
        Collecting esptool==3.3
        
        Using cached esptool-3.3.tar.gz (213 kB)
        
        Preparing metadata (setup.py): started
        
        Preparing metadata (setup.py): finished with status 'done'
        
        Collecting kconfiglib==13.7.1
        
        Using cached kconfiglib-13.7.1-py2.py3-none-any.whl (145 kB)
        
        Collecting paho-mqtt==1.6.1
        
        Using cached paho-mqtt-1.6.1.tar.gz (99 kB)
        
        Preparing metadata (setup.py): started
        
        Preparing metadata (setup.py): finished with status 'done'
        
        Collecting PyYAML==6.0
        
        Using cached PyYAML-6.0.tar.gz (124 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 zeroconf==0.38.4
        
        Using cached zeroconf-0.38.4-py3-none-any.whl (106 kB)
        
        Collecting click==8.1.3
        
        Using cached click-8.1.3-py3-none-any.whl (96 kB)
        
        Collecting colorama==0.4.4
        
        Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)
        
        Collecting tzdata>=2021.1
        
        Using cached tzdata-2022.1-py2.py3-none-any.whl (339 kB)
        
        Collecting platformio==5.2.5
        
        Using cached platformio-5.2.5.tar.gz (218 kB)
        
        Preparing metadata (setup.py): started
        
        Preparing metadata (setup.py): finished with status 'done'
        
        Collecting esphome-dashboard==20220508.0
        
        Using cached esphome_dashboard-20220508.0-py3-none-any.whl (601 kB)
        
        Collecting noiseprotocol<1.0,>=0.3.1
        
        Using cached noiseprotocol-0.3.1-py3-none-any.whl (20 kB)
        
        Collecting protobuf<4.0,>=3.12.2
        
        Using cached protobuf-3.20.1-py2.py3-none-any.whl (162 kB)
        
        Collecting bitstring>=3.1.6
        
        Using cached bitstring-3.1.9-py3-none-any.whl (38 kB)
        
        Collecting cryptography>=2.1.4
        
        Using cached cryptography-37.0.2.tar.gz (585 kB)
        
        Installing build dependencies: started
        
        Installing build dependencies: finished with status 'error'
        
        host.raspberrypi Cannot install iobroker.esphome@0.2.4: 1
        
        ERROR: Process exited with code 25
        

        Ich gebe vorerst mal auf! Danke!!

        1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active last edited by Thomas Braun

          @tontechniker

          Mach es ausnahmsweise mal über npm direkt.

          cd /opt/iobroker
          npm install iobroker.esphome
          
          T 1 Reply Last reply Reply Quote 0
          • T
            Tontechniker @Thomas Braun last edited by Tontechniker

            @thomas-braun

            pi@raspberrypi:/opt/iobroker $ npm install iobroker.esphome
            
            > iobroker.esphome@0.2.4 install /opt/iobroker/node_modules/iobroker.esphome
            > npip install
            
            No python_modules directory; installing pip locally if needed.
              Cache entry deserialization failed, entry ignored
              Cache entry deserialization failed, entry ignored
            Successfully completed pip check.
            Collecting esphome>=2021.8
              Using cached esphome-2022.5.1-py2.py3-none-any.whl (2.3 MB)
            Collecting tornado>=3.2
              Using cached tornado-6.1.tar.gz (497 kB)
              Preparing metadata (setup.py) ... done
            Collecting pyserial==3.5
              Using cached pyserial-3.5-py2.py3-none-any.whl (90 kB)
            Collecting PyYAML==6.0
              Using cached PyYAML-6.0.tar.gz (124 kB)
              Installing build dependencies ... done
              Getting requirements to build wheel ... done
              Preparing metadata (pyproject.toml) ... done
            Collecting tzlocal==4.2
              Using cached tzlocal-4.2-py3-none-any.whl (19 kB)
            Collecting click==8.1.3
              Using cached click-8.1.3-py3-none-any.whl (96 kB)
            Collecting tzdata>=2021.1
              Using cached tzdata-2022.1-py2.py3-none-any.whl (339 kB)
            Collecting voluptuous==0.13.1
              Using cached voluptuous-0.13.1-py3-none-any.whl (29 kB)
            Collecting aioesphomeapi==10.8.2
              Using cached aioesphomeapi-10.8.2-py2.py3-none-any.whl (49 kB)
            Collecting colorama==0.4.4
              Using cached colorama-0.4.4-py2.py3-none-any.whl (16 kB)
            Collecting paho-mqtt==1.6.1
              Using cached paho-mqtt-1.6.1.tar.gz (99 kB)
              Preparing metadata (setup.py) ... done
            Collecting esptool==3.3
              Using cached esptool-3.3.tar.gz (213 kB)
              Preparing metadata (setup.py) ... done
            Collecting esphome-dashboard==20220508.0
              Using cached esphome_dashboard-20220508.0-py3-none-any.whl (601 kB)
            Collecting kconfiglib==13.7.1
              Using cached kconfiglib-13.7.1-py2.py3-none-any.whl (145 kB)
            Collecting platformio==5.2.5
              Using cached platformio-5.2.5.tar.gz (218 kB)
              Preparing metadata (setup.py) ... done
            Collecting zeroconf==0.38.4
              Using cached zeroconf-0.38.4-py3-none-any.whl (106 kB)
            Collecting protobuf<4.0,>=3.12.2
              Using cached protobuf-3.20.1-py2.py3-none-any.whl (162 kB)
            Collecting noiseprotocol<1.0,>=0.3.1
              Using cached noiseprotocol-0.3.1-py3-none-any.whl (20 kB)
            Collecting bitstring>=3.1.6
              Using cached bitstring-3.1.9-py3-none-any.whl (38 kB)
            Collecting cryptography>=2.1.4
              Using cached cryptography-37.0.2.tar.gz (585 kB)
              Installing build dependencies ... error
              error: subprocess-exited-with-error
            
              × pip subprocess to install build dependencies did not run successfully.
              │ exit code: 1
              ╰─> [126 lines of output]
                  Collecting setuptools!=60.9.0,>=40.6.0
                    Using cached setuptools-62.3.3-py3-none-any.whl (1.2 MB)
                  Collecting wheel
                    Using cached wheel-0.37.1-py2.py3-none-any.whl (35 kB)
                  Collecting cffi>=1.12
                    Using cached cffi-1.15.0.tar.gz (484 kB)
                    Preparing metadata (setup.py): started
                    Preparing metadata (setup.py): finished with status 'done'
                  Collecting setuptools-rust>=0.11.4
                    Using cached setuptools_rust-1.3.0-py3-none-any.whl (21 kB)
                  Collecting pycparser
                    Using cached pycparser-2.21-py2.py3-none-any.whl (118 kB)
                  Collecting semantic-version<3,>=2.8.2
                    Using cached semantic_version-2.10.0-py2.py3-none-any.whl (15 kB)
                  Collecting typing-extensions>=3.7.4.3
                    Using cached typing_extensions-4.2.0-py3-none-any.whl (24 kB)
                  Building wheels for collected packages: cffi
                    Building wheel for cffi (setup.py): started
                    Building wheel for cffi (setup.py): finished with status 'error'
                    error: subprocess-exited-with-error
            
                    × python setup.py bdist_wheel did not run successfully.
                    │ exit code: 1
                    ╰─> [38 lines of output]
                        /opt/iobroker/node_modules/iobroker.esphome/python_modules/lib/python3.9/site-packages/setuptools/config/setupcfg.py:459: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.
                          warnings.warn(msg, warning_class)
                        running bdist_wheel
                        running build
                        running build_py
                        creating build
                        creating build/lib.linux-armv7l-cpython-39
                        creating build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/lock.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/vengine_gen.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/error.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/model.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/__init__.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/ffiplatform.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/api.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/cparser.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/commontypes.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/verifier.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/pkgconfig.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/recompiler.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/_cffi_include.h -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/parse_c_type.h -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/_embedding.h -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-cpython-39/cffi
                        running build_ext
                        building '_cffi_backend' extension
                        creating build/temp.linux-armv7l-cpython-39
                        creating build/temp.linux-armv7l-cpython-39/c
                        arm-linux-gnueabihf-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -ffile-prefix-map=/python3.9-3.9.2=. -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/python3.9 -c c/_cffi_backend.c -o build/temp.linux-armv7l-cpython-39/c/_cffi_backend.o
                        c/_cffi_backend.c:2:10: fatal error: Python.h: Datei oder Verzeichnis nicht gefunden
                            2 | #include <Python.h>
                              |          ^~~~~~~~~~
                        compilation terminated.
                        error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1
                        [end of output]
            
                    note: This error originates from a subprocess, and is likely not a problem with pip.
                    ERROR: Failed building wheel for cffi
                    Running setup.py clean for cffi
                  Failed to build cffi
                  Installing collected packages: wheel, typing-extensions, setuptools, semantic-version, pycparser, setuptools-rust, cffi
                    Running setup.py install for cffi: started
                    Running setup.py install for cffi: finished with status 'error'
                    error: subprocess-exited-with-error
            
                    × Running setup.py install for cffi did not run successfully.
                    │ exit code: 1
                    ╰─> [40 lines of output]
                        /opt/iobroker/node_modules/iobroker.esphome/python_modules/lib/python3.9/site-packages/setuptools/config/setupcfg.py:459: SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use license_files instead.
                          warnings.warn(msg, warning_class)
                        running install
                        /opt/iobroker/node_modules/iobroker.esphome/python_modules/lib/python3.9/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
                          warnings.warn(
                        running build
                        running build_py
                        creating build
                        creating build/lib.linux-armv7l-cpython-39
                        creating build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/setuptools_ext.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/lock.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/vengine_gen.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/backend_ctypes.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/error.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/model.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/__init__.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/ffiplatform.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/api.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/cparser.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/vengine_cpy.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/cffi_opcode.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/commontypes.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/verifier.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/pkgconfig.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/recompiler.py -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/_cffi_include.h -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/parse_c_type.h -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/_embedding.h -> build/lib.linux-armv7l-cpython-39/cffi
                        copying cffi/_cffi_errors.h -> build/lib.linux-armv7l-cpython-39/cffi
                        running build_ext
                        building '_cffi_backend' extension
                        creating build/temp.linux-armv7l-cpython-39
                        creating build/temp.linux-armv7l-cpython-39/c
                        arm-linux-gnueabihf-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -ffile-prefix-map=/python3.9-3.9.2=. -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/include/python3.9 -c c/_cffi_backend.c -o build/temp.linux-armv7l-cpython-39/c/_cffi_backend.o
                        c/_cffi_backend.c:2:10: fatal error: Python.h: Datei oder Verzeichnis nicht gefunden
                            2 | #include <Python.h>
                              |          ^~~~~~~~~~
                        compilation terminated.
                        error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1
                        [end of output]
            
                    note: This error originates from a subprocess, and is likely not a problem with pip.
                  error: legacy-install-failure
            
                  × Encountered error while trying to install package.
                  ╰─> cffi
            
                  note: This is an issue with the package mentioned above, not pip.
                  hint: See above for output from the failure.
                  [end of output]
            
              note: This error originates from a subprocess, and is likely not a problem with pip.
            error: subprocess-exited-with-error
            
            × pip subprocess to install build dependencies did not run successfully.
            │ exit code: 1
            ╰─> See above for output.
            
            note: This error originates from a subprocess, and is likely not a problem with pip.
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
            
            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-06-11T12_14_44_232Z-debug.log
            pi@raspberrypi:/opt/iobroker
            

            Benötige ich für Python 3 eine Lizenz?

            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Tontechniker last edited by

              @tontechniker sagte in Probleme mit Installation von ESP Home@0.2.4:

              Benötige ich für Python 3 eine Lizenz?

              Nein, aber ggf. dev-Files und ein buildenvironment

              apt policy python-dev-is-python3 build-essential
              
              T 1 Reply Last reply Reply Quote 1
              • T
                Tontechniker @Thomas Braun last edited by

                @thomas-braun

                pi@raspberrypi:/opt/iobroker $ apt policy python-dev-is-python3 build-essential
                python-dev-is-python3:
                  Installiert:           (keine)
                  Installationskandidat: 3.9.2-1
                  Versionstabelle:
                     3.9.2-1 500
                        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                build-essential:
                  Installiert:           12.9
                  Installationskandidat: 12.9
                  Versionstabelle:
                 *** 12.9 500
                        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                        100 /var/lib/dpkg/status
                pi@raspberrypi:/opt/iobroker $
                
                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Tontechniker last edited by

                  @tontechniker sagte in Probleme mit Installation von ESP Home@0.2.4:

                  python-dev-is-python3

                  Dann installier das nach:

                  sudo apt install python-dev-is-python3
                  
                  T 1 Reply Last reply Reply Quote 1
                  • T
                    Tontechniker @Thomas Braun last edited by

                    @thomas-braun
                    Nach der Installation:

                    pi@raspberrypi:/opt/iobroker $ apt policy python-dev-is-python3 build-essential
                    python-dev-is-python3:
                      Installiert:           3.9.2-1
                      Installationskandidat: 3.9.2-1
                      Versionstabelle:
                     *** 3.9.2-1 500
                            500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                            100 /var/lib/dpkg/status
                    build-essential:
                      Installiert:           12.9
                      Installationskandidat: 12.9
                      Versionstabelle:
                     *** 12.9 500
                            500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                            100 /var/lib/dpkg/status
                    pi@raspberrypi:/opt/iobroker $
                    

                    Soll ich nochmal rebooten und versuchen ESP zu installieren?

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Tontechniker last edited by

                      @tontechniker

                      Ich vermute die Installation von esphome funktioniert nun.
                      Ansonsten wüsste ich auch nicht weiter.

                      T 1 Reply Last reply Reply Quote 1
                      • T
                        Tontechniker @Thomas Braun last edited by

                        @thomas-braun
                        Hatte immernoch Fehlermeldung. Dann in Console Install nochmal gestartet und am Ende Fehlermeldung, dass Rust-Compiler >=1.41.0 sein muß. Habe dann "Pip" installiert und mit

                        pip install --upgrade Rust
                        

                        den Upgrade durchgeführt. Danach von Admin aus Install ESP gestartet und - siehe da! Es Funktioniert!
                        Vielen Dank für Deine/Eure Hilfe!!
                        Hans

                        J 1 Reply Last reply Reply Quote 0
                        • J
                          Jan1 @Tontechniker last edited by

                          @tontechniker
                          Da frag ich mich warum dass nur bei Dir so ein Umstand war den Adapter ans laufen zu bekommen?
                          Das Buster nach Bullseye upzugraden funktioniert zwar, aber ne Neuinstallation dauert nicht wirklich länger und ist definitiv sauber. Könnte ne mögliche Ursache sein, oder bei mir wurde das bei Dir nun manuell installierte Zeug im Zuge einer anderen Installation schon unbemerkt von mir bereits installiert. Hatte einfach mal den Adapter von GIT zum Testen geladen und lief sofort ohne Fehler durch.

                          T 1 Reply Last reply Reply Quote 1
                          • T
                            Tontechniker @Jan1 last edited by Tontechniker

                            @jan1 Ich kann Dir nicht sagen, wie das passiert ist. Ich habe vor einigen Monaten Bullseye auf einer SSD installiert, eingestellt und dann IoBroker installiert und dann mein IoBroker-Backup eingespielt.
                            Dir auch nochmal ein herzliches "DANKESCHÖN"!

                            J 1 Reply Last reply Reply Quote 0
                            • J
                              Jan1 @Tontechniker last edited by Jan1

                              @tontechniker
                              Ok, hattes Du nicht geschrieben, dass Du das Bullseye von Buster hochgezogen hast? Wenn nicht, dann ist es ja ne Neuinstallation, wobei man das eigentlich nicht von ner CD macht beim PI, sondern mit dem dafür vorgesehenen Tool 😉

                              Edit:
                              ok das mit dem Upgrade war der Kamerad aus dem anderen Thread.
                              Scheiß Konzentration Probleme nach Corna, LOL

                              1 Reply Last reply Reply Quote 0
                              • S
                                Sushibomba last edited by

                                Ich bekomme es leider auch nicht hin den espHome Adapter zu installieren.
                                Kann mir wer helfen 😞 ?

                                NPM version: 8.11.0
                                
                                Installing iobroker.esphome@0.2.4... (System call)
                                
                                host.Pi4ioBroker Cannot install iobroker.esphome@0.2.4: 1
                                
                                ERROR: Process exited with code 25
                                
                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @Sushibomba last edited by

                                  @sushibomba

                                  Installier den Adapter mit --debug-Option.
                                  Dann sieht man wo es da klemmen könnte.

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    Sushibomba @Thomas Braun last edited by

                                    @thomas-braun

                                    Könntest du mir schreiben welche Befehle ich dafür verwenden muss in Putty 😕

                                    Homoran 1 Reply Last reply Reply Quote 0
                                    • Homoran
                                      Homoran Global Moderator Administrators @Sushibomba last edited by

                                      @sushibomba Tanzen wir jetzt auf zwei Hochzeiten?

                                      S 1 Reply Last reply Reply Quote 0
                                      • S
                                        Sushibomba @Homoran last edited by

                                        @homoran

                                        Nein war nicht meine Absicht. Hatte nur in beiden geschrieben weil ich nicht wusste wo die Leute häufiger rein schauen 😞

                                        Homoran 1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators @Sushibomba last edited by

                                          @sushibomba sagte in Probleme mit Installation von ESP Home@0.2.4:

                                          @homoran

                                          Nein war nicht meine Absicht. Hatte nur in beiden geschrieben weil ich nicht wusste wo die Leute häufiger rein schauen 😞

                                          also doch eine Absicht dahinter

                                          S 1 Reply Last reply Reply Quote 0
                                          • S
                                            Sushibomba @Homoran last edited by Sushibomba

                                            @homoran
                                            Ja wenn man es so nimmt schon. Aber keine böse 😄

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            948
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            6
                                            109
                                            6129
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo