-
Notifications
You must be signed in to change notification settings - Fork 4
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
Login won't stay persistent after signing in. #6
Comments
After you're logged out, what happens if you visit Home Assistant directly? (not through the extension) |
My HA session accessed at the same URL is always connected via a browser window and stays logged in even when the extension logs me out. Same experience with the HA Android App, it doesn't log me out from there either when the extension does. Also not sure if it helps but the extension has me go through 2FA and I successfully complete that every time I log into the extension. |
Experiencing the same. Not useing 2FA. I have made sure all Firefox and other privacy settings are off for the HAS IP address. I call the extension, login and use the HAS page. I can go back a few moments or minutes later and I'm asked to log back in again. When logged out HAS works as usual - no login required. Notes
|
I'm sorry but I cannot reproduce this on my side, so I am completely unable to investigate and fix it 😞
I highly doubt it, because I'm just cropping the window with CSS ! I don't see how it can influence anything related to authentication... |
Yep Agreed - seems that that was a false positive. It's back to asking for the login. Let me try again tomorrow on a different PC and see if I can get any clues in console for you. |
BTW - thanks for this. This linked with the Spotify/Spotcast custom component and the Mini Media Player card is a fantastic combo. |
sry I guess I didn't get an email for this chain. Testing now with the header enabled to see if that changes anything. |
Well that took about 2 min for it to appear again haha. I was actually in the middle of checking another bug I found which when it happened again. 2nd bug is (and im not sure if this is by design or a limitation) but when I attempt to use the header (now that I have exposed it), it wont change the page but it does move a long the top navigation. https://prnt.sc/134khwv vs https://prnt.sc/134klu0 Also its now asked me to login 4 times in 6 minutes since I started testing again |
Thanks for the screenshot, but I still don't know how to reproduce it on my side, so I cannot do anything 🤷♂️ On my computer, I stay logged in 100% of the time, as it should be |
OK I haven't used Chrome since yesterday and opening it now the extension
works perfectly and I'm logged in. Firefox 80.0.1 won't retain the login
for the extension. I have all FF and other adblocks/privacy switched off
…On Thu, 20 May 2021 at 15:41, Boris K ***@***.***> wrote:
Thanks for the screenshot, but I still don't know how to reproduce it on
my side, so I cannot do anything 🤷♂️
On my computer, I stay logged in 100% of the time, as it should be
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK5MTVWF4ECVO2QT2LE7ADTTOS4I3ANCNFSM44WFTIBQ>
.
|
I think I have the cause. In Firefox about:preferences#privacy I had "Enhanced Tracking Protection" to STRICT. Changing this to STANDARD allows the HAS login to persist. Perhaps we can use the CUSTOM setting to avoid this. Anyhows, hope this helps . |
That's it ! I tried to set the protection to "strict" and I the extension asked me to log in Switched it again to "standard", and the extension was working again Well done 👍 |
I've added a little explanation in the extension description for people who encounter the same problem |
I wonder if there is a way to do this without lowering security settings for the whole browser. |
Using FF 88.0.1
After signing into HA using the add on it will not stay logged in. After a period of time (5+ min) it logs me out and asks me to log in again.
The text was updated successfully, but these errors were encountered: