keshavdv / unifi-cam-proxy

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

Can't even get the test video to work... #107

Closed m3resourcesllc closed 2 years ago

m3resourcesllc commented 2 years ago

Can anyone tell me what I'm doing wrong?

UDM Pro with Protect 1.19.2 Unifi Cam Proxy 0.1.4

Proxy is running in docker. I created the cert per instructions, decoded the QR to get the adoption token and can successfully start the docker container. In the UDMP (or the Protect app on Android) I get snapshots that do seem to cycle properly but clicking in to see live video doesn't work on either, I just get a single frame of video that never changes.

docker command: unifi-cam-proxy --verbose --ip 10.0.50.200 --host 10.0.50.1 --cert /cert/client.pem --token gAv0v4HnfGijbGBZzYsYZbPR6vgaCl8U rtsp -s rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_175k.mov

I've tried changing the container from bridge to host networking in case there was a network issue. Ultimately I'm trying to get this to with with Reolink cameras but reverted to getting the test stream working when I was unsuccessful with the cameras.

Some questions that may or may not be a problem or related:

In the logs it appears that the proxy is responding to a NetworkStatus request with a camera gateway IP of 192.168.103.1 but I'm not sure where this is coming from. I don't have that subnet in my network and definitely doesn't match the subnet of the UDMP, the docker host or the cameras. I haven't dug into the code yet to determine where this is coming from...

Is the camera IP that appears in Unifi Protect (UDMP) purely informational? I ask b/c it's showing the actual IP of the camera but there is a proxy in the middle. I would expect that the camera IP showing in Protect would be the proxy IP rather than the actual camera IP...

Thanks!

m3resourcesllc commented 2 years ago

Can anyone tell me what I'm doing wrong?

UDM Pro with Protect 1.19.2 Unifi Cam Proxy 0.1.4

Proxy is running in docker. I created the cert per instructions, decoded the QR to get the adoption token and can successfully start the docker container. In the UDMP (or the Protect app on Android) I get snapshots that do seem to cycle properly but clicking in to see live video doesn't work on either, I just get a single frame of video that never changes.

docker command: unifi-cam-proxy --verbose --ip 10.0.50.200 --host 10.0.50.1 --cert /cert/client.pem --token gAv0v4HnfGijbGBZzYsYZbPR6vgaCl8U rtsp -s rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_175k.mov

I've tried changing the container from bridge to host networking in case there was a network issue. Ultimately I'm trying to get this to with with Reolink cameras but reverted to getting the test stream working when I was unsuccessful with the cameras.

Some questions that may or may not be a problem or related:

In the logs it appears that the proxy is responding to a NetworkStatus request with a camera gateway IP of 192.168.103.1 but I'm not sure where this is coming from. I don't have that subnet in my network and definitely doesn't match the subnet of the UDMP, the docker host or the cameras. I haven't dug into the code yet to determine where this is coming from...

Is the camera IP that appears in Unifi Protect (UDMP) purely informational? I ask b/c it's showing the actual IP of the camera but there is a proxy in the middle. I would expect that the camera IP showing in Protect would be the proxy IP rather than the actual camera IP...

Thanks!

I've made a little bit of progress. Still no luck getting the test video to play, only getting the snapshots. But at least I now have the Reolink cameras doing the same. My issue, to help others was an "$" in the camera password. It must have been escaping something causing the whole ffmpeg command to fail, which I realized after checking "top" and never seeing ffmpeg running.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.