Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] Warema wmswebcontrol mit Fehler seit JS 5.0.12

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    [gelöst] Warema wmswebcontrol mit Fehler seit JS 5.0.12

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

      @blacktigga

      Im Log steht
      Node.js v18.17.1
      Was denn nun?

      Prüfen, am besten gleich auf nodejs 18.18.0 gehen.

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

        @thomas-braun
        Ja sorry, ist aktuell 18.7.1

        Hier wird ja grundsätzlich das node Update für größere Versionssprünge beschrieben, aber wie wäre die Syntax wenn ich genau 18.18.0 installieren möchte?

        Habe jetzt ganz simpel geacht, aber das nachfolgende hat nicht funktioniert:

        blacktigga@All-In-One-RasPi:~$ curl -sL https://deb.nodesource.com/setup_18.18.0 | sudo -E bash -
        bash: Zeile 1: Syntaxfehler beim unerwarteten Symbol »newline«
        bash: Zeile 1: `<!DOCTYPE html>''
        
        B 1 Reply Last reply Reply Quote 0
        • B
          BlackTigga @BlackTigga last edited by

          Denn wenn ich gemäß Update Beschreibung vorgehe erhalte ich:

          blacktigga@All-In-One-RasPi:~$ sudo apt-get install -y nodejs
          Paketlisten werden gelesen… Fertig
          Abhängigkeitsbaum wird aufgebaut… Fertig
          Statusinformationen werden eingelesen… Fertig
          nodejs ist schon die neueste Version (18.17.1-deb-1nodesource1).
          0 aktualisiert, 0 neu installiert, 0 zu entfernen und 6 nicht aktualisiert.
          
          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @BlackTigga last edited by Thomas Braun

            @blacktigga

            Mach es mit dem Skript. Siehe meine Signatur.

            Die Anleitung ist nicht mehr aktuell.

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

              @thomas-braun

              ioBroker nodejs fixer 2023-09-20
              
              Recommended nodejs-version is: 18.18.0
              Checking your installation now. Please be patient!
              
              Your current setup is:
              /usr/bin/nodejs         v18.17.1
              /usr/bin/node           v18.17.1
              /usr/bin/npm            9.6.7
              /usr/bin/npx            9.6.7
              /usr/bin/corepack       0.18.0
              
              We found these nodejs versions available for installation:
              
              nodejs:
                Installed: 18.17.1-deb-1nodesource1
                Candidate: 18.18.0-1nodesource1
                Version table:
                   18.18.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
               *** 18.17.1-deb-1nodesource1 100
                      100 /var/lib/dpkg/status
                   18.17.1-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.17.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.16.1-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.16.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.15.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.14.2-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.14.1-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.14.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.13.0+dfsg1-1 500
                      500 http://deb.debian.org/debian bookworm/main arm64 Packages
                   18.13.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.12.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.11.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.10.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.9.1-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.9.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.8.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.7.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.6.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.5.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.4.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.3.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.2.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.1.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
                   18.0.0-1nodesource1 1001
                      500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages
              
              
              
              Nothing to do - Your installation is using the correct paths.
              
              You are running nodejs v18.17.1. Do you want to install recommended version 18.18.0?
              
              Press <y> to continue or any other key to quit
              Trying to fix your installation now. Please be patient.
              Waiting for ioBroker to shut down - Give me a minute...
              ############################################################
              
              *** These repos are active on your system:
              Hit:1 http://deb.debian.org/debian bookworm InRelease
              Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
              Hit:3 http://security.debian.org bookworm-security InRelease
              Hit:4 http://deb.debian.org/debian bookworm-backports InRelease
              Hit:5 http://fi.mirror.armbian.de/apt bookworm InRelease
              Reading package lists... Done
              
              *** Installing ca-certificates, curl and gnupg, just in case they are missing.
              
              *** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source
              deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main
              Package: nodejs
              Pin: origin deb.nodesource.com
              Pin-Priority: 1001
              
              *** These repos are active after the adjustments:
              Hit:1 http://deb.debian.org/debian bookworm InRelease
              Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
              Hit:3 http://security.debian.org bookworm-security InRelease
              Hit:4 http://deb.debian.org/debian bookworm-backports InRelease
              Get:5 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]
              Hit:6 http://fi.mirror.armbian.de/apt bookworm InRelease
              Get:7 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages [5036 B]
              Get:8 https://deb.nodesource.com/node_18.x nodistro/main arm64 Contents (deb) [28.6 kB]
              Fetched 45.8 kB in 3s (16.2 kB/s)
              Reading package lists... Done
              
              Installing the recommended nodejs version now!
              
              We tried our best to fix your nodejs. Please run iob diag again to verify.
              
              *** RESTARTING ioBroker NOW! ***
               Please refresh or restart your browser in a few moments.
              

              Habe das Script jetzt dreimal durchlaufen lassen. Ich erhalte die zweite 'nothing to do' Meldung nicht. Wird nicht auf 18.18.0 aktualisiert:

              blacktigga@All-In-One-RasPi:~$ node -v
              v18.17.1
              
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @BlackTigga last edited by

                @blacktigga

                Geht nun mit der üblichen Systempflege.

                sudo apt update && sudo full-upgrade
                
                B 1 Reply Last reply Reply Quote 0
                • B
                  BlackTigga @Thomas Braun last edited by

                  @thomas-braun
                  Hat geklappt.

                  blacktigga@All-In-One-RasPi:~$ node -v
                  v18.18.0
                  

                  Die Fehlermeldung vom wmswebcontrol kommt aber leider weiterhin:

                  2023-09-24 13:13:32.619 - info: host.All-In-One-RasPi "system.adapter.wmswebcontrol.0" enabled
                  2023-09-24 13:13:37.065 - info: host.All-In-One-RasPi instance system.adapter.wmswebcontrol.0 started with pid 440703
                  2023-09-24 13:13:40.283 - error: host.All-In-One-RasPi Caught by controller[0]: node:internal/modules/cjs/loader:573
                  2023-09-24 13:13:40.284 - error: host.All-In-One-RasPi Caught by controller[0]: throw e;
                  2023-09-24 13:13:40.285 - error: host.All-In-One-RasPi Caught by controller[0]: ^
                  2023-09-24 13:13:40.286 - error: host.All-In-One-RasPi Caught by controller[0]: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/defaults' is not defined by "exports" in /opt/iobroker/node_modules/axios/package.json
                  2023-09-24 13:13:40.287 - error: host.All-In-One-RasPi Caught by controller[0]: at new NodeError (node:internal/errors:405:5)
                  2023-09-24 13:13:40.288 - error: host.All-In-One-RasPi Caught by controller[0]: at exportsNotFound (node:internal/modules/esm/resolve:362:10)
                  2023-09-24 13:13:40.288 - error: host.All-In-One-RasPi Caught by controller[0]: at packageExportsResolve (node:internal/modules/esm/resolve:698:9)
                  2023-09-24 13:13:40.289 - error: host.All-In-One-RasPi Caught by controller[0]: at resolveExports (node:internal/modules/cjs/loader:567:36)
                  2023-09-24 13:13:40.290 - error: host.All-In-One-RasPi Caught by controller[0]: at Module._findPath (node:internal/modules/cjs/loader:636:31)
                  2023-09-24 13:13:40.290 - error: host.All-In-One-RasPi Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1063:27)
                  2023-09-24 13:13:40.291 - error: host.All-In-One-RasPi Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27)
                  2023-09-24 13:13:40.291 - error: host.All-In-One-RasPi Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19)
                  2023-09-24 13:13:40.292 - error: host.All-In-One-RasPi Caught by controller[0]: at require (node:internal/modules/cjs/helpers:119:18)
                  2023-09-24 13:13:40.292 - error: host.All-In-One-RasPi Caught by controller[0]: at Object. (/opt/iobroker/node_modules/axios-cookiejar-support/lib/index.js:8:40) {
                  2023-09-24 13:13:40.294 - error: host.All-In-One-RasPi Caught by controller[0]: code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
                  2023-09-24 13:13:40.294 - error: host.All-In-One-RasPi Caught by controller[0]: }
                  2023-09-24 13:13:40.295 - error: host.All-In-One-RasPi Caught by controller[0]: Node.js v18.18.0
                  2023-09-24 13:13:40.296 - error: host.All-In-One-RasPi instance system.adapter.wmswebcontrol.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                  2023-09-24 13:13:40.297 - info: host.All-In-One-RasPi Restart adapter system.adapter.wmswebcontrol.0 because enabled
                  2023-09-24 13:14:11.025 - info: host.All-In-One-RasPi instance system.adapter.wmswebcontrol.0 started with pid 441667
                  2023-09-24 13:14:14.736 - error: host.All-In-One-RasPi Caught by controller[0]: node:internal/modules/cjs/loader:573
                  2023-09-24 13:14:14.737 - error: host.All-In-One-RasPi Caught by controller[0]: throw e;
                  2023-09-24 13:14:14.738 - error: host.All-In-One-RasPi Caught by controller[0]: ^
                  2023-09-24 13:14:14.739 - error: host.All-In-One-RasPi Caught by controller[0]: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/defaults' is not defined by "exports" in /opt/iobroker/node_modules/axios/package.json
                  2023-09-24 13:14:14.740 - error: host.All-In-One-RasPi Caught by controller[0]: at new NodeError (node:internal/errors:405:5)
                  2023-09-24 13:14:14.740 - error: host.All-In-One-RasPi Caught by controller[0]: at exportsNotFound (node:internal/modules/esm/resolve:362:10)
                  2023-09-24 13:14:14.741 - error: host.All-In-One-RasPi Caught by controller[0]: at packageExportsResolve (node:internal/modules/esm/resolve:698:9)
                  2023-09-24 13:14:14.742 - error: host.All-In-One-RasPi Caught by controller[0]: at resolveExports (node:internal/modules/cjs/loader:567:36)
                  2023-09-24 13:14:14.742 - error: host.All-In-One-RasPi Caught by controller[0]: at Module._findPath (node:internal/modules/cjs/loader:636:31)
                  2023-09-24 13:14:14.743 - error: host.All-In-One-RasPi Caught by controller[0]: at Module._resolveFilename (node:internal/modules/cjs/loader:1063:27)
                  2023-09-24 13:14:14.743 - error: host.All-In-One-RasPi Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:922:27)
                  2023-09-24 13:14:14.744 - error: host.All-In-One-RasPi Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19)
                  2023-09-24 13:14:14.744 - error: host.All-In-One-RasPi Caught by controller[0]: at require (node:internal/modules/cjs/helpers:119:18)
                  2023-09-24 13:14:14.745 - error: host.All-In-One-RasPi Caught by controller[0]: at Object. (/opt/iobroker/node_modules/axios-cookiejar-support/lib/index.js:8:40) {
                  2023-09-24 13:14:14.745 - error: host.All-In-One-RasPi Caught by controller[0]: code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
                  2023-09-24 13:14:14.746 - error: host.All-In-One-RasPi Caught by controller[0]: }
                  2023-09-24 13:14:14.746 - error: host.All-In-One-RasPi Caught by controller[0]: Node.js v18.18.0
                  2023-09-24 13:14:14.747 - error: host.All-In-One-RasPi instance system.adapter.wmswebcontrol.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                  2023-09-24 13:14:14.748 - info: host.All-In-One-RasPi Restart adapter system.adapter.wmswebcontrol.0 because enable
                  
                  B 1 Reply Last reply Reply Quote 0
                  • B
                    BlackTigga @BlackTigga last edited by

                    Gibt es sonst noch Ideen wie ich diesen Fehler beheben könnte?

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

                      @blacktigga

                      Du könntest im github mal anfragen.

                      https://github.com/TA2k/ioBroker.wmswebcontrol/issues

                      Ich könnte mir vorstellen, dass der Adapter einfach nach zwei Jahren etwas Liebe benötigt.

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        TT-Tom @Thomas Braun last edited by TT-Tom

                        @thomas-braun

                        die Fehlermeldung lässt drauf schliessen, das der Adapter eine Auffrischung benötigt

                        Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/defaults' is not defined by "exports" in /opt/iobroker/node_modules/axios/package.json
                        
                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @TT-Tom last edited by

                          @tt-tom

                          Ja, würde ich auch sagen.

                          1 Reply Last reply Reply Quote 0
                          • B
                            BlackTigga last edited by

                            @thomas-braun @TT-Tom

                            https://github.com/TA2k/ioBroker.wmswebcontrol/issues/8
                            Mit beta repo und update auf 0.0.6 ist der Fehler behoben.

                            Besten Dank !

                            BlackTigga created this issue in TA2k/ioBroker.wmswebcontrol

                            closed Malfunction since js-controller update to version 5.0.12 #8

                            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

                            627
                            Online

                            32.0k
                            Users

                            80.6k
                            Topics

                            1.3m
                            Posts

                            3
                            13
                            431
                            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