now 4.13.3 has been removed as an update will HA stop blocking it, I mean I never updated to 4.13.3 and yet I got failed to setup and removed and try to re add but authing is in a loop now (enter user, then password then back it goes to user lol)… I litrally use alex just for actionable notifications and thats it.
Schwabi
October 4, 2024, 9:39am
35
I reinstalled AMP 4.13.2
Gav_in
October 4, 2024, 2:43pm
36
as FYI…looks like the plan to block AMP in HA has been reverted according to this PR now that AMP v4.13.3 has been pulled
home-assistant:dev ← home-assistant:frenck-2024-0528
opened 10:47AM - 04 Oct 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Reverts #127412
Original issue: https://github.com/alandtse/alexa_media_player/issues/2579
I'm unblocking this one, as Alexa Media Player v4.13.3 has been pulled and is no longer available.
Integrations should never crash the system. That said, the previous versions are not great either, but blocking it will make us look like bad guys in this case (even though, IMHO, it is the right thing to do right now). I would rather have the community look at the state of the custom integration and report upstream instead.
Additionally, instead of pulling the version, it would have been better to have shipped a new version (as it allows people to upgrade themselves out of the issue they are having). It allows us to block older versions at that point (preventing people from getting into a crashing issue at all).
Let's see how this develops from here on. We can always reinstate this block if it continues to be problematic.
/CC @alandtse
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [x] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
@poudenes you asked about the block too so just FYI
chrisExh
October 4, 2024, 5:27pm
37
DOH!
Wish I’d seen this first. In debugging I removed AMP and now trying to reinstall it I can’t get past the Amazon.co.uk login screen. 2FA is good and matches, grrrrr
“Solution”
opened 07:18PM - 08 Sep 24 UTC
**Describe the bug**
Setup via amazon.com, will endlessly loop through the am… azon login screen, it never progresses beyond inputting password.
Setup via amazon.com.be will give a 500 Internal server error.
Setup via amazon.de or amazon.co.uk will succeed, but all devices will be unavailable & uncontrollable.
My account region info:
Going to Amazon.de -> Manage Your Content and Devices: states that it is setup through Amazon.com
Going to Amazon.com -> Manage Your Content and Devices -> Country/Region Settings: Is set to Belgium, as that is my address of residence, and changing it requires a valid address.
**To Reproduce**
1. Have an amazon account set to Belgium.
2. Try to setup the integration using .com or .com.be
3. See error
**Expected behavior**
All echo devices available & controllable.
**System details**
- Home Assistant version: 2024.9.0
- alexa_media version (from `const.py` or HA startup log): 4.12.12
- alexapy version (from `pip show alexapy` in homeasssistant container or HA startup log):
- Is Amazon [2FA/2SV enabled](https://github.com/alandtse/alexa_media_player/wiki/Configuration#enable-two-factor-authentication-for-your-amazon-account) (y/n): Y
- Amazon Domain: Amazon.com.be ???
@Richi_Bowzer @chrisExh try this to solve the login screen issue.
All thanks go to @dbrunt who made a simple, step by step tutorial with pics!
1 Like
P6Dave
October 5, 2024, 12:39pm
40
I had a look through that and yes it does look like a lot of work. I mainly use my Amazon Echos as announcement speakers in HA and have some quite complex scripts to collate all the information I need for a particular announcement then send it to an Echo in whichever room I am in.
I couldn’t see any way of doing that from this skill. I might just switch to local voice once I get my local voice assist set up. It’s the one advantage Google speakers have over Amazon.
sweh
October 5, 2024, 1:26pm
41
Amazon doesn’t seem to let you do that in routines. It’s also not designed to allow for dynamic content; it’s pretty much just for “fixed” stuff.
I can think of a kludge, but it’s a bit messy… have a virtual switch for each room/message you you would want, and have a different routine triggered from each switch. Then your complicated HA setup would decide which switch(es) need to be triggered. It doesn’t scale too well, but if you just have 5 rooms and 3 messages then 15 switches and 15 routines is managable…
Rage321
October 5, 2024, 11:10pm
42
Hi everyone. I’m glad I found this thread. I’m not exactly sure what to do, but I’m stuck where I can’t get into HA via a browser nor through SSH. I have a ping -t going, to see if it truly rebooting on me like the others, and if so I going to log in as quickly as possible and disable the Alexa.
Still, I’m not able to get in, what are my options? I have a back up from 3 days ago.
petro
October 5, 2024, 11:22pm
43
Power it off, plug a keyboard and monitor into the system. Turn it on, when the screen boots up, type
ha core restart --safe-mode
Once you’re into safe mode, disable the integration. And you can restart in non safe mode to downgrade it
3 Likes
Rage321
October 5, 2024, 11:40pm
44
Thank you for this response. I’ve gone just this, and I see hope. Hope on a Saturday!
So, just to get this clearly out there.
If you STAY on AMP 4.13.2 you should NOT upgrade to HA 2024.10.1. Is this correct? Otherwise AMP won’t work?
Until a new stable version of AMP is released, then HA should NOT go above 2024.10.0, correct?
Gav_in
October 6, 2024, 8:06am
46
No…AMP 4.13.2 works fine with HA 2024.10.1…the block was pulled, see PSA: Alexa Media Player v4.13.3 breaks all versions of Home Assistant - #36 by Gav_in for the details
Sammy521
October 6, 2024, 11:20am
47
How to downgrade? Can you explain for dummies like me?
I experience unstability HA boots new every now and then. Maybe coz i made the last alexa media player Update
Gav_in
October 6, 2024, 11:25am
48
How have you installed AMP?
Gav_in
October 6, 2024, 9:45pm
50
AMP 4.13.4 is available now and according to release notes fixes the resource issues of 4.13.3
diedrichg
October 7, 2024, 1:30am
51
Can anybody confirm stability for 4.13.4?
I’m wondering if anyone here in this thread is able to use AMP in HA 2024.10.x in region amazon.de
Für me it stopped working HA releases far in the future (where I’m still sitting because of this problem). Regardless of AMP version.
_dev_null
October 7, 2024, 9:20am
53
