Navigation

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

    NEWS

    • JAHRESRÜCKBLICK 2024 ✨

    • NEWS von ioBroker im Blog!

    • Cloud/Vis-Offline-Weihnachtsangebot 2024

    [Neuer Adapter] EuSec

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

      @minki das weiss ich leider nicht evtl. sollten wir mal @bropat dazu befragen, oder noch besser du erstellst eine Anfrage auf github.

      Grüe
      Fabio

      M 1 Reply Last reply Reply Quote 1
      • M
        MINKI @Fabio last edited by

        @fa-bio oh ok! Das hab ich noch nie gemacht. Mache ich da ein Issue auf?

        Fabio 1 Reply Last reply Reply Quote 0
        • Fabio
          Fabio @MINKI last edited by

          @minki ja ein New issue. 👍

          M 1 Reply Last reply Reply Quote 0
          • M
            MINKI @Fabio last edited by MINKI

            @fa-bio Erledigt!

            UPDATE: seit zwei Tagen beobachte ich, dass der Adapter sich inaktiv schaltet. Jemand eine Idee woran das liegt? Im Log gibt es keine Fehlermeldung.Bildschirm­foto 2023-03-15 um 09.23.06.png

            M Fabio 2 Replies Last reply Reply Quote 1
            • M
              MINKI @MINKI last edited by

              @minki Das steht im log (Log Stufe "Debug")

              
eusec.0
2023-03-15 12:52:09.615	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - received from host 91.36.92.152:22942 - Processing sequence 0...

eusec.0
2023-03-15 12:52:09.578	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA DATA - Received expected sequence (expectedSeqNo: 2 seqNo: 1 queuedData.size: 0)

eusec.0
2023-03-15 12:52:09.578	debug	[P2PClientProtocol.closeEnergySavingDevice] Station T8124P20223610B9 - Energy saving device - No more p2p commands to execute or running streams, initiate disconnect timeout in 30000 milliseconds...

eusec.0
2023-03-15 12:52:09.578	debug	[Station.onCommandResponse] Got p2p command response [{"station":"T8124P20223610B9","commandType":1103,"channel":255,"returnCodeName":"ERROR_PPCS_SUCCESSFUL","returnCode":0}]

eusec.0
2023-03-15 12:52:09.577	debug	[P2PClientProtocol.handleData] Station T8124P20223610B9 - Result data for command received [{"message":{"sequence":1,"commandType":1103,"channel":255,"acknowledged":true,"retries":0,"returnCode":-133,"data":{"type":"Buffer","data":[209,0,0,1,88,90,89,72,79,4,4,0,0,0,1,0,255,0,0,0,255,0,0,0]}},"resultCodeName":"ERROR_PPCS_SUCCESSFUL","resultCode":0}]

eusec.0
2023-03-15 12:52:09.577	debug	[P2PClientProtocol.handleData] Station T8124P20223610B9 - Energy saving Device - Result data received - Detecting correct sequence number [{"commandIdName":"CMD_CAMERA_INFO","commandId":1103,"seqNumber":1,"newSeqNumber":1,"energySavingDeviceP2PSeqMappingCount":1}]

eusec.0
2023-03-15 12:52:09.576	debug	[P2PClientProtocol.handleData] Station T8124P20223610B9 - Received data [{"commandIdName":"CMD_CAMERA_INFO","commandId":1103,"resultCodeName":"ERROR_PPCS_SUCCESSFUL","resultCode":0,"message":"\u0000\u001c\u0000\u0000\u0004\u0015\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","data":"00000000001c000004150000000000000000000000000000000000000000000000000000","seqNumber":2,"energySavingDeviceP2PDataSeqNumber":2,"offsetDataSeqNumber":0}]

eusec.0
2023-03-15 12:52:09.576	debug	[P2PClientProtocol.parseDataMessage] Station T8124P20223610B9 - Received data [{"seqNo":1,"header":{"commandId":1103,"bytesToRead":36,"channel":255,"signCode":0,"type":1},"bytesRead":36,"bytesToRead":36,"firstPartMessage":true,"messageSize":52}]

eusec.0
2023-03-15 12:52:09.575	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA DATA - received from host 91.36.92.152:22942 - Processing sequence 1...

eusec.0
2023-03-15 12:52:09.496	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA DATA - Received expected sequence (expectedSeqNo: 1 seqNo: 0 queuedData.size: 0)

eusec.0
2023-03-15 12:52:09.496	debug	[P2PClientProtocol.closeEnergySavingDevice] Station T8124P20223610B9 - Energy saving device - No more p2p commands to execute or running streams, initiate disconnect timeout in 30000 milliseconds...

eusec.0
2023-03-15 12:52:09.495	debug	[Station.onCommandResponse] Got p2p command response [{"station":"T8124P20223610B9","commandType":1144,"channel":255,"returnCodeName":"ERROR_PPCS_SUCCESSFUL","returnCode":0}]

eusec.0
2023-03-15 12:52:09.495	debug	[P2PClientProtocol.handleData] Station T8124P20223610B9 - Result data for command received [{"message":{"sequence":0,"commandType":1144,"channel":255,"acknowledged":true,"retries":0,"returnCode":-133,"data":{"type":"Buffer","data":[209,0,0,0,88,90,89,72,120,4,136,0,0,0,1,0,255,0,0,0,0,0,0,0,0,0,0,0,52,56,51,98,100,98,53,48,48,53,55,49,56,53,48,98,101,99,48,54,49,98,100,54,98,99,55,56,54,57,99,51,52,102,102,52,99,54,57,51,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]}},"resultCodeName":"ERROR_PPCS_SUCCESSFUL","resultCode":0}]

eusec.0
2023-03-15 12:52:09.494	debug	[P2PClientProtocol.handleData] Station T8124P20223610B9 - Received data [{"commandIdName":"CMD_SDINFO_EX","commandId":1144,"resultCodeName":"ERROR_PPCS_SUCCESSFUL","resultCode":0,"message":"�\u001c\u0000\u0000\u0004\u0015\u0000\u0000","data":"00000000a81c000004150000","seqNumber":2,"energySavingDeviceP2PDataSeqNumber":2,"offsetDataSeqNumber":0}]

eusec.0
2023-03-15 12:52:09.494	debug	[P2PClientProtocol.parseDataMessage] Station T8124P20223610B9 - Received data [{"seqNo":0,"header":{"commandId":1144,"bytesToRead":12,"channel":255,"signCode":0,"type":1},"bytesRead":12,"bytesToRead":12,"firstPartMessage":true,"messageSize":28}]

eusec.0
2023-03-15 12:52:09.493	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA DATA - received from host 91.36.92.152:22942 - Processing sequence 0...

eusec.0
2023-03-15 12:52:09.404	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - Received already processed sequence (expectedSeqNo: 1 seqNo: 0 queuedData.size: 0)

eusec.0
2023-03-15 12:52:09.404	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - received from host 192.168.2.60:21207 - Processing sequence 0...

eusec.0
2023-03-15 12:52:09.394	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - Received already processed sequence (expectedSeqNo: 1 seqNo: 0 queuedData.size: 0)

eusec.0
2023-03-15 12:52:09.394	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - received from host 192.168.2.60:21207 - Processing sequence 0...

eusec.0
2023-03-15 12:52:09.390	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - Received already processed sequence (expectedSeqNo: 1 seqNo: 0 queuedData.size: 0)

eusec.0
2023-03-15 12:52:09.390	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - received from host 192.168.2.60:21207 - Processing sequence 0...

eusec.0
2023-03-15 12:52:09.383	debug	[P2PClientProtocol.closeEnergySavingDevice] Station T8124P20223610B9 - Energy saving device - No more p2p commands to execute or running streams, initiate disconnect timeout in 30000 milliseconds...

eusec.0
2023-03-15 12:52:09.383	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - ACK DATA - received from host 91.36.92.152:22942 for sequence 1

eusec.0
2023-03-15 12:52:09.381	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - Received already processed sequence (expectedSeqNo: 1 seqNo: 0 queuedData.size: 0)

eusec.0
2023-03-15 12:52:09.381	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - received from host 192.168.2.60:21207 - Processing sequence 0...

eusec.0
2023-03-15 12:52:09.378	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - Received expected sequence (expectedSeqNo: 1 seqNo: 0 queuedData.size: 0)

eusec.0
2023-03-15 12:52:09.378	debug	[P2PClientProtocol.handleDataControl] Station T8124P20223610B9 - CMD_SET_FLOODLIGHT_MANUAL_SWITCH [{"enabled":false,"payload":"\u0000\u0000\u0000\u0000"}]

eusec.0
2023-03-15 12:52:09.377	debug	[P2PClientProtocol.parseDataMessage] Station T8124P20223610B9 - Received data [{"seqNo":0,"header":{"commandId":1400,"bytesToRead":4,"channel":0,"signCode":0,"type":0},"bytesRead":4,"bytesToRead":4,"firstPartMessage":true,"messageSize":20}]

eusec.0
2023-03-15 12:52:09.377	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - DATA CONTROL - received from host 192.168.2.60:21207 - Processing sequence 0...

eusec.0
2023-03-15 12:52:09.289	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.289	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.288	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.288	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.287	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.286	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.285	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.278	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.276	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.275	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.273	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.272	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.271	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.266	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.264	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.262	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.261	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.258	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.256	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.254	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}]

eusec.0
2023-03-15 12:52:09.248	debug	[P2PClientProtocol.handleMsg] Station T8124P20223610B9 - received unknown message [{"remoteAddress":"192.168.2.60","remotePort":21207,"response":{"message":"f143002c5a5843414d414100000c9535474e484d430000000002d7523c02a8c000000000000000000000000000000000","length":48}}
              1 Reply Last reply Reply Quote 0
              • Fabio
                Fabio @MINKI last edited by Fabio

                @minki keine Ahnung hast du irgendwas in der Eufy App geändert, Passwort oder neue Geräte angelegt oder getauscht? Oder zu Hause am Router was verändert etc.?

                Probiere folgendes:
                Alle Eufy Homebase neu starten, aber vorher den Adapter in Pause schicken. Warten bis alle Eufys in der App wieder Online sind dann Adapter neu starten.

                M 1 Reply Last reply Reply Quote 0
                • M
                  MINKI @Fabio last edited by

                  @fa-bio An der Eufy App habe ich nichts geändert. Ich habe lediglich vor einigen Tagen mal testweise Wireguard via Fritzbox angeschaltet und probiert.

                  Ich werde deinen Vorschlag mal umsetzen und melde mich zeitnah! Danke für deinen tollen Support hier!

                  Fabio 1 Reply Last reply Reply Quote 0
                  • Fabio
                    Fabio @MINKI last edited by

                    @minki sagte in [Neuer Adapter] EuSec:

                    Wireguard

                    das könnte die Ursache sein. Schalte das mal ab und starte auch den Router neu.

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      MINKI @Fabio last edited by

                      @fa-bio Ich habe das ganze relativ schnell wieder abgeschaltet. Den Router werde ich heute Abend neustarten.

                      Fabio 1 Reply Last reply Reply Quote 0
                      • Fabio
                        Fabio @MINKI last edited by

                        @minki ja probiere erst die Eufys dann wenn es immer noch nicht geht den Router. Und Adapter dann immer in Pause schicken.

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          MINKI @Fabio last edited by MINKI

                          @fa-bio Habe mich an deine Anleitung gehalten. Bisher kein Ausfall mehr. Ich prüfe morgen früh nochmal den Status. Ich werde berichten!

                          Fabio 1 Reply Last reply Reply Quote 1
                          • Fabio
                            Fabio @MINKI last edited by

                            @minki mach das.👍

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              MINKI @Fabio last edited by

                              @fa-bio ba375884-d3ee-4590-8075-d0a9f18ed935-image.png

                              Same procedure my dear! Heute Abend schaue ich mir mal den Router an. Merkwürdig...

                              Fabio 1 Reply Last reply Reply Quote 0
                              • Fabio
                                Fabio @MINKI last edited by

                                @minki ja sehr komisch. Das weiss ich jetzt auch nicht mehr weiter.🤷‍♂️
                                Grüße
                                Fabio

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

                                  Hallo zusammen! Und danke für deinen Adapter.

                                  Ich möchte mich gerne über Pushover über den Ladezustand meiner Eufy 2C informieren lassen. Leider ändert sich der Datenpunkt "battery" nicht zu aktualisieren.
                                  Ich habe meine Cam heute geladen, der Datenpunkt steht aber immer noch auf 4%.
                                  In dem Adapter habe ich angegeben, dass der Abfrageintervall 1min sein soll. Warum klappt es nicht. Der Datenpunkt charging_status wird aber entsprechend aktualisiert, wenn ich die Cam lade.

                                  Kann mir da jemand helfen?

                                  Danke Euch!

                                  Fabio 1 Reply Last reply Reply Quote 0
                                  • Fabio
                                    Fabio @Uli977 last edited by Fabio

                                    @uli977 also ich habe gerade bei mir mal geschaut. Die letzte Aktualisierung war heute morgen um 11.06 Uhr der aktuelle Wert beträgt jetzt 73% im Adapter und in der Eufy App wird da auch der selbe Wert angezeigt. Vielleicht dauert es da halt was länger mit den Batteriewerten.
                                    eusec.jpg

                                    Grüße
                                    Fabio

                                    Uli977 3 Replies Last reply Reply Quote 0
                                    • Uli977
                                      Uli977 @Fabio last edited by

                                      @fa-bio

                                      Ich dachte auch, vielleicht meldet die Cam ja nur 1x am Tag an die Basisstation und der Wert wird deshalb nicht aktualisiert. Ich warte mal ab.
                                      Aktuell steht mein Wert noch auf 8:30 Uhr, das war als ich den Adapter nochmal neu gestartet und die Datenpunkte neu eingelesen habe.

                                      1 Reply Last reply Reply Quote 0
                                      • Uli977
                                        Uli977 @Fabio last edited by

                                        @fa-bio noch was....

                                        Kannst du den last-camera-picture-url auslesen? Also das Bild anzeigen lassen?

                                        Fabio 1 Reply Last reply Reply Quote 0
                                        • Fabio
                                          Fabio @Uli977 last edited by

                                          @uli977 https://forum.iobroker.net/post/959800 lies mal bitte.

                                          Uli977 1 Reply Last reply Reply Quote 0
                                          • Uli977
                                            Uli977 @Fabio last edited by Uli977

                                            @fa-bio

                                            Worauf willst du mich hinweisen? Das dass aktuell nicht mehr geht? Oder irgendetwas in dem Github Link?

                                            Ziehe die Frage zurück!

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.4k
                                            Online

                                            30.7k
                                            Users

                                            77.3k
                                            Topics

                                            1.2m
                                            Posts

                                            adapter cameras doorbell eufy eufycam security
                                            152
                                            1095
                                            159299
                                            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