When I first decided to build a smart home system, I had no idea what Home Assistant was or how to set it up on my local network. The first time I saw that URL with port 8123, I thought there was something wrong with my computer. I remember spending hours trying to figure out why I couldn’t access it from my phone, and whether I even needed to know what localhost meant. If you’re in the same boat right now, reading this because you’re confused about setting up Home Assistant on your local network, then this guide is exactly what you need.
Home Assistant is basically an open source platform that helps you control all your smart home devices from one central location. Instead of jumping between different apps for your lights, your thermostat, your security cameras, and all your other smart gadgets, Home Assistant brings everything together in one place. The best part? It runs on your own hardware, which means you’re in complete control of your data and privacy. You’re not sending information to some company’s cloud servers. Everything stays on your own devices, right there in your home network.
The local network setup is crucial because it’s how you actually access and control Home Assistant on a day to day basis. Whether you’re at home wanting to turn off the lights from your phone or adjust the temperature from your laptop, you’re going through that local network connection. Understanding how it works makes the whole experience so much smoother, and honestly, it’s not as complicated as it sounds once someone explains it properly.
Understanding the Basics
Let me break down some fundamentals that will make everything else in this article much clearer. When you see something like “http://homeassistant.local:8123”, this is the address you use to reach Home Assistant. The part “homeassistant.local” is the hostname, which is basically a friendly name for your Home Assistant server. Your computer and other devices on your network use this to find the right device instead of having to remember a complicated number.
The number 8123 at the end is the port. Think of ports like doors on a big building. Your device might have thousands of possible doors, but specific services use specific doors. Port 8123 is the door that Home Assistant has chosen to listen on. Some services use port 80 for regular web traffic, others use port 443 for secure traffic, and Home Assistant picked 8123. This is totally customizable if you want to change it later, but there’s rarely a good reason to.
Now let’s talk about localhost. This is a term that scared me when I first heard it, but it just means your own computer. When you’re sitting at the computer running Home Assistant and you type “localhost:8123” into your browser, you’re accessing Home Assistant on that same computer. It’s a shorthand way of saying “look at this computer I’m on right now.” If you’re on a different device on your network, you can’t use localhost because that device is not the one running Home Assistant. Instead, you’d use the IP address or the hostname.
The difference between local network access and remote access is important to understand. Local network access means you’re on the same WiFi network as your Home Assistant server. You’re physically connected to the same router. This is fast, secure, and what most people use daily. Remote access means you’re trying to reach Home Assistant from outside your home network, maybe from work or while you’re on vacation. This requires additional setup and different security considerations. For now, let’s focus on getting your local network access working properly.
Initial Setup Process
Before you can even think about accessing Home Assistant through your browser, you need to actually install it somewhere. Most people run Home Assistant on a Raspberry Pi, which is a tiny but powerful little computer that uses very little electricity and is perfect for always-on services like a smart home hub. Some people use old laptops, NAS devices, or dedicated servers. The installation process varies depending on what hardware you choose, but once it’s installed and running, the rest of the setup is basically the same.
When Home Assistant starts up for the first time, it automatically begins the onboarding process. This is actually really nice because it walks you through everything step by step. Your Home Assistant instance is now running on your local network, listening on port 8123. The first thing you need to do is open a web browser on another device on your network. This could be your phone, your laptop, your tablet, or any other device connected to the same WiFi network as your Home Assistant server.
Here’s where that address comes in handy. You’re going to type “http://homeassistant.local:8123” into your browser’s address bar. If your Home Assistant is set up and running correctly, you should see the Home Assistant login screen appear. Notice I said “http” and not “https” at this point. For local network access, you don’t need the secure protocol yet. That matters more when you’re accessing from outside your home network. If you see a blank page or an error, don’t worry. This is a common issue that usually means either Home Assistant isn’t running yet, or there’s a network connectivity problem that we can troubleshoot.
Once you successfully load the page, you’ll be prompted to create an account. This is your username and password for accessing Home Assistant. Make it something you’ll remember because you’ll be using it regularly. After you log in, Home Assistant will guide you through the initial setup process. You’ll choose your location, set your time zone, and decide on your preferred temperature unit. These things matter because Home Assistant uses them for automations and displaying information correctly.
Configuring Your Local Network
Finding your Home Assistant’s IP address is something you’ll probably need to do at some point. The hostname “homeassistant.local” works great when it’s available, but sometimes devices struggle to find it. Having the actual IP address as a backup is really useful. An IP address on your local network looks something like 192.168.1.100 or 10.0.0.50. These are private addresses that only work on your local network.
To find your Home Assistant’s IP address, you can check your router’s admin panel. Log in to your router using its IP address, usually 192.168.1.1 or 192.168.0.1, and look for a list of connected devices. You should see your Home Assistant device listed there with its IP address. You could also access Home Assistant through the hostname first, then go into the settings and look for network information. Once you have the IP address, you can use it directly in your browser like “http://192.168.1.100:8123” if the hostname stops working for any reason.
The port configuration is something most people leave alone, and honestly, there’s no reason to change it unless you have a specific issue. If port 8123 is somehow already in use by another service on your network, then you’d want to change it. You can do this in Home Assistant’s configuration files, but that’s beyond the scope of this beginner’s guide. Just know that if you do change it, you’ll need to remember your new port number when accessing Home Assistant.
When you have multiple devices on your network that you want to use for controlling Home Assistant, they all need to be able to reach that same address. This is usually automatic if they’re on the same network. Your phone, your laptop, your tablet, and any other device will all be able to navigate to “homeassistant.local:8123” if they’re on the same WiFi network. Sometimes WiFi can be weird, and one device might have trouble while another works fine. This is usually a network driver issue or a WiFi connectivity problem, not a Home Assistant problem.
Accessing from Different Devices
Using Home Assistant from your desktop computer is straightforward. You just open your web browser, type in the address, and you’re in. I usually leave a tab open in my browser with Home Assistant so I can quickly check on things or make adjustments. The web interface is responsive, meaning it works well whether your browser window is small or large. You can do pretty much everything from here that you can do from a phone, like controlling lights, viewing automations, and adjusting settings.
Mobile access is where Home Assistant really shines for many people. The official Home Assistant app for iOS and Android is specifically designed to work with your Home Assistant instance. You’ll still need to set it up to connect to your local network first. The app can automatically discover your Home Assistant on the network, which is really convenient. Once you’ve connected it, controlling your smart home from your phone is incredibly responsive and smooth. The app also handles things like notifications from automations, which the web interface doesn’t do.
Voice assistant integration is something a lot of people are curious about. If you have an Amazon Alexa or Google Assistant device, you can integrate it with Home Assistant to control your smart home using voice commands. This integration usually works over your local network as well, though the setup is a bit more involved. You’ll need to use something like the Nabu Casa cloud service or set up a local integration depending on which voice assistant you’re using. This is honestly one of the most convenient ways to interact with your smart home once it’s all set up.
Troubleshooting Common Issues
The most common problem I’ve seen is when someone can’t reach Home Assistant on their local network. Usually this happens because the device they’re using isn’t on the same WiFi network as the Home Assistant server. If you’re on the 5GHz WiFi band and Home Assistant is on the 2.4GHz band, or if one is on WiFi and one is on a wired connection, there might be communication issues. Most modern routers broadcast both bands, so try switching between them to see if one works better.
Sometimes you’ll see an error saying “cannot reach Home Assistant” or “connection refused.” This usually means either Home Assistant isn’t running at all, or there’s a firewall blocking access. If you just installed Home Assistant, it might still be starting up. Home Assistant takes a minute or two to fully boot and be ready to accept connections. If it’s been running for a while and still isn’t working, check if the process is actually running on your server. You might need to restart Home Assistant or restart the device entirely.
Port accessibility issues are less common on a local network compared to the internet, but they can still happen. If you have a firewall on your Home Assistant device, it might be blocking port 8123. Most firewalls allow local network traffic through automatically, so this is usually not the issue. If you suspect this is the problem, you can try accessing it from another device on the network. If that works but your current device doesn’t, the problem is probably with that specific device’s network settings, not with Home Assistant.
Network configuration fixes are sometimes necessary if something gets misconfigured. The easiest fix is always a restart. Restart your Home Assistant server, restart your router, restart the device you’re trying to access from. Most network problems go away after a restart. If they don’t, you might need to check your router’s DHCP settings to make sure it’s still assigning IPs correctly. You could also try giving your Home Assistant server a static IP address instead of a dynamic one, which prevents the address from changing and causing confusion.
Advanced Network Features
Setting up remote access is when things get more interesting. Many people want to be able to control their smart home even when they’re not at home. The safest way to do this is through the Nabu Casa service, which is offered by the Home Assistant creators themselves. This service gives you a secure tunnel to your Home Assistant instance and handles all the security stuff for you automatically. It’s a paid service, but it’s very reasonably priced and takes the complexity out of remote access.
If you don’t want to use a paid service, you can set up remote access using DuckDNS and port forwarding. DuckDNS is a free dynamic DNS service that lets you use a friendly domain name instead of your ever-changing home IP address. You’ll set up a DuckDNS account, then configure your Home Assistant to use it. You’ll also need to forward port 8123 on your router to your Home Assistant server. This is more complex and requires you to manage SSL certificates yourself, but it’s completely free and gives you full control. Honestly, for most people, the Nabu Casa service is worth the cost because you don’t have to worry about any of this.
SSL certificate configuration is important when you’re accessing Home Assistant over the internet. An SSL certificate encrypts the data between your browser and Home Assistant, protecting your login information and sensitive data. When you use Nabu Casa, this is all handled automatically. If you’re using port forwarding and DuckDNS, you’ll need to set up a certificate using Let’s Encrypt, which is free. Home Assistant actually makes this pretty easy with an add-on that automates the whole process.
Security Considerations
Local network security might not seem like a big deal since you’re on your own WiFi at home, but it’s still important to think about. Your local network is only as secure as your WiFi password. If someone knows your WiFi password or manages to connect to your network, they could potentially access Home Assistant and control all your smart home devices. This is why it’s important to have a strong WiFi password that you don’t share with too many people.
Password protection for Home Assistant is your first line of defense. Make sure your Home Assistant account password is strong and unique. Don’t use the same password you use for email or other important accounts. If someone gets access to your Home Assistant account, they can’t just control your smart home, they might also be able to see personal information about your home and habits. Home Assistant supports two-factor authentication, which adds an extra security layer. If you want to be really secure, I’d recommend enabling this.
Device authentication can be configured in Home Assistant to limit which devices can access it. You can create multiple user accounts with different permission levels. For example, you might give family members a basic user account that can turn lights on and off but not access advanced settings or automations. You can also revoke access from devices that you no longer want to have access. This is especially useful if you’re concerned about someone’s phone being stolen or if you remove it from your family group.
Frequently Asked Questions
Can I access Home Assistant if I’m not on my home WiFi?
Yes, but you need to set up remote access. This requires additional configuration like Nabu Casa or port forwarding with DuckDNS.
What if I forget the hostname?
You can always use the IP address instead. If you forget both, you can check your router’s admin panel or restart Home Assistant to figure out what address it’s using.
Is port 8123 standard?
It’s the default port for Home Assistant, but it’s not a standard port used by other services. This is why Home Assistant chose it, to avoid conflicts.
Can I change the port?
Yes, you can change it in the configuration, but there’s usually no reason to. Stick with 8123 unless you have a specific conflict.
Do I need a static IP for my Home Assistant?
Not required, but it’s helpful. A static IP means the address never changes, which makes it easier to remember and less likely to cause issues.
What’s the difference between localhost and homeassistant.local?
Localhost only works on the same device running Home Assistant. Homeassistant.local works from any device on the network.
Is Home Assistant safe to use?
Home Assistant itself is very safe. It’s open source and maintained by a large community. Your security depends on having strong passwords and proper network configuration.
Can I use Home Assistant without internet?
Absolutely. Local network access works without any internet connection at all. You only need internet if you want remote access from outside your home.
Conclusion
Getting Home Assistant set up on your local network really isn’t as complicated as it might seem at first. Once you understand what localhost means, what port 8123 is, and how to find the right address to type into your browser, everything else follows pretty logically. I remember how frustrating those first few minutes were when I couldn’t figure out how to access it, but once I got it working, I realized it was actually quite straightforward.
The whole point of setting up Home Assistant on your local network is to give you easy, immediate access to control your smart home from any device at home. Whether you’re using your phone, your laptop, or any other device connected to your WiFi, you can quickly and easily manage all your smart devices from one central location. The local network access is fast, responsive, and doesn’t depend on your internet connection being perfect. It’s the foundation that everything else builds on.
As you get more comfortable with Home Assistant, you might want to explore remote access, advanced automations, or integrating more devices. All of that comes later. Right now, focus on getting comfortable with accessing Home Assistant on your local network and using the basic features. Once you’re confident with that, everything else is just additional learning on top of a solid foundation. Home Assistant is a powerful tool, but it becomes manageable when you take it one step at a time, and local network access is the perfect place to start.
