Nabu Casa errors on HA log

[def1149]

The problem

See below. Nabu Casa errors in the log

What version of Home Assistant Core has the issue?

2024.5.2

What was the last working version of Home Assistant Core?

??

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Nabu Casa

Link to integration documentation on our website

No response

Diagnostics information

`
Logger: hass_nabucasa.iot
Source: /usr/local/lib/python3.12/site-packages/hass_nabucasa/iot.py:139
First occurred: 3:25:36 PM (6 occurrences)
Last logged: 3:26:40 PM

Error handling message
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/hass_nabucasa/iot.py", line 123, in _async_handle_handler_message
result = await handler(self.cloud, message.get("payload"))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/hass_nabucasa/iot.py", line 175, in async_handle_alexa
return await cloud.client.async_alexa_message(payload)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/cloud/client.py", line 263, in async_alexa_message
return await alexa_smart_home.async_handle_message(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/alexa/smart_home.py", line 237, in async_handle_message
assert directive.entity_id is not None
AssertionError
`

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @home-assistant/cloud, mind taking a look at this issue as it has been labeled with an integration (cloud) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of cloud can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign cloud Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

cloud documentation
cloud source
_{^{(message by IssueLinks)}}

[home-assistant]

Hey there @home-assistant/cloud, @ochlocracy, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (alexa) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of alexa can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign alexa Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

alexa documentation
alexa source
_{^{(message by IssueLinks)}}

[jbouwh]

The error can occur if an endpoint is included but is not enabled. So please check if you have any entities included to alexa that are disabled.

I must say the raw error message is not the preferred way to log errors. Could you check if you have any disabled entities that are included (not excluded) for Alexa?

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.