Apollon77 / ioBroker.alexa2

ioBroker Adapter to control Amazon Alexa/Echo devices
MIT License
163 stars 47 forks source link

History is not updating #1181

Closed matze939939 closed 2 months ago

matze939939 commented 2 months ago

Describe the bug: Alexa Adapter doesn't provide a history since two days. See debug log attached. In the alexa app it is still working. I tried the following:

Get new cookies Trigger the update manually using the DP In Alexa App commands are shown in history Push connection is enabled - everything in adapter is on standard settings. To Reproduce Talk to alexa, check if history json or summary gets updated.

Expected behavior history json or summary should update.

Screenshots & Logfiles I attached logfiles from debug (start of adapter until voice command)

Versions:

Adapter version: 3.26.5 JS-Controller version: 6.0.11 Node version: v18.20.4 Operating system: Debian

Bildschirmfoto vom 2024-09-06 12-44-25

Apollon77 commented 2 months ago

Please add the debug log ... but please also make sure that the adapter was fully initialized before you did the test because this can take some minutes ! For me all is working as expected

Apollon77 commented 2 months ago

"Everything is standard settings"? YOu need to enable that history is taken automatically ... else ONLY the #trigger gets an update

matze939939 commented 2 months ago

Everything worked well sind April 2024. Without any change, History no longer updating. Here's the Log:

2024-09-06 13:24:47.071 - debug: alexa2.0 (1661) Alexa-Remote: Response: {"access_token":"Atna|EwICIHaszoDOBpEz5RQ8SGZeCXCSAnByAVnjs0xqDhTS2dxe-ZTMKrGNglRHyhYHHK2yP_UUO63cwZcACLFr66SS9XEx1ftKPqVSPpwcwcTIDvXKzhZ5VrqC5pPvlN3LsRMpOLcOHVelZmiK_62v5EJSW8IKNaDgVxkAqiWhMN1NBEQ-jNRTecGJgxVOtVdObGv5BcMZ7fCuYzhG79EL5wPiqq7JHUVSAHMUE1jy4MlOmU1sbdK0O0giXj-25tUj4GMGw3IRX353syyC7R6F7rxRThTFYIwLzkcvKzQeUpjC_ZUdbZxS9zuV083wyX7WxDwwn3WTfGouqZpQhu94k-0apmgq0_X_HZ3414poE1AhEC-YGKS-MAEM_zxjsNxC3JLndu_rmgvPEaHQTjK7ZUpHChQW","response":{"token_expires_in":"3600","token_type":"bearer_token","token":"Atna|EwICIHaszoDOBpEz5RQ8SGZeCXCSAnByAVnjs0xqDhTS2dxe-ZTMKrGNglRHyhYHHK2yP_UUO63cwZcACLFr66SS9XEx1ftKPqVSPpwcwcTIDvXKzhZ5VrqC5pPvlN3LsRMpOLcOHVelZmiK_62v5EJSW8IKNaDgVxkAqiWhMN1NBEQ-jNRTecGJgxVOtVdObGv5BcMZ7fCuYzhG79EL5wPiqq7JHUVSAHMUE1jy4MlOmU1sbdK0O0giXj-25tUj4GMGw3IRX353syyC7R6F7rxRThTFYIwLzkcvKzQeUpjC_ZUdbZxS9zuV083wyX7WxDwwn3WTfGouqZpQhu94k-0apmgq0_X_HZ3414poE1AhEC-YGKS-MAEM_zxjsNxC3JLndu_rmgvPEaHQTjK7ZUpHChQW"},"token_type":"bearer","expires_in":3600,"request_id":"fd511c96-61b6-41d5-9b36-46d39a733626"} 2024-09-06 13:24:47.072 - debug: alexa2.0 (1661) Alexa-Remote: Auth token: Atna|EwICIHaszoDOBpEz5RQ8SGZeCXCSAnByAVnjs0xqDhTS2dxe-ZTMKrGNglRHyhYHHK2yP_UUO63cwZcACLFr66SS9XEx1ftKPqVSPpwcwcTIDvXKzhZ5VrqC5pPvlN3LsRMpOLcOHVelZmiK_62v5EJSW8IKNaDgVxkAqiWhMN1NBEQ-jNRTecGJgxVOtVdObGv5BcMZ7fCuYzhG79EL5wPiqq7JHUVSAHMUE1jy4MlOmU1sbdK0O0giXj-25tUj4GMGw3IRX353syyC7R6F7rxRThTFYIwLzkcvKzQeUpjC_ZUdbZxS9zuV083wyX7WxDwwn3WTfGouqZpQhu94k-0apmgq0_X_HZ3414poE1AhEC-YGKS-MAEM_zxjsNxC3JLndu_rmgvPEaHQTjK7ZUpHChQW 2024-09-06 13:24:47.072 - debug: alexa2.0 (1661) Alexa-Remote: Initialize WS-MQTT Push Connection 2024-09-06 13:24:47.072 - debug: alexa2.0 (1661) Alexa-Remote: Update access token ... 2024-09-06 13:24:47.072 - debug: alexa2.0 (1661) Alexa-Remote HTTP2-PUSH: Use host bob-dispatch-prod-eu.amazon.com 2024-09-06 13:24:47.366 - debug: alexa2.0 (1661) Alexa-Remote HTTP2-PUSH: Initialization completed 2024-09-06 13:24:47.366 - info: alexa2.0 (1661) Alexa-Push-Connection (macDms = true) established. Disable Polling 2024-09-06 13:24:49.568 - debug: alexa2.0 (1661) Alexa-Remote: Response: Error: Error: socket hang up 2024-09-06 13:25:06.273 - debug: alexa2.0 (1661) Alexa-Remote: Response: Error: Error: socket hang up

matze939939 commented 2 months ago

Solved: After rebooting the router, the connection/updating of the data points works again. Thanks for the quick support!