Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Skripten / Logik
    4. JavaScript
    5. javaskript variablen monitoren

    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

    javaskript variablen monitoren

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

      Hallo, wenn ich über creatobject eine Variable angelegt habe, dann kann ich diese ja über die objekte einsehen.
      Gibt es auch eine Möglichkeit die internen lokalen Variablen zur Laufzeit des Skripts zu beobachten?

      Ich habe eine Schrittkette programmiert und würde gerne den aktuellen Status einsehen, während diese durchlaufen wird.

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

        @ben1983 Dafür gibts den Debugger:
        a8dfa6a7-1b39-40c4-b8eb-f69a56aca2fd-grafik.png

        Ben1983 1 Reply Last reply Reply Quote 0
        • Ben1983
          Ben1983 @AlCalzone last edited by

          @alcalzone Wenn ich das anklicke, wird das skript gestoppt und es läuft oben nur ein balken durch und es steht dort skript läuft nicht. Mehr passiert nicht.

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

            @ben1983 Welcher Browser? Irgendein Fehler in der Browserkonsole?

            Ben1983 AlCalzone 2 Replies Last reply Reply Quote 0
            • Ben1983
              Ben1983 @AlCalzone last edited by

              @alcalzone Chrome
              4353879d-4a04-4376-9d0c-6cd900613581-image.png

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

                @alcalzone sagte in javaskript variablen monitoren:

                Irgendein Fehler in der Browserkonsole?

                👆

                Ben1983 T 2 Replies Last reply Reply Quote 0
                • Ben1983
                  Ben1983 @AlCalzone last edited by

                  @alcalzone nein kein fehler

                  1 Reply Last reply Reply Quote 0
                  • T
                    ticaki Developer @AlCalzone last edited by

                    @alcalzone
                    Bei mir geht das ebenfalls nicht. Ich bekomme jedoch folgende Fehlermeldungen im Log:

                    2021-07-18 16:21:09.815 - error: javascript.0 (25154) uncaught exception: Cannot call write after a stream was destroyed
                    2021-07-18 16:21:09.816 - error: javascript.0 (25154) Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
                    at doWrite (_stream_writable.js:399:19)
                    at writeOrBuffer (_stream_writable.js:387:5)
                    at Socket.Writable.write (_stream_writable.js:318:11)
                    at Console.log (/opt/iobroker/node_modules/winston/lib/winston/transports/console.js:79:23)
                    at Console._write (/opt/iobroker/node_modules/winston-transport/index.js:103:17)
                    at doWrite (/opt/iobroker/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:428:64)
                    at writeOrBuffer (/opt/iobroker/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:417:5)
                    at Console.Writable.write (/opt/iobroker/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:334:11)
                    at DerivedLogger.ondata (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:681:20)
                    at DerivedLogger.emit (events.js:326:22)
                    at DerivedLogger.EventEmitter.emit (domain.js:483:12)
                    at addChunk (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:298:12)
                    at readableAddChunk (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:280:11)
                    at DerivedLogger.Readable.push (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_readable.js:241:10)
                    at DerivedLogger.Transform.push (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:139:32)
                    at DerivedLogger._transform (/opt/iobroker/node_modules/winston/lib/winston/logger.js:305:12)
                    at DerivedLogger.Transform._read (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:177:10)
                    at DerivedLogger.Transform._write (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_transform.js:164:83)
                    at doWrite (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:409:139)
                    at writeOrBuffer (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:398:5)
                    at DerivedLogger.Writable.write (/opt/iobroker/node_modules/winston/node_modules/readable-stream/lib/_stream_writable.js:307:11)
                    at DerivedLogger. [as info] (/opt/iobroker/node_modules/winston/lib/winston/create-logger.js:81:14)
                    at Log.info (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:123:21)
                    at prepareScript (/opt/iobroker/node_modules/iobroker.javascript/main.js:1709:25)
                    at /opt/iobroker/node_modules/iobroker.javascript/main.js:1817:17
                    at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.javascript/main.js:1306:17)
                    at processImmediate (internal/timers.js:463:21)
                    2021-07-18 16:21:09.817 - error: javascript.0 (25154) Exception-Code: ERR_STREAM_DESTROYED: Cannot call write after a stream was destroyed
                    

                    Dann ein paar Startmeldungen von Skripten und anschließend:

                    2021-07-18 16:21:10.645 - error: host.tims-pi1 Caught by controller[1]: Runtime.executionContextCreated: =>
                    2021-07-18 16:21:10.651 - error: host.tims-pi1 Caught by controller[1]: {
                    2021-07-18 16:21:10.651 - error: host.tims-pi1 Caught by controller[1]: "context": {
                    2021-07-18 16:21:10.651 - error: host.tims-pi1 Caught by controller[1]: "id": 1,
                    2021-07-18 16:21:10.652 - error: host.tims-pi1 Caught by controller[1]: "origin": "",
                    2021-07-18 16:21:10.652 - error: host.tims-pi1 Caught by controller[1]: "name": "/usr/bin/node[25154]",
                    2021-07-18 16:21:10.652 - error: host.tims-pi1 Caught by controller[1]: "auxData": {
                    2021-07-18 16:21:10.653 - error: host.tims-pi1 Caught by controller[1]: "isDefault": true
                    2021-07-18 16:21:10.653 - error: host.tims-pi1 Caught by controller[1]: }
                    2021-07-18 16:21:10.653 - error: host.tims-pi1 Caught by controller[1]: }
                    2021-07-18 16:21:10.654 - error: host.tims-pi1 Caught by controller[1]: }
                    2021-07-18 16:21:10.654 - error: host.tims-pi1 Caught by controller[2]: Runtime.executionContextCreated: =>
                    2021-07-18 16:21:10.655 - error: host.tims-pi1 Caught by controller[2]: {
                    2021-07-18 16:21:10.655 - error: host.tims-pi1 Caught by controller[2]: "context": {
                    2021-07-18 16:21:10.655 - error: host.tims-pi1 Caught by controller[2]: "id": 2,
                    2021-07-18 16:21:10.655 - error: host.tims-pi1 Caught by controller[2]: "origin": "",
                    2021-07-18 16:21:10.656 - error: host.tims-pi1 Caught by controller[2]: "name": "VM Context 1",
                    2021-07-18 16:21:10.656 - error: host.tims-pi1 Caught by controller[2]: "auxData": {
                    2021-07-18 16:21:10.656 - error: host.tims-pi1 Caught by controller[2]: "isDefault": false
                    2021-07-18 16:21:10.656 - error: host.tims-pi1 Caught by controller[2]: }
                    2021-07-18 16:21:10.657 - error: host.tims-pi1 Caught by controller[2]: }
                    2021-07-18 16:21:10.657 - error: host.tims-pi1 Caught by controller[2]: }
                    2021-07-18 16:21:10.657 - error: host.tims-pi1 Caught by controller[3]: ReferenceError: stats is not defined
                    2021-07-18 16:21:10.658 - error: host.tims-pi1 Caught by controller[3]: at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:482:59)
                    2021-07-18 16:21:10.658 - error: host.tims-pi1 Caught by controller[3]: at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5706:41)
                    2021-07-18 16:21:10.658 - error: host.tims-pi1 Caught by controller[3]: at processImmediate (internal/timers.js:461:21)
                    2021-07-18 16:21:10.659 - error: host.tims-pi1 instance system.adapter.javascript.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                    2021-07-18 16:21:10.659 - info: host.tims-pi1 Restart adapter system.adapter.javascript.0 because enabled
                    
                    1 Reply Last reply Reply Quote 0
                    • AlCalzone
                      AlCalzone Developer last edited by

                      Hmm, dann macht doch bitte mal ein Issue in https://github.com/ioBroker/ioBroker.javascript auf, damit man sich das anschauen kann.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post

                      Support us

                      ioBroker
                      Community Adapters
                      Donate

                      842
                      Online

                      31.8k
                      Users

                      80.0k
                      Topics

                      1.3m
                      Posts

                      3
                      9
                      278
                      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