eufy-security-ws: [Bug]: AFter Updating 1.6.3-> P2P streaming doesnt work on floodflight
Version
1.6.3
Node version
latest
Operating System type
Linux
Operating system version
HASSOS
Describe the bug
When startting the P2P stream, the stream neve starts and keeps hanging indefendly on PREPARING. Seems like command is sended to the camera but camera never actually starts…
data: <Buffer d1 00 00 0b 58 5a 59 48 a4 06 80 01 00 00 01 00 00 01 00 00 18 68 64 03 7e f4 47 28 67 d0 2d 0a 83 14 62 9e 71 67 b4 74 b2 b3 4d 09 be 44 11 be cb 96 ... 354 more bytes>,
customData: {
command: {
name: 'deviceStartLivestream',
value: 0
}
}
},
resultCodeName: 'ERROR_NULL_POINT',
resultCode: -100
}
2023-08-22 13:13:36.381 DEBUG [Station.onCommandResponse] Got p2p command response
{
station: 'T8424N1021291061',
commandType: 1000,
channel: 0,
returnCodeName: 'ERROR_NULL_POINT',
returnCode: -100,
customData: {
command: {
name: 'deviceStartLivestream',
value: 0
}
}
}
2023-08-22 13:13:36.382 DEBUG [P2PClientProtocol.handleMsg] Station T8424N1021291061 - DATA DATA - Received expected sequence (expectedSeqNo: 12 seqNo: 11 queuedData.size: 0)
2023-08-22 13:13:41.382 INFO [Timeout._onTimeout] Stopping the station stream for the device T8424N1021291061, because we haven't received any data for 5000 seconds
2023-08-22 13:13:41.383 DEBUG [P2PClientProtocol._sendCommand] Sending p2p command...
{
station: 'T8424N1021291061',
sequence: 12,
commandType: 1004,
channel: 0,
retries: 0,
messageStatesSize: 1
}
2023-08-22 13:13:41.395 DEBUG [P2PClientProtocol.handleMsg] Station T8424N1021291061 - ACK DATA - received from host 192.168.20.212:10426 for sequence 12
2023-08-22 13:13:41.406 DEBUG [P2PClientProtocol.handleMsg] Station T8424N1021291061 - DATA DATA - received from host 192.168.20.212:10426 - Processing sequence 12...
2023-08-22 13:13:41.406 DEBUG [P2PClientProtocol.parseDataMessage] Station T8424N1021291061 - Received data
{
seqNo: 12,
header: {
commandId: 1004,
bytesToRead: 132,
channel: 0,
signCode: 1,
type: 1
},
bytesRead: 132,
bytesToRead: 132,
firstPartMessage: true,
messageSize: 148
}
2023-08-22 13:13:41.407 DEBUG [P2PClientProtocol.handleData] Station T8424N1021291061 - Received data
{
commandIdName: 'CMD_STOP_REALTIME_MEDIA',
commandId: 1004,
resultCodeName: 'ERROR_PPCS_SUCCESSFUL',
resultCode: 0,
message: '\x00\x00\x04\x00\x00\x04\x00\x00...\n' +
'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
data: '0000000000000400000400002e2e2e0a0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000',
seqNumber: 13,
energySavingDeviceP2PDataSeqNumber: 0,
offsetDataSeqNumber: 0
}
2023-08-22 13:13:41.407 DEBUG [P2PClientProtocol.handleData] Station T8424N1021291061 - Result data for command received
{
message: {
sequence: 12,
commandType: 1004,
nestedCommandType: undefined,
channel: 0,
acknowledged: true,
retries: 0,
returnCode: -133,
data: <Buffer d1 00 00 0c 58 5a 59 48 ec 03 10 00 00 00 01 00 00 01 00 00 87 47 44 a1 ac be 2a b3 5d 70 29 f1 a1 0e 26 55>,
customData: {
command: {
name: 'deviceStopLivestream'
}
}
},
resultCodeName: 'ERROR_PPCS_SUCCESSFUL',
resultCode: 0
}
2023-08-22 13:13:41.408 DEBUG [Station.onCommandResponse] Got p2p command response
{
station: 'T8424N1021291061',
commandType: 1004,
channel: 0,
returnCodeName: 'ERROR_PPCS_SUCCESSFUL',
returnCode: 0,
customData: {
command: {
name: 'deviceStopLivestream'
}
}
}
2023-08-22 13:13:41.409 DEBUG [P2PClientProtocol.handleMsg] Station T8424N1021291061 - DATA DATA - Received expected sequence (expectedSeqNo: 13 seqNo: 12 queuedData.size: 0)
To reproduce
Start Stream on floodllight tru integration. NOthing happens
In App it still works fine.
Screenshots & Logfiles
No response
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 10 months ago
- Comments: 19 (8 by maintainers)
Commits related to this issue
- Fixed issue #253 Fixed issue #251 Updated dependency eufy-security-client to 2.8.1 Updated version and docs Updated dev dependencies — committed to bropat/eufy-security-ws by bropat 10 months ago
@kvanbiesen
I have now implemented everything so that the library now recognises whether a device supports P2P encryption and which or not. You can revoke the sharing. I will release everything soon.
Yeah I don’t mind. You can use the device. As long as you don’t put it on away mode or make the siren go “whieeeeee”… 😃
No I don’t mind using he 1.6.2 release as my home is still the old not latest firmware so still supports non encryption.
No rush my friend. …I appreciate already all your work
All devices I think that get an update now…most people upgraded and issues with. P20p started, (mine didn’t receive update) floodlight is not popular so.
I think for now, only way of knowing is people like me making error.
Dunno if it possible but maybe add a per device switch to enable p2p encryption? Well think that’s more fuatakside but your add on bass to support the switch.
Thanks for the support man, great work!
Yeah, untill 1.6.x it has been working. Someone on the fuatakgun repo also said that guard mode changing didnt work anymore. i’ve tested it also and indeed its not working. You can use mine to test it.
Please use the Home / Disarmed method if you wanna test tho, dont want the neighbours to panic when the alarm goes of lol (so not arm it :p) 😄
super, thanks for the support.
Just give me a holler if you need access again 😃
I won’t be able to look again for a few days (probably at the weekend). I want to try to understand from where the app understands whether a device supports p2p encryption or not. In the meantime, you can use the previous version 😉. If this is not a problem for you, I would keep the device sharing for the time being.
invitation send. (EU)