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 goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    js-controller 3.0/3.1 jetzt im Latest!

    This topic has been deleted. Only users with topic management privileges can see it.
    • sigi234
      sigi234 Forum Testing Most Active @apollon77 last edited by

      @apollon77

      Läuft, alle Adapter Grün, vorläufig keine Meldungen im Log.

      Screenshot (2433).png

      1 Reply Last reply Reply Quote 1
      • Holger76
        Holger76 last edited by Holger76

        bei mir leider nicht. Es streikt der Unifi - Adapter, bleibt gelb (0.5, aber auch ein downgrade auf den vorigen läuft nicht) Meldung im LOG :

        (3030) Error: api.err.Invalid

        Ansonsten streikt auch der Discovergy Adapter, bleibt rot. (Login-Daten stimmen, nochmal kontrolliert, ging ja vorher auch)

        LOG:

        2020-05-10 00:02:01.030 - info: discovergy.0 (3267) starting. Version 0.5.4 in /opt/iobroker/node_modules/iobroker.discovergy, node: v12.16.3, js-controller: 3.1.2
2020-05-10 00:02:01.044 - info: discovergy.0 (3267) Discovergy Adapter startet, trying to discover meters associated with your account
2020-05-10 00:02:01.209 - error: discovergy.0 (3267) Connection_Failed at meter indication run, check your credentials !
2020-05-10 00:02:01.211 - error: 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().
2020-05-10 00:02:01.211 - error: discovergy.0 (3267) unhandled promise rejection: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.214 - error: discovergy.0 (3267) StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
at Request.emit (events.js:310:20)
at Request.EventEmitter.emit (domain.js:482:12)
at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.214 - info: discovergy.0 (3267) cleaned everything up...
2020-05-10 00:02:01.266 - info: discovergy.0 (3267) terminating
2020-05-10 00:02:01.267 - info: discovergy.0 (3267) Terminated (NO_ERROR): Without reason
2020-05-10 00:02:01.789 - error: host.ioBroker Caught by controller[0]: 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(). The promise rejected with the reason:
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: StatusCodeError: 401 - "401 Unauthorized: Invalid email or password supplied in the HTTP Authorization header"
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at new StatusCodeError (/opt/iobroker/node_modules/request-promise-core/lib/errors.js:32:15)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.plumbing.callback (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:104:33)
2020-05-10 00:02:01.790 - error: host.ioBroker Caught by controller[1]: at Request.RP$callback [as _callback] (/opt/iobroker/node_modules/request-promise-core/lib/plumbing.js:46:31)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request. (/opt/iobroker/node_modules/request/request.js:1154:10)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.emit (events.js:310:20)
2020-05-10 00:02:01.791 - error: host.ioBroker Caught by controller[1]: at Request.EventEmitter.emit (domain.js:482:12)
2020-05-10 00:02:01.792 - error: host.ioBroker Caught by controller[1]: at IncomingMessage. (/opt/iobroker/node_modules/request/request.js:1076:12)
2020-05-10 00:02:01.792 - info: host.ioBroker instance system.adapter.discovergy.0 terminated with code 0 (NO_ERROR)
2020-05-10 00:02:01.792 - info: host.ioBroker Restart adapter system.adapter.discovergy.0 because enabled

        Alle Adapter sind latest.
        Debian 10, NodeJS12

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

          @Holger76 dann bitte die Fehler bei beiden Adaptern melden, haben beide nichts direkt mit dem Controller zu tun. Am besten in den einschlägigen Forum Threads bzw als GitHub-Issue

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

            @Holger76 Versuch mal im Admin die Passwörter neu zu einzugeben bei den beiden Adaptern.

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

              @apollon77 hatte ich natürlich schon getestet, bevor ich sowas hier melde 😉

              ok ich meld mich bei den Adaptern direkt...

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

                @Holger76 Ich habe gerade die 3.1.3 released die deine Probleme beheben sollte. Habe mich entschieden nach Check das ganze im js-controller zu fixen. Es lag daran das die Passwörter falsch entschlüsselt wurden. Bitte checke mal die 3.1.3 sobald Sie für dich da ist

                S Holger76 2 Replies Last reply Reply Quote 0
                • M
                  Marty56 last edited by

                  Version 3.1.3. zeigt bei mir keine Fehler. Super Arbeit!

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

                    @apollon77
                    Moin,
                    ich habe jetzt gerade das Gefühl, dass der Sonos Adapter das JS-Controller Update nicht vertragen hat.
                    Fehler im Log kamen direkt nach dem Update auf 3.13

                    Ist aber für mich kein Problem, entsorge den jetzt sowieso, sollte nur als Info für Dich sein.

                    sonos.0	2020-05-10 06:20:01.791	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:20:01.791	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:20:01.791	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:20:01.791	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:20:01.791	error	(30381) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:20:01.790	error	(30381) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:20:01.771	error	(30381) unknown user "undefined"
                    MichMein apollon77 3 Replies Last reply Reply Quote 0
                    • MichMein
                      MichMein @skokarl last edited by MichMein

                      Hi,

                      Ich habe anscheinend das gleiche Problem wie @skokarl mit dem Sonos Adapter 😞 nach Update auf 3.1.3

                      
host.raspberrypi	2020-05-10 06:50:57.059	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:50:57.058	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:50:56.855	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.854	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.831	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:56.401	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.400	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.357	info	(16270) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:50:56.356	info	(16270) terminating
sonos.0	2020-05-10 06:50:56.350	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:56.275	info	(16270) terminating
sonos.0	2020-05-10 06:50:56.272	error	(16270) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:56.269	error	(16270) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:56.256	error	(16270) unknown user "undefined"
sonos.0	2020-05-10 06:50:55.620	info	(16270) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v12.16.3, js-controller: 3.1.3
host.raspberrypi	2020-05-10 06:50:54.368	info	instance system.adapter.sonos.0 started with pid 16270
host.raspberrypi	2020-05-10 06:50:24.346	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:50:24.345	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:50:23.819	info	(15535) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:50:23.817	info	(15535) terminating
sonos.0	2020-05-10 06:50:23.777	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.776	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.775	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.775	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.744	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:23.726	info	(15535) terminating
sonos.0	2020-05-10 06:50:23.723	error	(15535) TypeError: Cannot read property 'state' of undefined at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68) at /opt/iobroker/node_modules/iobroker.js-
sonos.0	2020-05-10 06:50:23.720	error	(15535) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:50:23.717	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:23.683	error	(15535) unknown user "undefined"
sonos.0	2020-05-10 06:50:22.987	info	(15535) starting. Version 2.0.1 in /opt/iobroker/node_modules/iobroker.sonos, node: v12.16.3, js-controller: 3.1.3
host.raspberrypi	2020-05-10 06:50:21.520	info	instance system.adapter.sonos.0 started with pid 15535
host.raspberrypi	2020-05-10 06:49:51.453	info	Restart adapter system.adapter.sonos.0 because enabled
host.raspberrypi	2020-05-10 06:49:51.452	info	instance system.adapter.sonos.0 terminated with code 0 (NO_ERROR)
sonos.0	2020-05-10 06:49:51.251	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:51.251	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:51.251	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:51.251	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:51.251	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:51.250	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:51.228	error	(14829) unknown user "undefined"
sonos.0	2020-05-10 06:49:50.987	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:50.987	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:50.987	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:50.987	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:50.987	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.986	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.936	info	(14829) Terminated (NO_ERROR): Without reason
sonos.0	2020-05-10 06:49:50.935	info	(14829) terminating
sonos.0	2020-05-10 06:49:50.924	error	(14829) unknown user "undefined"
sonos.0	2020-05-10 06:49:50.858	info	(14829) terminating
sonos.0	2020-05-10 06:49:50.856	error	at processTicksAndRejections (internal/process/task_queues.js:97:5)
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49
sonos.0	2020-05-10 06:49:50.856	error	at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/iobroker.objects-redis/index.js:1:93234
sonos.0	2020-05-10 06:49:50.856	error	at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5012:26
sonos.0	2020-05-10 06:49:50.856	error	at checkState (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4904:68)
sonos.0	2020-05-10 06:49:50.856	error	(14829) TypeError: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.852	error	(14829) uncaught exception: Cannot read property 'state' of undefined
sonos.0	2020-05-10 06:49:50.839	error	(14829) unknown user "undefined"

                      EDIT: Das kam nach dem abschalten des Adapters dazu,

                      host.raspberrypi	2020-05-10 06:51:28.854	info	Do not restart adapter system.adapter.sonos.0 because disabled or deleted
host.raspberrypi	2020-05-10 06:51:28.853	error	instance system.adapter.sonos.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
sonos.0	2020-05-10 06:51:28.315	warn	(16988) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
sonos.0	2020-05-10 06:51:28.303	error	(16988) adapter disabled
host.raspberrypi	2020-05-10 06:51:12.560	info	"system.adapter.sonos.0" disabled
                      S 1 Reply Last reply Reply Quote 0
                      • S
                        skokarl @MichMein last edited by

                        @MichMein

                        mach ihn weg..... der geht sowieso schon lange nicht mehr richtig.

                        oder stell nen Issue auf Github ein.

                        Alternative

                        MichMein 1 Reply Last reply Reply Quote 0
                        • MichMein
                          MichMein @skokarl last edited by

                          @skokarl du bist ja ne Marke. Lässt mich nen riesigen Thread lesen und kurz vor Schluss kommt dann das 😂

                          @skokarl sagte in Sonos-HTTP-API Installation für Newbies, Dummies und mich:

                          ACHTUNG DAS UPDATE SONOS S2 MACHT DIE API EVTL. UNBRAUCHBAR

                          S2 Update

                          Danke, es hätte ja vielleicht tatsächlich ne Alternative sein können. Aber Ich warte erstmal ab was da nich so alles kommt. Sowohl der Adapter als auch die API stellt nicht die für mich interessanten zu automatisierenden Funktionen bereit. Abwarten und Kaffee trinken.

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

                            @apollon77 Alles i.O . mit der neuen Version, beide Adapter sind grün !! TOP

                            1 Reply Last reply Reply Quote 0
                            • JB_Sullivan
                              JB_Sullivan last edited by

                              Mal eine kurze Frage am Rande. Ich war jetzt eine Woche nicht aktiv und sehe heute, das schon wieder 9 Adapter Updates und ein js-controller Update anstehen.

                              In welcher Reihenfolge machte man es am "Richtigsten"?

                              Erst den js-controller und dann die Adapter Updates oder anders herum?

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

                                @JB_Sullivan Erst die Adapter, dann der controller. So mache ich es jedenfalls immer.
                                Und das darunter liegende System halte ich auch auf Stand.

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

                                  @Thomas-Braun
                                  Da hätte ich jetzt exakt anderes rum getippt. Zuerst das System dann das was drauf aufbaut. Wobei ich das schon so und so gemacht hatte und weder noch ein Problem damit 😉

                                  1 Reply Last reply Reply Quote 0
                                  • JB_Sullivan
                                    JB_Sullivan last edited by

                                    Ja ich habe auch schon beides gemacht, aber eigentlich habe ich immer Probleme ( siehe hier: https://forum.iobroker.net/topic/32892/update-prozess-unendlich-lang-iob-defekt/7 )

                                    Darum dachte ich das es ggf. eine zwingende Reihenfolge geben sollte.

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

                                      @JB_Sullivan Empfohlen wird es wohl so:

                                      Die folgenden Adapter müssen auf die genannten Minimalversionsnummern aktualisiert werden, da diese sonst nicht mit dem js-controller 3.0/3.1 funktionieren. Diese Updates am besten vorher ausführen, weil alle genannten Versionen auch mit den alten js-controller Versionen funktionieren.

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

                                        @JB_Sullivan
                                        Du bist auf nem Windows System mit IOBroker, da ist eh wieder alles anderes und nicht ganz so optimal.

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

                                          @Jan1 @JB_Sullivan
                                          Bei Windows-Installer soll man auf einen aktualisierten Installer warten, hab ich irgendwo gelesen. Aber da ich kein Windows fahre...

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

                                            @Thomas-Braun

                                            Bei meinem Produktiv System würde ich das auch tun, aber ich kann die Finger nicht von diesen latest Updates auf meinem Testsystem lassen. Wenn das dann man baden geht, ist es prinzipell nicht schlimm, aber es Fuckt mich dann trotzdem immer wieder ab, wenn ich das Testsystem neu aufsetzten muss.

                                            J 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

                                            876
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

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