Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 4.0.x jetzt für alle User im STABLE!

    NEWS

    • [erledigt] 15. 05. Wartungsarbeiten am ioBroker Forum

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 4.0.x jetzt für alle User im STABLE!

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

      @haselchen

      Guckstu:

      https://github.com/DrozmotiX/ioBroker.coronavirus-statistics/issues/347

      Draexl created this issue in DrozmotiX/ioBroker.coronavirus-statistics

      closed Wrong Object type #347

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

        @thomas-braun

        Aaah, okay. Also grase ich die Issues ab und packe wenn, meine Logs dazu oder mache ein Neues auf?

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

          @haselchen

          Würde ich machen. Nur so sieht der entsprechende Maintainer die Dinge.

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

            @thomas-braun

            Was, wenn der Yeelight Entwickler nicht mehr aktiv ist, wer aus dem Team muss benachrichtig werden?

            apollon77 1 Reply Last reply Reply Quote 0
            • apollon77
              apollon77 @haselchen last edited by

              @haselchen Wer ist das denn?

              haselchen 1 Reply Last reply Reply Quote 0
              • haselchen
                haselchen Most Active @apollon77 last edited by haselchen

                @apollon77

                Wenn ich das richtig interpretiere sind es 11 Mitwirkende.
                Und das letzte Update ist von August 21.

                Edit: Gerade gesehen , Du gehörst auch dazu 🙂

                Thomas Braun apollon77 2 Replies Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @haselchen last edited by Thomas Braun

                  Hier stand Quatsch.

                  1 Reply Last reply Reply Quote 0
                  • apollon77
                    apollon77 @haselchen last edited by

                    @haselchen Naja leg ein isue an.

                    haselchen 1 Reply Last reply Reply Quote 0
                    • haselchen
                      haselchen Most Active @apollon77 last edited by haselchen

                      @apollon77

                      Gibt es seit September 2021 😉

                      https://github.com/iobroker-community-adapters/ioBroker.yeelight-2/issues/124

                      Pittini created this issue in iobroker-community-adapters/ioBroker.yeelight-2

                      closed Warnings "...has no existing object, this might lead to an error in future versions" since JS Controller 3.3 update #124

                      1 Reply Last reply Reply Quote 1
                      • crunchip
                        crunchip Forum Testing Most Active last edited by

                        da ich gerade ein bisschen aufräumen wollte und ein paar Adapter gelöscht habe, hätte ich eine Frage zu folgender Error Meldung
                        Was bedeutet dies?

                        2022-03-20 08:34:49.694 - error: host.IoBroker cannot process: system.adapter.icons-material-svg.0: TypeError: Cannot read property 'type' of null / TypeError: Cannot read property 'type' of null
                        at change (/opt/iobroker/node_modules/iobroker.js-controller/main.js:772:32)
                        at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:391:41)
                        at processImmediate (internal/timers.js:464:21)
                        
                        2022-03-20 08:35:09.208 - info: admin.0 (924986) Request actual repository...
                        2022-03-20 08:35:24.166 - info: admin.0 (924986) Repository received successfully.
                        2022-03-20 08:39:05.948 - error: host.IoBroker cannot process: system.adapter.icons-mfd-svg.0: TypeError: Cannot read property 'type' of null / TypeError: Cannot read property 'type' of null
                        at change (/opt/iobroker/node_modules/iobroker.js-controller/main.js:772:32)
                        at Immediate._onImmediate (/opt/iobroker/node_modules/@iobroker/db-objects-redis/lib/objects/objectsInRedisClient.js:391:41)
                        at processImmediate (internal/timers.js:464:21)
                        
                        apollon77 1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 @crunchip last edited by

                          @crunchip das du vllt nen Bug gefunden hast. GitHub issue bitte

                          H 1 Reply Last reply Reply Quote 1
                          • H
                            hardy_01 @apollon77 last edited by hardy_01

                            Bei mir hat sich beim Update irgendwas aufgehangen. Seit dem ist der broker nicht mehr erreichbar

                            pi@raspberrypi-iob:~ $ iobroker upgrade self
                            Update js-controller from @3.1.6 to @4.0.21
                            NPM version: 6.14.16
                            npm install iobroker.js-controller@4.0.21 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                            In file included from ../../nan/nan.h:56,
                                             from ../src/unix_dgram.cc:5:
                            /home/iobroker/.cache/node-gyp/14.19.1/include/node/node.h:793:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                   (node::addon_register_func) (regfunc),                          \
                                                                       ^
                            /home/iobroker/.cache/node-gyp/14.19.1/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
                               NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                               ^~~~~~~~~~~~~
                            ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                             NODE_MODULE(unix_dgram, Initialize)
                             ^~~~~~~~~~~
                             Objects 127.0.0.1:53902 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                             States 127.0.0.1:38688 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                             Objects 127.0.0.1:53902 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                             Objects 127.0.0.1:53902 Error from InMemDB: Error: scan NOT SUPPORTED
                            /opt/iobroker/node_modules/standard-as-callback/built/index.js:6
                                    throw e;
                                    ^
                            
                            ReplyError: Error scan NOT SUPPORTED
                                at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                                at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                            Emitted 'error' event on ScanStream instance at:
                                at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
                                at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
                                at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
                                at processTicksAndRejections (internal/process/task_queues.js:95:5) {
                              command: {
                                name: 'scan',
                                args: [ '0', 'MATCH', 'cfg.o.system.host.*', 'COUNT', '250' ]
                              }
                            }
                            npm ERR! code ELIFECYCLE
                            npm ERR! errno 1
                            npm ERR! iobroker.js-controller@4.0.21 install: `node iobroker.js setup first`
                            npm ERR! Exit status 1
                            npm ERR! 
                            npm ERR! Failed at the iobroker.js-controller@4.0.21 install script.
                            npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                            
                            npm ERR! A complete log of this run can be found in:
                            npm ERR!     /home/iobroker/.npm/_logs/2022-03-29T16_38_52_007Z-debug.log
                            host.raspberrypi-iob Cannot install iobroker.js-controller@4.0.21: 1
                            

                            iobroker update bringt

                            pi@raspberrypi-iob:/opt/iobroker $ iobroker update
                            internal/modules/cjs/loader.js:905
                              throw err;
                              ^
                            
                            Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                                at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
                                at Function.Module._load (internal/modules/cjs/loader.js:746:27)
                                at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
                                at internal/main/run_main_module.js:17:47 {
                              code: 'MODULE_NOT_FOUND',
                              requireStack: []
                            }
                            

                            Jemand eine Idee wo ich ansetzen kann?

                            H apollon77 2 Replies Last reply Reply Quote 0
                            • H
                              hardy_01 @hardy_01 last edited by

                              @hardy_01 said in js-controller 4.0.x jetzt für alle User im STABLE!:

                              Bei mir hat sich beim Update irgendwas aufgehangen. Seit dem ist der broker nicht mehr erreichbar

                              pi@raspberrypi-iob:~ $ iobroker upgrade self
                              Update js-controller from @3.1.6 to @4.0.21
                              NPM version: 6.14.16
                              npm install iobroker.js-controller@4.0.21 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                              In file included from ../../nan/nan.h:56,
                                               from ../src/unix_dgram.cc:5:
                              /home/iobroker/.cache/node-gyp/14.19.1/include/node/node.h:793:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                     (node::addon_register_func) (regfunc),                          \
                                                                         ^
                              /home/iobroker/.cache/node-gyp/14.19.1/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
                                 NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                 ^~~~~~~~~~~~~
                              ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                               NODE_MODULE(unix_dgram, Initialize)
                               ^~~~~~~~~~~
                               Objects 127.0.0.1:53902 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                               States 127.0.0.1:38688 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                               Objects 127.0.0.1:53902 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                               Objects 127.0.0.1:53902 Error from InMemDB: Error: scan NOT SUPPORTED
                              /opt/iobroker/node_modules/standard-as-callback/built/index.js:6
                                      throw e;
                                      ^
                              
                              ReplyError: Error scan NOT SUPPORTED
                                  at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                                  at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                              Emitted 'error' event on ScanStream instance at:
                                  at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
                                  at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
                                  at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
                                  at processTicksAndRejections (internal/process/task_queues.js:95:5) {
                                command: {
                                  name: 'scan',
                                  args: [ '0', 'MATCH', 'cfg.o.system.host.*', 'COUNT', '250' ]
                                }
                              }
                              npm ERR! code ELIFECYCLE
                              npm ERR! errno 1
                              npm ERR! iobroker.js-controller@4.0.21 install: `node iobroker.js setup first`
                              npm ERR! Exit status 1
                              npm ERR! 
                              npm ERR! Failed at the iobroker.js-controller@4.0.21 install script.
                              npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                              
                              npm ERR! A complete log of this run can be found in:
                              npm ERR!     /home/iobroker/.npm/_logs/2022-03-29T16_38_52_007Z-debug.log
                              host.raspberrypi-iob Cannot install iobroker.js-controller@4.0.21: 1
                              

                              iobroker update bringt

                              pi@raspberrypi-iob:/opt/iobroker $ iobroker update
                              internal/modules/cjs/loader.js:905
                                throw err;
                                ^
                              
                              Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                                  at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
                                  at Function.Module._load (internal/modules/cjs/loader.js:746:27)
                                  at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12)
                                  at internal/main/run_main_module.js:17:47 {
                                code: 'MODULE_NOT_FOUND',
                                requireStack: []
                              }
                              
                              pi@raspberrypi-iob:/opt/iobroker $ iobroker start
                              pi@raspberrypi-iob:/opt/iobroker $ iobroker fix
                              library: loaded
                              Library version=2022-02-10
                              ioBroker is not installed in /opt/iobroker! Cannot fix anything...
                              

                              Jemand eine Idee wo ich ansetzen kann?

                              crunchip 1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @hardy_01 last edited by

                                @hardy_01

                                Falls es auch danach noch Fehler gibt, bitte die Installation erneut mittels sudo -H -u iobroker npm install iobroker.js-controller versuchen. 
                                
                                1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 @hardy_01 last edited by

                                  @hardy_01 naja Du kommst von der 3.1 ... Da steht oben das Du idealerweise zuerst die 3.2 installieren solltest bzw ja bei DIr wäre der direkte weg via npm der sinnvolle. Siehe letzter Post

                                  H 1 Reply Last reply Reply Quote 0
                                  • H
                                    hardy_01 @apollon77 last edited by

                                    @apollon77
                                    Habe ich probiert, bekomme leider immer noch einen Fehler (Berechtigung).

                                    pi@raspberrypi-iob:~ $ sudo -H -u iobroker npm install iobroker.js-controller
                                    npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                    npm WARN deprecated har-validator@5.1.5: this library is no longer supported
                                    npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
                                    npm WARN checkPermissions Missing write access to /home/pi
                                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
                                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                    npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'
                                    npm WARN pi No description
                                    npm WARN pi No repository field.
                                    npm WARN pi No README data
                                    npm WARN pi No license field.
                                    
                                    npm ERR! code EACCES
                                    npm ERR! syscall access
                                    npm ERR! path /home/pi
                                    npm ERR! errno -13
                                    npm ERR! Error: EACCES: permission denied, access '/home/pi'
                                    npm ERR!  [Error: EACCES: permission denied, access '/home/pi'] {
                                    npm ERR!   errno: -13,
                                    npm ERR!   code: 'EACCES',
                                    npm ERR!   syscall: 'access',
                                    npm ERR!   path: '/home/pi'
                                    npm ERR! }
                                    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.
                                    
                                    npm ERR! A complete log of this run can be found in:
                                    npm ERR!     /home/iobroker/.npm/_logs/2022-03-29T20_06_59_453Z-debug.log
                                    
                                    mikeal created this issue in request/request

                                    open Request’s Past, Present and Future #3142

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

                                      @hardy_01
                                      Du stehst im falschen Verzeichnis...

                                      cd /opt/iobroker
                                      

                                      Und dann die direkte Installation wie schon versucht.

                                      H 1 Reply Last reply Reply Quote 1
                                      • H
                                        hardy_01 @Thomas Braun last edited by

                                        @thomas-braun
                                        Herzlichen Dank an alle, hat funktioniert 😊

                                        1 Reply Last reply Reply Quote 1
                                        • J
                                          Jack01 last edited by Jack01

                                          Moin,
                                          heute habe ich mal allen Mut gefasst und auf die aktuelle Version upgedatet.
                                          Es sieht so aus, als ob alles funktioniert hat.
                                          Es allerdings ein paar Meldungen, die von dem Beispiel im ersten Thread abweichen

                                          pi@raspberrypi:/opt/iobroker $ iobroker upgrade self
                                          Update js-controller from @3.3.22 to @4.0.21
                                          NPM version: 6.14.16
                                          npm install iobroker.js-controller@4.0.21 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                                          In file included from ../src/unix_dgram.cc:5:
                                          ../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
                                          ../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                                               , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                                                        ^
                                          In file included from ../../nan/nan.h:56,
                                                           from ../src/unix_dgram.cc:5:
                                          ../src/unix_dgram.cc: At global scope:
                                          /home/iobroker/.cache/node-gyp/14.19.1/include/node/node.h:793:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                                 (node::addon_register_func) (regfunc),                          \
                                                                                     ^
                                          /home/iobroker/.cache/node-gyp/14.19.1/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
                                             NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                                             ^~~~~~~~~~~~~
                                          ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                                           NODE_MODULE(unix_dgram, Initialize)
                                           ^~~~~~~~~~~
                                          Server Objects 127.0.0.1:41112 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                                          Server Objects 127.0.0.1:41112 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                                          Server Objects 127.0.0.1:41112 Error from InMemDB: Error: Unknown LUA script load
                                          Server Objects 127.0.0.1:41112 Error from InMemDB: Error: Unknown LUA script load
                                          Server Objects 127.0.0.1:41112 Error from InMemDB: Error: Unknown LUA script load
                                          Server Objects 127.0.0.1:41112 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                          Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                                          pi@raspberrypi:/opt/iobroker $
                                          
                                          

                                          Muss ich hier noch etwas unternehmen oder ist das so OK?

                                          Gruß

                                          Hans-Jürgen

                                          Nachtrag:
                                          meine Datenbanken sehen jetzt so aus:

                                          
                                          pi@raspberrypi:/opt/iobroker $ iob status
                                          iobroker is running on this host.
                                          
                                          
                                          Objects type: jsonl
                                          States  type: redis
                                          pi@raspberrypi:/opt/iobroker $
                                          
                                          
                                          Thomas Braun 1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @Jack01 last edited by

                                            @jack01

                                            Schaut okay aus.

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

                                            Support us

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

                                            426
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            83
                                            501
                                            109168
                                            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