Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Alpha Test js-controller 5.0

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Alpha Test js-controller 5.0

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

      Hi,

      gerade den Master auf 5.0.1 angehoben:

      Web adapter crasht wegen Trashschedule fehler. Ich vermute das "ü" als Übeltäter wobei ich auch ein "ä" verwende was nicht angemeckert wird:

      0df65724-8944-467b-8a93-bb7d131b5240-grafik.png

      2023-04-11 12:21:46.870  - error: web.0 (8220) uncaught exception: The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern
2023-04-11 12:21:46.873  - error: web.0 (8220) Error: The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern
    at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2161:15)
    at pattern2RegEx (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
    at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
    at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:489:26)
    at commands.subscribe (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
    at Socket.emit (node:events:513:28)
    at /opt/iobroker/node_modules/socket.io/lib/socket.js:531:14
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
2023-04-11 12:21:46.874  - error: web.0 (8220) The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern

      Linux Control läuft nicht mehr zum steuern meiner Wandtablets

      mirko@iobroker:/opt/iobroker$ tail -f /opt/iobroker/log/iobroker.current.log |grep linux
2023-04-11 12:30:02.872  - info: host.iobroker instance system.adapter.linux-control.0 started with pid 8596
2023-04-11 12:30:07.502  - warn: linux-control.0 (8596) Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-04-11 12:30:07.503  - warn: linux-control.0 (8596) This object will not be created in future versions. Please report this to the developer.
2023-04-11 12:30:07.544  - info: linux-control.0 (8596) starting. Version 1.1.5 in /opt/iobroker/node_modules/iobroker.linux-control, node: v18.14.2, js-controller: 5.0.1-alpha.0-20230406-4552d569
2023-04-11 12:30:07.872  - warn: linux-control.0 (8596) Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
2023-04-11 12:30:07.893  - warn: linux-control.0 (8596) This object will not be created in future versions. Please report this to the developer.
2023-04-11 12:30:07.990  - info: linux-control.0 (8596) getting data from VIS-OG (192.168.178.215:22, Adapter start)
2023-04-11 12:30:08.000  - info: linux-control.0 (8596) getting data from VIS-EG (192.168.178.216:22, Adapter start)
2023-04-11 12:30:24.355  - warn: host.iobroker-Server States 127.0.0.1:33208 Error from InMemDB: Error: The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern
2023-04-11 12:30:24.359  - error: linux-control.0 (8596) 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().
2023-04-11 12:30:24.360  - error: linux-control.0 (8596) unhandled promise rejection: Error The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern
2023-04-11 12:30:24.361  - error: linux-control.0 (8596) ReplyError: Error The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern
2023-04-11 12:30:24.361  - error: linux-control.0 (8596) Error The pattern "linux-control.0.VIS-OG.services.●.restart" is not a valid ID pattern
2023-04-11 12:30:24.380  - info: linux-control.0 (8596) cleaned everything up...
2023-04-11 12:30:24.381  - info: linux-control.0 (8596) terminating
2023-04-11 12:30:24.381  - warn: linux-control.0 (8596) Terminated (UNCAUGHT_EXCEPTION): Without reason
2023-04-11 12:30:24.385  - error: linux-control.0 (8596) 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().
2023-04-11 12:30:24.386  - error: linux-control.0 (8596) unhandled promise rejection: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern
2023-04-11 12:30:24.387  - error: linux-control.0 (8596) Error: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern
2023-04-11 12:30:24.387  - error: linux-control.0 (8596) The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern
2023-04-11 12:30:24.401  - warn: host.iobroker-Server States 127.0.0.1:33208 Error from InMemDB: Error: The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.404  - error: linux-control.0 (8596) 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().
2023-04-11 12:30:24.404  - error: linux-control.0 (8596) unhandled promise rejection: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.405  - error: linux-control.0 (8596) ReplyError: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.405  - error: linux-control.0 (8596) Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.736  - error: linux-control.0 (8596) 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().
2023-04-11 12:30:24.737  - error: linux-control.0 (8596) unhandled promise rejection: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern
2023-04-11 12:30:24.737  - error: linux-control.0 (8596) Error: The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern
2023-04-11 12:30:24.737  - error: linux-control.0 (8596) The pattern "io.linux-control.0.VIS-OG.services.●.start" is not a valid ID pattern
2023-04-11 12:30:24.783  - warn: host.iobroker-Server States 127.0.0.1:33208 Error from InMemDB: Error: The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.792  - error: linux-control.0 (8596) 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().
2023-04-11 12:30:24.792  - error: linux-control.0 (8596) unhandled promise rejection: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.793  - error: linux-control.0 (8596) ReplyError: Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.793  - error: linux-control.0 (8596) Error The pattern "linux-control.0.VIS-OG.services.●.stop" is not a valid ID pattern
2023-04-11 12:30:24.888  - info: linux-control.0 (8596) terminating
2023-04-11 12:30:24.900  - warn: linux-control.0 (8596) get state error: Connection is closed.
2023-04-11 12:30:24.907  - error: linux-control.0 (8596) [servicesInfo] VIS-OG (192.168.178.215:22): error: DB closed, stack: Error: DB closed
2023-04-11 12:30:25.038  - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): datapoint-id: VIS_OG_ScreenOff, description: ViS-OG_ScreenOff
2023-04-11 12:30:25.039  - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): error: DB closed, stack: Error: DB closed
2023-04-11 12:30:25.041  - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): datapoint-id: VIS_OG_ScreenOn, description: VIS-OG_ScreenOn
2023-04-11 12:30:25.042  - error: linux-control.0 (8596) [userCommandExecute] VIS-OG (192.168.178.215:22): error: DB closed, stack: Error: DB closed
2023-04-11 12:30:25.494  - error: host.iobroker instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2023-04-11 12:30:25.502  - info: host.iobroker Restart adapter system.adapter.linux-control.0 because enabled

      Nehme an es liegt an dem "dicken" Punkt im Namen und ist ein Adapter issue, oder?

      Enigma 2 Adapter läuft nicht mehr:

      mirko@iobroker:/opt/iobroker$ tail -f /opt/iobroker/log/iobroker.current.log |grep enigma
2023-04-11 12:36:12.099  - info: host.iobroker instance system.adapter.enigma2.0 started with pid 8762
2023-04-11 12:36:12.802  - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js
2023-04-11 12:36:12.802  - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/main.js
2023-04-11 12:36:12.802  - error: host.iobroker Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js:46:25)
2023-04-11 12:36:12.805  - error: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js',
2023-04-11 12:36:12.805  - error: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.enigma2/main.js'
2023-04-11 12:36:12.805  - error: host.iobroker instance system.adapter.enigma2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2023-04-11 12:36:12.812  - info: host.iobroker Rebuild for adapter system.adapter.enigma2.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.
2023-04-11 12:36:28.124  - info: host.iobroker "system.adapter.enigma2.0" disabled
2023-04-11 12:36:34.443  - info: host.iobroker "system.adapter.enigma2.0" enabled
2023-04-11 12:36:34.613  - info: host.iobroker instance system.adapter.enigma2.0 started with pid 8775
2023-04-11 12:36:36.424  - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js
2023-04-11 12:36:36.425  - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/main.js
2023-04-11 12:36:36.425  - error: host.iobroker Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js:46:25)
2023-04-11 12:36:36.426  - error: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js',
2023-04-11 12:36:36.426  - error: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.enigma2/main.js'
2023-04-11 12:36:36.426  - error: host.iobroker instance system.adapter.enigma2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2023-04-11 12:36:36.426  - info: host.iobroker Rebuild for adapter system.adapter.enigma2.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.

      EDIT: Ergänzung zum Enigma2 Adapter:

      2023-04-11 12:48:29.329  - info: trashschedule.0 (10113) [ical] configurured ical preview is 34 days - increase this value to find more events in the future
2023-04-11 12:48:46.571  - info: host.iobroker iobroker npm-rebuild: rebuilt dependencies successfully
2023-04-11 12:48:46.776  - info: host.iobroker iobroker npm-rebuild: Rebuilding native modules done
2023-04-11 12:48:47.781  - info: host.iobroker iobroker npm-rebuild: exit 0
2023-04-11 12:48:47.972  - info: host.iobroker instance system.adapter.enigma2.0 started with pid 10173
2023-04-11 12:48:49.184  - error: host.iobroker Caught by controller[0]: node:internal/modules/cjs/loader:1078
2023-04-11 12:48:49.184  - error: host.iobroker Caught by controller[0]:   throw err;
2023-04-11 12:48:49.184  - error: host.iobroker Caught by controller[0]:   ^
2023-04-11 12:48:49.184  - error: host.iobroker Caught by controller[0]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js'
2023-04-11 12:48:49.184  - error: host.iobroker Caught by controller[0]: Require stack:
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]: - /opt/iobroker/node_modules/iobroker.enigma2/main.js
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:920:27)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1141:19)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at require (node:internal/modules/cjs/helpers:110:18)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js:46:25)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module._compile (node:internal/modules/cjs/loader:1254:14)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module.load (node:internal/modules/cjs/loader:1117:32)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module._load (node:internal/modules/cjs/loader:958:12)
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:     at Module.require (node:internal/modules/cjs/loader:1141:19) {
2023-04-11 12:48:49.185  - error: host.iobroker Caught by controller[0]:   code: 'MODULE_NOT_FOUND',
2023-04-11 12:48:49.186  - error: host.iobroker Caught by controller[0]:   requireStack: [
2023-04-11 12:48:49.186  - error: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.enigma2/lib/utils.js',
2023-04-11 12:48:49.186  - error: host.iobroker Caught by controller[0]:     '/opt/iobroker/node_modules/iobroker.enigma2/main.js'
2023-04-11 12:48:49.186  - error: host.iobroker Caught by controller[0]:   ]
2023-04-11 12:48:49.186  - error: host.iobroker Caught by controller[0]: }
2023-04-11 12:48:49.186  - error: host.iobroker Caught by controller[0]: Node.js v18.14.2
2023-04-11 12:48:49.186  - error: host.iobroker instance system.adapter.enigma2.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2023-04-11 12:48:49.186  - info: host.iobroker Adapter system.adapter.enigma2.0 needs rebuild and will be restarted afterwards.
2023-04-11 12:48:49.186  - info: host.iobroker system.adapter.enigma2.0 will be rebuilt
2023-04-11 12:48:49.186  - warn: host.iobroker adapter "enigma2" seems to be installed for a different version of Node.js. Trying to rebuild it... 3 attempt
2023-04-11 12:48:49.187  - info: host.iobroker iobroker rebuild
2023-04-11 12:48:52.129  - info: host.iobroker iobroker npm-rebuild: Rebuilding native modules ...
      foxriver76 1 Reply Last reply Reply Quote 0
      • foxriver76
        foxriver76 Developer @wendy2702 last edited by

        @wendy2702 Legt Trashschedule wirklich States mit Umlauten an? Sollte eigentlich nicht möglich sein und entsprechend sollte der Adapter auch den subscribe entsprechend anpassen.

        Die anderen beiden sind sicher Adapter Issues.

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

          @foxriver76 Ja, legt der Adapter an:

          d3ef4127-808a-4a75-ae01-bc67e84d9b67-grafik.png

          Zum Enigma2 Adapter: habe den zum testen mal komplett gelöscht, also Instanz und Adapter. Jetzt kann ich ihn nicht mehr installieren:

          2023-04-11 12:54:08.072  - info: host.iobroker iobroker add enigma2 auto --host iobroker --debug
2023-04-11 12:54:11.281  - error: host.iobroker iobroker host.iobroker Unknown packetName enigma2. Please install packages from outside the repository using npm!
2023-04-11 12:54:12.335  - info: host.iobroker iobroker exit 12

          EDIT: OK, der hing wohl noch im Cache in der Anzeige der verfügbaren Adapter.

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

            @wendy2702 enigma2 ist nicht im offiziellen Repo

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

              @foxriver76 Ja, ist mir dann auch wieder auf/eingefallen.

              Komplette neu installation leider auch erfolglos. Da, der Adapter wenn ich das richtig sehe nicht mehr gepflegt wird, es hier doch einige User gibt sollte man eventuell einen Hinweis geben oder bin ich der einzige bei dem er mit Controller V5 nicht mehr läuft ?

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

                @wendy2702

                Arbeit am Adapter enigma2 abgebrochen. Projekt Übernehmer gesucht!

                Sieht sehr eindeutig nach verwaist aus.

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

                  @wendy2702 Wird bei keinem laufen, lässt sich relativ einfach fixen. Habe gesehen dass nicht gepflegt, wäre gut wenn der damalige Entwickler den Adapter wie vorgeschlagen in community-adapters übergibt.

                  Ok, Umlaute sind tatsächlich nicht verboten, entsprechend sollte Pattern auch nicht meckern bei einem richtigen ü. Allerdings scheint der Adapter dein ü als ü zu speichern, evtl Encoding-Problem beim Speichern der Daten vom Frontend. Damit auch Adapter Fehler.

                  Enigma 2 kann ich vorbereiten, allerdings muss der Dev mergen.

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

                    @foxriver76 OK.

                    Und was genau heisst das jetzt für den Trashschedule Adapter?

                    foxriver76 3 Replies Last reply Reply Quote 0
                    • foxriver76
                      foxriver76 Developer @wendy2702 last edited by

                      @wendy2702 Issue anlegen bitte

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

                        @wendy2702 Probier gerne mal Enigma von folgender URL: https://github.com/foxriver76/ioBroker.enigma2

                        PR ist gestellt: https://github.com/Matten-Matten/ioBroker.enigma2/pull/63

                        foxriver76 created this issue in Matten-Matten/ioBroker.enigma2

                        closed make adapter v5 compatible #63

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

                          Edit: ne doch issue erstellen 😉

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

                            @foxriver76 sagte in Alpha Test js-controller 5.0:

                            https://github.com/foxriver76/ioBroker.enigma2

                            Dein PR ist gemerged und der Adapter läuft mit JS 5.0.1

                            Bin gestern zurück auf JS 4.0.24 und jetzt wieder auf 5.0.1.

                            EDIT: Trashschedule Fehler ist noch vorhanden, zeigt sich aber heute Hartnäckig.

                            Nachdem das entfernen der Umlaute nicht geholfen hat, habe ich die Trashschedule Instanz gestoppt.

                            Alle Objekte gelöscht

                            989751ce-5484-406c-a302-9323645df0fa-grafik.png

                            aber der WEB Adapter meckert immer noch:

                            2023-04-12 09:53:28.585  - error: web.0 (32727) uncaught exception: The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern
2023-04-12 09:53:28.586  - error: web.0 (32727) Error: The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern
    at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:2161:15)
    at pattern2RegEx (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/adapter-core/build/controllerTools.js:94:44)
    at SocketCommands.subscribe (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:267:13)
    at SocketCommands._subscribeStates (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:489:26)
    at commands.subscribe (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1356:25)
    at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.socketio/node_modules/@iobroker/socket-classes/lib/socketCommands.js:1556:43)
    at Socket.emit (node:events:513:28)
    at /opt/iobroker/node_modules/socket.io/lib/socket.js:531:14
    at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
2023-04-12 09:53:28.587  - error: web.0 (32727) The pattern "trashschedule.0.type.Restmüll.daysleft" is not a valid ID pattern
                            foxriver76 1 Reply Last reply Reply Quote 0
                            • foxriver76
                              foxriver76 Developer @wendy2702 last edited by foxriver76

                              @wendy2702 ah das war ja nicht von trashschedule selbst sondern von web. Dann kommts vermutlich von vis oder web direkt.

                              Bitte bei web Issue anlegen.

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

                                @foxriver76 Das Problem lag am Ende scheinbar daran das in VIS Widgets nach dem Upgrade auf JS5.0.1 das hier z.B. drin steht bzw. er das anmeckert.

                                Zeile  87403:           "color": "{wert:trashschedule.0.type.Restmüll.daysleft; wert<2 ? \"#ff0000\" :: wert == 2 ? \"#f3f60e\" :: \"#ffffff\"}",
                                foxriver76 1 Reply Last reply Reply Quote 0
                                • foxriver76
                                  foxriver76 Developer @wendy2702 last edited by

                                  @wendy2702 ah perfekt dass du es gefunden hast. Funktioniert es mit einem ü nicht oder warum der Escape?

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

                                    @foxriver76 Da stand eigentlich bis zu irgendeinem Upgrade ein "ü" welches dann nach Upgrade von was auch immer von alleine in das "ü" geändert.

                                    Habe jetzt in Trashschedule und in den Widgets erstmal das "ü" und das "ü" mit "ue" ersetzt.

                                    Muss mal testen ob es auch funktioniert wenn überall wieder das "ü" steht.

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

                                      Hallo alle zusammen,

                                      ich habe soeben die Alpha Version vom js-controller 5 aktualisiert.

                                      Changelog 5.0.1-alpha.0-20230418-efa3e809

                                      • Fixed issue with certificate validity on leap years
                                      • Backup fixed (Fixed wrong return type on db level for readFile promisified)
                                      • Remove windows bat files completely, installer will create them when needed
                                      • Respect dns resolution (ipv4/ipv6 first) from config internally and provide relevant methods via adapter-core - I theory a ipv6 only iobroker in a ipv6 only network is possible with this!

                                      Adapter mit bekannten Problemen hinzugefügt:

                                      • fitbit-fitness
                                      • enigma2 (GitHub version fixed)
                                      Gaspode ? Feuersturm Rene55 4 Replies Last reply Reply Quote 3
                                      • Gaspode
                                        Gaspode @apollon77 last edited by

                                        @apollon77
                                        Keine Auffälligkeiten, keine Fehler im Log File.
                                        Die alten Windows bat Files wurden beim Update gelöscht.

                                        1 Reply Last reply Reply Quote 1
                                        • ?
                                          A Former User @apollon77 last edited by

                                          @apollon77

                                          Hello,
                                          laeuft hier wunderbar, das Backup geht wieder, super!

                                          Der Fitbit-Adapter hatte damals (mit der letzten Alpha) einen Schluckauf, jetzt einwandfrei gestartet... konnte den Fehler nicht mehr nach vollziehen..

                                          Genauso hatte ich nicht nachvollziehbare Phänomene mit dem Tuya Adapter.. ich behalts im Auge, wenn ich was nachvollziehen kann, gibts n Issue mit Debuglog..

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

                                            @apollon77 sagte in Alpha Test js-controller 5.0:

                                            ich habe soeben die Alpha Version vom js-controller 5 aktualisiert.
                                            Changelog 5.0.1-alpha.0-20230418-efa3e809

                                            Master Slave System erfolgreich aktualisiert und keine Auffälligkeiten im Log 🙂

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            798
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            25
                                            140
                                            15007
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo