CONTROL4 DOOYA: Devices will not discover

CONTROL4 DOOYA: Devices will not discover

The Control4 Dooya driver communicates with all Dooya Connector Bridge devices on the local network using UDP multicast. This allows the driver to broadcast discovery and control messages that can be received by all Dooya bridges simultaneously, enabling efficient and reliable communication.

Common Networking Issues

UDP multicast communication can be disrupted by certain network configurations or hardware features—especially on wireless access points (APs) and managed switches. The most frequent causes include:

  • Access Points (Wi-Fi) – Many access points block or fail to route UDP multicast and broadcast traffic from Wi-Fi to the wired LAN by default. This is often done to reduce wireless congestion. As a result, Control4 controllers connected via Ethernet may not be able to discover or communicate with Dooya bridges connected over Wi-Fi.

  • Network Switches – Managed switches may restrict multicast traffic through settings like multicast suppression, storm control, or VLAN segmentation.

  • Routers and Firewalls – Some routers prevent multicast traffic from crossing between wired and wireless segments or between VLANs unless explicitly allowed.

Recommended Configuration

To ensure successful communication between the Control4 Dooya driver and Dooya Connector Bridges:

  1. Enable UDP Multicast and Broadcast Traffic on all network devices, including access points and switches.

  2. Disable AP or Client Isolation on wireless networks to allow LAN-wide device discovery.

  3. Confirm All Devices Are on the Same Subnet – multicast packets typically will not traverse subnets without proper multicast routing.

  4. Review IGMP Snooping Settings – if enabled, make sure IGMP Querier is active on the network.

  5. Allow Wi-Fi to LAN Multicast Routing – check AP settings for options like “Multicast Forwarding,” “Allow Broadcast to LAN,” or “Enable Bonjour / mDNS,” and enable them as needed.

See knowledgebase article for assistance with configuration of Araknis 220/320/420 switches

Troubleshooting Tips

If communication remains unreliable:

  • Temporarily connect both the Control4 controller and Dooya Connector Bridge to the same wired switch to verify functionality.

  • Switch from the Wi-Fi based Dooya Connector Bridge to the ethernet based model.

  • Disable multicast filtering or isolation features on your access point.

Proper multicast handling across Wi-Fi and Ethernet is essential for stable communication and full shade control functionality in Control4.

    • Related Articles

    • Control4 Hisense VIDAA: TV control is erratic

      TV Control only works intermittently Solution Ensure that CEC is disabled on the TV. CEC can interfere with control particularly when devices power on or off Check the stability of the network connection. A wired connection is recommended for best ...
    • CONTROL4 AJAX: Integrating Ajax Devices

      It is possible to integrate Ajax Devices (MotionProtect, DoorProtect etc) using this driver for automation purposes BUT there are some limitations to be aware of. Limitations By Default, devices such as MotionProtect, DoorProtect do not report alarm ...
    • CONTROL4 DOOYA: Shade Discovery Successful but Control Unavailable

      Symptoms The driver successfully discovers and imports shades; however, it is unable to control them. Cause This issue typically occurs when the Dooya Connector Bridge has been previously paired with a different account. In such cases, the bridge ...
    • Control4 LIFX: V3 Agent Is Unable To Discover Lights

      Problem LIFX is unable to discover lights on network Solution This can be caused by a few issues The minimum version required for Control4 X4 (or later) is 20241111. In X4, other versions will fail to load correctly Ensure you are using the latest ...
    • Control4 Shelly - Setting Up Shelly BLU / BTHome Devices

      Requirements Chowmain Shelly Driver 20260407 Control4 OS 3.4.0 or later BTHome Compatible Gateway. This includes Gen3+ Devices, BLU Gateway (Gen 3 or later) or Shelly Pro (Gen 2 or Later). Shelly Gateway BLU Gen 1 is NOT supported as a supported ...