Apollon77 / ioBroker.alexa2

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

Alexa2.0 Commands are not working anymore. #582

Closed polocup100 closed 3 years ago

polocup100 commented 3 years ago

Since a few weeks the speak command is not working, the other commands also not work.

I tryed V3.3.1 and 3.2.4. I get no error in the Logfile.

Any known Problems? History is working fine.

Admin 4.0.10

alexa2.0 2020-12-01 23:02:58.675 info (10494) Alexa-Push-Connection established. Disable Polling
alexa2.0 2020-12-01 23:02:56.833 info (10494) Subscribing to states...
alexa2.0 2020-12-01 23:02:42.962 info (10494) Alexa-Push-Connection disconnected - retry: Retry Connection in 15s
alexa2.0 2020-12-01 23:02:42.960 info (10494) Alexa-Push-Connection disconnected - retry: Retry Connection in 10s
alexa2.0 2020-12-01 23:02:42.958 info (10494) Alexa-Push-Connection Error: Error: WebSocket was closed before the connection was established
alexa2.0 2020-12-01 23:02:13.931 info (10494) Device-type:A1ZB65LA390I4K (VOLUME_SETTING,REMINDERS,TIMERS_AND_ALARMS,ASCENDING_ALARM_VOLUME,PERSISTENT_CONNECTION,DIALOG_INTERFACE_VERSION,CUSTOM_ALARM_TONE,SUPPORTS_SOFTWARE_VERSION,SO
alexa2.0 2020-12-01 23:02:13.930 info (10494) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2020-12-01 23:02:13.929 info (10494) Unknown Device, but enabling commands, Try it and report back if commands work.
alexa2.0 2020-12-01 23:02:13.801 info (10494) Device-type:A9YU3XB1OZ676 (DEEZER,VOLUME_SETTING,CHANGE_NAME,DEREGISTER_DEVICE,AMAZON_MUSIC,REMINDERS,TIMERS_AND_ALARMS,SIRIUSXM,PERSISTENT_CONNECTION,TIDAL,KINDLE_BOOKS,SUPPORTS_CONNECTE
alexa2.0 2020-12-01 23:02:13.800 info (10494) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted
alexa2.0 2020-12-01 23:02:13.799 info (10494) Unknown Device, but enabling commands, Try it and report back if commands work.
alexa2.0 2020-12-01 23:02:08.441 info (10494) starting. Version 3.2.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v12.18.3, js-controller: 3.1.6

Best regards

Sascha

Apollon77 commented 3 years ago

No problems are know at the moment. Please try to setup a routine in the alexa app. Is speak working there? if not ... this is your reason

polocup100 commented 3 years ago

With a routine it is working.

Ingo Fischer notifications@github.com schrieb am Di., 1. Dez. 2020, 23:27:

No problems are know at the moment. Please try to setup a routine in the alexa app. Is speak working there? if not ... this is your reason

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Apollon77/ioBroker.alexa2/issues/582#issuecomment-736860115, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZ7FDHSYDFULFBFXAQAPKTSSVUVVANCNFSM4UJT5ZNA .

Apollon77 commented 3 years ago

Please set adapter to debug log (Instances - export mode - column loglevel) and provide debug log of such a speak command

Apollon77 commented 3 years ago

Also: is announcement or any other command working?

polocup100 commented 3 years ago

Here is the Log:

alexa2.0 2020-12-02 07:44:54.008 debug (31522) Alexa-Remote: Sending Request with {"host":"alexa.amazon.de","path":"/api/behaviors/preview","method":"POST","timeout":10000,"headers":{}} and data={"behaviorId":"PREVIEW","sequenceJson":"{\" alexa2.0 2020-12-02 07:44:54.007 debug (31522) Alexa-Remote: No authentication check needed (time elapsed 243581) alexa2.0 2020-12-02 07:44:54.005 debug (31522) State changed alexa2.0.Echo-Devices.G090LF1174550NK6.Commands.speak: {"val":"Test","ack":false,"ts":1606891494001,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1606891

other Commands are also not working, like good morning...

Am Mi., 2. Dez. 2020 um 00:07 Uhr schrieb Ingo Fischer < notifications@github.com>:

Also: is announcement or any other command working?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Apollon77/ioBroker.alexa2/issues/582#issuecomment-736876477, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZ7FDGMHSG6J74UVH7VMN3SSVZJLANCNFSM4UJT5ZNA .

Apollon77 commented 3 years ago

For me everything is working. What are this for devices?

Please provide the log again but from the logfile on disk and not from admin (admin cut lines!)

And best save a manual "speak" routine and send the log from a direct speak and from activating that routine from within the adapter (restart adapter after you saved the routine)

polocup100 commented 3 years ago

Devices Echo Dot2,3 or show10".

2020-12-02 17:22:01.095 - [34mdebug [39m: alexa2.0 (10887) State changed alexa2.0.Echo-Devices.G090LF1174550QB7.Commands.speak: {"val":"Flurtür 2OG schließen","ack":false,"ts":1606926121089,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1606924653750} 2020-12-02 17:22:01.098 - [34mdebug [39m: alexa2.0 (10887) Alexa-Remote: No authentication check needed (time elapsed 337288) 2020-12-02 17:22:01.098 - [34mdebug [39m: alexa2.0 (10887) Alexa-Remote: Sending Request with {"host":"alexa.amazon.de","path":"/api/behaviors/preview","method":"POST","timeout":10000,"headers":{}} and data={"behaviorId":"PREVIEW","sequenceJson":"{\"@type\":\"com.amazon.alexa.behaviors.model.Sequence\",\"startNode\":{\"@type\":\"com.amazon.alexa.behaviors.model.SerialNode\",\"name\":null,\"nodesToExecute\":[{\"@type\":\"com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode\",\"operationPayload\":{\"deviceType\":\"A3S5BH2HU6VAYF\",\"deviceSerialNumber\":\"G090LF1174550QB7\",\"locale\":\"de-DE\",\"customerId\":\"ASKC63P3YLN5L\",\"value\":4},\"type\":\"Alexa.DeviceControls.Volume\"},{\"@type\":\"com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode\",\"operationPayload\":{\"deviceType\":\"A3S5BH2HU6VAYF\",\"deviceSerialNumber\":\"G090LF1174550QB7\",\"locale\":\"de-DE\",\"customerId\":\"ASKC63P3YLN5L\",\"textToSpeak\":\"Flurtür 2OG schließen\"},\"type\":\"Alexa.Speak\"},{\"@type\":\"com.amazon.alexa.behaviors.model.OpaquePayloadOperationNode\",\"operationPayload\":{\"deviceType\":\"A3S5BH2HU6VAYF\",\"deviceSerialNumber\":\"G090LF1174550QB7\",\"locale\":\"de-DE\",\"customerId\":\"ASKC63P3YLN5L\",\"value\":50},\"type\":\"Alexa.DeviceControls.Volume\"}]}}","status":"ENABLED"}

what do you mean with a manual "speak" routine ...

Am Mi., 2. Dez. 2020 um 08:50 Uhr schrieb Ingo Fischer < notifications@github.com>:

For me everything is working. What are this for devices?

Please provide the log again but from the logfile on disk and not from admin (admin cut lines!)

And best save a manual "speak" routine and send the log from a direct speak and from activating that routine from within the adapter (restart adapter after you saved the routine)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Apollon77/ioBroker.alexa2/issues/582#issuecomment-737057493, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZ7FDCBQ3AMJAQD5BYJLILSSXWUFANCNFSM4UJT5ZNA .

Apollon77 commented 3 years ago

what do you mean with a manual "speak" routine ...

Create a routine in alexa app that uses Speak (aslexa says something) with a custom text. the restart adapter and start this routine from the adapter

ghost commented 3 years ago

Hi habe auch das problem das Speak und Announcement nicht mehr funktionieren. Synology 218+ Docker habe den adapter schon neuinstalliert ... leider ohne erfolg. -------

Update; Funktioniert wider mit aktueller Version 3.3.5

Danke

beandi commented 3 years ago

Same here, "Speak" does not work anymore. Had no issues for the last ~18 months. (Adapter 3.3.1) iobroker on Debian.

canim60 commented 3 years ago

habe mein Pi neugestartet, seit dem funktioniert der Speak nichtmehr, über Routine geht es einwandfrei

Wenn ich über Routine was sagen lasse kommt das im Debu

`

alexa2.0 2020-12-03 19:59:53.473 debug (2862) Alexa-Remote: 0 entries left in activity queue
alexa2.0 2020-12-03 19:59:53.470 debug (2862) device-activity: {"data":{"_disambiguationId":null,"activityStatus":"SUCCESS","creationTimestamp":1607021992754,"description":"{\"summary\":\"\",\"firstUtteranceId\":\"A1RABVCI4QCIKC:1.0/2020/1
alexa2.0 2020-12-03 19:59:53.469 debug (2862) Alexa-Remote: Activity found 0 for Activity ID 1607021992754#A1RABVCI4QCIKC#G0911M06928523QQ
alexa2.0 2020-12-03 19:59:53.467 debug (2862) Alexa-Remote: Response: {"activities":[{"_disambiguationId":null,"activityStatus":"SUCCESS","creationTimestamp":1607021992754,"description":"{\"summary\":\"\",\"firstUtteranceId\":\"A1RABVCI4QC
alexa2.0 2020-12-03 19:59:53.098 debug (2862) Alexa-Remote: Sending Request with {"host":"alexa.amazon.de","path":"/api/activities?startTime=&size=3&offset=1","method":"GET","timeout":10000,"headers":{}}
alexa2.0 2020-12-03 19:59:53.097 debug (2862) Alexa-Remote: No authentication check needed (time elapsed 88920)
alexa2.0 2020-12-03 19:59:52.895 debug (2862) Alexa-Remote WS-MQTT: Command PUSH_ACTIVITY: { "destinationUserId": "A1PT5EBRCA41TF", "timestamp": 1607021992773, "key": { "registeredUserId": "A1PT5EBRCA41TF", "ent
alexa2.0 2020-12-03 19:59:50.501 debug (2862) Alexa-Push-Connection Device Volume change for 6845b1afa33a4caca903d2dafbce7b7b -> 87/false
alexa2.0 2020-12-03 19:59:50.500 debug (2862) Alexa-Remote WS-MQTT: Command PUSH_VOLUME_CHANGE: { "destinationUserId": "A1PT5EBRCA41TF", "dopplerId": { "deviceType": "A2TF17PFR55MTB", "deviceSerialNumber": "6845b1af

`

Lodenhaarbaer commented 3 years ago

Hallo,

ich habe das gleiche Problem seit einem Neustart des Pi. Im Log steht das gleiche wie bei lordnaicon. Über eine Routine in der Alexa-App funktioniert alles.

polocup100 commented 3 years ago

nothing happens, when i start the routine from the adapter

best regards Sascha

Am Do., 3. Dez. 2020 um 08:30 Uhr schrieb Ingo Fischer < notifications@github.com>:

what do you mean with a manual "speak" routine ...

Create a routine in alexa app that uses Speak (aslexa says something) with a custom text. the restart adapter and start this routine from the adapter

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Apollon77/ioBroker.alexa2/issues/582#issuecomment-737721504, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZ7FDGRGC4L3V7SKAG25JDSS45C7ANCNFSM4UJT5ZNA .

polocup100 commented 3 years ago

2020-12-03 22:31:18.702 - [32minfo [39m: alexa2.0 (25090) Proxy IP not set, use first network interface (192.168.2.20) instead 2020-12-03 22:31:26.452 - [32minfo [39m: alexa2.0 (25090) Alexa-Push-Connection established. Disable Polling 2020-12-03 22:31:27.276 - [32minfo [39m: alexa2.0 (25090) Unknown Device, but enabling commands, Try it and report back if commands work. 2020-12-03 22:31:27.277 - [32minfo [39m: alexa2.0 (25090) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2020-12-03 22:31:27.278 - [32minfo [39m: alexa2.0 (25090) Device-type:A9YU3XB1OZ676 (CHANGE_NAME,REMINDERS,SLEEP,VOLUME_SETTING,TIMERS_AND_ALARMS,I_HEART_RADIO,TUNE_IN,DEREGISTER_DEVICE,MICROPHONE,AUDIBLE,MUSIC_SKILL,KINDLE_BOOKS,PERSISTENT_CONNECTION,AMAZON_MUSIC,GOLDFISH,DEEZER,APPLE_MUSIC,TIDAL,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,AUDIO_PLAYER,DREAM_TRAINING,SIRIUSXM) 2020-12-03 22:31:27.374 - [32minfo [39m: alexa2.0 (25090) Unknown Device, but enabling commands, Try it and report back if commands work. 2020-12-03 22:31:27.375 - [32minfo [39m: alexa2.0 (25090) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2020-12-03 22:31:27.376 - [32minfo [39m: alexa2.0 (25090) Device-type:A30YDR2MK8HMRV (UPDATE_WIFI,LEMUR_ALPHA,EQUALIZER_CONTROLLER_BASS,GADGETS,DISPLAY_BRIGHTNESS_ADJUST,SALMON,TUPLE_CATEGORY_A,PAIR_REMOTE,MUSIC_SKILL,KINDLE_BOOKS,EFDCARDS,PERSISTENT_CONNECTION,AMAZON_MUSIC,GOLDFISH,TIDAL,VOICE_TRAINING,SIRIUSXM,CHANGE_NAME,SUPPORTS_SOFTWARE_VERSION,DIALOG_INTERFACE_VERSION,SET_LOCALE,ALEXA_GESTURES,DEREGISTER_DEVICE,EQUALIZER_CONTROLLER_MIDRANGE,PAIR_BT_SINK,ALEXA_PRESENCE,SUPPORT_CALENDAR_ALERT,EARCONS,AUDIO_PLAYER,SUPPORTS_CONNECTED_HOME_CLOUD_ONLY,TUPLE,EQUALIZER_CONTROLLER_TREBLE,BT_PAIRING_FLOW_V2,SUPPORTS_LOCALE,MULTI_WAKEWORDS_SUPPORTED,REMINDERS,DS_VOLUME_SETTING,SUPPORTS_LOCALE_SWITCH,VOLUME_SETTING,TUNE_IN,TAHOE_BYOD,DISPLAY_ADAPTIVE_BRIGHTNESS,DISPLAY_POWER_TOGGLE,REQUIRES_OOBE_FOR_SETUP,GUARD_EARCON,FLASH_BRIEFING,POPTART,ACTIVE_AFTER_FRO,SLEEP,AUDIO_CONTROLS,PAIR_BT_SOURCE,CUSTOM_ALARM_TONE,ASCENDING_ALARM_VOLUME,TIMERS_AND_ALARMS,TIMERS_ALARMS_NOTIFICATIONS_VOLUME,I_HEART_RADIO,CLOCK_FORMAT_24_HR,MICROPHONE,AUDIBLE,FAR_FIELD_WAKE_WORD,SET_TIME_ZONE,DEEZER,SOUND_SETTINGS,PANDORA,APPLE_MUSIC,DREAM_TRAINING) 2020-12-03 22:31:27.394 - [32minfo [39m: alexa2.0 (25090) Unknown Device, but enabling commands, Try it and report back if commands work. 2020-12-03 22:31:27.395 - [32minfo [39m: alexa2.0 (25090) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2020-12-03 22:31:27.395 - [32minfo [39m: alexa2.0 (25090) Device-type:A1ZB65LA390I4K (SUPPORTS_LOCALE,REMINDERS,CUSTOM_ALARM_TONE,ASCENDING_ALARM_VOLUME,SUPPORTS_SOFTWARE_VERSION,SUPPORTS_LOCALE_SWITCH,VOLUME_SETTING,TIMERS_AND_ALARMS,DIALOG_INTERFACE_VERSION,ASX_TIME_ZONE,MICROPHONE,PERSISTENT_CONNECTION,SOUND_SETTINGS,NO_TIME_ZONE_SETTING) 2020-12-03 22:31:31.131 - [31merror [39m: alexa2.0 (25090) The "Echo-Devices.42f978136a6048428f755ebad25e46e0.Music-Provider." is invalid. Ids are not allowed to end in "." at Adapter.setObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1817:40) at /opt/iobroker/node_modules/iobroker.alexa2/main.js:346:25 at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2354:71) at processImmediate (internal/timers.js:456:21) 2020-12-03 22:32:02.694 - [31merror [39m: alexa2.0 (25090) The "Echo-Devices.4b3d754355dc497d99186e0c0894ea5d.Music-Provider." is invalid. Ids are not allowed to end in "." at Adapter.setObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1817:40) at /opt/iobroker/node_modules/iobroker.alexa2/main.js:346:25 at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:2354:71) at processImmediate (internal/timers.js:456:21) 2020-12-03 22:35:56.549 - [32minfo [39m: host.raspberrypi4-iobroker stopInstance system.adapter.alexa2.0 (force=false, process=true) 2020-12-03 22:35:56.565 - [32minfo [39m: host.raspberrypi4-iobroker stopInstance system.adapter.alexa2.0 send kill signal 2020-12-03 22:35:56.584 - [32minfo [39m: alexa2.0 (25090) Got terminate signal TERMINATE_YOURSELF 2020-12-03 22:35:56.589 - [32minfo [39m: alexa2.0 (25090) terminating 2020-12-03 22:35:56.591 - [32minfo [39m: alexa2.0 (25090) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

Am Mi., 2. Dez. 2020 um 08:50 Uhr schrieb Ingo Fischer < notifications@github.com>:

For me everything is working. What are this for devices?

Please provide the log again but from the logfile on disk and not from admin (admin cut lines!)

And best save a manual "speak" routine and send the log from a direct speak and from activating that routine from within the adapter (restart adapter after you saved the routine)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Apollon77/ioBroker.alexa2/issues/582#issuecomment-737057493, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQZ7FDCBQ3AMJAQD5BYJLILSSXWUFANCNFSM4UJT5ZNA .

Apollon77 commented 3 years ago

The Music Provider issue is fixed in 3.3.5 ... Rest we need to see

Apollon77 commented 3 years ago

Command still work on my devices ...

zaunermax commented 3 years ago

I've also noticed, that the announce command does not work on my sonos alexa connected device, not sure if the issue is connected 🤔 - I will investigate

Apollon77 commented 3 years ago

honestly: sonos speak/announce was broken by amazon several ties in the past :-(

zaunermax commented 3 years ago

oh, didn't know that - never mind then ^^

zaunermax commented 3 years ago

If I wanted to dig into the bugfixing myself, could you point me to somwhere where I could get started with developing/fixing adapters? 🤔 I tried searching the forums but i found it a bit tedious - thanks in advance 🙌

Apollon77 commented 3 years ago

Starting this with alexa2 adapter would be a veeer complex topic ;-) Ok the fix for this Music provider issue was rather easy, right because it is just ignoring a new entry that do not have a name ;-)

For in general adapter development we have groups in Telegram and discord and also in the forum ... if you do not have an own idea you can check the Adapter requests if something might interest you ;-) Then we support all new devs the best we can in the above mentioned channels

Apollon77 commented 3 years ago

a good starting point is also https://www.iobroker.net/#de/documentation/dev/adapterdev.md

ppb1308 commented 3 years ago

Hallo Apollon77,

wann sehe ich 3.3.5 im latest repository? Ich habe bisher nur 3.3.2 dort verfügbar...

The Music Provider issue is fixed in 3.3.5 ... Rest we need to see

Apollon77 commented 3 years ago

Lade mal dein Repo neu (Adapter der pfeil im kreis ... sonst Github install

Lodenhaarbaer commented 3 years ago

Danke, 3.3.5 funktioniert!

ppb1308 commented 3 years ago

Ja, danke, konnte 3.5.5 installieren und geht nun wieder.

Lade mal dein Repo neu (Adapter der pfeil im kreis ... sonst Github install