Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 5.0.x jetzt in der BETA

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.9k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    913

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.2k

js-controller 5.0.x jetzt in der BETA

Scheduled Pinned Locked Moved ioBroker Allgemein
580 Posts 71 Posters 206.9k Views 67 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Sandy

    Hallo

    Also bei mir zeigen nach dem Update alle Wetter Instanzen eine Warnung an.

    Gruss Sandy

    Screenshot 2023-06-16 092713.jpg

    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    wrote on last edited by
    #210

    @sandy

    Kann es sein, dass 'daswetter' ein Scheduled-Adapter ist und der einfach nur im eingestellten Intervall startet?

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    S sigi234S 2 Replies Last reply
    0
    • Thomas BraunT Thomas Braun

      @sandy

      Kann es sein, dass 'daswetter' ein Scheduled-Adapter ist und der einfach nur im eingestellten Intervall startet?

      S Offline
      S Offline
      Sandy
      wrote on last edited by
      #211

      @thomas-braun da kenne ich mich leider nicht so mit aus :-(

      Thomas BraunT 1 Reply Last reply
      0
      • Thomas BraunT Thomas Braun

        @sandy

        Kann es sein, dass 'daswetter' ein Scheduled-Adapter ist und der einfach nur im eingestellten Intervall startet?

        sigi234S Online
        sigi234S Online
        sigi234
        Forum Testing Most Active
        wrote on last edited by
        #212

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

        Kann es sein, dass 'daswetter' ein Scheduled-Adapter ist und der einfach nur im eingestellten Intervall startet?

        Jupp

        Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
        Immer Daten sichern!

        S 1 Reply Last reply
        0
        • sigi234S sigi234

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

          Kann es sein, dass 'daswetter' ein Scheduled-Adapter ist und der einfach nur im eingestellten Intervall startet?

          Jupp

          S Offline
          S Offline
          Sandy
          wrote on last edited by
          #213

          @sigi234 was kann ich denn dagegen machen ?

          M sigi234S 2 Replies Last reply
          0
          • S Sandy

            @thomas-braun da kenne ich mich leider nicht so mit aus :-(

            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            wrote on last edited by
            #214

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

            da kenne ich mich leider nicht so mit aus

            Aber mit Beta-Zeug herummachen.
            Wenig sinnig.

            was kann ich denn dagegen machen ?

            Nichts, das ist so richtig und soll so sein.

            Linux-Werkzeugkasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
            NodeJS Fixer Skript:
            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

            1 Reply Last reply
            0
            • Thomas BraunT Thomas Braun

              Upgrade von 5.0.3 auf 5.0.4 über GUI hat bei mir funktioniert.
              Wollte ich nur mal verkünden.

              M Offline
              M Offline
              Monger71
              wrote on last edited by Monger71
              #215

              @thomas-braun
              Bei mir klappt es noch nicht. Wird zwar angezeigt, dass 5.0.4 verfügbar ist (im Info-Bereich), bei Host, steht eine (1), dort steht noch, dass nur 5.0.3 verfügbar und auch installiert ist. (Linux-Umgebung)

              Denke mal, dass es aus dem Host-Bereich installierbar sein sollte, oder?

              Nebenbei ist mir gerade noch aufgefallen, dass auch ein Adapter als hochrüstbar gemeldet wurde, das Update aber auch nicht in der Adapter-Liste angezeigt wurde. War Discovery 3.1.0 => 3.2.0. Per Konsole ging es.

              5.0.4 war übrigens dann auch per Konsole möglich..

              1 Reply Last reply
              0
              • S Sandy

                @sigi234 was kann ich denn dagegen machen ?

                M Offline
                M Offline
                Marty56
                wrote on last edited by
                #216

                @sandy die Log Stufe des Adapters auf "Error" stellen.

                HW:NUC (16 GB Ram)
                OS: Debian Bullseye, Promox V7, node v16.x npm 8.19.3

                B 1 Reply Last reply
                2
                • M Marty56

                  @sandy die Log Stufe des Adapters auf "Error" stellen.

                  B Do not disturb
                  B Do not disturb
                  bommel_030
                  wrote on last edited by
                  #217

                  @marty56
                  Kann das js-controller Update den "Wert" der Meldung von "info" auf "warn" geändert haben? Die Meldungen hatte ich vor dem Update nicht im LOG und die Warnstufe der Adapter habe ich erst danach auf Error gestellt.

                  foxriver76F 1 Reply Last reply
                  0
                  • B bommel_030

                    @marty56
                    Kann das js-controller Update den "Wert" der Meldung von "info" auf "warn" geändert haben? Die Meldungen hatte ich vor dem Update nicht im LOG und die Warnstufe der Adapter habe ich erst danach auf Error gestellt.

                    foxriver76F Offline
                    foxriver76F Offline
                    foxriver76
                    Developer
                    wrote on last edited by foxriver76
                    #218

                    @bommel_030 Ja, unabsichtlich, wenn der Adapter eine eigene Begründung zum Terminate angegeben hat, danke fürs Melden - wird gefixt sein in nächster Version

                    Videotutorials & mehr

                    Hier könnt ihr mich unterstützen.

                    B 1 Reply Last reply
                    3
                    • foxriver76F foxriver76

                      @bommel_030 Ja, unabsichtlich, wenn der Adapter eine eigene Begründung zum Terminate angegeben hat, danke fürs Melden - wird gefixt sein in nächster Version

                      B Do not disturb
                      B Do not disturb
                      bommel_030
                      wrote on last edited by
                      #219

                      @foxriver76
                      Ich meine irgendwo gelesen zu haben, die "alias-subscription-errors" sollten mit der 5er Version auch behoben sein (Finde die passende Stelle gerade nicht).
                      Da sich einer meiner Shellies verabschiedet hab musste ich in einem Skript das einen Alias steuert den Trigger anpassen.
                      Das hat mir >48 "alias-subscription-errors" ins LOG gehauen. Die funktionieren seit jeher einwandfrei und sind in dem Skript auch nicht eingebunden.

                      foxriver76F 1 Reply Last reply
                      0
                      • B bommel_030

                        @foxriver76
                        Ich meine irgendwo gelesen zu haben, die "alias-subscription-errors" sollten mit der 5er Version auch behoben sein (Finde die passende Stelle gerade nicht).
                        Da sich einer meiner Shellies verabschiedet hab musste ich in einem Skript das einen Alias steuert den Trigger anpassen.
                        Das hat mir >48 "alias-subscription-errors" ins LOG gehauen. Die funktionieren seit jeher einwandfrei und sind in dem Skript auch nicht eingebunden.

                        foxriver76F Offline
                        foxriver76F Offline
                        foxriver76
                        Developer
                        wrote on last edited by
                        #220

                        @bommel_030 Es wurde geschrieben, dass sie villt. behoben sind. Wurde allerdings leider bereits verneint.

                        Videotutorials & mehr

                        Hier könnt ihr mich unterstützen.

                        1 Reply Last reply
                        0
                        • S Sandy

                          @sigi234 was kann ich denn dagegen machen ?

                          sigi234S Online
                          sigi234S Online
                          sigi234
                          Forum Testing Most Active
                          wrote on last edited by
                          #221

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

                          @sigi234 was kann ich denn dagegen machen ?

                          Nix, ist nur eine Warnung

                          Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                          Immer Daten sichern!

                          E 1 Reply Last reply
                          0
                          • sigi234S sigi234

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

                            @sigi234 was kann ich denn dagegen machen ?

                            Nix, ist nur eine Warnung

                            E Offline
                            E Offline
                            Einstein67
                            wrote on last edited by
                            #222

                            Ich hab den neuen Controller nun ein paar Tage am laufen. Läuft sehr gut und schnell.

                            Das einzige das mir aufgefallen ist, dass ich keine Zigbee Geräte mehr löschen kann.

                            Bei Zigbee-Adapter 1.8.10 hab ich nichts geändert. Beim löschen passiert folgendes:

                            2023-06-16 15:18:01.567 - info: admin.0 (339) ==> Connected system.user.admin from ::ffff:192.168.0.26
                            2023-06-16 15:18:01.795 - info: zigbee.0 (1881) List of port: [{"path":"/dev/ttyUSB0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS10"},{"path":"/dev/ttyS11"},{"path":"/dev/ttyS12"},{"path":"/dev/ttyS13"},{"path":"/dev/ttyS14"},{"path":"/dev/ttyS15"},{"path":"/dev/ttyS16"},{"path":"/dev/ttyS17"},{"path":"/dev/ttyS18"},{"path":"/dev/ttyS19"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS20"},{"path":"/dev/ttyS21"},{"path":"/dev/ttyS22"},{"path":"/dev/ttyS23"},{"path":"/dev/ttyS24"},{"path":"/dev/ttyS25"},{"path":"/dev/ttyS26"},{"path":"/dev/ttyS27"},{"path":"/dev/ttyS28"},{"path":"/dev/ttyS29"},{"path":"/dev/ttyS3"},{"path":"/dev/ttyS30"},{"path":"/dev/ttyS31"},{"path":"/dev/ttyS4"},{"path":"/dev/ttyS5"},{"path":"/dev/ttyS6"},{"path":"/dev/ttyS7"},{"path":"/dev/ttyS8"},{"path":"/dev/ttyS9"},{"path":"/dev/ttyS0"}]
                            2023-06-16 15:18:12.680 - error: zigbee.0 (1881) uncaught exception: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed
                            2023-06-16 15:18:12.686 - error: zigbee.0 (1881) Error: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed
                            at Function.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:241:19)
                            at Zigbee.deleteState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5793:19)
                            at /opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:314:34
                            at Array.forEach ()
                            at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:313:24)
                            at processImmediate (node:internal/timers:478:21)
                            2023-06-16 15:18:12.686 - error: zigbee.0 (1881) Parameter "parentChannel" needs to be of type "string" but type "object" has been passed
                            2023-06-16 15:18:12.710 - info: zigbee.0 (1881) cleaned everything up...
                            2023-06-16 15:18:12.721 - info: zigbee.0 (1881) Zigbee: disabling joining new devices.
                            2023-06-16 15:18:12.914 - error: host.iob18 Caught by controller[0]: Error: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed
                            2023-06-16 15:18:12.915 - error: host.iob18 Caught by controller[0]: at Function.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:241:19)
                            2023-06-16 15:18:12.915 - error: host.iob18 Caught by controller[0]: at Zigbee.deleteState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5793:19)
                            2023-06-16 15:18:12.915 - error: host.iob18 Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:314:34
                            2023-06-16 15:18:12.915 - error: host.iob18 Caught by controller[0]: at Array.forEach ()
                            2023-06-16 15:18:12.915 - error: host.iob18 Caught by controller[0]: at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:313:24)
                            2023-06-16 15:18:12.915 - error: host.iob18 Caught by controller[0]: at processImmediate (node:internal/timers:478:21)
                            2023-06-16 15:18:12.915 - error: host.iob18 instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                            2023-06-16 15:18:12.915 - info: host.iob18 Restart adapter system.adapter.zigbee.0 because enabled
                            2023-06-16 15:18:42.990 - info: host.iob18 instance system.adapter.zigbee.0 started with pid 1904
                            

                            Ist das ein Problem des Zigbee Adapters oder des Controllers? Wie schon geschrieben wurde nur der Controller aktualisiert ....

                            foxriver76F 1 Reply Last reply
                            0
                            • FeuersturmF Online
                              FeuersturmF Online
                              Feuersturm
                              wrote on last edited by Feuersturm
                              #223

                              @foxriver76 @apollon77
                              Ich habe gerade mein ioBroker Master auf js-controller 5.0.4 aktualisiert.
                              Wenn ich jetzt meine vis1 starte kommen folgend Meldungen im Log

                              2023-06-16 20:11:38.257 - error: web.0 (7732) uncaught exception: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                              2023-06-16 20:11:38.260 - error: web.0 (7732) Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" 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:489:26)
                              at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                              at Socket. (/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 ()
                              at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                              at processImmediate (node:internal/timers:476:21)
                              2023-06-16 20:11:38.262 - error: web.0 (7732) The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                              2023-06-16 20:11:38.907 - error: host.ioBrokerTestsystem Caught by controller[0]: URIError: URI malformed
                              2023-06-16 20:11:38.912 - error: host.ioBrokerTestsystem Caught by controller[0]: at decodeURI ()
                              2023-06-16 20:11:38.914 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.web/main.js:1718:31
                              2023-06-16 20:11:38.916 - error: host.ioBrokerTestsystem Caught by controller[0]: at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
                              2023-06-16 20:11:38.917 - error: host.ioBrokerTestsystem Caught by controller[0]: at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)
                              2023-06-16 20:11:38.920 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/express/lib/router/index.js:286:9
                              2023-06-16 20:11:38.921 - error: host.ioBrokerTestsystem Caught by controller[0]: at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)
                              2023-06-16 20:11:38.922 - error: host.ioBrokerTestsystem Caught by controller[0]: at next (/opt/iobroker/node_modules/express/lib/router/index.js:280:10)
                              2023-06-16 20:11:38.924 - error: host.ioBrokerTestsystem Caught by controller[0]: at getSocketIoFile (/opt/iobroker/node_modules/iobroker.web/main.js:1105:9)
                              2023-06-16 20:11:38.925 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.web/main.js:1260:44
                              2023-06-16 20:11:38.926 - error: host.ioBrokerTestsystem Caught by controller[0]: at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
                              2023-06-16 20:11:38.927 - error: host.ioBrokerTestsystem Caught by controller[1]: Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                              2023-06-16 20:11:38.928 - error: host.ioBrokerTestsystem Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
                              2023-06-16 20:11:38.929 - error: host.ioBrokerTestsystem Caught by controller[1]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
                              2023-06-16 20:11:38.931 - error: host.ioBrokerTestsystem Caught by controller[1]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
                              2023-06-16 20:11:38.932 - error: host.ioBrokerTestsystem Caught by controller[1]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:489:26)
                              2023-06-16 20:11:38.933 - error: host.ioBrokerTestsystem Caught by controller[1]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                              2023-06-16 20:11:38.934 - error: host.ioBrokerTestsystem Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
                              2023-06-16 20:11:38.935 - error: host.ioBrokerTestsystem Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100
                              2023-06-16 20:11:38.936 - error: host.ioBrokerTestsystem Caught by controller[1]: at Array.forEach ()
                              2023-06-16 20:11:38.938 - error: host.ioBrokerTestsystem Caught by controller[1]: at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                              2023-06-16 20:11:38.939 - error: host.ioBrokerTestsystem Caught by controller[1]: at processImmediate (node:internal/timers:476:21)
                              2023-06-16 20:11:38.940 - error: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                              2023-06-16 20:11:38.942 - info: host.ioBrokerTestsystem Restart adapter system.adapter.web.0 because enabled
                              2023-06-16 20:12:09.206 - info: host.ioBrokerTestsystem instance system.adapter.web.0 started with pid 8152
                              2023-06-16 20:12:13.598 - info: web.0 (8152) starting. Version 5.5.3 in /opt/iobroker/node_modules/iobroker.web, node: v18.16.0, js-controller: 5.0.4
                              2023-06-16 20:12:13.886 - warn: web.0 (8152) Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                              2023-06-16 20:12:13.998 - info: web.0 (8152) socket.io server listening on port 8082
                              2023-06-16 20:12:14.014 - info: web.0 (8152) http server listening on port 8082
                              2023-06-16 20:12:15.658 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                              2023-06-16 20:12:15.910 - info: web.0 (8152) <== Disconnect system.user.admin from 192.168.178.20
                              2023-06-16 20:12:16.434 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                              2023-06-16 20:12:17.644 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                              2023-06-16 20:12:17.803 - info: web.0 (8152) <== Disconnect system.user.admin from 192.168.178.20
                              2023-06-16 20:12:18.466 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                              2023-06-16 20:12:19.700 - warn: web.0 (8152) Alias alias.0.testobjekte.Temperatur.ACTUAL has no target 12
                              2023-06-16 20:12:20.146 - error: web.0 (8152) uncaught exception: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                              2023-06-16 20:12:20.148 - error: web.0 (8152) Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" 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:489:26)
                              at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                              at Socket. (/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 ()
                              at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                              at processImmediate (node:internal/timers:476:21)
                              2023-06-16 20:12:20.150 - error: web.0 (8152) The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                              2023-06-16 20:12:20.683 - error: host.ioBrokerTestsystem Caught by controller[0]: Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                              2023-06-16 20:12:20.686 - error: host.ioBrokerTestsystem Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
                              2023-06-16 20:12:20.687 - error: host.ioBrokerTestsystem Caught by controller[0]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
                              2023-06-16 20:12:20.688 - error: host.ioBrokerTestsystem Caught by controller[0]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
                              2023-06-16 20:12:20.689 - error: host.ioBrokerTestsystem Caught by controller[0]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:489:26)
                              2023-06-16 20:12:20.690 - error: host.ioBrokerTestsystem Caught by controller[0]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                              2023-06-16 20:12:20.692 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
                              2023-06-16 20:12:20.693 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100
                              2023-06-16 20:12:20.694 - error: host.ioBrokerTestsystem Caught by controller[0]: at Array.forEach ()
                              2023-06-16 20:12:20.695 - error: host.ioBrokerTestsystem Caught by controller[0]: at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                              2023-06-16 20:12:20.696 - error: host.ioBrokerTestsystem Caught by controller[0]: at processImmediate (node:internal/timers:476:21)
                              2023-06-16 20:12:20.698 - error: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                              2023-06-16 20:12:20.699 - info: host.ioBrokerTestsystem Restart adapter system.adapter.web.0 because enabled
                              

                              In meiner VIS habe ich bei bei einem icon folgendes Binding hinterlegt {val:javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow": " "}
                              93ec8d89-f5e2-4558-b248-9d68cad51556-grafik.png

                              Im Reiter CSS ist folgendes eingetragen

                              /* -----
                                 glow
                                 ----- */
                              .mdui-red-glow {
                                filter: drop-shadow(0px 0px 2px #F44336) drop-shadow(0px 0px 2px #F44336) drop-shadow(0px 0px 4px #F44336);
                              }
                              

                              Ob der Fehler auch mit einer früheren 5.x Alpha Version bereits auftritt müsste ich nachstellen wenn es hilft.

                              Edit: Issue beim web. Adapter angelegt: https://github.com/ioBroker/ioBroker.web/issues/316

                              foxriver76F 1 Reply Last reply
                              0
                              • FeuersturmF Feuersturm

                                @foxriver76 @apollon77
                                Ich habe gerade mein ioBroker Master auf js-controller 5.0.4 aktualisiert.
                                Wenn ich jetzt meine vis1 starte kommen folgend Meldungen im Log

                                2023-06-16 20:11:38.257 - error: web.0 (7732) uncaught exception: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                                2023-06-16 20:11:38.260 - error: web.0 (7732) Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" 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:489:26)
                                at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                                at Socket. (/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 ()
                                at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                                at processImmediate (node:internal/timers:476:21)
                                2023-06-16 20:11:38.262 - error: web.0 (7732) The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                                2023-06-16 20:11:38.907 - error: host.ioBrokerTestsystem Caught by controller[0]: URIError: URI malformed
                                2023-06-16 20:11:38.912 - error: host.ioBrokerTestsystem Caught by controller[0]: at decodeURI ()
                                2023-06-16 20:11:38.914 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.web/main.js:1718:31
                                2023-06-16 20:11:38.916 - error: host.ioBrokerTestsystem Caught by controller[0]: at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
                                2023-06-16 20:11:38.917 - error: host.ioBrokerTestsystem Caught by controller[0]: at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)
                                2023-06-16 20:11:38.920 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/express/lib/router/index.js:286:9
                                2023-06-16 20:11:38.921 - error: host.ioBrokerTestsystem Caught by controller[0]: at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)
                                2023-06-16 20:11:38.922 - error: host.ioBrokerTestsystem Caught by controller[0]: at next (/opt/iobroker/node_modules/express/lib/router/index.js:280:10)
                                2023-06-16 20:11:38.924 - error: host.ioBrokerTestsystem Caught by controller[0]: at getSocketIoFile (/opt/iobroker/node_modules/iobroker.web/main.js:1105:9)
                                2023-06-16 20:11:38.925 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.web/main.js:1260:44
                                2023-06-16 20:11:38.926 - error: host.ioBrokerTestsystem Caught by controller[0]: at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
                                2023-06-16 20:11:38.927 - error: host.ioBrokerTestsystem Caught by controller[1]: Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                                2023-06-16 20:11:38.928 - error: host.ioBrokerTestsystem Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
                                2023-06-16 20:11:38.929 - error: host.ioBrokerTestsystem Caught by controller[1]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
                                2023-06-16 20:11:38.931 - error: host.ioBrokerTestsystem Caught by controller[1]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
                                2023-06-16 20:11:38.932 - error: host.ioBrokerTestsystem Caught by controller[1]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:489:26)
                                2023-06-16 20:11:38.933 - error: host.ioBrokerTestsystem Caught by controller[1]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                                2023-06-16 20:11:38.934 - error: host.ioBrokerTestsystem Caught by controller[1]: at Socket. (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
                                2023-06-16 20:11:38.935 - error: host.ioBrokerTestsystem Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100
                                2023-06-16 20:11:38.936 - error: host.ioBrokerTestsystem Caught by controller[1]: at Array.forEach ()
                                2023-06-16 20:11:38.938 - error: host.ioBrokerTestsystem Caught by controller[1]: at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                                2023-06-16 20:11:38.939 - error: host.ioBrokerTestsystem Caught by controller[1]: at processImmediate (node:internal/timers:476:21)
                                2023-06-16 20:11:38.940 - error: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                2023-06-16 20:11:38.942 - info: host.ioBrokerTestsystem Restart adapter system.adapter.web.0 because enabled
                                2023-06-16 20:12:09.206 - info: host.ioBrokerTestsystem instance system.adapter.web.0 started with pid 8152
                                2023-06-16 20:12:13.598 - info: web.0 (8152) starting. Version 5.5.3 in /opt/iobroker/node_modules/iobroker.web, node: v18.16.0, js-controller: 5.0.4
                                2023-06-16 20:12:13.886 - warn: web.0 (8152) Information for Developer: Using the direct "Let's encrypt" module import is deprecated and will be removed in the next js-controller version, use @iobroker/webserver instead
                                2023-06-16 20:12:13.998 - info: web.0 (8152) socket.io server listening on port 8082
                                2023-06-16 20:12:14.014 - info: web.0 (8152) http server listening on port 8082
                                2023-06-16 20:12:15.658 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                                2023-06-16 20:12:15.910 - info: web.0 (8152) <== Disconnect system.user.admin from 192.168.178.20
                                2023-06-16 20:12:16.434 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                                2023-06-16 20:12:17.644 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                                2023-06-16 20:12:17.803 - info: web.0 (8152) <== Disconnect system.user.admin from 192.168.178.20
                                2023-06-16 20:12:18.466 - info: web.0 (8152) ==> Connected system.user.admin from 192.168.178.20
                                2023-06-16 20:12:19.700 - warn: web.0 (8152) Alias alias.0.testobjekte.Temperatur.ACTUAL has no target 12
                                2023-06-16 20:12:20.146 - error: web.0 (8152) uncaught exception: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                                2023-06-16 20:12:20.148 - error: web.0 (8152) Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" 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:489:26)
                                at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                                at Socket. (/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 ()
                                at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                                at processImmediate (node:internal/timers:476:21)
                                2023-06-16 20:12:20.150 - error: web.0 (8152) The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                                2023-06-16 20:12:20.683 - error: host.ioBrokerTestsystem Caught by controller[0]: Error: The pattern "javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow"" is not a valid ID pattern
                                2023-06-16 20:12:20.686 - error: host.ioBrokerTestsystem Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
                                2023-06-16 20:12:20.687 - error: host.ioBrokerTestsystem Caught by controller[0]: at pattern2RegEx (/opt/iobroker/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
                                2023-06-16 20:12:20.688 - error: host.ioBrokerTestsystem Caught by controller[0]: at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
                                2023-06-16 20:12:20.689 - error: host.ioBrokerTestsystem Caught by controller[0]: at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:489:26)
                                2023-06-16 20:12:20.690 - error: host.ioBrokerTestsystem Caught by controller[0]: at Object.commands.subscribe (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
                                2023-06-16 20:12:20.692 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/iobroker.ws/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
                                2023-06-16 20:12:20.693 - error: host.ioBrokerTestsystem Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:100
                                2023-06-16 20:12:20.694 - error: host.ioBrokerTestsystem Caught by controller[0]: at Array.forEach ()
                                2023-06-16 20:12:20.695 - error: host.ioBrokerTestsystem Caught by controller[0]: at Immediate. (/opt/iobroker/node_modules/@iobroker/ws-server/index.js:152:83)
                                2023-06-16 20:12:20.696 - error: host.ioBrokerTestsystem Caught by controller[0]: at processImmediate (node:internal/timers:476:21)
                                2023-06-16 20:12:20.698 - error: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                2023-06-16 20:12:20.699 - info: host.ioBrokerTestsystem Restart adapter system.adapter.web.0 because enabled
                                

                                In meiner VIS habe ich bei bei einem icon folgendes Binding hinterlegt {val:javascript.0.Google_Maps.nach_Hause_x.Staustufe_0>"0"? "mdui-red-glow": " "}
                                93ec8d89-f5e2-4558-b248-9d68cad51556-grafik.png

                                Im Reiter CSS ist folgendes eingetragen

                                /* -----
                                   glow
                                   ----- */
                                .mdui-red-glow {
                                  filter: drop-shadow(0px 0px 2px #F44336) drop-shadow(0px 0px 2px #F44336) drop-shadow(0px 0px 4px #F44336);
                                }
                                

                                Ob der Fehler auch mit einer früheren 5.x Alpha Version bereits auftritt müsste ich nachstellen wenn es hilft.

                                Edit: Issue beim web. Adapter angelegt: https://github.com/ioBroker/ioBroker.web/issues/316

                                foxriver76F Offline
                                foxriver76F Offline
                                foxriver76
                                Developer
                                wrote on last edited by
                                #224

                                @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.

                                Videotutorials & mehr

                                Hier könnt ihr mich unterstützen.

                                FeuersturmF 1 Reply Last reply
                                0
                                • foxriver76F foxriver76

                                  @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.

                                  FeuersturmF Online
                                  FeuersturmF Online
                                  Feuersturm
                                  wrote on last edited by
                                  #225

                                  @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?

                                  foxriver76F 1 Reply Last reply
                                  0
                                  • FeuersturmF Feuersturm

                                    @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?

                                    foxriver76F Offline
                                    foxriver76F Offline
                                    foxriver76
                                    Developer
                                    wrote on last edited by foxriver76
                                    #226

                                    @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": ""}

                                    Videotutorials & mehr

                                    Hier könnt ihr mich unterstützen.

                                    FeuersturmF 1 Reply Last reply
                                    2
                                    • foxriver76F 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": ""}

                                      FeuersturmF Online
                                      FeuersturmF Online
                                      Feuersturm
                                      wrote on last edited by
                                      #227

                                      @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
                                      1
                                      • FeuersturmF Online
                                        FeuersturmF Online
                                        Feuersturm
                                        wrote on last edited by
                                        #228

                                        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.

                                        apollon77A 1 Reply Last reply
                                        0
                                        • MalleRalleM Offline
                                          MalleRalleM Offline
                                          MalleRalle
                                          wrote on last edited by
                                          #229

                                          @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?

                                          foxriver76F F 2 Replies Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          514

                                          Online

                                          32.6k

                                          Users

                                          82.2k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe