NEWS
Problem mit Ring-Adapter
-
Da gehen mir ehrlich gesagt die Ideen aus .
Adapter Einstellung ( da die Meldung vom Adapter kommt) oder Blockly oder Skript.
Das sind die Hauptverdächtigen.Ich versuche es nochmal, vielleicht hat ja jemand noch eine Idee:
Sobald ich den Ring-Adapter starte, liefert er pausenlos Fehlermeldungen.2025-03-22 08:59:03.308 - info: ring.0 (3998066) starting. Version 6.3.0 in /opt/iobroker/node_modules/iobroker.ring, node: v20.19.0, js-controller: 7.0.6 2025-03-22 08:59:03.321 - info: ring.0 (3998066) Initializing Api Client 2025-03-22 08:59:06.715 - info: ring.0 (3998066) Received new Refresh Token. Will use the new one until the token in config gets changed 2025-03-22 08:59:13.877 - info: ring.0 (3998066) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 08:59:13.918 - info: ring.0 (3998066) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 08:59:13.920 - info: ring.0 (3998066) Get sunset and sunrise 2025-03-22 08:59:13.939 - info: ring.0 (3998066) Daily sun parameter calculation scheduled for 00:00:40 2025-03-22 08:59:15.003 - info: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob Auto save HD Snapshot starts 2025-03-22 08:59:15.004 - info: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob Auto save HD Snapshot starts 2025-03-22 08:59:20.004 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:20.005 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:25.004 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:25.005 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:30.003 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:30.004 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:35.002 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:35.002 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:40.003 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:40.004 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time!Hat vielleicht jemand noch eine Idee was da falsch läuft?
-
Ich versuche es nochmal, vielleicht hat ja jemand noch eine Idee:
Sobald ich den Ring-Adapter starte, liefert er pausenlos Fehlermeldungen.2025-03-22 08:59:03.308 - info: ring.0 (3998066) starting. Version 6.3.0 in /opt/iobroker/node_modules/iobroker.ring, node: v20.19.0, js-controller: 7.0.6 2025-03-22 08:59:03.321 - info: ring.0 (3998066) Initializing Api Client 2025-03-22 08:59:06.715 - info: ring.0 (3998066) Received new Refresh Token. Will use the new one until the token in config gets changed 2025-03-22 08:59:13.877 - info: ring.0 (3998066) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 08:59:13.918 - info: ring.0 (3998066) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 08:59:13.920 - info: ring.0 (3998066) Get sunset and sunrise 2025-03-22 08:59:13.939 - info: ring.0 (3998066) Daily sun parameter calculation scheduled for 00:00:40 2025-03-22 08:59:15.003 - info: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob Auto save HD Snapshot starts 2025-03-22 08:59:15.004 - info: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob Auto save HD Snapshot starts 2025-03-22 08:59:20.004 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:20.005 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:25.004 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:25.005 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:30.003 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:30.004 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:35.002 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:35.002 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:40.003 - warn: ring.0 (3998066) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 08:59:40.004 - warn: ring.0 (3998066) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time!Hat vielleicht jemand noch eine Idee was da falsch läuft?
-
@haselchen said in Problem mit Ring-Adapter:
Nimm hier mal bei beiden Einträgen die 5sek raus
Hab ich gemacht, danach den Adapter neu gestartet. Bringt nicht viel.
2025-03-22 13:13:27.648 - info: host.ioB-Master stopInstance system.adapter.ring.0 (force=false, process=true) 2025-03-22 13:13:27.654 - info: ring.0 (3998066) Got terminate signal TERMINATE_YOURSELF 2025-03-22 13:13:27.655 - info: ring.0 (3998066) terminating 2025-03-22 13:13:27.655 - info: ring.0 (3998066) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-22 13:13:27.781 - info: host.ioB-Master stopInstance system.adapter.ring.0 send kill signal 2025-03-22 13:13:28.156 - info: ring.0 (3998066) terminating 2025-03-22 13:13:28.782 - info: host.ioB-Master stopInstance timeout system.adapter.ring.0 killing pid 3998066 2025-03-22 13:13:28.873 - warn: host.ioB-Master instance system.adapter.ring.0 terminated due to SIGKILL 2025-03-22 13:13:28.873 - info: host.ioB-Master instance system.adapter.ring.0 terminated with code null () 2025-03-22 13:13:32.258 - info: host.ioB-Master instance system.adapter.ring.0 in version "6.3.0" started with pid 3998701 2025-03-22 13:13:33.747 - info: ring.0 (3998701) starting. Version 6.3.0 in /opt/iobroker/node_modules/iobroker.ring, node: v20.19.0, js-controller: 7.0.6 2025-03-22 13:13:33.760 - info: ring.0 (3998701) Initializing Api Client 2025-03-22 13:13:37.168 - info: ring.0 (3998701) Received new Refresh Token. Will use the new one until the token in config gets changed 2025-03-22 13:13:44.326 - info: ring.0 (3998701) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:13:44.361 - info: ring.0 (3998701) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:13:44.362 - info: ring.0 (3998701) Get sunset and sunrise 2025-03-22 13:13:44.376 - info: ring.0 (3998701) Daily sun parameter calculation scheduled for 00:00:29 2025-03-22 13:13:45.002 - info: ring.0 (3998701) Device 384912755 ("Parkplatz"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:13:45.004 - info: ring.0 (3998701) Device 213497705 ("Haustür"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:13:45.448 - info: host.ioB-Master stopInstance system.adapter.ring.0 (force=false, process=true) 2025-03-22 13:13:45.450 - info: ring.0 (3998701) Got terminate signal TERMINATE_YOURSELF 2025-03-22 13:13:45.452 - info: ring.0 (3998701) terminating 2025-03-22 13:13:45.452 - info: ring.0 (3998701) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-22 13:13:45.503 - info: host.ioB-Master stopInstance system.adapter.ring.0 send kill signal 2025-03-22 13:13:45.953 - info: ring.0 (3998701) terminating 2025-03-22 13:13:46.502 - info: host.ioB-Master stopInstance timeout system.adapter.ring.0 killing pid 3998701 2025-03-22 13:13:46.567 - warn: host.ioB-Master instance system.adapter.ring.0 terminated due to SIGKILL 2025-03-22 13:13:46.567 - info: host.ioB-Master instance system.adapter.ring.0 terminated with code null () 2025-03-22 13:13:49.955 - info: host.ioB-Master instance system.adapter.ring.0 in version "6.3.0" started with pid 3998716 2025-03-22 13:13:51.428 - info: ring.0 (3998716) starting. Version 6.3.0 in /opt/iobroker/node_modules/iobroker.ring, node: v20.19.0, js-controller: 7.0.6 2025-03-22 13:13:51.453 - info: ring.0 (3998716) Initializing Api Client 2025-03-22 13:13:54.913 - info: ring.0 (3998716) Received new Refresh Token. Will use the new one until the token in config gets changed 2025-03-22 13:14:02.024 - info: ring.0 (3998716) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:14:02.055 - info: ring.0 (3998716) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:14:02.058 - info: ring.0 (3998716) Get sunset and sunrise 2025-03-22 13:14:02.074 - info: ring.0 (3998716) Daily sun parameter calculation scheduled for 00:00:28 2025-03-22 13:14:05.004 - info: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:14:05.006 - info: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:14:10.003 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:10.004 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:15.005 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:15.006 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:20.004 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:20.006 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:25.003 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:25.003 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:30.002 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:30.003 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time!(...) 2025-03-22 13:14:02.024 - info: ring.0 (3998716) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:14:02.055 - info: ring.0 (3998716) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" (...)Da wird alle 5Min was ausgeführt oder? Könnte das damit zu tun haben?
-
@haselchen said in Problem mit Ring-Adapter:
Nimm hier mal bei beiden Einträgen die 5sek raus
Hab ich gemacht, danach den Adapter neu gestartet. Bringt nicht viel.
2025-03-22 13:13:27.648 - info: host.ioB-Master stopInstance system.adapter.ring.0 (force=false, process=true) 2025-03-22 13:13:27.654 - info: ring.0 (3998066) Got terminate signal TERMINATE_YOURSELF 2025-03-22 13:13:27.655 - info: ring.0 (3998066) terminating 2025-03-22 13:13:27.655 - info: ring.0 (3998066) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-22 13:13:27.781 - info: host.ioB-Master stopInstance system.adapter.ring.0 send kill signal 2025-03-22 13:13:28.156 - info: ring.0 (3998066) terminating 2025-03-22 13:13:28.782 - info: host.ioB-Master stopInstance timeout system.adapter.ring.0 killing pid 3998066 2025-03-22 13:13:28.873 - warn: host.ioB-Master instance system.adapter.ring.0 terminated due to SIGKILL 2025-03-22 13:13:28.873 - info: host.ioB-Master instance system.adapter.ring.0 terminated with code null () 2025-03-22 13:13:32.258 - info: host.ioB-Master instance system.adapter.ring.0 in version "6.3.0" started with pid 3998701 2025-03-22 13:13:33.747 - info: ring.0 (3998701) starting. Version 6.3.0 in /opt/iobroker/node_modules/iobroker.ring, node: v20.19.0, js-controller: 7.0.6 2025-03-22 13:13:33.760 - info: ring.0 (3998701) Initializing Api Client 2025-03-22 13:13:37.168 - info: ring.0 (3998701) Received new Refresh Token. Will use the new one until the token in config gets changed 2025-03-22 13:13:44.326 - info: ring.0 (3998701) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:13:44.361 - info: ring.0 (3998701) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:13:44.362 - info: ring.0 (3998701) Get sunset and sunrise 2025-03-22 13:13:44.376 - info: ring.0 (3998701) Daily sun parameter calculation scheduled for 00:00:29 2025-03-22 13:13:45.002 - info: ring.0 (3998701) Device 384912755 ("Parkplatz"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:13:45.004 - info: ring.0 (3998701) Device 213497705 ("Haustür"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:13:45.448 - info: host.ioB-Master stopInstance system.adapter.ring.0 (force=false, process=true) 2025-03-22 13:13:45.450 - info: ring.0 (3998701) Got terminate signal TERMINATE_YOURSELF 2025-03-22 13:13:45.452 - info: ring.0 (3998701) terminating 2025-03-22 13:13:45.452 - info: ring.0 (3998701) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-03-22 13:13:45.503 - info: host.ioB-Master stopInstance system.adapter.ring.0 send kill signal 2025-03-22 13:13:45.953 - info: ring.0 (3998701) terminating 2025-03-22 13:13:46.502 - info: host.ioB-Master stopInstance timeout system.adapter.ring.0 killing pid 3998701 2025-03-22 13:13:46.567 - warn: host.ioB-Master instance system.adapter.ring.0 terminated due to SIGKILL 2025-03-22 13:13:46.567 - info: host.ioB-Master instance system.adapter.ring.0 terminated with code null () 2025-03-22 13:13:49.955 - info: host.ioB-Master instance system.adapter.ring.0 in version "6.3.0" started with pid 3998716 2025-03-22 13:13:51.428 - info: ring.0 (3998716) starting. Version 6.3.0 in /opt/iobroker/node_modules/iobroker.ring, node: v20.19.0, js-controller: 7.0.6 2025-03-22 13:13:51.453 - info: ring.0 (3998716) Initializing Api Client 2025-03-22 13:13:54.913 - info: ring.0 (3998716) Received new Refresh Token. Will use the new one until the token in config gets changed 2025-03-22 13:14:02.024 - info: ring.0 (3998716) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:14:02.055 - info: ring.0 (3998716) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:14:02.058 - info: ring.0 (3998716) Get sunset and sunrise 2025-03-22 13:14:02.074 - info: ring.0 (3998716) Daily sun parameter calculation scheduled for 00:00:28 2025-03-22 13:14:05.004 - info: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:14:05.006 - info: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob Auto save HD Snapshot starts 2025-03-22 13:14:10.003 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:10.004 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:15.005 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:15.006 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:20.004 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:20.006 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:25.003 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:25.003 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:30.002 - warn: ring.0 (3998716) Device 213497705 ("Haustür"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time! 2025-03-22 13:14:30.003 - warn: ring.0 (3998716) Device 384912755 ("Parkplatz"): Cronjob HD Snapshot not executed because another job is already running. Please adapt timer and/or duration time!(...) 2025-03-22 13:14:02.024 - info: ring.0 (3998716) Device 213497705 ("Haustür"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" 2025-03-22 13:14:02.055 - info: ring.0 (3998716) Device 384912755 ("Parkplatz"): Create scheduled Job for HD Snapshot at "*/5 * * * * *" (...)Da wird alle 5Min was ausgeführt oder? Könnte das damit zu tun haben?
Alle 5 sek
Und das würde zu der Einstellung passen, die ich vorhin gepostet habe
Edit: woher kommt der Cronjob aus dem 2.Log?
-
@haselchen said in Problem mit Ring-Adapter:
Nimm hier mal bei beiden Einträgen die 5sek raus
Das habe ich gemacht. Sieht jetzt genauso aus wie auf deinem Screenshot.
@haselchen said in Problem mit Ring-Adapter:
Alle 5 sek
Edit: woher kommt der Cronjob aus dem 2.Log?
Ob es ein Cronjob ist, keine Ahnung. Es wird ausgeführt wenn ich den Adapter starte. Es ist in dem ersten Log auch enthalten, ich habe es im zweiten Log nur nochmal separiert.
-
@haselchen said in Problem mit Ring-Adapter:
Nimm hier mal bei beiden Einträgen die 5sek raus
Das habe ich gemacht. Sieht jetzt genauso aus wie auf deinem Screenshot.
@haselchen said in Problem mit Ring-Adapter:
Alle 5 sek
Edit: woher kommt der Cronjob aus dem 2.Log?
Ob es ein Cronjob ist, keine Ahnung. Es wird ausgeführt wenn ich den Adapter starte. Es ist in dem ersten Log auch enthalten, ich habe es im zweiten Log nur nochmal separiert.
-
Ich hole das Thema nochmal hoch. Folgendes hat sich ergeben bzw ich denke das ich den Fehler gefunden habe, benötige aber trotzdem noch etwas Hilfe:
In den Datenpunkten des Ring-Adapters finde ich den Datenpunkt history_url. wenn ich den Link aus dem DP in meinen DP einfüge den meine VIS ausliest, wird das Bild angezeigt und alles funktioniert wie es soll.Das habe ich jetzt versucht zu automatisieren:
Als Trigger erschien mit der DP des Adapters sinnvoll, wo das Datum und die Uhrzeit der letzten Aktion rein geschrieben wird.Wenn ich das so laufen lasse, bekomme ich folgende Logeinträge
ring.0 3748 2025-05-29 21:30:58.747 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(). ring.0 3748 2025-05-29 21:30:58.747 error unhandled promise rejection: Parameter "filename" needs to be of type "string" but type "undefined" has been passed ring.0 3748 2025-05-29 21:30:58.748 error Error: Parameter "filename" needs to be of type "string" but type "undefined" has been passed at Validator.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/validator.js:166:13) at RingAdapter.writeFile (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4398:32) at /opt/iobroker/node_modules/iobroker.ring/build/lib/services/file-service.js:103:21 at new Promise (<anonymous>) at FileService.writeFile (/opt/iobroker/node_modules/iobroker.ring/build/lib/services/file-service.js:89:16) at OwnRingCamera.takeSnapshot (/opt/iobroker/node_modules/iobroker.ring/build/lib/ownRingCamera.js:319:42) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async OwnRingCamera.notifyRecording (/opt/iobroker/node_modules/iobroker.ring/build/lib/ownRingCamera.js:841:51) ring.0 3748 2025-05-29 21:30:58.749 error Parameter "filename" needs to be of type "string" but type "undefined" has been passed host.ioB-Master 2025-05-29 21:30:59.320 error instance system.adapter.ring.0 terminated with code 6 (UNCAUGHT_EXCEPTION) host.ioB-Slave 2025-05-29 21:31:42.253 error instance system.adapter.daswetter.0 having pid 9609 terminated with code 15 (UNKNOWN_ERROR)Und jetzt komme ich nicht weiter... der Datenpunkt in den geschrieben wird mit dem Script ist vom Typ String.
-
Soweit ich weiss, muss man die Bilder mit dem writeFile Befehl in einen bestimmten Ordner schreiben , damit sie von der VIS akzeptiert werden (tmp Ordner z.B.)
Schon nen paar Jahre alt, aber sollte noch so stimmen (Beispielskript)
var fs = require('fs'); exec('wget --output-document /tmp/alarm5.jpg \'http://192.168.8.95:8765/picture/1/current/?_username=xxxx&_signature=ba8317b8fc071dadb725d4d0d9dbf7e606acbf1e\''); const bild = fs.readFileSync('/tmp/alarm5.jpg'); writeFile('vis.0','alarm5.jpg', bild);Edit: gibt mit Sicherheit aktuell galantere Lösungen. So habe und praktiziere ich es aktuell.
-
Soweit ich weiss, muss man die Bilder mit dem writeFile Befehl in einen bestimmten Ordner schreiben , damit sie von der VIS akzeptiert werden (tmp Ordner z.B.)
Schon nen paar Jahre alt, aber sollte noch so stimmen (Beispielskript)
var fs = require('fs'); exec('wget --output-document /tmp/alarm5.jpg \'http://192.168.8.95:8765/picture/1/current/?_username=xxxx&_signature=ba8317b8fc071dadb725d4d0d9dbf7e606acbf1e\''); const bild = fs.readFileSync('/tmp/alarm5.jpg'); writeFile('vis.0','alarm5.jpg', bild);Edit: gibt mit Sicherheit aktuell galantere Lösungen. So habe und praktiziere ich es aktuell.
@haselchen said in Problem mit Ring-Adapter:
Soweit ich weiss, muss man die Bilder mit dem writeFile Befehl in einen bestimmten Ordner schreiben , damit sie von der VIS akzeptiert werden (tmp Ordner z.B.)
Die VIS akzeptiert das Video und spielt es in Dauerschleife, so wie es sein soll. Ich kann nur die URL vom Ring-Adater nicht in meinen Datenpunkt schreiben den die VIS ausliest. Schreibe ich die URL manuell in den DP, geht es.
Es müsste jetzt nur wenn sich im Adapter der DP mit Datum und Uhrzeit ändert, die URL des aktuellen Videos aus dem DP des Adapters in den DP, den meine VIS ausliest übergeben werden.
Von welchem Typ muss der DP sein in den eine URL geschrieben wird? Bei mir ist es String. Das scheint aber ja lt. den Logs nicht ok zu sein.
-
@haselchen said in Problem mit Ring-Adapter:
Soweit ich weiss, muss man die Bilder mit dem writeFile Befehl in einen bestimmten Ordner schreiben , damit sie von der VIS akzeptiert werden (tmp Ordner z.B.)
Die VIS akzeptiert das Video und spielt es in Dauerschleife, so wie es sein soll. Ich kann nur die URL vom Ring-Adater nicht in meinen Datenpunkt schreiben den die VIS ausliest. Schreibe ich die URL manuell in den DP, geht es.
Es müsste jetzt nur wenn sich im Adapter der DP mit Datum und Uhrzeit ändert, die URL des aktuellen Videos aus dem DP des Adapters in den DP, den meine VIS ausliest übergeben werden.
Von welchem Typ muss der DP sein in den eine URL geschrieben wird? Bei mir ist es String. Das scheint aber ja lt. den Logs nicht ok zu sein.
In Deinem letzten Thread war die Rede von einem Bild….
-
In Deinem letzten Thread war die Rede von einem Bild….
@haselchen said in Problem mit Ring-Adapter:
In Deinem letzten Thread war die Rede von einem Bild….
Ich könnte jetzt antworten mit "Videos bestehen doch auch aus Bildern..." aber ok, ich habe das etwas undeutlich formuliert. Also gemeint ist das Video vom letzten Ereignis, dass dann in der Vis in Dauerschleife läuft, bis zum nächsten Ereignis.
770
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge