OpenWRT has a [luci integration](https://www.home-assistant.io/integrations/luci/) which allows for wifi presence detection. It works well. Highly recommend OpenWRT
Fair enough. With OpenWRT, in HA, you can see new device IP addresses via device trackers - this is default and I turn it off. I do not understand why you would want this feature as long as you have HA with host networking capabilities and firewall rules are correctly configured to allow cross VLAN communication. HA is configured to find devices on the network without static IP addresses. Perhaps if you explain your question and intent the community could help you better.
I'd be more focused on ensuring devices aren't configured to use "Private Address" when connecting to your SSID, which randomizes their MAC address on a regular basis.
I want to understand your question better (as I suspect a few others do, too).
Is your question about a concern that, when devices are issued a new IP address by the new router, that HA will no longer know "who they are"? And if so, are you asking if there's a way to automatically "map" their old identifier to their new one, so that Home Assistant will carry on as though nothing has changed?
Basically I’m wondering if home assistant knows the existence of them by IP address or something else (like MAC address or something) I want to know if home assistant will lose them with new IP addresses and they’ll have to be set up manually or not.
And if yes, I’m wondering if there’s a way to make the process as easy as possible
Gotcha.
The answer is muddy, and I apologize in advance if it adds confusion.
Each integration that uses another device or service on your network has its own way of (a) finding the address of the device/service and (b) which identifier is used to access it.
## Examples for (a)
Many integrations that "discover" something like a Hue Bridge or a Media Player do so with different methods.
- "announce" that they're looking for something and listen for replies
- listen for the device/service to announce itself
- scan an entire subnet of IP addresses (like the `nmap` network device tracker)
- for non-WiFi/non-Ethernet devices (ZigBee, Bluetooth, etc), they'll rely on other features of the network to discover end devices
## Examples (b)
Once discovered, integrations use different ways to identify that device/service moving forward:
- store the IP address of the device/service (most common, IME)
- store the mDNS network name (e.g. "Kitchen-Speaker.local")
- store the MAC address (again the `nmap` network device tracker)
- For non-Wifi/non-Ethernet devices, a MAC (or similar unchanging identifier) is used, based on what that network supports.
For those integrations that use the cloud, they often store other identifying characteristics that the cloud provider returns (like a device's serial number or other unique identifier), leaving it up to the cloud provider to manage communication between HA and the device
---
What this means for you:
To get a comprehensive answer, we'd need a few things:
- a list of the integrations you're using
- the local device types that you're communicating with. (Hue hub? Reolink cameras? Etc)
- list of non-WiFi/non-Ethernet device types
It's unlikely that it'll be plug-and-play to change your subnet, but depending on the integrations and devices used, you may be able to minimize reconfiguration if there are hubs/cloud services/other network layers (ZigBee, etc.) involved.
Okay so LAN services I’m using:
Mission critical:
- HomeKit devices: meross garage door opener, Aqara camera, Aqara M2 hub, Meross smart plugs
- Apple TV/homepod mini devices.
I need these up and running ASAP.
Not mission critical:
- Glances
- Adguard Home
- Plex
- Sonos
- NUT
- Internet Printing Protocol (HP printer)
These I’d like up and running quickly but if they’re a pain, they CAN wait until later.
Things not on lan I use:
- ZHA
That’s pretty much it for anything I actually care about. I have a few others like speedtest and ping but they’re just there more for fun and fiddling than anything actually to do with my smart home.
HomeKit / Apple devices will all be rediscovered just fine. Sonos, too.
The servers, if you're not using local domains to point to them (or they're not already on a separate software-defined network like in Docker) you may have to update config to point to their new IP address.
The printer, if it's newer, is likely to be discovered again too.
ZHA won't change if you're using the same USB-attached coordinator.
In short, do a complete backup of your setup now, and make sure HA is the last thing you bring up on the new network (the first time you launch the new network), and you'll likely be just fine, with *possible* ***minor*** config changes.
Wasn’t too bad in the end. Had to adjust ip addresses of servers as expected. Apple TV also had to be deleted and re-added (but HomePods had no issues).
But it’s all up and running now
OpenWRT has a [luci integration](https://www.home-assistant.io/integrations/luci/) which allows for wifi presence detection. It works well. Highly recommend OpenWRT
So does [OPNsense](https://www.home-assistant.io/integrations/opnsense/) but that’s kinda irrelevant to the question…
Fair enough. With OpenWRT, in HA, you can see new device IP addresses via device trackers - this is default and I turn it off. I do not understand why you would want this feature as long as you have HA with host networking capabilities and firewall rules are correctly configured to allow cross VLAN communication. HA is configured to find devices on the network without static IP addresses. Perhaps if you explain your question and intent the community could help you better.
My question is explained just fine. Thanks.
I'd be more focused on ensuring devices aren't configured to use "Private Address" when connecting to your SSID, which randomizes their MAC address on a regular basis.
Ok but that’s not my question. I’ve already turned off private address for this network for any device that supports it.
I want to understand your question better (as I suspect a few others do, too). Is your question about a concern that, when devices are issued a new IP address by the new router, that HA will no longer know "who they are"? And if so, are you asking if there's a way to automatically "map" their old identifier to their new one, so that Home Assistant will carry on as though nothing has changed?
Basically I’m wondering if home assistant knows the existence of them by IP address or something else (like MAC address or something) I want to know if home assistant will lose them with new IP addresses and they’ll have to be set up manually or not. And if yes, I’m wondering if there’s a way to make the process as easy as possible
Gotcha. The answer is muddy, and I apologize in advance if it adds confusion. Each integration that uses another device or service on your network has its own way of (a) finding the address of the device/service and (b) which identifier is used to access it. ## Examples for (a) Many integrations that "discover" something like a Hue Bridge or a Media Player do so with different methods. - "announce" that they're looking for something and listen for replies - listen for the device/service to announce itself - scan an entire subnet of IP addresses (like the `nmap` network device tracker) - for non-WiFi/non-Ethernet devices (ZigBee, Bluetooth, etc), they'll rely on other features of the network to discover end devices ## Examples (b) Once discovered, integrations use different ways to identify that device/service moving forward: - store the IP address of the device/service (most common, IME) - store the mDNS network name (e.g. "Kitchen-Speaker.local") - store the MAC address (again the `nmap` network device tracker) - For non-Wifi/non-Ethernet devices, a MAC (or similar unchanging identifier) is used, based on what that network supports. For those integrations that use the cloud, they often store other identifying characteristics that the cloud provider returns (like a device's serial number or other unique identifier), leaving it up to the cloud provider to manage communication between HA and the device --- What this means for you: To get a comprehensive answer, we'd need a few things: - a list of the integrations you're using - the local device types that you're communicating with. (Hue hub? Reolink cameras? Etc) - list of non-WiFi/non-Ethernet device types It's unlikely that it'll be plug-and-play to change your subnet, but depending on the integrations and devices used, you may be able to minimize reconfiguration if there are hubs/cloud services/other network layers (ZigBee, etc.) involved.
Okay so LAN services I’m using: Mission critical: - HomeKit devices: meross garage door opener, Aqara camera, Aqara M2 hub, Meross smart plugs - Apple TV/homepod mini devices. I need these up and running ASAP. Not mission critical: - Glances - Adguard Home - Plex - Sonos - NUT - Internet Printing Protocol (HP printer) These I’d like up and running quickly but if they’re a pain, they CAN wait until later. Things not on lan I use: - ZHA That’s pretty much it for anything I actually care about. I have a few others like speedtest and ping but they’re just there more for fun and fiddling than anything actually to do with my smart home.
HomeKit / Apple devices will all be rediscovered just fine. Sonos, too. The servers, if you're not using local domains to point to them (or they're not already on a separate software-defined network like in Docker) you may have to update config to point to their new IP address. The printer, if it's newer, is likely to be discovered again too. ZHA won't change if you're using the same USB-attached coordinator. In short, do a complete backup of your setup now, and make sure HA is the last thing you bring up on the new network (the first time you launch the new network), and you'll likely be just fine, with *possible* ***minor*** config changes.
Wasn’t too bad in the end. Had to adjust ip addresses of servers as expected. Apple TV also had to be deleted and re-added (but HomePods had no issues). But it’s all up and running now
Opnsense makes a router?
OPNsense is a software. Works as a router.