Check the Wi-Fi band first
This is the most common cause of detection failures: your phone is connected to 5GHz Wi-Fi but your smart device only supports 2.4GHz. During setup, temporarily switch your phone to the 2.4GHz network (it often has the same SSID with '-2.4G' appended, or you may need to separate bands in your router settings). Once the device is configured and connected, your phone can return to 5GHz. This single issue resolves approximately 60% of smart device setup failures we encounter.
Skill not enabled or account not linked
For Alexa, most third-party smart home devices require their own 'Skill' to be enabled in the Alexa app (More → Skills & Games → search for your brand). After enabling the skill, you must link your account credentials for that brand. For Google Home, this is done via Works with Google (+ → Set up device → Works with Google). Without account linking, the voice assistant has no way to communicate with your devices even if they're online.
Device discovery must be triggered
After enabling a skill or linking an account, Alexa and Google do not always discover devices automatically in real time. In Alexa, say 'Alexa, discover my devices' or go to Devices → + → Add Device → Discover Devices. In Google Home, tap + → Set up device and follow the flow. Some integrations update within minutes; others require a manual rediscovery each time a new device is added to your account.
Firmware and app version mismatches
Outdated device firmware or an outdated version of the manufacturer's app can break integration with Alexa and Google. Manufacturers frequently update their cloud APIs, and older firmware may no longer be compatible. Check the device manufacturer's app for firmware update prompts, and ensure both the manufacturer app and the Alexa/Google Home app are updated to current versions. If the device was working previously and suddenly stopped, a firmware mismatch is the most likely cause.
Router firewall and DNS issues
Some routers — particularly those with aggressive firewall presets or parental control features — block the outbound connections smart devices need to reach their cloud services. Check your router's client list to confirm the device has a valid IP address. Temporarily disable any custom DNS filtering (Pi-hole, NextDNS) to test if that is blocking the device's cloud connectivity. Smart devices that rely on cloud infrastructure can be silently blocked by DNS-level ad/tracking filters.
When nothing works: factory reset and re-add
If you've verified network, skill, account linking, and firmware without success, a factory reset of the device followed by fresh setup is almost always the resolution. Most smart devices have a reset button or a hold-sequence documented in the manual. After reset, follow the manufacturer's setup process from scratch before attempting voice assistant integration. Attempting to re-add a device that was not cleanly removed from its previous configuration frequently causes persistent detection failures.