Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Tapo will sich mit der cloud verbinden (gelöst)

    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

    Tapo will sich mit der cloud verbinden (gelöst)

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      maximinus @Duffy last edited by

      @duffy

      Nachdem der Adapterentwickler auf Github empfohlen hatte die Version 0.2.9 zu verwenden, diese aber im ioBroker nicht zur Verfügung stand, habe ich nachdem ich die Version 0.0.2 über den Instanzentab entfernt hatte, mit npm install iobroker.tapo installiert.
      Da nach einem Restart die Instanz tapo.0 nicht aufschien, mit sudo systemctl restart iobroker.service ohne Erfolg aktualisiert.

      Darnach iobroker diag mit diesem Ergebnis

      ======== Start marking the full check here =========

      Skript v.2023-10-10
      
      *** BASE SYSTEM ***
         Static hostname: pivpn
               Icon name: computer
        Operating System: Raspbian GNU/Linux 11 (bullseye)
                  Kernel: Linux 6.1.21-v8+
            Architecture: arm64
      
      Model           : Raspberry Pi 4 Model B Rev 1.4
      Docker          : false
      Virtualization  : none
      Kernel          : aarch64
      Userland        : armhf
      
      Systemuptime and Load:
       02:53:26 up 12:43,  1 user,  load average: 0.15, 0.11, 0.31
      CPU threads: 4
      
      
      *** RASPBERRY THROTTLING ***
      Current issues:
      No throttling issues detected.
      
      Previously detected issues:
      No throttling issues detected.
      
      *** Time and Time Zones ***
                     Local time: Wed 2024-03-27 02:53:26 WET
                 Universal time: Wed 2024-03-27 02:53:26 UTC
                       RTC time: n/a
                      Time zone: Atlantic/Canary (WET, +0000)
      System clock synchronized: yes
                    NTP service: active
                RTC in local TZ: no
      
      *** User and Groups ***
      pi
      /home/pi
      pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker
      
      *** X-Server-Setup ***
      X-Server:       false
      Desktop:
      Terminal:       tty
      Boot Target:    multi-user.target
      
      *** MEMORY ***
                     total        used        free      shared  buff/cache   available
      Mem:            1.8G        666M        417M        3.0M        765M        1.1G
      Swap:            99M         42M         57M
      Total:          1.9G        709M        474M
      
               1849 M total memory
                666 M used memory
                288 M active memory
                931 M inactive memory
                417 M free memory
                123 M buffer memory
                641 M swap cache
                 99 M total swap
                 42 M used swap
                 57 M free swap
      
      Raspberry only:
      oom events: 0
      lifetime oom required: 0 Mbytes
      total time in oom handler: 0 ms
      max time spent in oom handler: 0 ms
      
      *** FAILED SERVICES ***
      
        UNIT             LOAD   ACTIVE SUB    DESCRIPTION
      * hciuart.service  loaded failed failed Configure Bluetooth Modems connected by UART
      * iobroker.service loaded failed failed ioBroker Server
      
      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.
      
      *** FILESYSTEM ***
      Filesystem     Type      Size  Used Avail Use% Mounted on
      /dev/root      ext4       29G  9.1G   19G  33% /
      devtmpfs       devtmpfs  667M     0  667M   0% /dev
      tmpfs          tmpfs     925M  1.6M  924M   1% /dev/shm
      tmpfs          tmpfs     370M  1.1M  369M   1% /run
      tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
      /dev/mmcblk0p1 vfat      255M   51M  205M  20% /boot
      tmpfs          tmpfs     185M     0  185M   0% /run/user/1000
      
      Messages concerning ext4 filesystem in dmesg:
      [Tue Mar 26 14:10:14 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=E4:5F:01:20:8D:54 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=bd727156-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=AT
      [Tue Mar 26 14:10:15 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
      [Tue Mar 26 14:10:15 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
      [Tue Mar 26 14:10:16 2024] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
      [Tue Mar 26 14:10:16 2024] EXT4-fs (mmcblk0p2): 1 orphan inode deleted
      [Tue Mar 26 14:10:16 2024] EXT4-fs (mmcblk0p2): recovery complete
      [Tue Mar 26 14:10:16 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
      [Tue Mar 26 14:10:16 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
      [Tue Mar 26 14:10:18 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.
      
      Show mounted filesystems \(real ones only\):
      TARGET  SOURCE         FSTYPE OPTIONS
      /       /dev/mmcblk0p2 ext4   rw,noatime
      `-/boot /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
      
      Files in neuralgic directories:
      
      /var:
      2.6G    /var/
      1.6G    /var/log
      1.3G    /var/log/journal/8f8800bc2dd742ba810579339a904aaf
      1.3G    /var/log/journal
      540M    /var/cache
      
      Archived and active journals take up 1.2G in the file system.
      
      /opt/iobroker/backups:
      2.2G    /opt/iobroker/backups/
      
      /opt/iobroker/iobroker-data:
      134M    /opt/iobroker/iobroker-data/
      82M     /opt/iobroker/iobroker-data/files
      67M     /opt/iobroker/iobroker-data/files/javascript.admin
      48M     /opt/iobroker/iobroker-data/files/javascript.admin/static
      47M     /opt/iobroker/iobroker-data/files/javascript.admin/static/js
      
      The five largest files in iobroker-data are:
      13M     /opt/iobroker/iobroker-data/objects.jsonl
      7.5M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/691.26ff76ce.chunk.js.map
      7.1M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.d3cce782.chunk.js.map
      6.3M    /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map
      6.0M    /opt/iobroker/iobroker-data/states.jsonl
      
      USB-Devices by-id:
      USB-Sticks -  Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id':
      
      find: '/dev/serial/by-id/': No such file or directory
      
      *** NodeJS-Installation ***
      
      /usr/bin/nodejs         v18.19.1
      /usr/bin/node           v18.19.1
      /usr/bin/npm            10.2.4
      /usr/bin/npx            10.2.4
      /usr/bin/corepack       0.22.0
      
      
      nodejs:
        Installed: 18.19.1-1nodesource1
        Candidate: 18.20.0-1nodesource1
        Version table:
           18.20.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
       *** 18.19.1-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
              100 /var/lib/dpkg/status
           18.19.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.18.2-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.18.1-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.18.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.17.1-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.17.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.16.1-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.16.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.15.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.14.2-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.14.1-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.14.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.13.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.12.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.11.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.10.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.9.1-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.9.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.8.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.7.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.6.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.5.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.4.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.3.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.2.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.1.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           18.0.0-1nodesource1 500
              500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
           12.22.12~dfsg-1~deb11u4 500
              500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
      
      Temp directories causing npm8 problem: 0
      No problems detected
      
      Errors in npm tree:
      npm ERR! code ELSPROBLEMS
      npm ERR! extraneous: @ampproject/remapping@2.3.0 /opt/iobroker/node_modules/@ampproject/remapping
      npm ERR! extraneous: @babel/code-frame@7.24.2 /opt/iobroker/node_modules/@babel/code-frame
      npm ERR! extraneous: @babel/compat-data@7.24.1 /opt/iobroker/node_modules/@babel/compat-data
      npm ERR! extraneous: @babel/core@7.24.3 /opt/iobroker/node_modules/@babel/core
      npm ERR! extraneous: @babel/generator@7.24.1 /opt/iobroker/node_modules/@babel/generator
      npm ERR! extraneous: @babel/helper-compilation-targets@7.23.6 /opt/iobroker/node_modules/@babel/helper-compilation-targets
      npm ERR! extraneous: @babel/helper-environment-visitor@7.22.20 /opt/iobroker/node_modules/@babel/helper-environment-visitor
      npm ERR! extraneous: @babel/helper-function-name@7.23.0 /opt/iobroker/node_modules/@babel/helper-function-name
      npm ERR! extraneous: @babel/helper-hoist-variables@7.22.5 /opt/iobroker/node_modules/@babel/helper-hoist-variables
      npm ERR! extraneous: @babel/helper-module-imports@7.24.3 /opt/iobroker/node_modules/@babel/helper-module-imports
      npm ERR! extraneous: @babel/helper-module-transforms@7.23.3 /opt/iobroker/node_modules/@babel/helper-module-transforms
      npm ERR! extraneous: @babel/helper-simple-access@7.22.5 /opt/iobroker/node_modules/@babel/helper-simple-access
      npm ERR! extraneous: @babel/helper-split-export-declaration@7.22.6 /opt/iobroker/node_modules/@babel/helper-split-export-declaration
      npm ERR! extraneous: @babel/helper-string-parser@7.24.1 /opt/iobroker/node_modules/@babel/helper-string-parser
      npm ERR! extraneous: @babel/helper-validator-identifier@7.22.20 /opt/iobroker/node_modules/@babel/helper-validator-identifier
      npm ERR! extraneous: @babel/helper-validator-option@7.23.5 /opt/iobroker/node_modules/@babel/helper-validator-option
      npm ERR! extraneous: @babel/helpers@7.24.1 /opt/iobroker/node_modules/@babel/helpers
      npm ERR! extraneous: @babel/highlight@7.24.2 /opt/iobroker/node_modules/@babel/highlight
      npm ERR! extraneous: @babel/parser@7.24.1 /opt/iobroker/node_modules/@babel/parser
      npm ERR! extraneous: @babel/template@7.24.0 /opt/iobroker/node_modules/@babel/template
      npm ERR! extraneous: @babel/traverse@7.24.1 /opt/iobroker/node_modules/@babel/traverse
      npm ERR! extraneous: @babel/types@7.24.0 /opt/iobroker/node_modules/@babel/types
      npm ERR! extraneous: @emnapi/core@1.1.0 /opt/iobroker/node_modules/@emnapi/core
      npm ERR! extraneous: @emnapi/runtime@1.1.0 /opt/iobroker/node_modules/@emnapi/runtime
      npm ERR! extraneous: @istanbuljs/load-nyc-config@1.1.0 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config
      npm ERR! extraneous: @istanbuljs/schema@0.1.3 /opt/iobroker/node_modules/@istanbuljs/schema
      npm ERR! extraneous: @jridgewell/gen-mapping@0.3.5 /opt/iobroker/node_modules/@jridgewell/gen-mapping
      npm ERR! extraneous: @jridgewell/resolve-uri@3.1.2 /opt/iobroker/node_modules/@jridgewell/resolve-uri
      npm ERR! extraneous: @jridgewell/set-array@1.2.1 /opt/iobroker/node_modules/@jridgewell/set-array
      npm ERR! extraneous: @jridgewell/sourcemap-codec@1.4.15 /opt/iobroker/node_modules/@jridgewell/sourcemap-codec
      npm ERR! extraneous: @jridgewell/trace-mapping@0.3.25 /opt/iobroker/node_modules/@jridgewell/trace-mapping
      npm ERR! extraneous: @napi-rs/wasm-runtime@0.1.2 /opt/iobroker/node_modules/@napi-rs/wasm-runtime
      npm ERR! extraneous: @node-rs/jieba-android-arm-eabi@ /opt/iobroker/node_modules/@node-rs/jieba-android-arm-eabi
      npm ERR! extraneous: @node-rs/jieba-android-arm64@ /opt/iobroker/node_modules/@node-rs/jieba-android-arm64
      npm ERR! extraneous: @node-rs/jieba-darwin-arm64@ /opt/iobroker/node_modules/@node-rs/jieba-darwin-arm64
      npm ERR! extraneous: @node-rs/jieba-darwin-x64@ /opt/iobroker/node_modules/@node-rs/jieba-darwin-x64
      npm ERR! extraneous: @node-rs/jieba-freebsd-x64@ /opt/iobroker/node_modules/@node-rs/jieba-freebsd-x64
      npm ERR! extraneous: @node-rs/jieba-linux-arm-gnueabihf@1.10.0 /opt/iobroker/node_modules/@node-rs/jieba-linux-arm-gnueabihf
      npm ERR! extraneous: @node-rs/jieba-linux-arm64-gnu@ /opt/iobroker/node_modules/@node-rs/jieba-linux-arm64-gnu
      npm ERR! extraneous: @node-rs/jieba-linux-arm64-musl@ /opt/iobroker/node_modules/@node-rs/jieba-linux-arm64-musl
      npm ERR! extraneous: @node-rs/jieba-linux-x64-gnu@ /opt/iobroker/node_modules/@node-rs/jieba-linux-x64-gnu
      npm ERR! extraneous: @node-rs/jieba-linux-x64-musl@ /opt/iobroker/node_modules/@node-rs/jieba-linux-x64-musl
      npm ERR! extraneous: @node-rs/jieba-wasm32-wasi@ /opt/iobroker/node_modules/@node-rs/jieba-wasm32-wasi
      npm ERR! extraneous: @node-rs/jieba-win32-arm64-msvc@ /opt/iobroker/node_modules/@node-rs/jieba-win32-arm64-msvc
      npm ERR! extraneous: @node-rs/jieba-win32-ia32-msvc@ /opt/iobroker/node_modules/@node-rs/jieba-win32-ia32-msvc
      npm ERR! extraneous: @node-rs/jieba-win32-x64-msvc@ /opt/iobroker/node_modules/@node-rs/jieba-win32-x64-msvc
      npm ERR! extraneous: @node-rs/jieba@1.10.0 /opt/iobroker/node_modules/@node-rs/jieba
      npm ERR! extraneous: @tybys/wasm-util@0.8.1 /opt/iobroker/node_modules/@tybys/wasm-util
      npm ERR! extraneous: @types/parse-json@4.0.2 /opt/iobroker/node_modules/@types/parse-json
      npm ERR! extraneous: aggregate-error@3.1.0 /opt/iobroker/node_modules/aggregate-error
      npm ERR! extraneous: append-transform@2.0.0 /opt/iobroker/node_modules/append-transform
      npm ERR! extraneous: archy@1.0.0 /opt/iobroker/node_modules/archy
      npm ERR! extraneous: babel-plugin-macros@2.8.0 /opt/iobroker/node_modules/babel-plugin-macros
      npm ERR! extraneous: babel-plugin-preval@4.0.0 /opt/iobroker/node_modules/babel-plugin-preval
      npm ERR! extraneous: browserslist@4.23.0 /opt/iobroker/node_modules/browserslist
      npm ERR! extraneous: caching-transform@4.0.0 /opt/iobroker/node_modules/caching-transform
      npm ERR! extraneous: callsites@3.1.0 /opt/iobroker/node_modules/callsites
      npm ERR! extraneous: caniuse-lite@1.0.30001600 /opt/iobroker/node_modules/caniuse-lite
      npm ERR! extraneous: clean-stack@2.2.0 /opt/iobroker/node_modules/clean-stack
      npm ERR! extraneous: commander@1.1.1 /opt/iobroker/node_modules/commander
      npm ERR! extraneous: commondir@1.0.1 /opt/iobroker/node_modules/commondir
      npm ERR! extraneous: convert-source-map@1.9.0 /opt/iobroker/node_modules/convert-source-map
      npm ERR! extraneous: cosmiconfig@6.0.0 /opt/iobroker/node_modules/cosmiconfig
      npm ERR! extraneous: default-require-extensions@3.0.1 /opt/iobroker/node_modules/default-require-extensions
      npm ERR! extraneous: electron-to-chromium@1.4.717 /opt/iobroker/node_modules/electron-to-chromium
      npm ERR! extraneous: error-ex@1.3.2 /opt/iobroker/node_modules/error-ex
      npm ERR! extraneous: es6-error@4.1.1 /opt/iobroker/node_modules/es6-error
      npm ERR! extraneous: escape-string-regexp@1.0.5 /opt/iobroker/node_modules/escape-string-regexp
      npm ERR! extraneous: esprima@4.0.1 /opt/iobroker/node_modules/esprima
      npm ERR! extraneous: find-cache-dir@3.3.2 /opt/iobroker/node_modules/find-cache-dir
      npm ERR! extraneous: foreground-child@2.0.0 /opt/iobroker/node_modules/foreground-child
      npm ERR! extraneous: fromentries@1.3.2 /opt/iobroker/node_modules/fromentries
      npm ERR! extraneous: gensync@1.0.0-beta.2 /opt/iobroker/node_modules/gensync
      npm ERR! extraneous: get-package-type@0.1.0 /opt/iobroker/node_modules/get-package-type
      npm ERR! extraneous: globals@11.12.0 /opt/iobroker/node_modules/globals
      npm ERR! extraneous: hasha@5.2.2 /opt/iobroker/node_modules/hasha
      npm ERR! extraneous: html-escaper@2.0.2 /opt/iobroker/node_modules/html-escaper
      npm ERR! extraneous: import-fresh@3.3.0 /opt/iobroker/node_modules/import-fresh
      npm ERR! extraneous: imurmurhash@0.1.4 /opt/iobroker/node_modules/imurmurhash
      npm ERR! extraneous: indent-string@4.0.0 /opt/iobroker/node_modules/indent-string
      npm ERR! extraneous: iobroker.lovelace@4.1.2 /opt/iobroker/node_modules/iobroker.lovelace
      npm ERR! extraneous: iobroker.type-detector@3.0.5 /opt/iobroker/node_modules/iobroker.type-detector
      npm ERR! extraneous: is-core-module@2.13.1 /opt/iobroker/node_modules/is-core-module
      npm ERR! extraneous: is-windows@1.0.2 /opt/iobroker/node_modules/is-windows
      npm ERR! extraneous: istanbul-lib-coverage@3.2.2 /opt/iobroker/node_modules/istanbul-lib-coverage
      npm ERR! extraneous: istanbul-lib-hook@3.0.0 /opt/iobroker/node_modules/istanbul-lib-hook
      npm ERR! extraneous: istanbul-lib-instrument@4.0.3 /opt/iobroker/node_modules/istanbul-lib-instrument
      npm ERR! extraneous: istanbul-lib-processinfo@2.0.3 /opt/iobroker/node_modules/istanbul-lib-processinfo
      npm ERR! extraneous: istanbul-lib-report@3.0.1 /opt/iobroker/node_modules/istanbul-lib-report
      npm ERR! extraneous: istanbul-lib-source-maps@4.0.1 /opt/iobroker/node_modules/istanbul-lib-source-maps
      npm ERR! extraneous: istanbul-reports@3.1.7 /opt/iobroker/node_modules/istanbul-reports
      npm ERR! extraneous: js-tokens@4.0.0 /opt/iobroker/node_modules/js-tokens
      npm ERR! extraneous: jsesc@2.5.2 /opt/iobroker/node_modules/jsesc
      npm ERR! extraneous: json-parse-even-better-errors@2.3.1 /opt/iobroker/node_modules/json-parse-even-better-errors
      npm ERR! extraneous: jstimezonedetect@1.0.7 /opt/iobroker/node_modules/jstimezonedetect
      npm ERR! extraneous: keypress@0.1.0 /opt/iobroker/node_modules/keypress
      npm ERR! extraneous: lines-and-columns@1.2.4 /opt/iobroker/node_modules/lines-and-columns
      npm ERR! extraneous: lodash.flattendeep@4.4.0 /opt/iobroker/node_modules/lodash.flattendeep
      npm ERR! extraneous: node-preload@0.2.1 /opt/iobroker/node_modules/node-preload
      npm ERR! extraneous: node-releases@2.0.14 /opt/iobroker/node_modules/node-releases
      npm ERR! extraneous: nodejieba@2.5.2 /opt/iobroker/node_modules/nodejieba
      npm ERR! extraneous: nyc@15.1.0 /opt/iobroker/node_modules/nyc
      npm ERR! extraneous: package-hash@4.0.0 /opt/iobroker/node_modules/package-hash
      npm ERR! extraneous: parent-module@1.0.1 /opt/iobroker/node_modules/parent-module
      npm ERR! extraneous: parse-json@5.2.0 /opt/iobroker/node_modules/parse-json
      npm ERR! extraneous: path-parse@1.0.7 /opt/iobroker/node_modules/path-parse
      npm ERR! extraneous: path-type@4.0.0 /opt/iobroker/node_modules/path-type
      npm ERR! extraneous: pinyin@3.1.0 /opt/iobroker/node_modules/pinyin
      npm ERR! extraneous: pkg-dir@4.2.0 /opt/iobroker/node_modules/pkg-dir
      npm ERR! extraneous: preval.macro@4.0.0 /opt/iobroker/node_modules/preval.macro
      npm ERR! extraneous: process-on-spawn@1.0.0 /opt/iobroker/node_modules/process-on-spawn
      npm ERR! extraneous: release-zalgo@1.0.0 /opt/iobroker/node_modules/release-zalgo
      npm ERR! extraneous: resolve-from@5.0.0 /opt/iobroker/node_modules/resolve-from
      npm ERR! extraneous: resolve@1.22.8 /opt/iobroker/node_modules/resolve
      npm ERR! extraneous: segmentit@2.0.3 /opt/iobroker/node_modules/segmentit
      npm ERR! extraneous: spawn-wrap@2.0.0 /opt/iobroker/node_modules/spawn-wrap
      npm ERR! extraneous: sprintf-js@1.0.3 /opt/iobroker/node_modules/sprintf-js
      npm ERR! extraneous: strip-bom@4.0.0 /opt/iobroker/node_modules/strip-bom
      npm ERR! extraneous: supports-preserve-symlinks-flag@1.0.0 /opt/iobroker/node_modules/supports-preserve-symlinks-flag
      npm ERR! extraneous: test-exclude@6.0.0 /opt/iobroker/node_modules/test-exclude
      npm ERR! extraneous: to-fast-properties@2.0.0 /opt/iobroker/node_modules/to-fast-properties
      npm ERR! extraneous: translit-rus-eng@1.0.8 /opt/iobroker/node_modules/translit-rus-eng
      npm ERR! extraneous: type-fest@0.8.1 /opt/iobroker/node_modules/type-fest
      npm ERR! extraneous: typedarray-to-buffer@3.1.5 /opt/iobroker/node_modules/typedarray-to-buffer
      npm ERR! extraneous: update-browserslist-db@1.0.13 /opt/iobroker/node_modules/update-browserslist-db
      npm ERR! extraneous: write-file-atomic@3.0.3 /opt/iobroker/node_modules/write-file-atomic
      npm ERR! extraneous: yaml@1.10.2 /opt/iobroker/node_modules/yaml
      npm ERR! extraneous: convert-source-map@2.0.0 /opt/iobroker/node_modules/@babel/core/node_modules/convert-source-map
      npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/@babel/core/node_modules/debug
      npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/@babel/core/node_modules/ms
      npm ERR! extraneous: semver@6.3.1 /opt/iobroker/node_modules/@babel/core/node_modules/semver
      npm ERR! extraneous: lru-cache@5.1.1 /opt/iobroker/node_modules/@babel/helper-compilation-targets/node_modules/lru-cache
      npm ERR! extraneous: semver@6.3.1 /opt/iobroker/node_modules/@babel/helper-compilation-targets/node_modules/semver
      npm ERR! extraneous: yallist@3.1.1 /opt/iobroker/node_modules/@babel/helper-compilation-targets/node_modules/yallist
      npm ERR! extraneous: ansi-styles@3.2.1 /opt/iobroker/node_modules/@babel/highlight/node_modules/ansi-styles
      npm ERR! extraneous: chalk@2.4.2 /opt/iobroker/node_modules/@babel/highlight/node_modules/chalk
      npm ERR! extraneous: has-flag@3.0.0 /opt/iobroker/node_modules/@babel/highlight/node_modules/has-flag
      npm ERR! extraneous: supports-color@5.5.0 /opt/iobroker/node_modules/@babel/highlight/node_modules/supports-color
      npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/@babel/traverse/node_modules/debug
      npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/@babel/traverse/node_modules/ms
      npm ERR! extraneous: argparse@1.0.10 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config/node_modules/argparse
      npm ERR! extraneous: js-yaml@3.14.1 /opt/iobroker/node_modules/@istanbuljs/load-nyc-config/node_modules/js-yaml
      npm ERR! invalid: @node-rs/jieba-android-arm-eabi@ /opt/iobroker/node_modules/@node-rs/jieba-android-arm-eabi
      npm ERR! invalid: @node-rs/jieba-android-arm64@ /opt/iobroker/node_modules/@node-rs/jieba-android-arm64
      npm ERR! invalid: @node-rs/jieba-darwin-arm64@ /opt/iobroker/node_modules/@node-rs/jieba-darwin-arm64
      npm ERR! invalid: @node-rs/jieba-darwin-x64@ /opt/iobroker/node_modules/@node-rs/jieba-darwin-x64
      npm ERR! invalid: @node-rs/jieba-freebsd-x64@ /opt/iobroker/node_modules/@node-rs/jieba-freebsd-x64
      npm ERR! invalid: @node-rs/jieba-linux-arm64-gnu@ /opt/iobroker/node_modules/@node-rs/jieba-linux-arm64-gnu
      npm ERR! invalid: @node-rs/jieba-linux-arm64-musl@ /opt/iobroker/node_modules/@node-rs/jieba-linux-arm64-musl
      npm ERR! invalid: @node-rs/jieba-linux-x64-gnu@ /opt/iobroker/node_modules/@node-rs/jieba-linux-x64-gnu
      npm ERR! invalid: @node-rs/jieba-linux-x64-musl@ /opt/iobroker/node_modules/@node-rs/jieba-linux-x64-musl
      npm ERR! invalid: @node-rs/jieba-wasm32-wasi@ /opt/iobroker/node_modules/@node-rs/jieba-wasm32-wasi
      npm ERR! invalid: @node-rs/jieba-win32-arm64-msvc@ /opt/iobroker/node_modules/@node-rs/jieba-win32-arm64-msvc
      npm ERR! invalid: @node-rs/jieba-win32-ia32-msvc@ /opt/iobroker/node_modules/@node-rs/jieba-win32-ia32-msvc
      npm ERR! invalid: @node-rs/jieba-win32-x64-msvc@ /opt/iobroker/node_modules/@node-rs/jieba-win32-x64-msvc
      npm ERR! extraneous: is-arrayish@0.2.1 /opt/iobroker/node_modules/error-ex/node_modules/is-arrayish
      npm ERR! extraneous: resolve-from@4.0.0 /opt/iobroker/node_modules/import-fresh/node_modules/resolve-from
      npm ERR! extraneous: semver@6.3.1 /opt/iobroker/node_modules/istanbul-lib-instrument/node_modules/semver
      npm ERR! extraneous: p-map@3.0.0 /opt/iobroker/node_modules/istanbul-lib-processinfo/node_modules/p-map
      npm ERR! extraneous: uuid@8.3.2 /opt/iobroker/node_modules/istanbul-lib-processinfo/node_modules/uuid
      npm ERR! extraneous: make-dir@4.0.0 /opt/iobroker/node_modules/istanbul-lib-report/node_modules/make-dir
      npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/istanbul-lib-source-maps/node_modules/debug
      npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/istanbul-lib-source-maps/node_modules/ms
      npm ERR! extraneous: node-addon-api@3.2.1 /opt/iobroker/node_modules/nodejieba/node_modules/node-addon-api
      npm ERR! extraneous: brace-expansion@1.1.11 /opt/iobroker/node_modules/nyc/node_modules/brace-expansion
      npm ERR! extraneous: cliui@6.0.0 /opt/iobroker/node_modules/nyc/node_modules/cliui
      npm ERR! extraneous: glob@7.2.3 /opt/iobroker/node_modules/nyc/node_modules/glob
      npm ERR! extraneous: minimatch@3.1.2 /opt/iobroker/node_modules/nyc/node_modules/minimatch
      npm ERR! extraneous: p-map@3.0.0 /opt/iobroker/node_modules/nyc/node_modules/p-map
      npm ERR! extraneous: wrap-ansi@6.2.0 /opt/iobroker/node_modules/nyc/node_modules/wrap-ansi
      npm ERR! extraneous: y18n@4.0.3 /opt/iobroker/node_modules/nyc/node_modules/y18n
      npm ERR! extraneous: yargs-parser@18.1.3 /opt/iobroker/node_modules/nyc/node_modules/yargs-parser
      npm ERR! extraneous: yargs@15.4.1 /opt/iobroker/node_modules/nyc/node_modules/yargs
      npm ERR! extraneous: brace-expansion@1.1.11 /opt/iobroker/node_modules/test-exclude/node_modules/brace-expansion
      npm ERR! extraneous: glob@7.2.3 /opt/iobroker/node_modules/test-exclude/node_modules/glob
      npm ERR! extraneous: minimatch@3.1.2 /opt/iobroker/node_modules/test-exclude/node_modules/minimatch
      npm ERR! invalid: fsevents@ /opt/iobroker/node_modules/fsevents
      
      npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-03-27T02_53_33_337Z-debug-0.log
      
      *** ioBroker-Installation ***
      
      ioBroker Status
      iobroker is not running on this host.
      
      No iobroker host is running.
      
      Objects type: redis
      States  type: redis
      
      Core adapters versions
      js-controller:  5.0.19
      admin:          6.13.16
      javascript:     7.8.0
      
      Adapters from github:   0
      
      Adapter State
        system.adapter.admin.0                  : admin                 : pivpn                                    -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        system.adapter.alexa2.0                 : alexa2                : pivpn                                    -  enabled
        system.adapter.alias-manager.0          : alias-manager         : pivpn                                    -  enabled
        system.adapter.backitup.0               : backitup              : pivpn                                    -  enabled
        system.adapter.devices.0                : devices               : pivpn                                    -  enabled
        system.adapter.discovery.0              : discovery             : pivpn                                    -  enabled
        system.adapter.flot.0                   : flot                  : pivpn                                    -  enabled
        system.adapter.habpanel.0               : habpanel              : pivpn                                    -  enabled
        system.adapter.influxdb.0               : influxdb              : pivpn                                    -  enabled, port: 8086
        system.adapter.iqontrol.0               : iqontrol              : pivpn                                    -  enabled
        system.adapter.javascript.0             : javascript            : pivpn                                    -  enabled
        system.adapter.mqtt.0                   : mqtt                  : pivpn                                    - disabled, port: 1886, bind: 192.168.1.9
        system.adapter.node-red.0               : node-red              : pivpn                                    -  enabled, port: 1880, bind: 0.0.0.0
        system.adapter.parser.0                 : parser                : pivpn                                    - disabled
        system.adapter.rpi2.0                   : rpi2                  : pivpn                                    -  enabled
        system.adapter.sonoff.0                 : sonoff                : pivpn                                    -  enabled, port: 1500, bind: 0.0.0.0
        system.adapter.telegram.0               : telegram              : pivpn                                    -  enabled, port: 8443, bind: 0.0.0.0
        system.adapter.tuya.0                   : tuya                  : pivpn                                    -  enabled
        system.adapter.vis-2-widgets-energy.0   : vis-2-widgets-energy  : pivpn                                    -  enabled
        system.adapter.vis-2-widgets-gauges.0   : vis-2-widgets-gauges  : pivpn                                    -  enabled
        system.adapter.vis-2-widgets-jaeger-design.0: vis-2-widgets-jaeger-design: pivpn                                    -  enabled
        system.adapter.vis-2.0                  : vis-2                 : pivpn                                    -  enabled
        system.adapter.vis-plumb.0              : vis-plumb             : pivpn                                    -  enabled
        system.adapter.vis.0                    : vis                   : pivpn                                    -  enabled
        system.adapter.web.0                    : web                   : pivpn                                    -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      
      + instance is alive
      
      Enabled adapters with bindings
        system.adapter.admin.0                  : admin                 : pivpn                                    -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        system.adapter.influxdb.0               : influxdb              : pivpn                                    -  enabled, port: 8086
        system.adapter.node-red.0               : node-red              : pivpn                                    -  enabled, port: 1880, bind: 0.0.0.0
        system.adapter.sonoff.0                 : sonoff                : pivpn                                    -  enabled, port: 1500, bind: 0.0.0.0
        system.adapter.telegram.0               : telegram              : pivpn                                    -  enabled, port: 8443, bind: 0.0.0.0
        system.adapter.web.0                    : web                   : pivpn                                    -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
      
      ioBroker-Repositories
      stable        : http://download.iobroker.net/sources-dist.json
      beta          : http://download.iobroker.net/sources-dist-latest.json
      
      Active repo(s): stable
      
      Installed ioBroker-Instances
      Used repository: stable
      Adapter    "admin"        : 6.13.16  , installed 6.13.16
      Adapter    "alexa2"       : 3.26.4   , installed 3.26.4
      Adapter    "alias-manager": 1.2.6    , installed 1.2.6
      Adapter    "backitup"     : 2.10.11  , installed 2.10.11
      Adapter    "devices"      : 1.1.5    , installed 1.1.5
      Adapter    "discovery"    : 4.4.0    , installed 4.4.0
      Adapter    "flot"         : 1.12.0   , installed 1.12.0
      Adapter    "fritzdect"    : 2.5.9    , installed 2.5.9
      Adapter    "habpanel"     : 0.5.0    , installed 0.5.0
      Adapter    "influxdb"     : 4.0.2    , installed 4.0.2
      Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
      Adapter    "javascript"   : 7.8.0    , installed 7.8.0
      Controller "js-controller": 5.0.19   , installed 5.0.19
      Adapter    "lovelace"     : 4.1.2    , installed 4.1.2
      Adapter    "mqtt"         : 5.2.0    , installed 5.2.0
      Adapter    "node-red"     : 5.1.0    , installed 5.1.0
      Adapter    "parser"       : 2.1.0    , installed 2.1.0
      Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
      Adapter    "shelly"       : 6.8.0    , installed 6.7.0  [Updatable]
      Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
      Adapter    "socketio"     : 6.6.0    , installed 6.6.0
      Adapter    "sonoff"       : 3.0.3    , installed 3.0.3
      Adapter    "tapo"         : 0.0.8    , installed 0.0.8
      Adapter    "telegram"     : 3.1.0    , installed 3.1.0
      Adapter    "tuya"         : 3.15.0   , installed 3.15.0
      Adapter    "vis"          : 1.5.4    , installed 1.5.4
      Adapter    "vis-2"        : 2.9.32   , installed 2.9.32
      Adapter    "vis-2-widgets-energy": 0.3.11, installed 0.3.9 [Updatable]
      Adapter    "vis-2-widgets-gauges": 1.0.2, installed 1.0.2
      Adapter    "vis-2-widgets-jaeger-design": 1.1.10, installed 1.1.10
      Adapter    "vis-2-widgets-material": 1.3.18, installed 1.3.18
      Adapter    "vis-materialdesign": 0.5.9, installed 0.5.9
      Adapter    "vis-plumb"    : 1.0.2    , installed 1.0.2
      Adapter    "web"          : 6.2.3    , installed 6.2.3
      Adapter    "ws"           : 2.5.10   , installed 2.5.10
      
      Objects and States
      Please stand by - This may take a while
      Objects:        2301
      States:         1682
      
      *** OS-Repositories and Updates ***
      Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
      Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
      Hit:3 https://repos.influxdata.com/debian bullseye InRelease
      Hit:4 https://packages.grafana.com/oss/deb stable InRelease
      Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
      Reading package lists...
      Pending Updates: 1
      
      *** Listening Ports ***
      Active Internet connections (only servers)
      Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
      tcp        0      0 0.0.0.0:514             0.0.0.0:*               LISTEN      0          14587      422/rsyslogd
      tcp        0      0 127.0.0.1:6379          0.0.0.0:*               LISTEN      112        13080      525/redis-server 12
      tcp        0      0 127.0.0.1:5335          0.0.0.0:*               LISTEN      0          15504      722/unbound
      tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      999        3847       766/pihole-FTL
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          3615       548/sshd: /usr/sbin
      tcp        0      0 127.0.0.1:8088          0.0.0.0:*               LISTEN      998        14861      740/influxd
      tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      0          15578      840/lighttpd
      tcp        0      0 127.0.0.1:4711          0.0.0.0:*               LISTEN      999        3853       766/pihole-FTL
      tcp        0      0 127.0.0.1:8953          0.0.0.0:*               LISTEN      0          15505      722/unbound
      tcp6       0      0 ::1:4711                :::*                    LISTEN      999        3854       766/pihole-FTL
      tcp6       0      0 :::514                  :::*                    LISTEN      0          14588      422/rsyslogd
      tcp6       0      0 :::3000                 :::*                    LISTEN      111        3955       882/grafana
      tcp6       0      0 :::8086                 :::*                    LISTEN      998        15628      740/influxd
      tcp6       0      0 ::1:6379                :::*                    LISTEN      112        13081      525/redis-server 12
      tcp6       0      0 :::53                   :::*                    LISTEN      999        3849       766/pihole-FTL
      tcp6       0      0 :::22                   :::*                    LISTEN      0          3617       548/sshd: /usr/sbin
      tcp6       0      0 :::80                   :::*                    LISTEN      0          15579      840/lighttpd
      udp        0      0 0.0.0.0:514             0.0.0.0:*                           0          14583      422/rsyslogd
      udp        0      0 0.0.0.0:51820           0.0.0.0:*                           0          13230      -
      udp        0      0 0.0.0.0:53              0.0.0.0:*                           999        3846       766/pihole-FTL
      udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          13101      736/dhcpcd
      udp        0      0 127.0.0.1:5335          0.0.0.0:*                           0          15503      722/unbound
      udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        12900      352/avahi-daemon: r
      udp        0      0 0.0.0.0:41243           0.0.0.0:*                           108        12902      352/avahi-daemon: r
      udp6       0      0 :::48490                :::*                                108        12903      352/avahi-daemon: r
      udp6       0      0 :::514                  :::*                                0          14584      422/rsyslogd
      udp6       0      0 :::51820                :::*                                0          13231      -
      udp6       0      0 :::53                   :::*                                999        3848       766/pihole-FTL
      udp6       0      0 :::5353                 :::*                                108        12901      352/avahi-daemon: r
      
      *** Log File - Last 25 Lines ***
      
      2024-03-27 02:36:19.517  - info: telegram.0 (2095) terminating
      2024-03-27 02:36:19.523  - info: sonoff.0 (2205) terminating
      2024-03-27 02:36:19.525  - info: telegram.0 (2095) Terminated (NO_ERROR): Without reason
      2024-03-27 02:36:19.526  - info: sonoff.0 (2205) Terminated (NO_ERROR): Without reason
      2024-03-27 02:36:19.539  - info: iqontrol.0 (2288) terminating
      2024-03-27 02:36:19.555  - info: admin.0 (2025) terminating
      2024-03-27 02:36:19.565  - info: javascript.0 (2051) terminating
      2024-03-27 02:36:19.666  - info: host.pivpn instance system.adapter.node-red.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.810  - info: host.pivpn instance system.adapter.rpi2.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.812  - info: host.pivpn instance system.adapter.alexa2.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.813  - info: host.pivpn instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.815  - info: host.pivpn instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.816  - info: host.pivpn instance system.adapter.iqontrol.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.818  - info: host.pivpn instance system.adapter.vis-2.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.839  - info: host.pivpn instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.887  - info: host.pivpn instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.889  - info: host.pivpn instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:19.890  - info: host.pivpn instance system.adapter.web.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:20.066  - info: host.pivpn instance system.adapter.telegram.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:20.079  - info: host.pivpn instance system.adapter.sonoff.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:22.012  - info: tuya.0 (2150) terminating
      2024-03-27 02:36:22.013  - info: tuya.0 (2150) Terminated (NO_ERROR): Without reason
      2024-03-27 02:36:22.551  - info: host.pivpn instance system.adapter.tuya.0 terminated with code 0 (NO_ERROR)
      2024-03-27 02:36:22.552  - info: host.pivpn All instances are stopped.
      2024-03-27 02:36:22.706  - info: host.pivpn terminated
      
      

      ============ Mark until here for C&P ===========

      Danach wie empfohlen npm Log
      ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-03-27T02_53_33_337Z-debug-0.log

      pi@pivpn:~/.npm/_logs $ cat 2024-03-27T02_39_38_147Z-debug-0.log
      0 verbose cli /usr/bin/node /usr/lib/node_modules/npm/bin/npm-cli.js
      1 info using npm@10.2.4
      2 info using node@v18.19.1
      3 timing npm:load:whichnode Completed in 3ms
      4 timing config:load:defaults Completed in 5ms
      5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 1ms
      6 timing config:load:builtin Completed in 1ms
      7 timing config:load:cli Completed in 8ms
      8 timing config:load:env Completed in 1ms
      9 timing config:load:file:/opt/iobroker/.npmrc Completed in 4ms
      10 timing config:load:project Completed in 6ms
      11 timing config:load:file:/home/pi/.npmrc Completed in 0ms
      12 timing config:load:user Completed in 1ms
      13 timing config:load:file:/usr/etc/npmrc Completed in 0ms
      14 timing config:load:global Completed in 0ms
      15 timing config:load:setEnvs Completed in 2ms
      16 timing config:load Completed in 28ms
      17 timing npm:load:configload Completed in 29ms
      18 timing config:load:flatten Completed in 8ms
      19 timing npm:load:mkdirpcache Completed in 1ms
      20 timing npm:load:mkdirplogs Completed in 0ms
      21 verbose title npm exec
      22 verbose argv "exec" "--version"
      23 timing npm:load:setTitle Completed in 3ms
      24 timing npm:load:display Completed in 2ms
      25 verbose logfile logs-max:10 dir:/home/pi/.npm/_logs/2024-03-27T02_39_38_147Z-
      26 verbose logfile /home/pi/.npm/_logs/2024-03-27T02_39_38_147Z-debug-0.log
      27 timing npm:load:logFile Completed in 25ms
      28 timing npm:load:timers Completed in 0ms
      29 timing npm:load:configScope Completed in 0ms
      30 timing npm:load Completed in 118ms
      31 verbose exit 0
      32 timing npm Completed in 137ms
      33 info ok
      pi@pivpn:~/.npm/_logs $
      

      Danach IOB fix

      keine Änderung, iob Läuft, Instanz tapo.0 fehlt

      Soll ich ein restore auf einen früheren Status machen oder lässt sich das beheben?

      LG Gerhard

      DJMarc75 1 Reply Last reply Reply Quote 0
      • DJMarc75
        DJMarc75 @maximinus last edited by

        @maximinus sagte in Tapo will sich mit der cloud verbinden:

        Instanz tapo.0 fehlt

        Die musst Du auch noch hinzufügen, da Du nur den Adapter installiert hast:

        (unter Adapter)

        Screenshot 2024-03-27 115327.png

        M 1 Reply Last reply Reply Quote 0
        • M
          maximinus @DJMarc75 last edited by

          @djmarc75

          Ich blicke da leider nicht durch. Ich dachte wenn ein Adapter installiert wird erzeugt er eine Instanz

          Wenn ich unter Adapter den TAPO aufrufe um das "+" zu drücken, stehen nur die Versionen 0.0.2 bis 0.0.8 zur Verfügung, es soll aber 0.2.9 sein.

          In der iob diag erscheint unter installierte Adapter tapo 0.0.8 auf, obwohl ich den doch zuvor entfernt hatte (die Angabe oben dass ich 0.0.2 entfernt hätte war falsch, es war 0.0.8)

          Gerhard

          DJMarc75 Duffy Thomas Braun 3 Replies Last reply Reply Quote 0
          • DJMarc75
            DJMarc75 @maximinus last edited by

            @maximinus

            Dann stelle KURZ Dein Repository auf Beta um, installiere die aktuelle Version vom Tapo und stelle bitte das Repository gleich danach auf Stable zurück.

            1 Reply Last reply Reply Quote 0
            • Duffy
              Duffy @maximinus last edited by Duffy

              @maximinus sagte in Tapo will sich mit der cloud verbinden:

              Ich blicke da leider nicht durch. Ich dachte wenn ein Adapter installiert wird erzeugt er eine Instanz

              Da bin ich auch immer von ausgegangen und bin beim simple-api auch schon drüber gestolpert.

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

                @maximinus

                Du steht im falschen Verzeichnis.
                Am besten die Finger komplett von npm direkt lassen und den wrapper 'iobroker' dafür verwenden, der setzt die Verzeichnisse nämlich gleich richtig.
                Vielleicht besser sogar noch über den Admin unter Experten-Optionen...

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

                  @thomas-braun

                  Meine letzte Installation von Tapo hatte ich über "stable" gemacht aber inzwischen wieder gelöscht da es nicht funktioniert hatte.

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

                    @maximinus sagte in Tapo will sich mit der cloud verbinden:

                    Ich dachte wenn ein Adapter installiert wird erzeugt er eine Instanz

                    Nicht bei GitHub-Installationen.
                    Und nur, wenn man dem Kram nicht im Home des Users 'pi' installiert sondern im richtigen Verzeichnis.

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

                      @thomas-braun

                      Man lernt nie aus.

                      Ich habe aber trotzdem noch eine Frage dazu.

                      Den simple-api Adapter hatte ich auch über Stable installiert und trotzdem musste ich erst auf das "+" klicken um eine Instanz zu bekommen.

                      Aber das soll es dann auch zu dem simple-api gewesen sein will nicht vom Thema ablenken, sorry.

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        maximinus @Duffy last edited by maximinus

                        @DJMarc75

                        Im beta nur die Ver 0.2.0 verfügbar

                        @Thomas Braun

                        Du steht im falschen Verzeichnis.

                        Ja, das habe ich leider zu spät bemerkt. Mein Verzeichnis sieht jetzt so aus:

                        pi@pivpn:~ $ ls -lah
                        total 152K
                        drwxr-xr-x  10 pi   pi   4.0K Mar 27 02:36 .
                        drwxr-xr-x   4 root root 4.0K Dec 13 14:16 ..
                        -rw-------   1 pi   pi   7.2K Mar 27 02:56 .bash_history
                        -rw-r--r--   1 pi   pi    220 Dec  5 02:39 .bash_logout
                        -rw-r--r--   1 pi   pi   3.7K Mar 27 02:36 .bashrc
                        drwxr-xr-x   4 pi   pi   4.0K Dec 13 14:18 .cache
                        drwx------   3 pi   pi   4.0K Dec 14 01:01 .config
                        drwxrwxrwx   2 pi   pi   4.0K Dec 12 21:32 configs
                        -rw-r--r--   1 pi   pi    348 Feb 16 19:34 .influx_history
                        drwxr-xr-x   2 pi   pi   4.0K Dec 13 14:18 .iobroker
                        drwxr-xr-x   3 pi   pi   4.0K Dec 26 14:41 .local
                        drwxr-xr-x 162 pi   pi   4.0K Mar 27 02:24 node_modules
                        drwxr-xr-x   4 pi   pi   4.0K Dec 13 14:18 .npm
                        -rw-------   1 pi   pi     36 Dec 13 14:14 .npmrc
                        -rw-r--r--   1 pi   pi     58 Mar 27 02:24 package.json
                        -rw-r--r--   1 pi   pi    73K Mar 27 02:24 package-lock.json
                        -rw-r--r--   1 pi   pi    807 Dec  5 02:39 .profile
                        -rw-------   1 pi   pi    110 Dec 25 19:00 .rediscli_history
                        drwxr-xr-x   3 pi   pi   4.0K Dec 29 21:05 rpi-clone
                        pi@pivpn:~ $
                        

                        Was alles muss da wieder weg?

                        Am besten die Finger komplett von npm direkt lassen und den wrapper 'iobroker' dafür verwenden, der setzt die Verzeichnisse nämlich gleich richtig.

                        Wäre mir ohnedies am liebsten gewesen; nur wusste/weiss ich nicht wie ich zu 0.2.9 komme. Ich habe mich davon verleiten lassen:

                        Git TAPO.jpg

                        Vielleicht besser sogar noch über den Admin unter Experten-Optionen...

                        Mit Experten Einstellung und beta repositories bin ich jetzt auf Ver. 0.2.0

                        Der Adapter ist grün, hat die Kamera offline gemeldet - obwohl online - und empfohlen die IP manuell nachzutragen was ich gemacht habe. Es kommen keine Fehlermeldungen mehr aber jetzt gibt es den Datenpunkt motionEvent nicht mehr.

                        Das ist das log

                        tapo.0
                        	2024-03-27 17:55:17.488	info	Wait for connections
                        tapo.0
                        	2024-03-27 17:55:17.469	warn	No IP found for 802141D2D2775E47A3BDEA507CBF826921C449A4 put the device online or set the ip state manually
                        tapo.0
                        	2024-03-27 17:55:17.461	error	{"error_code":-20571,"msg":"Device is offline"}
                        tapo.0
                        	2024-03-27 17:55:17.160	warn	Error: write EPROTO 40F7ABF7:error:0A000152:SSL routines:final_renegotiate:unsafe legacy renegotiation disabled:../deps/openssl/openssl/ssl/statem/extensions.c:922:
                        tapo.0
                        	2024-03-27 17:55:16.744	info	Found 1 devices
                        tapo.0
                        	2024-03-27 17:55:16.456	info	Login succesfull
                        tapo.0
                        	2024-03-27 17:55:15.713	info	Login tp TAPO App
                        tapo.0
                        	2024-03-27 17:55:15.630	info	starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.tapo, node: v18.19.1, js-controller: 5.0.19
                        tapo.0
                        	2024-03-27 17:55:10.726	info	terminating
                        tapo.0
                        	2024-03-27 17:55:10.222	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
                        tapo.0
                        	2024-03-27 17:55:10.219	info	terminating
                        tapo.0
                        	2024-03-27 17:55:10.210	info	Got terminate signal TERMINATE_YOURSELF
                        tapo.0
                        	2024-03-27 17:53:57.905	error	Please set username and password in the instance settings
                        tapo.0
                        	2024-03-27 17:53:57.880	info	starting. Version 0.2.0 in /opt/iobroker/node_modules/iobroker.tapo, node: v18.19.1, js-controller: 5.0.19
                        

                        Die Kamera habe ich über die App neu gestartet aber im Log rührt sich nichts
                        Wahrscheinlichist es am besten zu warten bis 0.2.9 im beta oder stable ist.

                        Gerhard

                        DJMarc75 1 Reply Last reply Reply Quote 0
                        • DJMarc75
                          DJMarc75 @maximinus last edited by

                          @maximinus sagte in Tapo will sich mit der cloud verbinden:

                          Im beta nur die Ver 0.2.0 verfügbar

                          na das wage ich zu bezweifeln 🙂

                          Screenshot 2024-03-27 194337.png

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            maximinus @DJMarc75 last edited by maximinus

                            @djmarc75

                            Das gibts doch nicht, Bei mir sieht das so aus

                            WARNUNG: Aktuelles Repository ist "beta". Benutzung auf eigene Gefahr!
                            	
                            
                            Name
                            	
                            
                            Beschreibung
                            		
                            
                            Installiert
                            	
                            
                            Verfügbar
                            	
                            
                            Lizenz
                            	
                            
                            Installieren
                            	
                            TP-Link Tapo
                            Adapter für TP-Link Tapo	
                            	
                            0.2.0 (1~)
                            	
                            0.2.0
                            	MIT	
                            	MIT
                            

                            Das ist als beta Repository eingetragen

                            http://download.iobroker.net/sources-dist-latest.json
                            

                            Ich habe da nie etwas verstellt. Ist das bei dir anders?

                            Gerhard

                            Wie kommt man zu der einzeiligen Darstellung? wenn ich das nebenstehende als Text markiere und als code formatiere entsteht das was da oben abgebildet ist.
                            tapo.jpg

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

                              @maximinus

                              iob update
                              

                              sagt?

                              M 1 Reply Last reply Reply Quote 0
                              • M
                                maximinus @Thomas Braun last edited by

                                @thomas-braun

                                Sagt das:

                                pi@pivpn:~ $ iob update
                                Used repository: beta
                                Adapter    "admin"        : 6.15.2   , installed 6.13.16 [Updatable]
                                Adapter    "alexa2"       : 3.26.4   , installed 3.26.4
                                Adapter    "alias-manager": 1.2.6    , installed 1.2.6
                                Adapter    "backitup"     : 2.11.0   , installed 2.10.11 [Updatable]
                                Adapter    "devices"      : 1.1.5    , installed 1.1.5
                                Adapter    "discovery"    : 4.4.0    , installed 4.4.0
                                Adapter    "flot"         : 1.12.0   , installed 1.12.0
                                Adapter    "fritzdect"    : 2.5.9    , installed 2.5.9
                                Adapter    "habpanel"     : 0.5.0    , installed 0.5.0
                                Adapter    "influxdb"     : 4.0.2    , installed 4.0.2
                                Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
                                Adapter    "javascript"   : 7.11.0   , installed 7.8.0  [Updatable]
                                Controller "js-controller": 5.0.19   , installed 5.0.19
                                Adapter    "mqtt"         : 5.2.0    , installed 5.2.0
                                Adapter    "node-red"     : 5.2.0    , installed 5.1.0  [Updatable]
                                Adapter    "parser"       : 2.1.0    , installed 2.1.0
                                Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
                                Adapter    "shelly"       : 6.9.0    , installed 6.7.0  [Updatable]
                                Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
                                Adapter    "socketio"     : 6.6.1    , installed 6.6.0  [Updatable]
                                Adapter    "sonoff"       : 3.0.3    , installed 3.0.3
                                Adapter    "tapo"         : 0.2.9    , installed 0.2.0  [Updatable]
                                Adapter    "telegram"     : 3.1.0    , installed 3.1.0
                                Adapter    "tuya"         : 3.15.0   , installed 3.15.0
                                Adapter    "vis"          : 1.5.4    , installed 1.5.4
                                Adapter    "vis-2"        : 2.9.47   , installed 2.9.32 [Updatable]
                                Adapter    "vis-2-widgets-energy": 0.3.11, installed 0.3.9 [Updatable]
                                Adapter    "vis-2-widgets-gauges": 1.0.3, installed 1.0.2 [Updatable]
                                Adapter    "vis-2-widgets-jaeger-design": 1.1.19, installed 1.1.10 [Updatable]
                                Adapter    "vis-2-widgets-material": 1.3.25, installed 1.3.18 [Updatable]
                                Adapter    "vis-materialdesign": 0.5.9, installed 0.5.9
                                Adapter    "vis-plumb"    : 1.0.2    , installed 1.0.2
                                Adapter    "web"          : 6.2.5    , installed 6.2.3  [Updatable]
                                Adapter    "ws"           : 2.5.11   , installed 2.5.10 [Updatable]
                                pi@pivpn:~ $
                                

                                Komisch da steht auch tapo 0.2.9
                                Kann es sein dass da unterschiedliche repositories abgefragt werden?

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

                                  @maximinus sagte in Tapo will sich mit der cloud verbinden:

                                  Kann es sein dass da unterschiedliche repositories abgefragt werden?

                                  Nein. Aber GUIs 'schwindeln' gerne.

                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    maximinus @Thomas Braun last edited by

                                    @thomas-braun

                                    Aus mir nicht erklärlichen Gründen konnte ich das beta Repository auf 0.2.9 updaten. Datenpunkt motionEvent ist wieder hier und es kommen keine Fehlermeldungen

                                    Nochmals danke an alle.

                                    Gerhard

                                    fAz3rs adventures 1 Reply Last reply Reply Quote 0
                                    • fAz3rs adventures
                                      fAz3rs adventures @maximinus last edited by fAz3rs adventures

                                      @maximinus
                                      Servus zusammen,

                                      Ich bastel auch gerade mit dem Tapo Adapter rum (hab eine C210)
                                      Über beta konnte ich auch auf die 0.2.9 gehen und habe die Kamera auch Verbunden.
                                      Ich kann über die Datenpunkte auch den Alarm einschalten, alles andere jedoch nicht.
                                      Gerne würde ich über IoBroker die Kamera mit dem moveMotorStep Datenpunkt bewegen können
                                      Hat hier jemand erfahrung bzw nutzt die Funktion?

                                      Korrektur von meiner Seite:
                                      Die Datenpunkte stehen wohl einfach für das Modell nicht zur Verfügung

                                      Grüßle
                                      Timo

                                      M 1 Reply Last reply Reply Quote 0
                                      • M
                                        maximinus @fAz3rs adventures last edited by

                                        @faz3rs-adventures said in Tapo will sich mit der cloud verbinden (gelöst):

                                        Gerne würde ich über IoBroker die Kamera mit dem moveMotorStep Datenpunkt bewegen können.

                                        Habe ich eben ausprobiert: geht nicht. Das einzige was funktioniert ist motionEvent; der geht auf true wenn sich etwas bewegt

                                        LG Gerhard

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

                                        Support us

                                        ioBroker
                                        Community Adapters
                                        Donate

                                        451
                                        Online

                                        31.9k
                                        Users

                                        80.3k
                                        Topics

                                        1.3m
                                        Posts

                                        6
                                        34
                                        1559
                                        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