Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Entwicklung
    4. [Neuer Adapter] Reolink Kamera

    NEWS

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    [Neuer Adapter] Reolink Kamera

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

      Hallo Zusammen,
      ich habe jetzt wieder etwas mehr Zeit um mich mit der Adapter-Entwicklung zu beschäftigen.
      @oelison hat ja schon viel entwickelt und integriert. VIELEN DANK dafür.

      Dazu habe ich jetzt einen neuen minor release veröffentlicht (0.1.0). Dabei wurde der Code etwas aufgeräumt, optimiert und ein paar gewünschte Funktionen integriert:

      • added getAutoFocus funktion
      • beim Start, prüft Status von Autofocus
      • added getIrLight funktion
      • beim Start, prüft Status von IR Licht
      • added getWhiteLED function
      • beim Start, prüft Status von LEDs
      • added getMailNotification function & setMailNotification function
      • beim Start, Ein- bzw. Ausschalten der Mail Benachrichtigung

      Falls eure Kamera eine der Funktionen nicht unterstützen sollte, wird im Datenpunkt "Error or not supported" angezeigt.

      Falls Ihr noch Wünsche habt oder Verbesserungsvorschläge, melde euch.
      Ich bin jetzt wieder mehr aktiv.

      Danke & viele Grüße
      aendue

      H da_Woody 2 Replies Last reply Reply Quote 1
      • H
        Hansi1234 @Andy Grundt last edited by

        @andy-grundt super, dass der Adapter so viel Interesse weckt. Kommst du an den Motion Trigger heran? Also, wenn Bewegung, dann Datenpunkt true?

        Andy Grundt 1 Reply Last reply Reply Quote 0
        • Andy Grundt
          Andy Grundt Developer @Hansi1234 last edited by

          @hansi1234 Motion Detection wird schon gelesen. Findest du unter: reolink.0.sensor.motion

          H 1 Reply Last reply Reply Quote 0
          • H
            Hansi1234 @Andy Grundt last edited by

            @andy-grundt ah funktioniert das? Geht auch Mensch, Fahrzeug , Tiererkennung?

            Andy Grundt 1 Reply Last reply Reply Quote 0
            • da_Woody
              da_Woody @Andy Grundt last edited by

              @andy-grundt autsch, hab über git die neue version eingespielt.
              e002def6-267d-404f-bd19-867697bc58c6-grafik.png

              host.ioBroker
2022-10-25 19:47:34.662	warn	Do not restart adapter system.adapter.reolink.0 because restart loop detected
host.ioBroker
2022-10-25 19:47:34.662	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.0
2022-10-25 19:47:33.970	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 19:47:33.968	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:47:33.968	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 19:47:33.968	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:47:33.967	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().
host.ioBroker
2022-10-25 19:47:02.266	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.0
2022-10-25 19:47:01.628	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 19:47:01.626	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:47:01.625	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 19:47:01.625	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:47:01.624	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().
host.ioBroker
2022-10-25 19:46:39.189	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.0
2022-10-25 19:46:38.565	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 19:46:38.556	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:46:38.556	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 19:46:38.555	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:46:38.554	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().
host.ioBroker
2022-10-25 19:46:31.252	warn	Do not restart adapter system.adapter.reolink.2 because restart loop detected
host.ioBroker
2022-10-25 19:46:31.251	error	instance system.adapter.reolink.2 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker
2022-10-25 19:46:30.973	warn	Do not restart adapter system.adapter.reolink.1 because restart loop detected
host.ioBroker
2022-10-25 19:46:30.973	error	instance system.adapter.reolink.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker
2022-10-25 19:46:30.807	warn	Do not restart adapter system.adapter.reolink.0 because restart loop detected
host.ioBroker
2022-10-25 19:46:30.807	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.2
2022-10-25 19:46:30.379	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.2
2022-10-25 19:46:30.360	error	Cannot read properties of null (reading 'val')

reolink.2
2022-10-25 19:46:30.360	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.2
2022-10-25 19:46:30.359	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.2
2022-10-25 19:46:30.355	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().

