2 new errors that arise during startup after update to latest version w/ 2022.9
See original GitHub issueDescribe the bug There’s 2 errors in the logs, it doesn’t seem like I have control over these errors.
To Reproduce I’m not sure if this can be reproduced, but the errors themselves are pretty easy to follow.
Error 1: discovery info doesn’t have [“config”][“email”], no check for it. Error 2: the hass object is none when it shouldn’t be.
Expected behavior No errors in logs.
Screenshots NA
System details
- Home-assistant (version): 2022.9
- Hassio (Yes/No): Supervised.
- alexa_media (version from
const.py
or HA startup): 4.1.2 - alexapy (version from
pip show alexapy
or HA startup): 1.26.3 - Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: Y
Logs Error 1
2022-09-08 19:19:22.473 ERROR (MainThread) [homeassistant.components.switch] Error while setting up alexa_media platform for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 281, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/alexa_media/switch.py", line 44, in async_setup_platform
account = config[CONF_EMAIL] if config else discovery_info["config"][CONF_EMAIL]
KeyError: 'email'
Error 2
2022-09-08 19:20:58.366 ERROR (MainThread) [homeassistant] Error doing job: _GatheringFuture exception was never retrieved
Traceback (most recent call last):
File "/config/custom_components/alexa_media/helpers.py", line 156, in _catch_login_errors
result = await func(*args, **kwargs)
File "/config/custom_components/alexa_media/media_player.py", line 894, in async_update
or email not in self.hass.data[DATA_ALEXAMEDIA]["accounts"]
AttributeError: 'NoneType' object has no attribute 'data'
Issue Analytics
- State:
- Created a year ago
- Comments:6
Top Results From Across the Web
Windows 10 upgrade issues troubleshooting - Microsoft Learn
Understanding the Windows 10 upgrade process can help you troubleshoot errors when something goes wrong. Find out more with this guide.
Read more >2022.9: Home Assistant Birthday Release!
New revamped Automation Editor, Weekly Schedule helper to help with automations, and Paul Bottein (Mushroom Cards) joins Nabu Casa.
Read more >How to Fix Critical Error Your Start Menu Isn't Working ...
Fix 1: Enter Safe Mode and Restart Computer · Fix 2: Create a New Administrator Account · Fix 3: Temporary Hide Cortana from...
Read more >Cloud Composer release notes | Google Cloud
You can see the latest product updates for all of Google Cloud on the Google ... New environments will use the latest Cloud...
Read more >Troubleshoot startup errors on Xbox
If you're seeing the Something went wrong screen with an “E” error code when your Xbox console restarts after a system update, use...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks. At this point the component is in a pretty bad state. We can catch for it, but it’ll be non functional since even the hass entity is None. hass should always be valid. I’ll add it to the backlog of things to catch.
issue cleared itself up