Closed StijnMut closed 1 week ago
I recently upgraded my UDM to a UDM Pro and immediately set out to use this project in order to integrate my non-Unifi cameras into Protect. I was disappointed when I found that I was experiencing the same behaviour though.
I have downgraded my Protect version to 4.0.21 though, and found that the behaviour still exists. All I get is the initial frame, then a loading indicator in the bottom left of each camera:
This being the case, I'm not entirely convinced that this is related to differences between versions.
My UDM is on the latest and it's still working with the branch that was mentioned in the other thread. It's slow but it eventually does load.
i have the same issue
I identified a potential fix, playing with the flags on the container command, I found that Unifi Protect doesn't seem to like the aac
reencoding flags. Using --ffmpeg-args="-c copy"
seemed to work fine.
EDIT: might need to change the ffmpeg-args to copy all of the original args but change "-codec:a aac" to "-codec:a copy"
I too am only able to get around 1 frame every few minutes when running the latest version of protect, and the dev build of the proxy to prevent constant broken pipe errors.
Unfortunately @jasoryeh suggestion to change the codec choice hasn't resolved the problem for me.
I too am only able to get around 1 frame every few minutes when running the latest version of protect, and the dev build of the proxy to prevent constant broken pipe errors.
Unfortunately @jasoryeh suggestion to change the codec choice hasn't resolved the problem for me.
I've identified that the specific codec that seems to work is pcm_alaw
, could you try using this flag on the command: -c:v copy -ar 32000 -ac 1 -codec:a pcm_alaw -b:a 32k
Others have tried, and it makes the live preview work on the web, only issue is the mobile app, when selecting an individual stream doesn't load (general live preview with multiple cameras appears to work).
The 1 frame every few minutes is from unifi-cam-proxy re-rendering a new image preview which appears to be a somewhat different process.
I've just thrown that flag in and restarted the container. Still no live video. The "thumbnail" preview when highlighting the camera in the devices tab seems to update randomly every 2-10 seconds. I'm seeing fairly regular "broken pipe" and "ffmpeg process for videoX died" errors when attempting to view any live video even on the dev branch, which from what I gather from the other threads, isn't meant to be the case.
Hey guys - I found out that you need to use the newest Protect 4.1.39
. Then it was working for me!
Even without --ffmpeg-args
.
Hey guys - I found out that you need to use the newest
Protect 4.1.39
. Then it was working for me! Even without--ffmpeg-args
.
Hello. I assume Protect version 4.1.39 is a beta/RC? I see 4.1.51 is the latest RC version on the UniFi forums now, so hopefully the fixes continue through to release. Fingers crossed!
I'm on 4.1.53 and I no longer see events in my timeline. This possibly could be upgrading to frigate 0.14.1, perhaps the matt code needs to be updated.
given unifi's onvif roadmap, might be end of the road for this one.
Support for ONVIF hit my Dream Machine pro today. I was able to adopt my Reolink Duo 3 PoE.
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.
Camera
RTSP Stream Source
Firmware version of the camera
Protect version 4.0.33
Description
Since update 4.0.33 live streaming for 3rd party cameras doesnt work anymore over unifi-cam-proxy version 4.0.21 is the latest one that seems to still be in working order downgrading to 4.0.21 allows live streaming to be accessed but this makes the web interface unusable due to an error, can we find a way to update unifi-cam-proxy to protect version 4.0.33?
How to reproduce
Run protect version 4.0.33
Expected behaviour
No live stream just one image every 5-10 minutes
Screenshots
No response
Additional information
This is a kind of update request on the older version of protect the proxy works wonderfully