Open Dazer95 opened 2 weeks ago
jamieturner26
commented
1 week ago I had the same issue. The way I solved it was to use amazon.com instead of amazon.com.au. I also have these entries in my configuration.yaml file. Not everything becomes available, but the echos become available:
notify:
- platform: alexa_media
name: alexa_media
alexa_media:
accounts:
email: !secret amazon_email
password: !secret amazon_pass
url: amazon.com
Dazer95
commented
1 week ago Ah, I see. Turns out for me it was just the power being off at the wall, someone turned it off while I was awayOn 25 Oct 2024, at 12:15 PM, jamieturner26 @.***> wrote: I had the same issue. The way I solved it was to use amazon.com instead of amazon.com.au. I also have these entries in my configuration.yaml file. Not everything becomes available, but the echos become available: notify:
platform: alexa_media name: alexa_media
alexa_media: accounts: email: !secret amazon_email password: !secret amazon_pass url: amazon.com
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
Baffo69Ud
commented
1 week ago Hi, i solved during configuration of Alexa Media Player modifying "Amazon.eu" with my country , then in "Amazon.it" My error in log was: 2024-10-27 21:28:37.370 WARNING (MainThread) [alexapy.alexalogin] Domain amazon.com does not match reported account domain amazon.it; functionality is not likely to work, please fix. Hope this can help. Let us know.
jamieturner26
commented
1 week ago I have an unusual set up with Alexa devices because some functionality is geo-blocked in my country, like the available music subscription services, for no good reason. So I originally set up my devices on the Amazon.com site.
danielbrunt57
commented
1 week ago I had the same issue. The way I solved it was to use amazon.com instead of amazon.com.au.
Are your devices registered in your amazon.com account?
danielbrunt57
commented
1 week ago I have an unusual set up with Alexa devices because some functionality is geo-blocked in my country, like the available music subscription services, for no good reason. So I originally set up my devices on the Amazon.com site.
I was like that also. My first device I bought from amazon.com so that's where alexa originally pointed. Over the years I added more, then moved them to amazon.ca to get Telus Smart Home skill for Optik TV (which failed to work) then moved them back to amazon.com to get USA only music & Alexa Guard which wasn't offered in Canada for a long time. But guard was discontinued nearly a year ago as a free service and I no longer use that music skill so I recently moved them back to .ca, retried the Canadian only skill for Telus Optik (TV) control and that now works.
agmuz
commented
1 week ago look this 2024-10-29 09:22:54.657 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant, kurtyna
danielbrunt57
commented
1 week ago That warning is just a standard canned warning that HA logs for ALL custom components as HA has tested NONE of them. I have 31 of those warnings...
custom integration patch
custom integration pyscript
custom integration localtuya
custom integration sun
custom integration thermal_comfort
custom integration nodered
custom integration variable
custom integration battery_notes
custom integration composite
custom integration delete
custom integration currentcost
custom integration hyperhdr
custom integration scheduler
custom integration network_scanner
custom integration smartthinq_sensors
custom integration waste_collection_schedule
custom integration next_holiday
custom integration fontawesome
custom integration uniled
custom integration o365
custom integration watchman
custom integration input_timetable
custom integration sonoff
custom integration alarmo
custom integration arpscan_tracker
custom integration samsungtv_smart
custom integration alexa_media
custom integration average
custom integration config_editor
custom integration auto_backup
custom integration mass
custom integration ltss
custom integration homeseer
custom integration fordpass
custom integration setter
custom integration osrm_travel_time
custom integration saver
custom integration ocpp
custom integration hass_agent
custom integration simpleicons
custom integration var d
custom integration leviton_decora_smart_wifi
custom integration scrypted be sure
custom integration spook_inverse be
custom integration entity_tz be sur
custom integration bhyve
custom integration spook
custom integration hacs
custom integration adaptive_lighting
custom integration neviweb
custom integration lunar_phase
custom integration retry
custom integration spotcast
custom integration astromech
custom integration astroweather
custom integration browser_mod
custom integration battery_consumption
custom integration entity_controller
custom integration ha_skyfield
custom integration pfsensepo zmianie hasła na amzonie nie można uruchomić komponentu alexa, nie widzi echo dot i żadnychintegracji, dobrze że node-red widzi
danielbrunt57
commented
6 days ago @agmuz after changing the password on amzon, the alexa component cannot be started, it does not see echo dot and any integrations, it's good that node-red sees it
Did you remove/re-add the integration to instantiate your new password?
agmuz
commented
6 days ago usuwałem, przywracałem z kopii całego HA , próbowałem na starej wersji, na nowym innym konto, tragedia nie działa
"I deleted it, restored it from a copy of the entire HA, tried it on the old version, on the new one, on a different account, it doesn't work"
danielbrunt57
commented
6 days ago @agmuz Please have a look at trying @srescio's modification for alexapy, See issue Alexa Media Reauthentication Required - continuously appear: Login error detected; not contacting API #2453
agmuz
commented
6 days ago ok
agmuz
commented
6 days ago niestety wątek jest zbyt mdlisty , jednym działa innym nie , poczekam na jakieś sprawdzone rozwiązania
IMPORTANT: 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
all devices go unavailable except the mobile device tied to the account **To Reproduce**Login and all your devices will show as unavailable except your mobile device
Expected behavior
Screenshots
System details
const.pyor HA startup log): 4.13.5pip show alexapyin homeasssistant container or HA startup log):Debug Logs (alexa_media & alexapy) Please provide logs.
Additional context