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

    • Änderungen iob CLI/Installer/Fixer mit Root Accounts

    • ioBroker Community-Treffen 9.11.24 ausverkauft

    • js-controller Lucy (v7.0.0) jetzt im Beta Repository

    js-controller 5.0.x jetzt in der BETA

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

      @foxriver76 upload durchgeführt, zusätzlich war ein Reboot notwendig. Jetzt läuft der Host ohne Fehlermeldung. Dies zur Info

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

        bei mir erscheint

        IMG_0254.jpeg

        2023-06-12 21:02:59.879 - info: host.iobroker-testsystem8 Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
2023-06-12 21:03:32.474 - info: host.iobroker-testsystem8 Controller will upgrade itself to version 5.0.2
2023-06-12 21:04:11.371 - info: host.iobroker-testsystem8 Controller will upgrade itself to version 5.0.2

        Plattform: docker
        Betriebssystem: linux
        Architektur: x64
        Node.js: v18.16.0
        NPM: 9.5.1

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

          @crunchip Welches Betriebssystem?

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

            @foxriver76 debian VM in Proxmox
            aktuell js-controller: 5.0.1-alpha.0-20230406-4552d569
            f9c214e7-78b9-422b-8ab1-bda8e9a9cdba-image.png

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

              @crunchip Hmm.. ok dann sollte es eigentlich gehen. Müsste @Bluefox etwas zu sagen, wie der Admin Check genau ausschaut.

              haselchen crunchip 2 Replies Last reply Reply Quote 0
              • haselchen
                haselchen Most Active @foxriver76 last edited by

                @foxriver76

                @crunchip , ich und erstmal @heinhan hatten das „VIS“ Problem.
                Kommt da ein Fix zu ?!

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

                  @apollon77
                  Der LGTV Adapter fällt aus wie erwartet (ist aber bei mir eher unwichtig)
                  Dazu kommt noch eine Fehlermeldung:

                  host.ioBroker
2023-06-12 22:06:50.881	error	cannot call visUtils: Not exists

                  Die Fehlermeldung blieb jetzt erstmal weg nachdem ich den VIS Adapter nochmal hochgeladen habe.
                  Ansonsten scheint alles zu laufen.

                  Edit:
                  Scheinbar kommt doch noch was:

                  host.ioBroker
2023-06-12 22:20:00.903	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker
2023-06-12 22:20:00.903	error	Caught by controller[1]: at processImmediate (node:internal/timers:478:21)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46)
host.ioBroker
2023-06-12 22:20:00.902	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-12 22:20:00.902	error	Caught by controller[1]: Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[0]: at processImmediate (node:internal/timers:478:21)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46)
host.ioBroker
2023-06-12 22:20:00.901	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-12 22:20:00.899	error	Caught by controller[0]: Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.678	error	The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.678	error	Error: The pattern "Montag<br>12.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 Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46) at processImmediate (node:internal/timers:478:21)

web.0
2023-06-12 22:20:00.677	error	uncaught exception: The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.638	error	The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.637	error	Error: The pattern "Montag<br>12.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 Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46) at processImmediate (node:internal/timers:478:21)

web.0
2023-06-12 22:20:00.631	error	uncaught exception: The pattern "Montag<br>12.06.2023" is not a valid ID pattern
                  apollon77 ilovegym 2 Replies Last reply Reply Quote 0
                  • Chaot
                    Chaot last edited by

                    Der VIS Editor hat auf zwei von 5 Projekten mit einem Absturz reagiert. Nach einem Neustart der ganzen VM scheint es jetzt allerdings zu laufen.
                    Ich habe zwei Fehlermeldungen, die aber scheinbar bei mir aus dem System kommen und nichts mit dem Controler zu tun haben.
                    Wie bekomme ich die weg?

                    host.ioBroker
2023-06-12 22:30:52.020	error	iobroker npm-install: host.ioBroker Unknown packetName fontui. Please install packages from outside the repository using npm!
host.ioBroker
2023-06-12 22:30:43.727	error	iobroker npm-install: host.ioBroker Unknown packetName openuv. Please install packages from outside the repository using npm!

                    Da scheint irgendwas falsch installiert zu sein.

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

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

                      Wie bekomme ich die weg?

                      Das sind wohl verwaiste Adapter. Wenn die nicht benötigt werden würde ich die vor die Tür setzen.

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

                        @thomas-braun Dachte ich auch. Danke dir.
                        Haben gerade den Tritt bekommen.

                        1 Reply Last reply Reply Quote 0
                        • E
                          e-i-k-e @haselchen last edited by

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

                          @foxriver76

                          @crunchip , ich und erstmal @heinhan hatten das „VIS“ Problem.
                          Kommt da ein Fix zu ?!

                          Ich habe den Fehler bei mir auch beobachten können. Bin allerdings noch auf der letzten Alpha von js.Controller.

                          1 Reply Last reply Reply Quote 0
                          • M
                            Merlin123 last edited by Merlin123

                            Wenn ich in einem Blockly einen anderen DP auswählen will öffnet sich der Objektbaum, die Anzeige springt zum aktuellen DP und dann dreht sich nur noch der Wartekreis. Keine Chance, den DP wieder zu ändern.

                            Versuche ich einen Reload der Seite ( http://192.168.0.251:8081/#tab-javascript ) kommt erstmal ein "Webseite nicht erreichbar".
                            Muss dann so ne halbe bis ganze Minute warten, dann läd er die Seite wieder. Versuche ich den DP nochmal zu ändern gleiches Spiel.
                            Alle Adapter auf den neusten Beta Stand.

                            EDIT: Nach Downgrade auf 4.0.24 geht das wieder.

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

                              @heinhan Leider ist der Fehler heute wieder auf getaucht.

                              error: host.Iobroker cannot call visUtils: Not exi
                              M 1 Reply Last reply Reply Quote 0
                              • M
                                Marty56 @heinhan last edited by Marty56

                                Installation von js-controller 5.0.x ist möglich.
                                Allerdings kann ich diverse Adapter nicht mehr upgraden.
                                Ich bekomme die Fehlermeldung:

                                js-controller (>=2.0.0): 5.0.2
node (>=14.0.0):

                                Meine Node Versionen sind größer als 14.00

                                 node -v
v18.16.0
npm -v
9.5.1

                                Update: nach iob fix funktionierte es wieder

                                Folgende Ausfälle bei mir.

                                Yakha (V1.03)

                                host.iobroker
2023-06-13 08:11:39.286	error	instance system.adapter.yahka.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[26]: [Yahka-0 011F@Wasseralarm@Wasseralarm@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[25]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[24]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[23]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[22]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[21]: [Yahka-0 011F@nördliches Fenster K1@nördliches Fenster K1@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[20]: [Yahka-0 011F@südliche, rechte Fenster K3@südliche,rechteFenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[19]: [Yahka-0 011F@südliche, linke Fenster K3@südliche,linke Fenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[18]: [Yahka-0 011F@südliche, rechte Fenster im OG@südliche, rechte Fenster im OG@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[17]: [Yahka-0 011F@südliche, linke Fenster im OG@südliche, linke Fenster im OG@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[16]: [Yahka-0 011F@nördliches Fenster im Bad@nördliches Fenster im Bad@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[15]: [Yahka-0 011F@südliches Fenster OF@südliches Fenster OF@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.286	error	Caught by controller[14]: [Yahka-0 011F@südliches Fenster KZ@südliches Fenster KZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[13]: [Yahka-0 011F@westliches Fenster KZ@westliches Fenster KZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[12]: [Yahka-0 011F@westliches Fenster SZ@westliches Fenster SZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[11]: [Yahka-0 011F@nördliches Fenster SZ@nördliches Fenster SZ@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[10]: [Yahka-0 011F@Haustür@Haustür@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[9]: [Yahka-0 011F@Haustür@Haustür@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[8]: [Yahka-0 011F@westliche Tür@westliche Tür@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[7]: [Yahka-0 011F@westliche Tür@westliche Tür@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[6]: [Yahka-0 011F@Terrasse rechts@Terrassentür rechts@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[5]: [Yahka-0 011F@Terrasse links@Terrassentür links@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[4]: [Yahka-0 011F@Neue Post@Neue Post@On] characteristic value expected boolean and received undefined
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[4]: [Yahka-0 011F@Garage@Garage@Obstruction Detected] characteristic value expected boolean and received undefined
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[3]: [Yahka-0 011F@Lampe im Schlafzimmer@Nachttischlampe@Hue] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.285	error	Caught by controller[2]: [Yahka-0 011F@Lampe im Schlafzimmer@Nachttischlampe@Saturation] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.284	error	Caught by controller[1]: [Yahka-0 011F@Luftqual@Luftqualität@PM2.5 Density] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:39.284	error	Caught by controller[0]: [Yahka-0 011F@Justin@Justin@On] characteristic value expected boolean and received undefined

yahka.0
2023-06-13 08:11:38.555	error	Error The pattern "ObstructionDetectedObstructionDetectedObstructionDetectedObstructionDetected0_userdata.0.Garage.ObstructionDetected" is not a valid ID pattern

yahka.0
2023-06-13 08:11:38.555	error	ReplyError: Error The pattern "ObstructionDetectedObstructionDetectedObstructionDetectedObstructionDetected0_userdata.0.Garage.ObstructionDetected" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

yahka.0
2023-06-13 08:11:38.544	error	unhandled promise rejection: Error The pattern "ObstructionDetectedObstructionDetectedObstructionDetectedObstructionDetected0_userdata.0.Garage.ObstructionDetected" is not a valid ID pattern

yahka.0
2023-06-13 08:11:38.536	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().
host.iobroker
2023-06-13 08:11:05.745	error	instance system.adapter.yahka.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
2023-06-13 08:11:05.745	error	Caught by controller[26]: [Yahka-0 011F@Wasseralarm@Wasseralarm@Status Low Battery] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[25]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[24]: [Yahka-0 011F@Heizung im Kinderzimmer@KZ Heizung@Status Low Battery] characteristic value expected valid finite number and received "NaN" (number)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[23]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[22]: [Yahka-0 011F@Leuchtstreifen@Leuchtstreifen@Color Temperature] characteristic was supplied illegal value: number 0 exceeded minimum of 140
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[21]: [Yahka-0 011F@nördliches Fenster K1@nördliches Fenster K1@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[20]: [Yahka-0 011F@südliche, rechte Fenster K3@südliche,rechteFenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[19]: [Yahka-0 011F@südliche, linke Fenster K3@südliche,linke Fenster K3@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)
host.iobroker
2023-06-13 08:11:05.744	error	Caught by controller[18]: [Yahka-0 011F@südliche, rechte Fenster im OG@südliche, rechte Fenster im OG@Contact Sensor State] characteristic value expected valid finite number and received "undefined" (undefined)

                                VIS (V 1.4.16 ) Anzeige Web UI

                                File index.html not found: {}

                                Log File:

                                vis.0
2023-06-13 08:30:13.571	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

vis.0
2023-06-13 08:30:13.063	error	Not exists

vis.0
2023-06-13 08:30:13.062	error	Error: Not exists at ObjectsInRedisClient._readFile (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:856:19) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-objects-redis/build/lib/objects/objectsInRedisClient.js:893:59) at process.processImmediate (node:internal/timers:478:21)

vis.0
2023-06-13 08:30:13.061	error	unhandled promise rejection: Not exists

vis.0
2023-06-13 08:30:13.059	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().
                                apollon77 1 Reply Last reply Reply Quote 0
                                • mcm1957
                                  mcm1957 @apollon77 last edited by mcm1957

                                  @apollon77
                                  FHEM sollte auch auf die Liste der bekannten Adapterinkompatibilitäten:
                                  https://github.com/iobroker-community-adapters/ioBroker.fhem/issues/213
                                  sieht nach Problem analog zu stiebel-isg aus

                                  asmitconsulting created this issue in iobroker-community-adapters/ioBroker.fhem

                                  closed [JS-Controller5] Error after Update JS-Controller - Parameter "options" needs to be a real object... #213

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

                                    @chaot Also hier bitte web issue um die Fehler besser abzufangen und ansonsten such welches Widget mit solchen Daten hantiert weil das macht was komisches und versufht scheinbar DInge abzufragen die keine State IDs sind!! Also da ist eher in deiner Vis oder einem Widget was broken!

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

                                      @merlin123 Bitte Admin issue mit der relevanten Browser Konsole Fehlermeldung ... da müsste es eine geben

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

                                        @marty56 Bitte issue in yahka anlegen und "iob upload vis" machen. Danach ok? Auch issue in vis bitte dennich mit der Fehlermeldung

                                        M 2 Replies Last reply Reply Quote 0
                                        • ilovegym
                                          ilovegym Forum Testing @Chaot last edited by

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

                                          @apollon77
                                          Der LGTV Adapter fällt aus wie erwartet (ist aber bei mir eher unwichtig)
                                          Dazu kommt noch eine Fehlermeldung:

                                          Es gibt mittlerweile einen Fork von @basti4557 vom LG Adapter, Version 1.1.11, die funktioniert auch mit js-controller 5.x einwandfrei.
                                          https://github.com/basti4557/ioBroker.lgtvs

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

                                            @ilovegym Ist das jetzt was anderes als

                                            lgtv from https://github.com/foxriver76/ioBroker.lgtv nutzen bis Entwickler angepasst hat ?!

                                            ilovegym 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

                                            1.6k
                                            Online

                                            30.2k
                                            Users

                                            76.3k
                                            Topics

                                            1.2m
                                            Posts

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