Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • 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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

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

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.3k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.4k

js-controller 5.0.x jetzt in der BETA

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
580 Beiträge 71 Kommentatoren 196.7k Aufrufe 67 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • 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
    schrieb am zuletzt editiert von
    #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 Antwort Letzte Antwort
    0
    • FeuersturmF Online
      FeuersturmF Online
      Feuersturm
      schrieb am zuletzt editiert von 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 Antwort Letzte Antwort
      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
        schrieb am zuletzt editiert von
        #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 Antwort Letzte Antwort
        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
          schrieb am zuletzt editiert von
          #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 Antwort Letzte Antwort
          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
            schrieb am zuletzt editiert von 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 Antwort Letzte Antwort
            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
              schrieb am zuletzt editiert von
              #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 Antwort Letzte Antwort
              1
              • FeuersturmF Online
                FeuersturmF Online
                Feuersturm
                schrieb am zuletzt editiert von
                #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 Antwort Letzte Antwort
                0
                • MalleRalleM Offline
                  MalleRalleM Offline
                  MalleRalle
                  schrieb am zuletzt editiert von
                  #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 Antworten Letzte Antwort
                  0
                  • MalleRalleM MalleRalle

                    @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 Offline
                    foxriver76F Offline
                    foxriver76
                    Developer
                    schrieb am zuletzt editiert von
                    #230

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

                    Videotutorials & mehr

                    Hier könnt ihr mich unterstützen.

                    F 1 Antwort Letzte Antwort
                    1
                    • E Einstein67

                      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 Offline
                      foxriver76F Offline
                      foxriver76
                      Developer
                      schrieb am zuletzt editiert von
                      #231

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

                      Videotutorials & mehr

                      Hier könnt ihr mich unterstützen.

                      1 Antwort Letzte Antwort
                      1
                      • FeuersturmF Feuersturm

                        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 Offline
                        apollon77A Offline
                        apollon77
                        schrieb am zuletzt editiert von
                        #232

                        @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

                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                        FeuersturmF 1 Antwort Letzte Antwort
                        0
                        • apollon77A apollon77

                          @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

                          FeuersturmF Online
                          FeuersturmF Online
                          Feuersturm
                          schrieb am zuletzt editiert von
                          #233

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

                          1 Antwort Letzte Antwort
                          0
                          • MalleRalleM MalleRalle

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

                            F Offline
                            F Offline
                            fastfoot
                            schrieb am zuletzt editiert von
                            #234

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

                            iobroker läuft unter Docker auf QNAP TS-451+
                            SkriptRecovery: https://forum.iobroker.net/post/930558

                            1 Antwort Letzte Antwort
                            0
                            • foxriver76F foxriver76

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

                              F Offline
                              F Offline
                              fastfoot
                              schrieb am zuletzt editiert von
                              #235

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

                              iobroker läuft unter Docker auf QNAP TS-451+
                              SkriptRecovery: https://forum.iobroker.net/post/930558

                              1 Antwort Letzte Antwort
                              0
                              • ChaotC Offline
                                ChaotC Offline
                                Chaot
                                schrieb am zuletzt editiert von Chaot
                                #236

                                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
                                

                                ioBroker auf NUC unter Proxmox; VIS: 12" Touchscreen und 17" Touch; Lichtsteuerung, Thermometer und Sensoren: Tasmota (39); Ambiente Beleuchtung: WLED (9); Heizung: DECT Thermostate (9) an Fritz 6690; EMS-ESP; 1 Echo V2; 3 Echo DOT; 1 Echo Connect; 2 Echo Show 5; Unifi Ap-Ac Lite.

                                foxriver76F 1 Antwort Letzte Antwort
                                0
                                • ChaotC 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
                                  
                                  foxriver76F Offline
                                  foxriver76F Offline
                                  foxriver76
                                  Developer
                                  schrieb am zuletzt editiert von
                                  #237

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

                                  Videotutorials & mehr

                                  Hier könnt ihr mich unterstützen.

                                  FeuersturmF ChaotC apollon77A 4 Antworten Letzte Antwort
                                  1
                                  • foxriver76F foxriver76

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

                                    FeuersturmF Online
                                    FeuersturmF Online
                                    Feuersturm
                                    schrieb am zuletzt editiert von
                                    #238

                                    @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 Antwort Letzte Antwort
                                    0
                                    • foxriver76F Offline
                                      foxriver76F Offline
                                      foxriver76
                                      Developer
                                      schrieb am zuletzt editiert von
                                      #239

                                      @feuersturm Ja bitte gg

                                      Videotutorials & mehr

                                      Hier könnt ihr mich unterstützen.

                                      1 Antwort Letzte Antwort
                                      0
                                      • foxriver76F foxriver76

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

                                        ChaotC Offline
                                        ChaotC Offline
                                        Chaot
                                        schrieb am zuletzt editiert von
                                        #240

                                        @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)}
                                        

                                        ioBroker auf NUC unter Proxmox; VIS: 12" Touchscreen und 17" Touch; Lichtsteuerung, Thermometer und Sensoren: Tasmota (39); Ambiente Beleuchtung: WLED (9); Heizung: DECT Thermostate (9) an Fritz 6690; EMS-ESP; 1 Echo V2; 3 Echo DOT; 1 Echo Connect; 2 Echo Show 5; Unifi Ap-Ac Lite.

                                        mcm1957M 1 Antwort Letzte Antwort
                                        0
                                        • ChaotC Chaot

                                          @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)}
                                          
                                          mcm1957M Online
                                          mcm1957M Online
                                          mcm1957
                                          schrieb am zuletzt editiert von
                                          #241

                                          @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

                                          Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                                          Support Repositoryverwaltung.

                                          Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                                          LESEN - gute Forenbeitrage

                                          1 Antwort Letzte Antwort
                                          1
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          513

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe