Quick answer
Open http://homeassistant.local:8123 in a browser on your home network. If that name does not resolve, use http://<device-IP>:8123 with your device’s IP address. Home Assistant has no default username or password. You create the owner account yourself the first time you open it.
Open Home Assistant on your local network
Home Assistant listens on port 8123 by default, so the address you type needs that port:
http://homeassistant.local:8123uses a local name. It often works, but some Android phones, VPNs, VLANs and Windows setups cannot resolve.localnames.http://<device-IP>:8123works when your computer is on the same network. Find the IP in your router’s list of connected devices, or on the console of a Home Assistant OS device.- If you set up SSL in the
http:section ofconfiguration.yaml, onlyhttps://works, even on your home network.
The device has to be on and fully started. On Home Assistant OS, the first boot can show “Preparing Home Assistant” for up to about 20 minutes. If the page still will not load, see why you can’t connect to your Home Assistant.
The companion app uses the same local address when your phone is on your home Wi-Fi.
Create your owner account
There is no factory login. The first time you open Home Assistant, the setup wizard asks you to create the owner account: a name, a username and a password. Usernames are lowercase and have no spaces.
The owner account has full administrator rights, so choose a long, unique password. Anyone who can reach your login page can try to guess a password, which is one reason to turn on multi-factor authentication (MFA) later.
Log in with the username
When you log in, use the username, not the display name you entered during setup. If you have forgotten the username, you can list the accounts from the device console:
auth list
On Home Assistant OS, run this at the console (a monitor and keyboard, or a VM console). If you have also forgotten the password, see how to reset your Home Assistant password.
Manage users and who can log in
Admins add and edit users under Settings > People > Users. The Users tab appears only when Advanced mode is turned on in your profile.
For an account that never needs remote access, turn on Can only log in from the local network. That setting blocks remote logins for that one account and leaves the others alone.
Create a long-lived access token
Long-lived access tokens let scripts, dashboard tools and other apps call the Home Assistant API. To create one:
- Select your profile at the bottom left of the sidebar.
- Open the Security tab.
- Scroll to Long-lived access tokens and select Create token.
- Give the token a name that says what will use it, then copy it.
Home Assistant shows the token only once. If you lose it, delete it and create a new one. Long-lived tokens can last up to about 10 years, so review them regularly and revoke any you no longer use. A token has the same permissions as the account that created it, so treat it like a password.
Use the token with the API
Send the token in the Authorization header. This quick check should return a short “API running” message:
curl -H "Authorization: Bearer <your-token>" http://homeassistant.local:8123/api/
The REST API lives under http://<host>:8123/api/. Logins through the web interface and the companion app use shorter-lived access tokens. Those expire after 30 minutes and renew through refresh tokens, so you do not need to manage them yourself.
Does Home Assistant support single sign-on?
As far as we can confirm, Home Assistant core does not include built-in single sign-on (SSO) with OpenID Connect, SAML or LDAP. Check the current release notes, because this can change.
If you want SSO, there are three routes, and each one has trade-offs:
- A community OIDC integration. Community projects can add OpenID Connect login through HACS, the Home Assistant Community Store. These are not official features, and they need upkeep when Home Assistant updates.
- A scripted login with
command_line. Some people write login scripts against a directory server such as LDAP. Support depends on your setup and is not official. - A login layer in front of Home Assistant. Products such as Authelia or authentik can protect the web address. Companion apps and some integrations may then fail unless you add bypass rules for their own connections.
Trusted-networks login is sometimes mistaken for SSO. It is not. It lets listed addresses skip the password, so it should never include internet-facing ranges.
Reach Home Assistant from outside your home
Local addresses only work on your home network. For remote access you need a secure route, such as Home Assistant Cloud, a VPN like Tailscale, or a reverse proxy with HTTPS. Read how to set up secure remote access to Home Assistant before you open any ports on your router.
Linking Alexa or Google Home also needs an address the cloud service can reach. A VPN-only setup does not cover that by itself.
Keep your login secure
- Turn on multi-factor authentication for each account. You can set up a TOTP app under Profile > Security.
- Do not forward port 8123 directly to the internet without TLS and MFA in place.
- Revoke long-lived tokens you no longer use, under Profile > Security.
- Keep Home Assistant up to date, and read the release notes first. The update and reboot guide covers the steps.