Updated November 2026

When Home Assistant Alexa devices not working is the problem, the cause is usually one of three things: a broken link between Home Assistant and Amazon’s cloud, a stale login token, or a device exposed in a way Alexa can’t read. This guide walks through the checks in the order that solves most cases, so you can restore voice control without rebuilding your setup.

Check Your Integration Status First

Start in Home Assistant by going to Settings > Devices & Services and looking at the integration you use to connect to Alexa. If it shows a red “Failed to set up” or “Reauthentication required” message, Alexa can’t receive updates from Home Assistant, and no amount of device-level troubleshooting will help. Restarting Home Assistant clears many temporary failures, so do that before going further.

Shopping for one? See our guide: 9 Best Alexa Compatible Devices for Smart Home Setups (2026).

If you installed Alexa devices through a community integration or a cloud service such as Nabu Casa, confirm that the subscription or connection is still active. The Import Alexa Devices to Home Assistant: A Step-by-Step Guide (2026) guide covers how the import works, which helps you spot where the chain breaks.

Amazon login tokens expire, and a password change or a new Alexa app login can invalidate them. Remove the integration, then add it again and sign in with the same Amazon account your Echo devices use. Confirm the two-step verification prompt if it appears. This single step fixes a large share of “it worked last month” complaints.

Keep in mind that the Amazon account must match the one linked to your Echo hardware. Signing into a different account will show devices, but Alexa will not respond to them.

Verify Which Entities Are Exposed to Alexa

Home Assistant only shares entities you explicitly expose. If a light appears in Alexa’s app but won’t respond, or it disappeared after an update, open the integration’s options and check the entity filter. Make sure the lights, switches, and sensors you want are included, and that their names are short and unique. Alexa struggles with names like “Light 1” or duplicates across rooms.

Run a Discovery Scan in the Alexa App

After any change, tell Alexa to look for new devices. In the Alexa app, go to Devices > + > Add Device, or say “Alexa, discover devices.” Discovery can take up to 45 seconds. If a device still doesn’t appear, delete it from the Alexa app, rename it in Home Assistant, and run discovery again. Renaming resolves more problems than people expect.

Check Emulated Hue and Local Network Settings

If you use Emulated Hue rather than a cloud integration, Alexa needs to reach your Home Assistant host on the local network. Confirm the following:

  1. Home Assistant and your Echo devices are on the same subnet and VLAN.
  2. The host has a fixed IP address through a DHCP reservation, so it doesn’t change after a router restart.
  3. The Emulated Hue port (default 8300) isn’t blocked by a firewall or VPN.
  4. After changing the config, you rebooted Home Assistant and ran discovery in Alexa again.

Restart the Echo Device and Update Software

Unplug your Echo device for 30 seconds and plug it back in. This clears cached device lists that can hold on to old IDs. Then check that the Echo firmware and the Alexa app are current. Outdated firmware sometimes causes intermittent failures that look like integration bugs.

Common Mistakes

  • Changing an entity ID in Home Assistant without rediscovering the device in Alexa.
  • Using a second Amazon account for the Alexa app than the one on your Echo.
  • Exposing too many entities, which can make discovery time out or return partial results.
  • Assuming a Wi-Fi outage is an integration fault. Test the Echo’s internet connection first.
  • Skipping a Home Assistant restart after editing YAML configuration.

A wired Ethernet connection for your Home Assistant host reduces the chance of dropped connections that break cloud-linked devices. View on Amazon

A small smart plug with energy monitoring helps you confirm whether a device has lost power or is simply unresponsive in software. View on Amazon

FAQ

Why do my Alexa devices work in the Alexa app but not with voice commands?

This usually means the device is discovered but its name or room assignment is causing Alexa to misinterpret your request. Rename the device to something short and unique, then ask Alexa to discover devices again.

Do I need to re-add Alexa devices after a Home Assistant update?

Usually not, but major updates can change integration behavior. If devices stop responding after an update, reauthenticate the integration and run discovery once.

Can a router change break my Alexa and Home Assistant connection?

Yes, if the Home Assistant host gets a new IP address. Assign a fixed address through a DHCP reservation so local connections stay stable.

Conclusion

Most Home Assistant Alexa problems come down to an expired login, an unexposed entity, or a network change that moved the host. Work through the checks in order: integration status, reauthentication, exposure settings, and discovery. If the problem persists after those steps, the Alexa troubleshooting guide at Alexa Devices Not Working: 8 Fixes to Try First (2026) covers device-side issues in more depth.

Colin Foster

About Colin Foster

Colin Foster is part of our editorial team and reviews and edits our smart home guides, checking product details against manufacturer specifications and owner feedback.