ioBroker.eusec icon indicating copy to clipboard operation
ioBroker.eusec copied to clipboard

[Bug]: Error when downloading a video from T8124 (Solocam S40)

Open nielswd opened this issue 1 year ago • 0 comments

Adapter version

0.9.3

JS-Controller version

4.0.23

Node version

v14.20.0

Operating System type

Linux

Operating system version

Raspbian 11

Describe the bug

Hello, before anything, thanks a lot for your libs and all the work you've put around Eufy API.

I've an issue with my Solocam S40 (T8124) cameras : upon motion notification, the video seems to be downloaded fine using P2P :

2022-07-19 10:42:30.289  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - received from host 192.168.68.106:19387 - Processing sequence 763...
2022-07-19 10:42:30.291  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - Received not expected sequence, added to the queue for future processing (seqNo: 763 queuedData.size: 35)
2022-07-19 10:42:30.294  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - received from host 192.168.68.106:19387 - Processing sequence 654...
2022-07-19 10:42:30.296  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - Received already processed sequence (seqNo: 654 queuedData.size: 35)
2022-07-19 10:42:30.298  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - received from host 192.168.68.106:19387 - Processing sequence 655...
2022-07-19 10:42:30.300  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - Received already processed sequence (seqNo: 655 queuedData.size: 35)
2022-07-19 10:42:30.303  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - received from host 192.168.68.106:19387 - Processing sequence 656...
2022-07-19 10:42:30.304  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - Received already processed sequence (seqNo: 656 queuedData.size: 35)
2022-07-19 10:42:30.307  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - received from host 192.168.68.106:19387 - Processing sequence 657...
2022-07-19 10:42:30.309  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - DATA BINARY - Received already processed sequence (seqNo: 657 queuedData.size: 35)
2022-07-19 10:42:30.359  - [32minfo[39m: eusec.0 (10575) Initiated closing of connection to station T8124P20221906B7 for saving battery.
2022-07-19 10:42:30.363  - [32minfo[39m: eusec.0 (10575) Disconnected from station T8124P20221906B7
2022-07-19 10:42:32.120  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - END - received from host 192.168.68.106:19387

But right after, I guess during the conversion from .264 to .ts, something is going wrong :

2022-07-19 10:42:32.120  - [34mdebug[39m: eusec.0 (10575) [P2PClientProtocol.handleMsg] Station T8124P20221906B7 - END - received from host 192.168.68.106:19387
2022-07-19 10:42:34.411  - [31merror[39m: eusec.0 (10575) ffmpegStreamToHls(): An error occurred: ffmpeg exited with code 1: Cannot determine format of input stream 0:0 after EOF
Error marking filters as finished
Conversion failed!

2022-07-19 10:42:34.413  - [31merror[39m: eusec.0 (10575) ffmpegStreamToHls(): ffmpeg output:

2022-07-19 10:42:34.414  - [31merror[39m: eusec.0 (10575) ffmpegStreamToHls(): ffmpeg stderr:
[h264 @ 0x2d0f7b0] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. ([email protected])
[h264 @ 0x2d0f7b0] no frame!
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 0x2d54470] data partitioning is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[h264 @ 0x2d54470] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. ([email protected])
[h264 @ 0x2d54470] no frame!
[h264 @ 0x2d6cfd0] data partitioning is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[h264 @ 0x2d6cfd0] If you want to help, upload a sample of this file to https://streams.videolan.org/upload/ and contact the ffmpeg-devel mailing list. ([email protected])
[h264 @ 0x2d6cfd0] no frame!
....
[h264 @ 0x2def010] no frame!
Error while decoding stream #0:0: Invalid data found when processing input
    Last message repeated 4 times
Cannot determine format of input stream 0:0 after EOF
Error marking filters as finished
Conversion failed!

2022-07-19 10:42:34.419  - [31merror[39m: eusec.0 (10575) Station: T8124P20221906B7 Device: T8124P20221906B7 - Error - Cancelling download... [{}]
2022-07-19 10:42:34.422  - [33mwarn[39m: eusec.0 (10575) The station isn't downloading a video for the device T8124P20221906B7!

I've seen it working once or twice, with .m3u8 and .ts files being generated, but there is nothing inside when played with VLC.

I can add more logs if needed, and try any dev version, as I'm only using ioBroker to save the videos from my cameras for now.

To reproduce

  1. Go to Logs
  2. Wait for motion detection for Eufy Cameras (SolocamS40)
  3. See error messages

Reproduced with 0.9.1 and 0.9.3

Screenshots & Logfiles

event.log

Additional context

RaspberryPi 2 B 1Go RAM ffmpeg version 4.3.4-0+deb11u1+rpt2 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 10 (Raspbian 10.2.1-6+rpi1)

nielswd avatar Jul 19 '22 09:07 nielswd