Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. [gelöst] js-controller 3.0.19 upgrade Fehler - Iobroker tot

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    16
    1
    352

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    4.8k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.3k

[gelöst] js-controller 3.0.19 upgrade Fehler - Iobroker tot

Scheduled Pinned Locked Moved ioBroker Allgemein
js-controller update
47 Posts 17 Posters 6.5k Views 12 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Jey CeeJ Jey Cee

    @smart-home. Liegt im iobroker verzeichnis unter logs

    Der Fehler muss durch einen Entwickler behoben werden. Sleber könnt ihr nur versuchen das pcket iobroker.objects-redis zu löschen und dann in version 3.3.2 zu installieren.
    Das sollten nur die unter euch machen die wissen was sie tun, daher keine Anleitung von mir.

    F Offline
    F Offline
    f0rd42
    wrote on last edited by
    #14

    @Jey-Cee

    Da die Installation nun ja sowieso tot ist, kann ja nicht mehr viel passieren.
    könntest du trotzdem eine "Anleitung" posten? Natürlich auf eigene Gefahr

    kann man eventuell wieder auf 3.0.18 zurück?

    M 1 Reply Last reply
    0
    • F f0rd42

      @Jey-Cee

      Da die Installation nun ja sowieso tot ist, kann ja nicht mehr viel passieren.
      könntest du trotzdem eine "Anleitung" posten? Natürlich auf eigene Gefahr

      kann man eventuell wieder auf 3.0.18 zurück?

      M Offline
      M Offline
      MarkusW27
      wrote on last edited by MarkusW27
      #15

      @f0rd42 Bzgl. "Zurück auf 3.0.18": Hab ich schon probiert - ändert nichts (zumindest bei mir)

      1 Reply Last reply
      0
      • F Offline
        F Offline
        funbert
        wrote on last edited by
        #16

        2020-04-28 10:52:00.793 - error: history.0 (19709) uncaught exception: allback is not defined
        2020-04-28 10:52:00.802 - error: history.0 (19709) ReferenceError: allback is not defined
        at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
        at process._tickCallback (internal/process/next_tick.js:68:7)
        2020-04-28 10:52:01.172 - info: host.athomepi4 instance system.adapter.mercedesme.0 started with pid 19728
        2020-04-28 10:52:01.181 - info: history.0 (19709) terminating
        2020-04-28 10:52:01.183 - info: history.0 (19709) Terminated (NO_ERROR): Without reason
        2020-04-28 10:52:01.709 - error: host.athomepi4 Caught by controller[0]: This error originated either by t
        hrowing inside of an async function without a catch block, or by rejecting a promise which was not handled with .ca
        tch(). The promise rejected with the reason:
        2020-04-28 10:52:01.710 - error: host.athomepi4 Caught by controller[0]: ReferenceError: allback is not de
        fined
        2020-04-28 10:52:01.710 - error: host.athomepi4 Caught by controller[0]: at _0x411ccb._applyViewFunc (
        /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
        2020-04-28 10:52:01.710 - error: host.athomepi4 Caught by controller[0]: at process._tickCallback (int
        ernal/process/next_tick.js:68:7)
        2020-04-28 10:52:01.710 - info: host.athomepi4 instance system.adapter.history.0 terminated with code 0 (N
        O_ERROR)
        2020-04-28 10:52:01.711 - info: host.athomepi4 Restart adapter system.adapter.history.0 because enabled

        1 Reply Last reply
        0
        • F Offline
          F Offline
          f0rd42
          wrote on last edited by
          #17

          Warum steht da im Fehler eigentlich immer "Allback' Anstalt "Callback"?

          AlCalzoneA 1 Reply Last reply
          0
          • F f0rd42

            Warum steht da im Fehler eigentlich immer "Allback' Anstalt "Callback"?

            AlCalzoneA Offline
            AlCalzoneA Offline
            AlCalzone
            Developer
            wrote on last edited by
            #18

            @f0rd42 Genau das ist das Problem :)

            Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

            F 1 Reply Last reply
            0
            • AlCalzoneA AlCalzone

              @f0rd42 Genau das ist das Problem :)

              F Offline
              F Offline
              f0rd42
              wrote on last edited by
              #19

              @AlCalzone Dann warten wir auf den Entwickler, sollte ja kein "grosses" Problem sein :-)

              1 Reply Last reply
              0
              • ? Offline
                ? Offline
                A Former User
                wrote on last edited by
                #20

                2020-04-28 10:17:27.955 - ^[[32minfo^[[39m: discovery.0 (519) starting. Version 2.3.3 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.16.3, js-controller: 3.0.19
                2020-04-28 10:17:29.936 - ^[[32minfo^[[39m: knx.0 (530) starting. Version 1.0.41 in /opt/iobroker/node_modules/iobroker.knx, node: v10.16.3, js-controller: 3.0.19
                2020-04-28 10:17:29.963 - ^[[33mwarn^[[39m: knx.0 (530) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
                2020-04-28 10:17:30.037 - ^[[31merror^[[39m: knx.0 (530) uncaught exception: allback is not defined
                2020-04-28 10:17:30.038 - ^[[31merror^[[39m: knx.0 (530) ReferenceError: allback is not defined
                at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                at process._tickCallback (internal/process/next_tick.js:68:7)

                hier mal ein ausschnitt aus meinem Log. Zumindestens steht da "Report this to Developer!":blush:

                1 Reply Last reply
                0
                • apollon77A Offline
                  apollon77A Offline
                  apollon77
                  wrote on last edited by
                  #21

                  Bitte kurz warten ... controller 3.0.20 baut gerade um das zu fixen ... melde mich sobald verfügbar

                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                  1 Reply Last reply
                  0
                  • SchuchtyS Offline
                    SchuchtyS Offline
                    Schuchty
                    wrote on last edited by
                    #22

                    Hallo zusammen,

                    da ich das oben beschriebene Problem alleine nicht lösen kann, habe ich mich hier im Forum angemeldet.
                    Ich hoffe es kann mir jemand helfen - die Hausautomation läuft leider nicht mehr.
                    Nach dem js-controller Upgrade startet das System nicht mehr.

                    Folgendes habe ich in der Konsole ausgeführt:

                    iobroker stop
                    iobroker update
                    iobroker upgrade self
                    iobroker start
                    

                    Der js-controller hat jetzt die neue Version.
                    iobroker info liefert folgendes Ergebnis:

                    (node:32704) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                        at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                        at process._tickCallback (internal/process/next_tick.js:68:7)
                    (node:32704) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
                    (node:32704) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                    

                    Environment:
                    Rpi4
                    node 10.17.0
                    mpm 6.14.4

                    Vielen Dank im Voraus.

                    LG Wolfgang

                    haselchenH sigi234S 2 Replies Last reply
                    0
                    • apollon77A Offline
                      apollon77A Offline
                      apollon77
                      wrote on last edited by
                      #23

                      3.0.20 ist auf npm und kommt jetzt bald ins latest. Imzweifel bitte IM ioBroker VERZEICHNIS !!!! per "npm install iobroker.js-controller@3.0.20" installieren

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      F 1 Reply Last reply
                      2
                      • SchuchtyS Schuchty

                        Hallo zusammen,

                        da ich das oben beschriebene Problem alleine nicht lösen kann, habe ich mich hier im Forum angemeldet.
                        Ich hoffe es kann mir jemand helfen - die Hausautomation läuft leider nicht mehr.
                        Nach dem js-controller Upgrade startet das System nicht mehr.

                        Folgendes habe ich in der Konsole ausgeführt:

                        iobroker stop
                        iobroker update
                        iobroker upgrade self
                        iobroker start
                        

                        Der js-controller hat jetzt die neue Version.
                        iobroker info liefert folgendes Ergebnis:

                        (node:32704) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                            at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                            at process._tickCallback (internal/process/next_tick.js:68:7)
                        (node:32704) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
                        (node:32704) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                        

                        Environment:
                        Rpi4
                        node 10.17.0
                        mpm 6.14.4

                        Vielen Dank im Voraus.

                        LG Wolfgang

                        haselchenH Offline
                        haselchenH Offline
                        haselchen
                        Most Active
                        wrote on last edited by
                        #24

                        @Schuchty

                        Guck mal hier

                        https://forum.iobroker.net/topic/32731/js-controller-upgrade-fehler-iobroker-tot

                        @Negalein
                        führe die Threads mal bitte zusammen :)
                        https://forum.iobroker.net/topic/32731/js-controller-upgrade-fehler-iobroker-tot

                        Synology DS218+ & 2 x Fujitsu Esprimo (VM/Container) + FritzBox7590 + 2 AVM 3000 Repeater & Homematic & HUE & Osram & Xiaomi, NPM 10.9.4, Nodejs 22.21.0 ,JS Controller 7.0.7 ,Admin 7.7.19

                        NegaleinN 1 Reply Last reply
                        0
                        • SchuchtyS Offline
                          SchuchtyS Offline
                          Schuchty
                          wrote on last edited by
                          #25

                          @haselchen Habe den Controller auf 3.0.20 upgedated, läuft.
                          Super, danke.
                          LG Wolfgang

                          1 Reply Last reply
                          0
                          • SchuchtyS Schuchty

                            Hallo zusammen,

                            da ich das oben beschriebene Problem alleine nicht lösen kann, habe ich mich hier im Forum angemeldet.
                            Ich hoffe es kann mir jemand helfen - die Hausautomation läuft leider nicht mehr.
                            Nach dem js-controller Upgrade startet das System nicht mehr.

                            Folgendes habe ich in der Konsole ausgeführt:

                            iobroker stop
                            iobroker update
                            iobroker upgrade self
                            iobroker start
                            

                            Der js-controller hat jetzt die neue Version.
                            iobroker info liefert folgendes Ergebnis:

                            (node:32704) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined
                                at _0x411ccb._applyViewFunc (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:115051)
                                at process._tickCallback (internal/process/next_tick.js:68:7)
                            (node:32704) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
                            (node:32704) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
                            

                            Environment:
                            Rpi4
                            node 10.17.0
                            mpm 6.14.4

                            Vielen Dank im Voraus.

                            LG Wolfgang

                            sigi234S Online
                            sigi234S Online
                            sigi234
                            Forum Testing Most Active
                            wrote on last edited by
                            #26

                            @Schuchty sagte in Problem nach js-controller Upgrade von 3.0.18 auf 3.0.19:

                            (node:32704) UnhandledPromiseRejectionWarning: ReferenceError: allback is not defined

                            allback

                            und genau da lag der Fehler. Es fehlte ein C :smirk:

                            Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                            Immer Daten sichern!

                            1 Reply Last reply
                            0
                            • C Offline
                              C Offline
                              ChristianS
                              wrote on last edited by
                              #27

                              @apollon77
                              Ich hatte das gleiche Problem und habe mitgelesen :-)
                              Nach "npm install iobroker.js-controller@3.0.20" funktioniert bei mir wieder alles.

                              Vielen Dank!

                              1 Reply Last reply
                              1
                              • ? Offline
                                ? Offline
                                A Former User
                                wrote on last edited by A Former User
                                #28

                                Bei mir funktioniert es leider nicht:

                                pi@ioBroker-RasPi4:/opt/iobroker $ npm install iobroker.js-controller@3.0.20
                                npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                npm WARN deprecated fsevents@1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
                                npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/chokidar/node_modules/fsevents
                                npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.loxone/node_modules/chokidar/node_modules/fsevents
                                npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/chokidar/node_modules/fsevents/node_modules
                                npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.loxone/node_modules/chokidar/node_modules/fsevents/node_modules
                                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/iobroker.js-controller/node_modules/chokidar/node_modules/fsevents):
                                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents):
                                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/iobroker.loxone/node_modules/chokidar/node_modules/fsevents):
                                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/fsevents/package.json'
                                npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.loxone/node_modules/fsevents/package.json'
                                npm WARN ws@7.2.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
                                npm WARN ws@7.2.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.

                                npm ERR! path /opt/iobroker/node_modules/chokidar/node_modules/fsevents
                                npm ERR! code EACCES
                                npm ERR! errno -13
                                npm ERR! syscall access
                                npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/chokidar/node_modules/fsevents'
                                npm ERR! { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/chokidar/node_modules/fsevents']
                                npm ERR! stack:
                                npm ERR! 'Error: EACCES: permission denied, access '/opt/iobroker/node_modules/chokidar/node_modules/fsevents'',
                                npm ERR! errno: -13,
                                npm ERR! code: 'EACCES',
                                npm ERR! syscall: 'access',
                                npm ERR! path: '/opt/iobroker/node_modules/chokidar/node_modules/fsevents' }
                                npm ERR!
                                npm ERR! The operation was rejected by your operating system.
                                npm ERR! It is likely you do not have the permissions to access this file as the current user
                                npm ERR!
                                npm ERR! If you believe this might be a permissions issue, please double-check the
                                npm ERR! permissions of the file and its containing directories, or try running
                                npm ERR! the command again as root/Administrator (though this is not recommended).

                                npm ERR! A complete log of this run can be found in:
                                npm ERR! /home/pi/.npm/_logs/2020-04-28T10_11_11_846Z-debug.log
                                pi@ioBroker-RasPi4:/opt/iobroker $

                                und jetzt hab ich glaube ich noch ein größeres Problem:

                                pi@ioBroker-RasPi4:/opt/iobroker $ sudo iobroker update
                                internal/modules/cjs/loader.js:638
                                throw err;
                                ^

                                Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iob roker.js'
                                at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
                                at Function.Module._load (internal/modules/cjs/loader.js:562:25)
                                at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
                                at startup (internal/bootstrap/node.js:283:19)
                                at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

                                arteckA 1 Reply Last reply
                                0
                                • ? A Former User

                                  Bei mir funktioniert es leider nicht:

                                  pi@ioBroker-RasPi4:/opt/iobroker $ npm install iobroker.js-controller@3.0.20
                                  npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                  npm WARN deprecated fsevents@1.2.12: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
                                  npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/chokidar/node_modules/fsevents
                                  npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.loxone/node_modules/chokidar/node_modules/fsevents
                                  npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/chokidar/node_modules/fsevents/node_modules
                                  npm WARN checkPermissions Missing write access to /opt/iobroker/node_modules/iobroker.loxone/node_modules/chokidar/node_modules/fsevents/node_modules
                                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/iobroker.js-controller/node_modules/chokidar/node_modules/fsevents):
                                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/chokidar/node_modules/fsevents):
                                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/iobroker.loxone/node_modules/chokidar/node_modules/fsevents):
                                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                  npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/fsevents/package.json'
                                  npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.loxone/node_modules/fsevents/package.json'
                                  npm WARN ws@7.2.1 requires a peer of bufferutil@^4.0.1 but none is installed. You must install peer dependencies yourself.
                                  npm WARN ws@7.2.1 requires a peer of utf-8-validate@^5.0.2 but none is installed. You must install peer dependencies yourself.

                                  npm ERR! path /opt/iobroker/node_modules/chokidar/node_modules/fsevents
                                  npm ERR! code EACCES
                                  npm ERR! errno -13
                                  npm ERR! syscall access
                                  npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/chokidar/node_modules/fsevents'
                                  npm ERR! { [Error: EACCES: permission denied, access '/opt/iobroker/node_modules/chokidar/node_modules/fsevents']
                                  npm ERR! stack:
                                  npm ERR! 'Error: EACCES: permission denied, access '/opt/iobroker/node_modules/chokidar/node_modules/fsevents'',
                                  npm ERR! errno: -13,
                                  npm ERR! code: 'EACCES',
                                  npm ERR! syscall: 'access',
                                  npm ERR! path: '/opt/iobroker/node_modules/chokidar/node_modules/fsevents' }
                                  npm ERR!
                                  npm ERR! The operation was rejected by your operating system.
                                  npm ERR! It is likely you do not have the permissions to access this file as the current user
                                  npm ERR!
                                  npm ERR! If you believe this might be a permissions issue, please double-check the
                                  npm ERR! permissions of the file and its containing directories, or try running
                                  npm ERR! the command again as root/Administrator (though this is not recommended).

                                  npm ERR! A complete log of this run can be found in:
                                  npm ERR! /home/pi/.npm/_logs/2020-04-28T10_11_11_846Z-debug.log
                                  pi@ioBroker-RasPi4:/opt/iobroker $

                                  und jetzt hab ich glaube ich noch ein größeres Problem:

                                  pi@ioBroker-RasPi4:/opt/iobroker $ sudo iobroker update
                                  internal/modules/cjs/loader.js:638
                                  throw err;
                                  ^

                                  Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iob roker.js'
                                  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
                                  at Function.Module._load (internal/modules/cjs/loader.js:562:25)
                                  at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
                                  at startup (internal/bootstrap/node.js:283:19)
                                  at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

                                  arteckA Offline
                                  arteckA Offline
                                  arteck
                                  Developer Most Active
                                  wrote on last edited by
                                  #29

                                  @smart-home lass den fixer drüber laufen dann nochma update

                                  zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                  ? 1 Reply Last reply
                                  0
                                  • arteckA arteck

                                    @smart-home lass den fixer drüber laufen dann nochma update

                                    ? Offline
                                    ? Offline
                                    A Former User
                                    wrote on last edited by
                                    #30

                                    @arteck

                                    pi@ioBroker-RasPi4:/opt/iobroker $ curl -sL https://iobroker.net/fix.sh | bash -
                                    library: loaded
                                    Library version=2020-04-12
                                    ioBroker is not installed in /opt/iobroker! Cannot fix anything...
                                    pi@ioBroker-RasPi4:/opt/iobroker $

                                    arteckA 1 Reply Last reply
                                    0
                                    • ? A Former User

                                      @arteck

                                      pi@ioBroker-RasPi4:/opt/iobroker $ curl -sL https://iobroker.net/fix.sh | bash -
                                      library: loaded
                                      Library version=2020-04-12
                                      ioBroker is not installed in /opt/iobroker! Cannot fix anything...
                                      pi@ioBroker-RasPi4:/opt/iobroker $

                                      arteckA Offline
                                      arteckA Offline
                                      arteck
                                      Developer Most Active
                                      wrote on last edited by
                                      #31

                                      @smart-home

                                      dann Brechstange

                                      sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller
                                      

                                      zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                      ? 1 Reply Last reply
                                      0
                                      • arteckA arteck

                                        @smart-home

                                        dann Brechstange

                                        sudo -H -u iobroker npm install ioBroker/ioBroker.js-controller
                                        
                                        ? Offline
                                        ? Offline
                                        A Former User
                                        wrote on last edited by
                                        #32

                                        @arteck in /opt/iobroker Verzeichnis oder ohne Verzeichnis?

                                        apollon77A 1 Reply Last reply
                                        0
                                        • ? A Former User

                                          @arteck in /opt/iobroker Verzeichnis oder ohne Verzeichnis?

                                          apollon77A Offline
                                          apollon77A Offline
                                          apollon77
                                          wrote on last edited by
                                          #33

                                          @smart-home Npm Befehle immer im ioBroekr Verzeicvhnis

                                          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

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

                                          298

                                          Online

                                          32.7k

                                          Users

                                          82.5k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe