Same With Only 81 devices exposed 
maybe this should give you some ideas:
Unfortunately the extended SQS client relies in S3 for large messages which doesn’t have an unlimited free tier.
I pushed out a new version (1.0.7) which should handle the large response. It’ll send multiple SQS messages back via SQS and they get re-assembled.
Give it a try and let me know if it works. I don’t have that many devices to have a real large response but I tried to mimic it with some fake data and it seems to work.
Thanks, no more error now.
Only have to find a way to easyly manage the excluded ans included entitys
Another question, what is “reconstruct (in french reconstruire)” close to Start .Restart .Stop ?
What is the good way to reinclude the apparels with your Addon ?
Thanks again !
Eric
It is “Rebuild”.
I am not too sure. I think it recreates the docker image the addon uses. I am not sure when you’d want to press it.
I am not sure what you mean by this. Entity inclusion/exclusion is the same as whatever HomeAssistant uses for exposing devices to Alexa.
Thanks,
I mean, do I have to restart your plugin when I change my alexa’s excusion in config.yaml ? Do I allso have to unlink and relink you skill in Alexa ?
You don’t need to specifically restart the addon or relink anything. You just need to ensure HomeAssistant is picking up the config.yaml changes
I’m wondering if this add-on would overcome the following limitation for me:
I have two homes with separate HA instances. Both homes use a bunch of Alexa devices associated with the same single Amazon account. Since the HA Alexa skill can only be set up once, I cannot associate the devices of my second home with my second HA instance, as the skill is already taken by my first HA instance.
Will this add-on here allow me to associate devices from my second home with my second HA instance, circumventing the need for the official HA skill? Thanks!
I haven’t tried it but I think it would work. You would be basically setting up a second skill and enabling it. You might need to ensure you don’t have name collisions between the 2 houses.
1 Like
Thank you Adam! It took me a bit of time to set all this up but I’m finally all set up. I have two main points of feedback:
-
The Add-On doesn’t clean up any prior failed Stacks or Log Groups, so when you initially run into an error, one has to then manually remove the stack from the CloudFormation web page, and then manually remove two Log Groups using the AWS CLI. I think it would be a good enhancement if the Add-On were to check for whether the stack is in an error state (i.e. a rollback error), then automatically delete the entire stack and all log groups, then re-create the stack.
-
The Add-On exposes all 200+ devices I have in HA. Is there a way to make it respect my selection of which HA devices I want to expose through the Alexa assistant?
All else is great 
-
I am surprised you needed to delete any log groups manually - deleting the CloudFormation stack should have deleted the log groups too. I see about an auto-delete on creation failure.
-
The addon proxies exactly what is exposed in HomeAssistant. Official docs
If more devices are being exposed then you’ll need to double check that your configuration is picked up by HA.
1 Like
I see my mistake – I was thinking that it would follow the selections I made in the UI for which entities should be exposed to Alexa. It didn’t occur to me that this is entirely separate and requires manually expressing filters in the configuration.yaml.
After days of fighting Cloudflare firewall rules and access policies trying to lock down access to something other than Everyone or permitting 900+ IP ranges for AWS us-east-1 (which leaves it open to anyone with a VM on AWS), I had my skill linked and 56 new devices discovered in less than 10 minutes! Thank you!
Now if I could only do the same with the Alexa Actionable Notifications skill…
I am also having this problem. Please advise if there is a solution. There is no such thing as ‘Alexa Smart Home’ for source, only ‘Alexa’. There is also no ‘Smart Home’ option or anything like it. Any thoughts?
Hi @adamirr
found a little typo in the documentation:
Select the appropraite region for where your Alexa skill is located
us-east-1 for English (US) or English (CA) skills
eu-east-1 for English (UK), English (IN), German (DE), Spanish (ES) or French (FR) skills
us-west-2 for for Japanese and English (AU) skills.
Fill in your Alexa Skill Id from when you setup the skill before
instead of eu-east-1 it should be eu-west-1
What about me? 
arrght - sorry - mixed it up
Hi Adamirr, Just posting to say many thanks for this Alexa integration Addon. All up and running as expected
1 Like
