Control4 TP-Link: Failed To Connect. Handshake 1 Failed

Control4 TP-Link: Failed To Connect. Handshake 1 Failed

Problem

When trying to connect in Control4 to a TP-Link KLAP Device, Control4 shows "Failed To Connect. Handshake 1 Failed"

Solution

  1. Particularly for Tapo devices, the device must be running the latest firmware to be supported
  2. Ensure that the username and password is set correctly in the KLAP Device (or TPLink Agent) properties
  3. Some devices (in particular the KP303 and Tapo P110) may require Third Party Compatibility enabled in the KASA/Tapo App. More information is provided by TP-Link . After enabling this option, in rare cases, it may switch the protocol back to the old protocol, and you may need to test with the V2 outlet driver (which may be able to connect instead)
  4. We have found that some devices such as the P100 may require a factory reset for correct operation 
  5. Check that the IP Address is correct 

    • Related Articles

    • Control4 TPLink: Failed to connect. Authentication Failed

      Symptom When attempting to attempt to connect to a KLAP based Tapo or KASA device, Connection Status shows "Failed to connect. Authentication failed" Solution Ensure you are using Version 20251218 or later. Check and ensure you are using the latest ...

    • Control4 TP-Link: Unable to Control Device

      General Issues If the logs show "COMMS_MANAGER: Unable to fetch device info: -1" . You may need to enable third party compatibility using: https://www.tp-link.com/au/support/faq/4416/ . If Device still ceases to work, replace the KLAP Device driver ...

    • Control4 TP-Link: Logs Show Unable to fetch device info: -1. Unable to control device

      Problem Description In some cases (in particular the KP303), it may be detected during autosetup, the KLAP device is added and the device says Connected Successfully. However, the properties say unknown, and when logs are set to print, and DEBUG ...

    • Control4 TPLink - VLAN Support

      Support for VLANs Chowmain is unable to provide technical support for configuration via VLAN, and recommends deployment of TPLink devices on the same network segment as the Control4 Primary Controller. In our experience, discovery is particularly ...

    • Control4 TP-Link: Driver Not working in Control X4 or Later

      After Upgrading to Control4 X4 or later, TPLink KASA / TAPO / V2 Stops working and may display errors during driver start Solution The original TPLink V1 drivers must be deleted from the project and upgraded to V2 / KLAP to support X4. A licence ...