I had some entities without ID, tried to purge them, and followed this forum post:
Somewhere someone wrote that after doing some steps, you needed to log-out and back in again, so I did. But now I can’t log-in anymore.
Using the proper username and password, it simply states that either of the two is incorrect.
I have still access to it on my phone though, but not through the browser on my laptop anymore.
I have terminal and ssh installed, but when I try to connect from a terminal on my laptop, the connection is refused.
I have read this post multiple times:
At one point it says that by doing:
auth list
you’ll get a list of users.
I tried to do that in the terminal inside home assistant on my phone, but the auth command is not found.
How do I get back in on my laptop? I don’t dare to do anything on my phone anymore.
At the bottom of the menu on the left, the user name is one of the items to chose, when I use that name, exactly as on the menu, with the password I’m 100% certain of, I can’t get in.
phone still working usually means the password is fine and the laptop is just stuck on a bad cookie or the wrong login name.
try these on the laptop before you touch the phone login:
private/incognito window, or a different browser entirely
use the username from Settings > People on the phone, not whatever shows in the sidebar
if that still fails, reset the password from the phone while youre still logged in (Settings > People > your user), then try the new one on the laptop auth list is an HA CLI thing. in the Terminal add-on its ha auth list, not a bare auth command. that is why it said not found.
dont log out of the phone until the laptop works again lol
No, DON’T change the password for your current user. Go to Settings > People > Users & create a new Administrator account, then log in with that on your laptop. You can delete/disable this account after you’ve sorted out your issue.
If you still can’t manage to access auth list from your laptop, hook up a keyboard & monitor to your HA server & type it in there.
Good to here that my first reacting was not to touch anything on the phone while it’s still working there. Clearing all cache of the browser didn’t work, removing all relevant cookies neither. Other browser, no luck too. I finally did what ShadowFist suggested: I created a new user with admin rights. I was finally able to gain access to HA from the laptop again using that user. I removed the original user, and re-created again, now that user works again (although technically it’s a new user).
So crisis averted, and back to modifying automations.
Your suggestion did work, like you can read in my responds up above.
I have no idea what may have caused this, and I’m not really motivated to dive deeper. Have some automations to modify.
Using old guides for removing entities can be fraught with danger if the underlying structure has changed in the meantime.
Install the HACS app Spook to check what is now broken, and it has some added routines accessible from Settings/Tools/Actions you may find useful in helping to clean up the database. Be sure to load the latest version before embarking on a clean-up spree as it has recent bug fixes, some benign, some not.
You may have been extremely fortunate the login credentials were in the browser cache to enable you to create a bypass login. Spook will check any broken relationships.
If it looks too hard to remedy, maybe do a restore from before you started pruning. Of course your newly created user should then be gone, and you should explore other less fatal options going forward with cleanup.
I’ve installed Spook, it looks like a very usefull addition to HA. I’ll definitely read the documentation to see what it can do.
In the end, I was able to log-in again and I was able to clean up what started the mess.
I’ve also looked at my back-up strategy: now I have a back-up stored on-device, on a different NAS but in the same rack, and a third back-up on a NAS at my parents place. All automatically done, all encrypted, that has been done very well in the GUI in HA. So now I should be very safe.