-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Streaming Taking Long Time to Start #69
Comments
I use the same logic as the base homebridge camera ffmpeg plugin. |
It takes about 2 seconds on my Raspberry Pi 4 4GB, running the Homebridge OS image. |
@beele there’s really nothing useful in the logs which is why I didn't include them. If I clear logs before opening the stream in Home.app, the logs will be empty for 20-30s after I tap the camera in Home.app before finally kicking off the ffmpeg request. At that point, assuming the app hasn’t given up, everything works fine. |
Back when I was seeing slow ffmpeg times on my old Raspberry Pi 3 with Nest cameras, it was related to the order with which I had compiled and set everything up. Namely that I ended up with multiple versions of it installed in different directories because I had followed different tutorials and instructions, one of which was not configured to take advantage of hardware acceleration on the Raspberry Pi, using the wrong protocol, was missing libfdk-aac, and more. Can you confirm that this plugin is finding and using the correct copy of ffmpeg, and can you copy its configuration here. You can get it via the command line simply by typing:
Mine looks like this:
|
I'm having trouble streaming on my Pi4 on my UDMP. My ffmpeg shows this:
|
Recompiled with:
|
If you start homebridge, the plugin should print out the path of the ffmpeg binary that is being used. Can you confirm this is using your compiled version. The video config section for the plugin should be adjusted to this:
|
The new beta fixed all the ffmpeg issues. It now streams and works correctly. Sound works perfect too. |
@beele closing this out -- not your fault, I figured out the issue though for others who may experience this: HomeKit seems to load everything sequentially (unsure if this is a HAP/Homebridge issue or HomeKit itself). If you open a section in Home.app like favorites with 6 cameras on it and immediately open a stream, the plugin doesn't get the request for In my case, one of my cameras is slow, which added to the delay. Interestingly, this seems to be hub-specific (which may mean it's a HAP/Homebridge limitation?). My ring plugin wasn't suffering this because I have it in a separate homebridge instance. |
Describe the bug
I'm opening this separate from #62 because it doesn't actually seem to be an issue with ffmpeg.
Basically, after I open the request in Home.app (on either iOS or macOS), it seems to take 30+ seconds before the plugin even acknowledges there was a request to open.
I've previously used a different UniFi plugin without this issue (migrated when upgrading to Protect) and my Ring doesn't have the problem either -- it seems specific to this plugin.
This may or may not be a dupe of #58, but sounds like a similar issue.
Specifications
What hardware and OS is your Homebridge running on?: Tested with homebridge running on macOS and Debian
What Unifi hardware are you using: UDM-Pro, 3x G3, 1x G3 Dome, 1x G4 Doorbell
The text was updated successfully, but these errors were encountered: