Integration not loaded after updating to 2022.12
See original GitHub issueIMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug After updating to 2022.12 the integration cannot be loaded after the restart.
To Reproduce
Expected behavior Integration loaded after the HA restart.
Screenshots
System details
- Home-assistant (version): 2022.12
- alexa_media (version from
const.py
or HA startup): 4.3.2 - alexapy (version from
pip show alexapy
or HA startup): - Amazon 2FA is enabled (y/n): Yes, It was enabled. But now it is impossible to reconfigure the integration, because as it is not loaded… the setup option is not available anymore.
Logs
Logger: homeassistant.util.package
Source: util/package.py:98
First occurred: 09:16:33 (1 occurrences)
Last logged: 09:16:33
Unable to install package alexapy==1.26.4:
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f19439a0>: Failed to establish a new connection: [Errno -3] Try again')': /musllinux/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f19400d0>: Failed to establish a new connection: [Errno -3] Try again')': /musllinux/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f1940040>: Failed to establish a new connection: [Errno -3] Try again')': /musllinux/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f19cab00>: Failed to establish a new connection: [Errno -3] Try again')': /musllinux/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f18f1990>: Failed to establish a new connection: [Errno -3] Try again')': /musllinux/
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f17c1ea0>: Failed to establish a new connection: [Errno -3] Try again')': /simple/alexapy/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f1b0b640>: Failed to establish a new connection: [Errno -3] Try again')': /simple/alexapy/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f1b0b2b0>: Failed to establish a new connection: [Errno -3] Try again')': /simple/alexapy/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f1b0b430>: Failed to establish a new connection: [Errno -3] Try again')': /simple/alexapy/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7fd9f1b0b160>: Failed to establish a new connection: [Errno -3] Try again')': /simple/alexapy/
ERROR: Could not find a version that satisfies the requirement alexapy==1.26.4 (from versions: none)
ERROR: No matching distribution found for alexapy==1.26.4
WARNING: There was an error checking the latest version of pip.
Additional context The integration was already updated to the latest version before updating Anyway, after seeing this error I went to HACS and I tried to redownloading the last available version. Then I restarted HA … without no luck, still is not being able to be loaded after the restart.
Issue Analytics
- State:
- Created 9 months ago
- Comments:6
Top Results From Across the Web
After Update to 2022.12.4 Homematic integration not working
Hello all there, i just started with Home Assistant, starting to integrate all my Devices. I got Homematic (not IP) finally working using ......
Read more >Xiaomi Miio integration doesn't wiek after HA updated ... - GitHub
The problem Hi, Xiaomi Miio integration doesn't wiek after HA updated to 2022.12.5 version. Gateways and all devices connected to them are not...
Read more >2022.12.3.16 Official Tesla Release Notes - Software Updates
Vehicle preconditioning accessed via the Tesla app will now remain active up to 30 minutes after a door is opened, making it easier...
Read more >Tesla Software Updates and Release Notes
There are also times when software release notes are provided but only Tesla test engineers get the updates. Not having a listed feature...
Read more >Production Release Notes - Okta Documentation
2022.12.0: Monthly Production release began deployment on December 12 ... The following SWA apps were not working correctly and are now fixed.
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
I had the same issue, along with bluetooth service failing to start. Rolling back to a previous back up of HA and updating again solved the issue entirely for me.
Just for the record and for anyone who has a similar issue in the future.
Finally I move the NAS to a new location … I connected it to a different network and … homeassistant was able to load the Alexa Media Player integration without any problem… so the files that the integration needs (and that were deleted or corrupted after installing homeassistant 2022.12) were downloaded and installed correctly.
Now I moved again the NAS to home … and the integration was loaded Ok.
So maybe there is a problem with the router … that is blocking something (although I didn’t change anything recently) o maybe it was a problem with the ISP.