Home assistant, Synology Docker - can't discover TP-Link Kasa Smart devices

Configuration
1

Hello! Brand new user here. I’ve installed Home Assistant in Docker on a Synology NAS. The container is up, I can log in to Home Assistant, so I figure I’ve installed it correctly LOL. So now I go to add some integrations. I have close to a dozen TP-Link Kasa Smart devices - HS 103 and HS105 plugs, and also number of bulbs. I see that the plugs are all on the supported list. Yet when I install the integration, and don’t give it a specific host IP (meaning I want it to discover everything on my home LAN that is a TP-Link Kasa Smart device), it tells me I have none. :slight_smile:

Yet if I give it a host IP of the devices (a HS103, a KL125 bulb, etc), it finds it right away, shows me the name I’ve assigned to it, etc. I can even control it from home assistant - turn it on and off, etc. So I know the integration, and my installation, is all working (mostly).
So I figure I must have something simple misconfigured, else it should find all the other devices automatically. But I don’t see anything that I have change, for that to happen. The docker container is running in bridge mode on the Synology.
What have I done wrong, that discovery is not finding any of my devices? I have 9 plugs (all supported), 3 bulbs, and even a TP-Link router (which may not be supported, that’s fine), and I’d rather not have to add each plug and device individually by IP address.

I’ve Googled, but all the instructions just say to let it discover devices, and no hints as to what to do when discovery doesn’t discover. LOL

Thanks!

2

Discovery doesn’t work in docker or at least it is hit and miss. I think its the broadcast messages that docker cant see.

3

ratz. Oh, well. I can manually add all those devices by looking up their IPs first; the majority of my smart home devices are TP Link devices.

Thanks!

4

When using host networking it works. With macvlan it supposedly works but i dont think tested this. Its bridge networking where this does not work

5

I wondered at that. I don’t see a way to set my docker container network to be the host network, only the bridged network. That may have been because of the way I installed the container (I followed these directions - How to Install Home Assistant on Your Synology NAS – Marius Hosting).

Well, since I haven’t really started using it yet, I suppose it won’t hurt if I completely remove the container and re-install. If so, maybe I’ll try the supervised way, using the virtual machine manager. My Synology supports that, I just don’t know how smoothly it will run that way …

So many questions! LOL

[edit] I decided to just delete the container, and re-create it. I tried duplicating the settings, but it still wouldn’t let me change the network. But since all I had in the container was 1 Kasa Smart plug, no great loss. And I did it remotely from work, via Synology QuickConnect. :slight_smile: When I get home tonight, I’ll try configuring it all over again …

Thanks

6

Not sure if host is possible in synology

7

It does work with host networking.And I came home, and it had discovered all of my Kasa Smart devices, my 2 Synologies, and my Roku stick. So now I have some devices to play with, and hopefully any new integrations with also Just Work.

Thanks!