So this is installed pending restart for me
Is there any way to roll back at this point?
My ha restarts itself overnight so would like to fix this before I go to bed
Edit:
Okay, I’ve disabled AMP and I’ve found the redownload button and redownload the old version
It now says I have two pending restarts for AMP
Am I safe to reboot?
Gav_in
(Gavin)
October 3, 2024, 8:21pm
21
You seem to be on HACS 2.0 so in HA go to Developer Tools > Actions and then
action: update.install
data:
version: v4.13.2
target:
entity_id: update.alexa_media_player_update
then if you check the update.alexa_media_player_update
entity it’ll show the installed version
1 Like
poudenes
(Poudenes)
October 3, 2024, 8:41pm
23
Goto Hacs press the 3 dots icon. Redownload and select the other release. Download and restart
2 Likes
Mark_M
(Mark)
October 3, 2024, 9:01pm
24
Please can Home Assistant add a limit to prevent memory leaks or an addon using soo much RAM that it crashes.
I’ve found there is an option to limit RAM usage by add-on but it’s not implemented by default.
Looking online I see there is ways in config.yaml or some addon’s configuration to limit the amount of RAM they can use.
But does Home Assistant have a default limit to prevent itself from crashing?
I accidentally created a NodeRed flow which seems to overflow the RAM usage of my Raspberry Pi and then Home Assistant crashes completely.
The worst part is that I allowed NodeRed to start on boot and you can guess what happens again… whoops. (Was fixed by quickly disabling ‘start on boot’ as HA w…
Gav_in
(Gavin)
October 3, 2024, 9:09pm
25
Yeah think so…if you have AMP Integration disabled it’ll not impact HA anyway…
1 Like
Gav_in
(Gavin)
October 3, 2024, 9:12pm
26
Add-ons and Integrations are two different things…AMP is an Integration rather than an Add-on…
In your other thread where you mention Node Red that is an Add-on.
(but a good idea if it’s possible)
Thanks a lot! this was wrecking my head all evening trying to figure out what was happening!
1 Like
Godmag
October 3, 2024, 9:41pm
28
I’m having the feeling that the add-on was causing problems also before 4.13.2. it wasn’t crashing HA but I had high CPU usage without any reason. I didn’t look for it and just restarted HA. Not sure if this is correct I will try.
1 Like
RTech73
(Ron)
October 3, 2024, 10:05pm
29
SO glad there is a post about this! I upgraded to 10.0 and got the memory leak errors! Fortunately I had a full backup less than a month old.
If I disable the update entity in the Alexa Media Player integration, it’ll stop bugging me for updates (for now) correct?
I hope this finds a new stable home. I use this one a LOT!
Very grateful for this community today!
1 Like
Thank you for this thread!
I’ve been pulling my hair out all day!
1 Like
raym64
(Ray Morgan)
October 4, 2024, 1:34am
31
Thank you for this. I had updated Core yesterday and then saw the update tonight for Alexa Media player. As soon as I updated AMP, I got stuck in the boot loop. When I started searching for an answer, this thread popped up.
Fortunately, I was able to trigger a restore in-between reboots to when I updated the core yesterday, and all seems okay after reinstalling the Core update.
This time when AMP notified me of the update, I skipped it.
dgaust
(dgaust)
October 4, 2024, 2:07am
32
Glad I found this… I still had AMP installed, even though it wasn’t in use. Uninstalled and all is good.
Of course, in the interim, I used this as an excuse to upgrade the HP 800 Mini G1 to a G5 version
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
(Stef)
October 4, 2024, 9:39am
35
I reinstalled AMP 4.13.2
Is now running stable since I rolled back
Gav_in
(Gavin)
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
(Chris)
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