ioBroker.alexa2: alexa2.0.Echo-Devices.[dev_id].Commands not working in 3.12.0

Hi, I don’t know if it’s coincidence or related but since I updated my js-controller to 3.3.19 my whole alexa2.0.Echo-Devices.[dev_id].Commands are not working on my echo-dot. (rebooted it, restarted adapter) It does not matter if I use say, or trigger funcfact or whatever. Nothing happens. I tried to debug - the following lines appear:

` alexa2.0 2021-11-19 12:09:02.377 debug 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":{"customerId":"A2DCYSWB9T88GE","expireAfter":"PT5S","content":[{"locale":"de-DE","display":{"title":"ioBroker","body":"Testansage. sag was! "},"speak":{"type":"ssml","value":"<speak>Testansage. sag was! </speak>"}}],"target":{"customerId":"A2DCYSWB9T88GE","devices":[{"deviceSerialNumber":"G090XG07939309UQ","deviceTypeId":"A1RABVCI4QCIKC"}]}},"type":"AlexaAnnouncement"}]}}”,“status”:“ENABLED”}

alexa2.0 2021-11-19 12:09:02.376 debug Alexa-Remote: No authentication check needed (time elapsed 107319)

alexa2.0 2021-11-19 12:09:02.372 debug State changed alexa2.0.Echo-Devices.G090XG07939309UQ.Commands.ssml: {“val”:“<speak>Testansage. sag was! </speak>”,“ack”:false,“ts”:1637320142369,“q”:0,“from”:“system.adapter.admin.0”,“user”:“system.user.admin”,“lc”:1637320142369}

alexa2.0 2021-11-19 12:09:02.370 silly States user redis pmessage io.alexa2.0.*/io.alexa2.0.Echo-Devices.G090XG07939309UQ.Commands.ssml:{“val”:“<speak>Testansage. sag was! </speak>”,“ack”:false,“ts”:1637320142369,“q”:0,“from”:“system.adapter.admin.0”,“user”:“system.user.admin”,“lc”:1637320142369}`

Is there a general problem, or is it with my echo dot or installation? What can I do? The interesting thing is - it seems not only say related - the whole commands do not work while the IOT adapter in combination with text2command works and triggers speech outputs.

Thanks for help and advice!

Cheers

Wolfgang

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 41 (15 by maintainers)

Most upvoted comments

Immer noch genauso, weiterhin “bald” … 3.11.2 tut doch wieder wie vorher … von daher einfacher workaround …

Noch keine Zeit gehabt, kommt aber die Tage dran.

Ich hänge mich hier einmal mit ran, Log sende ich per Mail

Ich habe die Logs gesendet . Wenn es nicht reicht gerne Info. Besten Dank vorab