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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    js-controller 5.0.x jetzt in der BETA

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

      @foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:

      @feuersturm ja Web Adapter sollte das in Zukunft catchen aber das binding ist ist nicht valide. Du hast da alles val assigned und arbeitest nie damit.

      Wie wäre es denn richtig?

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

        @feuersturm bin nur am Handy aber vermutlich so in die Richtung

        {val:javascript.0.Google_Maps.nach_Hause_x.Staustufe_0;parseInt(val) > 0 ? "mdui-red-glow": ""}

        Feuersturm 1 Reply Last reply Reply Quote 2
        • Feuersturm
          Feuersturm @foxriver76 last edited by

          @foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:

          {val:javascript.0.Google_Maps.nach_Hause_x.Staustufe_0;parseInt(val) > 0 ? "mdui-red-glow": ""}

          Dankeschön. Scheint zu funktionieren. Es gibt zumindest schonmal keine Fehler mehr im Log 🙂

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

            Wenn ich den VIS1 Editor oder die VIS1 Runtime unter Firefox von meinem Testsystem mit js-controller 5.0.4 öffne dann lädt die jeweilige Seite nicht und folgendes steht im Log

            Create inner vis object rainbird.0.device.stations.2.runZone instrument.ts:129:35
Create inner vis object rainbird.0.device.stations.3.runZone instrument.ts:129:35
Create inner vis object rainbird.0.device.stations.4.runZone instrument.ts:129:35
Create inner vis object device-watcher.0.sonos.listAll instrument.ts:129:35
"Use background": {"en": "Use background", "de": "Use background", "ru": "Use background"}, instrument.ts:129:35
Uncaught SyntaxError: JSON.parse: unexpected non-whitespace character after JSON data at line 1 column 6 of the JSON data
    unserialize http://192.168.178.77:8082/vis/lib/js/loStorage.js:2
    get http://192.168.178.77:8082/vis/lib/js/loStorage.js:2
    i[l][f]</< http://192.168.178.77:8082/vis/lib/js/loStorage.js:2
    bindInstance http://192.168.178.77:8082/vis/js/vis.js:583
    initNext http://192.168.178.77:8082/vis/js/vis.js:712
    init http://192.168.178.77:8082/vis/js/vis.js:610
    loadWidgetSets http://192.168.178.77:8082/vis/js/vis.js:575
    init http://192.168.178.77:8082/vis/js/vis.js:609
    afterInit http://192.168.178.77:8082/vis/js/vis.js:3609
    getConfig http://192.168.178.77:8082/vis/js/conn.js:1355
    findAnswer http://192.168.178.77:8082/lib/js/socket.io.js:304
    onmessage http://192.168.178.77:8082/lib/js/socket.io.js:212

            Wenn ich im Firefox den Vis Editor oder die Vis Runtime von meinem Produktivsystem aufrufe wo noch der js-controller 4.0.24 läuft, dann laden die beiden Seiten ohne Probleme.

            apollon77 1 Reply Last reply Reply Quote 0
            • MalleRalle
              MalleRalle last edited by

              @apollon77 @foxriver76
              Beim Export der Scripts kommt eine weisse Seite:
              File files/admin.0/zip/2023-06-16-scripts.zip not found

              Ist das schon bekannt?

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

                @malleralle Lt. https://github.com/ioBroker/ioBroker.javascript/issues/1340 tritt das auch mit altem Controller auf, also eher javascript Issue

                MK-66 created this issue in ioBroker/ioBroker.javascript

                closed Export all scripts does not work since v7.0.5 #1340

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

                  @einstein67 teils teils, wird im Controller gefixt sein in der nächsten Version.

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

                    @feuersturm Das ist ja im Browser ... da scheint irgendwas mit den Daten im local Storage zu sein ... da kann an sich der controller nix für ... Bitte mal vis issue

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

                      @apollon77 mit einem Browser Cache löschen hat sich das Problem gelöst.

                      1 Reply Last reply Reply Quote 0
                      • F
                        fastfoot @MalleRalle last edited by

                        @malleralle ja, gibt ein issue dazu und für controller 5.x nutzer auch einen Workaround

                        1 Reply Last reply Reply Quote 0
                        • F
                          fastfoot @foxriver76 last edited by

                          @foxriver76 ja, tritt auch mit altem controller auf, issue gibt es schon
                          https://github.com/ioBroker/ioBroker.javascript/issues/1340#issuecomment-1591811349

                          MK-66 created this issue in ioBroker/ioBroker.javascript

                          closed Export all scripts does not work since v7.0.5 #1340

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

                            Bei mir kommt eine Fehlermeldung deren Ursprung ich nicht so richtig lokalisieren kann:

                            host.ioBroker
