Closed mkanet closed 1 year ago
You're not describing an issue with AMP. AMP exposes Alexa entities to HA. Report to core since it's with Alexa communicating with HA.
You're not describing an issue with AMP. AMP exposes Alexa entities to HA. Report to core since it's with Alexa communicating with HA.
@alandtse Thank you for your response. My apologies. Where specifically should I open this issue? This issue happens only after starting/restarting Home Assistant OS, not Home Assistant Core. Should I open the issue in the link below?
Describe the bug: Approximately 1 year ago, something changed either in Alexa Media Player or Home Assistant OS which causes Alexa devices like Echo Dot not to be able to communicate with Home Assistant entities, scripts, etc. after Home Assistant Host reboots (synced via Nabu Casa):
If I say "Alexa, turn on Bathroom Lights", it will say "Device isn’t responding. Please check its network connection and power supply". It will do that for all Home Assistant entities.
It is important to note that all other services have no issues communicating with Home Assistant via TCP/IP; also, the web interface is accessible to everywhere.
The only way to mitigate this issue is to restart Home Assistant VM via Hypervisor instead of restarting Host via Home Assistant's interface. This is reproducible on 2 different PC setups:
The issue doesn't occur again until Home Assistant Host reboots again. Rebooting HA Core or updating HA Core does NOT cause the problem.
IMPORTANT NOTES:
System details:
const.py
or HA startup): 4.6.5pip show alexapy
or HA startup): Unsure how to do this, I have a Home Assistant VM.Log: (While issue is occurring) home-assistant.log
Log: (After VMWare Workstation Player Hypervisor reboots Home Assistant VM). No issues at all. Everything working normally until Home Assistant Host instigates a reboot again. home-assistant2.log
Additional context: I have a feeling this issue is related to all the lines in the debug log that looks like below. Note: These errors did not occur in Alexa Player debug over a year ago when the issue didn't occur.