Today, I Had home assistant go haywire w/locks, garage doors and lights randomly changing states today. Worried i might be hacked.
i set up 2 point verification, 3 login attempt threshold for ip ban when i set up remote access.
I’ve disabled remote access, but had a few questions.
Is there a way to see who accessed my home assistant today via logs
using the video above, i used a duck dns certificate and currently have this error under network: You have configured an HTTPS certificate in Home Assistant. This means that your internal URL needs to be set to a domain covered by the certficate.
if i delete this bit in my config.yaml file, will this error go away : http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
ip_ban_enabled: true
login_attempts_threshold: 3
I switched over to nabu casa right now so i can keep remote access/google assistant integration, but says that i can’t use google assistant bc of the certificate. Again, would deleting the lines in config.yaml, fix this?
Hope i didn’t mess things up too badly. Any and all help is appreciated.
i followed your instructions and now running through nabu casa. Was pretty smooth sailing w/no issues until about 1 hr ago.
similar event happened today. Lights switching on and off, front door unlocked and locked again and garage doors as well. here’s a screengrab of most recent logbook. What do you think i should do at this point.
My wife and I are using the same nabu casa login via our smartphones, but nobody else has this access as far as i know.
the locks and garage doors are tied to automations, but the lights are not.
i’ve deleted my duckdns domain and when i type that url in, it won’t login. i’m now only using http locally and the nabu cass url. locally, my browser says that it is not secured.
Any further recs? Change my home assistant password again? Fresh install?
Well if you’re no longer connected directly to the internet… Make sure you’ve unforwarded your router ports.
Btw, you’re assuming (if it was someone connecting to your instance) that they came through the internet. Maybe your neighbor’s kid has your wifi password (but they would also need your HA password which is pretty easy to obtain on a non-ssl connection.
It’s fairly annoying that you can’t see something as simple as ‘current logins’ and ‘login history’ in home assistant.
Yeah, double checked today and ports still closed. Only remote access is through nabu casa right now supposedly. But I’ve got 2fa setup too so local neighborhood kid seems less likely.
The Trusted Networks auth provider defines a range of IP addresses for which no authentication will be required (also known as “allowlisting”). For example, you can allowlist your local network so you won’t be prompted for a password if you access Home Assistant from inside your home.
When you log in from one of these networks, you will be asked which user account to use and won’t need to enter a password.
I know.
But given that the user is new and has a new password then the list should be small.
If you log out as many devices as possible then you might be able to see if there is someone else there.
Why have passwordless login at all?
In my opinion, you clearly have an issue so try and stop the issue first then see what can be done to make life easier.