Home Assistant Static IPs: Which Devices Need Them and How to Set Them Up
The most common reason Home Assistant integrations show “Entity unavailable” isn’t a bug — it’s an IP address change. A device got a new address from DHCP, Home Assistant still has the old one, and the integration breaks silently.
The fix is assigning stable addresses to the right devices. Here’s how to think about which ones need them.
Three tiers of devices
Critical — always needs a static IP:
- The Home Assistant server itself (other devices need to find it)
- Your router, switches, and access points
- NAS devices that HA accesses for media or backups
Integration-dependent — usually needs a static IP:
- Sonos speakers (required for reliable audio automation)
- Smart TVs and streaming devices (Samsung, LG, Chromecast, Apple TV)
- IP cameras and NVR systems
- Smart home hubs (Philips Hue Bridge, SmartThings)
- MQTT broker if running separately from HA
Hub-connected — usually fine with DHCP:
- Zigbee and Z-Wave devices (they talk through their coordinator, not directly by IP)
- Cloud-API WiFi devices (the cloud finds them regardless of local IP)
- Bluetooth sensors
The practical rule: if Home Assistant communicates with the device directly by IP, give it a stable address. If it communicates through a hub or cloud, the IP doesn’t matter.
DHCP reservation vs. static on the device
There are two ways to assign a stable IP:
DHCP reservation (recommended for most devices): You tell your router “always give this MAC address this IP.” The device still uses DHCP, but always gets the same address. If the device gets factory reset, it comes back to the same IP automatically.
Static IP configured on the device: You configure the IP directly on the device. Works even if DHCP is unavailable. Required for your router itself, and useful for servers that need to boot before DHCP is available.
For most smart home devices, DHCP reservation is better — it’s centralised, survives device resets, and is easier to change later.
A simple addressing plan
Organise your range by device type:
| Range | Purpose |
|---|---|
| .1–.10 | Network infrastructure |
| .11–.20 | Home Assistant + home servers |
| .51–.100 | Smart home hubs and bridges |
| .101–.150 | Media devices (Sonos, TVs, Chromecast) |
| .151–.200 | Cameras and security |
| .201–.254 | DHCP pool (phones, laptops, guests) |
Keep your DHCP pool at the top of the range so new devices never accidentally get an IP you’re using for something important.
When devices change IPs despite your best efforts
It happens. When a HA integration breaks:
- Check your router’s client list for the device’s current IP
- Match it by MAC address to identify it
- Either add a DHCP reservation for that MAC, or reconfigure the HA integration to point to the new IP
For discovery-based integrations (Chromecast, Sonos), removing and re-adding the integration often works — HA will find the device at its new address.
Document what you assign
The problem with static IPs isn’t the setup — it’s forgetting what you’ve assigned. Before you give a new device an IP, check your records. Before you add a DHCP reservation, verify the MAC is correct (some devices have different WiFi and Ethernet MACs).
Netory is designed for exactly this: a local-first inventory of your network so you can see what’s assigned, add new devices to the right pool, and troubleshoot without guessing.
Track your Home Assistant network in Netory — free for iOS and Android.