reolink.1
2022-10-25 19:46:30.318	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.1
2022-10-25 19:46:30.288	error	Cannot read properties of null (reading 'val')

reolink.1
2022-10-25 19:46:30.281	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.1
2022-10-25 19:46:30.272	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.1
2022-10-25 19:46:30.267	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().

reolink.0
2022-10-25 19:46:30.182	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 19:46:30.151	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:46:30.151	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 19:46:30.150	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:46:30.148	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().
host.ioBroker
2022-10-25 19:45:55.574	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker
2022-10-25 19:45:55.345	error	instance system.adapter.reolink.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker
2022-10-25 19:45:55.186	error	instance system.adapter.reolink.2 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.0
2022-10-25 19:45:54.772	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 19:45:54.766	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:45:54.766	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 19:45:54.765	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 19:45:54.764	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().

reolink.1
2022-10-25 19:45:54.665	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.1
2022-10-25 19:45:54.631	error	Cannot read properties of null (reading 'val')

reolink.1
2022-10-25 19:45:54.631	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.1
2022-10-25 19:45:54.630	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.1
2022-10-25 19:45:54.629	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().

reolink.2
2022-10-25 19:45:54.550	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.2
2022-10-25 19:45:54.526	error	Cannot read properties of null (reading 'val')

reolink.2
2022-10-25 19:45:54.523	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.2
2022-10-25 19:45:54.522	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.2
2022-10-25 19:45:54.518	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().
host.ioBroker
2022-10-25 19:45:20.651	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker
2022-10-25 19:45:20.547	error	instance system.adapter.reolink.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.ioBroker
2022-10-25 19:45:20.251	error	instance system.adapter.reolink.2 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.1
2022-10-25 19:45:19.913	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 19:45:19.910	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.1
2022-10-25 19:45:19.895	error	Cannot read properties of null (reading 'val')
              Andy Grundt 1 Reply Last reply Reply Quote 0
              • Andy Grundt
                Andy Grundt Developer @Hansi1234 last edited by

                @hansi1234 ja das funktioniert. Warum sollte es auch nicht, wenn wir es einbauen.
                Allerdings muss der Status von der Kamera abgefragt werden (Polling). Push funktioniert leider nicht. (Bei Push würde sich die Kamera melden)
                Wenn die Kamera ein Objekt erkennt, hat diese den Status für 30 Sekunden. Im Adapter kannst du die Abfragezeit einstellen. Default ist 10s.

                Zurzeit ist es ein allgemeiner Status von allen 3 (Mensch, Auto, Tier)

                1 Reply Last reply Reply Quote 0
                • Andy Grundt
                  Andy Grundt Developer @da_Woody last edited by Andy Grundt

                  @da_woody Kannst du mal auf debug stellen und dann nochmal die Fehlermeldung zuschicken?

                  EDIT: Fehler in GetAutoFocus Funktion gefunden. Bitte nochmal neu von GitHub installieren.

                  da_Woody 1 Reply Last reply Reply Quote 1
                  • da_Woody
                    da_Woody @Andy Grundt last edited by

                    @andy-grundt alle instanzen gestoppt, update,
                    3422dbb7-a303-4729-85ca-e83c4f74e533-grafik.png

                    host.ioBroker
2022-10-25 20:11:56.768	warn	Do not restart adapter system.adapter.reolink.0 because restart loop detected
host.ioBroker
2022-10-25 20:11:56.768	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.0
2022-10-25 20:11:56.074	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 20:11:56.061	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 20:11:56.061	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 20:11:56.061	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 20:11:56.060	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().
host.ioBroker
2022-10-25 20:11:23.963	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.0
2022-10-25 20:11:23.354	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 20:11:23.347	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 20:11:23.347	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 20:11:23.346	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 20:11:23.345	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().
host.ioBroker
2022-10-25 20:10:51.498	error	instance system.adapter.reolink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

reolink.0
2022-10-25 20:10:50.867	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

reolink.0
2022-10-25 20:10:50.860	error	Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 20:10:50.859	error	TypeError: Cannot read properties of null (reading 'val') at ReoLinkCam.onReady (/opt/iobroker/node_modules/iobroker.reolink/main.js:67:36)

reolink.0
2022-10-25 20:10:50.859	error	unhandled promise rejection: Cannot read properties of null (reading 'val')

reolink.0
2022-10-25 20:10:50.858	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().
                    Andy Grundt 1 Reply Last reply Reply Quote 0
                    • Andy Grundt
                      Andy Grundt Developer @da_Woody last edited by

                      @da_woody Ich habe jetzt mal die Autofokus Funktion deaktiviert. Leider habe ich keine Kamera mit Autofokus und daher konnte ich das nicht testen. Bitte lade dir in 10 min nochmal die aktuelle Version von GitHub.

                      Danke

                      da_Woody 1 Reply Last reply Reply Quote 0
                      • da_Woody
                        da_Woody @Andy Grundt last edited by

                        @andy-grundt mach ich morgen. bin heute erledigt und muß die hufe hochlagern... 🙂
                        ist ja kein stress. mit der vorigen war alles noch grün...

                        Andy Grundt 1 Reply Last reply Reply Quote -1
                        • Andy Grundt
                          Andy Grundt Developer @da_Woody last edited by

                          @da_woody OK, geb dann bitte nochmal bescheid! Danke

                          da_Woody 1 Reply Last reply Reply Quote 1
                          • da_Woody
                            da_Woody @Andy Grundt last edited by da_Woody

                            @andy-grundt moin! 🙂 gerade noch mal drübergespielt, jetzt wurde reolink.0 grün. die beiden anderen instanzen gestartet, auch beide grün.
                            log:

                            
reolink.2
2022-10-26 06:16:19.517	warn	Read-only state "reolink.2.disc.mounted" has been written without ack-flag with value "false"

reolink.2
2022-10-26 06:16:19.471	warn	Read-only state "reolink.2.disc.free" has been written without ack-flag with value "0"

reolink.2
2022-10-26 06:16:19.424	warn	Read-only state "reolink.2.disc.formatted" has been written without ack-flag with value "false"

reolink.2
2022-10-26 06:16:19.413	warn	Read-only state "reolink.2.disc.capacity" has been written without ack-flag with value "0"

reolink.1
2022-10-26 06:16:12.548	warn	Read-only state "reolink.1.disc.mounted" has been written without ack-flag with value "false"

reolink.1
2022-10-26 06:16:12.492	warn	Read-only state "reolink.1.disc.free" has been written without ack-flag with value "0"

reolink.1
2022-10-26 06:16:12.435	warn	Read-only state "reolink.1.disc.formatted" has been written without ack-flag with value "false"

reolink.1
2022-10-26 06:16:12.386	warn	Read-only state "reolink.1.disc.capacity" has been written without ack-flag with value "0"

reolink.0
2022-10-26 06:15:45.925	warn	Read-only state "reolink.0.disc.mounted" has been written without ack-flag with value "false"

reolink.0
2022-10-26 06:15:45.878	warn	Read-only state "reolink.0.disc.free" has been written without ack-flag with value "0"

reolink.0
2022-10-26 06:15:45.833	warn	Read-only state "reolink.0.disc.formatted" has been written without ack-flag with value "false"

