search

keshavdv / unifi-cam-proxy

Enable non-Ubiquiti cameras to work with Unifi NVR
MIT License
1.6k stars 226 forks source link

streaming not working in 1.21.3 #199

Closed jurajs5 closed 9 months ago

jurajs5 commented 2 years ago

no streaming in version 1.21.3

snapshots are there, but streaming is KO in proxy site, looks like all is ok, but in unifi UDM pro - there is no video, 3dost all the time (loading)

Camera:

eltomato89 commented 2 years ago

Same problem here! Screenshots do work, but no video stream. Reolink RLC-410-5MP Already tried readopting ..

2022-03-08 10:09:12 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Core[1] INFO Creating ws connection to wss://172.20.10.1:7442/camera/1.0/ws?token=Qk8IHpfFVlgWhuQmOQ09FEOgFwcnokE3
2022-03-08 10:09:12 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Adopting with token [Qk8IHpfFVlgWhuQmOQ09FEOgFwcnokE3] and mac [EC:71:DB:BA:1B:3D]
2022-03-08 10:09:12 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Connecting to motion events API: http://172.20.60.20/api.cgi?cmd=GetMdState&user=[user]&password=[password]
2022-03-08 10:09:12 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_hello] message
2022-03-08 10:09:12 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_hello] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_paramAgreement] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_paramAgreement] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [StopService] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeIspSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeIspSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeOsdSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeSoundLedSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeSmartMotionSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [EnableLogging] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeDeviceSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeDeviceSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [SmartMotionTest] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [UpdateUsernamePassword] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:09:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:09:14 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [UpdateFirmwareRequest] message
2022-03-08 10:09:14 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Reconnecting...
2022-03-08 10:09:14 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Cleaning up instance
2022-03-08 10:09:14 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Core[1] INFO Backing off connect(...) for 2.0s (True)
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Core[1] INFO Creating ws connection to wss://172.20.10.1:7442/camera/1.0/ws?token=Qk8IHpfFVlgWhuQmOQ09FEOgFwcnokE3
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Adopting with token [Qk8IHpfFVlgWhuQmOQ09FEOgFwcnokE3] and mac [EC:71:DB:BA:1B:3D]
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Connecting to motion events API: http://172.20.60.20/api.cgi?cmd=GetMdState&user=[user]&password=[password]
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_hello] message
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_hello] message
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_paramAgreement] message
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ubnt_avclient_paramAgreement] message
2022-03-08 10:09:16 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [StopService] message
2022-03-08 10:09:17 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeDeviceSettings] message
2022-03-08 10:09:17 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:09:17 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeIspSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeOsdSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeAudioEventsSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeSoundLedSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeSmartMotionSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [EnableLogging] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeDeviceSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeDeviceSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [SmartMotionTest] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [UpdateUsernamePassword] message
2022-03-08 10:09:22 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
2022-03-08 10:09:23 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:09:23 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:09:24 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
ffmpeg version 4.1.6 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 8.3.0 (Alpine 8.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --disable-debug
  libavutil      56. 22.100 / 56. 22.100
  libavcodec     58. 35.100 / 58. 35.100
  libavformat    58. 20.100 / 58. 20.100
  libavdevice    58.  5.100 / 58.  5.100
  libavfilter     7. 40.101 /  7. 40.101
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc    55.  3.100 / 55.  3.100
2022-03-08 10:09:24 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Spawning ffmpeg for video1 (lzdb1tDNhFXaPSUE): ffmpeg -nostdin -loglevel error -y -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -stimeout 15000000 -rtsp_transport tcp -i "rtsp://[user]:[password]@172.20.60.20:554//h264Preview_01_main" -c:v copy -vbsf "h264_metadata=tick_rate=60000/1001" -ar 32000 -ac 1 -codec:a aac -b:a 32k -metadata streamname=lzdb1tDNhFXaPSUE -f flv - | /usr/local/bin/python -m unifi.clock_sync | nc 172.20.10.1 7550
2022-03-08 10:09:24 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
ffmpeg version 4.1.6 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 8.3.0 (Alpine 8.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --disable-debug
  libavutil      56. 22.100 / 56. 22.100
  libavcodec     58. 35.100 / 58. 35.100
  libavformat    58. 20.100 / 58. 20.100
  libavdevice    58.  5.100 / 58.  5.100
  libavfilter     7. 40.101 /  7. 40.101
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc    55.  3.100 / 55.  3.100
2022-03-08 10:09:24 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Spawning ffmpeg for video3 (YcMABRI5Qqhkv1ty): ffmpeg -nostdin -loglevel error -y -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -stimeout 15000000 -rtsp_transport tcp -i "rtsp://[user]:[password]@172.20.60.20:554//h264Preview_01_main" -c:v copy -vbsf "h264_metadata=tick_rate=60000/1001" -ar 32000 -ac 1 -codec:a aac -b:a 32k -metadata streamname=YcMABRI5Qqhkv1ty -f flv - | /usr/local/bin/python -m unifi.clock_sync | nc 172.20.10.1 7550
2022-03-08 10:09:33 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:09:33 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:09:39 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [ChangeVideoSettings] message
ffmpeg version 4.1.6 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 8.3.0 (Alpine 8.3.0)
  configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --disable-debug
  libavutil      56. 22.100 / 56. 22.100
  libavcodec     58. 35.100 / 58. 35.100
  libavformat    58. 20.100 / 58. 20.100
  libavdevice    58.  5.100 / 58.  5.100
  libavfilter     7. 40.101 /  7. 40.101
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale      5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc    55.  3.100 / 55.  3.100
2022-03-08 10:09:39 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Spawning ffmpeg for video2 (mt1I7zmnsRr9H1Sj): ffmpeg -nostdin -loglevel error -y -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -stimeout 15000000 -rtsp_transport tcp -i "rtsp://[user]:[password]@172.20.60.20:554//h264Preview_01_main" -c:v copy -vbsf "h264_metadata=tick_rate=60000/1001" -ar 32000 -ac 1 -codec:a aac -b:a 32k -metadata streamname=mt1I7zmnsRr9H1Sj -f flv - | /usr/local/bin/python -m unifi.clock_sync | nc 172.20.10.1 7550
2022-03-08 10:09:43 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:09:43 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:09:44 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:09:44 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:09:53 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:09:53 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:09:59 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:09:59 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:10:03 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:10:03 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:10:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:10:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:10:17 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:10:17 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:10:23 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:10:23 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:10:30 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:10:30 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:10:33 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:10:33 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:10:42 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:10:42 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:10:43 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:10:43 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:10:53 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:10:53 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:10:58 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:10:58 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:11:03 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:11:03 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:11:10 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:11:10 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
2022-03-08 10:11:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:11:13 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:11:23 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [NetworkStatus] message
2022-03-08 10:11:23 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetSystemStats] message
2022-03-08 10:11:27 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Processing [GetRequest] message
2022-03-08 10:11:27 unifi-cam-proxy-haustuer-79c4b5b7c9-xnh8w Reolink[1] INFO Grabbing snapshot: http://172.20.60.20/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=6PHVjvf0UntSLbyT&user=[user]&password=[password]
eltomato89 commented 2 years ago

Also .. I dont know if this is connected to the problem, but I found a stacktrace after restarting the unifi protect application on my udm pro:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/app/unifi/clock_sync.py", line 167, in <module>
    main()
  File "/app/unifi/clock_sync.py", line 157, in main
    write(read_bytes(source, payload_size))
  File "/app/unifi/clock_sync.py", line 87, in write
    sys.stdout.buffer.write(data)
BrokenPipeError: [Errno 32] Broken pipe
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/app/unifi/clock_sync.py", line 167, in <module>
    main()
  File "/app/unifi/clock_sync.py", line 157, in main
    write(read_bytes(source, payload_size))
  File "/app/unifi/clock_sync.py", line 87, in write
    sys.stdout.buffer.write(data)
BrokenPipeError: [Errno 32] Broken pipe
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipe
xsasx commented 2 years ago

hopefully it will be fixed soon cause 1.21.3 is out now since 1 hour official

keshavdv commented 2 years ago

Finally got the update and looking for a fix. At the moment, it doesn't look like an easy one, so I'd suggest disabling auto-update and downgrading if you rely on the proxy for important cameras.

pgeremia commented 2 years ago

Seeing same thing on my setup. I mean right now there are NO cameras to buy from Unifi so this is our only option. :-/

tboyce021 commented 2 years ago

What's the latest version of protect that should work? I tried back to 1.19.2 but kept getting the same error. Do I need to downgrade the entire unifi-os on the udm pro since I updated to 1.11.4?

lcasale commented 2 years ago

1.21.2 works

tphipps commented 2 years ago

Identical issue here. 4 x Hikvision cameras working perfectly with Protect v1.21.2, only low-res screenshots with v1.21.3 and seeing the identical crash as @eltomato89 above. Reverting to Protect v.1.21.2 got the cameras back online.

To save time for others looking for how to revert, ssh into the UDM-Pro and:

apt-get update
apt-get install --reinstall --allow-downgrades unifi-protect=1.21.2 -y
DebauchedSloth commented 2 years ago

Same here with Amcrest / Dahua cams.

frieck commented 2 years ago

Any updates? I am having the same problem with Dahua

tsspmq commented 2 years ago

A few posts up he said it wasn't going to be easy to fix, so I would stay on 1.21.2 (if you have access) as long as it takes if you need them. Nothing in .3 is really exciting enough to upgrade anyway.

lcasale commented 2 years ago

FYI this is still broken in Protect 1.21.4 incase anyone was curious on upgrading.

FrancescoFdd5 commented 2 years ago

Same Issue

ChronoBrake commented 2 years ago

Any chance it will be resolved or Ubiquiti killed that project :/ ? @keshavdv

DReffects commented 2 years ago

Ah damn, should have looked in here first... going mad for weeks now because the cameras froze for no apperant reason. Changed switches, cables, firmware... oh my...

My Dahua cams always worked for one up to four days, then died in a way that only a loss of power could revive them. no access via webinterface was possible. switching to protect 1.21.2 now for testing.

DReffects commented 2 years ago

1.21.2 seems to work for the past 4 hours but only without seperate screenshot URL. I hope the cameras stay on.

ChronoBrake commented 2 years ago

New version 1.23.4 with changelog: Fix an issue that prevents G3 cameras from streaming and recording until they are restarted. https://community.ui.com/releases/UniFi-Protect-Application-1-21-4/b0c494ef-a768-4aae-8ac1-e70851de4290

Maybe it's be a bug? Somebody can check it's be resolved on new Protect version?

FrancescoFdd5 commented 2 years ago

Maybe it's be a bug? Somebody can check it's be resolved on new Protect version?

Still not work in 1.21.4

pgeremia commented 2 years ago

Same here. 1.21.4 only snapshots are working. I have not had any time to debug but maybe I will see what I can find over the next few days. Has anyone looked at 1.21.3 release notes to get a clue what may have changed? I will check that too.

benmprojects commented 2 years ago

Identical issue here. 4 x Hikvision cameras working perfectly with Protect v1.21.2, only low-res screenshots with v1.21.3 and seeing the identical crash as @eltomato89 above. Reverting to Protect v.1.21.2 got the cameras back online.

To save time for others looking for how to revert, ssh into the UDM-Pro and:

apt-get update
apt-get install --reinstall --allow-downgrades unifi-protect=1.21.2 -y

This works perfectly. Thanks!

FrancescoFdd5 commented 2 years ago

Any updates?

EasternIndustries-IT commented 2 years ago

So Just an update for me I updated the console to 2.3.15 (NOT THE PROTECT APP ) and my cameras stopped working :/ . I'm getting a streamname: = nlkjljoilkljkljjijj898yo invalid arguments

Proxy1_1  | [NULL @ 0x55fdda3c95c0] Unable to find a suitable output format for 'streamname=C1wrNdvUWdyPHU4G'
Proxy1_1  | streamname=C1wrNdvUWdyPHU4G: Invalid argument
Proxy1_1  | 2022-04-05 23:31:00 4e9f6e056c18 RTSPCam[1] INFO Processing [GetRequest] message
Proxy1_1  | 2022-04-05 23:31:00 4e9f6e056c18 RTSPCam[1] INFO Processing [ChangeVideoSettings] message
Proxy1_1  | ffmpeg version 4.1.6 Copyright (c) 2000-2020 the FFmpeg developers
Proxy1_1  |   built with gcc 8.3.0 (Alpine 8.3.0)
Proxy1_1  |   configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --disable-debug
Proxy1_1  |   libavutil      56. 22.100 / 56. 22.100
Proxy1_1  |   libavcodec     58. 35.100 / 58. 35.100
Proxy1_1  |   libavformat    58. 20.100 / 58. 20.100
Proxy1_1  |   libavdevice    58.  5.100 / 58.  5.100
Proxy1_1  |   libavfilter     7. 40.101 /  7. 40.101
Proxy1_1  |   libavresample   4.  0.  0 /  4.  0.  0
Proxy1_1  |   libswscale      5.  3.100 /  5.  3.100
Proxy1_1  |   libswresample   3.  3.100 /  3.  3.100
Proxy1_1  |   libpostproc    55.  3.100 / 55.  3.100
Proxy1_1  | 2022-04-05 23:31:01 4e9f6e056c18 RTSPCam[1] WARNING Previous ffmpeg process for video2 died.
Proxy1_1  | 2022-04-05 23:31:01 4e9f6e056c18 RTSPCam[1] INFO Spawning ffmpeg for video2 (C1wrNdvUWdyPHU4G): ffmpeg -nostdin -loglevel error -y -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -stimeout 15000000 -rtsp_transport tcp -i "rtsp://admin:eXXX@192.168.30.XXX:554/cam/realmonitor?channel=1&subtype=0" -f lavfi -i anullsrc -c:v copy -ar 32000 -ac 1 -codec:a aac -b:a 32k> -metadata streamname=C1wrNdvUWdyPHU4G-f flv - | /usr/local/bin/python -m unifi.clock_sync | nc 192.168.30.10 7550

Config unifi-cam-proxy --host 192.168.30.10 -i 192.168.30.43 --mac 'F4:FA:4C:39:E4:49' -c /client.pem -t KsnCXmmwlTY3iqAtA73j6FVFzt6DeGeq dahua -u admin -p eAstern23 --ffmpeg-args="-f lavfi -i anullsrc -c:v copy -ar 32000 -ac 1 -codec:a aac -b:a 32k">

keshavdv commented 2 years ago

I've made some progress trying to understand the new entirely custom video feed, but haven't quite been able to figure out which bits are necessary just yet. Thank you for your patience!

DReffects commented 2 years ago

. Thank you for your patience! THANK YOU!!

If I can assist in any way let me know

poldim commented 2 years ago

Getting a similar error

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/app/unifi/clock_sync.py", line 167, in <module>
    main()
  File "/app/unifi/clock_sync.py", line 157, in main
    write(read_bytes(source, payload_size))
  File "/app/unifi/clock_sync.py", line 87, in write
    sys.stdout.buffer.write(data)
BrokenPipeError: [Errno 32] Broken pipe
av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipepipe:: Broken pipe
EasternIndustries-IT commented 2 years ago

So Im not sure if this has anything to do with a broken pip error. But since the update of the controller only not the app. I can no longer reach the unvr or protect by the specified ports

192.168.XXX.XXX:7443
192.168.XXX.XXX:7080

So I assume the port mapping for the UNVR has changed the ports listed below

7080 - HTTP Web UI & API

7443 - HTTPS Web UI & API

7444 - Camera firmware updates from controller

7447 - RTSP via the controller

7550 - Streaming to UFP

7442 - Camera management
keshavdv commented 2 years ago

Update: I've been able to make progress and get basic streaming working again in 1.21.4, but it will take me a few days to get things in good enough shape to ship a fix and push a new version.

ksorokin commented 2 years ago

Thank you for your effort to get things back. While you're shaping up the things, could you please share some details on the root cause? Just curious, I spent some time to investigate the issue, but not enough :)

keshavdv commented 2 years ago

In the latest releases, Protect has switched to an entirely non-standard flv encoding format which isn't supported by any existing open source tools. Most of the effort was in trying to identify the custom extensions of the video stream and figure out how to inject them into an existing stream without re-encoding.

PxxBxx commented 2 years ago

I'm just giving stimulus here, I hope you'll manage something with the .4 and/or .5 protect version. If you success, I'll try my best to disable any auto-upgrade, your proxy is amazing. Keep up the good work, and good luck with FLV !

tsspmq commented 2 years ago

I wonder if the timelapse from the newer protect version email notifications is related to this or just a coincidence. That is the 2.0.0 beta line though.

ksorokin commented 2 years ago

@keshavdv is it possible I can help you somehow? If you can share more details on your research and desired outcome , I can spend time for a PR to get it done

DReffects commented 2 years ago

In the latest releases, Protect has switched to an entirely non-standard flv encoding format which isn't supported by any existing open source tools. Most of the effort was in trying to identify the custom extensions of the video stream and figure out how to inject them into an existing stream without re-encoding.

Could you please provide additional info on this or an example file? I have a good amount of knowledge in regards to video codecs, recoding and transcoding. Maybe I can help.

lcasale commented 2 years ago

@keshavdv would it be possible for you to commit and push the branch you're working on? To @DReffects point we may be able to divide and conquer the work. Thanks!

keshavdv commented 2 years ago

I've pushed a branch called protect-124 which makes live streaming work again but seemingly only on iOS. Recording somewhat works, but the timestamps are off likely due to incorrect generation of the timestamps sent after each packet.

daltskin commented 2 years ago

Just a heads up..

I downgraded to 1.21.2 a while back and disabled auto-updates of apps - and everything was awesome.

image

However, at some point this week version 1.21.5 got auto-installed onto the UDM Pro regardless, causing the broken pipe errors. Downgrading again resolves the issue:

apt-get update
apt-get install --reinstall --allow-downgrades unifi-protect=1.21.2 -y

I'm not sure exactly when it stopped working to identify the cause, but see this in the logs which is possibly related:

[2022-05-06T03:31:03,581] INFO system - ====================================================================== [2022-05-06T03:31:03,582] INFO system - UniFi 7.1.61 (build atag_7.1.61_17860 - release/release) is started [2022-05-06T03:31:03,583] INFO system - ======================================================================

DReffects commented 2 years ago

From what I can understand the UDM Pro updates applications if they are bundled with new releases of the UniFi OS - happened to me to.

elafargue commented 2 years ago

Protect 1.21.6 on this branch works a lot better - streaming on iOS does work as you mentioned, but streaming on the web app does not, with ffmpeg being restarted every couple of seconds. Very encouraging though! Let us know if there's anything more we can do to help

jurajs5 commented 2 years ago

i have updated to 1.21.6 and cam proxy to 0.20 but still can not see streamong on hikvision camera. Any ideas?

elafargue commented 2 years ago

i have updated to 1.21.6 and cam proxy to 0.20 but still can not see streamong on hikvision camera. Any ideas?

only the protect-124 branch works somewhat on recent Protect versions, the main branch does not. And by "somewhat" I mean that it is (very) encouraging but not ready for production yet.

ChronoBrake commented 2 years ago

Waiting for updates with patient. @keshavdv can you "break" new version to get work of your project on all platforms? Regards

mrMiimo commented 2 years ago

i have updated to 1.21.6 and cam proxy to 0.20 but still can not see streamong on hikvision camera. Any ideas?

only the protect-124 branch works somewhat on recent Protect versions, the main branch does not. And by "somewhat" I mean that it is (very) encouraging but not ready for production yet.

is there a docker image for this branch (protect-124)?

eltomato89 commented 2 years ago

I have built it but its not working for me (not on the 1.21.2 and not on the current 1.21.6 version of unifi protect) But please share if it works for you! docker pull koehler/unifi-cam-proxy:protect-124

ptorsten commented 2 years ago

protect-124 makes the live stream work on mobile (ios and android) but not web

jurajs5 commented 2 years ago

Any chance for positive update?

ilbarone87 commented 2 years ago

whats's the tag for protect-124 on docker registry? can't see it in docker registry, only latest and dev. Or maybe is there another way to pull it for docker compose?

Jaffa commented 2 years ago

whats's the tag for protect-124 on docker registry? can't see it in docker registry, only latest and dev. Or maybe is there another way to pull it for docker compose?

To test the protect-124 branch, you could try the image above from @eltomato89 or build it yourself:

git clone https://github.com/keshavdv/unifi-cam-proxy.git
git checkout origin/protect-124
sudo docker build
sudo docker images

Take the Image ID from the image just built, and put that in docker-compose.yml as the image value.

My own testing with a Reolink RL-510A seems to confirm the above: streaming seems to be OK to mobile devices; doesn't work on the web; but no obvious errors now in the logs.

ilbarone87 commented 2 years ago

whats's the tag for protect-124 on docker registry? can't see it in docker registry, only latest and dev. Or maybe is there another way to pull it for docker compose?

To test the {{protect-124}} branch, you could try the image above from @eltomato89 or build it yourself:

git clone https://github.com/keshavdv/unifi-cam-proxy.git
git checkout origin/protect-124
sudo docker build
sudo docker images

Take the Image ID from the image just built, and put that in docker-compose.yml as the image value.

Thanks missed that

ilbarone87 commented 2 years ago

I have built it but its not working for me (not on the 1.21.2 and not on the current 1.21.6 version of unifi protect) But please share if it works for you! docker pull koehler/unifi-cam-proxy:protect-124

I'm getting this

Traceback (most recent call last):
  File "/usr/local/bin/unifi-cam-proxy", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.8/site-packages/unifi/main.py", line 116, in main
    cam = klass(args, logger)
  File "/usr/local/lib/python3.8/site-packages/unifi/cams/reolink.py", line 21, in __init__
    self.cam = reolinkapi.Camera(
  File "/usr/local/lib/python3.8/site-packages/reolinkapi/camera.py", line 38, in __init__
    super().login()
  File "/usr/local/lib/python3.8/site-packages/reolinkapi/handlers/api_handler.py", line 70, in login
    response = Request.post(self.url, data=body, params=param)
  File "/usr/local/lib/python3.8/site-packages/reolinkapi/handlers/rest_handler.py", line 20, in post
    r = requests.post(url, verify=False, params=params, json=data, headers=headers,
  File "/usr/local/lib/python3.8/site-packages/requests/api.py", line 117, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 529, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/local/lib/python3.8/site-packages/requests/sessions.py", line 645, in send
    r = adapter.send(request, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/requests/adapters.py", line 519, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='10.10.30.78', port=80): Max retries exceeded with url: /cgi-bin/api.cgi?cmd=Login&token=null (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f1241c54370>: Failed to establish a new connection: [Errno 111] Connection refused'))
ptorsten commented 2 years ago

Spoke to soon - the timestamps is way of in the Android app after a day