Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 3.0/3.1 jetzt im Latest!

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 3.0/3.1 jetzt im Latest!

    This topic has been deleted. Only users with topic management privileges can see it.
    • foxriver76
      foxriver76 Developer @dirk1962 last edited by

      @dirk1962 Jop, Problem ist bereits identifiziert und Fix steht bereit

      K dslraser 2 Replies Last reply Reply Quote 0
      • K
        Kueppert @foxriver76 last edited by

        @foxriver76 lol, einmal nicht direkt auf die neue Version gesprungen und Glück gehabt ^^ die neue Neue nehme ich dann direkt wieder mit zum Testen

        J 1 Reply Last reply Reply Quote 0
        • dslraser
          dslraser Forum Testing Most Active @foxriver76 last edited by

          @foxriver76 sagte in js-controller 3.0 jetzt im Latest!:

          Jop, Problem ist bereits identifiziert und Fix steht bereit

          neue Version ? 3.0.16 oder wie installieren ?

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

            @Kueppert
            Ich hab sie nur genommen, weil ich damit ein anderes Problem ausschließen wollte, danach hatte ich ein s mehr 🙂
            @foxriver76 sagte in js-controller 3.0 jetzt im Latest!:

            Fix steht bereit

            und wie bekomme ich das drauf, wenn die Kommandos aus dem Beta Thread hier nicht funktionieren?

            1 Reply Last reply Reply Quote 0
            • foxriver76
              foxriver76 Developer @dslraser last edited by

              @dslraser Ne, noch warten @apollon77 wird eine neue Version machen, evtl ergibt sich im Laufe des Tages noch etwas, was mit rein kommt.

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

                @foxriver76
                OK, wir warten, ist ja nicht so dramatisch.

                1 Reply Last reply Reply Quote 0
                • foxriver76
                  foxriver76 Developer @dslraser last edited by

                  @dslraser sagte in js-controller 3.0 jetzt im Latest!:

                  @Jan1
                  aber was soll @version in Deinem Befehl, oder hast Du das da rein geschrieben ?

                  root@Beelink:/opt/iobroker# npm install iobroker.js-controller@version
                  

                  version muss allerdings durch die Zielversion ersetzt werden.

                  dslraser 1 Reply Last reply Reply Quote 1
                  • dslraser
                    dslraser Forum Testing Most Active @foxriver76 last edited by dslraser

                    @foxriver76
                    ja, das ist mir bewußt, deshalb habe ich @Jan1 danach gefragt, weil das von Ihm aus einem Beitrag ist.

                    1 Reply Last reply Reply Quote 0
                    • I
                      ITCrowd last edited by apollon77

                      Update auf 3.0.14 problemlos. Aber dann:

                      Adapter Innogy Smarthome: Im Intervall mehrere Seiten.

                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at process._tickCallback (internal/process/next_tick.js:68:7)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)]
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at (anonymous function).(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:92586)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at adapterObjects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2787:21)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at /opt/iobroker/node_modules/iobroker.innogy-smarthome/main.js:286:36
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Capability.setState (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/smarthome/objects/capability.js:117:12)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at new Promise (/opt/iobroker/node_modules/bluebird/js/release/promise.js:103:10)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Promise._resolveFromExecutor (/opt/iobroker/node_modules/bluebird/js/release/promise.js:518:18)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Promise.cancellationExecute [as _execute] (/opt/iobroker/node_modules/bluebird/js/release/debuggability.js:406:9)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at /opt/iobroker/node_modules/innogy-smarthome-lib/lib/smarthome/objects/capability.js:157:29
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Requestor.call (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/requestor/index.js:48:17)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Requestor.doRequest (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/requestor/index.js:54:12)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at new Promise (/opt/iobroker/node_modules/bluebird/js/release/promise.js:103:10)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Promise._resolveFromExecutor (/opt/iobroker/node_modules/bluebird/js/release/promise.js:518:18)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Promise.cancellationExecute [as _execute] (/opt/iobroker/node_modules/bluebird/js/release/debuggability.js:406:9)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at /opt/iobroker/node_modules/innogy-smarthome-lib/lib/requestor/index.js:56:22
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Object.getAuthorizationStatus (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/oauth2/index.js:300:20)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at getAuthorizationStatus (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/oauth2/index.js:278:21)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at /opt/iobroker/node_modules/innogy-smarthome-lib/lib/requestor/index.js:67:22
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at Requestor.$doRequest (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/requestor/index.js:145:10)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	at AsyncLock.acquire (/opt/iobroker/node_modules/async-lock/lib/index.js:148:15)
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	(4800) Error: Too much pending tasks
                      innogy-smarthome.0	2020-04-22 12:25:15.254	error	(4800) uncaught exception: Too much pending tasks
                                      debug	at process._tickCallback (internal/process/next_tick.js:68:7)
                      		debug	at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
                      		debug	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
                      		debug	at (anonymous function).(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:92586)
                      		debug	at adapterObjects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2787:21)
                      		debug	at /opt/iobroker/node_modules/iobroker.innogy-smarthome/main.js:286:36
                      		debug	at Capability.setState (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/smarthome/objects/capability.js:117:12)
                      		debug	at new Promise (/opt/iobroker/node_modules/bluebird/js/release/promise.js:103:10)
                      		debug	at Promise._resolveFromExecutor (/opt/iobroker/node_modules/bluebird/js/release/promise.js:518:18)
                      		debug	at Promise.cancellationExecute [as _execute] (/opt/iobroker/node_modules/bluebird/js/release/debuggability.js:406:9)
                      		debug	at /opt/iobroker/node_modules/innogy-smarthome-lib/lib/smarthome/objects/capability.js:157:29
                      		debug	at Requestor.call (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/requestor/index.js:48:17)
                      		debug	at Requestor.doRequest (/opt/iobroker/node_modules/innogy-smarthome-lib/lib/requestor/index.js:54:12)
                      		debug	at new Promise (/opt/iobroker/node_modules/bluebird/js/release/promise.js:103:10)
                      

                      oder

                      innogy-smarthome.0	2020-04-22 12:30:27.506	error	at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
                      innogy-smarthome.0	2020-04-22 12:30:27.506	error	(4931) Error: read ECONNRESET
                      innogy-smarthome.0	2020-04-22 12:30:27.506	error	(4931) uncaught exception: read ECONNRESET
                      innogy-smarthome.0	2020-04-22 12:30:27.506	info	(4931) Terminated (NO_ERROR): Without reason
                      innogy-smarthome.0	2020-04-22 12:30:27.505	info	(4931) terminating
                      innogy-smarthome.0	2020-04-22 12:30:27.461	error	at TLSWrap.onStreamRead (internal/stream_base_commons.js:111:27)
                      innogy-smarthome.0	2020-04-22 12:30:27.461	error	(4931) Error: read ECONNRESET
                      innogy-smarthome.0	2020-04-22 12:30:27.460	error	(4931) uncaught exception: read ECONNRESET]
                      

                      KM200:

                      km200.0	2020-04-22 12:35:19.701	warn	(4977) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer
                      
                      foxriver76 1 Reply Last reply Reply Quote 0
                      • foxriver76
                        foxriver76 Developer @ITCrowd last edited by

                        @ITCrowd Issues beim jeweiligen Adapter anlegen bitte.

                        1 Reply Last reply Reply Quote 0
                        • K
                          Kugelkopf @jf62 last edited by

                          @jf62 Bei mir hat nach den bereits vorgeschlagenen Sachen ein upload funktioniert.

                          1 Reply Last reply Reply Quote 0
                          • F
                            Flugschüler @apollon77 last edited by

                            @apollon77 said in js-controller 3.0 jetzt im Latest!:

                            .catch(err => { //Fehlerhandling})

                            Also mein Script sieht jetzt so aus.

                            node_ssh = require('node-ssh');
                            ssh = new node_ssh();
                            ssh.connect({
                            host: '192.168.1.140',
                            username: 'pi',
                            password: '********'
                            }).then(() => {
                            ssh.execCommand("sudo shutdown -h now");
                            })

                            Wo muß ich das dann .catch(err => { //Fehlerhandling}) einfügen bzw. wie sieht das ganze Script dann aus.
                            Kannst du mir bitte helfen, ich kenne mich beim Scripte schreiben null aus.

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

                              @Jan1 sagte in js-controller 3.0 jetzt im Latest!:

                              War wohl "nur" der IoT Skill, aber dadurch bemerkt, dass der iQontrol den Web Adapter killt

                              ??

                              1 Reply Last reply Reply Quote 1
                              • apollon77
                                apollon77 @Kibbles last edited by

                                @Kibbles Bitte alexa 2 issue anlegen. Interessanter Fehler

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

                                  @Kibbles PS: nodejs 14 ... ooooookkkkkk jemand ganz experimentierfreudig 🙂 Gratuliere hast einen Adapter-Breaks-mit-nodejs-14" Bug gefunden

                                  1 Reply Last reply Reply Quote 0
                                  • F
                                    Flugschüler @Flugschüler last edited by

                                    @Flugschüler Ich glaube ich habs, stimmt das so?

                                    node_ssh = require('node-ssh');
                                    ssh = new node_ssh();
                                    ssh.connect({
                                    host: '192.168.1.140',
                                    username: 'pi',
                                    password: '********'
                                    }).then(() => {
                                    ssh.execCommand("sudo shutdown -h now");
                                    }).catch(err => { //Fehlerhandling})
                                    })

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

                                      @dslraser Rebuild nur mit Adaptername!

                                      "Iobroker rebuild iot" und wenn das nicht holgt "iobroker rebuild iot --install" ... steht doch alles im ersten Thread 😉

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

                                        @Jan1 Ja, Fehler identifiziert, Fix kommt zeitnah als 3.0.16

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

                                          @LJSven Siehe erster Post ganz oben

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

                                            @LJSven Wir prüfen

                                            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

                                            881
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            127
                                            1340
                                            397573
                                            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