Apollon77 / ioBroker.alexa2

ioBroker Adapter to control Amazon Alexa/Echo devices
MIT License
160 stars 46 forks source link

No smart home devices to query #1169

Closed matze939939 closed 4 months ago

matze939939 commented 4 months ago

Amazon Echo Devices no longer listed - still working in AlexaApp

Without adjustments, the Alexa devices (Objects folder Echo Devices) are suddenly no longer displayed. Restarting the adapter and renewing the Amazon cookies were unsuccessful.

Versions:

Apollon77 commented 4 months ago

Hm ... Ok Whats the issue now? Amazon Devices at all? Or Smart Home devices? There are two completely different things.

Pleas enable debug log and post log

matze939939 commented 4 months ago

Hi, only the amazon Devices are missing. The Smart Home devices are available (cached).

Here's the Debug Log:

2024-05-08 18:07:13.550 - debug: alexa2.0 (858242) Alexa-Remote: No authentication check needed (time elapsed 53477) 2024-05-08 18:07:13.550 - debug: alexa2.0 (858242) Alexa-Remote: Sending Request with {"host":"eu-api-alexa.amazon.de","path":"/api/phoenix?includeRelationships=true","method":"GET","timeout":30000,"headers":{"Accept-Language":"de-DE"}} 2024-05-08 18:07:43.572 - debug: alexa2.0 (858242) Alexa-Remote: Response: Error: Error: socket hang up 2024-05-08 18:07:43.575 - info: alexa2.0 (858242) Using cached smart home devices list from Mon May 06 2024 22:26:22 GMT+0200 (Central European Summer Time) . . . 2024-05-08 18:07:43.580 - info: alexa2.0 (858242) Could not get smart home devices from Amazon. Using cached list. . . . 2024-05-08 18:07:57.109 - info: alexa2.0 (858242) Initialization Done ... 2024-05-08 18:08:07.169 - debug: alexa2.0 (858242) Alexa-Remote: Response: Error: Error: socket hang up 2024-05-08 18:08:07.169 - debug: alexa2.0 (858242) Alexa-Remote: Error getting auth token: socket hang up 2024-05-08 18:08:07.169 - debug: alexa2.0 (858242) Alexa-Remote: Error getting auth token: socket hang up 2024-05-08 18:08:07.169 - debug: alexa2.0 (858242) Alexa-Remote: Initializing WS-MQTT Push Connection failed because no Access-Token available! 2024-05-08 18:08:16.544 - debug: alexa2.0 (858242) Alexa-Remote: Response: Error: Error: socket hang up 2024-05-08 18:12:57.111 - debug: alexa2.0 (858242) Alexa-Remote: No authentication check needed (time elapsed 397038) 2024-05-08 18:12:57.111 - debug: alexa2.0 (858242) Alexa-Remote: Sending Request with {"host":"eu-api-alexa.amazon.de","path":"/api/devices-v2/device?cached=true&_=1715184777111","method":"GET","timeout":10000,"headers":{"Accept-Language":"de-DE"}} 2024-05-08 18:13:07.141 - debug: alexa2.0 (858242) Alexa-Remote: Response: Timeout 2024-05-08 18:13:07.142 - debug: alexa2.0 (858242) Alexa-Remote: No authentication check needed (time elapsed 407069) 2024-05-08 18:13:07.142 - debug: alexa2.0 (858242) Alexa-Remote: Sending Request with {"host":"eu-api-alexa.amazon.de","path":"/api/bluetooth?cached=true","method":"GET","timeout":10000,"headers":{"Accept-Language":"de-DE"}}

Apollon77 commented 4 months ago

"socket hang up"? Thats clearly netwlok stuff ... please check any firewalls, proxies, maybe pohole or other anto-whatever systems. Is there anything? Maybe reboot the host ...

matze939939 commented 4 months ago

Thanks for the tip, it was due to a block list entry in the pihole. Amazon domain whitelisted - devices are found again.