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

Handle unavailability of cameras #4998

Closed
felipecrs opened this issue Jan 10, 2023 · 6 comments
Closed

Handle unavailability of cameras #4998

felipecrs opened this issue Jan 10, 2023 · 6 comments
Labels
enhancement New feature or request

Comments

@felipecrs
Copy link
Contributor

Describe what you are trying to accomplish and why in non technical terms

If some of my cameras becomes unavailable for whatever reasons, poor Wi-Fi, network issues, random crashes, or anything, Frigate does not help much to identify that unless I start to interpret the logs.

Describe the solution you'd like

It would be nice if Frigate could handle the unavailability of cameras instead of just treating it as an error. Some things Frigate could do:

  1. Display camera unavailable in its UI
  2. The Home Assistant integration to turn the entities into unavailable state
    1. This one is cool because I could then use HA's history to figure out how often my cameras becomes unavailable.

Describe alternatives you've considered
There is none, I believe.

Additional context
The way I see this being implemented is: Frigate injects the stream URL into go2rtc, and go2rtc handle the errors and return some error indicator somehow, like an HTTP status (I don't understand much about RTSP). Frigate then simply handles it.

This would require that restream is always enabled for the camera, and that the restream RTSP is reused for the other roles as mentioned in the documentation. But I think it's an ok compromise.

@felipecrs felipecrs added the enhancement New feature or request label Jan 10, 2023
@NickM-27
Copy link
Collaborator

NickM-27 commented Jan 10, 2023

Display camera unavailable in its UI

Frigate already does this in 0.12

Screen Shot 2023-01-10 at 07 09 56 AM

@NickM-27
Copy link
Collaborator

The way I see this being implemented is: Frigate injects the stream URL into go2rtc, and go2rtc handle the errors and return some error indicator somehow, like an HTTP status (I don't understand much about RTSP). Frigate then simply handles it.

This would require that restream is always enabled for the camera, and that the restream RTSP is reused for the other roles as mentioned in the documentation. But I think it's an ok compromise.

I think more info is needed, I don't see why go2rtc would be a part of this feature at all, frigate already knows whether or not the camera is currently sending it a stream or not

@NickM-27
Copy link
Collaborator

I also think more info is needed on if this request is different than #4361

@felipecrs
Copy link
Contributor Author

No, it's probably the same. The only thing not covered then is setting the camera state to unavailable in Home Assistant. Should I open an issue in the integration repository then?

@NickM-27
Copy link
Collaborator

yes, I think there is enough information available in the existing APIs for the integration to be able to do that

@felipecrs
Copy link
Contributor Author

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants