Smart Bulb Works in App but Not With Voice Assistant: How to Fix It

Quick Answer

When a smart bulb works in its app but not with a voice assistant, the most common cause is a link or identity mismatch between the bulb’s “control system” and the voice assistant’s “control system.” In plain terms: the app is talking to the bulb directly (local WiFi, hub, or vendor cloud), but the voice assistant is trying to control a different copy of that device (wrong account, wrong home, wrong room), or it has stale data (outdated device list, duplicate device, or an old integration token).

This is especially common after changing routers, renaming devices, moving bulbs between rooms, switching from a hub to Matter, enabling a second integration (for example, both Matter and the vendor skill), or having multiple household members with different accounts. WiFi bulbs, Zigbee bulbs behind hubs (like Hue-style bridges), and Matter bulbs can all show this symptom.

Do these three quick diagnostics first: (1) In the voice assistant app, run “sync devices” (or “discover devices”) and check whether the bulb appears twice or shows “unresponsive.” (2) Turn the bulb on/off from the voice assistant app button (not by voice) to see if the assistant can control it at all; this separates microphone/command issues from device-link issues. (3) Confirm the bulb is assigned to the correct Home/Household and the correct Room/Location in the voice assistant app, not just in the bulb’s own app.

Why This Happens

The core issue is usually not the bulb itself. It’s the connection path the voice assistant uses. Your bulb app may control the bulb locally (direct WiFi on your LAN, or through a hub on your LAN) or through the manufacturer’s cloud. The voice assistant often controls the bulb through a separate integration: a linked account (“skill”/service), a hub connection, or a Matter controller relationship. If that integration is stale, duplicated, or pointing to the wrong “home,” the assistant’s commands go nowhere even though the bulb remains perfectly controllable in the vendor app.

Common technical causes tied to this integration path include:

1) Account linking drift: the voice assistant is linked to the wrong manufacturer account, or the token expired and silently stopped updating device status.

2) Duplicate device identities: the same physical bulb is exposed to the voice assistant twice (for example, once via Matter and once via the vendor cloud), so voice commands may hit the wrong entry.

3) Home/room assignment mismatch: the bulb is in the correct room in the vendor app, but it’s in a different Home/Household or room in the voice assistant app, so your command targets a different device or no device at all.

4) Hub/controller confusion: Zigbee bulbs controlled by a hub can work in the hub’s app, but the voice assistant may have lost its connection to the hub integration (or the hub is connected to a different account/home).

5) Overlooked technical cause: permissions and “local network” access. Some voice assistant apps (and some smart home apps) need local network permission on the phone to discover and manage devices properly, especially during re-linking or Matter commissioning. If that permission was denied after an OS update, discovery and control can partially fail.

Real-world scenario: A homeowner replaces their router and keeps the same WiFi name and password. The bulbs reconnect and still work in the bulb app, but the voice assistant continues trying to control the old device entries it learned months ago. The assistant shows the bulb in the device list, but it’s “unresponsive,” or it controls a duplicate that no longer maps to the real bulb.

Common user mistake: Linking the manufacturer service using a different email than the one used in the bulb app, then assuming “it’s linked” because the assistant shows some devices. The result is partial control or control of the wrong home.

Most Likely Causes in Real Homes

1) The voice assistant has a stale or broken link to the bulb service or hub, even though the bulb app still works.

2) Duplicate device entries (often caused by adding Matter after already using a vendor integration, or vice versa).

3) The bulb is assigned to the wrong Home/Household or room in the voice assistant app, so voice commands target the wrong place.

4) A group/scene mismatch: the bulb works alone in the app, but voice commands are hitting a group, scene, or “All lights” behavior that includes an unresponsive device and fails partially.

5) Cloud or account sync delay/outage: the vendor app may be controlling locally while the voice assistant relies on cloud status that is delayed.

Step-by-Step Fix

1. Confirm the voice assistant can control the bulb from its device page (not by voice). Open the voice assistant app, find the bulb device, and tap On/Off and brightness.

   What the result means: If the on-screen controls work, the integration is mostly fine and the problem is likely naming, room targeting, or a voice command interpretation issue. If the on-screen controls fail or show “unresponsive,” it’s an integration, duplicate, or account/home issue.

   If it fails, try next: Continue to step 2 to force a device sync and check for duplicates.

2. Run device discovery/sync and check for duplicates. Use the voice assistant’s “sync devices,” “discover devices,” or “refresh” option, then search the device list for the bulb name. Look for two similar entries (same name, or same room) and for devices marked offline/unresponsive.

   What the result means: If you see duplicates, voice commands often hit the wrong one. If the bulb is missing, the assistant is not receiving the device from the service/hub/controller.

   If it fails, try next: If duplicates exist, disable one path (step 3). If the device is missing, verify account/home and re-link (step 4).

3. Eliminate duplicate control paths (vendor integration vs Matter vs hub exposure). Decide how you want the bulb exposed to the voice assistant: through the manufacturer service, through a hub integration, or through Matter. Remove or disable the extra path so only one remains. For example, if the bulb is added via Matter, remove the vendor skill/service connection that also exposes the same bulb; or if you prefer the vendor/hub integration, remove the Matter version from the voice assistant.

   What the result means: If voice control starts working after removing duplicates, the assistant was targeting the wrong device identity.

   If it fails, try next: Proceed to step 4 to verify account linking and the correct home/household.

4. Verify the correct account and Home/Household in the voice assistant app. In the voice assistant app settings, confirm you are in the correct Home/Household (not a second home or a previous setup). Then check which account is linked to the bulb manufacturer service or hub service. If multiple family members manage the home, confirm the bulb is shared into the same home that your voice profile uses.

   What the result means: If the bulb appears only under a different home or different account, your voice commands may be controlling a different device list than the one you’re viewing in the bulb app.

   If it fails, try next: Re-link the service carefully in step 5 and then re-sync devices.

5. Re-link the manufacturer service (or hub) to the voice assistant. In the voice assistant app, unlink the lighting service/skill/integration, then link it again using the exact same login used in the bulb’s app. After linking, run device discovery/sync. For hub-based systems, confirm the hub is online in its own app first.

   What the result means: If the integration token was stale or linked to the wrong account, re-linking usually restores control and correct device status.

   If it fails, try next: Continue to step 6 to check naming, room targeting, and groups.

6. Check the bulb’s name, room, and “same-name conflicts.” In the voice assistant app, ensure the bulb has a unique name that doesn’t match a room name or another device (avoid “Kitchen” as a bulb name if you also have a Kitchen room). Confirm the bulb is assigned to the correct room in the voice assistant app. Then test a very specific command like “Turn on Bulb Name” rather than “Turn on the kitchen lights.”

   What the result means: If specific commands work but room-based commands fail, the assistant is targeting the wrong group/room or encountering a naming conflict.

   If it fails, try next: Move to step 7 to test group and scene behavior.

7. Test group control vs single-device control (group sync test). If the bulb works individually but not as part of “All lights,” a room group, or a scene, remove the bulb from that group and add it back. Also check whether the group contains a device marked unresponsive; some assistants behave poorly when a group includes a dead/offline device.

   What the result means: If the bulb works alone but not in a group, the issue is likely group membership, a broken scene, or an unresponsive device in the same group.

   If it fails, try next: Continue to step 8 to check automations and schedules that may be overriding your voice commands.

8. Verify schedules, routines, and “adaptive” lighting features (schedule verification). In both the bulb app and the voice assistant app, check for schedules, routines, scenes, or “wake/sleep” behaviors that may immediately change the bulb state after a voice command. Temporarily disable them for 10 minutes and test voice control again.

   What the result means: If voice commands appear to work but the bulb instantly changes back, an automation is overriding you.

   If it fails, try next: Proceed to step 9 to isolate network/controller issues with a controlled test.

9. Run a hotspot isolation test to separate “integration” problems from “network path” problems. This is a controlled test, not a permanent setup. If you have a spare phone, enable its hotspot with a simple name and password. Move one WiFi bulb (or the hub, if it supports WiFi) onto that hotspot network and add it fresh to the bulb app, then link to the voice assistant again. For hub-based Zigbee bulbs, keep bulbs on the hub and move only the hub’s network connection if applicable.

   What the result means: If voice control works on the hotspot setup, your main home network setup is interfering (often due to router isolation settings, multicast handling, or multiple mesh nodes creating inconsistent discovery). If it still fails, the issue is more likely account linking, duplicate identities, or voice assistant configuration.

   If it fails, try next: Continue to step 10 for a targeted power cycle and controller restart sequence.

10. Do a full restart sequence in the correct order (power cycle sequence). Turn the bulb off for 15 seconds (using the wall switch only if it controls that bulb), then back on. Restart the hub/bridge (if used). Restart the router. Finally, restart the voice assistant speaker/display (or the phone that acts as the controller for some Matter setups). After everything is back, run device sync again.

    What the result means: This clears stale sessions between hub/router/assistant and forces fresh device status.

    If it fails, try next: Move to step 11 to check WiFi band and mesh behavior for WiFi bulbs.

11. For WiFi bulbs: verify WiFi band and mesh behavior (WiFi band check + mesh behavior test). Confirm the bulb is on the expected WiFi network (many bulbs require 2.4 GHz). If your router uses one combined name for 2.4/5 GHz, temporarily create a dedicated 2.4 GHz network name and connect the bulb to it. If you use a mesh system, test by placing the bulb’s controlling phone and the bulb on the same node area (near one access point) and see if voice control becomes reliable.

    What the result means: If reliability improves when the bulb is clearly on 2.4 GHz or near one mesh node, the assistant’s control path was being disrupted by band steering or inconsistent mesh routing.

    If it fails, try next: Proceed to step 12 to verify permissions and local network access on the phone used for setup.

12. Check app permissions and local network access (often overlooked). On the phone/tablet used to manage the smart home, confirm the voice assistant app and the bulb app have permission for Local Network (where applicable), Bluetooth (for Matter commissioning), and background refresh. Then re-run device discovery/sync.

    What the result means: If permissions were blocking discovery or updates, fixing them often makes devices reappear or become controllable.

    If it fails, try next: Continue to Advanced Troubleshooting for cloud/account status and firmware checks.

Advanced Troubleshooting

This section is only needed if basic fixes fail.

Account or cloud issue: If the bulb app works only when you are at home on WiFi but fails when you are away, it may be controlling locally while cloud access is failing. In that case, the voice assistant (which often relies on cloud control) will also fail. Check the bulb app for “remote access” status, and confirm the manufacturer account shows the correct home and devices. If the voice assistant shows widespread “unresponsive” across multiple devices from the same service, unlink/re-link again and wait a few minutes for cloud sync to settle.

Network issue (relevant when discovery or hub visibility is inconsistent): Some routers have settings that isolate devices (often called AP/client isolation) or restrict multicast/broadcast traffic that discovery relies on. If your voice assistant device is on a “guest” network and the bulbs/hub are on the main network, they may never see each other correctly. Put the voice assistant device and the hub/bulbs on the same main network and retest. If you recently enabled a new firewall setting, “IoT network,” or VLAN-like separation, temporarily disable it to confirm whether it’s the cause.

Firmware/software cause: Update the bulb firmware in the vendor app and update the hub firmware if present. Also update the voice assistant app and the smart home platform app. If the issue started right after an update, a reboot of the phone and the voice assistant device can clear stuck background services. Firmware mismatches can show up as “works in app, not by voice” when the vendor app uses a newer local protocol while the assistant integration expects updated cloud metadata.

Configuration conflict (groups, scenes, automations, permissions): If only certain phrases fail (for example, “set kitchen to 30%” fails but “turn on kitchen light” works), check whether “Kitchen” exists as both a room and a device name, or whether multiple homes have a Kitchen. If only scenes fail, rebuild the scene in the voice assistant app rather than importing it. If multiple household members can control the bulb but one person cannot, check voice assistant household permissions and whether that person is operating in the correct home.

When to Reset or Replace the Device

Soft restart vs factory reset: A soft restart is simply power cycling the bulb and restarting the hub/router/assistant devices. Do this first because it does not erase anything. A factory reset wipes the bulb’s pairing information (WiFi credentials, hub binding, or Matter commissioning) and forces you to set it up again from scratch.

What you lose after a factory reset: Expect to lose the bulb’s name, room assignment, scenes, automations tied directly to that device entry, and any Matter pairing or hub association. You will usually need to remove the old device entry from the voice assistant and re-add it so you don’t keep a “ghost” duplicate.

When reset is justified: Reset if the bulb is consistently “unresponsive” in the voice assistant after re-linking, or if duplicates cannot be removed cleanly because the assistant keeps rediscovering an old identity. Reset is also reasonable after major changes like switching from vendor integration to Matter, or moving from direct WiFi control to a hub.

Safety note: If the bulb is overheating, flickering excessively, smells unusual, has visible damage, or the base is discolored, stop using it and replace it. Do not try to repair it or open it.

How to Prevent This in the Future

Keep one control path per bulb when possible: Avoid exposing the same bulb to the voice assistant through multiple methods at the same time (for example, both Matter and a vendor skill). Pick the method you prefer and remove the other to prevent duplicates and wrong-target commands.

Be consistent with accounts and homes: Use one primary account for setup and ensure household members are added properly. After adding devices, confirm they appear in the correct Home/Household and room inside the voice assistant app, not only in the bulb app.

Manage automations carefully: When you create schedules in both the bulb app and the voice assistant app, conflicts are common. Keep time-based schedules in one place so a routine doesn’t “undo” your voice command.

Plan for power outages: After outages, hubs and routers may come back in a different order. If voice control is flaky afterward, restart the hub and the voice assistant device once everything is online, then run a device sync.

Maintain firmware and app updates: Update bulb and hub firmware periodically and keep the voice assistant app current. If you notice issues right after an update, a restart of the phone and voice assistant device often restores normal discovery and control.

FAQ

Why does the bulb respond in the manufacturer app but the voice assistant says “device not responding”?

This usually means the manufacturer app is controlling the bulb locally (or through a hub locally), while the voice assistant is trying to control it through a different path that is broken or stale (linked account token, hub integration, or a duplicate device entry). If the voice assistant’s on-screen device controls fail, focus on re-linking the service, removing duplicates, and confirming the correct home/household.

My voice assistant controls the bulb sometimes, but not always. What does that point to?

Intermittent control often points to duplicates, group/scene conflicts, or network/controller inconsistency (mesh steering, assistant device on a different network segment, or a hub that is online but not reliably reachable). Test single-device control versus room/group control, then remove and re-add the bulb to the group. If it improves when you keep devices near one mesh node or on a dedicated 2.4 GHz SSID, the network path is a major factor.

Do I need to delete and re-add the bulb to fix voice control?

Not always. Start by syncing devices, removing duplicates, and re-linking the service. Delete and re-add (or factory reset) is most useful when the assistant has a “ghost” device entry that won’t go away, or when you changed the integration method (for example, switching to Matter) and the assistant keeps targeting the old identity.

Misconception: “If it works in the app, the WiFi must be fine, so the voice assistant is broken.” Is that true?

Not necessarily. “Works in the app” only proves one control path works. The voice assistant may be using a different path (cloud integration, hub link, or Matter controller relationship). The bulb can be healthy and the WiFi can be adequate, but the assistant may still be controlling the wrong device entry, the wrong home, or an expired account link.

What if only one bulb fails but all other bulbs work with voice?

That usually points to a device-specific identity issue: a duplicate entry for that bulb, a naming conflict, or a bulb that was moved between rooms/homes and didn’t sync cleanly. Check for a second copy of the bulb in the voice assistant device list, rename it uniquely, confirm room assignment, and then remove/re-add it to any groups or scenes that include it.

There’s a relief in watching it settle into place, like the last loose screw finally finding its home. The world didn’t change overnight, but it feels less noisy around the edges.

Some problems stick around just to keep you second-guessing yourself. This one doesn’t—at least not for long—so you can get back to the ordinary parts of your day without the extra mental clutter.