Subscribing to Home Assistant Cloud by Nabu Casa also supports the people that build and maintain Home Assistant. If you can spare it, support the project 👍
do you have another way to support home assistants? I want to support when I want and not have a subscription. plus learning to do that myself is rewarding ^.^
exactly the same here, the extra testing and varification he does along the way is super handy. I think I found where I got it wrong before too although I cant check until tomorrow. You didnt happen to be forwarding to port 443 instead of 8123 did you?
Bro THANK YOU!!! AFTER 5HOURS OF TRYING, READING AND WATCHING TUTORIAL I CLICKED on your video - TH-cam SHOULD PUT YOUR VIDEO ON TOP OF SEARCH RESULTS - GREAT STUFF
@grayson Adams, great video! There is only one downside in this that you lose local access to Home Assistant. A better way will be to use NGINX Home Assistant SSL proxy add-on to serve the certificates instead. This way you have both local and remote access. :) Regards Andy
I think this is my first ever comment on TH-cam. Just wanted to give a shout out to your excellent video series. I'm very tech/network savvy, but really had not gotten into external home networking because I didn't want to have to pay for static IP addresses from my ISP, deal with SSL certs, etc. You video did a fantastic job of showing each and every step to understand all the things you were doing, and thought through all the corner cases. Very nicely done!
I stumbled across your videos earlier today and have found them very clear and informative. I've been using Home Assistant for a while, but I've held off on experimenting very much as there's just so much to learn. Thank you for making it more accessible.
awesome video thank you for breaking it down so cleanly and easy to follow. I was about to give up on home assistant till I came across this video. you made it nice and easy to follow and thank you for showing some of the "errors" you might get along the way if you don't do HTTPS and also explaining why we are doing different steps and how to check that things are working along the way. can't wait to watch your other videos on HA :)
Grayson, thank you... your video for setting up duckdns was exactly what I needed. I've watched many other videos and as "jimbo retired sparky" stated earlier, they stopped short of key points that get newbies like myself in trouble... but yours helped tremendously and well explained !
Hi! I set up correctly the forwarding in my FritzBox but no luck. I have HA in VirtualBox like you and Network attached to bridged adapter.. any advice? Solved, my provider got me a private Dynamic ip. They give only that or public static, so now requested the public static. Thanx for the great video!
Really appreciate this series so far! At the end of all the how-tos, could you maybe do a "Home Assistant Ideas" video that shows some of your favorite automations done with Home Assistant?
Super video that really guides you step by step on how to access your home assistant remotely. Big thumbs up and definitely subscribing to the channel. 👍🏻
Awesome video. Subscribed immediately. Insanely clear and detailed. Not new to programming, but newish to networking and HA. Going through the series now. BTW, I dig the DrZzs haircut. Now you just need to do the floating head narration! 😂🤣
Great series of videos, Grayson. They have allowed me to do my first installation of Home Assistant. I do have a major problem, however. I have an ATT Arris BGW210-700 with fiber, which I have read have lots of problems with home assistant. I was able to get to this video and get duckdns working and actually use the secure domain, but since I did that, I can only login from my phone when I am not on my home wifi and I can no longer log in at all from my computer. I have tried the Android app it does not work on wifi or on cell signal. With so many steps involved setting all this up, I am a bit lost trying to troubleshoot. I am fairly old but relatively computer savvy, so i hopefully can try whatever you suggest. Thank you again for the helpful Home Assistant series.
Great video. One small issue though, I was pausing the video as I made the changes. When I got to the end and it didn't work, I thought my Home Assistant setup was bad, and had no idea how to fix it. It took me about 5 minutes to try https: and it worked, then I restarted your video - THEN you mention that issue. Argh!
Hi Grayson, thank you for this great tutorial. I have a problem setting things up. My duckdns add on works good on Home Assistant and updates the ip but when I checked my status in my router I found that actual ip that I can access my home is different than the ip when I search on google via whats my ip. I think my service provides changes the ip with a NAT. Is there a way to change the duckdns addon settings which it can resolve my real ip address?
excellent video mate. The way you varify and explain each step is second to none on youtube. Thats a big like and subscribe from me. ps - you hair grows so fast ;-)
Awesome video. I will be following and learning from these. I am new to Home Assistant. Now that I have the duckdns setup how do I access my Home Assistant locally to get to the folders so I can add HACS?
Great video!!! I set remote access to my home assistant!
3 ปีที่แล้ว
Grayson, thank you very much! Your step by step tutorial helped me a lot. One question left. Is it true that the Home Assistant mobile app can no longer be reached via the old local address? Do I have to change that adress to the new duck.dns address?
Hi, and thanks for a great video. I intend to follow the steps described in the video. But before I doi that I have a question: When I do the set of the DuckDNS it will pick up the public ip address on the location where I do the installation. That´s my understanding from the video. If I later on will move the Hom Assistant to another geographical location (with another public ip address) - will that be possible? If it is - how is proceedure to change the ip address setting?
Great info! Thank you! One question, though: I am using MS Edge as my default browser and it seems to act the same as FireFox when access locally (not recognizing the certificate). Is there a fix for this in Edge (or Firefox)?
Hi Grayson, thanks for the video. I am now able to access HA through DuckDNS, however am still struggling with the certificate verification on local access. Seems the iOS/ipadOS app does not accept the local address with the duckdns certificate at all. Any suggestion on how I could solve this?
Thanks for the tutorial! What can be the reason that port forwarding not working, I'm trying to verify with my local ip:8123?? (in tutorial 6:21). I defined in the router correctly
Good Morning Grayson I followed your nice tutorial and installed duckdns to obtain remote access to my HA. However I lost access to it via PuTTY which was working perfectly before this. Are these 2 items conflicting to each other? Is there any way to recover my PuTTy? There are so many things are have to be done through commands so PuTTY is very necessary tool for us. Thanks, Val.
Do you know of any other ways besides port forwarding and Nabu Casa for remote access? My ISP allows port forwarding after a $15/month ordeal. Wondering if there’s any last options to play/learn with.
Me too, I'm searching. It seems that port forwarding not works for me even I did this at least 10 times... I remotely access my Home Assistant with "chrome desktop remote" extensions. Try it if it suits you. My home assistant works on a virtualbox windows 10. So if you're on PC you rather can use this solution but I'm still not able to use my Google assistant with my home assistant devices.
Hey Grayson, thank for this video. After finsing this long proccess and setting duckdns and port forwarding I found out that I can't enter HA from the companion app at my phone. On the PC it works great, but on the app no matter what kind of addresses I tried, both internal and external, nothing changed and I'm stuck out of my HA instence on the app
my hass always break when i wrote the http: and the rest on file configuration, i dont know why. havent able to run duckdns as well with all the setting
Thank you for the great videos! These have been a great help for me. I have been having an issue, which you may have already addressed but I didn't see if you have. Sorry in advance for the long winded question here. I am experiencing an issue accessing Home Assistant using the secure DuckDNS domain while inside my LAN. It times out every time. The only way I can access Home assistant using the DuckDNS domain is if I try from outside of my LAN. I can of course access internally using the local address. This is fine if I'm using my computer inside the LAN, but if I'm using my phone app, I can no longer connect unless I am outside of my LAN. Is this by design? I did notice in the video you were successful in accessing via the DuckDNS domain, were you actually doing it from internally or external? I also do see in the Home Assistant app there are fields for internal and external addresses but, it doesn't seem to switched between the two for me. Thank you again for taking the time to make these videos.
Thanks for a good video - Had some fun for a minute with the error ERROR: deploy_challenge hook returned with non-zero exit code but it was when copying and pasting the Token I had a leading space. This should have been easy for me as I have a static IP and a DNS name already but because I already have a Webserver on PORT 80 I couldn't use the LetsEncrypt addon option so I had to setup a DuckDNS account and do it that way. At the end of the day I don't really see the URL in the App so its all the same to me.
@grayson Adams, thank you. I have another question if you dont mind. If I dont want access from outside, what is the best way to turn that feature off? I thought if I would just stop the Duck DNS device on home assistant it would work, but I was able to continue to access from outside. Thx!
I think the DuckDNS service on your home assistant is just updating DuckDNS when your ISP WAN address changes. There are a couple things you could do to disable remote access. Turning off port forwarding from your router should make it not possible to reach your home assistant. You could also delete your duckdns domain so that name no longer resolves to your IP address. If you do that but leave port forwarding on your router, someone could still access your HA if they had your WAN IP address and port.
Great tutorials, wish I found these sooner, new subscriber. Any idea why I can launch File Editor in Supervisor by clicking "OPEN WEB UI" but when I add it to the sidebar and click from there, I get "401: Unauthorized"
Hi! thanks for you video's they help me a lot! but i have a problem now. once i use this DuckDNS and ssl setup (also with Unifi) the TTS google cast feature is not working anymore? (the "chime" sound plays on the google home, but the text is not played) Can somone help me out?
IS THERE anything special I have to do to install node red? And on mosquitto mqqt is the ip address, for example, 192.168.0.45 sames as home assistant or do I have to put in the . I am using Ubuntu 16.05
Hi Grayson, Really enjoying the series on Home Automation and going smoothly up until Port Forwarding. Hope you can help. I have a Huawei router for my ISP, and my Ubiquiti USG Gateway is plugged into this. From there I have my LAN and Wifi networks. I think the forwarding is getting stuck in here somewhere. In my Huawei Router I have created a Port Forwarding rule from anywhere to port 8123. The rules require I have to specify an external start port value, and external end port value. I selected 443 as I think this is correct. For the internal host IP I have used the IP address of my Ubiquiti Switch, as that is the only part of my ubiquiti set up that the Huawei router is recognising as connected. It does not recognise the home assistant ip address. The internal port is 8123. Then I have created a rule within my ubiquiti network to port from the Huawei router (I also tried the from anywhere option), to port forward to my home assistant ip address. Unfortunately I still can't see the Home Assistant via my external ip or my duckdns address. Please help! This has been going so well up to now!
Hey! Great Video but i can't access the Home Assistant via the Domain. It says, it took too long to Respond. And Eventually time outs.... Would Appreciate a bit of help here :) I'm Fairly new to this Home Assistant Platform and Raspberry Pi Overall.
I, I follow the steps and I couldn't make it work. My duck domain pings my ip, but do not resolve...what I'm doing wrong? I also tried nginx, no success either. But let's encrypt is saying "Port 80 is already in use by something else on the host", anyone can help??? thanks in advance!
Word of warning: make sure you have a copy of you HA instance you can restore is this doesn't work for you. Can be tricky to get back in if there is an issue with this [speaking from experience]. I have tried this twice now, first time had to throw out my instance and start again, second time I was able to restore back to pre-duckdns settings but you have to flush browsing cache and reset everything. In this video I notice Grayson is forwarding 8123 while other videos I have seen its 443???
@@GraysonAdams thanks for your guide. I followed it and have it up and running. Phone app works great from outside my local network. However, when to go into HA via the duckdns url from inside my network, it is painfully slow. Some pages load ok while nodeRed just won't load. I am running HA on a QNap VM. I can login via the local static ip I have HA setup on but have to use https but you get that first nag screen before you login. Any ideas?
@@GraysonAdams awesome thanks for the quick response. I'm working on it now. When I typed in what is my IP it was giving me the pv6 not b4. Did some searching and found the public V4 and it's working now. Thanks for the awesome videos.
Hi, Thanks for the tutorial! I have next issue with my configuration file -"Invalid config for [http]: not a file for dictionary value @ data['http']['ssl_certificate']. Got '/ssl/fullchain.pem' not a file for dictionary value @ data['http']['ssl_key']. Got '/ssl/privkey.pem'. (See /config/configuration.yaml, line 16)." someone can assist?
there is a fundamental issue with the remote access to home assistant using DuckDNS add-on - once setup, you need to have an internet connection to access your home assistant, even you are at your home, connected to your home network. As things happen, we do lost the internet connection from time to time. Once that happens, I don't know how you can still gain the access to your home assistant. You might lost the control of your connected devices. That is really a bad thing in my view. I hope that this issue could be fixed in the future. By the way, using https on a local IP address still requires an internet connection, as it needs to verify the certificate any way. so, you cannot really have the local access to your home assistant without internet.
@@GraysonAdams I had it working without an issue but I had to set up a new router. I've forwarded 8123 to 8123 but its not working. For some reason the router is forwarding to a NAS on my network rather that to the machine running HA even though I've specifically set it the the right internal ip address. Very strange indeed.
@@fred7flinstone Connect to the GUI or command prompt for your NAS and confirm what IP address it believes it is assigned to / fixed to. Does it match what the router claims, or is it contesting over the same IP as the Hassio VM / deployment?
@@GraysonAdams I connect to the nas via ip 192.168.1.253 and connect to HA server on 192.168.1.24. I've set the port forward to 192.168.1.24, but when I load it loads the NAS.
![ILLSLICK - WINTER IS COMING [Official Video]](http://i.ytimg.com/vi/dwTMeM1zIhQ/mqdefault.jpg)
![[UNCUT]"ทนายตั้ม" แฉยับ! ความลับสวรรค์ ใครคือ "บิ๊กเทวดา" ของบอสพอล l คนดังนั่งเคลียร์ l 15 ต.ค. 67](http://i.ytimg.com/vi/ru9fpSaUwdA/mqdefault.jpg)
Subscribing to Home Assistant Cloud by Nabu Casa also supports the people that build and maintain Home Assistant. If you can spare it, support the project 👍
do you have another way to support home assistants? I want to support when I want and not have a subscription.
plus learning to do that myself is rewarding ^.^
Can we start promoting other platforms? HA slowy becoming politically inclined and when you want apolitical environment then they throwing bans.
@@asdkjh4370in what way is it becoming political?
Best video out there on this subject. There is another well known HA guy who does one and I could NEVER get it to work! Thank you!
exactly the same here, the extra testing and varification he does along the way is super handy. I think I found where I got it wrong before too although I cant check until tomorrow. You didnt happen to be forwarding to port 443 instead of 8123 did you?
Bro THANK YOU!!! AFTER 5HOURS OF TRYING, READING AND WATCHING TUTORIAL I CLICKED on your video - TH-cam SHOULD PUT YOUR VIDEO ON TOP OF SEARCH RESULTS - GREAT STUFF
Boy, if it isn't the best guide on how to setup external access to HA, IDK what it.
Thanks for that!
Thanks Grayson, very clear and concise. Tried other videos and they stopped short on some of the points that get the newbie into trouble.
@grayson Adams, great video! There is only one downside in this that you lose local access to Home Assistant. A better way will be to use NGINX Home Assistant SSL proxy add-on to serve the certificates instead. This way you have both local and remote access. :)
Regards
Andy
I think this is my first ever comment on TH-cam. Just wanted to give a shout out to your excellent video series. I'm very tech/network savvy, but really had not gotten into external home networking because I didn't want to have to pay for static IP addresses from my ISP, deal with SSL certs, etc. You video did a fantastic job of showing each and every step to understand all the things you were doing, and thought through all the corner cases. Very nicely done!
Thanks for taking the time to put this together for us. Your help is much appreciated, sir!
I stumbled across your videos earlier today and have found them very clear and informative.
I've been using Home Assistant for a while, but I've held off on experimenting very much as there's just so much to learn.
Thank you for making it more accessible.
Good job bro, very clear information. i finally mark HA is not difficult. looking forward your video how to connect camera, cctv, etc
Perfect. Clear and well presented explanation of this subject. Well done.
awesome video thank you for breaking it down so cleanly and easy to follow. I was about to give up on home assistant till I came across this video. you made it nice and easy to follow and thank you for showing some of the "errors" you might get along the way if you don't do HTTPS and also explaining why we are doing different steps and how to check that things are working along the way. can't wait to watch your other videos on HA :)
I watched like three other videos on the same topic and this one was the only one that made me understand it and make it work! Thanks a lot!
Grayson, thank you... your video for setting up duckdns was exactly what I needed. I've watched many other videos and as
"jimbo retired sparky"
stated earlier, they stopped short of key points that get newbies like myself in trouble... but yours helped tremendously and well explained !
Hi! I set up correctly the forwarding in my FritzBox but no luck. I have HA in VirtualBox like you and Network attached to bridged adapter.. any advice?
Solved, my provider got me a private Dynamic ip. They give only that or public static, so now requested the public static. Thanx for the great video!
Really appreciate this series so far! At the end of all the how-tos, could you maybe do a "Home Assistant Ideas" video that shows some of your favorite automations done with Home Assistant?
Alex S I plan to do tutorials on automations themselves soon!
Grayson Adams - GTOTechnology Excellent, thanks
Super video that really guides you step by step on how to access your home assistant remotely. Big thumbs up and definitely subscribing to the channel. 👍🏻
Awesome video. Subscribed immediately. Insanely clear and detailed. Not new to programming, but newish to networking and HA. Going through the series now.
BTW, I dig the DrZzs haircut. Now you just need to do the floating head narration! 😂🤣
Thanks for the tutorial! I have just a remark to make, if you are using a docker image for HA you will not find the Supervisor tab
Thank you so much for this video!! I've been tripping over how to do this for a long time and I finally have external access.
Cool insights. Thanks for the detailed tutorial. Even though I have been using HA for quite some time but your detailing is amazing
Great series of videos, Grayson. They have allowed me to do my first installation of Home Assistant. I do have a major problem, however. I have an ATT Arris BGW210-700 with fiber, which I have read have lots of problems with home assistant. I was able to get to this video and get duckdns working and actually use the secure domain, but since I did that, I can only login from my phone when I am not on my home wifi and I can no longer log in at all from my computer. I have tried the Android app it does not work on wifi or on cell signal. With so many steps involved setting all this up, I am a bit lost trying to troubleshoot. I am fairly old but relatively computer savvy, so i hopefully can try whatever you suggest. Thank you again for the helpful Home Assistant series.
YES!!!!!!!! this worked! I've been faffing with this for days, but this worked thanks so much!
I followed another youtube video and I could not get it to work. With yours, it works! Thanks! Subscribed.
This is an awesome video. Thanks for explaining context to make it even more interesting.
Great videos man. This worked like a charm. Easy, quick, concise. Thank you.
Fantastic video! Totally made everything easy to comprehend. Any chance you would happen to do a video for SmartThings and HA integration??!!
Great video! Followed the steps and everything worked as shown! Liked and subscribed!
Great video. One small issue though, I was pausing the video as I made the changes. When I got to the end and it didn't work, I thought my Home Assistant setup was bad, and had no idea how to fix it. It took me about 5 minutes to try https: and it worked, then I restarted your video - THEN you mention that issue. Argh!
Hi Grayson, thank you for this great tutorial. I have a problem setting things up. My duckdns add on works good on Home Assistant and updates the ip but when I checked my status in my router I found that actual ip that I can access my home is different than the ip when I search on google via whats my ip. I think my service provides changes the ip with a NAT. Is there a way to change the duckdns addon settings which it can resolve my real ip address?
Hey Grayson. Thank you very much for the great video!! Keep up the good work ;-) Greetings from Denmark!
excellent video mate. The way you varify and explain each step is second to none on youtube. Thats a big like and subscribe from me.
ps - you hair grows so fast ;-)
Your video is so helpful. Thanks for uploading such videos. Appreciated
Hi Grayson, great Video thanks, all setup and working. Nice to see some up to date advice. Keep up the good work. Jamie
thanks for helping me with this. super clear advice. only forgot to change the agree terms but that fixed everything :)
Excellent and helpful.
Awesome video. I will be following and learning from these. I am new to Home Assistant. Now that I have the duckdns setup how do I access my Home Assistant locally to get to the folders so I can add HACS?
Great video!!! I set remote access to my home assistant!
Grayson, thank you very much! Your step by step tutorial helped me a lot. One question left. Is it true that the Home Assistant mobile app can no longer be reached via the old local address? Do I have to change that adress to the new duck.dns address?
thank you for super clear guidance - much appreciated
Hi, and thanks for a great video. I intend to follow the steps described in the video. But before I doi that I have a question: When I do the set of the DuckDNS it will pick up the public ip address on the location where I do the installation. That´s my understanding from the video. If I later on will move the Hom Assistant to another geographical location (with another public ip address) - will that be possible? If it is - how is proceedure to change the ip address setting?
Fantastic tutorial, thanks so much! Subscribed!
bro just grew hair in the whole process
Thank you bro! :)
Another excellent tutorial!!!, Thank you👍.
Great info! Thank you! One question, though: I am using MS Edge as my default browser and it seems to act the same as FireFox when access locally (not recognizing the certificate). Is there a fix for this in Edge (or Firefox)?
Another amazing tutorial! Thank you!
Hi Grayson, thanks for the video.
I am now able to access HA through DuckDNS, however am still struggling with the certificate verification on local access. Seems the iOS/ipadOS app does not accept the local address with the duckdns certificate at all. Any suggestion on how I could solve this?
I thought i lost my HA. thank you, your 15:04 saved me.😃
Not every HA installation has a supervisor. Is there a way without add-ons using only HA core?
Thanks for the tutorial! What can be the reason that port forwarding not working, I'm trying to verify with my local ip:8123?? (in tutorial 6:21). I defined in the router correctly
Me too
Thanks and much appreciated. Nice detailed video
Good Morning Grayson I followed your nice tutorial and installed duckdns to obtain remote access to my HA. However I lost access to it via PuTTY which was working perfectly before this. Are these 2 items conflicting to each other? Is there any way to recover my PuTTy? There are so many things are have to be done through commands so PuTTY is very necessary tool for us. Thanks, Val.
Thanx! So great how you explain it!
Do you know of any other ways besides port forwarding and Nabu Casa for remote access? My ISP allows port forwarding after a $15/month ordeal. Wondering if there’s any last options to play/learn with.
Me too, I'm searching. It seems that port forwarding not works for me even I did this at least 10 times...
I remotely access my Home Assistant with "chrome desktop remote" extensions. Try it if it suits you.
My home assistant works on a virtualbox windows 10. So if you're on PC you rather can use this solution but I'm still not able to use my Google assistant with my home assistant devices.
Very good info, thank you Pelon.
Very good videos! Have 3b Pi not in use and planning to test HA next to my Homey hub.
Thanks bro...yes you provided really a solid information..
Hey Grayson, thank for this video.
After finsing this long proccess and setting duckdns and port forwarding I found out that I can't enter HA from the companion app at my phone. On the PC it works great, but on the app no matter what kind of addresses I tried, both internal and external, nothing changed and I'm stuck out of my HA instence on the app
my hass always break when i wrote the http: and the rest on file configuration, i dont know why. havent able to run duckdns as well with all the setting
Thank you for the great videos! These have been a great help for me. I have been having an issue, which you may have already addressed but I didn't see if you have. Sorry in advance for the long winded question here. I am experiencing an issue accessing Home Assistant using the secure DuckDNS domain while inside my LAN. It times out every time. The only way I can access Home assistant using the DuckDNS domain is if I try from outside of my LAN. I can of course access internally using the local address. This is fine if I'm using my computer inside the LAN, but if I'm using my phone app, I can no longer connect unless I am outside of my LAN. Is this by design? I did notice in the video you were successful in accessing via the DuckDNS domain, were you actually doing it from internally or external? I also do see in the Home Assistant app there are fields for internal and external addresses but, it doesn't seem to switched between the two for me. Thank you again for taking the time to make these videos.
Thanks for a good video - Had some fun for a minute with the error
ERROR: deploy_challenge hook returned with non-zero exit code
but it was when copying and pasting the Token I had a leading space. This should have been easy for me as I have a static IP and a DNS name already but because I already have a Webserver on PORT 80 I couldn't use the LetsEncrypt addon option so I had to setup a DuckDNS account and do it that way. At the end of the day I don't really see the URL in the App so its all the same to me.
Very well done video - excellent!
So helpful, thanks much. Cheers!
Great video dude!
Nice job dude, thanks very much!
I can login via duckdns but then i always get unable to connect. Any ideas?
really i love this man
How about using the TOR add-on to have remote access? Could you check that out.
Thanks for the video definitely will donate.
And if you forward the port to 443, you can remove at the end of the address: 8123?
but set in configuration.yaml server_port:443
@grayson Adams, thank you. I have another question if you dont mind. If I dont want access from outside, what is the best way to turn that feature off? I thought if I would just stop the Duck DNS device on home assistant it would work, but I was able to continue to access from outside. Thx!
I think the DuckDNS service on your home assistant is just updating DuckDNS when your ISP WAN address changes. There are a couple things you could do to disable remote access. Turning off port forwarding from your router should make it not possible to reach your home assistant. You could also delete your duckdns domain so that name no longer resolves to your IP address. If you do that but leave port forwarding on your router, someone could still access your HA if they had your WAN IP address and port.
Excelente video!!! TAHNKS
Great tutorials, wish I found these sooner, new subscriber. Any idea why I can launch File Editor in Supervisor by clicking "OPEN WEB UI" but when I add it to the sidebar and click from there, I get "401: Unauthorized"
I solved it by cleaning cookies on my chrome navigator
Can I do this with ddns?
Thanks for the video, but how do I secure my home assistant over remote access now?
i have a static ip address provided by my isp. if i use that and not duckdns will i lose a lot of security?
Do I need to have a public IP in order to use duckdns approach?
Hi! thanks for you video's they help me a lot!
but i have a problem now.
once i use this DuckDNS and ssl setup (also with Unifi)
the TTS google cast feature is not working anymore?
(the "chime" sound plays on the google home, but the text is not played)
Can somone help me out?
On the QNAP container I don"t see the Supervisor Tab ?
IS THERE anything special I have to do to install node red? And on mosquitto mqqt is the ip address, for example, 192.168.0.45 sames as home assistant or do I have to put in the . I am using Ubuntu 16.05
Thanks!! It worksss
Thank you so much.
Hi Grayson, Really enjoying the series on Home Automation and going smoothly up until Port Forwarding. Hope you can help. I have a Huawei router for my ISP, and my Ubiquiti USG Gateway is plugged into this. From there I have my LAN and Wifi networks. I think the forwarding is getting stuck in here somewhere. In my Huawei Router I have created a Port Forwarding rule from anywhere to port 8123. The rules require I have to specify an external start port value, and external end port value. I selected 443 as I think this is correct. For the internal host IP I have used the IP address of my Ubiquiti Switch, as that is the only part of my ubiquiti set up that the Huawei router is recognising as connected. It does not recognise the home assistant ip address. The internal port is 8123. Then I have created a rule within my ubiquiti network to port from the Huawei router (I also tried the from anywhere option), to port forward to my home assistant ip address. Unfortunately I still can't see the Home Assistant via my external ip or my duckdns address. Please help! This has been going so well up to now!
please help after setting up when i use duck dns url it loops back to my isp gateway
i cant get this to work. Whats the dangers of not having the ssl in your yaml?
Is there a way to use http internally while using https for external connections?
Mep Mann Not that I’m aware of unfortunately
Hey! Great Video but i can't access the Home Assistant via the Domain.
It says, it took too long to Respond. And Eventually time outs....
Would Appreciate a bit of help here :)
I'm Fairly new to this Home Assistant Platform and Raspberry Pi Overall.
You've given no information to work with.
Go to community.home-assistant.io and post there with a lot more information
@@fanuchman Hey! Sorry for the Inconvenience. What kind of Details would be needed ?
I, I follow the steps and I couldn't make it work. My duck domain pings my ip, but do not resolve...what I'm doing wrong? I also tried nginx, no success either. But let's encrypt is saying "Port 80 is already in use by something else on the host", anyone can help??? thanks in advance!
How does this work if my public IP address is an ipv6 and not ipv4?
Word of warning: make sure you have a copy of you HA instance you can restore is this doesn't work for you. Can be tricky to get back in if there is an issue with this [speaking from experience]. I have tried this twice now, first time had to throw out my instance and start again, second time I was able to restore back to pre-duckdns settings but you have to flush browsing cache and reset everything.
In this video I notice Grayson is forwarding 8123 while other videos I have seen its 443???
Good points. You can port forward almost any port. It’s up to you which one you’d like to use. Many ISP’s prevent forwarding over 80/443.
@@GraysonAdams thanks for your guide. I followed it and have it up and running. Phone app works great from outside my local network. However, when to go into HA via the duckdns url from inside my network, it is painfully slow. Some pages load ok while nodeRed just won't load. I am running HA on a QNap VM. I can login via the local static ip I have HA setup on but have to use https but you get that first nag screen before you login. Any ideas?
You pull off a shaved head well. Especially when you say "scrub bar."
OK, DuckDNS is working but no HA with https...
Port forwarding is asking for start port and end port which one would the 8123 go to
If it’s asking for a range, just only put 8123
You can put 8123 for the external and internal port if you haven’t changed Hone Assistant’s default.
@@GraysonAdams awesome thanks for the quick response. I'm working on it now. When I typed in what is my IP it was giving me the pv6 not b4. Did some searching and found the public V4 and it's working now. Thanks for the awesome videos.
@@GraysonAdams how long should the reconnection take after restarting the server
30 seconds to a minute. If you enabled SSL make sure you’re using HTTPS
@@GraysonAdams yep... I'm an idiot. Thanks again.
Hi, Thanks for the tutorial! I have next issue with my configuration file -"Invalid config for [http]: not a file for dictionary value @ data['http']['ssl_certificate']. Got '/ssl/fullchain.pem' not a file for dictionary value @ data['http']['ssl_key']. Got '/ssl/privkey.pem'. (See /config/configuration.yaml, line 16)." someone can assist?
Had the same issue. Restarted the duckDNS and in the duckDNS logs I saw that it created the fullchain.pem. After that there was no conf issues.
@@felixtredal7297 BAM. Thanks Felix!
@@felixtredal7297 tnx, helped me!
dang u scared me at 15:03 lol
Same here!!
Dick move, Grayson! 😬🤣😂
After autentificatione ..... Loading data ..... and Unable to connect to Home Assistant. 😓
I have the same problem. It happens after adding the http: section to the configuration file ☹️
hello guys. just lost acces to my HA after the ssl and restart. anyone to help me out please?
I ran into the same issue and I had to start from square one.
of course I WILL, haha
there is a fundamental issue with the remote access to home assistant using DuckDNS add-on - once setup, you need to have an internet connection to access your home assistant, even you are at your home, connected to your home network. As things happen, we do lost the internet connection from time to time. Once that happens, I don't know how you can still gain the access to your home assistant. You might lost the control of your connected devices. That is really a bad thing in my view. I hope that this issue could be fixed in the future. By the way, using https on a local IP address still requires an internet connection, as it needs to verify the certificate any way. so, you cannot really have the local access to your home assistant without internet.
I don't get why port 443 wasn't forwarded.
It was exposed over port 8123 in the video instead. SSL can be served over any port.
@@GraysonAdams I had it working without an issue but I had to set up a new router. I've forwarded 8123 to 8123 but its not working. For some reason the router is forwarding to a NAS on my network rather that to the machine running HA even though I've specifically set it the the right internal ip address. Very strange indeed.
@@GraysonAdams I'm using NGINX Home Assistant SSL proxy add on.
@@fred7flinstone Connect to the GUI or command prompt for your NAS and confirm what IP address it believes it is assigned to / fixed to. Does it match what the router claims, or is it contesting over the same IP as the Hassio VM / deployment?
@@GraysonAdams I connect to the nas via ip 192.168.1.253 and connect to HA server on 192.168.1.24. I've set the port forward to 192.168.1.24, but when I load it loads the NAS.
There is much better and simpler way. Just buy Keenetic Router
And then?