Alexa with Home Assistant Local for FREE Without Subscription

In this video we are looking at how to integrate Alexa with Home Assistant local without having the Nabu Casa subscription or the cloud version of Home Assistant. If you aren't comfortable with doing these steps then I would definitely encourage you to use a Nabu Casa subscription which costs just $5 per month and it keeps the amazing Home Assistant project going and funds the developers for the Home Assistant project. You can find it at this link:

Hardware to run Home Assistant:

Lambda Function main code:

Lambda Test Code:

If you'd like to support me and future projects:
Patreon:

Buy Me a Coffee:

Written Article:

EVERYWHERE YOU CAN FIND ME:
Everything Smart Home Community Discord:

#homeassistant #smarthome
________________________

Some of the links above are affiliate links, where I earn a small commission if you click on the link and purchase an item. You are not obligated to do so, but it does help fund these videos in hopes of bringing value to you!

Music:
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

[EverythingSmartHome]

Make sure to check out the Google Home video here:

[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.

[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.

[bradpeabody]

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.

[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.

[janb]

A Google Home Video like this would be very appreciated!

[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 thanks man, i really appreciate your video and my goodness the struggle was real!

[HamishMilne]

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

[donatelonow]

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

[geraldmitchell]

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.

[marxdrive]

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

[gavynmilton]

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!

[anantanuragyadav]

This is 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!!!

[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!

[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.

[maltrisky]

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!

[julianstone]

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.

[Gromozeka]

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 ...
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.

[rob]

Another informative video, thanks Lewis!

I'd be interested in seeing the Google Assistant version as well please 👍🏻

[rodneyboyer]

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!