TLDR: everything has to be on the same, non-isolated network
I started this with a clean install of HASSOS on a RPI 3 using the Raspberry Pi Imager Home Assistant image installed on 9 April 25. Nothing TP-Link was detected on the initial boot of Home Assistant .
I ran python-kasa and same deal, nothing found with discovery.
The HS105 is running in a Guest network on the Deco M5 and the RPI 3 is on the main network. I enabled âAllow Local Accessâ and the devices responded to ping! Ran python-kasa again, nothing found. Nothing discovered in Home Assistant.
In the Kasa app, there is a feature called âThird Party Compatibilityâ that is off by default. Enabled it, nothing in python-kasa nor Home Assistant.
Finally, I removed the device in the Kasa app forcing a factory reset. I then joined the device to the same main network (not Guest) that the RPI is on. Before I got back to my screen, Home Assistant discovered the device and was ready to add it.
I really hope to find a way to isolate these on my network and stop outbound traffic. Iâm pretty sure with DHCP static mappings, Firewall Groups, Firewall Aliases and some rules I can get that done. At least for now, itâs working.
This worked for me with my HS103 plugs. I couldnât figure out why python-kasa worked just fine with getting the first plug to join my wifi network, but it couldnât seem to detect any of my other HS103s. Once I unplugged the first working HS103, I was then able to use python-kasa to configure the second one as well. Thank you thank you! I never would have figured that out on my own.
Thank you! This helped a lot. After enabling Third party access, I was struggling and then I see your point of devices not being visible automatically. To make home assistant see the devices on my guest network (ATT router), I had to enable local LAN access to the guest network so that they can be seen in the main network. Home assistant was able to pick it up right after it. Thank you so much!
Iâm having quite a time fixing this issue.
I have a complete TP-Link Omada network at home. I also have many Kasa devices (8x HS103, 1x KP125M, 1x KP401, 3x HS200, 8x HS220, 1x HS210, maybe more). Iâve setup a bunch of VLANs on my Omada network and Iâve set all the IoT devices on VLAN 50. Iâve also created ACL rules so that my main PC (on VLAN 1) and my phone (on VLAN 10) can find these devices. I have Home Assistant running as a VM on my server on VLAN 1, and the VM has its own IP. From within HAOS, Iâm able to ping every single device on the network - all the rules seem to be working just fine. Iâve also got mDNS turned on so that broadcasting from VLAN 50 can travel to VLANs 1 and 10.
HOWEVER, Home Assistant TP-Link Smarthome integration is seeing 2 devices, my KP125M and the KP401 outside.
I thought there was an issue within my network, but now that I can ping all the devices very fast, I should be able to detect all these devices. I turned on the Third Party access from my app⌠but that doesnât seem to be doing much. Nothing has changed inside Home Assistant.
Could this be a password thing breaking the integration? So far I have no answer, and Iâve setup many Reddit posts to figure this out, but none have been successful. Anyone?
Same situation here. I tried having light on an IOT VLAN, which isnât even blocked off yet. Can ping IP/hostname no problem from HA. But canât add integration.
EDIT: Got it working. I used the HASS SSH addon and added both vlans in the network configuration. Then I tagged the HA port on the managed switch.
I was able to add the bulb no problem.
EDIT2: After having other issues w/ having HASS on 2 VLANs. I moved HASS to the same VLAN as the TPLink bulbs. Back to original issue. Sigh.
EDIT3: Then it just discovered the bulb and added it no problem.
Basicamente tenia dos redes locales. La primera me la generaba el ROUTER suministrado por el proveedor de internet en donde los dispositivos (Pc, tablet ,etc,etc) estaban en el rango de direcciones IP 192.168.1.1 a 192.168.1.254 y la segunda red local me la generaba una RED MESH (Deco BE3600 TP-LINK) y estaban en direcciones IP en el rango desde 192.168.68.1 a 192.168.68.254
Los dispositivos TAPO ESTABAN EN LA SEGUNDA RED. Tenian direcciones IP 192.168.68.xx y HomeAssistant estaba en la direccion fija(yo lo puse ahi) 192.168.1.253
Por tanto NO SE PODIAN VER . Cuando me di cuenta, ANULE EL USO DE LA PRIMERA RED excepto darle Internet (via Ethernet) al DISPOSITIVO PRINCIPAL de la RED MESH. Recargue HomeAssistant que paso de ejecutarse como 192.168.1.254:8123 a ejecutarse como 192.168.68.81:8123
En cuanto entre en AĂADIR INTEGRACION, seleccione TP-LINK y deje el HOST en blanco y al momento tenia una lista de todo mis dispoitivos TAPO
QUE CONTENTO ESTOY!!! LLevaba 20 dias peleandome con el HA y al final gane!!!
Following up fruizfâs post (thank you btw).
If the device your Home Assistant is running on is connected to more than 1 network (e.g. plugged into ethernet and on a wifi, or has a 2nd wifi dongle), then there is a setting in Settings/Stystem/Network called Network Adapter that tells HA which to use for plugins like Tapo. Make sure itâs set to the network the Tapo devices are on.
Mine weirdly also decided to change ip even though it had a fixed address from my dhcp.
I also first thought it was a network issue because i moved some zigbee around.
Tried connecting to new IP and get the same error
We really need a list with all those companies killing local control and avoid them in general
Edit: It didnât accept the login, but with reloading it decided to pretend nothing happened
Got my TP Link devices working again, on separate VLAN with new IPs. It was actually quite simple, after some frustrating hours trying a few other things (including a side quest down a âMatter & IPv6â rabbit hole).
HA on VLAN 50
TP Link devices on VLAN 100
Pre-step: Enable or reenable third party services in the Kasa app â despite having HA working with these devices yesterday, that setting was someone off for me.
Change device network by soft resetting to keep configs
1.1. KL135: off > on > off > on > off > on > wait for blinks > add ânewâ device in Kasa app > keep settings / donât erase when prompted
1.2 KP125M: on > hold power button for ~5s > when changes orange to blue release > add ânewâ device in app > âŚ
All devices should be on new wifi, and working in Kasa app
Home Assistant > Devices & services > âTP-Link Smart Homeâ
3.1 You should see you list of devices with warnings, devices will try to reconnect and fail, attempts to reconfigure and set a new IP will fail.
Go back to Home Assistant > Devices & services > Add integration > TP-Link > âTP-Link Smart Homeâ
4.1 Note: Leave your existing TP Link integration alone
Eeek same - and annoyingly I didnât know that as well as breaking a lot of automation, when you remove a Device in HA it nukes the History Stats for that device.
Not good.
I had two P110 plugs do this, I suspect it was something to do with the fact they were on a 5Ghz network maybe and not my 2.4Ghz but HA refused to see them, repeatedly. Until I indeed like others here, reset the plugs fully - 10 second long press, and added them back.
Annoyingly it was the only plug that has history stat stuff, and another that doesnât - but if any other plug went down Iâd have shrugged and reset it, but tried and tried to resurrect this one with no avail cos I need the dehumidifier to run! Itâs not like the others where I donât really care if HA sees itâŚthey are more used with Alexa. Only if Alexa was better at integration, Iâd have them connected to one thing.
I did wonder if this was all Zigbee interference, but then again the affected plugs werenât all near the sensors Iâve just got. I have noticed some strange stuff with wifi disconnects, but canât see how to move channels on my router.
If they do this again I will be asking for suggestions for more reliable plug switches, because these have been great with Alexa but nothing but a pain with HA - random disconnects, etc. This is the first time theyâve just refused to be seen - I got the âtry connect all failedâ AND the TPAP error even if I put the IP in, and then they werenât seen on any search unless I put the IP in and repeatedly disabled and re-enabled the Third Party setting in the app.
.
