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

error with 'Request failed with status code 500' #410

Open
afi-dev opened this issue May 29, 2023 · 4 comments
Open

error with 'Request failed with status code 500' #410

afi-dev opened this issue May 29, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@afi-dev
Copy link

afi-dev commented May 29, 2023

Describe the bug
I add my camera with its rtsp stream and I get an error on the back-end informing me of a 500, unfortunately I don't know what it's due to as I don't even have the logs or the means to activate it in the configuration.

To Reproduce

  1. Add camera and set RSTP address look like this :
    image
  2. Go to Camera Dashboard

Expected behavior
This bug occurs when you add your camera and access it from the camera table, impossible for me to view it live but strangely I've noticed that it's working in a certain way even though I don't have a view when you go to the settings and then to "Video analysis" you can still see a preview.

Logs
The 500 error does not appear in the logs to my great disappointment, impossible for me to know precisely what the problem is.

Screenshots
image

However, I'm sure it's not an error or a bad configuration, because I've got the overview working in spite of everything when you go to the camera's "Video analysis" settings:
image

Environment

  • Node.js Version: v20.2.0
  • Camera UI Version: v1.1.18
  • Operating System: Ubuntu Server 22.04.2
  • Browser: Firefox 113.0.2
  • Camera used: EufyCam (Anker)
@afi-dev afi-dev added the bug Something isn't working label May 29, 2023
@imthoe
Copy link

imthoe commented Mar 21, 2024

In case anyone might have the same issue, this occurs because ffmpeg renamed the -stimeout option to -timeout.

In my case camera.ui displayed the error message Camera: Stream exited with error! (null) - Unrecognized option 'stimeout'. Error splitting the argument list: - Option not found in the console.

A simple workaround without changing the code is to add your camera like this: rtsp://admin:[email protected]/StreamingPath?ignore=-stimeout.

You can see it checks if the string -stimeout is present in your input source and will not add is a parameter to ffmpeg, if it can find it. Most cameras should just ignore the extra parameter, which doesn't do anything.

if (videoConfig.stimeout > 0 && !inputSource.includes('-stimeout')) {

@pstaubs
Copy link

pstaubs commented Mar 28, 2024

@imthoe your suggestion did not work for me.

I modified

[camera.ui/src/controller/camera/utils/camera.utils.js](

inputSource = `-stimeout ${videoConfig.stimeout * 10000000} ${inputSource}`;
)

inputSource = `-timeout ${videoConfig.stimeout * 10000000} ${inputSource}`;

And now it works.

BTW, Is this project dead? No, patches in the last two years.

@imthoe
Copy link

imthoe commented Mar 28, 2024

@pstaubs yeah I just wanted it to work for myself without having to modify the code. But thats perfectly fine too! As for the project being dead, seems like the author is busy and working on a new version, but I don't know.

seydx/homebridge-camera-ui#855 (comment)

@mkz212
Copy link
Contributor

mkz212 commented Jul 29, 2024

🎉 A new version of camera.ui

A new version of camera.ui is currently under active development. An initial alpha/beta release and previews are coming soon. Stay tuned for exciting updates: #448 .

This version will no longer be developed / fixed. The new version contains many novelties and fixes (most important is for HKSV recording).

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

4 participants