Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 5.0.x jetzt in der BETA

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    js-controller 5.0.x jetzt in der BETA

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

      @lausid da war allerdings noch ein fix dazwischen daher nicht 1:1 dasselbe. Vermute dass da was verbogen war

      1 Reply Last reply Reply Quote 0
      • mcm1957
        mcm1957 @bommel_030 last edited by

        @bommel_030 said in js-controller 5.0.x jetzt in der BETA:

        @foxriver76
        der km200 Version 2.0.4 läuft bei mir wieder mit js-controller 5.0.6, danke!

        Hi bommel_030

        Ich hab am km200 noch ein paar lange fällige Aufräumaktionen gemacht (Tests zum Laufen gebracht, fehlende dependencies ergänzt, Fehler in io-package.json gefixed, noch nicht angepasste urls angepasst, ...). Am Code selbst sollte sich aber nichts geändert haben.

        Da du offensichtlich eine Testmöglichkeit für den km200 hast könntest du bitte so nett sein und die 2.0.5 nochmal bewusst testen.

        DANKE

        P.S. LEdier kann ich von den offenen Issues voraussichtlich nichts fixen, da der Code selbst ei n gröberes Rewrite benötigen würde und ich keinerlei Testmöglichkeiten habe. Da muss ich / wir warten bis es einen dev mit Testmöglichkeit gibt 😞

        B K 3 Replies Last reply Reply Quote 0
        • B
          bommel_030 @mcm1957 last edited by

          @mcm57
          Klar, kann ich machen. Hab aber nur einen einfachen Brenner, und kann daher wahrscheinlich nicht alles testen was der Adapter kann.

          mcm1957 1 Reply Last reply Reply Quote 0
          • mcm1957
            mcm1957 @bommel_030 last edited by mcm1957

            @bommel_030
            Kein Problem - jeder Test ist besser als keiner.
            Und dann gibts ja noch den latest.
            Und den echten Fehler kommen dann im Oktober 🙂

            DANKE im Voraus

            mcm1957 1 Reply Last reply Reply Quote 0
            • mcm1957
              mcm1957 @mcm1957 last edited by

              @apollon77

              Adapter systeminfo crashed mit js-controller 5
              https://github.com/iobroker-community-adapters/ioBroker.systeminfo/issues/81
              https://github.com/iobroker-community-adapters/ioBroker.systeminfo/issues/82

              Grothesk242 created this issue in iobroker-community-adapters/ioBroker.systeminfo

              closed SemVer is broken. #81

              mcm1957 created this issue in iobroker-community-adapters/ioBroker.systeminfo

              closed Check / Fix compatibility with js-controller 5 #82

              1 Reply Last reply Reply Quote 0
              • K
                kimukao @mcm1957 last edited by kimukao

                @mcm57 Habe den km200 Adapter auf 2.0.5 aktualisiert, nachdem 2.0.4 keine Datenpunkte in der Verzeichnisstruktur mehr aufgebaut hatte. Leider dasselbe Problem. Ist der Fehler bekannt?

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

                  Version 5.0.7 ist auf dem Weg:

                  • Fehler in adapter.registerNotification Methode behoben (hatte aufgrund eines Fehlers noch nie funktioniert)
                  • Webserver Upgrade für Adapter hinzugefügt - wird vorrangig Admin in naher Zukunft erlauben dem User den Status eines Admin Updates anzuzeigen obwohl der Adapter während des Vorgangs gestoppt ist
                  • Fehler behoben um Controller UI Upgrade im offiziellen Docker Container zu unterstützen. Version 8.1.0 des Containers wird benötigt
                  • Fehler in getStatesmit Aliassen behoben, was dazu geführt hatte, dass z. B. Alias Werte mit einem nicht Admin User immer als null angezeigt wurden
                  • Absturz behoben, falls ein .thisisdocker File mit ungültiger Version existiert
                  B 1 Reply Last reply Reply Quote 5
                  • mcm1957
                    mcm1957 @kimukao last edited by

                    @kimukao
                    Nein nicht wirklich.
                    Bitte issue mit allen verfügbaren Infos, vor allem Versionsangaben und log im debug mode.

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kimukao @mcm1957 last edited by

                      @mcm57 Danke, hat sich erledigt. Mit dem ems-esp Adapter klappt‘s. Hab die Skripte angepasst. Danke trotzdem.

                      1 Reply Last reply Reply Quote 0
                      • ice987
                        ice987 @ice987 last edited by ice987

                        0166b78e-c01a-447e-b72e-5e288272426e-image.png

                        -> SyntaxError: Unexpected token '<', "<!doctype "... is not valid JSON

                        2023-07-10 07:22:33.789 - info: host.iobroker-testsystem8 Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
                        2023-07-10 07:23:44.644 - info: host.iobroker-testsystem8 Controller will upgrade itself to version 5.0.7
                        2023-07-10 07:23:50.402 - info: host.iobroker-testsystem8 [CONTROLLER_AUTO_UPGRADE] Stopping controller
                        

                        ioBroker.admin: v6.6.0
                        ioBroker.js-controller: v5.0.6 -> v5.0.7
                        Plattform: ioBroker.docker v8.1.0-beta.3
                        Betriebssystem: linux
                        Architektur: x64
                        Node.js: v18.16.1
                        NPM: 9.5.1

                        foxriver76 ice987 2 Replies Last reply Reply Quote 0
                        • foxriver76
                          foxriver76 Developer @ice987 last edited by

                          @ice987 As always, eine Neuerung die mit 5.0.7 kommt funktioniert nur wenn das Upgrade mit 5.0.7 angestoßen wird, also muss es leider erst eine 5.0.8 geben um das ausprobieren zu können.

                          Neuschwansteini 1 Reply Last reply Reply Quote 1
                          • Neuschwansteini
                            Neuschwansteini Banned @foxriver76 last edited by

                            @foxriver76

                            Hi, der cannot call visutils ist in der 5.0.7 immer noch da..

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

                              @ilovegym ganze Logzeile bitte

                              Neuschwansteini 1 Reply Last reply Reply Quote 0
                              • B
                                bommel_030 @foxriver76 last edited by

                                @foxriver76

                                Update über den Admin hat geklappt, evtl. Schönheitsfehler, Server läuft auf httpS nicht http. Und soll die Meldung doppelt kommen?

                                Stopping controller
                                Successfully stopped js-controller
                                Server is running on http://localhost:8081
                                
                                changed 14 packages in 36s
                                
                                286 packages are looking for funding
                                  run `npm fund` for details
                                
                                changed 14 packages in 36s
                                
                                286 packages are looking for funding
                                  run `npm fund` for details
                                
                                ---------------------------------------------------
                                js-controller wurde erfolgreich auf 5.0.7 aktualisiert
                                

                                Meine "null"-Aliase haben jetzt auch wieder einen Inhalt als nicht-admin Nutzer. Ich habe weiterhin das Probleme, dass ich mich nach einem reboot einmal als admin anmelden muss. Nehme ich nach dem reboot meinen Standaruser kommt die Fehlermeldung.

                                Error in GUI!
                                Please open the browser console (F12), copy error text from there and create the issue on github
                                Without this information it is not possible to analyse the error.
                                It should looks like
                                error
                                If in the second line you will see at :3000/static/js/main.chunk.js:36903 and not the normal file name,
                                please try to reproduce an error with opened browser console. In this case the special "map" files will be loaded and the developers can see the real name of functions and files.
                                Loading chunk 8855 failed. (error: https://mein.reverse.proxy/static/js/8855.45f1cd9d.chunk.js)
                                ChunkLoadError: Loading chunk 8855 failed.function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}(error: https://mein.reverse.proxy/static/js/8855.45f1cd9d.chunk.js)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at t.f.j (https://mein.reverse.proxy/static/js/main.e2346901.js:1:13656)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at https://mein.reverse.proxy/static/js/main.e2346901.js:1:1292function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at Array.reduce (<anonymous>)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at t.e (https://mein.reverse.proxy/static/js/main.e2346901.js:1:1257)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at https://mein.reverse.proxy/static/js/58.6dd21bc9.chunk.js:2:240446function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at P (https://mein.reverse.proxy/static/js/2791.8afe157f.chunk.js:2:3351)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at Ei (https://mein.reverse.proxy/static/js/4164.29c179b8.chunk.js:2:120786)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at ks (https://mein.reverse.proxy/static/js/4164.29c179b8.chunk.js:2:109418)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at ys (https://mein.reverse.proxy/static/js/4164.29c179b8.chunk.js:2:109346)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at vs (https://mein.reverse.proxy/static/js/4164.29c179b8.chunk.js:2:109209)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at as (https://mein.reverse.proxy/static/js/4164.29c179b8.chunk.js:2:104313)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at S (https://mein.reverse.proxy/static/js/4164.29c179b8.chunk.js:2:131316)function(e,t){return(0,le.jsxs)("div",{children:[e,(0,le.jsx)("br",{})]},t)}    at MessagePort.T (https://mein.reverse.proxy/static/js/4164.29c179b8.chunk.js:2:131850)
                                

                                Danach hilft nur reboot und anmelden als Admin. Mir wird dann Instanz admin.0 als deaktiviert weil loop detect angezeigt. Wenn ich dann den admin abmelde und wieder den normalen Nutzer anmelde läuft alles einwandfrei. Bin mir jetzt n icht sicher ob das hier oder als admin issue besser aufgehoben ist.

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

                                  @bommel_030 Wenn Restart Loop detected muss ja was im Log stehen.

                                  Und bitte auch Log aus Browser Console posten, wie oben beschrieben ist.

                                  Doppel Logging und http/s Logging fixe ich

                                  B 1 Reply Last reply Reply Quote 0
                                  • B
                                    bommel_030 @foxriver76 last edited by

                                    @foxriver76
                                    Erstmal Log nach reboot. Versucht als user anzumelden. Dann den webserver :8082 aufgerufen, dort abgemeldet. Unter :8081 als admin angemeldet, alles ok.
                                    Admin abmelden, user anmelden, soweit alles ok. Was ich jetzt aber noch festgestellt habe, ich habe als user versucht die Logstufe von admin.0 zu ändern bekomme ich den Toast "permission error", das taucht im Log allerdings nicht auf. Habe dann noch probiert via shuttercontrol mal alle Rolläden zu öffnen, da wurde mir der Zugriff auch verweigert. Letzte Zeile im Log. Als admin fahren die Rolläden wie erwartet hoch.

                                    2023-07-10 11:21:12.932  - info: admin.0 (578) failed connection to socket.io from ::ffff:192.168.10.57: Passport was not initialized
                                    2023-07-10 11:21:12.932  - info: admin.0 (578) failed connection to socket.io from ::ffff:192.168.10.57: Passport was not initialized
                                    2023-07-10 11:21:24.713  - info: admin.0 (578) ==> Connected system.user.bommel from ::ffff:192.168.10.57
                                    2023-07-10 11:21:24.713  - info: admin.0 (578) ==> Connected system.user.bommel from ::ffff:192.168.10.57
                                    2023-07-10 11:21:25.218  - warn: admin.0 (578) Permission error for user "system.user.bommel" on "system.adapter.admin.0.logging": setState
                                    2023-07-10 11:21:25.219  - error: admin.0 (578) 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().
                                    2023-07-10 11:21:25.219  - error: admin.0 (578) unhandled promise rejection: permissionError
                                    2023-07-10 11:21:25.313  - error: admin.0 (578) Error: permissionError
                                       at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                       at runNextTicks (node:internal/process/task_queues:60:5)
                                       at processImmediate (node:internal/timers:447:9)
                                       at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:21:25.314  - error: admin.0 (578) permissionError
                                    2023-07-10 11:21:25.321  - info: admin.0 (578) terminating https server on port 8081
                                    2023-07-10 11:21:25.323  - info: admin.0 (578) terminating
                                    2023-07-10 11:21:25.323  - warn: admin.0 (578) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                    2023-07-10 11:21:25.823  - info: admin.0 (578) terminating
                                    2023-07-10 11:21:26.067  - error: host.iobroker-master 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:
                                    2023-07-10 11:21:26.069  - error: host.iobroker-master Caught by controller[0]: Error: permissionError
                                    2023-07-10 11:21:26.069  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master Caught by controller[0]:     at runNextTicks (node:internal/process/task_queues:60:5)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master Caught by controller[0]:     at processImmediate (node:internal/timers:447:9)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    2023-07-10 11:21:25.218  - warn: admin.0 (578) Permission error for user "system.user.bommel" on "system.adapter.admin.0.logging": setState
                                    2023-07-10 11:21:25.219  - error: admin.0 (578) 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().
                                    2023-07-10 11:21:25.219  - error: admin.0 (578) unhandled promise rejection: permissionError
                                    2023-07-10 11:21:25.313  - error: admin.0 (578) Error: permissionError
                                       at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                       at runNextTicks (node:internal/process/task_queues:60:5)
                                       at processImmediate (node:internal/timers:447:9)
                                       at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:21:25.314  - error: admin.0 (578) permissionError
                                    2023-07-10 11:21:25.321  - info: admin.0 (578) terminating https server on port 8081
                                    2023-07-10 11:21:25.323  - info: admin.0 (578) terminating
                                    2023-07-10 11:21:25.323  - warn: admin.0 (578) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                    2023-07-10 11:21:25.823  - info: admin.0 (578) terminating
                                    2023-07-10 11:21:26.067  - error: host.iobroker-master 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:
                                    2023-07-10 11:21:26.069  - error: host.iobroker-master Caught by controller[0]: Error: permissionError
                                    2023-07-10 11:21:26.069  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master Caught by controller[0]:     at runNextTicks (node:internal/process/task_queues:60:5)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master Caught by controller[0]:     at processImmediate (node:internal/timers:447:9)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:21:26.070  - error: host.iobroker-master instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    2023-07-10 11:21:58.526  - info: admin.0 (2198) starting. Version 6.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.7
                                    2023-07-10 11:21:58.586  - info: admin.0 (2198) requesting all states
                                    2023-07-10 11:21:58.586  - info: admin.0 (2198) requesting all objects
                                    2023-07-10 11:21:58.995  - info: admin.0 (2198) Request actual repository...
                                    2023-07-10 11:21:58.526  - info: admin.0 (2198) starting. Version 6.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.7
                                    2023-07-10 11:21:58.586  - info: admin.0 (2198) requesting all states
                                    2023-07-10 11:21:58.586  - info: admin.0 (2198) requesting all objects
                                    2023-07-10 11:21:58.995  - info: admin.0 (2198) Request actual repository...
                                    2023-07-10 11:22:01.267  - info: admin.0 (2198) received all objects
                                    2023-07-10 11:22:01.402  - info: admin.0 (2198) Secure socket.io server listening on port 8081
                                    2023-07-10 11:22:01.403  - info: admin.0 (2198) https server listening on port 8081
                                    2023-07-10 11:22:01.404  - info: admin.0 (2198) Use link "https://127.0.0.1:8081" to configure.
                                    2023-07-10 11:22:01.838  - info: admin.0 (2198) Repository received successfully.
                                    2023-07-10 11:22:01.267  - info: admin.0 (2198) received all objects
                                    2023-07-10 11:22:01.402  - info: admin.0 (2198) Secure socket.io server listening on port 8081
                                    2023-07-10 11:22:01.403  - info: admin.0 (2198) https server listening on port 8081
                                    2023-07-10 11:22:01.404  - info: admin.0 (2198) Use link "https://127.0.0.1:8081" to configure.
                                    2023-07-10 11:22:01.838  - info: admin.0 (2198) Repository received successfully.
                                    2023-07-10 11:22:05.392  - info: admin.0 (2198) ==> Connected system.user.bommel from ::ffff:192.168.10.57
                                    2023-07-10 11:22:05.392  - info: admin.0 (2198) ==> Connected system.user.bommel from ::ffff:192.168.10.57
                                    2023-07-10 11:22:05.901  - warn: admin.0 (2198) Permission error for user "system.user.bommel" on "system.adapter.admin.0.logging": setState
                                    2023-07-10 11:22:05.903  - error: admin.0 (2198) 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().
                                    2023-07-10 11:22:05.904  - error: admin.0 (2198) unhandled promise rejection: permissionError
                                    2023-07-10 11:22:05.971  - error: admin.0 (2198) Error: permissionError
                                       at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                       at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:22:05.971  - error: admin.0 (2198) permissionError
                                    2023-07-10 11:22:05.977  - info: admin.0 (2198) terminating https server on port 8081
                                    2023-07-10 11:22:05.978  - info: admin.0 (2198) terminating
                                    2023-07-10 11:22:05.979  - warn: admin.0 (2198) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                    2023-07-10 11:22:06.479  - info: admin.0 (2198) terminating
                                    2023-07-10 11:22:06.614  - error: host.iobroker-master 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:
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master Caught by controller[0]: Error: permissionError
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    2023-07-10 11:22:05.901  - warn: admin.0 (2198) Permission error for user "system.user.bommel" on "system.adapter.admin.0.logging": setState
                                    2023-07-10 11:22:05.903  - error: admin.0 (2198) 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().
                                    2023-07-10 11:22:05.904  - error: admin.0 (2198) unhandled promise rejection: permissionError
                                    2023-07-10 11:22:05.971  - error: admin.0 (2198) Error: permissionError
                                       at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                       at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:22:05.971  - error: admin.0 (2198) permissionError
                                    2023-07-10 11:22:05.977  - info: admin.0 (2198) terminating https server on port 8081
                                    2023-07-10 11:22:05.978  - info: admin.0 (2198) terminating
                                    2023-07-10 11:22:05.979  - warn: admin.0 (2198) Terminated (UNCAUGHT_EXCEPTION): Without reason
                                    2023-07-10 11:22:06.479  - info: admin.0 (2198) terminating
                                    2023-07-10 11:22:06.614  - error: host.iobroker-master 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:
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master Caught by controller[0]: Error: permissionError
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass._checkStates (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7931:27)
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master Caught by controller[0]:     at AdapterClass.setForeignState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:8290:24)
                                    2023-07-10 11:22:06.615  - error: host.iobroker-master instance system.adapter.admin.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                                    2023-07-10 11:22:38.961  - info: admin.0 (2229) starting. Version 6.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.7
                                    2023-07-10 11:22:39.024  - info: admin.0 (2229) requesting all states
                                    2023-07-10 11:22:39.024  - info: admin.0 (2229) requesting all objects
                                    2023-07-10 11:22:39.414  - info: admin.0 (2229) Request actual repository...
                                    2023-07-10 11:22:38.961  - info: admin.0 (2229) starting. Version 6.6.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.7
                                    2023-07-10 11:22:39.024  - info: admin.0 (2229) requesting all states
                                    2023-07-10 11:22:39.024  - info: admin.0 (2229) requesting all objects
                                    2023-07-10 11:22:39.414  - info: admin.0 (2229) Request actual repository...
                                    2023-07-10 11:22:41.555  - info: admin.0 (2229) received all objects
                                    2023-07-10 11:22:41.693  - info: admin.0 (2229) Secure socket.io server listening on port 8081
                                    2023-07-10 11:22:41.694  - info: admin.0 (2229) https server listening on port 8081
                                    2023-07-10 11:22:41.695  - info: admin.0 (2229) Use link "https://127.0.0.1:8081" to configure.
                                    2023-07-10 11:22:42.015  - info: admin.0 (2229) Repository received successfully.
                                    2023-07-10 11:22:41.555  - info: admin.0 (2229) received all objects
                                    2023-07-10 11:22:41.693  - info: admin.0 (2229) Secure socket.io server listening on port 8081
                                    2023-07-10 11:22:41.694  - info: admin.0 (2229) https server listening on port 8081
                                    2023-07-10 11:22:41.695  - info: admin.0 (2229) Use link "https://127.0.0.1:8081" to configure.
                                    2023-07-10 11:22:42.015  - info: admin.0 (2229) Repository received successfully.
                                    2023-07-10 11:22:54.806  - info: admin.0 (2229) failed connection to socket.io from ::ffff:192.168.10.57: Passport was not initialized
                                    2023-07-10 11:22:54.806  - info: admin.0 (2229) failed connection to socket.io from ::ffff:192.168.10.57: Passport was not initialized
                                    2023-07-10 11:23:14.817  - info: admin.0 (2229) ==> Connected system.user.admin from ::ffff:192.168.10.57
                                    2023-07-10 11:23:14.817  - info: admin.0 (2229) ==> Connected system.user.admin from ::ffff:192.168.10.57
                                    2023-07-10 11:23:26.360  - info: admin.0 (2229) <== Disconnect system.user.admin from ::ffff:192.168.10.57 admin
                                    2023-07-10 11:23:26.360  - info: admin.0 (2229) <== Disconnect system.user.admin from ::ffff:192.168.10.57 admin
                                    2023-07-10 11:23:32.591  - info: admin.0 (2229) ==> Connected system.user.bommel from ::ffff:192.168.10.57
                                    2023-07-10 11:23:32.591  - info: admin.0 (2229) ==> Connected system.user.bommel from ::ffff:192.168.10.57
                                    2023-07-10 11:23:55.651  - warn: admin.0 (2229) Permission error for user "system.user.bommel" on "shuttercontrol.0.control.openAll": setState
                                    2023-07-10 11:23:55.651  - warn: admin.0 (2229) Permission error for user "system.user.bommel" on "shuttercontrol.0.control.openAll": setState
                                    
                                    


                                    iobroker.admin@6.6.0
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:24.579Z] Try to connect
                                    312.4df0a1cd.chunk.js:2 Stored version: , new version: 6.6.0
                                    312.4df0a1cd.chunk.js:2 Connected: true
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:25.857Z] ws connection error: CLOSE_ABNORMAL
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:25.858Z] Start reconnect 0
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:25.859Z] Try to connect
                                    socket.io.js:140 WebSocket connection to 'wss://192.168.10.15:8081/?sid=1688980885859&name=admin' failed: 
                                    SocketClient.connect @ socket.io.js:140
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:27.902Z] Start reconnect 1
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:27.902Z] ws connection error: CLOSE_ABNORMAL
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:27.902Z] Reconnect is already running 1
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:28.912Z] Try to connect
                                    socket.io.js:140 WebSocket connection to 'wss://192.168.10.15:8081/?sid=1688980888913&name=admin' failed: 
                                    SocketClient.connect @ socket.io.js:140
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:30.964Z] Start reconnect 2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:30.965Z] ws connection error: CLOSE_ABNORMAL
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:30.965Z] Reconnect is already running 2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:32.970Z] Try to connect
                                    socket.io.js:140 WebSocket connection to 'wss://192.168.10.15:8081/?sid=1688980892970&name=admin' failed: 
                                    SocketClient.connect @ socket.io.js:140
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:35.013Z] Start reconnect 3
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:35.013Z] ws connection error: CLOSE_ABNORMAL
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:35.014Z] Reconnect is already running 3
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:38.017Z] Try to connect
                                    socket.io.js:140 WebSocket connection to 'wss://192.168.10.15:8081/?sid=1688980898017&name=admin' failed: 
                                    SocketClient.connect @ socket.io.js:140
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:40.065Z] Start reconnect 4
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:40.065Z] ws connection error: CLOSE_ABNORMAL
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:40.065Z] Reconnect is already running 4
                                    312.4df0a1cd.chunk.js:2 Cannot getRepositoryCompact: timeout
                                    312.4df0a1cd.chunk.js:2 Cannot getInstalled: notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 Cannot read adapters: notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    2312.4df0a1cd.chunk.js:2 [ADAPTERS] Cannot compare "" and "5.0.7"
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    :8081/#tab-intro:1 Mixed Content: The page at 'https://192.168.10.15:8081/#tab-intro' was loaded over HTTPS, but requested an insecure element 'https://192.168.10.15:8081/img/no-image.png'. This request was not upgraded to HTTPS because its URL's host is an IP address.
                                    :8081/#tab-intro:1 Mixed Content: The page at 'https://192.168.10.15:8081/#tab-intro' was loaded over HTTPS, but requested an insecure element 'https://192.168.10.15:8081/img/no-image.png'. This request was not upgraded to HTTPS because its URL's host is an IP address.
                                    312.4df0a1cd.chunk.js:2 Cannot get instances: notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 Cannot get hosts: notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 Cannot get notifications: notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [ADAPTERS] Cannot compare "" and "5.0.7"
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 Cannot get logs: notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [ADAPTERS] Cannot compare "" and "5.0.7"
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    8855.45f1cd9d.chunk.js:1     Failed to load resource: net::ERR_CONNECTION_REFUSED
                                    312.4df0a1cd.chunk.js:2 ChunkLoadError: Loading chunk 8855 failed.
                                    (error: https://192.168.10.15:8081/static/js/8855.45f1cd9d.chunk.js)
                                       at t.f.j (main.e2346901.js:1:13656)
                                       at main.e2346901.js:1:1292
                                       at Array.reduce (<anonymous>)
                                       at t.e (main.e2346901.js:1:1257)
                                       at 58.6dd21bc9.chunk.js:2:240446
                                       at P (2791.8afe157f.chunk.js:2:3351)
                                       at Ei (4164.29c179b8.chunk.js:2:120786)
                                       at ks (4164.29c179b8.chunk.js:2:109418)
                                       at ys (4164.29c179b8.chunk.js:2:109346)
                                       at vs (4164.29c179b8.chunk.js:2:109209)
                                       at as (4164.29c179b8.chunk.js:2:104313)
                                       at S (4164.29c179b8.chunk.js:2:131316)
                                       at MessagePort.T (4164.29c179b8.chunk.js:2:131850)
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    :8081/#tab-intro:1 Mixed Content: The page at 'https://192.168.10.15:8081/#tab-intro' was loaded over HTTPS, but requested an insecure element 'https://192.168.10.15:8081/img/browserError.png'. This request was not upgraded to HTTPS because its URL's host is an IP address.
                                    :8081/#tab-intro:1 Mixed Content: The page at 'https://192.168.10.15:8081/#tab-intro' was loaded over HTTPS, but requested an insecure element 'https://192.168.10.15:8081/img/browserError.png'. This request was not upgraded to HTTPS because its URL's host is an IP address.
                                    no-image.png:1     Failed to load resource: net::ERR_CONNECTION_REFUSED
                                    browserError.png:1     Failed to load resource: net::ERR_CONNECTION_REFUSED
                                    :8081/#tab-intro:1 Uncaught (in promise) notConnectedError
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:44.066Z] Try to connect
                                    200312.4df0a1cd.chunk.js:2 notConnectedError
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    socket.io.js:140 WebSocket connection to 'wss://192.168.10.15:8081/?sid=1688980904067&name=admin' failed: 
                                    SocketClient.connect @ socket.io.js:140
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:46.113Z] Start reconnect 5
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:46.113Z] ws connection error: CLOSE_ABNORMAL
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:46.113Z] Reconnect is already running 5
                                    leaflet.css:1     GET https://192.168.10.15:8081/css/leaflet.css net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/lib/js/sparkline.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/main.e2346901.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/4223.59e16f0c.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/9907.74f37862.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/5377.b4b7e5a7.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/4564.8797be67.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:51.127Z] Try to connect
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/2791.8afe157f.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/2007.7259ed0a.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/7273.ce8e3693.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/4410.f7536cb0.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/4164.29c179b8.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/7116.2532a7ad.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    socket.io.js:140 WebSocket connection to 'wss://192.168.10.15:8081/?sid=1688980911127&name=admin' failed: 
                                    SocketClient.connect @ socket.io.js:140
                                    (anonymous) @ socket.io.js:428
                                    o @ 312.4df0a1cd.chunk.js:2
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:53.183Z] Start reconnect 5
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:53.183Z] ws connection error: CLOSE_ABNORMAL
                                    (anonymous) @ 312.4df0a1cd.chunk.js:2
                                    error @ socket.io.js:68
                                    socket.onclose @ socket.io.js:177
                                    312.4df0a1cd.chunk.js:2 [2023-07-10T09:21:53.183Z] Reconnect is already running 5
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/9256.4c640c0d.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/6264.ba6e9ccf.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    DevTools failed to load source map: Could not load content for https://192.168.10.15:8081/static/js/3303.2a92f4de.chunk.js.map: Connection error: net::ERR_CONNECTION_REFUSED
                                    

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

                                      @bommel_030 Danke, ich konnte es fixen.

                                      1 Reply Last reply Reply Quote 1
                                      • Neuschwansteini
                                        Neuschwansteini Banned @foxriver76 last edited by

                                        @foxriver76 gerne, ich hab zwar Vis installiert, benutze das aber nicht. Meine view wird mit MinuVis dargestellt.
                                        System: Debian Bookworm, Proxmox lxc, Node 18.16.1, NPM 9.5.1, Admin 6.6.0, JS Controller 5.0.7

                                        
                                        2023-07-10 13:21:00.633  - error: host.iobrokerS2 cannot call visUtils: Not exists
                                        
                                        

                                        Was ist das VisUtils…?

                                        foxriver76 1 Reply Last reply Reply Quote 0
                                        • B
                                          bommel_030 @mcm1957 last edited by

                                          @mcm57
                                          Kurz zum km200 und js 5.X
                                          Habe km200 auf 2.0.4 aktualisiert gehabt und nur stichprobenartig in meine Datenpunkte geschaut. Abgastemperatur z.B. hat sich korrekt aktualisiert und geändert.
                                          Habe dann auf die 2.0.5 aktualisiert und die Anzahl der Datenpunkte (bei nicht geändertem Filter) ist auf 18 zusammengeschrumpft. Der Datenpunkt Flamme AN/AUS ist zum Beispiel nicht mehr vorhanden. Downgrade auf 2.0.4 hat die Datenpunkte auch nicht zurück gebracht.
                                          Im Log kommt als Warnung nur:

                                          INit getservices error TypeError: Cannot create property '0' on boolean 'false' at /opt/iobroker/node_modules/iobroker.km200/km200.js:455:61 at Array.forEach (<anonymous>) at /opt/iobroker/node_modules/iobroker.km200/km200.js:455:37 at /opt/iobroker/node_modules/iobroker.km200/lib/myAdapter.js:822:53
                                          

                                          Wenn ich den Filter, also die Blacklist komplett leer lasse kommt nur ein Datenpunkt zur Firmware und die anderen 18 sind weg. Für mein Verständnis sollte eine leere Blacklist keine Datenpunkte blockieren.

                                          Ich werde mir den EMS Adapter mal anschauen was der für Daten liefert, vielleicht hat Buderus auch was geändert. Da ich dafür den QR auf dem Brenner brauche wird das allerdings frühestens nächste Woche was, selbiger steht aktuell gut 1000 km entfernt 😉

                                          mcm1957 1 Reply Last reply Reply Quote 0
                                          • mcm1957
                                            mcm1957 @bommel_030 last edited by

                                            @bommel_030

                                            Sorry,
                                            Wenn es auch mit der .4 nicht geht hab ich im Moment keine Ahnung.

                                            Da es aber - wie ich gestern mitbekommen habe - den ems-esp Adapter gibt laufen zur Zeit Überlegungen den km200 offiziell auf DEPRECATED zu setzen da es einerseits keine Maintainer mit Testmöglichkeit gibt (so wie es aussieht) und andrerseits 2 Adapter für dasselbe Gerät selten Sinn machen.

                                            B 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

                                            729
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            71
                                            580
                                            122884
                                            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