reolink.0
2022-10-26 06:15:45.784	warn	Read-only state "reolink.0.disc.capacity" has been written without ack-flag with value "0"

                            hatte gestern auch bei Hosts eine fehlermeldung. da stand was von "restart loop endeckt" leider keinen screenshot gemacht.

                            Andy Grundt 2 Replies Last reply Reply Quote 0
                            • Andy Grundt
                              Andy Grundt Developer @da_Woody last edited by

                              @da_woody Danke...falls du noch was findest, sagt beschied.

                              da_Woody 1 Reply Last reply Reply Quote 0
                              • da_Woody
                                da_Woody @Andy Grundt last edited by

                                @andy-grundt gerne, wenn ich zeit habe und verschiedene dingens probiere. ich verwende die meisten adapter nur rudimentär, also ohne irgend welche benachrichtigungen. so gesehn verwende ich auch keine bewegundmeldungen und sonstiges.
                                kann dir also nur berichten, ob eine neue version nicht tut... 🙂

                                I 1 Reply Last reply Reply Quote 0
                                • I
                                  Idefix01 @da_Woody last edited by

                                  Hallöchen, ich habe es in der Vis mit folgendem Link eingefügt und es funktioniert einwandfrei.

                                  https://IP-der-Kamera/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=wuuPhkmUCeI9WG 7C&user=Benutzername&password=Password&width=1920&height=1080

                                  1 Reply Last reply Reply Quote 0
                                  • Andy Grundt
                                    Andy Grundt Developer @da_Woody last edited by

                                    @da_woody
                                    Das schreiben der Datenpunkte ohne ack-flag wurde auch behoben. Sollte jetzt nicht mehr im log auftauchen.

                                    da_Woody 1 Reply Last reply Reply Quote 0
                                    • da_Woody
                                      da_Woody @Andy Grundt last edited by

                                      @andy-grundt hüstel... nach nem update über den link hats mächtig geraschelt. hab dann mal alle 3 instanzen, die grün waren gestoppt, log gelöscht, die 0 gestartet:

                                      
reolink.0
2022-10-28 13:54:54.672	error	DB closed

reolink.0
2022-10-28 13:54:54.671	error	Error: DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:657:40) at ReoLinkCam.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5880:35)

reolink.0
2022-10-28 13:54:54.670	error	unhandled promise rejection: DB closed

reolink.0
2022-10-28 13:54:54.670	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().

reolink.0
2022-10-28 13:54:54.670	warn	get state error: Connection is closed.

reolink.0
2022-10-28 13:54:54.553	warn	get state error: DB closed

reolink.0
2022-10-28 13:54:53.430	error	Value not supported!

reolink.0
2022-10-28 13:54:53.217	error	Value not supported!

reolink.0
2022-10-28 13:54:52.936	error	Value not supported!

reolink.0
2022-10-28 13:54:52.708	error	Value not supported!

reolink.0
2022-10-28 13:54:52.475	error	Value not supported!

reolink.0
2022-10-28 13:54:52.346	error	Value not supported!

reolink.0
2022-10-28 13:54:52.220	error	Value not supported!

reolink.0
2022-10-28 13:54:52.094	error	Value not supported!

reolink.0
2022-10-28 13:54:51.982	error	Value not supported!

reolink.0
2022-10-28 13:54:51.836	error	Value not supported!

reolink.0
2022-10-28 13:54:51.700	error	Value not supported!

reolink.0
2022-10-28 13:54:51.569	error	Value not supported!

reolink.0
2022-10-28 13:54:51.443	error	Value not supported!

reolink.0
2022-10-28 13:54:51.293	error	Value not supported!

reolink.0
2022-10-28 13:54:51.174	error	Value not supported!

reolink.0
2022-10-28 13:54:50.991	error	Value not supported!

reolink.0
2022-10-28 13:54:50.858	error	Value not supported!

reolink.0
2022-10-28 13:54:50.750	error	Value not supported!

reolink.0
2022-10-28 13:54:50.620	error	Value not supported!

reolink.0
2022-10-28 13:54:50.491	error	Value not supported!

reolink.0
2022-10-28 13:54:50.336	error	Value not supported!

reolink.0
2022-10-28 13:54:50.208	error	Value not supported!

reolink.0
2022-10-28 13:54:50.090	error	Value not supported!

reolink.0
2022-10-28 13:54:49.984	error	Value not supported!

reolink.0
2022-10-28 13:54:49.847	error	Value not supported!

reolink.0
2022-10-28 13:54:49.713	error	Value not supported!

reolink.0
2022-10-28 13:54:49.578	error	Value not supported!

reolink.0
2022-10-28 13:54:49.442	error	Value not supported!

reolink.0
2022-10-28 13:54:49.320	error	Value not supported!

reolink.0
2022-10-28 13:54:49.159	error	Value not supported!

reolink.0
2022-10-28 13:54:49.028	error	Value not supported!

reolink.0
2022-10-28 13:54:48.911	error	Value not supported!

reolink.0
2022-10-28 13:54:48.785	error	Value not supported!

reolink.0
2022-10-28 13:54:48.645	error	Value not supported!
                                      da_Woody 1 Reply Last reply Reply Quote 0
                                      • da_Woody
                                        da_Woody @da_Woody last edited by

                                        @da_woody hab nochmal den adapter instance0 gestartet mit debug

                                        host.ioBroker
2022-10-28 14:41:06.173	info	instance system.adapter.reolink.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
host.ioBroker
2022-10-28 14:41:05.072	info	stopInstance system.adapter.reolink.0 send kill signal

reolink.0
2022-10-28 14:41:05.029	info	State value to set for "reolink.0.settings.EmailNotification" has to be type "number" but received type "string"

reolink.0
2022-10-28 14:41:04.737	debug	Error or not supported getMailNotification

reolink.0
2022-10-28 14:41:04.614	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

reolink.0
2022-10-28 14:41:04.614	info	terminating

reolink.0
2022-10-28 14:41:04.614	debug	refreshStateTimeout: UNLOAD

reolink.0
2022-10-28 14:41:04.613	info	Got terminate signal TERMINATE_YOURSELF
host.ioBroker
2022-10-28 14:41:03.755	info	stopInstance system.adapter.reolink.0 (force=false, process=true)
host.ioBroker
2022-10-28 14:41:03.754	info	"system.adapter.reolink.0" disabled

reolink.0
2022-10-28 14:41:03.719	debug	mailValue 200: [{"cmd":"Unknown","code":1,"error":{"detail":"not support","rspCode":-9}}]

reolink.0
2022-10-28 14:41:03.647	error	Value not supported!

reolink.0
2022-10-28 14:41:03.647	info	Changed state: EmailNotification

reolink.0
2022-10-28 14:41:03.646	debug	state reolink.0.settings.EmailNotification changed: Error or not supported (ack = true)

reolink.0
2022-10-28 14:41:03.596	info	State value to set for "reolink.0.settings.EmailNotification" has to be type "number" but received type "string"

reolink.0
2022-10-28 14:41:03.560	debug	Error or not supported getMailNotification

reolink.0
2022-10-28 14:41:03.520	debug	mailValue 200: [{"cmd":"Unknown","code":1,"error":{"detail":"not support","rspCode":-9}}]

reolink.0
2022-10-28 14:41:03.428	error	Value not supported!
                                        1 Reply Last reply Reply Quote 0
                                        • Wszene
                                          Wszene last edited by Wszene

                                          @Andy-Grundt
                                          Hallo Zusammen,
                                          Ich habe 2x die Reolink RLC-510A
                                          Ich bekomme auch die Datenpunkte
                                          Habe da aber mal eine Frage zur Bewegungserkennung

                                          Sollte sich der DP "reolink.0.sensor.motion" bei Erkennung auf "1" ändern?
                                          Wenn Ja dann funktioniert das nicht
                                          Ich habe mal zum Testen in der App die Push-Mitteilung angeschalten Diese springt an

                                          Danke im Voraus
                                          Gruß
                                          Marcel

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            msauer last edited by

                                            Hallo Zusammen,
                                            ich würde gerne in Blockly mit einem Trigger des Objekts reolink.0.sensor.motion ein Bild per pushover verschicken. Nun ist in dem Beispiel zwar die Javascript Prozedur vorgeschlagen, wie aber setzte ich das in Blockly um. Hat das schon jemand gemacht und mag es mit uns teilen?

                                            Danke
                                            Mark

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.7k
                                            Online

                                            30.5k
                                            Users

                                            76.7k
                                            Topics

                                            1.2m
                                            Posts

                                            kamera neuer adapter reolink testen
                                            137
                                            830
                                            114439
                                            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