Hmmm, I seem to have include/exclude specified in ./config/.storage/core.config_entries
Is that meaningful ?
You should have a sensor… sensor.chad_s_2nd_echo_dor_next_timer
Thanks for the quick reply. Do I specify that in ./config/.storage/core.config_entries or ./config/configuration.yaml or ./config/sensors.yaml ?
It’s automatically created by the integration.
I think I may have shot myself in the foot by specifying an include list when I set this up years ago ? Feels like I need to re-setup without include/exclude, or figure out how to include…
It’s easier to just remove the integration and add it back. If I remember correctly, you can specify a device to exclude and leave the “include” field blank. That will create the media player and sensor entities for everything except the device(s) your exclude.
How did you get volume_level attribute?
Do you set volume programmatically?
If so, paste here an example, please.
The volume level can be accessed in automations and scripts by filling in the attribute field in a State trigger or condition, or by using a template: {{ state_attr('media_player.echo_dot', 'volume_level')}}
Volume can be set using the media_player.volume_set service.
- service: media_player.volume_set
target:
entity_id: media_player.your_echo
data:
volume_level: 0.3
1 Like
Try reloading the integration from your Settings > Devices & Services > Integrations page. In the past there were issue where the websocket would fail and it would affect receiving info from Amazon including volume level, and reloading would reestablish the connection.
I am still using 3.11.3
This is what happened when I reloaded it…
mac_dms not detected; websocket likely won't connect
5:22:39 AM – (WARNING) /usr/local/lib/python3.9/site-packages/alexapy/alexawebsocket.py
No access token found; falling back to credential login instead of oauth.
5:22:39 AM – (WARNING) /usr/local/lib/python3.9/site-packages/alexapy/alexalogin.py
I will try again when I decide to update.
I have seen people saying reauth is needed on every boot, so I will wait a little more.
Thanks
I think it’s standard stuff for the Alexa Media Player integration. That attribute was created for me automatically.
1 Like
The majority of people experiencing that issue updated without reading or understanding the breaking changes notification. When they updated they did not remove the old alexa_media login configuration from configuration.yaml. The legacy login method has been causing issues for a number of users for a while, so it has been deprecated.
1 Like
At some point my ‘alexa media player’ integration stopped working. I’m using it to announce when the doorbell rings. On the integrations page, it says “Not loaded”. I can’t delete it either. I renamed the authentication file pickle file to .old. I installed all HA updates, I rebooted, I tried removing the integration again… nothing. I tried disabling and then enabling. No change - I can’t delete it. Any tips?
To be honest, the import failure because of the old configuration.yaml is probably a bug that no one has actually reported (i.e., I had intended for that to actually still work but since most people are fine after removing, there’s little incentive to fix it), but otherwise you’re right. A lot of people updated without reviewing the change log. The main issue is that a lot of people had degraded functionality and we never surfaced it so it would sorta “work” and people would randomly complain about stuff not working (i.e., stuff doesn’t update instantly, reminders/timers/alarms didn’t show, etc.).
As of 4.0.x we don’t allow the degraded state so everyone who was sorta working is now being forced to reauthenticate. While there could be an issue with the reauthenticating, I haven’t seen any bug reports that show it’s more than user error yet.
I got it working. My version of alexa media player was on 3.10.15 (if I remember right) and way out of date. I did not realize my hacs integrations have to be manually updated. I updated it via HA ui in hacs and then recreated the 2fa code and it is working now.
I am having this issue regularly… can you please share details of how you recreated the 2fa code?
I am having this issue regularly… can you please share details of how you recreated the 2fa code?
Mine stopped working again and I haven’t had time to dig back into it. I’m guessing it is a different reason this time as to why it stopped working from my previous issue.
Thanks. Confirming that it is the same information I had. After two very long days, I submitted a detailed github request I am unable to re-authenticate alexa_media_player api · Issue #1648 · custom-components/alexa_media_player · GitHub
The sad part is, when it was working it was a true charm. Can you or anyone else provide any guidance?
1 Like