Experiencing the same thing where after re-installing the Login page just kept looping. I selected “Create new account” entered my e-mail address. This triggered an alert that I already had an account. I then switched back to “Sign in” and it worked as expected.
Hi,
I’m working with HA 2024.8.3 and AMP 4.13.2 successful and never had any issues since month. I have 9 Echos and use them intensively for tts and starting scripts.
But now, I will have to update due to other fixes and I’m totally unsettled because of these 3 threads on Github:
Alexa Media Reauthentication Required - continuously appear: Login error detected; not contacting API · Issue #2453 · alandtse/alexa_media_player (github.com)
Alexa API / Too many requests · Issue #2177 · alandtse/alexa_media_player (github.com)
TypeError: can only concatenate str (not “NoneType”) to str · Issue #2515 · alandtse/alexa_media_player (github.com)
It might have something to do with changes in HA. Otherwise I would have had these issues too.
Does anybody run AMP 4.13.2 or higher successfully on HA 2024.10.x without skipping the polling or other mods? Do I still have to wait for fixes?
Does anyone know if you can use the value of a sensor within the media_content_id field of the media_player.play_media action?
Use Case: I want to send a custom command to my Echo that leverages a sensor’s value as part of the sentence.
Example: Alexa, move music to <sensor.room_name> echo’
would result in sending: Alexa, move music to family room echo
Sure, just use a template:
action: media_player.play_media
target:
entity_id: media_player.dotkitchen
data:
media_content_type: custom
media_content_id: |
simon says H.A. version is {{ states('sensor.home_assistant_versions') }}
For now I use node-red with the alexa applestrudel node and most of the automations work, the only ones that I still can’t get to work are those related to the Alexa actionable notification because I can’t use the alexa applestrudel node but the event node and when Alexa media player doesn’t work those automations are “blocked”… Is there anyone who is using applestrudel for actionable notifications?
Is this how it’s supposed to be? Didn’t see this trick mentioned in the installation instruction.
Hi everyone,
I have two fire TV sticks and messed them up in my HA config.
I did not find an option to delete the Echo devices separately.
Anny suggestion how to delete a single Echo device and discover it again?
Thanks in advance.
Hi All,
I’ve just updated and was hit with a window asking me to include the external URL and a list of Allowed and denied devices separated by a comma… as far as I understand I’ve done that… copied and pasted my Nabucasa URL (including the last) and entered my included device list as “light.bedside1, light.bedside2, light.lounge_decorative_light, etc…” and my Excluded device list as “automation, binary_sensor, device_tracker, etc…” but it fails to load… where have I gone wrong?
my log file from the error is this,
Logger: homeassistant.setup
Source: setup.py:416
First occurred: 9:18:31 PM (1 occurrences)
Last logged: 9:18:31 PM
Error during setup of component alexa_media
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 416, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/alexa_media/__init__.py", line 159, in async_setup
CONF_PUBLIC_URL: account[CONF_PUBLIC_URL],
~~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'public_url'
I hope that makes sense to someone…
any and all help is greatly appreciated
thank you so much for your attention and participation.
Robin
I also have tried (twice) to upgrade to 4.13.8 (from 4.13.7). Upon reboot, I get the following notification:
Invalid config
The following integrations and platforms could not be set up:
alexa_media (Show logs)
Please check your config and logs.
In the log I get the following:
Log details (ERROR)
Logger: homeassistant.setup
Source: setup.py:416
First occurred: 5:45:22 PM (1 occurrences)
Last logged: 5:45:22 PM
Error during setup of component alexa_media
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 416, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/alexa_media/__init__.py", line 159, in async_setup
CONF_PUBLIC_URL: account[CONF_PUBLIC_URL],
~~~~~~~^^^^^^^^^^^^^^^^^
KeyError: 'public_url'
After going back to 4.13.7, I have no noticeable issues.
1 Like
Not just me then… thought I was going mad there but after reading this I went back to 4.13.7 and all is good for now.
1 Like
Hi, here is te same. rollback to 4.13.7 and everything works…