- Network segmentation blocks discovery
- integration token/session expired
- device protocol support mismatch
Problem Description
New smart home devices are online but do not appear in Brilliant discovery flow.
Why This Happens in Real Homes
Why this happens in real homes usually comes down to environment and timing, not instant hardware failure. New smart home devices are online but do not appear in Brilliant discovery flow. The pattern people actually report is Device visible in native app only, Brilliant scan finds nothing, and Partial room inventory in panel
The most common real-world triggers are Network segmentation blocks discovery, integration token/session expired, and device protocol support mismatch. The fix is most reliable when the sequence is followed exactly: Verify shared network path, then Reauthorize integrations, then Retry targeted discovery. After the repair, run multiple command and automation checks so the issue does not reappear later in the day.
Symptoms
- Device visible in native app only
- Brilliant scan finds nothing
- Partial room inventory in panel
Recognize these? Here's what usually causes it.
Common Causes
- Network segmentation blocks discovery
- integration token/session expired
- device protocol support mismatch
Most fixes happen in the first 3 steps.
Do not factory-reset all devices before validating account/session scope and network reachability.
Tools & Requirements
Step-by-Step Solution
Verify shared network path
Confirm Brilliant panel and target devices are on reachable segments.
Reauthorize integrations
Refresh account links, tokens, and app permissions.
Retry targeted discovery
Run discovery after protocol and account checks are confirmed.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If this comes back after following these steps, check whether a recent app or firmware update reset a default setting — the fix works, but the setting gets reverted silently.
Discovery reliability improves when onboarding is done from a clean network and fresh integration session.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Network segmentation blocks discovery
- integration token/session expired
- device protocol support mismatch
Before you go — try one of these (they fix most cases).
Need More Help? Brilliant Smart Home Support
Note: The contact information below connects you directly to Brilliant Smart Home's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.

