Control4 TPLink - VLAN Support

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 difficult to deploy, and most installers end up moving the devices back to the same segment as Control4 

Because KLAP uses TCP for control however, KLAP devices on VLAN's may be a lot easier for many installers to configure exclusively for control as standard routing may work in some cases.  

Third Party Compatibility

Third Party Compatibility must be set when on the same VLAN/Network segment/WiFi network as the device. We have found that factory resetting the devices may also not correctly enable this setting.

If this has been set from another VLAN / Network, return to the same VLAN, and turn off and back on Third Party Compatibility. Otherwise the option may not be set correctly.  

Ports Required

The Chowmain TPLink Driver uses the following ports for control and discovery. This info may be incomplete and additional network tools may be required to troubleshoot the setup and configuration 
  1. 9999 Outbound / Inbound (UDP. Unicast and Broadcast. For V2 protocol and discovery)
  2. 20002 Outbound / Inbound  (UDP, Unicast and Broadcast. KLAP Discovery)
  3. 80 Outbound (TCP. Unicast. KLAP Control) **PLEASE NOTE. THIS IS NOT HTTP. DO NOT USE A HTTP PROXY**

    • Related Articles

    • 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 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 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: 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 ...