Same issue. Bought a C220 indoor and a C550 outdoor. TP-Link Smart Home add on only asks for ip-address. When I enter it, i get an error: Connection error: Timed out getting discovery response for ip-address. Hostname, also error. Leaving it empty also produces error: “No devices found on the network”. Both cameras work fine in the Tapo-App. What is wrong??
same issue here!
I have a C425 Camera just I just purchased. Its configured using the Tapo app and it works fine independent of Home Assistant.
The problem is when I try to use the TPLink or Tapo integration in HA to add the camera, it gives me an error if I do NOT enter the ipaddress:
‘TP-Link Smart Home
No devices found on the network’
If I enter the IP address, username and password for my tapo account,
connection error (Connection error: Unable to connect to the device)
Not sure why this is so difficult to setup. Anyone have any ideas?
Same here except that it is with P100 plugs.
All was working fine until I deleted the integration and readded it so it might be something in the latest release?
I also have problems. I have three P100 plugs. One is connected fine. The other two have “Authentication expired” errors. When I re-enter my username and password on the first device I get this:
Invalid authentication: Server response doesn't match our challenge on ip 192.168.1.80
On the second device I get a different error when I re-enter my username and password:
Connection error: get_device_info not found in {'component_nego': {'component_list': [{'id': 'device', 'ver_code': 2}, {'id': 'firmware', 'ver_code': 1}, {'id': 'quick_setup', 'ver_code': 3}, {'id': 'time', 'ver_code': 1}, {'id': 'wireless', 'ver_code': 1}, {'id': 'schedule', 'ver_code': 2}, {'id': 'countdown', 'ver_code': 2}, {'id': 'antitheft', 'ver_code': 1}, {'id': 'account', 'ver_code': 1}, {'id': 'synchronize', 'ver_code': 1}, {'id': 'sunrise_sunset', 'ver_code': 1}, {'id': 'led', 'ver_code': 1}, {'id': 'cloud_connect', 'ver_code': 1}, {'id': 'iot_cloud', 'ver_code': 1}, {'id': 'default_states', 'ver_code': 1}, {'id': 'auto_off', 'ver_code': 2}]}, 'get_device_info': <SmartErrorCode.JSON_ENCODE_FAIL_ERROR: -1004>, 'get_connect_cloud_state': {'status': 0}} for device 192.168.1.56
I also notice “migration errors” for all of my devices on the Tapo integration page of the HA UI. I don’t know if it’s related. The log shows this for each device:
2024-11-22 12:02:02.765 ERROR (MainThread) [homeassistant.config_entries] Error migrating entry Tapo P100 Gill for tapo
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 978, in async_migrate
result = await component.async_migrate_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/tapo/__init__.py", line 73, in async_migrate_entry
await migrate_entry_to_v8(hass, config_entry)
File "/config/custom_components/tapo/migrations.py", line 15, in migrate_entry_to_v8
device = await connect(config=create_device_config(config_entry), session=session)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/plugp100/new/device_factory.py", line 43, in connect
protocol = await _get_or_guess_protocol(config, session)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/plugp100/new/device_factory.py", line 65, in _get_or_guess_protocol
return await _guess_protocol(config, session)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/plugp100/new/device_factory.py", line 102, in _guess_protocol
raise InvalidAuthentication(config.host, config.device_type)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/plugp100/new/errors/invalid_authentication.py", line 3, in __init__
super(f"Invalid authentication error for ${host}, ${device_type}")
TypeError: super() argument 1 must be a type, not str
2024-11-22 12:02:02.787 ERROR (MainThread) [DeviceFactory] None of available protocol is working, maybe invalid credentials
I’m using v3.1.2 of the Tapo integration. All three devices have previously been working fine together.
My problem was that Synology router has a button that works as hw on/off for wifi network and kids like to push buttons. The app on your phone can smoothly switch between LAN and internet access over cloud without noticing, that’s why it looks like the plugs are online. However, it is quite beyond me why the plugs were online without wifi as it was certainly by the wifi being off
I just bought two 115 plugs to track energy and a set of 125M’s. I could not get the 115 plugs to authenticate. The integration would never accept my U/PW for the 115’s, while I had zero issues with the 125M’s. I’m not sure why that plug has an issue or how best to elevate the observation. The 115s will be going back because, without the HA integration, I won’t be able to automate them as planned.
I’ll also note that I’m trying to add new Tapo P115 plugs into Home Assistant. I have tried using the TP-Link Smart Home integration, automatic host discovery works, but credentials for my TP account does not work, with error: Invalid authentication: Server response doesn’t match our challenge on ip [X.X.X.X].
P115 is listed as a supported device: TP-Link Smart Home - Home Assistant
I read elsewhere that “changing” the password in the Tapo app, but changing it to the original password, then restarting HA has worked for some people. Maybe worth a try.
Worked for me @itm1960 - THANK YOU!
That did the trick, thx!
Hello everyone, I discovered the issue in my case. Avoid using special characters in the camera account password, especially characters like #. These can be problematic because they may be interpreted as comment markers, leading to unexpected behavior.
Also worked for me, thanks a lot
Same problem. I think that I know why. The first device I clicked “Add” in the Tapo app. The second and third device auto discovered as soon as I plugged them in. The first device is no problem adding in Home Assistant. The others I cannot add. This has to be the reason! Please help.
I think you are on the right track! I have two P100 plugs, one is working fine, the other can’t authenticate. I have now removed the non-functioning P100 from the Tapo app and re-added it using the “Add” button. Now everything is working fine. At least for the time being…
Maybe this work around works for you as well?!
Ensure you have Third Party Compatibility turned on in the official Tapo app on your smartphone.
Tapo App → Me → Tapo Lab → Third-Party Compatibility → On
This worked for me
Alright, I’ve figured it out! I had a good intuition initially that it had something to do with tss, the solution only became clear once I found what TSS was about…
tss = “TP-Link Simple Setup” - TSS: Smart, Swift, and Simple TP-Link Device Setup - Home Network Community
tss is an Oboarding protocol which allows new devices that you plug in to obtain the configuration (credentials and WiFi password) from existing devices on your network.
If you plug in a new device and there are existing Tapo devices on your network that also support tss, then this is the onboarding protocol that will be used, and it would appear that it completely breaks local KLAP. I suppose this might be because the credentials are shared with additional hashing or in a different format when the device uses tss onboarding. So there is indeed a different treatment when tss is used to onboard new devices.
Here is how you can fix the KLAP auth issue on your devices:
1. Physically remove all existing similar TP-Link devices from your house power sockets.
2. Plug in only ONE device
3. Press the power button for 8 seconds (until you see the LED flashing green) - this will factory reset the device
4. Open the Tapo app on your smartphone and make sure your smartphone bluetooth is on
5. Find the device model to add, and wait for it to be found (make sure you are close to the device)
6. Add the device… This will effectively do a “tp-link” onboarding as opposed to a “tss” onboarding
7. Once the device is added, auth should now work. And --debug should read ‘obd_src’: ‘tp-link’ (if not it means you have other TP link devices that support tss plugged in somewhere in your house).
8. Repeat the procedure for all your devices.
Hope this helps! All my P110M are now working as expected with Home Assistant and they are all on the latest firmware.
This worked for me as well. I rfe-added in the Tapo app manually this time rather than accepting the auto-discover. Then restarted HA and added the plug again and this time my credentials were accepted
My Solution on a Tapo C520WS: Delete the camera in Tapo Control, give her in the Tapo App a new IP(!) (Generell static IP’s are a clever idea for the Tapo Control i discovered), and reconnect it. No chance on the same IP, there is something in the memory/storage in Tapo control. After reconnecting the Camera with a new IP, everything works (need to adjust the Preset-Automation, but thats alll)