Skip to content
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

FFmpeg exited with code: 8 and signal: null #966

Open
Dgrvictor opened this issue Oct 1, 2024 · 1 comment
Open

FFmpeg exited with code: 8 and signal: null #966

Dgrvictor opened this issue Oct 1, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Dgrvictor
Copy link

Describe the bug
Hello, I have been stuck on a problem for 2 days.
I would like to install 2 cameras of the brand "Imou" in the home application on my iPhone.
So I installed homebridge on my Ubuntu (Ubuntu is installed on a raspberry pi 5) and I also installed camera.ui in order to configure my cameras.
First I retrieved the RTSP URL addresses of my cameras and I checked that they work well in VLC.
So I configure the plugin and add my cameras, I enter the RTSP address, I activate the audio and I restart my plugin.

If I go to the camera.ui interface I see my 2 cameras and they are functional. However if I add my 2 cameras to Homekit it is displayed well in it, I also have the thumbnail but if I launch the live video stream it loads infinitely and in the homebridge console I have the following error: "FFmpeg exited with code: 8 and signal: null"

(I installed ffmpeg on my ubuntu with the command "sudo apt install ffmpeg" but that doesn't change anything)

I don't know what to do to resolve this error...

before that I tested the installation of homebridge on my raspberry pi 5 in several ways:

  • Homebridge installed on raspberry os
  • Homebridge OS

It was the same problem with also other problems in addition like the "Restart video analysis" in loop

before buying my raspberry I had done the test on a windows 11 VM in Manager Hyper V and it worked perfectly well, no errors, access to my cameras in the interface camera.ui but also in Homekit.
I don't understand why it works in a Windows 11 VM but not on my raspberry because the configuration is exactly the same.
I wanted to buy a raspberry to make a homebridge but I find myself unable to make my cameras work in homekit.

Logs
LogHomebridgeCameraUI.txt

Screenshots
Capture d’écran 2024-10-02 013909

Environment

  • Node.js Version: v20.17.0
  • Homebridge Version: v1.8.4
  • Camera UI Version: v5.0.27
  • Operating System: Ubuntu Noble (24.04.1 LTS)
  • Browser: Chrome
@Dgrvictor Dgrvictor added the bug Something isn't working label Oct 1, 2024
@mkz212
Copy link
Contributor

mkz212 commented Oct 2, 2024

Important

🚀 New Version in Development 🚀

A new version of camera.ui is currently under active development - in progress are advanced works on the alpha version and the public beta will be available soon.

Stay tuned for exciting updates:
seydx/camera.ui#448

Caution

This version will not be developed, current bugs will not be fixed and new features will not be introduced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants
@mkz212 @Dgrvictor and others