Hello! I have a Kasa smart plug mini that I want to add to my Home Assistant but it is in another subnet that somehow is not discoverable to Home Assistant. How can I tell Home Assistant to look for devices in another subnet? Thanks in advance.
I do this in the router. You can assign devices static IP’s based off the of devices mac address. Then when the device with that mac address connects to the router, the router will assign it the static IP you told it to. You can google “[router make/model] static IP assignment” for instructions for your particular router. So just assign it an IP within your subnet.
There is no need to wait until the Kasa device is diacovered. You can manually add a new device and the first thing you’re being asked is the device’s IP address.
Yup! I’ve done this a few times and it works great. Discovery doesn’t seem to ever work that way but if you manually specify the IP there’s no issue.
I used the command line tool to get the plug on the network and then manually added to Home Assistant without ever touching the Kasa app.
As others have said, just add the ip address to the kasa integration. Mine are all on the same subnet as my HA server, but I don’t ever wait for discovery - I just add the ip every time I had a device and it’s done
Here’s a video I made a while back that shows how to find the device and how to add it.
Manually adding the IP in the integration won’t work if the device is on a different subnet. You simply can’t communicate between devices on different subnets. The device needs to be assigned an IP withing the routers subnet range before this will work.
Wrong. I’ve seen me do it. In fact, I literally did it in the video I posted, so if you watch it, you can see me do it too. Lol that HA server was in 10.1.5.0/24 and the switch was in 10.1.6.0/24
You’re aware you can have multiple subnets in a network, right? I have 6 subnets here…
If you have a subnet mask of /24, then 10.1.5.xx is a different network than 10.1.6.xx and devices on those networks can’t “see” each other unless you are using a managed switch- which isn’t cheap.
Why do you need so many networks. The /24 subnet gives you IPs addtresses for 254 devices- isn’t that enough?
Oh sure. I’m also aware that doesn’t just happen by itself and takes some setup and know how. I’m guessing, by the actual asked question of the OP, that they aren’t set up that way and was trying to lead them to the easiest solution, which is fixing the IP of the one device that got assigned an IP outside of the range. So, you win your pedantic argument, but not sure you helped solve the issue at all. Probably just added to the confusion. You should take your advice that you deleted.
Uhh, I didn’t delete anything, so…
If he’s not set up that way, then how did it get assigned an ip? Something is on that range handing out IPs, so there’s dhcp. Perhaps you should stop being so defensive, and assuming people don’t know what they are talking about, and instead help the guy instead of giving bad info?
The issue he’s having is simply that since the KASA switches are in a different network, and discovery takes place by broadcast, they aren’t automatically found. Broadcast traffic does not cross subnet boundaries.
I gave him the solution, while you assumed he was an idiot. You tell me which one of us was more helpful.
Best of luck with your attitude…
My FIOS router uses the term “Permanent Lease” which is the technically correct term. The default lease time in most DHCP servers is 24 hours. At the end of the lease time, the DHCP server may reissue the IP address to a new device if it’s needed. But unless you have more than 254 devices this won’t happen. Most router DHCP servers will remember the MAC addresses it previously assigned an IP address to and if it hasn’t been reassigned to a new device then your current device will renew with the same IP address it had for the prior lease term. DHCP servers are not all the same.
The bottom line is that without extraordinary routing rules, devices in one subnet are invisible to another network.
So, @crc111, how did you wind up with two different networks?
There’s literally a managed switch on Amazon for $35 and more and more people are starting to use VLANs to secure their network. I would say this is especially true in the Home Assistant realm.