Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabled devices #2641

Open
Dazer95 opened this issue Oct 21, 2024 · 17 comments
Open

Disabled devices #2641

Dazer95 opened this issue Oct 21, 2024 · 17 comments

Comments

@Dazer95
Copy link

Dazer95 commented Oct 21, 2024

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

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Login and all your devices will show as unavailable except your mobile device

Expected behavior

Screenshots

image

System details

Debug Logs (alexa_media & alexapy)
Please provide logs.

Additional context

@jamieturner26
Copy link

jamieturner26 commented Oct 24, 2024

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
Copy link
Author

Dazer95 commented Oct 25, 2024 via email

@Baffo69Ud
Copy link

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
Copy link

jamieturner26 commented Oct 28, 2024

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
Copy link
Collaborator

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
Copy link
Collaborator

danielbrunt57 commented Oct 29, 2024

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
Copy link

agmuz commented Oct 29, 2024

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
Copy link
Collaborator

danielbrunt57 commented Oct 29, 2024

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 pfsense

@agmuz
Copy link

agmuz commented Oct 29, 2024

po zmianie hasła na amzonie nie można uruchomić komponentu alexa, nie widzi echo dot i żadnychintegracji, dobrze że node-red widzi

@danielbrunt57
Copy link
Collaborator

danielbrunt57 commented Oct 29, 2024

@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
Copy link

agmuz commented Oct 29, 2024

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
Copy link
Collaborator

@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
Copy link

agmuz commented Oct 29, 2024

ok

@agmuz
Copy link

agmuz commented Oct 29, 2024

niestety wątek jest zbyt mdlisty , jednym działa innym nie , poczekam na jakieś sprawdzone rozwiązania

@eich0rn
Copy link

eich0rn commented Nov 25, 2024

same problem here with version 4.13.7.
reinstalled this several times but no change. all devices were discovered but immidiatly changed to unavailable -_-

@noobshoes
Copy link

Same issue here. Using amazon.com.au.

@danielbrunt57
Copy link
Collaborator

Do you see error 429: Too many requests in the initialization stage for the GET /api/phoenix call in debug logs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants