-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Auto-reload/retry when server is down #1830
Comments
Strange, mine does recover, I'm often tweaking things in Frigate and stopping/starting the docker container for Frigate. So if I stop Frigate, all the frigate-hass-cards then say "Camera unavailable: " on the display, and then when I restart Frigate, all the frigate-hass-card's return back to normal. No refresh needed, nothing. This is on Chromium, Edge desktop browsers and the latest Home Assistant app on Android, I am using the frigate-hass-card v6.3.3 with latest stable Frigate and HA. |
+1, it should automatically recover from both the loss of a camera, and indeed loss of Home Assistant itself. @snoack Can you record a video of what you're seeing? |
After some further testing, I can confirm that it only happens on Chrome and the HA companion app on Android (but not on Firefox), and only when using following settings: live_provider: go2rtc
go2rtc:
modes:
- webrtc In that scenario, the card remains black when restarting the Docker container running Frigate (and go2rtc). If I don't set |
Whenever I have to restart the Frigate server, all my various devices showing camera feeds in Home Assistant using Frigate card get stuck with a failed server connection, and I have to go around, manually refreshing the page / restarting the companion app.
It would be nice if the Frigate card would periodically attempt to reconnect after a failed connection in order to automatically recover from a server down scenario.
The text was updated successfully, but these errors were encountered: