Several months ago, I began having lights and other Alexa-exposed Home Assistant entities turn on or off unexpectedly. Many of the incidents occurred overnight when nobody was intentionally using Alexa.
The behavior stopped after I disabled the Alexa integration through Home Assistant Cloud/Nabu Casa. Because of that, Alexa or the Alexa/Home Assistant Cloud connection became the leading suspect, but I was never able to determine the exact cause.
I do not use Alexa routines for these entities. I also checked the usual possibilities, including routines, Hunches, groups, and other Alexa automation features, but did not find anything that explained the switching.
I have now re-enabled the integration with:
- Expose new entities: Off
- Enable state reporting: Off
- Only selected entities exposed
I am logging relevant activity so that, if the behavior returns, I can compare the unexplained event against a known Alexa command and determine whether it came through the same Alexa/Home Assistant Cloud identity.
I am looking for feedback from anyone who has experienced something similar:
- Did the switching happen mostly overnight?
- Did the Home Assistant logbook attribute it to Home Assistant Cloud?
- Did disabling Alexa exposure stop it?
- Were routines, Hunches, groups, and occupancy features ruled out?
- Was state reporting enabled or disabled?
- Were the same entities also exposed through Matter or a manufacturer skill?
- Did re-linking the Alexa skill or removing duplicate endpoints resolve it?
- Did anyone confirm the source through
user_id, context IDs, or service-call logging?
I am particularly interested in whether this appears to be:
- An Alexa-side bug
- Duplicate or stale Alexa endpoints
- A Home Assistant Cloud integration issue
- A hidden Alexa automation or feature
- Something else entirely
Please share any logs, patterns, fixes, or related threads. I will update this post if the behavior returns and the new logging captures it.