CONTROL4 DOOYA: Shade Discovery Successful but Control Unavailable

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 retains the old secret key, preventing the new key from functioning correctly with your current setup.

Solution

  1. Open the Dooya Connector App and delete the existing hub.

  2. Perform a factory reset on the Connector Bridge.

  3. Re-pair the bridge with the Connector App under your current account.

  4. Once pairing is complete, return to your automation system and resume the integration process.

    • Related Articles

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

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

    • 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 Shelly Suite: Shelly Incorrectly Shows All Customers Devices

      For Shelly Agent to differentiate different systems correctly, Customers must use a different Shelly cloud email login for Shelly Cloud. If customers have multiple Control4 systems, it is also generally recommended to have a different account login ...

    • Control4 Shelly: Module Reboots Continuously In a Loop

      Symptom Module NG is continuously reconnecting, rebooting, and then repeats. This prevents the module from being controlled successfully as it is continuously rebooting Solution This is generally caused by having 2 or more Shelly Module NG drivers ...