2023-06-17 10:02:01.583	error	instance system.adapter.web.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker
2023-06-17 10:02:01.582	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
host.ioBroker
2023-06-17 10:02:01.582	error	Caught by controller[1]: at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1116:27)
host.ioBroker
2023-06-17 10:02:01.581	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
host.ioBroker
2023-06-17 10:02:01.580	error	Caught by controller[1]: Error: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern
host.ioBroker
2023-06-17 10:02:01.574	error	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:

web.0
2023-06-17 10:02:00.667	error	The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern

web.0
2023-06-17 10:02:00.667	error	Error: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at StateRedisClient.subscribe (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1116:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)

web.0
2023-06-17 10:02:00.506	error	unhandled promise rejection: The pattern "io.Samstag<br>17.06.2023" is not a valid ID pattern

web.0
2023-06-17 10:02:00.497	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().

                            Hat jemand eine Idee wo diese ungültige ID Pattern stehen könnte? Habe ich die eventuell selbst eingebaut, weil ich in der VIS öfter mal mit Bindings gearbeitet habe?

                            Wenn ich meinen VIS Editor aufrufe habe ich Verbindungsprobleme. Es Kommt immer die Einblendung "no connection" am oberen Rand. Edit: Browser refresh sollte man schon mal machen

                            Edit2:
                            Die Fehlermeldung ist erweitert:

                            host.ioBroker
2023-06-17 10:22:01.014	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker
2023-06-17 10:22:01.013	error	Caught by controller[1]: at processImmediate (node:internal/timers:476:21)
host.ioBroker
2023-06-17 10:22:01.013	error	Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
host.ioBroker
2023-06-17 10:22:01.013	error	Caught by controller[1]: at Array.forEach (<anonymous>)
host.ioBroker
2023-06-17 10:22:01.013	error	Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100
host.ioBroker
2023-06-17 10:22:01.013	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
host.ioBroker
2023-06-17 10:22:01.012	error	Caught by controller[1]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
host.ioBroker
2023-06-17 10:22:01.012	error	Caught by controller[1]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22)
host.ioBroker
2023-06-17 10:22:01.011	error	Caught by controller[1]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
host.ioBroker
2023-06-17 10:22:01.011	error	Caught by controller[1]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
host.ioBroker
2023-06-17 10:22:01.011	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
host.ioBroker
2023-06-17 10:22:01.011	error	Caught by controller[1]: Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern
host.ioBroker
2023-06-17 10:22:01.011	error	Caught by controller[0]: at processImmediate (node:internal/timers:476:21)
host.ioBroker
2023-06-17 10:22:01.010	error	Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
host.ioBroker
2023-06-17 10:22:01.010	error	Caught by controller[0]: at Array.forEach (<anonymous>)
host.ioBroker
2023-06-17 10:22:01.010	error	Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100
host.ioBroker
2023-06-17 10:22:01.010	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
host.ioBroker
2023-06-17 10:22:01.010	error	Caught by controller[0]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
host.ioBroker
2023-06-17 10:22:01.010	error	Caught by controller[0]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22)
host.ioBroker
2023-06-17 10:22:01.009	error	Caught by controller[0]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
host.ioBroker
2023-06-17 10:22:01.009	error	Caught by controller[0]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
host.ioBroker
2023-06-17 10:22:01.009	error	Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
host.ioBroker
2023-06-17 10:22:01.006	error	Caught by controller[0]: Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern

web.0
2023-06-17 10:22:00.556	error	The pattern "Samstag<br>17.06.2023" is not a valid ID pattern

web.0
2023-06-17 10:22:00.555	error	Error: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44) at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13) at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:492:22) at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25) at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43) at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100 at Array.forEach (<anonymous>) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83) at processImmediate (node:internal/timers:476:21)

web.0
2023-06-17 10:22:00.547	error	uncaught exception: The pattern "Samstag<br>17.06.2023" is not a valid ID pattern
                            foxriver76 1 Reply Last reply Reply Quote 0
                            • foxriver76
                              foxriver76 Developer @Chaot last edited by

                              @chaot Bitte mal allgemein jemand das Issue im Web Adapter melden, dass der bei sowas nicht mehr crasht.

                              Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.

                              Feuersturm Chaot apollon77 4 Replies Last reply Reply Quote 1
                              • Feuersturm
                                Feuersturm @foxriver76 last edited by

                                @foxriver76 sagte in js-controller 5.0.x jetzt in der BETA:

                                Ansonsten ja im Falle von @Feuersturm war es auch ein selbst erstelltes Binding, das aus Versehen die kompeltte Logik als ID hatte. Also einerseits schön, weil so auffällt, dass ein Binding kaputt ist, aber hart crashen sollte Adapter nicht.

                                Braucht ihr noch ein issue dafür beim Web Adapter?

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

                                  @feuersturm Ja bitte gg

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

                                    @foxriver76 Danke.
                                    Das fehlerhafte binding habe ich mittlerweile lokalisiert:

                                    {javascript.0.variables.dayTime.lc;momentDate(dddd)}<br>{javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}

                                    Komischerweise läuft das andere Binding in der zweiten View ohne Probleme, obwohl es (fast) gleich ist:

                                    {javascript.0.variables.dayTime.lc;momentDate(dd)}  {javascript.0.variables.dayTime.lc;momentDate(DD.MM.YYYY)}
                                    mcm1957 1 Reply Last reply Reply Quote 0
                                    • mcm1957
                                      mcm1957 @Chaot last edited by

                                      @apollon77

                                      Update für Problemliste:

                                      linux-control scheint ein Problem zu haben:
                                      https://github.com/Scrounger/ioBroker.linux-control/issues/49

                                      Für stiebel-isg und pi-hole dürfte es Updates geben:
                                      Im latest verfügbar (spätestens morgen), stable pending (kurze Karenzzeit erscheint sinnvoll)
                                      https://github.com/ioBroker/ioBroker.repositories/pull/2367

                                      Strobelix80 created this issue in Scrounger/ioBroker.linux-control

                                      closed Error with js-controller 5.x #49

                                      unltdnetworx created this issue in ioBroker/ioBroker.repositories

                                      closed Update sources-dist-stable.json - pi-hole and stiebel-isg #2367

                                      1 Reply Last reply Reply Quote 1
                                      • skvarel
                                        skvarel Developer last edited by

                                        Moin zusammen.

                                        bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau 😞

                                        a7ef0749-2914-4b8e-8e55-187b6bd79ee4-image.png

                                        Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0

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

                                          Es scheint an irgendwelchen Widgets zu liegen.

                                          @skvarel sagte in js-controller 5.0.x jetzt in der BETA:

                                          Moin zusammen.

                                          bei mir crashed der Web Adpater. Ich werde aus dem Log nicht schlau 😞

                                          a7ef0749-2914-4b8e-8e55-187b6bd79ee4-image.png

                                          Alle Adapter sind Beta, js-controller 5.0.4, Node 18.16.0

                                          M DJMarc75 2 Replies Last reply Reply Quote 0
                                          • M
                                            Marty56 @skvarel last edited by

                                            Ich habe gerade diesen "Alias Error Burst" bekommen.
                                            Schade, es scheint das js-controller 5 hier nicht geholfen hat.

                                            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

                                            911
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

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