How to Fix Control4 App Not Connecting on Local WiFi
- Client isolation enabled
- mDNS blocked
- Controller IP changed
Problem Description
When a Control4 Control4 App Connectivity drops offline, it's almost always a stale network session rather than hardware failure — the steps below fix the majority of cases in under five minutes.
Symptoms
- App cannot find system
- Connects on cellular but not WiFi
- Intermittent discovery
Recognize these? Here's what usually causes it.
Common Causes
- Client isolation enabled
- mDNS blocked
- Controller IP changed
Most fixes happen in the first 3 steps.
Do not troubleshoot app auth before confirming local reachability.
Tools & Requirements
Step-by-Step Solution
Check network isolation
Ensure mobile clients can reach controller on same segment.
Validate discovery protocols
Allow required local discovery traffic between app and controller.
Stabilize addressing
Reserve controller IP and reconnect app sessions.
Quick Solutions
Still having issues? This is usually the deeper cause below.
This usually happens right after a router reboot or ISP change — the device rejoins the network but drops its cloud session silently.
Network segmentation should be tested with Control4 discovery before rollout.
Most WiFi drop-offs happen right after a router reboot or ISP swap — the device reconnects to the network but silently loses its cloud registration.
- Client isolation enabled
- mDNS blocked
- Controller IP changed
Before you go — try one of these (they fix most cases).
Need More Help? Control4 Support
Note: The contact information below connects you directly to Control4's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.