Other users have indicated that it also fails for them in Chrome, but I haven't been able to make that happen. Firefox if I configure it to 'Delete cookies and site data when Firefox is closed'.This causes the supervisor to reject the request (HTTP 401), so the addon never gets the credentials it needs to work.

Thanks, I've had a lot of trouble figuring out why this stopped working.Īs far as I can tell, when I redirect the browser from habackup.io to your local addon to pass along Google Drive credentials, for some users the session cookie that indicates to the supervisor your broswer has permission doesn't get included in the request.

I am seeing the problem in both Firefox and Chrome and i do not delete cookes when either of them are closed down. If anyone is seeing this error and they aren't using Firefox with the 'Delete cookies and site data when Firefox is closed' option enabled, please chime in so I can broaden my search for other sources of the problem. I haven't released a new version of the addon, it doesn't look like it was an update in Firefox, and its not because of a new supervisor version. I'm at a loss for how this could just suddenly start happening.

I've tried using an older version of, v79.0.0 (80.0.1 is current latest) and I see the same problem, so I don't think this is a sudden regression in Firefox. The error message is actually the Home Assistant Supervisor claiming that your browser isn’t presenting the cookie that verifies you’re logged in to Home Assistant. I don’t know why this would cause problems, but turning it on is the only thing I’ve found that reliably reproduces the problem. I’ve been testing around with different browser configurations, and I’m pretty sure this “401: Permission Denied” issue only affects users of Firefox who have it set to automatically delete cookies when the browser closes.

Instal the new Google Drive 80.0.1