Announcing Native Amazon Echo integration

I was torn between the Echo and Dotand went with Dots as I will be playing music through Sonos, but I didn’t notice the difference in shipping dates. I still have 3 weeks to wait. :pensive:

I bought 2 echos and a dot along with a remote. The echos and the remote arrive wednesday, the dot is a few weeks after that. Intending on using Echo in the living room and kitchen, dot in the bedroom. Remote was a bit of a weird purchase, not really sure what I’m going to do with it lol

Apologies in advance if this has already been addressed, but I’ve read through all 39 pages of the chain and didn’t see it mentioned:

After attempting to create the Lambda/Skill a couple times, I get the following Lambda error message. Has anyone else encountered this? Is there a known fix?

{
“errorMessage”: “Process exited before completing request”
}

[quote=“Aura, post:583, topic:189448”]Apologies in advance if this has already been addressed, but I’ve read through all 39 pages of the chain and didn’t see it mentioned:

After attempting to create the Lambda/Skill a couple times, I get the following Lambda error message. Has anyone else encountered this? Is there a known fix?

{
“errorMessage”: “Process exited before completing request”
}[/quote]

I’ve not seen that myself. When do you get the error?

Martin

[quote=“martin12345”][quote=“Aura, post:583, topic:189448”]{
“errorMessage”: “Process exited before completing request”
}[/quote]

I’ve not seen that myself. When do you get the error?

Martin[/quote]

I had that in my logs when I was as testing my setup before is started working yesterday when the uk systems came online. I don’t think that error is there now though.

Sent from my iPhone using Tapatalk

Not sure whats wrong, this is the arn number i get,

arn:aws:lambda:us-west-2:922745777440:function:Myfunction

yet when i try to use it i get

Invalid ARN for NA region. Please provide a valid ARN in the form ‘arn:aws:lambda:us-east-1:000000000000:function:myFunction:myFunctionVersion’

I am in canada but i doubt that matters.

Also one other question, i use another skill named simple control to control my av equipment, can i make my own invocation word to be simple control as well so i can also control lights thermostats in addition to my av equipment ect… or will they conflict? I dont know if alexa will look to both apps then or if it will simply conflict.

[quote=“Ghostm, post:586, topic:189448”]Not sure whats wrong, this is the arn number i get,

arn:aws:lambda:us-west-2:922745777440:function:Myfunction

yet when i try to use it i get

Invalid ARN for NA region. Please provide a valid ARN in the form ‘arn:aws:lambda:us-east-1:000000000000:function:myFunction:myFunctionVersion’

I am in canada but i doubt that matters.[/quote]
As it says in the error message, you have an arn that is for lambda:us-west-2, but it needs to be in arn:aws:lambda:us-east-1. Deploy the lambda function to the right region (us east) and it will work.

The HA skills respond to commands like “Alexa, turn X on” whereas your skill will respond to commands like “Alexa, tell simple control to turn X on”. No, you can’t change that.

There are a couple of updates to the code which people can uptake if they are interested. One change is to allow you to optionally add the word “Scene” to the end of the scene names, and the other is to report the status of Stats along with the temperature. Thanks very much to Jim McGhee for those two changes.

Martin

Martin, it’s been a while since Ingrid your plugin…any news on Amazon adopting it for us Vera users using your servers ? Tnx

Sent from my iPhone using Tapatalk

[quote=“MrAutomate, post:591, topic:189448”]Martin, it’s been a while since Ingrid your plugin…any news on Amazon adopting it for us Vera users using your servers ? Tnx

Sent from my iPhone using Tapatalk[/quote]
Amazon won’t approve it for distribution until Vera supports OAuth.

Martin

Thanks Martin

Sent from my iPhone using Tapatalk

Now all we need is for the uk version to support ifttt and we’re all setup :slight_smile:

Sent from my iPhone using Tapatalk

I’ve also added a new feature to allow you to not discover devices. The problem I face is that Amazon keep unforgetting the devices and scenes I tell it to forget, so I have added the ability to list the devices that you don’t want discovered in the first place.

Martin

That’s exactly what I need!!! Thank you so much :slight_smile:

Sent from my iPhone using Tapatalk

I just tried
var devicesToIgnore=[“243”,“244”,“245”,“246”,“247”,“248”,“249”,“250”,“251”,“252”,“253”,“254”,“255"“S12”,“S13”,“S39”,“S40”,“S41”]; // create a list of IDs to ignore, e.g. [“252”,S7”] to exclude devices from discovery

And its’ still picking them up, did I do it wrong?

[quote=“CelticWebs, post:597, topic:189448”]I just tried
var devicesToIgnore=[“243”,“244”,“245”,“246”,“247”,“248”,“249”,“250”,“251”,“252”,“253”,“254”,“255"“S12”,“S13”,“S39”,“S40”,“S41”]; // create a list of IDs to ignore, e.g. [“252”,S7”] to exclude devices from discovery

And its’ still picking them up, did I do it wrong?[/quote]
Picking them up when you do a test in Lambda, or picking them up in the Alexa app? I think you need to forget them in the Alexa app if they are currently there - it won’t remove previously found devices even if they are not discovered.

They were already previously forgotten, I did a discover and it found them all again.

I’ve just spotted that you have a typo. You are missing a comma at "255"“S12”. That’s causing your problem.