-
@longbow sagte in [Neuer Adapter] EuSec:
@worxweis wie lass ich das abspielen? Denn ich habe nur eine 2Kb große Datei...
Zum Beispiel über den VLC Player, "Medien-->Netzwerkstream öffnen --> Netzwerk" Dort die Adresse reinkopieren.
@marc-berg ja, aber den vlc player kann man nicht in vis integrieren, oder?
-
@worxweis sagte in [Neuer Adapter] EuSec:
@marc-berg ja, aber den vlc player kann man nicht in vis integrieren, oder?
Nein, das geht nicht. Aber zu diesem Thema gibt es hier schon gefühlt dutzende Threads.
-
@minki sagte in [Neuer Adapter] EuSec:
@minki
RÜCKFRAGE:
eusec liefert mir als url für den livestream folgendes:/eusec.0/T8124P20223610B9/live/T8124P20223610B9.m3u8Das ist jetzt eine wirklich dumme Frage, aber ich muss sie stellen: Wo finde ich den Stream? Auf dem raspberry oder auf der Kamera? Ich frage, weil die Struktur der URL auf die Adapter Objektstruktur deutet. Vielleicht bin ich ja nicht der einzige der so dumm fragen muss...
guck mal da:
http://<name_des iobroker_host>:8082/eusec.0/T8124P20223610B9/live/T8124P20223610B9.m3u8
Die Datei liegt physisch unter ../iobroker/iobroker-data/eusec.0/xxx/last_live/xxx.m3u8
-
@worxweis sagte in [Neuer Adapter] EuSec:
@marc-berg ja, aber den vlc player kann man nicht in vis integrieren, oder?
Nein, das geht nicht. Aber zu diesem Thema gibt es hier schon gefühlt dutzende Threads.
-
@marc-berg Ich muss dich erneut dumm fragen: Gebe ich diesen Link an yahka weiter? Wenn ich versuche über den Browser auf die adresse zuzugreifen (natürlich für meine IT Infrastruktur angepasst) scheitere ich leider.
@minki sagte in [Neuer Adapter] EuSec:
@marc-berg Ich muss dich erneut dumm fragen: Gebe ich diesen Link an yahka weiter? Wenn ich versuche über den Browser auf die adresse zuzugreifen (natürlich für meine IT Infrastruktur angepasst) scheitere ich leider.
Ich kenne yahka nicht und kann dazu nichts sagen
-
@minki sagte in [Neuer Adapter] EuSec:
@marc-berg Ich muss dich erneut dumm fragen: Gebe ich diesen Link an yahka weiter? Wenn ich versuche über den Browser auf die adresse zuzugreifen (natürlich für meine IT Infrastruktur angepasst) scheitere ich leider.
Ich kenne yahka nicht und kann dazu nichts sagen
-
@marc-berg
Ja, aber ich habe hier im Forum auch noch keine Antwort bekommen, ob es schon jemand geschafft hat, diesen Stream ins VIS zu integrieren. Was bringt mir den der VLC-Player wenn ich VIS verwende?@worxweis sagte in [Neuer Adapter] EuSec:
@marc-berg
Ja, aber ich habe hier im Forum auch noch keine Antwort bekommen, ob es schon jemand geschafft hat, diesen Stream ins VIS zu integrieren. Was bringt mir den der VLC-Player wenn ich VIS verwende?Mit dem VLC Player kann man sich die Playlist anzeigen lassen. Das bringt natürlich nichts im Hinblick auf die VIS Integration.
Ich habe hier (oder in einem anderen Forum) mal gelesen, dass via "motioneye" Konvertierungen vorgenommen wurden, um eine Integration hinzubekommen. Das ist MIR aber alles zu fummelig, sodass ich mich nicht weiter darum gekümmert habe. -
@marc-berg
Bekomme eine neue Fehlermeldung. Welcher Passport wir hier gemeint?failed connection to socket.io from ::ffff:<LOCALIP>: Passport was not initialized@minki sagte in [Neuer Adapter] EuSec:
Kennst du eine anderen (besseren) mit dem es vielleicht klappen würde?
Nein. Aber das ist hier auch der falsche Thread, vielleicht machst du einen neuen auf.
-
@minki sagte in [Neuer Adapter] EuSec:
Kennst du eine anderen (besseren) mit dem es vielleicht klappen würde?
Nein. Aber das ist hier auch der falsche Thread, vielleicht machst du einen neuen auf.
@marc-berg Jawohl! Da hast du Recht - sorry dafür! Ich editiere das mal raus.
-
@marc-berg Jawohl! Da hast du Recht - sorry dafür! Ich editiere das mal raus.
-
Welchen Datenpunkt und welches Widget muss ich nehmen, damit mir das Bild vom letzten Ereignis meiner Eufy Doorbell angezeigt wird?
-
@lustig29 so weit mir das bekannt ist wird das zur Zeit nicht mehr unterstüzt bitte lesen:
https://github.com/bropat/ioBroker.eusec/releases/tag/0.9.10 -
Initiated closing of connection to station T8124P20223610B9 for saving battery.Meine Kamera ist ans Stromnetz angeschlossen. Besteht die Möglichkeit den automatischen disconnect abzustellen?
-
-
@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.
@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}} -
@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.
@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. -
@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. -
@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!
Support us
333
Online32.7k
Users82.6k
Topics1.3m
Posts