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 with the V2 Outlet or light, and set the correct Mac address if using agent (or IP, if not using Agent)
- If you are using Control4 4.0.0 or later , you must be using version 20250721 minimum for full support in all drivers. In particular, Versions older than 20241209 will not operate in X4 at all due to changes in Control4, and must be upgraded for any functionality.
- Ensure the driver is showing licenced or is operating in trial mode. If you upgraded from a purchased version older than 20240805, you may need to also migrate the licence to Chowmain marketplace
- V1 drivers are no longer supported. Ensure that all V1 drivers have been removed from project, and they are replaced with supported drivers. You may need to reboot controller after doing so
- Run Display Diagnostics, and check the output in Lua Terminal
- Ensure that the devices are running the latest firmware.
- In TPLink agent, ensure that the TPLink Account credentials have been added
Tapo P100 Outlet (And Other Tapo Devices) Unable To Authenticate
- Ensure that the Tapo P100 or Tapo device is running the latest firmware. Old firmware uses the Klap V1 protocol which is not supported
- In some circumstances, the device is unable to connect despite having the correct authentication details entered into Control4. This issue can be resolved by factory resetting the device and re-adding to the TAPO account using the Tapo mobile app. Generally, the driver itself requires no reconfiguration, and will simply work
V2 Device Has Ceased Operation
- Check the IP address in the Control4 driver is correct
- Ensure that the device can be controlled from the TPLink Mobile App
- Some firmware updates update the driver protocol to KLAPv2 (either via Automatic Update, or manually). Check Diagnostics in TPLink Agent which will be able to identify if the device is using the V2 driver, instead of the correct Klap device driver. If so, you will need to replace the V2 driver and replace with our KLAP drivers. EP25 and KP125 are two products which are known to have received updates which require the V2 driver to be replaced with KLAP
- UDP / broadcasting is not working correctly on the network. The most common cause of this is that the network has been reconfigured incorrectly, or IGMP has been enabled. Test with IGMP Snooping disabled, and if it works, reconfigure network for correct operation
- Ensure that all devices are in the same network segment. Some WiFi AP's (particularly Mesh) may not route UDP broadcast traffic correctly
- Check WiFi signal for device
KLAP Device Has Ceased Operation
- This may occur due to a change of the TPLink authentication details in the Mobile App. Please check the username and password in the TPLink Agent
- Ensure that the device can be controlled from the TPLink Mobile App
- If Authentication is failing and the device has been newly added, factory reset the device using the TPLink App. In some circumstances (particularly the Tapo P100), authentication may fail without the factory reset after the firmware update has been performed.
- If this device has just been added using Auto Setup, we have found in some cases that the device may have been detected incorrectly as a KLAP instead of V2 device. Delete the KLAP device and test using V2 Light / Outlet instead
Related Articles
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 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: 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 Particularly for Tapo devices, the device must be running the latest firmware to be supported Ensure that the ...
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 ...