I've tried opening multiple tickets but keep getting stuck in email verification loops, so trying here instead.
I'm having trouble getting newly-exposed Home Assistant entities to sync to Alexa through the Home Assistant Cloud / Alexa Smart Home skill.
WHAT'S WORKING:
- The Home Assistant skill is linked in the Alexa app and has been working for previously-exposed entities (door/window sensors, climate, lights, etc.) for a long time — these still show up correctly in the Alexa app's Devices list and respond to voice commands.
- Home Assistant Cloud reports as fully healthy: logged in, relayer connected, remote connected, Alexa enabled (confirmed via HA Cloud diagnostics).
- My HA instance: Home Assistant 2026.6.4 on HA Green hardware, Nabu Casa subscription active.
WHAT'S NOT WORKING:
- I created 9 new script entities (domain: script, e.g. script.sofabaton_volume_up) to expose to Alexa for voice control of a SofaBaton X2 universal remote hub.
- All 9 are correctly marked as exposed for Alexa (Settings → Voice assistants → Alexa → Expose — confirmed present and toggled on).
- None of the 9 have ever appeared in Alexa's Devices list, despite running "Alexa, discover devices" multiple times over several days, both via voice and via the Alexa app.
- I confirmed the scripts are not being triggered: checked script.sofabaton_volume_up's last_triggered timestamp after saying "Alexa, activate Volume Up" — it had not updated, confirming Alexa's acknowledgment chime fired but the command never reached Home Assistant.
WHAT I'VE ALREADY TRIED:
- Multiple "Alexa, discover devices" attempts (voice and app), spaced out over several days.
- Fully disabling and re-enabling the Home Assistant skill in the Alexa app (done twice on separate days), including signing back in to the Nabu Casa account each time.
- A full Home Assistant Core restart.
- A full Home Assistant Supervisor/Host reboot (HA Green).
- Reinstalled the Webhook Proxy add-on to generate a fresh MCP webhook URL.
- Checked HA's own system logs around each discovery attempt — no errors logged for the cloud or alexa components on the HA side, suggesting HA is building and reporting its entity list successfully, and the failure is happening somewhere between Nabu Casa's relay and Amazon's discovery backend.
- Verified pre-existing entities (e.g. "Freezer Door Door", "East Gate Door") are still present in Alexa's Devices list and working normally — confirming the issue is specifically with new entities not syncing, not a general connectivity failure.
Could you check the sync/relay logs for my account and advise what's preventing new entities from appearing in Alexa discovery? Happy to provide my Nabu Casa account email, HA instance ID, or any other diagnostic info you need.
Thanks,
Mike Stevens