Alexa with Home Assistant Local for FREE Without Subscription

[@EverythingSmartHome]

Make sure to check out the Google Home video here: kzbin.info/www/bejne/iKKqmpJ9fpWfqrc

[@DanangWidiantoro]

14:57 can you help me at this point. no device is detected when discovering devices. do I need to do some other thing?

[@SamiAbboud-mz4kk]

Hello dear, I live in lebanon and there is a lot of internet outage. Once I lose internet my alexa (show 8 gen2) is only a bluetooth speaker. Is there any way I can use it locally to do basic control over my devices? Many thanks in advance.

[@jamiefl]

Excellent video. There have been a few small changes to the AWS interface, but first, when prompted, choose Python 3.8. If you choose 3.9, the test script in a further step will not run. Next, when you get to adding a trigger, Alexa Smart Home has been moved. Choose Alexa and on the next screen, choose Smart Home, and continue with the vide. Thank you. This is complicated, but doable the way you presented it.

[@junlong68]

I did not pay attention to your wording, and it took me 3 passes to figure out and fix “Alexa Smart Home” issue.

[@rexgold101]

@@junlong68 Yep.. I did the same too.. kept missing out on the second step about 4 times... however, in my case, 3.9 did work and did pass the test.

[@zx85]

Really handy addendum - thank you!

[@zlove6tiqt]

Also make sure you select one of these regions, otherwise at the end you will get an error in developer console for unsupported region: Asia Pacific (Tokyo) EU (Ireland) US East (N. Virginia) US West (Oregon)

[@thediabeticway9115]

No Alexa Smart Home! Do you just select the Alexa one as that is all there is? Sure a shame when doing videos they always change I learnt tthis with wear Os and now given up making helpful videos as it becomes hard work keep updating a video than text its self Great Video though so far I just so a sharch on what as changed but not sure why Alexa Home is not there now?

[@exepnakides]

For those of you in Europe (I'm in Greece) who are trying to follow the video and you are failing at the last step, when you are trying to enable the skill in the Alexa app. If the error you are encountering is "Invalid client id or redirect Uri", try change the client id in your Alexa skill from the Europe one (layla) to the US one. I was looking many hours what I did wrong in the process and when I changed the client id it finally worked. Except from that, awesome video like always. I had watched it as educational before, but know that I got in my hands a Raspberry Pi it was time to try it out. Thanks again and keep up the good work.

[@ricardomagalhaes1984]

it works thanks.

[@ari802002]

thanks it works for me too but I cannot see my devices living in Sweden

[@mioszszyrner5990]

Happend to me. You made my day!

[@bradpeabody3413]

This video was perfect. Followed the detailed step-by-step instructions and had Alexa working Home Assistant in 20 minutes. Great job! Coffee headed your way. One other option for using port 443 is using Apache as a reverse proxy. Port 443 is forwarded to my web proxy machine which then forwards the http request to home assistant server on port 8123.

[@EverythingSmartHome]

Thanks Brad, appreciate it! Glad you found it useful and got it working! Yes that is another option, there are quite a few ways to do it!

[@swooper2476]

Any way you can give a "how to" would be great! Im stuck on accessing 443. Ive tried to open it up, no luck, I was easily able to get 8123 working just fine. Agreed video was perfect as always.

[@pekuhn]

I have a reverse proxy also but can't get the skill to work. Normal connection via App/Web is no problem.

[@CriticalErA]

it FINALLY worked for me!! it took me countless hours because 443 wouldn't open. I called my ISP and got that resolved after a 2 hour phone call. They could not explain why it kept coming up as closed when it was opened on their end. Then after that...I kept getting a 404 error around the 8 minute mark. took me another 2 hours trying to figure that out but couldn't, so I started over, took my time and BOOM! Alexa discovered everything in my HA!!!!! thanks man, i really appreciate your video and my goodness the struggle was real!

[@Dmkjr]

Worked great. For those that were just lost in the steps -- I had to circle back to the 'Alexa Redirect URI' being in the US and apparently since the video was released they are in a different order. "Layla" didn't work but the 'Pitangui' did work. Afterwards, all was well.

[@pogiest1]

I followed this exactly. The only think I did slightly differently was because I use NGINX to route my sites I did not enter a port number in any of the fields as I do not enter one when I connect to my current instance both internally and externally. Everything appeared to work, I ran the test code and it does in fact list out all my devices (including the device I am specifically doing this for) and I was able to enable the skill without any issues. However after the app running it's discovery it came back with no new devices. I do not know how this would work as mine didn't find any new devices, but most of my devices are already connected to Alexa with the one main exception of the esphome device that I was trying to link to Alexa. Is there something that I may be doing wrong?

[@wenxinliu152]

I have the same issue

[@divlooper]

The same issue happens here too! I have done everything exactly as in the video, and the test output contain the device I'm looking for, but Alexa can find these devices!

[@cosmiclightning4723]

I'm using cloudflare for my external service and I have the same issue, does not discover any new devices

[@andreyborisov293]

Same issue for me. Any solutions?

[@lpt2007lpt]

Same here:( Any solution I am using cloudflare?

[@donatelonow]

Excellent, that's exactly what I was looking for a couple of hours ago and here you saved me hours of work, buddy!

[@EverythingSmartHome]

Thank you buddy, means alot! 🙏

[@janb25]

A Google Home Video like this would be very appreciated!

[@EverythingSmartHome]

I'll get on it 😅

[@Mark-el8hh]

That would be great! Thanks in advance.

[@HamishMilne1]

I've tried various videos to try and get this done - this was BY FAR the easiest to follow and most comprehensive. Thank you!

[@EverythingSmartHome]

Thank you, appreciate it 🙏

[@snakesms]

@@EverythingSmartHome Awesome video, made it work straight away!

[@anantanuragyadav]

This is awesome!!!!! I just linked Alexa with HA by using the externally available HA URL via cloudflare. Obviously, I followed your other video about cloudflare. You are the man!!!

[@Siemershh]

Hello, Amazon has announced that support for Python 3.7 will be discontinued in AWS. You should update to Python 3.11. Does the access as shown here still work and how is the update to 3.11 done? Can you maybe show that sometime? Thanks

[@marxdrive]

I can confirm that in September 2023, this still works. The interface is quite different but everything you need is still there! ......Thanks brother for the video ;)

[@geraldmitchell6271]

Dude, you are amazing. I just completed this entire process to include the entire Remote Access for FREE - DuckDNS + processes. Took a while but was so much fun and learned a ton of great stuff. Thanks a ton.

[@mattstein9939]

with a duckdns address did you add the port number for the base URL?

[@QuintDutch]

Even though this video is 4 years old. I just did all your steps(well some sites look different now and had to figure out where your steps are) but i got it working within the 20 mins. great explanation, thanks

[@Gromozeka1212]

For all those who has a error: invalid client_id or redirect uri. I had the same issue. Check your "account linking" url via web alexa page. 1. My url looked like this: client_id=layla.amazon ... redirect_uri=pitangui.amazon... Compare client_id & redirect_uri 2. Home assistant skill icon under Dev skill in my case has badge devUS As i understand somehow i choose US region. In aws i have chosen EU(Ireland) and in developer console in pasted layla But at the end i have different client_id and redirect_uri in my linking url. So i have changed layla to pitangui in "Your Client ID" and the result was the same as we see on 12:35. So, i forwarded 443 port to 8123 on my firewall. And after that everything worked correct. Question: Maybe someone know where to change region in developer amazon com /alexa", because i fill that somehow i have chosen US region instead of EU.

[@cezarysliwkowski722]

Hey Dmitrijs, I had the same issue and followed your advice, but than I had device discovery issue - could't detect any device after account linking. It turned out that in alexa dev console I had language set to English (US), but lambda function was created in Ireland (eu-west-1) Also my default language in Alexa app was English (US), so I migrated lambda function to US East (us-east-1) and everything worked perfectly. So it seems that lambda must be created in same region as your default Alexa language

[@shlosiiiii]

Amazon just sent an email saying that they are ending support for Python 3.7 in AWS Lambda. What adjustments do we need to do in order to be supported by Amazon?

[@gavynmilton9875]

Great tutorial! For someone with beginners knowledge, I was still able to follow and learn some stuff along the way. Yes, it is tricky if you're not familiar, but stick with it. This guy has changed my weekend from great to amazing!

[@thediabeticway9115]

Really liking this video setup but just struggling a bit to connect at video Time 12:03 of your video Not sure if it because I have not added my local Home Assistant URL in the Account Linking section, I added the one made from Cloudflare Domain One but my local Home Assistant is not secure could it be that? Any help on this would be much appreciated I just purchased a Domain for this purpose. Everything seem to go well until I tried to Enable it in Alexa App I'm a Web Developer but still stuck with confusions! Would also be great if you could do a Google Setup too.

[@Hypeex]

While your HA is running locally, is still has to be controller from the internet. So "local" here is not really what it sounds like. It would be much nicer if it could actually be controlled locally like how HomeKit does it. Regardless, great video!

[@EverythingSmartHome]

Yeah, I'm using the word "local" here to differentiate between the cloud version of Home Assistant but I know what you mean 😅 thanks!

[@andreyv1]

I don't have an "environment variables" box like you do around 7:10 mark. everything else was followed to a T. edit: after digging around for a good 20 minutes, you can find the environment variables by clicking on the "configuration" menu and then environment variables will be on the left hand side. a lot of the things in this video are in different spots which isn't surprising since it is almost 2 years old.

[@tamildesan837]

Thanks for sharing. It helped me today

[@maltrisky2966]

This was an amazing video and so simple to follow. Along with your other video on getting home assistant with an external URL I got this working in one go and now have full control again with my Alexa. Thank you so much!

[@EverythingSmartHome]

Thanks Dave, glad it was useful!

[@wagnerfontes2]

This is great, Lewis, thanks for the tutorial. Do you know if it is possible to do the integration the other way around? I mean, having HA control the devices recognized by Alexa? Similar to what you did to Google, in the video of Jan 18, 2023. I wonder if Alexa would let you monitor the devices, not just send blind commands...

[@DeepakCG]

Great detailed video on Alexa integration with HA, worked perfectly, appreciate your efforts. IF you have ur Home Assistant enabled on a external URL like DuckDNS (with port forwarding) then this Alexa integration with HA is a breeze as long as u correctly follow each step mentioned in this video. Note - Make sure u select the correct region in AWS console, I selected Ireland even though I am from India.

[@TheNikhilmishras]

Hey! How are you able to fix the Double NAT problem with Indian Broadbands? I am unable to access Home Assistant from outside because of this. Please help :D

[@DeepakCG]

@@TheNikhilmishras I am on Airtel broadband and haven’t faced any issues so far, just make sure u have forwarded port 443 in ur router (for my Airtel broadband setup I am using the ISP provided Modem in bridge mode with a Asus Wifi router) I have enabled Port forwarding on Asus router

[@TheNikhilmishras]

@@DeepakCG okay sure. I'll try that again! 😁

[@Andrew-di4cm]

Hoping you can help. I get to 6:30 and cannot figure out how to edit the config file. I have Home assistant installed on my Synology NAS through Docker and don't have visual studio installed nor can I for the life of me figure out how to install it. Is this doable on a container install? Followed you thus far

[@AFC19034life]

Is there a way to only expose single entities using this method? Every time I want to discover a new devices I get 100+ entities in Alexa and have to manually remove them each time.

[@dc857]

I realise this is old but for anyone with the same issue kzbin.info/www/bejne/ipDNn4Gpg9uhmdE shows how to exclude devices and include only the ones you want in the configuration.yaml

[@DavidGalloway-q7e]

Thanks again for your help! where is the environmrnt variables located now to add base_url and the Https ? I see tabs now to add code but not sure if I might be in the wrong location on the test section of your video at Time 7:30 I see to have lots of issues getting voice to work in Home Assistant and been 9 months now why I tend to sticking to companys APPS but id rather be in HA Its ok now I have figured its the Configurations Tab that then list the environment variables on the left

[@a-casa-mais-inteligente]

Awesome video! By the way, this does not differ from the home assistant cloud. The key difference is that home assistant cloud provides the entire stack as well as updates. The two methods are cloud based

[@cdarrigo]

Can we get an update of this video? The AWS and Alexa UIs have changed quite a bit and I can't figure out to get this created. There are options added / Removed in the UI from when this video was recorded. For example, is publishing the lamba the same as deploying it? there is a deploy lambda@edge but that needs some additional cloudfront trigger setup. UPDATE: Ok.. some of this confusion was me being a newb.. I rewatched it, traced all my steps and got it working. Thanks. BTW.. Very important the email account you use for your Alexa developer account MUST match the email address you use when signing into Alexa or you won't see your skill. (ask me how I know).

[@rob1971]

Another informative video, thanks Lewis! I'd be interested in seeing the Google Assistant version as well please 👍🏻

[@EverythingSmartHome]

Thanks Rob, always appreciate your support!

[@robcalogero]

Hello, I noticed this video is over a year old and I just purchased a HomeAssistant Yellow to add to my smart home.. I mainly use voice to control devices via Alexa and was wondering if this is still the best way to go local with my Alexa or is there a simpler method.

[@AlexDelPrete]

Lewis, thank you so much for this, I wanted to do it since a long time and I had no idea you made a video about it. It was really really easy thanks to your clear guide, and having a homelab behind traefik (behind a Cloudflare Tunnel) made it even easier for me. I really appreciate what you do here, keep it going. :)

[@EverythingSmartHome]

Thanks, appreciate it!

[@rodneyboyer206]

Some of the locations of things has been updated on the AWS console but I was still able to follow along and figure it out. I was outside my network while doing this tutorial and then the account linking wouldn't work no matter what I tried. I was about to give up but then your comment about "turning off wifi" made me realize I was connected to my VPN on my phone. Once I paused it, the account linking worked just fine. I also followed your Google Home video tutorial and have it set up as well. Thanks for everything and keep making great videos like this one!

[@julianstone5861]

Thanks for this, got it working after setting up an external URL to work with HTTPS (using another of your excellent videos). For all of us older UK users, at around 10 mins when setting up Account linking, authorise must be spelt authorize or you'll get a 'not found' error.

[@EverythingSmartHome]

Glad it was useful, thanks for watching!

[@JamesMarcumStockton]

VERY well done, excellent explanations, and just an all-around awesome walk-thru! Thank you.

[@EverythingSmartHome]

Thanks James, very much appreciate it!

[@JamesMarcumStockton]

@@EverythingSmartHome Getting my setup squared away thanks to all the useful vids!

[@EverythingSmartHome]

That's great to hear, makes me very happy!

[@MatthewWorton-n8x]

Amazing tutorial as just completed the setup. One thing to note which tricked me up is when typing authorise on one of the last steps(as you can't see it in the video clearly) use the American spelling authorize. Lewis keep up the amazing work. You are my go to man mainly on Home assistant tutorials. You have a subscriber

[@tseawell90]

thank you for this video. I can't believe how complicated this is

[@kenwhitlow9691]

Excellent Job!! I tried some time ago to set this up using someone else's KZbin video but could never get it to work - your step-by-step guides are so helpful. Ran across this video today and successfully completed it even though so many things have changed on the amazon sites. Thanks!

[@RealElwood1]

Do Google also please

[@EverythingSmartHome]

Will do!

[@connorthompson8303]

Quick question! Can I use the same execution role on multiple Lambda functions? I have set this up for my own HA instance, but I am in the process of setting it up at my parents house too. I am curious as to whether I can use the same execution role?

[@johannesbauerstatter9051]

Thank you for this easy to use video. The only problem is that when i choose Europe (Ireland) I can't find the Alexa Smart Home Trigger. It was only available in Virgina and there it worked for testing. I got my devices in Lambda but I was not able to find any devices in the end. I think this is because I am from Austria and choose Virgina. Any solutions?

[@pronownjenkins1041]

Thanks bud, watching you do this showed me where I went wrong, I never would have gotten the skill created properly without this!

[@allbymyself85]

thank you. Everything was perfectly set. Just a note, of course a lot of options have been moved around in AWS and in the dev console. So a little bit of digging and you will find a way to complete all successfully. Once again. AMAZING VIDEO!

[@_od_7825]

The tutorial is great. I've got it all working, however is there a way to limit what gets sent to the Alexa app? At the moment it has a list of all my automations, all of my input_booleans etc. There's a list of things that doesn't work with Alexa all listed in the app. As a result the app is really slow and finding things is very time consuming. I don't necessarily want every light bulb there, but I am happy to have grouped lights in their place. That kind of thing.

[@michaelcohen4048]

First - thanks so much for yet another excellent video! Unfortunately, I'm not sure the 2 things I was looking for are possible: 1) Be able to control zigbee light dimmers which paired to my Echo Show on HA; and 2) Be able to see some of my my camera which stream to HA on the Echo Show. My Alexa apps shows the camera devices but says "live view not supported"

[@guitargrin]

Massive props! it took me a while to get my HA docker instance available publicly available with cloudflare zero trust tunnels, but the rest of this tutorial was AMAZING! Thank you so much for taking the time to do this!

[@littlepetebexley]

I think my problems started when I switched from duckdns to cloudflare. Now I can't figure out how to repair it

[@Garethuk2006]

I can't get to the lambda section as shown in 4:01 as I get the following "Verify your credit card information is correct. Also, check your credit card activity to see if there’s a $1 authorization (this is not a charge). You may need to contact your card issuer to approve the authorization." do you have to add a payment card?

[@EverythingSmartHome]

Possibly, there is no charge though it's free

[@marcelogomes1268]

Thanks for the step-by-step! But in the video part 4:52, adding the trigger, don´t show up "alexa smart home" to me... Do you know how to proceed? Thanks a lot

[@EverythingSmartHome]

Thanks! Are you sure you chose the correct region as explained in the video? That's usually the reason that people are missing that option. Hope that helps!

[@virimpact]

Love your videos.....I arrived at the activation of the skill, but the Alexa app does not discover any device. Can you suggest how to fix this?

[@Nickl191]

I got stuck at 7:42 adding the base URL, every time i get a certificate error, but if i change the URL to HTTP from HTTPS it works fine. Not sure this is ideal though but i don't know how to fix this.

[@MaxFritzhand]

What theme are you using?

[@frannerickcim-kho4736]

I got this setup work and running, thanks for that... but i got a newbie question, how do i enable and link HA to Alexa after this setup? Also how do i expose those entities from HA to alexa? Do i need to do the nabu casa trial 1 mo th in order to make the settings come out on the HA instance? Thanks

[@joaopedros2]

I performed all the steps successfully when running the test and I see my devices in the code. I have remote access with coudflare and I did the whole tutorial without introducing port 8123 in the url. In the Alexa app I can log in to HA but it does not discover any device. Anything I should do?

[@abdam137]

Great video, I've linked mine up now, however, how can I get home assistant to see my echo show, so I can then get it to control it, like turn the screen off? Does this only allow Alexa to control the devices home assistant sees and not the other way around?

[@MatteoSignorini]

This tutorial is great but I am puzzled out by the fact that we need to enter DNS/pubIP and port in the BASE_URL of the test code for the lambda function. Wasn't it a "LOCAL" solution?

[@Conundrum191]

Just followed this and it worked perfectly. One question though, how do you also go the other way -- As in be able to now use Home Assistant routines to trigger Alexa devices?

[@AlanJones-vc9yr]

Hi Amazingly well presented, thank you. However I am struggling to match the steps to the actual Amazon screens as they seem to have changed considerably. I have some of the functions set but struggling with others, so cannot complete. Please can you offer some guidance ? Thanks in advance. Al

[@bubokroar5157]

Hey Lewis, just wanted to say thanks for this tutorial. I was banging my head against the wall after setting everything up and being unable to link the skill properly.... but after going off wifi on my phone (like you mentioned in the tutorial) the linking worked! Thanks again!

[@EverythingSmartHome]

Hello! Thank you for watching and the support, very much appreciate it and glad you got it working!

[@ladaloutevans]

Is it correct that I don't have the Alexa voice assistant as an option when I want to expose an automation to Alexa? I have created one for my lights that uses a helper button. I wanted Alex to be able to see this button. I can't figure out how to expose this to the Alexa app?

[@olufemiolatinwo9522]

Lewis, thanks so much for this indepth tutorial. Got it installed as you instructed. Please do I need to remove the original home assistant linking I setup with cloud originally on my mobile phone and do I need to remove the integration setup with cloud account from home assistant too and reconfigure it? Need your expertise before proceeding. The local account linking is working well, though not able to discover new devices it default to the originally linked cloud account and pull all the devices. Thanks

[@olufemiolatinwo9522]

Bought you a coffee cup too. You deserve much more

[@DavidCumps]

It's always fun to listen to these videos when Alexa is near you

[@sheminasalam]

How can I add just some of my entities in home assistant to Alexa with this ?

[@grahamvs]

So much has changed with the AWS website that it's not easy to follow along anymore. We really could use an updated video.

[@KaleoMgmt]

Thank you!! Took a bit of skip-back/rewatch, but got it going. I honestly appreciate how you walk us along letting us get the errors (BASE_URL, Failed Login, etc.), and then show how to fix it. Gave me a better understanding of What's happening and Why. AWS and the Developer Consol have changed some, but a little bit of clicking around got me to where I needed to be. Thank you!! (I know the site is "Buy me a Coffee", but feel free to use it for a pint! 😀)

[@EverythingSmartHome]

Haha thanks for the coffee Chris, appreciate it! Glad it was useful 🙏

[@grant_HH]

Thanks Lewis I have an Alexa account, but its a family account my wife's account is the primary I assume for this to work I need to set up a dev account linked to her amazon account?

Great video everything is working fine. But is there a way to chose switch device to share? Cause i just tried this and discovery 207 devices lmao. Alexa is crazy with so many devices. Would be nice if we could use the new TAB of voice in the HA voice assistant configuration

[@AFC19034life]

Did you find out a way of limiting entities being discovered? I’ve got a light I want to add. But don’t want to have it discover another 180 useless entities haha.

@@AFC19034life nop, i end up just using emulated hue

[@neildotwilliams]

I’m here because Paul Hibbert told me this is how to do it for free and linked to here, in case you notice an uptick in traffic 👍 Thanks to you both.

[@shashankgupta8340]

following the video, at 4:52 i donot see Trigger "Alexa Smart home" is there a way to add or i see only Alexa Skills Kit

[@stephenjohnston8460]

Awesome video, one minor thing. When I use m echo show with a screen, if I say Alexa turn plug off, it runs perfectly and turns the plug off. But on the echo screen it will show the previous state of the plug which would be on. Then if I say Alexa turn plug on, the screen shows the plug as off. It is a minor issue, but is there anyway around it? I tested the official cloud version for HA and it show the correct state of the plug, so Alexa turn plug off, shows the plug as off, Alexa turn plug on, shows the plug as on.

[@dcattewell]

Is there a updated version to this video? I see some Amazon parts have changed?

[@SebVEVO]

Will Alexa still need to go to cloud first each time you ask it to control a HA device?

[@overdhill56]

Could you update this as the IAM Management Console has changed and I could not follow past 4:49 as there is no Alexa Smart Home selection

[@EverythingSmartHome]

I'm guessing that's because you selected the wrong region. Select a supported region as explained in the video and it will appear :)

[@jamesgothard7881]

@@EverythingSmartHome It seems that they have changed the options menu from having two options one for the Alexa skills kit and one for Alexa smart home. Now it just has Alexa IOT and you can then choose a product either Alexa skills kit or Alexa Smart Home.

[@vba77]

Excellent video. If some one has trouble with "test" part with SSL related errors (which I did while switching my domain), all you need to do is to upgrade the python runtime version from 3.7 or 3.8 to the latest (I had to use 3.11).

[@space_banane6033]

Quick Question : can i use the Alexa tts ? so tell homeassistant to say something over alexa? does that work?

[@glen_nz]

Most of the way through this but have hit a snag....when I go to enable the skill and log in, it says Error: Invalid redirect URI. I'm publishing HomeAssistant via Nginx Proxy Manager on port 443.

[@glen_nz]

UPDATE: changed to pitangui and can log in but discovery fails. I'm in New Zealand. Will try recreating the Lambda function in the US users region and see if this makes a difference.

[@glen_nz]

UPDATE 2: Creating in the US-East region, discovery is successful.

[@chimeranzl9147]

@@glen_nz thanks for this, also in NZ and about to setup!

[@dragosmc17]

can you give more details about how you solved this? same setup, tried to recreate it in US east from Ireland and I get the same error, login works but discovery fails. When testing the lambda function it gives 404 not found or 400 bad request

[@riebread13]

hi, id like to see a video about the uses this has while integrated, new into this stuff but trying to find out if it worth doing

[@88digitalelf]

Is there away to select which Home Assistant devices to interface with Alexa?

[@andrewshaw1525]

Many thanks for this video. There are some interface changes but I was able to follow the instructions. I had been putting this off because I'd heard it was difficult, but it became necessary when I began moving all my smart lights from a Hue Hub to a ConBee II stick in my Home Assistant, and your video was perfectly detailed and easy to understand. Subscribed :)

[@vaderaguk]

Amazing guide. Coupled with your Cloudflare video this was incredible :) Would love a follow up on if there is a way to a) choose which devices are revealed to Alexa and b) if there is a way to change the functions of devices which Alexa sees! Once again, thank you!

[@etiennehody5324]

Hi, have you found a way to make it work alongside ? I have a 404 error went I try the test on AWS. And I have the same problem with Google Home, the credential page never shows up when I want to link HA with it. Any idea please ?

[@5h4mr0Ck]

@@etiennehody5324 I set up Google Home after following the cloudflare video. When I did Google home I didn't put in the port number - all the rest was the same - and it worked fine. I've done the same for Alex, and it's working up to the discovery of the devices and it's failing there.

[@talvien9061]

@@5h4mr0Ck Same here, getting Authorization error on the lambda function test...

[@Flaterly01]

@@talvien9061 Cloudflare is probably blocking AWS as they think its a bot. Disable the bot security and check your events if any custom rules are blocking AWS from posting

[@danninoash]

Hey, thanks for the great video!! loved it! I gotta question please: soon i will end my Cloudflare domain and i wanted to use my new domain i bought (much cheaper via NameCheap). I wonder if I have to do the whole process again to just update the new domain in the Alexa developer portal?? Thanks!!

[@steverhysjenks]

After finally getting around to do this in the last night. The only point to be aware of is when doing the IAM role AWS has you as Global. So when you create the LAMBDA function double check there you are on the right region. Also some of the menu navigation has changed in AWS but its will fairly obvious what you need to do (I got it working just following this guide and repeating a section because of the region aspect).

[@whitewidowja]

Layout in AWS change a bit, but still perfectly doable ! Thanks a lot! Keep doing what you do best : Great work !

[@barrycooper9365]

Great video, I've just followed your video with some minor problems which I resolved along the way until I tried the Discovery which I managed to get working it actual showed my equipment as per your video. I then copied the code which i pasted into the Amazon Developer endpoint when I tried to save I got the following error! Failed to save skill information The Lambda ARN arn:aws:lambda:eu-west-2:XXXXXXXXXXXX:function:HomeAssistant is not valid for any of the supported regions. I have no idea what to do next, can you help? Barry

[@TheMrmaxno]

I did it according to your instructions and it works! It is excellent!!! Thanks for your work

[@CoachHomeUK]

ok I think I'm missing something because at 4:51 you select the 'Alexa Smart Home' but I can only find 'Alexa Skills Kit' have I not installed something? Any help would be appreciated.

[@EverythingSmartHome]

I'm guessing you selected the wrong region

[@CoachHomeUK]

@@EverythingSmartHome oh ok so when you pickid ireland it was so that shows up? I'm in Lincolnshire so picked London

[@EverythingSmartHome]

Yep that's right, it's mentioned in the video 😜

[@CoachHomeUK]

@@EverythingSmartHome ok got much further this time. Doing the test I get an error "errorMessage": "2022-01-26T01:03:41.647Z 97b02722-a3c9-4ba9-94a8-21be60500e1f Task timed out after 3.00 seconds" any ideas? :)

[@CoachHomeUK]

oh scratch that just used another port and, success :D

[@AnoNymous-lp5tb]

I followed your guide step by step and complete it successfully with the exception of discovery. When I did the test inside AWS, all entities showed up. But I enabled the skill in my alexa app it doesn't show any of my entities. Do you know what could possibly wrong with it?

[@EverythingSmartHome]

Did you remember to add the smart_home config to home assistant and restart?

[@AnoNymous-lp5tb]

@@EverythingSmartHome yes. smart_home config is in my config. alexa: smart_home: and all entities are showing up in the AWS test area. tried to disabled and enable the alexa skill and still no go. is it possible that in can conflict with other alexa integration like the custom alexa media player from HACS?

[@stoconnor]

@@AnoNymous-lp5tb I have the same problem, did you get this working?

[@cooperlutz2525]

I have the same problem

[@stoconnor]

I got it sorted. Your lambda needs to be in the same region as your skill. e.g US Skill needs to have N Virginia lambda, EU Skill to Ireland lambda

[@fredericomachado4116]

I just saw a video about emulated hue. I was wondering what the best option is

[@WeSmiths]

You probably know that AWS has changed the format of their Lambda Service. It's good that your video still works up to 7:06 when you use the 'Environment Variables' section - unfortunately these no longer appear where you show and I can't find them. Any help appreciated.

[@2dnik213]

The Environment Variables are now under "Configuration" tab and then in the left menu.

[@WeSmiths]

@@2dnik213 Thank you very much - got it

[@dominicstenzel7631]

@@2dnik213 Great !!!

[@mechrekt]

Hi, thank you for your video! Can you tell me how can I ask Alexa to do something that is not just turn on or off a device in my home assistant, but do some HA automation, for example Alexa clean my kitchen and start an automation that controls my robot vacuum? For now I created an helper toggle switch that runs that automation, but this way I need to say Alexa turn on clean the kitchen 😁 Thank you!

[@jaume6118]

My ISP blocked the 443 redirection, It;'s posible to use 8443 port instead and works perfectly.

[@xSazo]

I love you

[@maxmaurin277]

You are a genius. Had the same problem with 443 and 8443 works like a charm.

[@AndyZich]

It worked! I consider myself tech savvy but the AWS lambda function and alexa developer console skills are above my head. It took a few hours and a ton of video pausing but this video got me accross the finish line! Thanks man!! I hope Amazon doesn't impose any breaking changes because I'm not monitoring release notes so I'm cossing my fingers this stays working.

[@DanangWidiantoro]

can you discover the devices too? no device is detected in my end

[@defrom7147]

​@@DanangWidiantoro I have the same issue. Did you figure out how to get your devices ?

[@DanangWidiantoro]

@@defrom7147 I did actualy

[@bearhntr928]

Yet another great video -- even though it is 2 years old... learning lots. I clicked on your link for the "WRITTEN ARTICLE" and I am not able to find it. As I was hoping that the URLs for AWS and ALEXA DEVELOPER would be there.

[@VishwamittraBhardwaj]

hi, i have followed your tutorial, however i am using cloud flare tunneling for another of your tutorials ,I am not able to get the external ip and port Number for adding Environmental variables, if you could guide with that it will be great.

[@cyberdotone]

In the Alexa app, when I enable HomeAssistant it takes me to HomeAssistant Cloud, and to Naub Casa. What can I do to restore HomeAssistant?

[@eflores641]

I don't show the Alexa Smart Home trigger, only Alexa Skill Kit and then Apache Kafka. How can I proceed?

[@eflores641]

Nevermind I wasn't following instruction correctly. I got it.

[@EverythingSmartHome]

Glad you got it, yep you need to select the correct region

[@eflores641]

@@EverythingSmartHome Unfortunately the Alexa app is not finding my devices, like others have said. No errors anywhere to be found either. EDIT: Got it working, I re-did everything and I believe I missed the Deploy button the first time. Thanks for this!

[@ausguy4385]

Can have local home assistance and Tuya and run alexa on the HA cloud?

[@tamildesan837]

Thanks for the wonderful video tutorials. You saved lot of readings and gave the extract within 16 minutes. Your new subscriber here. I followed this video and got the Alexa integration done today. One note which I have observed, sharing here. If you already own an Alexa device, trying to integrate with your existing setup, create the Alexa developer and AwS cloud accounts with same ID that you have setup your Alexa. Due to some issue I had to use different account, at the end found the dev skill did not show up in my Alexa app. 😢 Managed it to solve using Amazon Household option but it’s not what you want to end up with. 😅

[@sosumitoo]

Is it possible to include/exclude entities like with Nabu Casa?

[@andreanizzola4645]

I got it working a few months ago but it is much slower than using nabucasa subscription or connecting the devices software directly to alexa. Is this normal or did I miss something? It takes 5-10s to do any command trough home assistant but from home assistant to the devices it's instant.

[@RichardTrautmann]

Great video, got it working for me. Do you know a way to delete ALL ghosted entities in Alexa? It now has all my "old" nabu casa devices as well as a bunch of other old devices I no longer use. I can only see to delete one by one thru the app which is several clicks each. Terrible on Amazon's part. Do you know a way? Or maybe it's possible through the API somehow?