Frigate 0.18.2 – 401 Unauthorized after the Home Assistant Android app is suspended

[LAJER333]

English version — Frigate 0.18.2

Title: Frigate 0.18.2 – 401 Unauthorized after the Home Assistant Android app is suspended

Hello,

Since upgrading to Frigate 0.18.2, I have been experiencing an authentication issue when accessing Frigate through the Home Assistant Companion app on Android.

Steps to reproduce:

1. Open Frigate using its entry in the Home Assistant sidebar.
2. Leave the Frigate camera dashboard visible.
3. Close the tablet cover or turn off the screen for several minutes.
4. Wake the device and return to Frigate.

Expected behaviour: Frigate should resume displaying the camera dashboard normally.

Actual behaviour: The Frigate page displays the following error:

"401: Unauthorized"

The same issue occurs on both my Android tablet and smartphone.

Troubleshooting already performed:

• Increased the Frigate session length to 7 days. The problem still occurs after only a few minutes.
• Refreshing the page by pulling down does not resolve the error.
• Returning to the Home Assistant main page and reopening Frigate restores the display.

This behaviour appeared after upgrading to Frigate 0.18.2. I did not experience it before the update.

Could this be related to session/token renewal or the embedded web interface when the Home Assistant Android app resumes after being suspended?

Has anyone else experienced or reproduced this issue with Frigate 0.18.2?

Thank you.

---

Version française — traduction

Titre : Frigate 0.18.2 – Erreur 401 Unauthorized après la mise en veille de l'application Android Home Assistant

Bonjour,

Depuis la mise à jour vers Frigate 0.18.2, je rencontre un problème d'authentification lorsque j'accède à Frigate depuis l'application Home Assistant Companion sur Android.

Étapes pour reproduire le problème :

1. Ouvrir Frigate depuis son entrée dans le menu latéral de Home Assistant.
2. Laisser le tableau de bord des caméras Frigate affiché.
3. Fermer le capot de la tablette ou éteindre l'écran pendant plusieurs minutes.
4. Rallumer l'écran et revenir sur Frigate.

Comportement attendu : Frigate devrait reprendre normalement l'affichage du tableau de bord des caméras.

Comportement constaté : La page Frigate affiche l'erreur suivante :

"401: Unauthorized"

Le même problème se produit sur ma tablette Android et sur mon smartphone.

Tests déjà effectués :

• Augmentation de la durée de session Frigate à 7 jours. Le problème se produit toujours après seulement quelques minutes.
• L'actualisation de la page en faisant glisser l'écran vers le bas ne résout pas l'erreur.
• Le retour à la page d'accueil de Home Assistant, puis la réouverture de Frigate, rétablit l'affichage.

Ce comportement est apparu après la mise à jour vers Frigate 0.18.2. Je ne rencontrais pas ce problème avant cette mise à jour.

Ce problème pourrait-il être lié au renouvellement de la session ou du jeton d'authentification, ou à l'interface Web intégrée lorsque l'application Android Home Assistant reprend après une mise en veille ?

D'autres utilisateurs ont-ils rencontré ou reproduit ce problème avec Frigate 0.18.2 ?

Merci.

[hawkeye217]

That 401 page comes from Home Assistant's ingress, not from Frigate, so the Frigate session length has no effect on it. Home Assistant keeps the ingress session alive in the background, and when Android suspends the app that stops, so the session expires. Reopening Frigate from the sidebar starts a new session, which is why that fixes it. You could report this to the Home Assistant Android app or frontend repo, or access Frigate directly on port 8971 instead of through ingress.

[LAJER333]

Thank you for your explanation. I understand now that the 401 error comes from the Home Assistant Ingress session expiring, rather than from Frigate's own session.

I will report this issue to the Home Assistant Android app team or the Home Assistant frontend repository, as you suggested.

Before doing so, may I ask whether this behaviour is already known or has been reported by other users? It occurs on both my Android tablet and smartphone after the screen has been off for several minutes. Reopening Frigate from the Home Assistant sidebar restores access.

Thank you again for your help and clarification.

---

Traduction française :

Merci pour votre explication. Je comprends maintenant que l'erreur 401 provient de l'expiration de la session Home Assistant Ingress, et non de la session propre à Frigate.

Je vais signaler ce problème à l'équipe de l'application Android Home Assistant ou au dépôt du frontend Home Assistant, comme vous me l'avez conseillé.

Avant cela, puis-je vous demander si ce comportement est déjà connu ou s'il a été signalé par d'autres utilisateurs ? Le problème se produit sur ma tablette Android et mon smartphone après que l'écran est resté éteint pendant plusieurs minutes. Le fait de rouvrir Frigate depuis le menu latéral de Home Assistant rétablit l'accès.

Merci encore pour votre aide et ces précisions.

[hawkeye217]

No, I'm not aware of an existing open report for this specific issue.

[ostracizado]

That 401 page comes from Home Assistant's ingress, not from Frigate, so the Frigate session length has no effect on it. Home Assistant keeps the ingress session alive in the background, and when Android suspends the app that stops, so the session expires. Reopening Frigate from the sidebar starts a new session, which is why that fixes it. You could report this to the Home Assistant Android app or frontend repo, or access Frigate directly on port 8971 instead of through ingress.

I can report the same problem on all platforms: Android & Win.
On Win, using Chrome, it does certainly come from: api/hassio_ingress/.../profile - "Failed to load resource: the server responded with a status of 401 (Unauthorized)"

But I couldn't replicate it on any other application; even those with a WebUI and login credentials.

[hawkeye217]

This is the same ingress session expiry. Those 401s come from Home Assistant rejecting the expired ingress session before the request ever reaches Frigate. It's now being tracked in home-assistant/android#7644 and home-assistant/frontend#54862. The frontend issue describes the cause: Home Assistant only renews the ingress session on a timer, which doesn't run while the device or tab is asleep.

[ELY3M]

I am having same issue and it is irritating me. to re-produce it, just open frigate dashboard from your sidebar and leave it idling, it will turn up page with "401 unauthorized" I am using both PC in firefox and android app. most of the time, I use firefox.