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 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 Govee: Some Cloud Lighting/Outlet Devices are not being detected / Discovered

      Some Devices (in particular, many light bulbs including the H600D) require an upgrade to our Govee V3 Driver to operate. V1/V2 will not detect many modern devices. Govee V3 utilises the "Awesome New API" (sic) from Govee and is a free upgrade for ...
    • Control4 Govee: Upgrade Govee V1 / V2 to Govee V3

      Govee V3 Advantages Some devices require Govee V3 to be controlled via Control4. Govee V3 offers many advantages over V1/V2 including: Govee V1/V2 utilises the old Govee Cloud API. This has more quota limitations than the "Awesome New API" (sic) ...
    • Control4 TP-Link: Unable to Control Device

      General Issues 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 ...
    • CONTROL4 DOOYA: Configuration for Araknis 220/320/420 Switches

      Note: Enable these settings on every managed switch on the network, unless a step specifically states it is for a core switch. Navigate to Settings > Multicast. Click the IGMP Snooping tab > Global Settings tab. Set the status to Enabled, then click ...